Integrating shared documents and video feeds during a conference call discussion

The conference platform integrates presenter video feeds within shared documents, addressing impersonal presentations and improving focus on both presenter and content, enhancing engagement and efficiency.

JP2026031780APending Publication Date: 2026-02-24GOOGLE LLC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025245591
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-12-28
Filing Date
2025-12-11
Publication Date
2026-02-24

AI Technical Summary

Technical Problem

Existing conference platforms fail to effectively integrate video feeds of presenters with shared documents during a conference call, leading to impersonal presentations and difficulty in focusing on both the presenter's image and document content, especially when multiple presenters are involved.

Method used

A conference platform that integrates video feeds of presenters within specific regions of a shared electronic document, allowing creators to designate areas for presenter video feeds, ensuring participants can focus on both the presenter and document content simultaneously.

Benefits of technology

Enhances engagement and clarity in conference discussions by allowing participants to focus on both the presenter and document content, reducing computing resource consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026031780000001_ABST
    Figure 2026031780000001_ABST
Patent Text Reader

Abstract

A GUI is provided to participants of the conference call that enables presentation of the electronic document. An electronic document for presentation to a participant is identified.SOLUTION: The first portion of the document comprises a first video feed integration object. The second portion comprises a second video feed integration object. The first object indicates a first region of the first portion to include a first video feed associated with a first client device of the first participant. The second object indicates a second region of the second portion to include a second video feed associated with a second client device of a second participant. The first and / or second portions of the document are provided via the GUI. The first video feed is included in the first region indicated by the first object. The second video feed is included in the second region indicated by the second object.SELECTED DRAWING: Figure 7A
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] Aspects and implementations of the present disclosure relate to integrating shared documents with video feeds during a conference call discussion. [Background technology]

[0002] A video or audio-based conference call discussion may be conducted between multiple participants via a conference platform. The conference platform includes tools that enable multiple client devices to be connected to each other over a network and share audio data (e.g., user speech recorded through a microphone on the client device) and / or video data (e.g., video captured by a camera on the client device or video captured from a screen image on the client device) with each other for efficient communication. The conference platform may also include tools that enable participants in a conference call to share documents displayed through a graphical user interface (GUI) on their associated client devices with other participants in the conference call. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] U.S. Patent Application Publication No. 2021 / 0076105 Summary of the Invention [Problem to be solved by the invention]

[0004] The following summary is a simplified summary of the disclosure to provide a basic understanding of some aspects of the disclosure. This summary is not an exhaustive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of particular embodiments of the disclosure or any claims. Its sole purpose is to present some concepts of the disclosure in a simplified form as a prelude to the more detailed description that is presented later. [Means for solving the problem]

[0005] In some implementations, systems and methods are disclosed for integrating a shared document with a video feed during a conference call discussion. In some implementations, a graphical user interface (GUI) enabling presentation of an electronic document is provided to participants in a video conference call. An electronic document is identified for presentation to the participants in the video conference call. A first portion of the electronic document comprises a first video feed integration object, and a second portion of the electronic document comprises a second video feed integration object. The first video feed integration object indicates a first region of the first portion of the electronic document comprising a first video feed associated with a first client device of a first participant in the video conference call. The second video feed integration object indicates a second region of the second portion of the electronic document comprising a second video feed associated with a second client device of a second participant in the video conference call. At least one of the first or second portions of the electronic document is provided for presentation to one or more participants in the video conference call via the GUI. The first video feed is contained in a first area indicated by a first video feed integration object, and the second video feed is contained in a second area indicated by a second video feed integration object.

[0006] Aspects and embodiments of the present disclosure will be more fully understood from the following detailed description of various aspects and embodiments of the disclosure and from the accompanying drawings, which should not be construed to limit the disclosure to any particular aspect or embodiment, but are for purposes of illustration and understanding only. [Brief explanation of the drawings]

[0007] [Figure 1] 1 illustrates an exemplary system architecture according to an implementation of the present disclosure. [Figure 2] 1 is a block diagram illustrating an exemplary conferencing platform and an exemplary video feed integration engine according to an implementation aspect of the present disclosure. FIG. [Figure 3A] 1 illustrates an example of designating one or more regions of an electronic document to include video feeds of conference call participants during presentation of the electronic document, according to an implementation of the present disclosure. [Figure 3B] 1 illustrates an example of designating one or more regions of an electronic document to include video feeds of conference call participants during presentation of the electronic document, according to an implementation of the present disclosure. [Figure 3C] 1 illustrates an example of designating one or more regions of an electronic document to include video feeds of conference call participants during presentation of the electronic document, according to an implementation of the present disclosure. [Figure 4A] 1 illustrates an example of integrating a shared electronic document with video feeds of conference call participants during a conference call discussion, according to an implementation of the present disclosure. [Figure 4B] 1 illustrates an example of integrating a shared electronic document with video feeds of conference call participants during a conference call discussion, according to an implementation of the present disclosure. [Figure 4C] 1 illustrates an example of integrating a shared electronic document with video feeds of conference call participants during a conference call discussion, according to an implementation of the present disclosure. [Figure 5]10 illustrates another example of designating one or more regions of an electronic document to include video feeds of conference call participants during presentation of the electronic document, according to an implementation of the present disclosure. [Figure 6A] 10 illustrates another example of integrating a shared electronic document with video feeds of conference call participants during a conference call discussion, according to an implementation of the present disclosure. [Figure 6B] 10 illustrates another example of integrating a shared electronic document with video feeds of conference call participants during a conference call discussion, according to an implementation of the present disclosure. [Figure 7A] 10 illustrates yet another example of designating one or more regions of an electronic document to include video feeds of conference call participants during presentation of the electronic document, according to an implementation of the present disclosure. [Figure 7B] 10 illustrates yet another example of designating one or more regions of an electronic document to include video feeds of conference call participants during presentation of the electronic document, according to an implementation of the present disclosure. [Figure 8] 10 illustrates an example of a generated file for an electronic document according to an implementation of the present disclosure. [Figure 9] 1 illustrates a flow diagram of an exemplary method for integrating a shared document with a video feed during a conference call discussion, according to an implementation aspect of the present disclosure. [Figure 10] FIG. 1 is a block diagram illustrating an exemplary computer system according to an implementation aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0008] Aspects of the present disclosure relate to integrating shared documents and video feeds during a conference call discussion. A conference platform can enable video or voice (audio)-based conference call discussions between multiple participants via respective client devices connected over a network, and can share each other's voice data (audio data, e.g., user speech recorded via a microphone of a client device) and / or video data (e.g., video captured by a camera of a client device) during the conference call. In some examples, the conference platform can enable a large number of client devices (e.g., up to 100 or more client devices) to be connected via a conference call.

[0009] Participants in a live conference call (e.g., a video conference call) may be reluctant to use a shared document (e.g., a slide presentation document, a word processing document, a web page document, etc.) to engage other participants in the conference call. For example, a presenter (speaker, speaker) of the conference call may prepare a document comprising content that the presenter plans to discuss in the conference call. Existing conference platforms allow the presenter to share a document displayed via the GUI of a client device associated with the presenter with other participants in the conference call via the conference platform GUI on each of their client devices while discussing the content contained in the shared document. However, such conference platforms do not effectively display the content of the shared document while simultaneously displaying an image representing the presenter via the conference platform GUI on client devices associated with the other participants. For example, some existing conference platforms may not provide an image representing the conference call presenter along with the shared document via the conference platform GUI, preventing the presenter from effectively engaging with participants via the conference platform's video capabilities. As a result, the presentation of a shared document during a conference call may feel impersonal or mechanical because it may not hold the conference call participants' attention for long (or at all). Other existing conference platforms may display the contents of the shared document through a first portion of the conference platform GUI and an image representing the presenter through a second portion of the conference platform GUI. However, if the image of the presenter is displayed in a separate portion of the conference platform GUI from the content of the shared document, participants may not be able to simultaneously focus on or concurrently observe visual cues or gestures provided by the presenter while attending to the content provided by the shared document.

[0010] In some examples, multiple presenters may be associated with a document shared with participants in a conference call via a conference platform GUI. For example, two or more presenters may be associated with the shared document, with a first presenter explaining content contained in a first portion of the shared document (e.g., a first slide of a slide presentation document), a second presenter explaining content contained in a second portion of the shared document (e.g., a second slide of the slide presentation document), and so on. In conventional systems, presenters of the shared document cannot seamlessly transition the discussion between different presenters. For example, when an electronic document is shared via a conventional conference platform, the electronic document may be presented via a first portion of the conference platform GUI, and video feeds associated with one or more participants in the conference call (e.g., including the presenters) may be presented via a second portion of the conference call. The size of the first portion of the conference platform GUI may be significantly larger (e.g., the size of the video feed may be significantly smaller) than the size of the video feed presented via the second portion of the conference platform GUI. If the size of the video feed presented via the second portion of the conference platform GUI is small, participants in the conference call discussion may not be able to easily identify the video feed of the presenter of the shared document. Participants may also not be able to easily notice that the presentation or discussion related to the shared document is transitioning from the first presenter to the second presenter. For these additional reasons, conventional conference platforms do not allow conference call presenters to effectively engage with participants in the conference call discussion, thereby preventing clear and effective transitions between presenters.

[0011] Aspects of the present disclosure address the above and other shortcomings by providing techniques for integrating a shared document with video feeds associated with one or more conference call presenters via a conference platform GUI on client devices associated with the conference call participants. The conference platform may provide a GUI that enables the presentation of an electronic document to video conference call participants. A client device associated with the conference call presenter may send a request to the conference platform via the GUI on a client device associated with the conference call participant to initiate a document sharing operation to share an electronic document (e.g., a slide presentation document, etc.) displayed via the GUI for the client device with the conference call participants. A first portion of the electronic document (e.g., a first slide, a first portion of the first slide, etc.) may include a first video feed integration object. The first video feed integration object may indicate (point to, point to, represent, point to) a first region of the first portion of the electronic document that will include a video feed generated by a first client device of the first conference call participant (e.g., the conference call presenter or another participant). In some embodiments, a second portion of the electronic document (e.g., a second slide, a second portion of the second slide, etc.) can include a second video feed integration object that can indicate (point to, point to, represent, point to) a second region of the second portion of the electronic document that includes a video feed generated by a second client device of a second participant in the conference call (e.g., another presenter in the conference call, etc.).

[0012] In some embodiments, the first video feed integration object and / or the second video feed integration object may be associated with an identifier of a particular user and / or a particular client device connected to the conferencing platform. For example, a creator and / or editor of an electronic document may provide an indication (e.g., via a conferencing platform GUI or another GUI, such as a collaborative document platform GUI) that a first region indicated by the first video feed integration object comprises a video feed generated by the first client device during the presentation of a first portion of the electronic document and / or that a second region indicated by the second video feed integration object comprises a video feed generated by the second client device during the presentation of a second portion of the electronic document. In other or similar embodiments, the first video feed integration object and / or the second video feed integration object may not be associated with an identifier of a particular user and / or a particular client device. Alternatively, the creator and / or editor of the electronic document may provide an indication that the first video feed integration object and / or the second video feed integration object provide a video feed associated with a client device that meets certain criteria (e.g., the voice (audio) recording component of the client device is unmuted, the camera component of the client device is activated, etc.) during presentation of the first and / or second portions of the electronic document. Thus, the conference platform may identify the first and / or second client device for obtaining and presenting a video feed by determining that the first and / or second client device meets certain criteria during presentation of the first and / or second portions of the electronic document.

[0013] In response to receiving a request to initiate a document sharing operation, the conference platform can identify the electronic document and provide the first and / or second portions of the electronic document for presentation via the conference platform GUI. When the first portion of the electronic document is presented via the conference platform GUI (e.g., during a first time period), the conference platform can acquire a video feed generated by a first client device (e.g., during the first time period) and include the acquired video feed in a first area indicated by a first video feed integration object. The video feed can show a first participant in the conference call during the presentation of the first portion of the electronic document. Thus, the video feed showing the first participant can be integrated into the first portion of the shared electronic document. Similarly, when a second portion of the electronic document is presented via the conference platform GUI (e.g., during a second time period), the conference platform can acquire a video feed generated by a second client device (e.g., during a second time period) and include the acquired video feed in a second area indicated by a second video feed integration object. The video feed can show the second participant during the presentation of the second portion of the electronic document. Thus, a video feed showing the second participant may be integrated into the second portion of the shared electronic document. Examples of video feed(s) associated with the first client device and / or the second client device are shown in Figures 4B-4C and 6A-6B, which are described in further detail herein.

[0014] Aspects of the present disclosure provide techniques for integrating video feeds of one or more presenters of a conference call discussion with a shared document during the conference call discussion. Aspects of the present disclosure enable a creator and / or editor of an electronic document to indicate which regions of the electronic document should include video feeds associated with each presenter of the conference call discussion. The creator and / or editor can further specify specific presenters and / or specific client devices (e.g., meeting one or more criteria during the presentation) for the indicated regions, such that the conference platform can acquire video feeds representing such presenters and / or video feeds generated by such client devices and can include the acquired video feeds in the indicated regions of the shared document during the conference call discussion. When the electronic document is shared with participants in the conference call discussion via the conference platform GUI, the conference platform can include the video feeds of the specific presenters and / or video feeds generated by the specific client devices in the indicated regions. Accordingly, embodiments of the present disclosure provide a mechanism for presenting video feeds of conference call presenters within defined regions of a shared electronic document during a conference call discussion. Creators and / or editors of electronic documents can more effectively plan for conference call discussions by indicating specific regions of the electronic document that should include the video feed of each conference call presenter. Conference call presenters are enabled to effectively engage with participants in the conference call discussion because the presenter's video feed is integrated into the content of the electronic document rather than being a separate part of the conference platform GUI. Additionally, conference call participants are enabled to focus their attention on an image representing the presenter along with the content contained in the document.Thus, conference call discussions can be conducted effectively and efficiently. Because conference call discussions are conducted effectively and efficiently, the conferencing platform can thereby consume fewer computing resources (e.g., processing cycles, memory space, etc.), and such resources can be made available for other processes associated with the conferencing platform or other systems.

[0015] 1 illustrates an exemplary system architecture 100 according to an implementation of the present disclosure. The system architecture 100 (also referred to herein as the “system”) includes client devices 102A-102N, a data store 110, a conferencing platform 120, and a collaborative document platform 130, each connected to a network 108. In an implementation, the network 108 may include a public network (e.g., the Internet), a private network (e.g., a local area network (LAN) or a wide area network (WAN)), a wired network (e.g., an Ethernet network), a wireless network (e.g., an 802.11 network or a Wi-Fi network), a cellular network (e.g., a Long Term Evolution (LTE) network), a router, a hub, a switch, a server computer, and / or combinations thereof.

[0016] In some implementations, data store 110 is a persistent (non-transitory) storage device capable of storing data as well as data structures for tagging, organizing, and indexing the data. Data items may comprise audio data and / or image data, according to embodiments described herein. In other or similar embodiments, data items may correspond to documents displayed via a graphical user interface (GUI) on client device 102, according to embodiments described herein. Data store 110 may be hosted by one or more storage devices, such as main memory, magnetic or optical disks, tapes or hard drives, NAS, and SAN. In some implementations, data store 110 may be a network-attached file server, and in other embodiments, data store 110 may be some other type of persistent storage device, such as object-oriented and relational databases, that may be hosted by conferencing platform 120 and / or collaborative document platform 130 or one or more different machines coupled to conferencing platform 120 and / or collaborative document platform 130 via network 108.

[0017] The conference platform 120 may enable users of client devices 102A-102N to connect with one another via conference calls, such as video or audio conference calls. A conference call refers to an audio and / or video call in which participants in a call can connect to multiple additional participants. The conference platform 120 may enable users to join and participate in video and / or audio conference calls with other users of the platform. While embodiments of the present disclosure refer to multiple participants (e.g., three or more) connecting via conference calls, it should be noted that embodiments of the present disclosure may be implemented with any number of participants (e.g., two or more) connecting via conference calls. Further details regarding the conference platform 120 are provided below.

[0018] Each of client devices 102A-102N may comprise a computing device such as a personal computer (PC), laptop, mobile phone, smartphone, tablet computer, netbook computer, network-connected television, or the like. In some implementations, client devices 102A-102N may also be referred to as a “user device.” Each of client devices 102A-102N may comprise a web browser and / or a client application (e.g., a mobile application or a desktop application). In some implementations, the web browser and / or client application may display a graphical user interface (GUI) provided by conferencing platform 120 for a user to access conferencing platform 120. For example, a user may join and participate in a video conference or an audio conference via a GUI provided by conferencing platform 120 and presented by the web browser or client application. In other or similar implementations, the web browser and / or client application may display a GUI provided by collaborative document platform 130 for a user to access collaborative document platform 130. For example, users may access (eg, create, edit, view, etc.) collaborative documents through a GUI provided by collaborative document platform 130 and presented by a web browser or client application.

[0019] Each client device 102A-102N may include one or more audiovisual components capable of generating audio and / or image data that is streamed to the conference platform 120. In some implementations, the audiovisual component may include a device (e.g., a camera) configured to capture images and generate image data associated with the captured images. For example, the camera of a client device 102 may capture images of conference call participants in a surrounding environment (e.g., background) during a conference call. In additional or alternative implementations, the audiovisual component may include a device (e.g., a microphone) for capturing audio signals representing a user's speech and generating audio data (e.g., an audio file) based on the captured audio signals. The audiovisual component may include another device (e.g., a speaker) for outputting audio data to a user associated with a particular client device 102A-102N.

[0020] Electronic document platform 130 may enable users of client devices 102A-102N to create, edit (e.g., collaboratively with other users), access, or share electronic documents (e.g., stored in data store 110) with other users. In some embodiments, electronic document platform 130 may enable users to create or edit files (e.g., electronic document files, etc.) through a content viewer user interface. In some embodiments, each client device 102A-102N may be equipped with a content viewer. A content viewer may be an application that provides a user interface for users to view, create, or edit the content of files, such as electronic document files. In one example, a content viewer may be a web browser that can access, retrieve, and / or navigate files served by a web server. In another example, a content viewer may be a standalone application (e.g., a mobile application, etc.) that enables users to view, edit, and / or create digital content items. In some embodiments, a content viewer may be provided by electronic document platform 130. In some embodiments, one or more files created or otherwise made accessible via the content viewer may be stored in the data store 110.

[0021] As shown in FIG. 1 , electronic document platform 130, in some embodiments, can include a document management component 132. Document management component 132 can be configured to manage access to specific documents by users of electronic document platform 130. For example, client device 102 can request a specific file corresponding to an electronic document from electronic document platform 130. Document management component 132 can identify the file (e.g., stored in data store 110) and determine whether a user associated with the client device is authorized to access the requested file. In response to determining that the user is authorized to access the requested file, document management component 132 can provide client device 102 with access to the file. Client device 102 can provide the user with access to the file via a content viewer GUI, as described above.

[0022] As described above, a user can create and / or edit an electronic document via a content viewer GUI of a client device associated with the user. In some embodiments, the electronic document can be or correspond to a slide presentation document, a Word document, a spreadsheet document, or the like. The electronic document platform 130 may include a document editing component 134 configured to enable a user to create and / or edit an electronic document. For example, a client device 102 associated with a user of the electronic document platform 130 can send a request to the electronic document platform 130 to create a slide presentation document based on a slide presentation document template associated with the electronic document platform 130. The electronic document platform 130 can generate a file associated with the slide presentation document based on the slide presentation document template and provide the user with access to the slide presentation document via the content viewer GUI. In another example, a client device 102 associated with a user of the electronic document platform 130 can send a request to access an electronic document (e.g., a slide presentation document) via the content viewer GUI. The document management component 132 can retrieve a file associated with the requested electronic document, as described above. The document editing component 134 can provide a user with access to an electronic document via a content viewer GUI. The user can edit one or more portions of the electronic document via the content viewer GUI, and the document editing component 134 can update a file associated with the electronic document to include the edits to the one or more portions.

[0023] In some embodiments, a user, via a content viewer GUI, can provide an indication of a region of an electronic document that will include a video feed of a presenter in a conference call discussion (e.g., facilitated by the conference platform 120) when the electronic document is shared with participants in the conference call discussion (e.g., via the conference platform GUI). A user can provide an indication of a region of an electronic document by adding a video feed integration object to one or more regions of the electronic document via the content viewer GUI. A region that includes a video feed integration object can indicate a region of the electronic document that will include a video feed of the presenter, as described above. In some embodiments, a user can add multiple video feed integration objects to separate portions of an electronic document. A user can also, in some embodiments, provide an indication of a particular user of the conference platform 120 that will be represented in the video feed included in the region indicated by each video feed integration object. In other or similar embodiments, a user can provide an indication of a particular client device 102 connected to the conference platform 120 that will generate the video feed included in the region indicated by the video feed integration object. Further details relating to adding a video feed integration object to a portion of an electronic document are provided herein with respect to FIGS. 3A-3C, 4A-4B, and 7.

[0024] In some embodiments, conference platform 120 may include a conference management component 122. Conference management component 122 may be configured to manage conference calls between multiple users of conference platform 120. In some embodiments, conference management component 122 may provide a GUI (also referred to herein as a conference platform GUI) for each client device 102 to enable users to watch and listen to each other during a conference call. In some embodiments, conference management component 122 may also enable users to share documents (e.g., slide presentation documents, word processing documents, web page documents, etc.) displayed via the GUI on an associated client device with other users. For example, during a conference call, conference management component 122 may receive a request to share a document displayed via the GUI on a first client device associated with a first participant in the conference call with other participants in the conference call. Conference management platform 122, in some embodiments, may modify the conference platform GUI on client devices 102 associated with the other conference call participants to display at least a portion of the shared document.

[0025] The conference platform 120 may also, in some embodiments, include a video feed integration engine 124. The video feed integration engine 124 may be configured to detect whether one or more portions of a document shared with conference call participants via the conference platform GUI include a video feed integration object. In response to determining that one or more portions of the shared document include a video feed integration object, the video feed integration engine 124 may determine a client device that generates a video feed to be integrated into the area of ​​the shared document that includes the video feed integration object. The client device 102 may be associated with a particular participant in the conference call discussion or may meet one or more video feed integration criteria. Since the audiovisual component of the determined client device 102 is capable of generating a video feed, the client device 102 may transmit the generated video feed to the conference platform 120, as described above. In response to receiving the video feed, the video feed integration engine 124 may provide the video feed within the area of ​​the shared document indicated by the video feed integration object. Further details related to the video feed integration engine 124 and video feed integration objects are provided herein.

[0026] In some implementations, conference platform 120 and / or electronic document platform 130 may operate on one or more computing devices (e.g., rack-mounted servers, router computers, server computers, personal computers, mainframe computers, laptop computers, tablet computers, desktop computers, etc.), data stores (e.g., hard disks, memory, databases), networks, software components, and / or hardware components that may be used to enable users to connect to other users via conference calls. In some implementations, the functionality of conference platform 120 and / or electronic document platform 130 may be provided by two or more machines. For example, in some implementations, the functionality of conference management component 122 and / or video feed integration engine 124 may be provided by two or more separate server machines. In another example, the functionality of document management component 132 and / or document editing component 134 may be provided by two or more separate server machines. Conference platform 120 and / or electronic document platform 130 may also include websites (e.g., web pages) or application backend software that may be used to enable users to connect to other users via conference calls. It should be noted that in some other implementations, the functionality of conferencing platform 120 and / or electronic document platform 130 may be provided by fewer machines. For example, in some implementations, conferencing platform 120 and / or electronic document platform 130 may be integrated into a single machine.

[0027] In general, functionality described in an implementation as being performed by conferencing platform 120 and / or electronic document platform 130 may also be performed on client devices 102A-102N in other implementations, where appropriate. In addition, functionality attributed to a particular component may be performed by different or multiple components operating together. Conferencing platform 120 and / or electronic document platform 130 may also be accessed as a service offered to other systems or devices through appropriate application programming interfaces, and thus are not limited to use on a website.

[0028] Although implementations of the present disclosure have been described from the perspective of conference platform 120 and users of conference platform 120 participating in video and / or audio conference calls, the implementations generally may apply to any type of telephone call or conference call between users. Implementations of the present disclosure are not limited to conference platforms that provide users with conference call tools. Additionally, while implementations of the present disclosure have been described from the perspective of electronic document platform 130 and users of electronic document platform 130 accessing electronic documents, the implementations generally may apply to any type of document or file. Implementations of the present disclosure are not limited to electronic document platforms that provide users with document creation, editing, and / or viewing tools.

[0029] In implementations of the present disclosure, a "user" may be represented as a single individual. However, other implementations of the present disclosure encompass a "user" that is a set of users and / or an entity controlled by an automated source. For example, a set of individual users integrated as a community in a social network may be considered a "user." In another example, an automated consumer may be an automated ingest pipeline, such as a topic channel, of conferencing platform 120 and / or electronic document platform 130.

[0030] In addition to the above, the systems, programs, or functionality described herein may provide users with controls that allow them to choose both when to allow and enable the collection of user information (e.g., information about the user's social network, social actions or activities, occupation, user preferences, or the user's current location) and whether to send content or communications from the server to the user. Furthermore, certain data may be treated in one or more ways before being stored or used so that personally identifiable information is removed. For example, the user's identity may be treated so that the user cannot be identified with personally identifiable information, or so that the user's geographic location from which location information is obtained may be generalized (e.g., to the city, zip code, or state level) so that the user's specific location cannot be determined. Thus, users may have control over what information about them is collected, how that information is used, and what information is provided to them.

[0031] 2 is a block diagram illustrating an example conferencing platform 120, an example electronic document platform 130, and an example video feed integration engine 124, according to an implementation of the present disclosure. As described with respect to FIG. 1, the electronic document platform 130 can provide users of the client devices 102 with tools for creating, editing, and / or viewing electronic documents via the GUI of a content viewer of the client devices 102. The conferencing platform 120 can provide users of the client devices 102 with tools for joining and participating in video and / or audio conference calls.

[0032] Electronic document platform 130, in some embodiments, can include a document management component 132 and / or a document editing component 134. As described with respect to FIG. 1, document management component 132 can be configured to manage access to particular electronic documents 210 by users of electronic document platform 130. Document editing component 134 can be configured to enable users to create and / or edit electronic documents 210. While FIG. 1 illustrates client device 102A connected to electronic document platform 130, it should be noted that, according to embodiments of the present disclosure, any of client device(s) 102 described with respect to FIG. 1 can be connected to electronic document platform 130 and provided with access to electronic documents 210.

[0033] In some embodiments, client device 102A can send a request to electronic document platform 130 (e.g., via network 108) to access electronic document 210, as described above. In other or similar embodiments, client device 102A can send a request to create and / or edit electronic document 210, as described above. In some embodiments, client device 102A can send the request(s) in response to detecting interaction with one or more GUI elements of a content viewer GUI by a user associated with client device 102A. In response to receiving the request(s), document management component 132 and / or document editing component 134 can provide the user with access to the requested electronic document 210 via the content viewer GUI. FIG. 3A illustrates an exemplary content viewer GUI 300, in accordance with an embodiment of the present disclosure. GUI 300 can, in some embodiments, comprise a first portion 310 and a second portion 312. In some embodiments, first portion 310 can include one or more GUI elements 314 that provide a user with a preview of one or more portions of electronic document 210. For example, in some embodiments, electronic document 210 can be a slide presentation document, and first portion 310 can include one or more GUI elements 314 (e.g., thumbnails, etc.), each of which includes a preview of one or more slides in the slide presentation document. A user can access each portion of electronic document 210 via second portion 312 of GUI 300 by selecting (e.g., clicking, etc.) a particular GUI element 314. As illustrated in FIG. 3A , a particular GUI element 314 included in first portion 310 of GUI 300 is highlighted, indicating that the user has selected the particular GUI element 314.Thus, the user can access the portion of the electronic document 210 associated with the selected GUI element 314 via a second portion 312 of the GUI 300 (eg, illustrated in FIG. 3A as portion 316).

[0034] 3A, and other figures of the present disclosure, are directed to slide presentation documents, it should be noted that embodiments of the present disclosure may be directed to any type of electronic document, and therefore, any reference herein to a slide presentation document is not intended to be limiting and should be considered for illustrative purposes only.

[0035] In some embodiments, first portion 310 may include one or more GUI elements 318. One or more GUI elements 318 may allow a user to modify various portions (e.g., slides) included in electronic document 210. For example, first portion 310 of GUI 300 may include a GUI element 318 that allows a user to add slides to slide presentation document 210, as illustrated in FIG. 3A. In another example, first portion 310 may include an additional GUI element 318 that allows a user to remove slides from slide presentation document 210. First portion 310 may also include one or more additional GUI elements 320 that allow a user to view previews for each portion of slide presentation document 210. For example, as illustrated in FIG. 3A, first portion 310 may include a scroll bar GUI element 320 that allows a user to view previews for each portion of slide presentation document 210 by scrolling GUI element 314. Note that other types of GUI elements may be included in first portion 310 in addition to or instead of GUI elements 318 and / or 320. Additionally, GUI elements 318 and / or 320 may be included in different portions of GUI 300 (eg, in second portion 312, etc.).

[0036] The GUI 300 may include one or more GUI elements 322 that enable a user to initiate one or more operations (movements, traversals) associated with the electronic document 210. For example, the GUI 300 may include a file GUI element 322A that enables a user to initiate one or more file-based operations (e.g., opening a file associated with the electronic document 210, saving updates made to the electronic document 210 to a file associated with the electronic document 210, etc.). The GUI 300 may also include an edit GUI element 322B that enables a user to initiate one or more editing operations (e.g., spelling and / or grammar check operations, etc.) associated with the electronic document 210, a view GUI element 322C that enables a user to initiate one or more view-based operations associated with the electronic document 210, and other types of GUI elements 322X. In some embodiments, the GUI 300 may include an insert GUI element 322D that enables a user to insert one or more objects into a region of the portion 316 of the electronic document 210. In some embodiments, the insert GUI element 322D enables a user to select (e.g., click, etc.) a particular type of object for insertion (e.g., via a drop-down menu, etc.). For example, in response to detecting that a user has selected insert GUI element 322D of GUI 300, document management component 132 and / or document editing component 134 may update GUI 300 to include one or more GUI elements 324. Each of one or more GUI elements 324 allows the user to insert a particular type of object into an area of ​​portion 316 of electronic document 210.As illustrated in FIG. 3A, GUI 300 may include a text box GUI element 324A that allows a user to insert a text box object into an area of ​​portion 316, an image GUI element 324B that allows a user to insert an image object into an area of ​​portion 316, and a video feed object GUI element 324C that allows a user to insert a video feed object into an area of ​​portion 316.

[0037] As described above, text box GUI element 324A allows a user to insert a text box object into an area of ​​portion 316. For example, in response to a user engaging (e.g., selecting, clicking, etc.) text box GUI element 324A, document editing component 134 can update second portion 312 of GUI 300 to include text box 326. Text box 326 can be an overlaid (e.g., displayed on top of) portion 316 of electronic document 210 included in second portion 312 of GUI 300. In some embodiments, a user can provide and / or edit the text included in text box 326 by providing text data indicating the text to be included in text box 326, for example, via a peripheral device (e.g., a keyboard device, etc.) of client device 102B or a peripheral device connected to client device 102B, as the user engages with text box 326. Client device 102B can receive the text data provided by the user. The document editing component 134 can update the GUI 300 to include text contained in the provided text data in a text box 326. In one example, a user can provide text data associated with the text "Hello!" via a peripheral device. In response to receiving text data from the client device 102B, the document editing component 134 can update the text box 326 to include the text "Hello!" as illustrated in FIG. 3A . In another example, a user can provide text data associated with the text "My name is..." and / or "I work at..." via a peripheral device. The document editing component 134 can update another text box 328 to include the text "My name is..." and / or "I work at..." as illustrated in FIG. 3A .In some embodiments, GUI 300 may include one or more additional GUI elements (not shown) that allow a user to modify the format and / or style associated with text boxes 326 and / or 328. Document editing component 134 may update GUI 300 based on modifications to the format and / or style associated with text boxes 326 and / or 328 as provided by the user (e.g., via a mouse device, trackpad, etc. connected to client device 102B).

[0038] In some embodiments, document editing component 134 may also update the preview provided by each GUI element 314 in response to updating portion 316 based on text and / or style and formatting provided by a user. For example, document editing component 134 may update the preview of portion 316 included in each GUI element 314 included in first portion 310 of GUI 300 in response to updating portion 316 to include text provided by a user associated with client device 102A.

[0039] As described above, the video feed object GUI element 324C allows a user to insert a video feed integration object into a region of the portion 316. FIG. 3B illustrates adding a video feed integration object 330 into a region of the portion 316 according to an implementation of the present disclosure. As described above, the video feed integration object 330 can indicate (point to, point to) a region of the portion 316 of the electronic document 210 that will include a video feed generated by a client device because the portion 316 was shared via the conferencing platform GUI during a conference call discussion (e.g., facilitated by the conferencing platform 120). Further details related to including a video feed in a region indicated by the video feed integration object 330 are provided herein. In one example, in response to a user engaging (e.g., selecting, clicking, etc.) with the video feed object GUI element 324C, the document editing component 134 can update the second portion 312 of the GUI 300 to include the video feed integration object 330. The video feed integration object may be an overlaid (e.g., displayed on top of) portion 316 of electronic document 210 included in second portion 312 of GUI 300. In some embodiments, a user associated with client device 102A can modify the size and / or shape of video feed integration object 330 by using a peripheral device (e.g., a mouse, a trackpad, etc.). For example, the user can select one or more corners of video feed integration object 330 and then drag the selected corners (e.g., using a peripheral device) to correspond to a target size and / or shape.

[0040] In some embodiments, second portion 312 of GUI 300 may include a GUI element 332 that allows a user to indicate a particular user of conferencing platform 120 that will be displayed in the video feed included in the area indicated by video feed integration object 330 and / or client device 102 that generates the video feed that will be included in the area indicated by video feed integration object 330. For example, in response to engaging with (e.g., selecting, clicking, etc.) GUI element 332, document editing component 134 may update portion 312 of GUI 300 to include an additional GUI element 334. Additional GUI element 334 may allow a user to provide (e.g., type, select, etc.) an identifier associated with a particular user of conferencing platform 120 and / or a particular client device 102 connected to conferencing platform 120. In response to providing an identifier associated with a particular user of conferencing platform 120, document editing component 134 may generate metadata associated with portion 316 of electronic document 210. The generated metadata may comprise a mapping (e.g., association) between a region of portion 316 indicated by video feed integration object 330 and an identifier associated with a particular user and / or a particular client device. The mapping may indicate (e.g., to one or more components of video feed integration engine 124, as described herein) that a region of portion 316 contains a video feed associated with a particular participant and / or generated by a particular client device when portion 316 is shared via the conference platform GUI during a conference call discussion.In one illustrative example, a user provides an identifier associated with “Participant A” via GUI element 334, which can indicate that a video feed associated with “Participant A” will be included in the region of slide 316 indicated by video feed integration object 330 when slide 316 is shared via the conference platform GUI. As illustrated in FIG. 3C , a user can add another slide to electronic document 210 according to the previously described embodiment and can add video feed integration object 338 to slide 336 of electronic document 210 as previously described. A user also provides an identifier associated with “Participant B” via GUI element 334, which can indicate that a video feed associated with “Participant B” will be included in the region of slide 336 when slide 336 is shared via the conference platform GUI.

[0041] As described above, in response to updating portion 312 of GUI 300, document editing component 134 can update previews associated with portions 316, 336 of electronic document 210 that are included in GUI element 314 of portion 310. For example, in response to adding slide 336 to electronic document 210 and adding text boxes 340 and 342 and video feed integration object 338 to slide 336, document editing component 134 can update GUI element 314 associated with slide 336 to include previews of the added text boxes 340 and 342 and / or video feed integration object 338.

[0042] As mentioned above, some embodiments of the present disclosure refer to a GUI or GUI elements provided via a GUI of a client device 102. It should be noted that such a GUI or GUI element may refer to any type of GUI or GUI element, including, but not limited to, buttons, drop-down menus, scroll bars, and text boxes.

[0043] Referring again to FIG. 2 , a user associated with client device 102A can create and / or modify electronic document 210 according to the embodiments described above. In some embodiments, document management component 132 and / or document editing component 134 can generate and / or update metadata 212 associated with document 210 based on the user's creation and / or modification of electronic document 210. For example, as described above, a user can provide an identifier associated with “Participant A” via element 332 and indicate that a video feed associated with “Participant A” is included in the region of slide 316 indicated by video feed integration object 330 when slide 316 is shared via the conference platform GUI. Document management component 132 and / or document editing component 134 can generate a mapping between the identifier associated with “Participant A” and the coordinates for the region of slide 316 indicated by video feed integration object 330. The generated mapping can be included in metadata 212. In another example, the user can also provide an identifier associated with “Participant B” via GUI element 332 and indicate that a video feed associated with “Participant B” is included in the region of slide 336 when slide 336 is shared via the conference platform GUI. Document management component 132 and / or document editing component 134 can generate a mapping between the identifier associated with “Participant B” and the coordinates for the region of slide 336 indicated by video feed integration object 338. The generated mapping can be included in metadata 212. In some embodiments, document management component 132 can store document 210 and / or metadata 212 in data store 110, as described above.

[0044] As described above, the conference platform 120 can provide users of client devices 102 with tools for joining and participating in video and / or audio conference calls. The conference management component 122 can manage conference calls between users of client devices 102. In some embodiments, each client device 102B associated with a user of the conference platform 120 can connect via the network 104 to other client devices 102 associated with other users of the conference platform 120. The audiovisual components (e.g., camera components, microphones, etc.) of each client device 102B can generate visual and / or audio data associated with the user during the conference call discussion, as described above. The generated visual and / or audio data is referred to herein as video feed data 214. The client device 102B can transmit the video feed data 214 to the conference platform 120 (e.g., via the network 104). The conference management component 122 can transmit the video feed data 214 received from the client device 102B to client devices 102 associated with other users of the conference platform 120. Each client device 102B can provide video feed data to other users of the conferencing platform 120 via the conferencing platform GUI.

[0045] FIG. 4A illustrates an example conference platform GUI 400 according to an implementation of the present disclosure. In some embodiments, the conference platform GUI may include a first portion 410 and a second portion 412. The first portion 410 may include a first section 414 and a second section 416 configured to display image data (e.g., video feeds) captured by the client devices 102 associated with participants in the conference call. For example, as illustrated in FIG. 4A , a video feed associated with a first participant (e.g., participant A) may be included in the first section 414 of the first portion 410. Video feeds associated with additional participants (e.g., participant B, participant N, etc.) may be included in the second section 416 of the first portion 410. In some embodiments, the first section 414 may be designed to include a video feed associated with the participant currently speaking. In other or similar embodiments, the first section 414 may be designed to include a video feed associated with a participant identified or designated as the presenter of the conference call discussion. In additional or alternative embodiments, the first partition 414 may comprise a single portion that displays video feeds captured by the client devices of participants who are currently speaking and / or identified as presenters, while not displaying video feeds captured by the client devices 102 of other participants who are not currently speaking and / or not identified as presenters. In another example, the first partition 414 may comprise multiple partitions that display video data associated with participants in the video conference call, regardless of whether the participants are currently speaking.

[0046] In some embodiments, the first portion 410 of the GUI 400 can also include one or more GUI elements that enable a presenter of a conference call to share one or more portions of an electronic document with the participants of the conference call. For example, the first portion 410 can include a button 418 that enables the presenter to share slides of a slide presentation document (e.g., the slide presentation document 210 described above) displayed in the second portion 412 with the participants of the conference call. The presenter can initiate an operation to share one or more portions of the document 210 with the participants by engaging (e.g., clicking) the button 418. In response to detecting the presenter's engagement with the button 418, a client device associated with the presenter (e.g., client device 102B) can detect that an operation to share at least a portion of the document 210 has been initiated. The client device 102B can send a request to the conference management component 122 of the conference platform 120 to initiate the document sharing operation. Note that the presenter can initiate an operation to share the document 210 with the participants through other techniques. For example, in response to detecting that document 210 has been retrieved from local memory of client device 102B and displayed in second portion 412 of GUI 400, settings on client device 102B may initiate an operation to share a portion of document 210.

[0047] 2 , the conference management component 122 can share one or more portions of the electronic document 210 with participants in a conference call according to embodiments of the present disclosure. In some embodiments, the electronic document platform 130 can send a file associated with the electronic document 210 to the conference management component 122. The conference management component 122 can share one or more portions of the electronic document 210 in response to receiving the file from the electronic document platform 130. In other or similar embodiments, the conference management component 122 can retrieve the file associated with the electronic document 210 from the data store 110 and share one or more portions of the electronic document 210 based on the retrieved file.

[0048] The video feed integration engine 124 can be configured to integrate portions of the electronic document 210 with video feeds associated with participants (e.g., presenters) in the conference call discussion. The portions of the electronic document 210 are then shared via a conference platform GUI. In some embodiments, the video feed integration engine 124 can include a document domain identifier component 220 (also referred to herein as document domain identifier 220) and / or an integration component 222. FIG. 4B illustrates an example conference platform GUI 420 according to implementations of the present disclosure. In some embodiments, the GUI 420 can include at least a first portion 422. The first portion 422 can be configured to display the portions of the electronic document 210 that have been shared with the conference call participants. In an example embodiment, the electronic document 210 shared via the GUI 420 can correspond to the slide presentation document described with respect to FIGS. 3A-3B. As illustrated in FIG. 4B, the first portion 422 of the GUI 420 can display a portion 316 (e.g., slide 316) of the slide presentation document 210. In some embodiments, the GUI 420 optionally includes a second portion 424 configured to provide video data (e.g., video feeds) captured by client devices 102 associated with participants in the conference call. As illustrated in FIG. 4B, the second portion 424 can include video feeds associated with participant B and participant N, etc.

[0049] As described above, the first portion 422 of the GUI 420 can display the portion 316 of the slide presentation document 210. The document domain identifier component 220 can determine whether the portion 316 includes one or more video feed integration objects. In some embodiments, the document domain identifier component 220 can determine whether the portion 316 includes a video feed integration object in response to the conference management component 122 receiving a request to share the portion 316 via the GUI 420. In other or similar embodiments, the document domain identifier component 220 can determine whether the portion 316 includes a video feed integration object in response to detecting that the conference management component 122 has initiated a share operation to share the portion 316 via the GUI 420.

[0050] The document region identifier 220 can determine whether the portion 316 comprises a video feed integration object by identifying each object associated with the portion 316 and determining whether each object is associated with a video feed integration object type. For example, the document region identifier 220 can identify objects 326, 328, and / or 330 associated with the portion 316. The document region identifier 220 can determine (e.g., based on metadata associated with the document 210) that objects 326 and 328 are text box objects and therefore are not associated with a video feed integration object type. The document region identifier 220 can determine that object 330 is a video feed integration object and therefore is associated with a video feed integration object type. Thus, the document region identifier 220 can determine that a video feed will be integrated into the region of the portion 316 indicated by the video feed integration object 330.

[0051] The document region identifier 220 can provide an integration component 222 of the video feed integration engine 124 with an indication of the region of the portion 316 that includes the video feed integration object 330. In some embodiments, the integration component 222 can determine whether the video feed integration object 330 is associated with a particular participant in the conference call and / or a particular client device 102 connected to the conference platform 120. For example, the integration component 222 can identify a mapping associated with the video feed integration object 330 by parsing the metadata 212 associated with the document 210. Based on the identified mapping, the integration component 222 can determine that the video feed integration object 330 is associated with participant A. The integration component 222 can determine the client device (e.g., client device 102B) associated with participant A. In some embodiments, the mapping included in the metadata 212 can include an identifier for the client device associated with participant A. Thus, the integration component 222 can determine that client device 102B is associated with participant A based on the mapping. In other or similar embodiments, the integration component 222 may determine that the client device 102B is associated with participant A based on a user profile associated with participant A (e.g., maintained by the conference platform 120).

[0052] In response to determining that client device 102B is associated with participant A, integration component 222 can obtain video feed data 214 associated with participant A according to the previously described embodiments. The video feed data 214 can include a video feed representing participant A in the conference call, generated by an audiovisual component of client device 102B, as described above. Integration component 222 can cause other participants in the conference call to provide video feeds within the area of ​​portion 316 indicated by video feed integration object 330. As illustrated in FIG. 4B , a first section 426 of first portion 422 of GUI 420 can include text associated with text box objects 326 and 328, as described with respect to FIG. 3B . A second section 428 of first portion 422 of GUI 420 can be associated with video feed integration object 330. Thus, integration component 222 can integrate a video feed associated with participant A within second section 428 of first portion 422 of GUI 420.

[0053] In some embodiments, the conference management component 122 can receive a request to share a different portion of the electronic document 210 via the conference platform GUI 420. For example, the conference management component 122 can receive a request to present a portion 336 (e.g., slide 336) of the slide presentation document 210 via the GUI 420 (e.g., in response to a presenter's transition from slide 316 to slide 336). In response to receiving the request, the document region identifier component 220 can determine that a video feed integration object 338 is included in portion 336, as described above, and can therefore provide an indication to the integration component 222 of the region of portion 336 that includes the video feed integration object 338. The integration component 222 can determine, based on the metadata 212 associated with the electronic document 210, that the video feed integration object 338 is associated with participant B of the conference call. The integration component 222 can obtain the video feed associated with participant B, as described above, and can therefore include the obtained video feed in the region of the first portion 422 of the GUI 420 indicated by the video feed integration object 338. 4C , the conference management component 122 can cause a portion 336 of the electronic document 210 to be presented via a first portion 422 of the GUI 420. A first section 430 of the first portion 422 can include text provided via text box objects 340 and 343, as described with respect to FIG. 3C . A second section 432 of the first portion 422 can be associated with a video feed integration object 338. Thus, the integration component 222 can integrate a video feed associated with participant B within the second section 432 of the first portion 422 of the GUI 420.

[0054] In some embodiments, the conference management component 122 can update the second portion 424 of the GUI 420 to include video feeds of participants in the conference call who are not the current presenter of the portion 336 of the electronic document 210. For example, the conference management component 122 can update the second portion 424 to include a video feed associated with participant A (e.g., so that participant A is not the presenter for the portion 336 of the electronic document 210).

[0055] As described above, in some embodiments, a user of electronic document platform 130 may not specify a particular user of conference platform 120 and / or a particular client device connected to conference platform 120 for each video feed integration object. Instead, a user of electronic document platform 130 may specify one or more video integration criteria for each video feed integration object. The integration component 222 of video feed integration engine 124 may integrate video feeds associated with particular participants and / or generated by particular client devices 102 in response to determining that the video integration criteria are met. FIG. 5 illustrates another example content viewer GUI 500 according to an embodiment of the present disclosure. GUI 500 may include one or more GUI elements corresponding to GUI elements of GUI 300, as described with respect to FIGS. 3A-3C . For example, GUI 500 may include a first portion 510 and a second portion 512 that may correspond to first portion 310 and second portion 312 of GUI 300. First portion 510 can include GUI element 314, which corresponds to GUI element 314 of GUI 300. First portion 510 can also include GUI elements 518 and / or 520, which can correspond to GUI elements 318 and / or 320 of GUI 300. Second portion 512 can include portion 516 of an electronic document (e.g., electronic document 210 or another electronic document), as described above. GUI 500 can also include one or more GUI elements 522, which can correspond to GUI element 322 of GUI 300. In some embodiments, GUI 500 can further include one or more GUI elements (not shown) that correspond to GUI element 324 of GUI 300.

[0056] In some embodiments, a user of electronic document platform 130 can insert one or more objects into an area of ​​portion 516 of an electronic document, as described above. For example, a user can insert one or more text box objects (e.g., text box object 526), ​​one or more image objects (not shown), and / or one or more video feed integration objects (e.g., objects 528, 530, and / or 532). A user can provide text (e.g., a "question and answer session") that is contained in one or more text boxes, as described above. As described with respect to FIGS. 3A-3C, a user can insert one or more video feed integration objects 528, 530, 532 and can modify the size and / or shape of the video feed integration objects 528, 530, 532. In some embodiments, each video feed integration object 528, 530, 532 may include a GUI element 534 that enables a user to indicate a particular user of conferencing platform 120 that appears in the video feed included in the area indicated by the video feed integration object 528, 530, 532 and / or a client device 102 that generated the video feed included in the area indicated by the video feed integration object 528, 530, 532. For example, as illustrated in FIG. 5 , in response to detecting that a user has engaged with GUI element 534 associated with video feed integration object 528, document editing component 134 may include an additional GUI element 536 that enables a user to provide an identifier associated with a particular user of conferencing platform 120 and / or a particular client device 102 connected to conferencing platform 120 by updating second portion 512 of GUI 500.The document editing component 134, according to the previously described embodiments, can generate metadata indicating the mapping between the video feed integration object 528 and the provided identifier.

[0057] In additional or alternative embodiments, element 524 may enable a user to indicate one or more video feed integration criteria that a client device 102 must satisfy in order for a video feed generated by the client device 102 to be included in the area of ​​portion 516 indicated by the video feed integration object. For example, as illustrated in FIG. 5 , a user may engage GUI element 534 associated with video feed integration objects 530 and / or 532. In response to detecting user engagement with GUI element 534, document editing component 134 may include an additional GUI element 536 that enables the user to update second portion 512 of GUI 500 to provide an indication of the criteria that must be satisfied for the video feed to be included in the area indicated by video feed integration object 530 and / or 532. In one example, the criteria may enable a video feed associated with a client device to be included in the area indicated by video feed integration object 530 and / or 532 if a microphone component associated with the client device is active (e.g., unmuted). In another example, the criteria may allow a video feed to be included if a camera component associated with the client device is active (e.g., unmuted). Note that other types of criteria may also be provided. The document editing component 134, according to the previously described embodiments, may generate metadata indicating a mapping between the video feed integration objects 530 and / or 532 and the provided video feed integration criteria.

[0058] As illustrated in FIG. 6A , portion 516 can be shared via a conference platform GUI 600 during the conference call, as described above. In some embodiments, GUI 600 can correspond to GUI 420 described with respect to FIGS. 4B-4C . For example, GUI 600 can include first and second portions 610 and 612 corresponding to first and second portions 422 and 424 of GUI 420. The document region identifier 220 of the video feed integration engine 124 can determine whether portion 516 of electronic document 210 includes any video feed integration objects, as described above, and thus provide an indication of the regions that include the video feed integration objects to the integration component 222. The integration component 222 can determine whether any particular participants and / or client devices are associated with each video feed integration object, as described above. For example, the integration component 222 can determine that video feed integration object 528 is associated with participant A based on metadata 212 associated with electronic document 210. Integration component 222 may also determine, based on metadata 212, that video feed integration objects 530 and / or 532 are associated with video feed integration criteria. Per the example provided with respect to FIG. 5 , the video feed integration criteria may enable video feeds generated by particular client devices 102 connected to conferencing platform 120 to be included in the area of ​​portion 516 indicated by video feed integration objects 530 and / or 532 when the microphones of client devices 102 are unmuted. When portion 516 is shared via GUI 600, the microphones of client devices 102 associated with participant B and participant N may be muted.Thus, the integration component 222 may determine that none of the client devices 102 connected to the conferencing platform 120 meet the criteria, and therefore none of the video feed(s) are included in the area of ​​the portion 516 indicated by the video feed integration object 530 and / or 532. As illustrated in FIG. 6A , the text provided via the text box object 526 (e.g., “Question and Answer Session”) is included in the first area 614 of the first portion 610 of the GUI 600. The video feed associated with participant A is included in the second area 616 of the first portion 610 of the GUI 600 (i.e., the area indicated by the video feed integration object 528). None of the video feeds are included in the third area 618 and / or the fourth area 620 of the first portion 610 of the GUI 600.

[0059] In response to detecting that the video feed integration criteria associated with the video feed integration objects 530 and / or 532 are satisfied, the integration component 222 can update the GUI 600 to include the video feeds of one or more participants in the third area 618 and / or the fourth area 620. For example, a microphone associated with the client device(s) 102 associated with participant B and / or participant N may be activated (e.g., unmuted). Thus, the integration component 222 can determine that the client device(s) 102 satisfy the video feed integration criteria, thereby including the video feeds generated by each client device(s) in the third area 618 and / or the fourth area 620. As illustrated in FIG. 6B , after the integration component 222 detects that the microphone associated with participant B's client device 102 has been activated (e.g., unmuted), the video feed associated with participant B can be included in the third area 618. Additionally or alternatively, after the integration component 222 detects that a microphone associated with participant N's client device 102 has been activated (e.g., unmuted), the video feed associated with participant N may be included in the fourth area 620. As illustrated in FIG. 6B , the conference management component 122 may remove the video feeds associated with participant B and / or participant N by updating the second portion 612 of the GUI 600 (e.g., in response to the integration component 222 including the video feeds in areas 618 and / or 620 of the first portion 610).

[0060] As previously described, in some embodiments, a content viewer GUI (e.g., GUI 300, GUI 500, etc.) may enable a user of electronic document platform 130 to insert image objects into portions of electronic document 210. FIG. 7A illustrates another example content viewer GUI 700 according to an implementation of the present disclosure. One or more portions and / or GUI elements of GUI 700 may correspond to respective portions and / or elements of GUIs 300 and / or 500, as described above. As illustrated in FIG. 7A , a user of electronic document platform 130 may insert one or more text box objects 726, 728 into portion 716 (e.g., a slide) of electronic document 210, as described above. The user may provide text (e.g., "Greetings!" and "I'm... I work on... the... team") to be included in the inserted one or more text box objects 726, 728, as described above. In some embodiments, a user can insert an image object into one or more areas 730 of portion 716. For example, the user can engage with insert GUI element 322D, as described above. In response to detecting that the user has engaged with insert GUI element 322D, document management component 132 and / or document editing component 134 can update GUI 700 to include one or more additional GUI elements 324. The additional GUI element 324 can include image object GUI element 324B, as described above. In response to detecting that the user has engaged with image object GUI element 324B, document management component 132 and / or document editing component 134 can update GUI 700 to include another GUI element (not shown) that allows the user to insert a particular image into area 730 of portion 716.In some embodiments, the GUI element allows a user to select an image stored in local memory of the client device 102 associated with the user. In other or similar embodiments, the GUI element allows a user to search (e.g., via a web browser, etc.) for an image that has been downloaded or copied to the client device 102 and will be included in region 730 of portion 716. The user can provide an indication of the image to be included in region 730, and the document management component 132 and / or document editing component 134 can update the GUI 700 to include the image shown in region 730. As illustrated in FIG. 7A , the document management component 132 and / or document editing component 134 can update the GUI 700 to include an image of a person in region 730 of portion 716 of the electronic document 210.

[0061] In some embodiments, a user can add additional objects to be overlaid on top of the objects included in portion 716 of electronic document 210. For example, after inserting an image in region 730 of portion 716, the user can insert a video feed integration object 732 into portion 716, as described herein. In some embodiments, the user can insert the video feed integration object 732 over the top of the image already inserted in region 730. As illustrated in FIG. 7B , the user can insert the video feed integration object 732 over the top of the image included in region 730. The user can also indicate particular users of the conferencing platform and / or particular client devices 102 connected to conferencing platform 120 that will provide video feeds to be integrated within region 730, as described above. When portion 716 is shared with participants in a conference call discussion via conferencing platform 120, the video feed integration engine 124 can include video feeds associated with particular participants and / or generated by particular client devices 102 within the region indicated by the video feed integration object 732, according to previously described embodiments. In such an embodiment, the image included in region 730 may not be displayed via the conferencing platform GUI. As described above, in some embodiments, a user of electronic document platform 130 may provide an indication of one or more video feed integration criteria associated with video feed integration object 732. If client device 102 meets one or more video feed integration criteria, a video feed generated by client device 102 may be included in the region of portion 716 indicated by video feed integration object 732, as described above.However, if the client device(s) 102 connected to the video conferencing platform 120 do not meet one or more video feed integration criteria, the image contained in area 730 can be presented within a corresponding area of ​​the shared portion 716 via the conferencing platform GUI.

[0062] Referring again to FIG. 2 , in some embodiments, a user of electronic document platform 130 may desire to convert a file associated with electronic document 210 from a first file format to a second file format. For example, electronic document 210 can be created as a slide presentation document, as described above. A user of platform 130 may desire to convert a file associated with the slide presentation document to another type of document (e.g., a Word document, a Portable Document Format (PDF) document, etc.). A client device associated with the user (e.g., client device 102A) can send a request to electronic document platform 130 to convert a file associated with electronic document 210 from the first file type to the second file type. File conversion component 224 of electronic document platform 130 can convert the file associated with electronic document 210 in response to the request. As described with respect to FIGS. 7A and 7B , in some embodiments, one or more portions of an electronic document can comprise an image and a video feed integration object overlaid on top of the image. When the file conversion component 224 converts the electronic document from the first file type to the second file type, the file conversion component 224 can remove (or otherwise omit) the video feed integration object from the top of the included image. FIG. 8 shows an example 800 of a portion of the electronic document 210 after conversion from the first file type to the second file type. The portion of the electronic document 210 can correspond to the portion 716 described with respect to FIGS. 7A and 7B. As illustrated in FIG. 8, the portion 716 of the electronic document 210 can include a first region 812 and a second region 614. The first region 612 of the portion 716 can include text provided via one or more text box objects inserted in the portion 716 (e.g., "Greetings!" and "I'm...").The second region 614 of the portion 716 may include an image inserted into the region 730 of the portion 716 via the content viewer GUI 700, as described with respect to Figures 7A and 7B. As illustrated in Figure 8, the video feed integration object 732 is not included in the embodiment 800 of the portion 716.

[0063] 9 illustrates a flow diagram of an exemplary method 900 for integrating a shared document with a video feed during a conference call discussion, according to an implementation of the present disclosure. The method 900 may be performed by processing logic, which may comprise hardware (circuitry, dedicated logic, etc.), software (e.g., instructions running on a processing device), or a combination thereof. In one implementation, some or all of the operations of the method 900 may be performed by one or more components of the system 100 of FIG. 1.

[0064] At block 910, processing logic may provide a graphical user interface (GUI). The GUI may enable presentation of an electronic document to participants in the video conference call. In some embodiments, the GUI may be a conference platform GUI provided by conference platform 120. At block 912, processing logic may identify an electronic document for presentation to participants in the video conference call. The electronic document may comprise a slide presentation document, a word processing document, a spreadsheet document, and / or a web page document. A first portion of the electronic document may comprise a first video feed integration object, and a second portion of the electronic document may comprise a second video feed integration object. The first video feed integration object may indicate a first region of the first portion of the electronic document as comprising a first video feed generated by a first client device of a first participant in the video conference call. The second video feed integration object may indicate a second region of the second portion of the electronic document as comprising a second video feed generated by a second client device of a second participant in the conference call.

[0065] At block 914, the processing logic may provide at least one of the first portion or the second portion of the electronic document via a GUI for presentation to one or more participants in the video conference call. A first video feed generated by a first client device will be included in a first region indicated by a first video feed integration object. A second video feed generated by a second client device will be included in a second region indicated by a second video feed integration object.

[0066] FIG. 10 is a block diagram illustrating an exemplary computer system 1000 according to an implementation aspect of the present disclosure. The computer system 1000 may correspond to the conferencing platform 120, the collaborative document platform 130, and / or the client devices 102A-102N, as illustrated in FIG. 1. The computer system 1000 may operate in the capacity of a server or endpoint machine in an endpoint-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a television, a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a web appliance, a server, a network router, a switch, or a bridge, or any machine capable of executing a set of instructions (series or otherwise) that define actions to be taken by the machine. Furthermore, while only a single machine is illustrated, the term “machine” is intended to include any collection of machines that individually or collectively execute a set (or sets) of instructions to perform any one or more of the methodologies discussed herein.

[0067] The exemplary computer system 1000 of the embodiment includes a processing device (processor) 1002, a main memory 1004 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM), double data rate (DDR SDRAM), or DRAM (RDRAM®)), a static memory 1006 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 1018, which communicate with each other via a bus 1040.

[0068] Processor (processing device) 1002 represents one or more general-purpose processing devices, such as a microprocessor or central processing unit. More specifically, processor 1002 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or combinations of instruction sets. Processor 1002 may also be one or more special-purpose processing devices, such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), or a network processor. Processor 1002 is configured to execute instructions 1005 for performing operations discussed herein (e.g., for predicting viewership for a channel lineup).

[0069] The computer system 1000 may further include a network interface device 1008. The computer system 1000 may also include a video display unit 1010 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), input devices 1012 (e.g., a keyboard and alphanumeric keyboard, a motion-sensing input device, a touch screen), a cursor control device 1014 (e.g., a mouse), and a signal generation device 1020 (e.g., a speaker).

[0070] The data storage device 1018 may comprise a non-transitory machine-readable storage medium 1024 (also a computer-readable storage medium) having stored thereon one or more sets of instructions 1005 embodying any one or more of the methods or functions described herein (e.g., for integrating a shared document with a video feed during a conference call discussion). The instructions may also reside, completely or partially, within the main memory 1004 and / or within the processor 1002 during execution thereof by the computer system 1000, the main memory 1004, and the processor 1002, which also constitute the machine-readable storage medium. The instructions may further be transmitted or received over a network 1030 via the network interface device 1008.

[0071] In one implementation, the instructions 1005 comprise instructions for overlaying an image representing the conference call participants with a shared document. While the computer-readable storage medium 1024 (machine-readable storage medium) is shown as a single medium in the exemplary implementation, the terms “computer-readable storage medium” and “machine-readable storage medium” should be interpreted to comprise a single medium or multiple media (e.g., centralized or distributed databases and / or associated caches and servers) that store one or more sets of instructions. The terms “computer-readable storage medium” and “machine-readable storage medium” should also be interpreted to comprise any medium capable of storing, encoding, or executing a set of instructions for execution by a machine, causing the machine to perform any one or more of the methods of the present disclosure. Thus, the terms “computer-readable storage medium” and “machine-readable storage medium” should be interpreted to include, but are not limited to, solid-state memory, optical media, and magnetic media.

[0072] References throughout this specification to "one implementation," "one embodiment," "an implementation," or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, the appearances of the phrases "in one implementation" or "in an implementation" in various places throughout this specification may, but do not necessarily, refer to the same embodiment, depending on the context. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0073] To the extent that the terms "includes," "including," "has," "contains," variations thereof, and other similar words are used in either the detailed description or the claims, these terms are intended to be as inclusive as the term "comprising" as an open transition word, without excluding additional or other elements.

[0074] As used in this application, terms such as "component," "module," or "system" can refer to a computer-related entity, either hardware (e.g., circuitry), software, a combination of hardware and software, or an entity related to an operable machine having one or more specific functionalities. For example, a component can be, but is not limited to, a process running on a processor (e.g., a digital signal processor), a processor, an object, an executable, a thread of execution, a program, and / or a computer. By way of example, both an application running on a controller and the controller can be a component. One or more components can reside within a process and / or thread of execution, and components can be localized on one computer and / or distributed among two or more computers. Furthermore, a "device" can be in the form of specially designed hardware, generalized hardware specialized by the execution of software thereon that causes the hardware to perform a specific function (e.g., generating points of interest and / or descriptions), software on a computer-readable medium, or a combination thereof.

[0075] The aforementioned systems, circuits, modules, etc. have been described with respect to interactions between multiple components and / or blocks. It will be understood that such systems, circuits, components, blocks, etc. may include those components or designated subcomponents, portions of the designated components or subcomponents, and / or additional components, according to various permutations and combinations of the foregoing. Subcomponents may also be implemented as components coupled to other components rather than being contained within a parent component (hierarchical). In addition, it should be noted that one or more components may be combined into a single component providing integrated functionality or may be divided into several separate subcomponents, and that any one or more intermediate layers, such as a management layer, may be provided to communicatively couple such subcomponents to provide integrated functionality. Any component described herein may also interact with one or more other components not specifically described herein but known to those skilled in the art.

[0076] Moreover, the word "embodiment" or "exemplary" is used herein to mean serving as an example, example, or illustration. Any aspect or design described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects or designs. Rather, use of the word "embodiment" or "exemplary" is intended to present concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise specified or clear from the context, "X uses A or B" is intended to mean natural inclusive permutations. That is, if X uses A, if X uses B, or if X uses both A and B, then "X uses A or B" is satisfied in each of the foregoing cases. Additionally, the articles "a" and "an," as used in this application and the appended claims, should generally be construed to mean "one or more" unless otherwise specified or clear from the context to refer to the singular form.

[0077] Finally, embodiments described herein include the collection of data describing users and / or user activities. In one embodiment, such data is collected only if the user consents to the collection of this data. In some embodiments, the user is asked to explicitly authorize the data collection. Furthermore, the user may opt in or out of participating in such data collection activities. In one embodiment, the collected data is anonymized before performing any analysis to obtain any statistical patterns, so that the identity of the user cannot be determined from the collected data.

Claims

1. 1. A method, comprising: providing an electronic document for editing by at least one user of the platform via a graphical user interface (GUI); receiving user input during an edit mode selecting an option to insert a video feed integration object into the electronic document, the video feed integration object indicating an area of ​​the electronic document that is to contain a video feed of at least one of the user or of an additional user of the platform when a presentation mode for the electronic document is initiated; inserting the video feed integration object into the region of the electronic document in response to the user input; and obtaining one or more video feeds of at least one of the users or the additional users during the presentation mode and including the one or more video feeds of at least one of the users or the additional users in the region of the electronic document comprising the video feed integration object; The method comprises:

2. The method further comprises: receiving additional user input associated with modifying one or more of the size or shape of the video feed integration object in the region of the electronic document from a first size to a second size or from a first shape to a second shape; and updating one or more of the size or the shape of the video feed integration object according to the additional user input from the first size to the second size or from the first shape to the second shape; Equipped with The method of claim 1.

3. The method further comprises receiving additional user input indicating a particular user of the platform associated with the video feed integration object; the video feed for the particular user is obtained for inclusion in the region of the electronic document based on the additional user input; The method of claim 1.

4. The method further comprises: receiving additional user input selecting an option to insert an additional video feed integration object into the electronic document, the additional video feed integration object indicating an additional area of ​​the electronic document, the additional area being for including one or more of the video feeds of one or more of the at least one user or the additional users, or for including additional video feeds of at least one user or the additional users, when the presentation mode is initiated; and acquiring the video feed or one or more of the additional video feeds during the presentation mode and including the video feed or one or more of the additional video feeds in the additional region of the electronic document comprising the additional video feed integration object; Equipped with The method of claim 1.

5. the additional user input further indicates the additional user associated with the additional video feed integration object; the additional video feeds of the additional users are obtained for inclusion in the additional regions of the electronic document based on the additional user input; The method of claim 4.

6. The method further comprises: receiving additional user input for inserting a default image into the region of the electronic document comprising the video feed integration object; determining whether a client device associated with at least one of the users or the additional users satisfies one or more video feed integration criteria; and providing the default image for presentation in place of the video feed during the presentation mode in response to determining that the client device does not meet one or more of the video feed integration criteria; Equipped with The method of claim 1.

7. Determining whether the client device satisfies one or more of the video feed integration criteria includes: determining whether at least one of a camera component or a microphone component of the client device is activated; The method of claim 6.

8. the electronic document comprises at least one of a slide presentation document, a word processing document, a spreadsheet document, or a web page document; The method of claim 1.

9. 1. A system comprising: memory, and a set of one or more processing devices connected to the memory; It is equipped with The set of one or more of the processing devices is adapted to perform an operation, the operation comprising: providing an electronic document for editing by at least one user of the platform via a graphical user interface (GUI); receiving user input during an edit mode to select an option to insert a video feed integration object into the electronic document, the video feed integration object indicating an area of ​​the electronic document that is to contain a video feed of at least one of the user or an additional user of the platform when a presentation mode for the electronic document is initiated; inserting the video feed integration object into the region of the electronic document in response to the user input; and obtaining one or more video feeds of at least one of the users or the additional users during the presentation mode and including the one or more video feeds of at least one of the users or the additional users in the region of the electronic document comprising the video feed integration object; A system comprising:

10. The operations further comprise: receiving additional user input associated with modifying one or more of the size or shape of the video feed integration object in the region of the electronic document from a first size to a second size or from a first shape to a second shape; and updating one or more of the size or the shape of the video feed integration object according to the additional user input from the first size to the second size or from the first shape to the second shape; Equipped with The system of claim 9.

11. The operations further include receiving additional user input indicating a particular user of the platform associated with the video feed integration object; the video feed for the particular user is obtained for inclusion in the region of the electronic document based on the additional user input; The system of claim 9.

12. The operations further comprise: receiving additional user input selecting an option to insert an additional video feed integration object into the electronic document, the additional video feed integration object indicating an additional area of ​​the electronic document, the additional area being for including one or more of the video feeds of one or more of the at least one user or the additional users, or for including additional video feeds of at least one user or the additional users, when the presentation mode is initiated; and acquiring the video feed or one or more of the additional video feeds during the presentation mode and including the video feed or one or more of the additional video feeds in the additional region of the electronic document comprising the additional video feed integration object; Equipped with The system of claim 9.

13. the additional user input further indicates the additional user associated with the additional video feed integration object; the additional video feeds of the additional users are obtained for inclusion in the additional regions of the electronic document based on the additional user input; The system of claim 12.

14. The operations further comprise: receiving additional user input for inserting a default image into the region of the electronic document comprising the video feed integration object; determining whether a client device associated with at least one of the users or the additional users satisfies one or more video feed integration criteria; and providing the default image for presentation in place of the video feed during the presentation mode in response to determining that the client device does not meet one or more of the video feed integration criteria; Equipped with The system of claim 9.

15. Determining whether the client device satisfies one or more of the video feed integration criteria includes: determining whether at least one of a camera component or a microphone component of the client device is activated; The system of claim 14.

16. 1. A non-transitory computer-readable storage medium comprising instructions that, when executed by a set of one or more processing devices, cause the set of one or more processing devices to perform an operation, the operation comprising: providing an electronic document for editing by at least one user of the platform via a graphical user interface (GUI); receiving user input during an edit mode selecting an option to insert a video feed integration object into the electronic document, the video feed integration object indicating an area of ​​the electronic document that is to contain a video feed of at least one of the user or of an additional user of the platform when a presentation mode for the electronic document is initiated; inserting the video feed integration object into the region of the electronic document in response to the user input; and obtaining one or more video feeds of at least one of the users or the additional users during the presentation mode and including the one or more video feeds of at least one of the users or the additional users in the region of the electronic document comprising the video feed integration object; Equipped with A non-transitory computer-readable storage medium.

17. The operations further comprise: receiving additional user input associated with modifying one or more of the size or shape of the video feed integration object in the region of the electronic document from a first size to a second size or from a first shape to a second shape; and updating one or more of the size or the shape of the video feed integration object according to the additional user input from the first size to the second size or from the first shape to the second shape; Equipped with 17. The non-transitory computer-readable storage medium of claim 16.

18. The operations further include receiving additional user input indicating a particular user of the platform associated with the video feed integration object; the video feed for the particular user is obtained for inclusion in the region of the electronic document based on the additional user input; 17. The non-transitory computer-readable storage medium of claim 16.

19. The operations further comprise: receiving additional user input selecting an option to insert an additional video feed integration object into the electronic document, the additional video feed integration object indicating an additional area of ​​the electronic document, the additional area to include one or more video feeds of one or more of the at least one user or additional users, or to include additional video feeds of at least one user or additional users, when the presentation mode is initiated; and acquiring the video feed or one or more of the additional video feeds during the presentation mode and including the video feed or one or more of the additional video feeds in the additional region of the electronic document comprising the additional video feed integration object; Equipped with 17. The non-transitory computer-readable storage medium of claim 16.

20. the additional user input further indicates the additional user associated with the additional video feed integration object; the additional video feeds of the additional users are obtained for inclusion in the additional regions of the electronic document based on the additional user input; 20. The non-transitory computer-readable storage medium of claim 19.

Citation Information

Patent Citations

  • Automatic Data Extraction and Conversion of Video / Images / Sound Information from a Slide presentation into an Editable Notetaking Resource with Optional Overlay of the Presenter

    US20210076105A1