Proactive suggestions for sharing meeting content

Abstract

The present disclosure relates to processing operations configured to manage (one or more) proactive suggestions that can be used to manage the sharing of meeting content. The present disclosure also describes optimizations to the user interface, thereby improving the user interface experience through new user interface features and actions that enable proactive presentation of suggestions for synchronizing content with a meeting and sharing the synchronized content. Various intelligent signals, such as the user's calendar, GPS location, camera roll content, captured content (including OCR, whiteboard detection, etc.), and capture time are collected and analyzed to make intelligent suggestions to the user to share content with a specific set of users (e.g., people attending a meeting). The processing described herein enables contextual correlation between specific content and a scheduled meeting, whereby the results of the contextual correlation can be used to perform programmed actions to improve the efficiency of computing devices and users.

Description

Background Art

[0001] Users continuously attend numerous meetings with different objectives. Since the user's brain is usually focused on the task at hand during the meeting, users often forget to capture content that may help in assisting with remembering the topics discussed in the meeting. If the user waits a long time before attempting to piece together all the discussed information, it usually results in key information being omitted and content being forgotten. Empirical studies have shown that if the user does not associate the content with the meeting within a specific time after the meeting occurs, the likelihood of the content being associated with the meeting is significantly reduced. When the user attempts to manually remember the content covered in the meeting, this not only leads to low processing efficiency for the user but also for the computing device used to locate the specific content. For example, the user may be performing many applications / services, a large amount of content, and associated actions to locate the content as the specific content the user wishes to remember. This is not only inefficient for the user during runtime but also causes device latency and consumes computing resources that could be allocated to other tasks.

[0002] In addition, conventionally, the user interfaces of applications / services are not configured to keep the user in the task of associating content with the meeting. If the user forgets to take a picture of the whiteboard in the room where the meeting is being held, the whiteboard may be erased and the content lost forever. Additionally, the conventional user interfaces of applications / services typically require the user to tediously perform multiple actions to locate content, create a message for sharing content with other users, identify the recipients of the shared content, etc. From a processing perspective, this is not only inefficient but also frustrating for the user, for example, when the user forgets to add content to a previous meeting instance. Summary of the Invention

[0003] In view of the foregoing technical challenges, the present disclosure relates to processing operations configured to manage one or more proactive suggestions that can be used to manage the sharing of meeting content. The present disclosure also describes an optimization of the user interface, thereby improving the user interface experience relative to a conventional user interface experience through new user interface features and actions that enable proactive presentation of suggestions for synchronizing content with a meeting and sharing the synchronized content. For example, various intelligent signals are captured and analyzed, such as a user's calendar, GPS location, camera roll content, captured content (including OCR, whiteboard detection, etc.), and capture time, to present intelligent suggestions to the user for sharing content with a specific set of users (e.g., those attending a meeting). Signal data can be collected for ad-hoc electronically scheduled meetings or non-routine meetings. In any example, the processing described herein enables context correlation between specific content and a scheduled meeting, whereby the context-correlated results can be used to perform programmed actions to increase the efficiency of the computing device and the user, such as in cases where content will be synchronized with a specific meeting and in cases where content will be shared with other users.

[0004] The present invention content is provided to introduce some concepts in a simplified form that will be further described in the detailed description below. The present invention content is neither intended to identify the key features or essential features of the claimed subject matter nor intended to be used to limit the scope of the claimed subject matter. Additional aspects, features, and / or advantages of the examples will be set forth in part in the description below, and in part will be obvious from the description, or may be learned by practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Non-limiting and non-exhaustive examples are described with reference to the following drawings.

[0006] Figure 1 An exemplary process flow is illustrated that can be utilized to practice aspects of the present disclosure, the process flow providing exemplary components that can be used to manage one or more proactive suggestions related to sharing meeting content as described herein.

[0007] Figures 2A - 2B An exemplary method related to managing proactive suggestions to facilitate sharing meeting content is illustrated that can be utilized to practice aspects of the present disclosure.

[0008] Figures 3A - 3G An exemplary view of a processing device is illustrated that can be utilized to practice aspects of the present disclosure, the processing device view providing an example of a user interface for providing one or more proactive suggestions that can be used to share meeting content.

[0009] Figure 4Illustrated is a computing system that can be utilized to practice aspects of the present disclosure, the computing system being suitable for implementing processing operations related to managing one or more active suggestions for sharing meeting content as described herein. Detailed Description

[0010] The present disclosure relates to processing operations configured to manage one or more active suggestions that can be used to manage sharing of meeting content. The present disclosure also describes optimization of a user interface to improve the user interface experience relative to a conventional user interface experience through new user interface features and actions that enable proactive presentation of suggestions for synchronizing content with a meeting and sharing the synchronized content. For example, various intelligent signals such as a user's calendar, GPS location, camera roll content, captured content (including OCR, whiteboard detection, etc.), and capture time are captured and analyzed to present intelligent suggestions to the user for sharing content with a particular set of users (e.g., those attending a meeting). Signal data can be collected for ad-hoc electronically scheduled meetings or non-routine meetings. In any example, the processing described herein enables context correlation between specific content and a scheduled meeting, whereby the context-correlated results can be used to perform programmed actions to improve the efficiency of the computing device and the user, such as in cases where content is to be synchronized with a particular meeting and in cases where content is to be shared with other users.

[0011] In some non-limiting examples, user interface prompts are generated that are automatically pre-filled with data to assist the user in sharing meeting content. For example, user interface fields can be pre-filled and / or suggestions presented to assist the user in associating content with an electronically scheduled meeting (or occurrence of an ad-hoc meeting) and sharing the content with other users. The interface prompts can be specifically configured for any type of application / service. In one example, an exemplary application / service is a productivity application / service for file hosting and synchronization (e.g., )。For example, a mode in which a user is operating an application / service (e.g., image capture mode, whiteboard mode, handwriting input mode, sticky note mode, content scanning mode, business card mode, audio / video capture mode, data backup mode) can be a trigger for associating content with a meeting on behalf of the user. In another example, the exemplary application / service is a productivity application / service, such as a camera application / service or a calendar application / service. However, the examples described herein are configured to work with any type of content and any type of application / service. Signal data can be collected and analyzed to generate insights for associating image content with an electronically scheduled meeting, where the user interface of the productivity application / service can be adapted to enable quick association of content with a meeting and identification of other users for sharing the content (e.g., meeting invitees or attendees). In one instance, a user interface prompt with a suggestion for associating specific content with a specific meeting is generated. In another instance, a user interface prompt can be generated that provides suggestions for sharing content with other users associated with the meeting.

[0012] In other non-limiting examples, sharing notifications are automatically generated on behalf of the user and automatically presented to the user. Exemplary sharing notifications can include reminders for associating content with an electronically scheduled meeting. For example, a sharing notification can be generated and presented within a predetermined time window for the occurrence of an electronically scheduled meeting, or in the case of an ad hoc electronic meeting. For example, the predetermined time window can be a time period: before the meeting; during the meeting; after the meeting; or a time period overlapping any combination thereof. In some alternative instances, for example, in the case where signal data is collected indicating that the user may have forgotten to associate content with a meeting or share content with other users, a sharing notification can be generated and displayed at a predetermined time window (e.g., one day, two days) after the meeting. Similar to other examples described herein, a type of mode in which the user is processing content can be for initiating a process of associating the content with a meeting and subsequently issuing a reminder notification to add the content to a storage device associated with the meeting and / or share the content with other users.

[0013] In additional examples, the relevance processing result that associates content with a meeting can be used to assist a user with other tasks or operations. Examples of such tasks or operations include, but are not limited to: automatically providing suggestions for adding content to a meeting event; supporting suggestions for searching topics / keywords; converting content to different formats (including adapting the content to work in different applications / services); facilitating collaboration among users with respect to the content; data organization suggestions (e.g., rearranging data in files and folders, grouping related content); and suggestions identified during data backup (e.g., suggestions for pairing content with a specific meeting or sharing content with other users), among other examples. In some cases, a user account can be associated with more than one meeting, where signal data can be collected and analyzed to suggest relevance between content and a specific meeting, or to provide a custom user interface prompt that enables the user to select a specific meeting associated with the content.

[0014] Exemplary technical advantages provided by the processes described in this disclosure include, but are not limited to: actively notifying and presenting suggestions for associating content with a specific meeting (or meeting group); actively notifying and generating sharing notifications that provide suggestions for sharing content with other users associated with a meeting; generating and applying a predicted confidence level for associating content with an electronically scheduled meeting; automatically pre-filling data fields in a contextually relevant manner on behalf of the user; improving the processing efficiency of a computing device during content capture and content sharing (e.g., reducing processing cycles, saving resources / bandwidth); adapting and improving a front-end user interface for active suggestion generation and content management; scaling to customize the processing operations described herein across multiple different applications / services; reducing latency during operation of an application / service; and improving the usability of an application / service, among other technical advantages.

[0015] Figure 1 Illustrated is an exemplary process flow 100 that can be utilized to practice aspects of the present disclosure. Process flow 100 provides exemplary components that can be used to manage one or more active suggestions related to sharing meeting content as described herein. For example, the components of process flow 100 can be implemented by, such as in Figure 4performed by the exemplary computing system(s) described in the description. The exemplary components described in process flow 100 can be hardware and / or software components programmed to perform the processing operations described herein. In one example, the components of process flow 100 can each be one or more computing devices associated with the execution of a particular service. The exemplary service can be managed by an application platform that also provides the components with access to and knowledge of other components associated with the application / service. In one instance, the processing operations described in process flow 100 can be implemented by one or more components connected on a distributed network. The operations performed in process flow 100 can correspond to operations performed by a system and / or service that executes computer programs, application programming interfaces (APIs), neural network or machine learning processing, language understanding processing, search and filtering processing, and generating content for presentation through the user interface of an application / service, and other examples. In the illustration of process flow 100, there are process flow steps that are non-limiting examples highlighting the interaction between the various components shown in Figure 1 without departing from the gist of the present disclosure. The process flow between components can be changed

[0016] Process flow 100 includes user computing device(s) 102 (e.g., client computing device). Examples of user computing device 102 are computing system(s) as described in the description of Figure 4 The user can interact with the exemplary application / service through user computing device(s) 102. For example, the user can connect to the application / service through any number of different device modalities. In some examples, the user can connect to the application / service through different user computing devices 102 (e.g., a productivity application / service used to access, create, or modify content), non-limiting examples of which are: smartphones, laptop computers, tablet computers, desktop computers, etc. In other cases, the user can perform multimodal communication with the application / service via multiple user computing devices.

[0017] A user may be accessing one or more applications / services used to perform any type of task via an interface between a computing device 102 and a productivity application / service component 106, including: accessing content; creating content; modifying content; managing content (including metadata) for a meeting; and attending a meeting (e.g., an electronically scheduled meeting or an ad-hoc meeting), among other examples. The application / service being accessed by the user is configured to provide a user interface or a graphical user interface (GUI) to support accessing content and creating / modifying content. An exemplary user interface may be adapted to provide the functionality described herein, wherein user interface features and application command controls are implemented to facilitate improved management of shared notifications and suggestions via new user interface features not present in conventional user interface systems. A new user interface menu may be presented to the user, the new user interface menu including proactive suggestions and notifications for managing content sharing with respect to an electronically scheduled meeting or an ad-hoc meeting. In Figures 3A - 3F A view of a processing device is provided that illustrates a non-limiting example of a user interface of the present disclosure.

[0018] As described above, an exemplary application / service may interface with other components of process flow 100 to enhance processing efficiency and functionality as described herein. The (one or more) productivity application / service components 106 are configured to interface with other components of process flow 100, including the (one or more) computing devices 102 and the (one or more) conferencing sharing components 104. The application / service may be any type of programmed software. An exemplary application / service is a productivity application / service that is configured to perform to enable a user to complete tasks on a computing device, where the exemplary productivity service may be configured to access content including electronic documents and create content including electronic documents. Examples of productivity services include, but are not limited to: word processing application / service, spreadsheet application / service, notes / note-taking application / service, authoring application / service, digital presentation application / service, search engine application / service, email application / service, messaging application / service, web browsing application / service, collaborative team application / service, digital assistant application / service, web building application / service, directory application / service, mapping application / service, calendar application / service, electronic payment application / service, file storage and synchronization application / service, digital data storage or distributed data storage application / service, web conferencing application / service, call communication application / service, camera application / service, audio / video application / service, language understanding application / service, robotics framework application / service, network application / service, and social network application / service, and other examples. In some examples, the exemplary productivity application / service may be a component of an application platform that provides a suite of productivity application / services. The application platform suite is configured to provide access to multiple applications / services, thereby enabling cross-application / service usage to enhance the functionality of a specific application / service at runtime. Since productivity features may span multiple functions, context relevance assessment is configured to identify the specific productivity features most relevant to the context in which the user is accessing an electronic document. Additionally, the specific application / service and the application platform suite may be configured to interface with other non-proprietary applications / services (e.g., third-party applications / services) to extend functionality including productivity feature suggestions and implementations.

[0019] (One or more) user computing devices 102 may be used to access content (or capture content) via one or more applications / services provided by (one or more) application / service components 106. In one example, the content may be locally stored on a data storage device associated with (one or more) user computing devices 102. In some other examples, (one or more) application / service components 106 are configured to provide a distributed storage device specific to a user account (or user group), where the content may be stored in (one or more) distributed storage devices and accessed by the user. As an example, the application / service may be an application / service for managing file storage and synchronization, which provides functions that enable users to: add file content, synchronize file content, backup file content, and capture new file content and share file content. In another instance, (one or more) user computing devices 102 may be used to capture content that is locally stored on a storage device associated with (one or more) user computing devices 102 and subsequently synchronized with a distributed application / service. In some examples, the user may be attempting to capture content (e.g., image content) via an application / service in a specific mode, and the application / service may provide details regarding the capture of the content. Types of content capture modes may include, but are not limited to: image capture mode; whiteboard mode; handwriting input mode; note mode; business card mode; content scanning mode; audio or video capture mode; and data backup mode, among other examples. In any example, (one or more) meeting sharing components 104 may be configured to interface with such applications / services to enable adjustment of a user interface that facilitates content related to a specific meeting (e.g., customized user interface prompts), provide pre-populated prompts for saving content, suggestions for managing content, and / or provide sharing notifications and suggestions.

[0020] As described above, the application / service component(s) 106 is configured to interface with the conferencing sharing component(s) 104. The interface between the application / service component(s) 106 and the conferencing sharing component(s) 104 enables the conferencing sharing component(s) 104 to collect and analyze signal data. As an example, a user may be capturing content via an application / service in which signal data is collected and analyzed to enable tasks and actions including, but not limited to: automatically providing suggestions for adding content to a meeting event; supporting suggestions for searching for topics / keywords; converting content to different formats (including adapting content to work in different applications / services); and facilitating collaboration among users for the content, among other examples. For instance, the type of pattern in which a user is capturing content can be a trigger for associating the content with a meeting on behalf of the user. If a user is capturing a photo in whiteboard mode, this may be a strong indication that the captured content may be relevant to a meeting at a time that overlaps with a predetermined time window for the meeting.

[0021] The conferencing sharing component(s) 104 is configured to perform the processing operations described herein to manage the relevance between content and a scheduled or ongoing meeting. The conferencing sharing component(s) 104 is also configured to subsequently manage the generation of user interface prompts that provide suggestions and notifications as described herein. Non-limiting examples of the processing operations performed by the conferencing sharing component(s) 104 include the processing operations described in method 200( Figure 2A ) and method 250 (Figure 250).

[0022] In one example, the (one or more) meeting sharing components 104 are configured to execute an application programming interface (API) that enables the collection and analysis of signal data related to associating content with a specific meeting. Examples of signal data that can be collected, parsed, and analyzed include: device-specific signal data; user-specific signal data (e.g., user account data and groups / teams); application / service-specific signal data; and any combination thereof. Non-limiting examples of specific signal data that can be collected from the sources identified above include, but are not limited to: calendar events associated with a user account; meeting details associated with an electronically scheduled meeting invitation; the invitee and / or attendee status of an electronically scheduled meeting invitation; geographic location data associated with a user computing device; metadata associated with specific content; results of identification analysis processing (e.g., optical character recognition (OCR) processing of image content, language understanding analysis, text and entity evaluation); the status of application / service execution (e.g., including signal data indicating the application / service being accessed by the user); signal data related to folder and file creation (e.g., creation of a folder for meeting content); and evaluation of tasks and reminders set by the (one or more) users, among other examples.

[0023] (One or more) meeting sharing components 104 can be configured to detect electronically scheduled meeting invitations, such as those scheduled in a calendar application / service or an email application / service. The electronically scheduled meeting invitations can be used for electronic meetings or meetings in person or by phone. In some examples, the application / service can detect the occurrence of an electronically scheduled meeting, for example, based on an analysis of signal data associated with the scheduling of the meeting and / or signal data indicating that the user is actively participating in the meeting. Alternatively, (one or more) meeting sharing components 104 can be configured to detect the ad-hoc occurrence of a meeting, for example, by calling a communication application / service (e.g., ), a social network application / service, an email application / service, a calendar application / service, a communication platform, etc.

[0024] In any example, the (one or more) meeting sharing components 104 can be configured to actively parse meeting data, for example, before, during, or after a meeting occurs, to generate insights related to associating content with the meeting. In other examples, the (one or more) meeting sharing components 104 can utilize the receipt of signal data within a given time window (e.g., a predetermined time period / window) in which the meeting occurs as a trigger for processing related to associating content with the meeting. The predetermined time window can be set by a developer and can be adjusted. For example, the predetermined time window can correspond to the time period set for the occurrence of the meeting, or can be within a given number of minutes, days, etc. before (or after) the meeting occurs. In some cases, the time window can correspond to a reminder (e.g., a pre-meeting reminder or a follow-up meeting reminder), where suggestions and / or notifications can be generated to remind the user to associate content with a specific meeting.

[0025] Signal data related to electronic details associated with an electronically scheduled meeting invitation (or an ad-hoc meeting) can be collected and analyzed to evaluate details that can be used to match content with a specific meeting. For example, the meeting title, subject, keywords, body text, etc. can be analyzed to identify meeting details that can be matched with the content to determine the relevance between the content and the meeting. Other types of data that can be analyzed from the meeting details include, but are not limited to: attachments; meeting invitees; attendee status; location; units connected to the meeting; and other examples.

[0026] In addition, the (one or more) meeting sharing components 104 are also configured to collect signal data for analyzing content that may be associated with a meeting. As indicated in the foregoing description, content can be accessed or captured via the (one or more) user computing devices 102 by accessing the executed applications / services. Any type of content can be relevant to a meeting, and non-limiting examples of content that can be analyzed include, but are not limited to: electronic documents / files; image content; text content; audio content; handwritten content; video content; rich interactive data objects; and messaging content (e.g., instant messages / chat messages, emails, social network posts), among other examples. The analysis of the signal data associated with the content can include evaluating: geographical location data associated with the user computing device; metadata associated with the specific content (including time / stamp data); the results of the identification analysis process (e.g., optical character recognition (OCR) process of image content, language understanding analysis, text and entity evaluation); the results of user actions, such as accessing content (e.g., when the user accesses the content), capturing content, etc.; the status of the application / service execution (e.g., including signal data indicating the application / service being accessed by the user), which includes the type of pattern of the content being accessed or captured; and signal data related to folder and file creation (e.g., creating a folder for meeting content), among other examples. For example, accessing or capturing content at a specific time that overlaps with the occurrence of a meeting (or within a predefined time window associated with the meeting) can provide a direct relevance suggestion that the accessed or captured content may be related to a specific meeting.

[0027] In some examples, the (one or more) meeting sharing components 104 are configured to analyze the signal data associated with the content. In other cases, the (one or more) meeting sharing components 104 interface with one or more other components via a distributed network to receive insights resulting from the analysis of the content. As an example, the (one or more) meeting sharing components 104 can be a component of or interface with an application / service of an application platform suite (e.g., ) that enables extension to multiple different applications / services that provide various functions.

[0028] (One or more) meeting sharing components 104 are also configured to perform processing operations for generating predictive or deterministic insights related to the meeting for the content. In one example, data analysis is performed by implementing data modeling for generating insights. For example, machine learning modeling can be applied to correlate the collected signal data and generate a confidence score for matching the content to a specific meeting. Other non-limiting examples related to the signal data include, but are not limited to: APIs, statistical classifiers, neural networks and artificial intelligence, and other examples. As is known to those skilled in the art, confidence scores or other ranking methods can be used to generate user interface prompts (including pre-filled data) and generate notifications (e.g., sharing notifications). For example, a threshold score can be used to generate a confidence determination that the content is associated with a specific meeting. In the case where the confidence threshold is not reached, (one or more) meeting sharing components 104 can be configured to generate a user interface feature that requests disambiguation from the user. For example, a user may have two concurrent scheduled meetings, where the content may be associated with either meeting. In such an example, one or more user interface prompts can be generated by (one or more) meeting sharing components 104, and the one or more user interface prompts can be presented through the user interface of the application / service to enable the user to select the specific meeting associated with the content. In some instances, (one or more) meeting sharing components 104 can be configured to pre-fill suggestions for associating the content with the two meetings, so that the user can easily and effectively select the suggestions and discard the irrelevant ones.

[0029] In some examples, (one or more) meeting sharing components 104 are configured to collect telemetry data to assist in generating predictive or deterministic insights. Non-limiting examples of the telemetry data collected for analysis include, but are not limited to: data to be scanned captured in a time window corresponding to the meeting; data captured for the content in a time window corresponding to the meeting (e.g., images, handwritten input, audio input, video input); metrics related to user interactions with notifications, suggestions, etc.; data related to the transmission of notifications (e.g., sent or received notifications); data related to collaborative access and sharing; data associated with the attendee / invitee status of the meeting; data related to the timing of the user's actions with respect to suggestions and / or notifications; data related to activating / deactivating notifications; and data related to the relevance of keywords in the content, e.g., the content matches a specific meeting, and other examples.

[0030] As described above, the (one or more) meeting sharing components 104 are configured to generate suggestions and notifications based on the results of the analysis of the aggregated signal data. The types of suggestions and / or notifications that can be generated include, but are not limited to: suggestions for saving content (e.g., for the content to include the meeting name in the file title); suggestions for associating content with a specific file or folder; suggestions for associating content with a specific meeting (or disambiguating multiple meetings); suggestions for sharing content with other users (e.g., other invitees or attendees of the meeting); notifications of the occurrence of a meeting, including reminders that associate content with the meeting; and suggestion notifications that associate specific content with a specific meeting, and other examples. In Figures 3A - 3F a view of a processing device is provided that illustrates non-limiting user interface examples of suggestions and notifications. The suggestions and / or notifications can be presented via the user interface of the application / service or via the user interface of the operating system executed on the client computing device 102.

[0031] In some non-limiting examples, user interface prompts are generated that are automatically pre-populated with data to assist the user in sharing meeting content. For example, user interface fields can be pre-populated and / or present suggestions to assist the user in associating content with an electronically scheduled meeting (or the occurrence of an ad-hoc meeting) and sharing content with other users. As an example, the (one or more) meeting sharing components 104 can be configured to use the attendee status (e.g., pending, accepted, rejected, tentative) to determine how to customize the user interface prompt to suggest users with whom to share the content. For example, the user interface prompt can be pre-populated with contact data for one or more invitees who have accepted an electronic meeting invitation for an electronically scheduled meeting. In other examples, data such as the meeting name, title, keywords, etc. can be used for naming conventions for a file (such as the content the user is capturing). In other examples, data extracted from the meeting details can be used to pre-populate the data fields of the sharing notification, where the message name or subject can include data identifying the specific meeting. The naming conventions and formats for the pre-populated content may vary according to developer preferences and can include any type of data obtained from the signal data analysis.

[0032] In other non-limiting examples, a shared notification is automatically generated on behalf of a user and automatically presented to the user. An exemplary shared notification can include a reminder associating content with an electronically scheduled meeting. For example, a shared notification can be generated and presented within a predetermined time window for the occurrence of an electronically scheduled meeting or in the case of an ad-hoc electronic meeting. For example, the predetermined time window can be a period of time: before the meeting; during the meeting; after the meeting; or a period of time overlapping any combination thereof. In some alternative instances, for example, in the case where it is determined that the user may have forgotten to associate content with a meeting or share content with other users, a shared notification can be generated and presented at a predetermined time window (e.g., one day, two days) after the meeting has occurred. Similar to other examples described herein, a type of pattern in which a user is handling content can be a process for initiating the association of content with a meeting and subsequently issuing a reminder notification to add the content to a storage device associated with the meeting and / or share the content with other users.

[0033] In additional examples, the results of a relevance process for associating content with a meeting can be used to assist a user with other tasks or operations. Examples of such tasks or operations include, but are not limited to: automatically providing suggestions for adding content to a meeting event; supporting suggestions for search topics / keywords; converting content to different formats (including adapting the content to work in different applications / services); facilitating collaboration among users for the content; data organization suggestions (e.g., rearranging data in files and folders, grouping related content); and suggestions identified during data backup (e.g., suggestions for pairing content with a specific meeting or sharing content with other users), among other examples.

[0034] Figures 2A - 2B Illustrated is an exemplary method related to the management of proactive suggestions for facilitating the sharing of meeting content that can be utilized to practice aspects of the present disclosure. The processing operations described in method 200 ( Figure 2A ) and method 250 ( Figure 2B ) can be performed by the components described in process flow 100 ( Figure 1 ), where the detailed description in process flow 100 supports and supplements the processing operations recited in the respective methods. Interfaces and communications between exemplary components such as those described in process flow 100 are known to those skilled in the art. For example, data requests and responses can be transmitted between applications / services such that a particular application / service can process data retrieved from other applications / services. Without departing from the spirit of the present disclosure, the format for such communications can vary according to the programmed protocols implemented by the developer.

[0035] As an example, method 200 and method 250 can be performed across an exemplary computing system (or computing systems) as described in Figure 4 the description. The exemplary components described in method 200 and method 250 can be hardware and / or software components programmed to perform the processing operations described herein. The operations performed in method 200 and method 250 can correspond to operations performed by a system and / or service that executes computer programs, software agents, intelligent robots, application programming interfaces (APIs), neural networks, and / or machine learning processes, among other examples. In some examples, the processing operations described in method 200 and method 250 can be performed by one or more applications / services associated with a web service that can access multiple applications / services, devices, knowledge resources, etc. In one instance, the processing operations described in method 200 and method 250 can be implemented by one or more components connected on a distributed network.

[0036] Method 200 begins with processing operation 202, where signal data associated with a meeting is analyzed. As described in the previous description, signal data can be analyzed for electronically scheduled meetings as well as in the case of an ad-hoc meeting. Processing operation 202 can be performed by a meeting sharing component 104 as described in Figure 1 the description. Examples of the analysis of signal data by the meeting sharing component 104 have been provided in the previous description. For example, non-limiting examples of signal data evaluated in processing operation 202 include, but are not limited to: detecting a scheduled meeting time for the electronically scheduled meeting; detecting the attendance status of invitees to the electronically scheduled meeting; and parsing meeting details associated with the electronically scheduled meeting.

[0037] In some examples of method 200, the process can proceed to processing operation 204, where access to content can be detected. For example, a user can access content (e.g., select, open, create) during a meeting (e.g., an electronically scheduled meeting) or at or near the occurrence of a predetermined time window associated with the meeting. This can be a trigger to associate the content with a specific meeting (processing operation 206).

[0038] In other examples of method 200, access to content is not required to initiate the association of the content with a specific meeting (processing operation 206). Processing operation 206 can be performed by a component as described in Figure 1It is executed by the conference sharing component 104 described therein. Examples related to the relevance of content and a specific conference have been provided in the foregoing description. The relevance of content to a specific conference (processing operation 206) may include operations such as the following: evaluating the content and data associated with the content (e.g., metadata, telemetry data; signal data associated with capturing or accessing the content); generating specific insights based on the matching of data from content analysis with data from the analysis of signal data associated with the electronically arranged conference; and generating a confidence determination for determining whether the content is relevant to a specific conference. As an example, a probability confidence level assessment associating the content with a specific conference may be generated. In one example, the relevance processing (processing operation 206) includes matching the access time of the content with a predetermined time window associated with the scheduled conference time for the electronically arranged conference. This can help identify content that is accessed or captured around the time when the electronically arranged conference occurs.

[0039] The flow of method 200 can proceed to processing operation 208, where a sharing notification is generated. The sharing notification can be generated based on the relevance of the content to a specific conference (processing operation 208). In one example, the sharing notification may include a reminder associating the content with the electronically arranged conference. In another example, the sharing notification may specifically identify the content and / or the specific conference (e.g., the electronically arranged conference) to remind the user to associate the content with the conference. In yet another example, the sharing notification may include a suggestion to share the content with other users associated with the conference. For example, the sharing notification can be pre-populated with contact data for one or more invitees (or attendees of the conference). The confidence level assessment generated in processing operation 206 can be used to customize user interface prompts for applicable use cases (e.g., what data to include in the pre-populated suggestions) for the suggestions and / or notifications.

[0040] At processing operation 210, the sharing notification is presented via a user interface executed on a computing device (e.g., the client computing device 102 described in Figure 1 ). As an example, the user interface can be an application / service executed on the computing device, such as a productivity application / service. In another example, the sharing notification is presented via a user interface associated with the operating system executed on the computing device.

[0041] Additional examples of method 200 include user processing results from interactions with users who share notifications. In processing operation 212, a selection of the shared notification is received. For example, a user may tap on the displayed shared notification or provide utterances that request further information regarding the displayed shared notification. In at least one example, receipt of the selection of the shared notification may trigger the display of a new user interface prompt. At processing operation 214, a new user interface prompt is displayed that includes pre-populated data for content to be shared with one or more meeting invitees (or attendees) of a particular meeting. As described previously, the pre-populated data may be generated based on processing the relevance of the content to a particular meeting (processing operation 206).

[0042] At decision operation 216, it is determined whether an action to share the content is received via the user interface. For example, a user may provide input to send the shared notification to one or more other users via the user interface, whether modified or not. In one example, sending the shared notification may include transmitting the shared notification to one or more pre-populated invitees. In an example where no share action is received, the flow of decision operation 216 branches to "No" and the processing of method 200 remains idle until subsequent processing is received. In an example where a share action is received, the flow of decision operation 216 branches to "Yes" and the processing of method 200 proceeds to processing operation 218. At processing operation 218, the content is shared with one or more meeting invitees. In some examples, processing operation 218 may also include providing the user with a notification that the content has been shared.

[0043] Turning to method 250, additional examples of processing operations related to the generation of proactive suggestions and notifications are provided.

[0044] Method 250 begins at processing operation 252, where access to content is detected by a user computing device. As an example, access to content may be detected at a time that overlaps with a predetermined time window for a meeting (e.g., an electronically scheduled meeting). In other instances, a user may be creating a document in preparation for a meeting, or a meeting may be occurring in the case where a user captures a photo of a whiteboard during the meeting. Detection of access to content (processing operation 252) may include detecting any file usage, including but not limited to: content opened by the user; content selected by the user; content viewed by the user or content captured by the user; and utterances spoken by the user that reference specific content (e.g., notes for reminders / tasks); and other examples. For example, during the occurrence of a meeting, a user may be capturing image content via a productivity application / service or the whiteboard mode of a camera application / service. Detection of access to content (processing operation 252) may also include collecting signal data associated with the access to content.

[0045] The process can proceed to processing operation 254, where the accessed content is analyzed. Processing operations related to the analysis of content, including the content itself as well as signal data and metadata associated with the content, have been described in the foregoing description (e.g., the description of the meeting sharing component 104 of Figure 1 ).

[0046] Method 250 can proceed to processing operation 256, where signal data associated with the meeting can be collected (processing operation 256) and analyzed (processing operation 258). The content can be related to data from a scheduled meeting (processing operation 260). Processing operations for collecting signal data, analyzing signal data, and associating content with one or more meetings have been described in the foregoing description (e.g., Figure 1 the description of the meeting sharing component 104 of ).

[0047] The processing of method 250 can proceed to operation 262, where one or more user interface prompts can be generated for the management of meeting content. The type of user interface prompt generated can depend on the context associated with the user's access to the content. For example, the following can be relevant: The user is capturing image content through an application / service at the time of a meeting (or within a predefined time window associated with the meeting). This may result in the generation of a user interface save prompt for the user to save the content associated with a specific meeting. In such a case, the user interface save prompt can be presented (processing operation 264) for the user to save the content and develop an association with the meeting (e.g., an electronically scheduled meeting). In some examples, the user interface save prompt can be pre-populated with data to associate the content with a storage folder for meeting content. For example, a storage folder can be created (or accessed) through a distributed application / service, where the storage folder can have a naming convention associated with the signal data extracted from the meeting. In other instances, the naming convention for files or folders can depend on the signal data extracted from the meeting as well as the signal data associated with the content. As a non-limiting example, whiteboard image content related to a specific meeting can have a naming convention similar to ("Meeting Name" - "Whiteboard"), indicating the meeting name and the type of content.

[0048] In a further example of method 250, a user interface prompt for sharing meeting content can be presented via the user interface of the application / service (processing operation 266). The user interface prompt can be configured to share image content with one or more invitees of the electronically scheduled meeting, wherein the user interface prompt is pre-populated with contact data for the one or more invitees based on the detected attendance status of the invitees for the electronically scheduled meeting. For example, the user interface prompt can be pre-populated with contact data for one or more invitees who have accepted an electronic meeting invitation for the electronically scheduled meeting. In some examples, based on the result of parsing the meeting details, the user interface prompt is further pre-populated with the meeting name for the electronically scheduled meeting.

[0049] At decision operation 268, it is determined whether an action to share content is received via the user interface of the application / service. For example, a user can provide input to send a share notification to one or more other users via the user interface, with or without modification. In one example, sending the share notification can include transmitting the share notification to one or more pre-populated invitees. In an example where no share action is received, the flow of decision operation 268 branches to "No", and the processing of method 250 remains idle until a subsequent process is received. In an example where a share action is received, the flow of decision operation 268 branches to "Yes", and the processing of method 250 proceeds to processing operation 270. At processing operation 270, the content is shared with one or more meeting invitees. In some examples, processing operation 270 can further include providing the user with a notification that the content has been shared.

[0050] Figures 3A - 3G An exemplary view of a processing device is illustrated that can be utilized to practice aspects of the present disclosure, the view of the processing device providing an example of a user interface for providing (one or more) proactive suggestions that can be used to share meeting content. In process flow 100 ( Figure 1 ), method 200 ( Figure 2A ), and method 250 ( Figure 2B ), the processing operations described support and complement the back-end processing for generating the exemplary view of the processing device shown in Figures 3A - 3G .

[0051] Figure 3APresents a processing device view 300, which illustrates an example of proactive suggestions for sharing content associated with a scheduled meeting. As an example, a scheduled meeting can be associated with a user account used to access the meeting. For example, the user account can be an invitee or attendee of an electronically scheduled meeting. The user account can log in to a computing device (e.g., an operating system) or an application / service (e.g., via a network connection), where the access initiated by the user account can be a trigger for performing backend processing operations to evaluate the status of the electronically scheduled meeting associated with the user account. In one example, the user account can be identified as an attendee of an upcoming, currently active, or recently ended web conference session (e.g., meeting). In any example, the processing operations described herein can be used to proactively generate and present a notification 302 on behalf of the user to assist in the processing efficiency and operation of the computing device and / or the executing application / service. The notification 302 is a user interface that provides suggestions for sharing content associated with a specific electronically scheduled meeting (e.g., "Jack and Greg Sync" associated with the user account). For example, during the occurrence of an electronically scheduled meeting or within a predetermined time window of the time when the scheduled meeting occurs, the user may be accessing image content or capturing a photo of a whiteboard (e.g., via a camera application / service, a distributed storage application / service, or other productivity application / service). An analysis can be performed that correlates the access to the image content with the meeting details associated with the meeting. The notification can be actively presented via the computing device to encourage the sharing and / or uploading of content that may be associated with the meeting. In other examples, the proactive notification 302 may be more of a general suggestion to remind attendees to share content for the meeting. The notification 302 can be an independent reminder for the user to take an action. Alternatively, the user interface can be adapted to enable linking task execution to the notification 302, where relevant content can be suggested via additional user interface prompts for sharing with other users (e.g., meeting invitees, attendees).

[0052] Figure 3B Presents a processing device view 310, which illustrates an example of a user interface notification customized for sharing content for a meeting. In one non-limiting example, the notification shown in the processing device view 310 can be a continuation example of the proactive notification 302( Figure 3A ), where selection of the proactive notification 302 can trigger user interface prompts pre-populated with meeting-specific data to assist in associating content with a specific electronically scheduled meeting. In other non-limiting examples, the user interface notification shown in the processing device view 310 can be the result of an action by a specific application / service (e.g., a productivity application / service), such as those shown in Figures 3C - 3G .

[0053] The user interface notifications shown in the processing device view 310 include a first user interface element 312 that provides a rendering of content (e.g., whiteboard image content) that a user may wish to associate with a meeting and / or share with other users. The content in the rendering can be content that the user is currently accessing, or content that has been captured and / or is contextually relevant to the meeting (e.g., title, topic, keywords, content, electronic document). In some cases, the user can manually select the content to be shared. In other cases, for example, based on a confidence analysis indicating the relevance between the content and the meeting, the processing operations described herein can be performed to pre-fill user interface prompts with relevant content.

[0054] The user interface prompt shown in the processing device view 310 can also include a second user interface element 314 that provides the relevance to a meeting (e.g., an electronically scheduled meeting). The second user interface element 314 can be pre-filled with specific data for the electronically scheduled meeting, can be selected based on an automatic evaluation of signal data, or can be manually selected by the user. In some alternative examples, a user account can be associated with multiple electronically scheduled meetings, where additional user interface prompts can be presented via the user interface to disambiguate the determination of the confidence level for associating content with a specific meeting. In a non-limiting example shown in the processing device view 310, the second user interface element 314 identifies the title ("Jack and Greg Synchronization") for the shared content imported from an active meeting. The pre-filled title also identifies the type of content (e.g., "Whiteboard" for whiteboard image content) to further assist the user in identifying how the content is bound to the meeting. There can also be alternative ways to pre-fill naming conventions without departing from the spirit of the present disclosure.

[0055] In addition, the user interface prompt further includes a third user interface element 316 that identifies the recipients with whom to share the content. The recipients can be derived from an evaluation of the signal data for the electronically scheduled meeting, where the recipients can include invitees or attendees of the electronically scheduled meeting. Developers can configure rules for pre-filling user interface prompts based on the status of the attendees, including but not limited to: all invitees; users indicating that they will be attendees of the meeting; users who declined to attend the meeting; users who temporarily accepted the electronic meeting invitation; users who have not yet responded to the electronic meeting invitation, and any combination thereof, among other examples.

[0056] The user interface prompt may further include a fourth user interface element 318 that enables a user to easily share content with other users. For example, when the user selects to send a sharing notification via the fourth user interface element 318, the content can be automatically shared with the designated recipients. In some examples, the user may be sharing content through a distributed storage application / service, where the content can be saved (or backed up) on a distributed storage device associated with the user account (or the accounts of a group of users). In such examples, the shared content can be associated with a specific storage device or directory (e.g., folder) related to the content of the electronically scheduled meeting. This can also occur in addition to directly sharing the content with other user accounts associated with the recipients. In other cases, a copy of the shared content can be locally stored on the computing device associated with the user.

[0057] Figure 3C A processing device view 320 is presented, which illustrates another example of an active suggestion for sharing content associated with a scheduled meeting. The example shown in the processing device view 320 is another alternative type of active notification that can represent the user. In Figure 3A The active notification 302 shown in is a suggestion that identifies the correlation between a specific type of accessed content (e.g., whiteboard image) and an electronically scheduled meeting. Compared with the active notification 302 shown in Figure 3A the active notification 302 shown in, in Figure 3C the active notification 322 shown in is a more general notification that serves as a reminder that the user is in a meeting and that sharing the content may be most relevant before a period of time has passed. For example, if the user forgets to upload content during or immediately after the meeting, the likelihood of them adding relevant content at a later time will be significantly reduced. This can result in inefficiencies for the user and inefficient operation of the computing device resources, where the user may have to search for the relevant content.

[0058] Figure 3D A processing device view 330 is presented, which illustrates a user interface example where the user is actively initiating the capture of content (e.g., images, videos, audio, handwritten input) through a productivity application / service. Non-limiting examples of productivity applications / services are distributed data storage applications / services, which may include user interface features to enable the user to manage the content associated with their user account. As an example, the user can select (operation 332) a user interface element to initiate the capture of content. The user may wish to capture content during an electronically scheduled meeting or within a predetermined time window / period associated with the electronically scheduled meeting.

[0059] Figure 3E A processing device view 340 is presented, which illustrates from the processing device view 330 (Figure 3D ) A continued user interface example of the example shown in. In the processing device view 340, the user interface of the productivity application / service is configured such that the user can actively capture content. In the exemplary display, the user is attempting to capture image content from a whiteboard. The user has selected (operation 342) to enter a specific mode for content capture (e.g., whiteboard mode) to best capture the content. Then, the user can perform a second selection (operation 344) to capture the specific content. In the example shown, operation 344 involves selecting the photo capture button to capture an image of the whiteboard.

[0060] Without departing from the gist of the present disclosure, the examples described herein can be configured to be used in any type of mode for content capture. Additionally, different productivity applications / services can have different modes for the capture of content, where any type of content can be captured and then its relevance to a meeting can be analyzed in turn. Non-limiting examples of content capture modes have been described in the foregoing description. The processing operations described herein related to evaluating signal data associated with accessing content (e.g., capturing content) can utilize signal data related to the type of mode in which the content is captured to assist in confidence determination when correlating the content with signal data for an electronically scheduled meeting. For example, a whiteboard image may be more suitable for a brainstorming meeting than a video of a user walking his dog.

[0061] Figure 3F The processing device view 350 is presented, which illustrates a sequential user interface example from the example shown in the processing device view 340 ( Figure 3E ) In the processing device view 352, a user interface save prompt 352 is actively presented to the user to assist in saving the captured image content. For example, the relevance evaluation described herein can associate the capture of image content with the occurrence of an electronically scheduled meeting. Such analysis enables the application / service to utilize meeting-specific data to actively pre-fill the user interface save prompt 352 such that the user may not have to manually associate the content with the meeting. In the example shown, the title for the captured content ("Jack and Greg Synchronize Whiteboard") is pre-filled, which associates the captured whiteboard image with the occurrence of an electronically scheduled meeting. Additionally, the signal data correlation between the content and the electronically scheduled meeting can also enable the application / service to be pre-filled with a save path or directory for storing the captured content. For example, the captured content can be saved to a folder associated with the meeting content for a specific meeting (e.g., "Jack and Greg Synchronize").

[0062] Figure 3GPresents a processing device view 360, which illustrates another example of proactive suggestions for sharing content associated with a scheduled meeting. The processing device 360 can be a continuing example of the processing shown in the processing device view 350( Figure 3F ), where the user has saved the captured content 362 to a storage device associated with their user account. In the example shown, on behalf of the user, a sharing notification 364 is proactively provided, alerting the user to the opportunity to share the content with other attendees of the relevant meeting. The user can select the sharing notification 364 to initiate an automated process to share the specific content with the identified attendees. In one such example, additional user interface prompts can be utilized to prompt the user, such as the user interface notification shown in the processing device view 310( Figure 3B ). This can enable the user to customize the sharing link according to their preferences.

[0063] Figure 4 Illustrates a computing system that can be utilized to practice aspects of the present disclosure, the computing system being suitable for implementing processing operations related to managing proactive suggestions for sharing meeting content described herein. The computing system 401 represents any system or collection of systems in which the various applications, services, scenarios, and processes disclosed herein can be implemented. Examples of the computing system 401 include, but are not limited to: server computers, rack servers, web servers, cloud computing platforms and data center equipment, and any other type of physical or virtual server machine, container, and any variations or combinations thereof. Other examples can include: smart phones, laptop computers, tablet computers, desktop computers, hybrid computers, gaming consoles, virtual reality devices, portable electronic devices, smart TVs, smart watches and other wearable devices, and any variations or combinations thereof.

[0064] The computing system 401 can be implemented as a single device, system, or apparatus, or can be implemented in a distributed manner as multiple devices, systems, or apparatuses. For example, the computing system 401 can include one or more computing devices that perform processing for applications and / or services over a distributed network to enable the processing operations described herein to be performed on one or more services. The computing system 401 can include a collection of devices that perform processing for front-end applications / services, back-end applications / services, or a combination thereof. The computing system 401 includes, but is not limited to: a processing system 402, a storage system 403, software 405, a communication interface system 407, and a user interface system 409. The processing system 402 is operatively coupled to the storage system 403, the communication interface system 407, and the user interface system 409. The processing system 402 loads and executes the software 405 from the storage system 403. The software 405 includes one or more software components (e.g., 406a and 406b) that are configured to satisfy the (one or more) shared components 406a and application / service components 406(b) (e.g., productivity application / service components). Examples of such components, including executable processing operations, have been described in the foregoing description. In some examples, the computing system 401 can be a computing device used by a user to access content and / or connect to an electronic meeting. The computing system 401 can be configured to provide an adapted user interface that is improved compared to a conventional user interface, where the user interface can be customized to support proactive suggestions for sharing meeting content, as described herein. When executed by the processing system 402, the software 405 directs the processing system 402 to operate as described herein for at least the various processes, operation scenarios, and sequences discussed in the foregoing implementations. The computing system 401 can optionally include additional devices, features, or functions not discussed for the sake of brevity.

[0065] Still referring to Figure 4 ,the processing system 402 can include a processor, a microprocessor, and other circuitry that retrieves and executes the software 405 from the storage system 403. The processing system 402 can be implemented within a single processing device, but can also be distributed across multiple processing devices or subsystems that cooperate to execute program instructions. Examples of the processing system 402 include general-purpose central processing units, graphics processing units, dedicated processors and logic devices, and any other type of processing device, combinations, or variations thereof.

[0066] The storage system 403 can include any computer-readable storage medium that is readable by the processing system 402 and capable of storing software 405. The storage system 403 can include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, caches, or other data. Examples of storage media include: random access memory, read-only memory, magnetic disks, optical disks, flash memory, virtual and non-virtual memory, cassette tapes, magnetic tapes, magnetic disk storage, or other magnetic storage devices, or other suitable storage media, excluding propagated signals. In any case, a computer-readable storage medium is not a propagated signal.

[0067] In addition to the computer-readable storage medium, in some implementations, the storage system 403 can also include a computer-readable communication medium on which at least some of the software 405 can be communicated internally or externally. The storage system 403 can be implemented as a single storage device, but can also be implemented across multiple storage devices or subsystems located in the same location or distributed relative to each other. The storage system 403 can include additional elements capable of communicating with the processing system 402 or possibly with other systems, such as a controller.

[0068] The software 405 can be implemented as program instructions, and other functions can direct the processing system 402 to operate as described with respect to the various operation scenarios, sequences, and processes illustrated herein when executed by the processing system 402. For example, the software 405 can include program instructions for implementing software components, hardware components, or combinations thereof. Specifically, the program instructions can include various components or modules that cooperate or otherwise interact to perform the various processes and operation scenarios described herein. The various components or modules can be embodied in compiled or interpreted instructions, or in some other variant or combination of instructions. The various components or modules can be executed serially or in parallel, synchronously or asynchronously, in a single-threaded environment or a multi-threaded environment, or according to any other suitable execution paradigm, variant, or combination thereof. The software 405 can include additional processes, programs, or components, such as operating system software, virtual machine software, or other application software. The software 405 can also include firmware or some other form of machine-readable processing instructions executable by the processing system 402.

[0069] Typically, when software 405 is loaded into and executed by processing system 402, it can transform a general-purpose computing system, represented by computing system 401, into a special-purpose computing system customized to process data and respond to queries. In fact, the encoded software 405 on storage system 403 can transform the physical structure of storage system 403. The specific transformation of the physical structure can depend on various factors in different implementations of this description. Examples of such factors can include, but are not limited to: the technology of the storage medium used to implement storage system 403, whether the computer storage medium is characterized as a main storage device or an auxiliary storage device, and other factors.

[0070] For example, if a computer-readable storage medium is implemented as a semiconductor-based memory, when program instructions are encoded therein, software 405 can transform the physical state of the semiconductor memory, such as by transforming the states of transistors, capacitors, or other discrete circuit elements that make up the semiconductor memory. Similar transformations can occur with respect to magnetic or optical media. Without departing from the scope of this specification, other transformations of the physical medium are possible, and the foregoing examples are provided only to facilitate this discussion.

[0071] Communication interface system 407 can include communication connections and devices that allow communication with other computing systems (not shown) via a communication network (not shown). Communication interface system 407 can also be used to encompass the interfaces between the processing components described herein. Examples of the connections and devices that together allow inter-system communication can include network interface cards or devices, antennas, power amplifiers, RF circuits, transceivers, and other communication circuits. The connections and devices can communicate over a communication medium to exchange communications with other computing systems or system networks (such as metal, glass, air, or any other suitable communication medium). The foregoing media, connections, and devices are well known and need not be discussed in detail herein.

[0072] User interface system 409 is optional and can include a keyboard, a mouse, a voice input device, a touch input device for receiving touch gestures from a user, a motion input device for detecting non-touch gestures and other movements of the user, and other equivalent input devices and associated processing elements capable of receiving user input from the user. Output devices, such as a display, a speaker, a tactile device, and other types of output devices, can also be included in user interface system 409. In some cases, the input device and the output device can be combined in a single device, such as a display capable of displaying images and receiving touch gestures. The foregoing user input and output devices are well known in the art and need not be discussed in detail herein.

[0073] The user interface system 409 may also include associated user interface software that can be executed by the processing system 402 to support the various user input and output devices discussed above. The user interface software and user interface devices can be used alone or in combination with each other and with other hardware and software elements, such as to support a graphical user interface, a natural user interface, or any other type of user interface, to implement front-end processing of the exemplary applications / services (including productivity applications / services) described herein.

[0074] Communication between the computing system 401 and other computing systems (not shown) can occur over one or more communication networks and according to various communication protocols, combinations of protocols, or variations thereof. Examples include intranets, the Internet, internets, local area networks, wide area networks, wireless networks, wired networks, virtual networks, software-defined networks, data center buses, computing backplanes, or any other type of network, combination of networks, or variation thereof. The foregoing communication networks and protocols are well known and need not be discussed in detail herein. However, some communication protocols that may be used include, but are not limited to: Internet Protocol (IP, IPv4, IPv6, etc.), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP), as well as any other suitable communication protocol, variation, or combination thereof.

[0075] In any of the above examples where data, content, or any other type of information is exchanged, the exchange of information can occur according to any one of a variety of protocols, including FTP (File Transfer Protocol), HTTP (Hypertext Transfer Protocol), REST (Representational State Transfer), WebSocket, DOM (Document Object Model), HTML (Hypertext Markup Language), CSS (Cascading Style Sheets), HTML5, XML (Extensible Markup Language), JavaScript, JSON (JavaScript Object Notation), and AJAX (Asynchronous JavaScript and XML), as well as any other suitable protocol, variation, or combination thereof.

[0076] The functional block diagrams, operational scenarios and sequences, and flowcharts provided in the accompanying drawings depict exemplary systems, environments, and methods for performing the novel aspects of the present disclosure. Although, for purposes of simplified explanation, the methods included herein may be in the form of functional diagrams, operational scenarios or sequences, or flowcharts and may be described as a series of acts, it should be understood and appreciated that these methods are not limited by the order of acts, as some acts may occur in a different order and / or concurrently with other acts than those shown and described herein. For example, those skilled in the art will understand and appreciate that a method may alternatively be represented as a series of related states or events, such as in a state diagram. Additionally, not all acts shown in the methods may be required for novel implementations.

[0077] The description and drawings included herein depict specific implementations to teach those skilled in the art how to make and use the best mode. Some conventional aspects have been simplified or omitted for purposes of teaching the inventive principles. Those skilled in the art will recognize variations from these implementations that fall within the scope of the present invention. Those skilled in the art will also understand that the above features may be combined in various ways to form multiple implementations. As a result, the present invention is not limited to the above specific implementations, but is defined only by the claims and their equivalents.

[0078] Throughout the specification, reference has been made to "one example" or "an example," which means that a particular described feature, structure, or characteristic is included in at least one example. Thus, the use of such phrases may refer to more than one example. Additionally, the described features, structures, or characteristics may be combined in any suitable manner in one or more examples.

[0079] However, those skilled in the relevant art will recognize that examples may be practiced without one or more of the specific details, or in conjunction with other methods, resources, materials, etc. In other instances, well-known structures, resources, or operations have not been shown or described in detail, merely to obscure aspects of the examples.

[0080] Although the exemplary examples and applications have been shown and described, it should be understood that the examples are not limited to the above exact configurations and resources. Various modifications, changes, and variations that are obvious to those skilled in the art may be made to the arrangements, operations, and details of the disclosed methods and systems without departing from the scope of the claimed examples.

Claims

1. A method, comprising: analyzing signal data associated with an electronic meeting invitation for an electronically scheduled meeting for a user account that is an attendee of the electronically scheduled meeting, wherein the analyzing of the signal data comprises: detecting the occurrence of the electronically scheduled meeting, and detecting the attendance status of an invitee associated with the electronic meeting invitation for the electronically scheduled meeting; detecting that an image content is captured by a computing device associated with the user account during the occurrence of the electronically scheduled meeting; automatically generating a message prompt after a predetermined period of time has elapsed after detecting that the time of the electronically scheduled meeting has ended, the message prompt being configured to assist in sharing the image content with one or more invitees of the electronically scheduled meeting, wherein the automatic generation of the message prompt comprises: pre-populating the message prompt based on the detected attendance status of the invitee from the electronic meeting invitation, using an identification of the image content and contact data for the one or more invitees; and presenting the message prompt via a user interface of an application or service.

2. The method according to claim 1, further comprising: parsing meeting details associated with the electronic meeting invitation for the electronically scheduled meeting, and wherein the presenting comprises: pre-populating the message prompt based on a result of the parsing of the meeting details associated with the electronic meeting invitation, using contact data for one or more invitees who have accepted the electronic meeting invitation for the electronically scheduled meeting.

3. The method according to claim 1, further comprising: analyzing the image content and data associated with the image content, wherein detecting that the image content is captured comprises: associating the image content with the electronically scheduled meeting by matching a timestamp of a capture time of the image content with a timestamp associated with the occurrence of the electronically scheduled meeting.

4. The method according to claim 1, wherein the analyzing of the signal data further comprises: parsing meeting details associated with the electronic meeting invitation for the electronically scheduled meeting, and wherein the user interface prompt is further pre-populated based on a result of the parsing of the meeting details, using a meeting name for the electronically scheduled meeting.

5. The method according to claim 1, wherein The analysis of the signal data further includes: parsing meeting details associated with the electronic meeting invitation for the electronically scheduled meeting, and the method further includes: after a predetermined period of time has elapsed after the time of the electronically scheduled meeting has ended, presenting a user interface save prompt through a user interface of a distributed storage application or service to save the image content to a storage folder associated with the electronically scheduled meeting, and wherein the user interface save prompt automatically pre-populates, based on the result of the parsing of the meeting details of the electronic meeting invitation, the storage folder with the meeting name for the electronically scheduled meeting.

6. The method according to claim 1, wherein, detecting that the image content is captured further includes: detecting that the image content is actively captured through an operating mode of a distributed storage application or service, and wherein the method further includes: collecting the signal data associated with the electronically scheduled meeting from the distributed storage application or service, and wherein the analysis analyzes the signal data collected from the distributed storage application or service during the process of detecting that the image content is captured during the occurrence of the electronically scheduled meeting.

7. A system, comprising: at least one processor; and a memory operatively connected to the at least one processor that stores computer-executable instructions that, when executed by the at least one processor, cause the at least one processor to perform a method including the following operations: analyzing signal data associated with an electronic meeting invitation for an electronically scheduled meeting for a user account that is an attendee of the electronically scheduled meeting, wherein the analysis of the signal data includes: detecting the occurrence of the electronically scheduled meeting, and detecting the attendance status of the invitees associated with the electronic meeting invitation for the electronically scheduled meeting; detecting that an image content is captured by a computing device associated with the user account during the occurrence of the electronically scheduled meeting; and automatically generating a message prompt after detecting that a predetermined period of time has elapsed after the time of the electronically scheduled meeting has ended, the message prompt being configured to assist in sharing the image content with one or more invitees of the electronically scheduled meeting, wherein the automatic generation of the message prompt includes: based on the detected attendance status of the invitees from the electronic meeting invitation, pre-populating the message prompt with an identifier of the image content and contact data for the one or more invitees; and presenting the message prompt through a user interface of an application or service.

8. The system according to claim 7, wherein, The method executed by the at least one processor further includes: parsing meeting details associated with the electronic meeting invitation for the electronically scheduled meeting, and wherein the presentation includes: based on the result of the parsing of the meeting details associated with the electronic meeting invitation, pre-populating the message prompt with contact data for one or more invitees who have accepted the electronic meeting invitation for the electronically scheduled meeting.

9. The system according to claim 7, wherein, The method executed by the at least one processor further includes: analyzing the image content and data associated with the image content, and wherein detecting that the image content is captured includes: associating the image content with the electronically scheduled meeting by matching a timestamp of the capture time of the image content with a timestamp associated with the occurrence of the electronically scheduled meeting.

10. The system according to claim 7, wherein, The analysis of the signal data further includes: parsing meeting details associated with the electronic meeting invitation for the electronically scheduled meeting, and wherein the user interface prompt is also pre-populated based on the result of the parsing of the meeting details with the meeting name for the electronically scheduled meeting.

11. A method, comprising: analyzing signal data associated with an electronic meeting invitation for an electronically scheduled meeting for a user account, the user account being an attendee of the electronically scheduled meeting, wherein the analysis of the signal data includes: detecting a scheduled meeting time for the electronically scheduled meeting from the electronic meeting invitation, and detecting an attendance status of an invitee of the electronic meeting invitation for the electronically scheduled meeting; detecting that an image content is captured by a computing device associated with the user account during the occurrence of the electronically scheduled meeting; automatically generating a sharing notification for the user account after a predetermined period of time has elapsed after detecting that the time of the electronically scheduled meeting has ended, the sharing notification including a reminder associating the image content with the electronically scheduled meeting, wherein the automatic generation of the sharing notification includes: based on the detected attendance status of the invitee from the electronic meeting invitation, pre-populating the sharing notification with an identifier of the image content and contact data for one or more invitees; and presenting the sharing notification through a user interface of an application or service.

12. The method according to claim 11, wherein, The analysis of the signal data further includes: parsing meeting details associated with the electronic meeting invitation for the electronically scheduled meeting to identify a title of the electronically scheduled meeting, and wherein the sharing notification provides a name for the image content as the identifier of the image content, the name including the title of the electronically scheduled meeting.

Images