Patent Grant
10650085
People interact with computer applications through user interfaces. While audio, tactile, and similar forms of user interfaces are available, visual user interfaces through a display device are the most common form of a user interface. With the development of faster and smaller electronics for computing devices, smaller size devices such as handheld computers, smart phones, tablet devices, and comparable devices have become common. Such devices execute a wide variety of applications ranging from communication applications to complicated analysis tools. Many such applications display a message and a preview of a content associated with the message through a display and enable users to provide input associated with the applications' operations.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to exclusively identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
Embodiments are directed to an interactive preview of a content within a communication. In some example embodiments, a messaging application may detect an insertion of a link of a content into a message. The content may include media such as a text, a video, an audio, an image, a graphic, an animation, or a combination of media, among others. The message may include an email message, or a text message, among others that may be displayed within a message body pane of a user interface of the messaging application. Information associated with the content may be retrieved from a content provider that stores the content. The information may be displayed in the interactive preview. The information may include a metadata of the content such as a title, a summary, a creation timestamp, and a last edit timestamp, among other attributes associated with the content.
The interactive preview may be generated based on the information. The interactive preview may provide actions to manage the interactive preview and the content. The actions may include an edit action, an add attachment action, a choose-preview-image action, a remove preview action, a remove-preview-image action, and a change permission action, among others. The interactive preview may be inserted into the message in proximity to a location of the insertion of the link. Custom operations associated with the actions that are selected by a user or settings associated with the content may be executed in response to a detection of a transmission of the message.
These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory and do not restrict aspects as claimed.
As briefly described above, an interactive preview of a content may be provided within a communication by a messaging application. Information associated with the content may be retrieved from a content provider in response to a detection of an insertion of a link of the content into the message. The interactive preview may be generated based on the information. The interactive preview may provide actions to manage the interactive preview and the content. The interactive preview may be inserted into the message in proximity to a location of where the link is inserted. Custom operations associated with the action may be executed in response to a detected transmission of the message.
In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computing device, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Embodiments may be implemented as a computer-implemented process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program that comprises instructions for causing a computer or computing system to perform example process(es). The computer-readable storage medium is a computer-readable memory device. The computer-readable memory device includes a hardware device that includes a hard disk drive, a solid state drive, a compact disk, and a memory chip, among others. The computer-readable storage medium can for example be implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, and a flash drive.
Throughout this specification, the term “platform” may be a combination of software and hardware components to provide an interactive preview of a content within a communication. Examples of platforms include, but are not limited to, a hosted service executed over a plurality of servers, an application executed on a single computing device, and comparable systems. The term “server” generally refers to a computing device executing one or more software programs typically in a networked environment. However, a server may also be implemented as a virtual server (software programs) executed on one or more computing devices viewed as a server on the network. More detail on these technologies and example embodiments may be found in the following description.
In a diagram 100, a computing device 104 may execute a messaging application 102. The computing device 104 may include a tablet device, a laptop computer, a desktop computer, and a smart phone, among others. The computing device 104 may display the messaging application 102 to a user 110. The user 110 may be allowed to interact with the messaging application 102 through an input device or touch enabled display component of the computing device 104. The computing device 104 may include a display device such as the touch enabled display component, and a monitor, among others to provide a user interface of the messaging application 102 to the user 110.
The messaging application 102 may detect an insertion of a link of a content into a message through an input 106 by the user 110. The content may include media such as a text, a video, an audio, an image, a graphic, an animation, or a combination of media, among others. The messaging application 102 may retrieve information associated with the content from a content provider such as a server 108. The information may include a metadata of the content. An interactive preview may be generated that includes actions, based on the metadata. The interactive preview may be presented to the user 110. Custom operations associated with the actions that are selected by the user 110 or settings associated with the content may be executed in response to a detection of a transmission of the message. The user 110 may interact with the messaging application 102 with a keyboard based input, a mouse based input, a voice based input, a pen based input, and a gesture based input, among others. The gesture based input may include one or more touch-based actions such as a touch action, a swipe action, and a combination of each, among others.
The messaging application 102 may retrieve the metadata of the content from a local source such as a storage media, a memory, a hard disk drive, and a solid state drive, among others that store the content. The metadata may also be received from a content provider such as the server 108 that provides the content. An example of a content provider may include a document management server, a media management server, or a web server, among others.
While the example system in
In a diagram 200, a messaging application 202 may display a user interface to display summary of messages and the messages. The user interface may include a menu pane 204 that includes controls to switch between communication user interfaces such as an email user interface 206, a calendar user interface, or a contacts user interface, among others. The menu pane 204 may also display a user control 224 that provides an operation to access attributes associated with a user account that receives the messages.
The messaging application 202 may also display a navigation pane 205 that provides controls to manage categories where the messages may be cataloged. A folders control 216 may include operations to provide additional controls, which correspond to folders such as “sent,” “deleted,” and “archived,” among others in which the messages may be stored. A people control 218 may include operations to display summaries of messages based on a selected contact within a summary pane 210. A groups control 220 may include operations to display summaries of messages based on a selected group, within the summary pane 210.
The summary pane 210 may display summaries of messages. A message summary 212 may display identifying information such as a subject, a sender, and a sample text, among others of a corresponding message. The message summary 212 may also provide an attachment notification 214 to indicate that the message may include an attachment such as a content 211. The content 231 may include an audio file, a video file, an image file, a text file, and an animation file, among others.
A message pane 222 may display a body of a message 224 that corresponds to a selected message summary 212 on the summary pane 210. The message pane 222 may also display a reply message as the message 224 in response to a user action to reply to the message 224 associated with the message summary 212.
A user may insert a link 228 to the content 231 into the message 224. The messaging application 202 may retrieve a metadata 245 of the content 231 from a content provider that stores the content 231. The metadata 245 may include a preview image 230, a sample 232 of a text of the content 231. The sample 232 may include a title 241 of the content 231, and a summary 242 of the content 231, among other identifiers associated with the content 231.
An interactive preview may be generated based on the metadata 245. The interactive preview may include the preview image 230 and the sample 232. The interactive preview may also include actions 234 to manage the interactive preview and the content. Custom operations associated with the actions 234 that are selected by the user or settings associated with the content may be executed in response to a detection of a transmission of the message 224. Settings associated with the content may include settings that are associated with the content or an attachment associated with the message 224. An example of the settings may include permission settings associated with the content 231, the attachment, or the message 224. The custom operations may transmit changes to the metadata 245 to the content provider to allow the content provider to synchronize the metadata 245 and the content 231 with changes to the metadata 245.
In a diagram 300, a messaging application 302 may provide an edit action 336 to allow editing of a sample of a text of a content displayed in an interactive preview 327 of the content, within a message. The interactive preview 327 may be generated from information of a content associated with a link 328 displayed in the message. The information may include a metadata of the content.
The interactive preview 327 may be inserted in proximity to the link 328. In an example scenario, the interactive preview 327 may be inserted adjacent to the link 328. In another example scenario, the interactive preview 327 may be inserted below the link 328. The interactive preview 327 may include a sample of the text of the content such as a title of the content and a summary of the content. The interactive preview 327 may also include a preview image 330 of the content retrieved from the metadata.
The messaging application 302 may provide actions 334 that includes the edit action 336. In response to a detection of an activation of the edit action, controls may be provided to edit the sample 310. The controls may include font formatting controls, paragraph formatting controls, text insertion controls, and text deletion controls, among others.
Detected changes to the sample 310 may be inserted into the metadata. The metadata may be transmitted to the content provider to allow the content provider to synchronize the metadata with the changes and apply the changes to the content, as well. The updated metadata may be transmitted to the content provider in response to a detection of a transmission of the message that includes the interactive preview. The updated metadata may also be transmitted to the content provider based on a repeating duration such as every second, every other second, every minute, every hour, among others. Alternatively, the updated metadata may be transmitted to the content provider on demand based on a variety of system and user configurable attributes.
In a diagram 400, a messaging application 402 may generate and display an interactive preview 427 of a content associated with a link 428 of the content inserted into a message 424. The messaging application may provide a change permissions action 404 to allow a user of the messaging application 402 to restrict an access to the interactive preview 427 and the content associated with the interactive preview 427. The user may restrict the access to recipients 434 of the message 424.
The user may be allowed to select the recipients 434 from the “To:” control of a message pane that lists the recipients. The selected recipients may be assigned permission setting(s) for the interactive preview 427 and the content. The permission setting may include a read-only setting and a read or edit setting, among others. The permission setting(s) may be captured based on selections by the user.
The permission setting for the interactive preview 427 may be different from the permission setting for the content. In an example scenario, the user may select a read-only setting for the interactive preview 427 while selecting a read or edit setting for the content. The permission setting(s) may be inserted into the metadata. The metadata may be transmitted to the content provider to allow the content provider to update the metadata of the content with the permission setting(s).
In a diagram 500, a messaging application 502 may display a remove-preview-image action 536 to remove a preview image of a content associated with a link 528. In response to a detection of an activation of the remove-preview-image action 536, the messaging application 502 may remove a preview image of the content from the interactive preview displayed in proximity to the link 528. A sample pane may be expanded to display a sample 532 of text of the content in a larger area that overlaps a previous area occupied by the removed preview image of the content.
In a diagram 600, a messaging application 602 may display a remove preview action 636 to remove an interactive preview of a content associated with a link 628. The interactive preview may be displayed in proximity to the link 628 prior to the activation of the remove preview action 636. In response to a detection of an activation of the remove preview action 636, the interactive preview may be removed. The actions may be adjusted to provide custom operations that reflect the removed status of the interactive preview. In an example scenario, the actions that manage the interactive preview may be removed. Actions that add a new interactive preview of a new content associated with the link 628 may be displayed.
In a diagram 700, a messaging application 702 may display a choose-preview-image action 736 to allow a user to select a preview image associated with a content of a link 728. In response to an activation of the choose-preview-image action 736, a content type of the content may be detected from the metadata. Preview images associated with the content type may be located from preview image providers. An example of a preview image provider may include the content provider.
The preview images may be displayed on a preview image pane 730 to allow a user to select one of the preview images for inclusion in the interactive preview. A selection 738 of one of the images may be detected. The selected preview image may be included in the interactive preview.
A related content action 731 may also be displayed to locate and display a related content section in the interactive preview. In response to a detection of an activation of the related content action 731, the content provider may be queried to retrieve related content metadata of related content(s) 733 associated with the content. The related content metadata 745 may include a title and a summary, among other identifiers of the related content(s) 733.
In response to receiving the related content metadata, a related content section may be generated from the related content metadata. The related content section may be inserted into the interactive preview.
An add as attachment action may be provided to allow a user to insert the content referred by the link 728 as an attachment into the message. The attachment of the content may include any edits that changed the content. Operations to attach the content may include a retrieval of the content from the content provider, a storage of the content in a format associated with an attachment associated with the message, an insertion of the attachment into the message, among others. The operations associated with the add as attachment action may be executed in response to a detection of a transmission of the message or in response to an activation of the add as attachment action.
An edit title action may be provided to allow the user to edit a title of the content referred by the link 728. The title of the content displayed on the interactive preview may be changed in response to a detection of the user activating the edit title action and editing the title of the content.
A copy to action may be provided to allow the user to copy the content from a current storage location (such as the content provider) to a new storage location (such as a local storage). The content may be copied to the new storage location in response to a detection of a transmission of the message or in response to an activation of the copy to action.
The technical advantage of providing an interactive preview of a content within a communication may include improved usability of user interfaces that present a preview of content within a message while allowing a user to update the interactive preview and the content through the interactive preview compared to legacy messaging solutions.
The example scenarios and schemas in
Client applications executed on any of the client devices 811-813 may facilitate communications via application(s) executed by servers 814, or on individual server 816. A messaging application may retrieve metadata associated with a content in response to a detection of an insertion of a link of the content into a message. An interactive preview of the content may be generated based on the metadata. The interactive preview (that provides actions to manage the interactive preview and the content) may be inserted to the message in proximity to the link. Custom operations of the operations may be executed in response to a transmission of the message. The messaging application may store data associated with content in data store(s) 819 directly or through database server 818.
Network(s) 810 may comprise any topology of servers, clients, Internet service providers, and communication media. A system according to embodiments may have a static or dynamic topology. Network(s) 810 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet. Network(s) 810 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks. Furthermore, network(s) 810 may include short range wireless networks such as Bluetooth or similar ones. Network(s) 810 provide communication between the nodes described herein. By way of example, and not limitation, network(s) 810 may include wireless media such as acoustic, RF, infrared and other wireless media.
Many other configurations of computing devices, applications, data sources, and data distribution systems may be employed to provide an interactive preview of a content within a communication. Furthermore, the networked environments discussed in
For example, the computing device 900 may be used to provide an interactive preview of a content within a communication. In an example of a basic configuration 902, the computing device 900 may include one or more processors 904 and a system memory 906. A memory bus 908 may be used for communication between the processor 904 and the system memory 906. The basic configuration 902 may be illustrated in
Depending on the desired configuration, the processor 904 may be of any type, including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. The processor 904 may include one more levels of caching, such as a level cache memory 912, a processor core 914, and registers 916. The processor core 914 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP Core), or any combination thereof. A memory controller 918 may also be used with the processor 904, or in some implementations, the memory controller 918 may be an internal part of the processor 904.
Depending on the desired configuration, the system memory 906 may be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The system memory 906 may include an operating system 920, a messaging application 922, and a program data 924. The messaging application 922 may retrieve metadata associated with a content in response to a detection of an insertion of a link of the content into a message. An interactive preview of the content may be generated based on the metadata. The interactive preview (that provides actions to manage the interactive preview and the content) may be inserted to the message in proximity to the link. Custom operations of the operations may be executed in response to a transmission of the message. Components of the messaging application 922 (such as a user interface) may also be displayed on a display device associated with the computing device 900. An example of the display device may include a hardware screen that may be communicatively coupled to the computing device 900. The display device may include a touch-based device that detects gestures such as a touch action. The display device may also provide feedback in response to detected gestures (or any other form of input) by transforming a user interface of the messaging application 922, displayed by the touch-based device. The program data 924 may also include, among other data, metadata 928, or the like, as described herein. The metadata 928 may include a preview image, a title of the content, and a summary of the content, among others.
The computing device 900 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 902 and any desired devices and interfaces. For example, a bus/interface controller 930 may be used to facilitate communications between the basic configuration 902 and one or more data storage devices 932 via a storage interface bus 934. The data storage devices 932 may be one or more removable storage devices 936, one or more non-removable storage devices 938, or a combination thereof. Examples of the removable storage and the non-removable storage devices may include magnetic disk devices, such as flexible disk drives and hard-disk drives (HDD), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSD), and tape drives, to name a few. Example computer storage media may include volatile and nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data.
The system memory 906, the removable storage devices 936, and the non-removable storage devices 938 may be examples of computer storage media. Computer storage media may include, but may not be limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD), solid state drives, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by the computing device 900. Any such computer storage media may be part of the computing device 900.
The computing device 900 may also include an interface bus 940 for facilitating communication from various interface devices (for example, one or more output devices 942, one or more peripheral interfaces 944, and one or more communication devices 966) to the basic configuration 902 via the bus/interface controller 930. Some of the example output devices 942 may include a graphics processing unit 948 and an audio processing unit 950, which may be configured to communicate to various external devices, such as a display or speakers via one or more A/V ports 952. One or more example peripheral interfaces 944 may include a serial interface controller 954 or a parallel interface controller 956, which may be configured to communicate with external devices, such as input devices (for example, keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices (for example, printer, scanner, etc.) via one or more I/O ports 958. An example communication device 966 may include a network controller 960, which may be arranged to facilitate communications with one or more other computing devices 962 over a network communication link via one or more communication ports 964. The one or more other computing devices 962 may include servers, client equipment, and comparable devices.
The network communication link may be one example of a communication media. Communication media may be embodied by computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of the modulated data signal characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR), and other wireless media. The term computer-readable media, as used herein, may include both storage media and communication media.
The computing device 900 may be implemented as a part of a general purpose or specialized server, mainframe, or similar computer, which includes any of the above functions. The computing device 900 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.
Example embodiments may also include methods to provide an interactive preview of a content within a communication. These methods may be implemented in any number of ways, including the structures described herein. One such way may be by machine operations, using devices of the type described in the present disclosure. Another optional way may be for one or more of the individual operations of the methods to be performed in conjunction with one or more human operators performing some of the operations while other operations may be performed by machines. These human operators need not be co-located with each other, but each may be with a machine that performs a portion of the program. In other examples, the human interaction may be automated such as by pre-selected criteria that may be machine automated.
Process 1000 begins with operation 1010, where an insertion may be detected of a link of a content into a message that is displayed on a display device. Information such as metadata associated with the content may be retrieved from a content provider (that stores the content) at operation 1020. The metadata may include a preview image, a title of the content, and a summary of the content, among other identifier information associated with the content. At operation 1030, an interactive preview of the content may be generated based on the information. The interactive preview may provide actions to manage the interactive preview and the content. The interactive preview may be inserted into the message, on the display device, in proximity to a location of the insertion of the link at operation 1040. The interactive preview may be placed in proximity to the link. At operation 1050, custom operations associated with the actions (that are selected by a user) may be executed in response to a detection of a transmission of the message.
The operations included in process 1000 are for illustration purposes. A messaging application according to embodiments may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.
According to some examples, a computing device to provide an interactive preview of a content within a communication may be described. The computing device may include a display device, a memory, and a processor coupled to the memory and the display device. The processor may execute a messaging application. The messaging application may be configured to detect an insertion of a link to the content into the message that is displayed on the display device, retrieve information associated with the content from a content provider that stores the content, generate the interactive preview of the content based on the information, where the interactive preview provides one or more actions to manage the interactive preview and the content, insert the interactive preview into the message in proximity to a location of the insertion of the link of the content, and in response to a detection of a transmission of the message, execute one or more operations associated with selected ones of the one or more actions.
According to other examples, the messaging application may be further configured to retrieve metadata of the content as the information, update the metadata of the content with one or more changes resulting from execution of the one or more custom operations, and transmit the updated metadata to the content provider to allow the content provider to synchronize the metadata of the content with the one or more changes. The one or more actions may include: an edit action, an add attachment action, a choose-preview-image action, a remove preview action, a remove-preview-image action, and a change permission action. The interactive preview may be displayed adjacent to the location of the insertion of the link of the content, within the message.
According to further examples, the messaging application may be further configured to detect through the information that the content includes text, select a sample of the text to insert into the interactive preview, where the sample of the text includes a title of the content and a summary of the content, provide an edit action within the interactive preview to allow a user to edit the sample, detect a selection of the edit action by the user, provide one or more controls on the interactive preview to edit the sample, detect one or more changes to the sample within the interactive preview as edited by the user, and transmit the one or more changes to the content provider to allow the content provider to synchronize the text of the content with the one or more changes.
According to other examples, the messaging application may be further configured to extract a preview image of the content from the metadata and display the preview image in the interactive preview. The messaging application may be further configured to detect a selection of a choose-preview-image action by a user, detect a content type of the content from the information, and locate one or more preview images associated with the content type from one or more preview image providers that includes the content provider, display the one or more preview images to allow the user to select one of the one or more preview images to be included in the interactive preview, detect a selection of one of the one or more preview images, and display the selected preview image in the interactive preview. The messaging application may be further configured to detect a selection of a remove-preview-image action by a user and remove a preview image of the content that is displayed in the interactive preview.
According to some examples, a method that is executed on a computing device to provide an interactive preview of a content within a communication may be described. The method may include detecting an insertion of a link to the content into a message, retrieving metadata associated with the content from a content provider that stores the content, generating the interactive preview of the content based on the metadata, where the interactive preview provides one or more actions to manage the interactive preview and the content, inserting the interactive preview into the message in proximity to a location of the insertion of the link, and in response to a detection of a transmission of the message, executing one or more custom operations associated with selected ones of the one or more actions.
According to other examples, the method may further include detecting a selection of a remove-preview action and removing the interactive preview. The method may further include detecting a selection of a rating action, capturing a rating 243 associated with the content 231 as rated by the user, where the rating 243 includes one or more of: a positive rating, a negative rating, and a neutral rating associated with the content 231, displaying the rating 243 within the interactive preview, inserting the rating 243 into the metadata 245, and transmitting the metadata 245 to the content 231 provider to allow the content provider to update the metadata 245 of the content 231 with the rating 243.
According to further examples, the method may further include detecting a selection of a change permission action, capturing a permission setting associated with a receiver of the message to restrict an access of the receiver to the content as provided by the user, inserting the permission setting into the metadata, and transmitting the metadata to the content provider to allow the content provider to update the metadata of the content with the permission setting. The method may further include detecting a selection of a related content action as the one or more actions, querying the content provider to retrieve one or more related content metadata of one or more related contents associated with the content, where the one or more related content metadata include a title and a summary of the one or more related contents, generating a related content section from the one or more related content metadata, and inserting the related content section into the interactive preview.
According to some examples, a computer-readable memory device with instructions stored thereon to provide an interactive preview of a content within a communication may be described. The instructions may include actions that are similar to method described above.
According to some examples, a means to provide an interactive preview of a content within a communication may be described. The means to provide an interactive preview of a content within a communication may include a means to detect an insertion of a link to the content into the message that is displayed on the display device, a means to retrieve information associated with the content from a content provider that stores the content, a means to generate the interactive preview of the content based on the information, where the interactive preview provides one or more actions to manage the interactive preview and the content, a means to insert the interactive preview into the message in proximity to a location of the insertion of the link of the content, and a means to execute one or more operations associated with selected ones of the one or more actions in response to a detection of a transmission of the message.
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7162488 | DeVorchik | Jan 2007 | B2 |
| 7599935 | La Rotonda et al. | Oct 2009 | B2 |
| 7917591 | Vakkalanka | Mar 2011 | B2 |
| 8135617 | Agostino | Mar 2012 | B1 |
| 8140905 | Beaty et al. | Mar 2012 | B2 |
| 8185591 | Lewis | May 2012 | B1 |
| 8201096 | Robert et al. | Jun 2012 | B2 |
| 8204717 | McLaughlin et al. | Jun 2012 | B2 |
| 8516038 | Jalon et al. | Aug 2013 | B2 |
| 8578261 | Gupta et al. | Nov 2013 | B1 |
| 8661036 | Turski | Feb 2014 | B2 |
| 8819701 | Wheeler et al. | Aug 2014 | B2 |
| 8954579 | Do et al. | Feb 2015 | B2 |
| 9021428 | Ajith Kumar et al. | Apr 2015 | B2 |
| 9298355 | Beausoleil | Mar 2016 | B1 |
| 9442903 | Katic | Sep 2016 | B2 |
| 9674583 | Fisher | Jun 2017 | B2 |
| 20020075312 | Amadio | Jun 2002 | A1 |
| 20040205514 | Sommerer et al. | Oct 2004 | A1 |
| 20040225381 | Ritz et al. | Nov 2004 | A1 |
| 20050015678 | Miller | Jan 2005 | A1 |
| 20060069990 | Yozell-Epstein et al. | Mar 2006 | A1 |
| 20060070077 | Erlandson et al. | Mar 2006 | A1 |
| 20060136456 | Jacobs | Jun 2006 | A1 |
| 20060242286 | Hawkins et al. | Oct 2006 | A1 |
| 20070118872 | Song et al. | May 2007 | A1 |
| 20070297029 | Low et al. | Dec 2007 | A1 |
| 20080109712 | McBrearty et al. | May 2008 | A1 |
| 20080282159 | Vanderwende | Nov 2008 | A1 |
| 20090013216 | Abrashkevich et al. | Jan 2009 | A1 |
| 20090055684 | Jamjoom et al. | Feb 2009 | A1 |
| 20090106674 | Bray et al. | Apr 2009 | A1 |
| 20090260060 | Smith | Oct 2009 | A1 |
| 20090313100 | Ingleshwar | Dec 2009 | A1 |
| 20090319618 | Affronti | Dec 2009 | A1 |
| 20100229022 | Anand et al. | Sep 2010 | A1 |
| 20100235395 | Cepuran | Sep 2010 | A1 |
| 20100329642 | Kam | Dec 2010 | A1 |
| 20110153605 | Silverman | Jun 2011 | A1 |
| 20110167469 | Letca et al. | Jul 2011 | A1 |
| 20110302308 | Prodan | Dec 2011 | A1 |
| 20120150989 | Portnoy | Jun 2012 | A1 |
| 20120151379 | Schultz | Jun 2012 | A1 |
| 20120179703 | Ajitomi | Jul 2012 | A1 |
| 20120192064 | Antebi | Jul 2012 | A1 |
| 20120278401 | Meisels | Nov 2012 | A1 |
| 20120278402 | Limont | Nov 2012 | A1 |
| 20120278403 | Costenaro | Nov 2012 | A1 |
| 20120278404 | Meisels | Nov 2012 | A1 |
| 20120284344 | Costenaro | Nov 2012 | A1 |
| 20120284345 | Costenaro | Nov 2012 | A1 |
| 20130198600 | Lockhart | Aug 2013 | A1 |
| 20130275422 | Silber et al. | Oct 2013 | A1 |
| 20130311902 | O'Shaugnessy et al. | Nov 2013 | A1 |
| 20140040226 | Sadhukha et al. | Feb 2014 | A1 |
| 20140189534 | Liu | Jul 2014 | A1 |
| 20140281895 | Tay | Sep 2014 | A1 |
| 20140310222 | Davlos et al. | Oct 2014 | A1 |
| 20140344658 | Srinivasan | Nov 2014 | A1 |
| 20140372877 | Snyder et al. | Dec 2014 | A1 |
| 20150106877 | Meyers | Apr 2015 | A1 |
| 20150134723 | Kansal et al. | May 2015 | A1 |
| 20150143211 | Kaufthal | May 2015 | A1 |
| 20150148328 | El-ahmad et al. | May 2015 | A1 |
| 20150149611 | Lissack | May 2015 | A1 |
| 20150154156 | Meyers, Jr. | Jun 2015 | A1 |
| 20150161123 | Sterling et al. | Jun 2015 | A1 |
| 20150186390 | Katic | Jul 2015 | A1 |
| 20150195182 | Mathur et al. | Jul 2015 | A1 |
| 20150195330 | Lee | Jul 2015 | A1 |
| 20150200885 | Sharp | Jul 2015 | A1 |
| 20150248421 | Hsiao et al. | Sep 2015 | A1 |
| 20160036670 | Sadovsky et al. | Feb 2016 | A1 |
| 20160094499 | Uraizee | Mar 2016 | A1 |
| 20160196013 | Gardenfors | Jul 2016 | A1 |
| 20170090705 | Fern | Mar 2017 | A1 |
| 20170286199 | Soini et al. | Oct 2017 | A1 |
| 20180095814 | Patil et al. | Apr 2018 | A1 |
| 20180097711 | Nallabothula et al. | Apr 2018 | A1 |
| 20200036613 | Nallabothula et al. | Jan 2020 | A1 |
| Entry |
|---|
| “Second Written Opinion Received for PCT Application No. PCT/US2016/023497”, dated Feb. 20, 017, 5 Pages. |
| “The evolution of email”, Published on: Mar. 31, 2014 Available at: http://blogs.office.com/2014/03/31/the-evolution-of-email/. |
| Premick, Justin, “Video in Email: One Step Closer to Reality?”, Retrieved on: Jan. 28, 2015 Available at: http://blog.aweber.com/email-marketing/video-email-closer.htm. |
| Hall, Stephen, “Google+ Hangouts Drive app Discontinued, Replaced with Inline Chat Sharing”, Published on: Nov. 19, 2014 Available at: http://9to5google.com/2014/11/19/google-hangouts-drive-app-discontinued-replaced-with-in line-chat-sharing/. |
| Mathur, Vaibhav, “Yammer Roadmap and Work-like-a-Network”, Published on: May 9, 2014 Available at: http://blogs.perficient.com/microsoft/2014/05/yammer-roadmap-and-work-like-a-network/. |
| “Inline Preview Images”, Published on: Aug. 6, 2013 Available at: https://developers.google.com/speed/pagespeed/module/filter-inline-preview-images. |
| “International Search Report and Written Opinion Issued in PCT Application No. PCT/US2016/023497”, dated Jun. 10, 2016, 10 Pages. |
| “International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2016/023497”, dated Jun. 8, 2017, 6 Pages. |
| “Fix Outlook Account Problems in Office 365”, Retrieved From https://web.archive.org/web/20161220173643/https://portal.office.com/support/help.aspx?sid=sara#/, Retrieved on Jun. 29, 2016, 3 Pages. |
| “IBM Support Assistant”, Retrieved From https://www-01.ibm.com/software/support/isa/, Apr. 13, 2014, 1 Page. |
| “Monitor Health and Performance of your Cloud Computing Resources”, Retrieved From https://www.manageengine.com/products/applications_manager/cloud-monitoring.html, Mar. 31, 2011, 3 Pages. |
| “Monitoring Uptime for your Site”, Retrieved From https://web.archive.org/web/20150906132850/https://docs.acquia.com/network/health, Sep. 6, 2015, 8 Pages. |
| “Support and Recovery Assistant for Office365 Available”, Retrieved From http://www.sharepointgeoff.com/support-recovery-assistant-office365/, Oct. 13, 2015, 4 Pages. |
| “Vmware: Knowledge Base”, Retrieved From https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2129384, Retrieved on Jun. 29, 2016, 4 Pages. |
| “Non Final Office Action Issued in U.S. Appl. No. 15/283,276”, dated May 31, 2018, 16 Pages. |
| “Non Final Office Action Issued in U.S. Appl. No. 15/283,524”, dated Apr. 25, 2018, 17 Pages. |
| Abdul, “5 Cloud Performance Monitoring Tools”, Retrieved From https://web.archive.org/web/20120728074517/http://cloudtweaks.com/2012/07/5-cloud-performance-monitoring-tools/, Jul. 25, 2012, 6 Pages. |
| Bekker, Scott, “Office 365 Tool Tells Partners About Customer Service Outages”, Retrieved From https://rcpmag.com/blogs/scott-bekker/2014/01/office-365-tool-service-outages.aspx, Jan. 29, 2014, 3 Pages. |
| Boucher, Rob, “How to Monitor Cloud Services”, Retrieved From https://web.archive.org/web/20160115211903/https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-monitor/, Jan. 4, 2016, 9 Pages. |
| Hogg, Jason, “Monitor, Diagnose, and Troubleshoot Microsoft Azure Storage”, Retrieved From http://web.archive.org/web/20151001104257/https://azure.microsoft.com/en-in/documentation/articles/storage-monitoring-diagnosing-troubleshooting/,Retrieved on Jun. 29, 2016, 37 Pages. |
| Platon, Oana, “Introduction to Service Fabric Health Monitoring”, Retrieved From https://azure.microsoft.com/en-in/documentation/articles/service-fabric-health-introduction/, Retrieved on Jun. 29, 2016, 15 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 15/283,276”, dated Nov. 20, 2018, 5 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 15/283,524”, dated Dec. 14, 2018, 21 Pages. |
| “Office Action Issued in European Patent Application No. 16712178.9”, dated Jan. 13, 2020, 6 Pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160283447 A1 | Sep 2016 | US |
