US20120198053A1 - Web Based Client/Server Notification Engine - Google Patents
Web Based Client/Server Notification Engine Download PDFInfo
- Publication number
- US20120198053A1 US20120198053A1 US13/196,528 US201113196528A US2012198053A1 US 20120198053 A1 US20120198053 A1 US 20120198053A1 US 201113196528 A US201113196528 A US 201113196528A US 2012198053 A1 US2012198053 A1 US 2012198053A1
- Authority
- US
- United States
- Prior art keywords
- notification
- notifications
- notification engine
- central
- engine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/964—Database arrangement
- Y10S707/966—Distributed
Definitions
- Communication and personal organizer programs typically have the ability to display messages received from one or more of these various sources.
- Some communication programs operate in a web browser, such as MICROSOFT® Office OUTLOOK® Web Access (OWA), Yahoo Mail, AOL Mail, and others.
- OWA MICROSOFT® Office OUTLOOK® Web Access
- Yahoo Mail Yahoo Mail
- AOL Mail AOL Mail
- the server is not contacted until something is needed, such as when the user performs an action that requires the page to be updated or changed.
- the client is not updated with the new content until the user selects an option to perform a manual refresh of the page's contents, or until the user otherwise takes some action causing the client to request that the server provide such updated information.
- a client notification engine of a user interface subscribes to receive notifications from a server side notification engine.
- the client polls the server side notification engine at specified intervals.
- the server side notification engine receives and aggregates notifications about and/or from one or more sources and aggregates them into a collection of relevant notifications at a specified interval.
- These notifications are sent to the client where the different subscriptions originated and are then used by the user interface in the client to update part of the content being displayed as appropriate.
- a status bar is updated to indicate that new communications have been received, such as a new email, a new fax, and/or a new voice mail.
- a folder list is updated to display updated totals, such as the number of unread messages in each folder or the number of total items in each folder.
- the contents of the folder that the user is currently viewing are updated if they changed.
- FIG. 1 is a diagrammatic view of parts of a system of one implementation.
- FIG. 2 is a diagrammatic view of additional parts of the system of FIG. 1 of one implementation.
- FIG. 3 is a high level process flow diagram for one implementation of the system of FIG. 1 .
- FIG. 4 is a logical diagram for one implementation of the system of FIG. 1 illustrating the communications between the client side notification engine and the front end server notification engine for subscribing to and managing notifications.
- FIG. 5 is a process flow diagram for one implementation of the system of FIG. 1 illustrating the stages involved in registering for notifications, collecting notification responses, and processing the response received.
- FIG. 6 is a simulated screen for one implementation of the system for FIG. 1 which illustrates allowing a user to specify messaging notification options.
- FIG. 7 is a simulated screen for one implementation of the system for FIG. 1 which illustrates allowing a user to specify reminder notification options.
- FIG. 8 is a simulated screen for one implementation of the system for FIG. 1 which illustrates an email application with unread totals that were updated based on the subscription process of FIGS. 4 and 5 .
- FIG. 9 is a simulated screen for one implementation of the system for FIG. 1 which illustrates an email application with a status bar that was updated based on the subscription process of FIGS. 4 and 5 .
- FIG. 10 is a simulated screen for one implementation of the system for FIG. 1 which illustrates the new email message that was received when the user selects the New Mail option on the status bar of the simulated screen of FIG. 9 .
- FIG. 11 is a simulated screen for one implementation of the system for FIG. 1 which illustrates the new voice mail message that was received when the user selects the New Voice Mail option on the status bar of the simulated screen of FIG. 9 .
- FIG. 12 is a simulated screen for one implementation of the system for FIG. 1 which illustrates the new fax message that was received when the user selects the New Fax option on the status bar of the simulated screen of FIG. 9 .
- FIG. 13 is a simulated screen for one implementation of the system for FIG. 1 which illustrates the new calendar reminder that was received when the user selects the Reminders option on the status bar of the simulated screen of FIG. 9 .
- the system may be described in the general context as a system that improves the updating of client content in a client/server arrangement.
- a client notification engine of a user interface subscribes to receive notifications from a server side notification engine.
- the client notification engine polls the server side notification engine at a specified interval.
- the server side notification engine receives and aggregates notifications about and/or from one or more sources and/or data stores and aggregates them into a collection of relevant notifications based on the context of the user.
- These notifications are sent to the client where the different subscriptions originated and are then used by the user interface in the client to update part of the content being displayed as appropriate.
- a status bar or other area is updated in the user interface to indicate that new communications have been received, such as a new email, a new fax, and/or a new voice mail.
- a folder list is updated to display updated totals, such as the number of unread messages in each folder or the number of total items in each folder.
- the contents of the folder that the user is currently viewing are updated if they
- folder as used herein is referring to any collection of messages, however they are stored and/or are represented in a graphical user interface.
- folder One of ordinary skill in the art will appreciate that some operating systems do not use the term folder when referring to a collection of messages, and that such scenarios are still covered by the examples illustrated herein that use the term folder.
- the system is a web-based communication application such as MICROSOFT® Office OUTLOOK® Web Access (OWA), Yahoo Mail, or AOL Mail.
- the system is any type of communication application, web-based or not, that is not required to maintain a constant connection to one or more data stores, such as MICROSOFT® Office OUTLOOK® and/or other email clients that support POP3 and/or other disconnected message protocols.
- the system is not a communication application, but serves other purposes, such as project scheduling, travel planning, or others.
- an exemplary computer system to use for implementing one or more parts of the system includes one or more computing devices, such as computing devices 100 , 130 , and/or 150 .
- computing devices 100 , 130 , and/or 150 typically include at least one processing unit ( 102 , 132 , and 152 , respectively) and memory ( 104 , 134 , and 154 , respectively).
- memory 104 , 134 , or 154
- memory may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two.
- This most basic configuration is illustrated in FIG. 1 by lines 106 , 136 , and 156 .
- devices 100 , 130 , and/or 150 may also have additional features/functionality.
- devices 100 , 130 , and/or 150 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape.
- additional storage is illustrated in FIG. 1 by removable storage ( 108 , 138 , and 158 , respectively) and non-removable storage ( 110 , 140 , and 160 , respectively).
- Computer storage media includes 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.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by device 100 , 130 , and/or 150 . Any such computer storage media may be part of device 100 , 130 , and/or 150 .
- Computing devices 100 , 130 , and/or 150 include one or more communication connections that allow computing devices 100 , 130 , and/or 150 to communicate with each other and/or one or more other computing devices over network 116 .
- Communications connection(s) 114 , 144 , and 164 are examples of communication media.
- Communication media typically embodies 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 includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- wireless media such as acoustic, RF, infrared and other wireless media.
- computer readable media includes both storage media and communication media.
- computing device 100 is a client computer that communicates with front end server computer 130 using communication connection 114 and 144 over network 116 .
- user interface 118 of client computing device 100 communicates with notification engine 148 on server computing device 130 to subscribe to notifications and receive updated information.
- Front end server computer 130 communicates with back end server computing device 150 by network 116 using communication connections 144 and 164 .
- user interface 118 of client computing device 100 is a browser-based user interface, such as MICROSOFT® Office OUTLOOK® Web Access (OWA), server computing device 130 is a web server, and back end server computing device 150 hosts a data store for a communication program, such as MICROSOFT® Exchange.
- user interface 118 of client computing device 100 is a user interface included in an executable program located on client computing device 100 , such as MICROSOFT® Office OUTLOOK®, MICROSOFT® Project, or Lotus Notes.
- front end server computer 130 and back end server computing device 150 can be the same computer in alternate embodiments.
- additional back end server computing device 150 could also be used, such as where multiple data stores are accessed by front end server computing device 130 .
- Computing devices 100 , 130 , and 150 may also have input device(s) ( 112 , 142 , and 162 , respectively) such as keyboard, mouse, pen, voice input device, touch input device, etc.
- input device(s) 112 , 142 , and 162 , respectively
- output device(s) 111 , 141 , and 161 , respectively
- display, speakers, printer, etc. may also be included.
- Notification engine 119 of user interface 118 on client computing device 100 communicates with central notification engine 148 of front end server computing device 130 to subscribe to notifications.
- central notification engine 148 has a notification manager class that contains methods for creating one or more event queues, deleting an event queue, flushing and/or disposing of an event queue, creating a condition advisor, deleting a condition advisor, flushing and/or disposing of a condition advisor, creating a folder count advisor, deleting a folder count advisor, flushing and/or disposing of a folder count advisor, and/or other methods for performing other operations.
- Central notification engine 148 has an event queue object 180 , a condition advisor object 182 , and a count advisor object 184 that are operable to communicate with one or more data stores 168 on one or more back end server computing devices 150 to obtain updated information at specified data gathering intervals.
- data stores include one or more message stores or products such as MICROSOFT® Exchange, a POP3 or IMAP email data store, a fax data store, and/or another file or database.
- the updated information is then aggregated by central notification engine 148 and returned to notification engine 119 on client computing device 100 for further processing by user interface 118 .
- only relevant information is returned, such as those specific to the context in which the user is working. As one non-limiting example, if the user is currently viewing his or her calendar, then detailed information about the calendar would be returned, but detailed information about the contents of the inbox would not be returned. In other implementations, more information is returned.
- the process of FIG. 3 is at least partially implemented in the operating logic of computing device 100 , 130 , and/or 150 .
- the process begins at start point 200 with the user logging into an email or other application (stage 202 ).
- Client computing device 100 retrieves notification settings for the particular user (stage 204 ). If notifications are not enabled for the particular user (decision point 206 ), then the process ends at end point 214 . If notifications are enabled for the particular user (decision point 206 ), then notification engine 119 of client computing device 100 communicates with central notification engine 148 on front end server computing device 130 to register for notifications (stage 208 ).
- Notification engine 119 polls for and receives notifications that were aggregated by central notification service about what, if anything changed, updated totals (such as unread item counts), and/or some details about the changed and/or new content (stage 210 ).
- the details about the changes and status of the various data that are received by the client are included in one or more text files, such as XML.
- the details are received in a scripting language format, such as JavaScript or VBScript, where the script is executed and/or consumed by the notification engine on the client.
- the details are received in another file type or format for interpretation, execution, and/or display on the client.
- User interface 118 interprets the information received from the central notification engine and updates the user interface display appropriately (stage 212 ).
- folder unread counts are updated to indicate the number of unread messages contained in that folder.
- a status or indicator bar in the user interface is updated to display whether there are new reminders and/or new messages, such as new email, fax, voice messages, and/or reminders.
- a custom-defined rule can be defined by the user for display in the status bar, such as to notify the user of any messages received from the boss.
- a folder the user is currently viewing is updated with any new content relevant to the particular display.
- other content can also be stored locally for quick retrieval once the user changes context where the information would be needed. The process then ends at end point 214 .
- FIG. 4 a logical diagram describing the process for subscribing to and managing notifications in one implementation are illustrated.
- the process of FIG. 4 is at least partially implemented in the operating logic of computing device 100 , 130 , and/or 150 .
- Client computing device 100 registers for one or more notifications, such as reminder notifications (stage 240 ), folder tree unread count notifications (stage 242 ), folder content change notifications (stage 244 ), and/or other notifications (stage 246 ) with client side notification engine 248 ( 119 on FIG. 2 ).
- Client side notification engine 248 registers for notifications with front end server notification engine 256 ( 148 on FIG. 2 ) and polls regularly (stage 252 ).
- Front end server notification engine 256 manages event queues 258 , condition advisors 260 , folder count advisor 262 , and/or other information tracking objects 264 .
- Front end server notification engine 256 registers for notifications (stage 266 ) with one or more data stores 168 on back end server computing device(s) 268 ( 150 on FIG. 2 ).
- Back end server computing device 268 updates front end server notification engine 256 with notifications periodically (stage 270 ).
- the event queue(s), content advisors, and item count advisors are updated accordingly.
- front end server notification engine 256 combines the responses for all notification requests (stage 254 ) and returns only the necessary ones (such as the relevant ones) to the client side notification engine 248 .
- the client side notification engine 248 distributes notifications to user interface components and performs the necessary actions (stage 250 ), such as to update the display.
- FIG. 5 the stages involved in registering for notifications, collecting notification responses, and processing the response received in one implementation are illustrated.
- the process of FIG. 5 is at least partially implemented in the operating logic of computing device 100 , 130 , and/or 150 .
- the process begins at start point 300 with the user logging in to the application (stage 302 ).
- Client side notification engine 248 of user interface 118 registers for notifications with the central notification engine 148 .
- central notification engine 148 creates folder modified condition advisors for all folders, event queues for new notifications, such as in the Inbox, and/or folder item count advisors for some or all of the folders (stage 304 ).
- the client notification engine 119 checks to determine whether the polling interval time has passed (decision 308 ). The client notification engine 119 waits until the polling interval passes by (decision point 308 ) to poll the central notification engine 148 for notifications (stage 310 ). If there are notifications to report (decision point 312 ), then the central notification engine 148 generates a response based on the information in the event queue(s), condition advisors, and folder unread count advisor(s) and sends them to the client side notification engine 248 for further processing by the user interface 118 (stage 316 ). User interface 118 interprets and/or otherwise executes the response, and updates the appropriate user interface views (stage 318 ).
- the central notification engine 148 If there are no notifications to report (decision point 312 ), then the central notification engine 148 generates an empty or blank response and sends it to the client side notification engine 248 (stage 314 ). The process then repeats for each polling interval (decision point 308 ) or until the user session times out or the user closes the application (decision point 306 ). If the session times out or the user otherwise ends the session or application (decision point 306 ), such as by closing the browser or program, then the event queue, condition advisors, and folder unread count advisor objects are destroyed (stage 320 ) to free up system resources. The process then ends at end point 322 .
- FIG. 6 is a simulated screen 340 for one implementation of the system for FIG. 1 which illustrates allowing a user to specify messaging notification options.
- the user can select whether to enable or disable options that display a notification message when new mail arrives 342 , display a notification message when a new voice mail arrives 344 , display a notification when new voice message arrives 346 , and/or to play a sound when new message arrives 348 .
- any one or more of these options are enabled (decision point 206 on FIG. 3 )
- user interface 118 of client computing device 100 registers for messaging event notifications with central notification engine 148 on front end server computing device 130 .
- FIG. 7 is a simulated screen 350 for one implementation of the system for FIG. 1 which illustrates allowing a user to specify reminder notification options.
- the user can select whether to enable or disable options that show reminder alerts for calendar items 352 , show reminder alerts for task items 354 , plays a sound when a reminder is due 356 , and/or to set the default reminder time frame 358 .
- any one or more of options 352 , 354 , or 356 are enabled (decision point 206 on FIG. 3 )
- user interface 118 of client computing device 100 registers for reminder event notifications with central notification engine 148 on front end server computing device 130 .
- user interface 118 After messaging and/or reminder notifications are registered with central notification engine 148 , user interface 118 then waits for the polling time to pass by (decision point 308 ), polls for and receives aggregated notifications from the central notification engine 148 (stage 310 ) and processes the response to update the user interface accordingly (stage 318 ).
- FIG. 8 is a simulated screen 360 for one implementation of the system for FIG. 1 which illustrates an email application with unread totals that were updated based on the event subscription process of FIGS. 3-5 .
- Simulated screen 360 is a browser-based communication/personal organizer application that has various folders, such as Inbox 364 , one or more user defined folder(s), Deleted Items 366 , Calendar 368 , and/or other folders, for displaying information to the user and allowing the user to manage his or her information and/or schedule.
- folder counts are updated, such as “(7)” for Inbox 364 , and/or others shown on screen 360 .
- the totals represent the total number of unread items in the folder.
- the total represents the total number of items in the folder.
- the user interface can be updated automatically to display new content that is relevant to the context that the user is working in. For example, since the user has the Inbox folder 364 selected, new messages can be displayed in message area 369 based upon a sort order setting specified by the user or by a system default setting.
- a status bar is updated based on the aggregated notifications received from central notification engine (stage 210 ).
- status bar 377 on simulated screen 370 includes four notification messages: New Email 375 , New Voice Mail 371 , New Fax 372 , and New Reminder 373 that represent the type of new messages and/or reminders (e.g. calendar and/or task reminders) that have been received by the user.
- New Reminder 373 represents the type of new messages and/or reminders (e.g. calendar and/or task reminders) that have been received by the user.
- Other variations are also possible that include some or additional message and/or reminder notifications than these.
- a Help option 374 is displayed in the status bar.
- the New Email notification message 382 when the user selects the New Email notification message 382 (or a particular notification) in the status bar of screen 380 , a snippet of the message 384 is shown near the status bar area to give the user a preview of the message.
- the New Email notification message 382 (or selected notification) then disappears after the user selects it from the status bar area.
- the New Email notification message 382 (or selected notification) is displayed until the user accesses the message in the Inbox folder and causes the status of the message to change to “read”.
- the snippet 384 can be displayed for a specified period of time (such as 5 seconds) when the screen is first updated.
- contents 386 of inbox folder are updated to include the new message(s).
- contents 386 of inbox folder are updated automatically when the aggregated notifications are received from the central notification engine 148 .
- Other variations are also possible that include combinations of these, fewer, and/or additional variations.
- FIGS. 11-13 are simulated screens ( 390 , 400 , and 410 , respectively) for one implementation of the system for FIG. 1 which illustrate what happens in the status bar area when the user selects the other options.
- simulated screen 390 of FIG. 11 illustrates what happens in the status bar area when the user selects the New Voice Mail notification message 392 .
- a snippet of the voice mail message 394 appears near the status bar and includes details such as the caller's phone number and the length of the message.
- Simulated screen 400 of FIG. 12 illustrates an example of what happens in the status bar area when the user selects the New Fax notification message 402 .
- a snippet of the message 404 appears near the status bar and includes details such as the sender's fax number and/or the number of pages received.
- simulated screen 410 of FIG. 13 illustrates an example of what happens in the status bar area when the user selects the New Reminders notification message 412 .
- a snippet of the reminder message 414 appears near the status bar and additional details about the appointment and/or task.
- calendar and task reminders are grouped together in the same reminder area.
- calendar reminders have a separate notification message on the status bar from task reminders.
- simulated screens 9 - 13 numerous other variations are also possible for determining when and where to display the respective snippet, if at all. In some implementations, part or all of the details related to the message and/or reminder are displayed and/or audibly rendered to the user in some fashion.
- FIGS. 7-13 are for purposes of illustration only, and are not limiting in nature.
- other variations are also possible, such as using the technologies and techniques discussed herein for receiving updated content from a server in applications other than communications programs, such as from a project planning application, such as MICROSOFT® Project.
- Other examples can include any type of application that does not maintain a constant connection with the server while a user is accessing the application.
Abstract
Various technologies and techniques improve the updating of client content in a client/server arrangement. A client notification engine of a user interface subscribes to receive notifications from a central server side notification engine. The client notification engine polls the server side notification engine at a specified interval. The server side notification engine receives and aggregates notifications about and/or from one or more sources and aggregates them into a collection of relevant notifications. These notifications are sent to the client where the different subscriptions originated and are then used by the user interface in the client to update part of the content being displayed as appropriate.
Description
- This application is a continuation of application Ser. No. 11/338,039, filed Jan. 24, 2006, which is incorporated herein by reference.
- In today's world of technology, it has become easier than ever before to communicate with people using one or more of a variety of communication methods, such as email, telephone, fax, instant messaging, and so on. Communication and personal organizer programs typically have the ability to display messages received from one or more of these various sources. Some communication programs operate in a web browser, such as MICROSOFT® Office OUTLOOK® Web Access (OWA), Yahoo Mail, AOL Mail, and others. With such disconnected applications, the server is not contacted until something is needed, such as when the user performs an action that requires the page to be updated or changed. When new communication messages are received on the server, the client is not updated with the new content until the user selects an option to perform a manual refresh of the page's contents, or until the user otherwise takes some action causing the client to request that the server provide such updated information.
- Various technologies and techniques are disclosed that improve the updating of client content in a client/server arrangement. A client notification engine of a user interface, such as a communication management or email application, subscribes to receive notifications from a server side notification engine. The client polls the server side notification engine at specified intervals. The server side notification engine receives and aggregates notifications about and/or from one or more sources and aggregates them into a collection of relevant notifications at a specified interval. These notifications are sent to the client where the different subscriptions originated and are then used by the user interface in the client to update part of the content being displayed as appropriate. In one implementation, a status bar is updated to indicate that new communications have been received, such as a new email, a new fax, and/or a new voice mail. Alternatively or additionally, a folder list is updated to display updated totals, such as the number of unread messages in each folder or the number of total items in each folder. Alternatively or additionally, the contents of the folder that the user is currently viewing are updated if they changed.
- This Summary was 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 identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
-
FIG. 1 is a diagrammatic view of parts of a system of one implementation. -
FIG. 2 is a diagrammatic view of additional parts of the system ofFIG. 1 of one implementation. -
FIG. 3 is a high level process flow diagram for one implementation of the system ofFIG. 1 . -
FIG. 4 is a logical diagram for one implementation of the system ofFIG. 1 illustrating the communications between the client side notification engine and the front end server notification engine for subscribing to and managing notifications. -
FIG. 5 is a process flow diagram for one implementation of the system ofFIG. 1 illustrating the stages involved in registering for notifications, collecting notification responses, and processing the response received. -
FIG. 6 is a simulated screen for one implementation of the system forFIG. 1 which illustrates allowing a user to specify messaging notification options. -
FIG. 7 is a simulated screen for one implementation of the system forFIG. 1 which illustrates allowing a user to specify reminder notification options. -
FIG. 8 is a simulated screen for one implementation of the system forFIG. 1 which illustrates an email application with unread totals that were updated based on the subscription process ofFIGS. 4 and 5 . -
FIG. 9 is a simulated screen for one implementation of the system forFIG. 1 which illustrates an email application with a status bar that was updated based on the subscription process ofFIGS. 4 and 5 . -
FIG. 10 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new email message that was received when the user selects the New Mail option on the status bar of the simulated screen ofFIG. 9 . -
FIG. 11 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new voice mail message that was received when the user selects the New Voice Mail option on the status bar of the simulated screen ofFIG. 9 . -
FIG. 12 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new fax message that was received when the user selects the New Fax option on the status bar of the simulated screen ofFIG. 9 . -
FIG. 13 is a simulated screen for one implementation of the system forFIG. 1 which illustrates the new calendar reminder that was received when the user selects the Reminders option on the status bar of the simulated screen ofFIG. 9 . - For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope is thereby intended. Any alterations and further modifications in the described embodiments, and any further applications of the principles as described herein are contemplated as would normally occur to one skilled in the art.
- The system may be described in the general context as a system that improves the updating of client content in a client/server arrangement. A client notification engine of a user interface subscribes to receive notifications from a server side notification engine. The client notification engine polls the server side notification engine at a specified interval. The server side notification engine receives and aggregates notifications about and/or from one or more sources and/or data stores and aggregates them into a collection of relevant notifications based on the context of the user. These notifications are sent to the client where the different subscriptions originated and are then used by the user interface in the client to update part of the content being displayed as appropriate. A status bar or other area is updated in the user interface to indicate that new communications have been received, such as a new email, a new fax, and/or a new voice mail. Alternatively or additionally, a folder list is updated to display updated totals, such as the number of unread messages in each folder or the number of total items in each folder. Alternatively or additionally, the contents of the folder that the user is currently viewing are updated if they changed.
- The term folder as used herein is referring to any collection of messages, however they are stored and/or are represented in a graphical user interface. One of ordinary skill in the art will appreciate that some operating systems do not use the term folder when referring to a collection of messages, and that such scenarios are still covered by the examples illustrated herein that use the term folder.
- In one implementation, the system is a web-based communication application such as MICROSOFT® Office OUTLOOK® Web Access (OWA), Yahoo Mail, or AOL Mail. In another implementation, the system is any type of communication application, web-based or not, that is not required to maintain a constant connection to one or more data stores, such as MICROSOFT® Office OUTLOOK® and/or other email clients that support POP3 and/or other disconnected message protocols. In yet another implementation, the system is not a communication application, but serves other purposes, such as project scheduling, travel planning, or others.
- As shown in
FIG. 1 , an exemplary computer system to use for implementing one or more parts of the system includes one or more computing devices, such ascomputing devices computing devices FIG. 1 bylines - Additionally,
devices devices FIG. 1 by removable storage (108, 138, and 158, respectively) and non-removable storage (110, 140, and 160, respectively). Computer storage media includes 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. Memory (104, 134, and 154), removable storage (108, 138, and 158), and non-removable storage (110, 140, and 160) are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed bydevice device -
Computing devices computing devices network 116. Communications connection(s) 114, 144, and 164 are examples of communication media. Communication media typically embodies 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 includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media. - In one implementation,
computing device 100 is a client computer that communicates with frontend server computer 130 usingcommunication connection network 116. In such an implementation,user interface 118 ofclient computing device 100 communicates withnotification engine 148 onserver computing device 130 to subscribe to notifications and receive updated information. Frontend server computer 130 communicates with back endserver computing device 150 bynetwork 116 usingcommunication connections - In one implementation,
user interface 118 ofclient computing device 100 is a browser-based user interface, such as MICROSOFT® Office OUTLOOK® Web Access (OWA),server computing device 130 is a web server, and back endserver computing device 150 hosts a data store for a communication program, such as MICROSOFT® Exchange. In another implementation,user interface 118 ofclient computing device 100 is a user interface included in an executable program located onclient computing device 100, such as MICROSOFT® Office OUTLOOK®, MICROSOFT® Project, or Lotus Notes. It will be appreciated that frontend server computer 130 and back endserver computing device 150 can be the same computer in alternate embodiments. Furthermore, it will be appreciated that additional back endserver computing device 150 could also be used, such as where multiple data stores are accessed by front endserver computing device 130. -
Computing devices - Turning now to
FIG. 2 with continued reference toFIG. 1 , a diagrammatic view of additional parts of system ofFIG. 1 of one implementation are illustrated. The same reference numerals are used onFIG. 2 for those items that are the same as onFIG. 1 .Notification engine 119 ofuser interface 118 onclient computing device 100 communicates withcentral notification engine 148 of front endserver computing device 130 to subscribe to notifications. In one implementation,central notification engine 148 has a notification manager class that contains methods for creating one or more event queues, deleting an event queue, flushing and/or disposing of an event queue, creating a condition advisor, deleting a condition advisor, flushing and/or disposing of a condition advisor, creating a folder count advisor, deleting a folder count advisor, flushing and/or disposing of a folder count advisor, and/or other methods for performing other operations. -
Central notification engine 148 has anevent queue object 180, acondition advisor object 182, and acount advisor object 184 that are operable to communicate with one ormore data stores 168 on one or more back endserver computing devices 150 to obtain updated information at specified data gathering intervals. A few non-limiting examples of such data stores include one or more message stores or products such as MICROSOFT® Exchange, a POP3 or IMAP email data store, a fax data store, and/or another file or database. The updated information is then aggregated bycentral notification engine 148 and returned tonotification engine 119 onclient computing device 100 for further processing byuser interface 118. In one implementation, only relevant information is returned, such as those specific to the context in which the user is working. As one non-limiting example, if the user is currently viewing his or her calendar, then detailed information about the calendar would be returned, but detailed information about the contents of the inbox would not be returned. In other implementations, more information is returned. - Turning now to
FIG. 3 with continued reference toFIGS. 1 and 2 , a high level process flow for one implementation is presented. In one form, the process ofFIG. 3 is at least partially implemented in the operating logic ofcomputing device start point 200 with the user logging into an email or other application (stage 202).Client computing device 100 retrieves notification settings for the particular user (stage 204). If notifications are not enabled for the particular user (decision point 206), then the process ends atend point 214. If notifications are enabled for the particular user (decision point 206), thennotification engine 119 ofclient computing device 100 communicates withcentral notification engine 148 on front endserver computing device 130 to register for notifications (stage 208). - A few non-limiting examples of notifications include email messages, calendar reminders, task reminders, folder content changes, folder count totals, etc.
Notification engine 119 polls for and receives notifications that were aggregated by central notification service about what, if anything changed, updated totals (such as unread item counts), and/or some details about the changed and/or new content (stage 210). - In one implementation, the details about the changes and status of the various data that are received by the client are included in one or more text files, such as XML. In another implementation, the details are received in a scripting language format, such as JavaScript or VBScript, where the script is executed and/or consumed by the notification engine on the client. In yet another implementation, the details are received in another file type or format for interpretation, execution, and/or display on the client.
User interface 118 interprets the information received from the central notification engine and updates the user interface display appropriately (stage 212). In one implementation, folder unread counts are updated to indicate the number of unread messages contained in that folder. Alternatively or additionally, a status or indicator bar in the user interface is updated to display whether there are new reminders and/or new messages, such as new email, fax, voice messages, and/or reminders. Alternatively or additionally, a custom-defined rule can be defined by the user for display in the status bar, such as to notify the user of any messages received from the boss. Alternatively or additionally, a folder the user is currently viewing is updated with any new content relevant to the particular display. Alternatively or additionally, other content can also be stored locally for quick retrieval once the user changes context where the information would be needed. The process then ends atend point 214. - Turning now to
FIG. 4 with continued reference toFIGS. 1 and 2 , a logical diagram describing the process for subscribing to and managing notifications in one implementation are illustrated. In one form, the process ofFIG. 4 is at least partially implemented in the operating logic ofcomputing device Client computing device 100 registers for one or more notifications, such as reminder notifications (stage 240), folder tree unread count notifications (stage 242), folder content change notifications (stage 244), and/or other notifications (stage 246) with client side notification engine 248 (119 onFIG. 2 ). Clientside notification engine 248 registers for notifications with front end server notification engine 256 (148 onFIG. 2 ) and polls regularly (stage 252). Front endserver notification engine 256 managesevent queues 258,condition advisors 260,folder count advisor 262, and/or other information tracking objects 264. - Front end
server notification engine 256 registers for notifications (stage 266) with one ormore data stores 168 on back end server computing device(s) 268 (150 onFIG. 2 ). Back endserver computing device 268 updates front endserver notification engine 256 with notifications periodically (stage 270). In other words, the event queue(s), content advisors, and item count advisors are updated accordingly. In one implementation, front endserver notification engine 256 combines the responses for all notification requests (stage 254) and returns only the necessary ones (such as the relevant ones) to the clientside notification engine 248. The clientside notification engine 248 distributes notifications to user interface components and performs the necessary actions (stage 250), such as to update the display. - Turning now to
FIG. 5 with continued reference toFIGS. 1 and 2 , the stages involved in registering for notifications, collecting notification responses, and processing the response received in one implementation are illustrated. In one form, the process ofFIG. 5 is at least partially implemented in the operating logic ofcomputing device start point 300 with the user logging in to the application (stage 302). Clientside notification engine 248 ofuser interface 118 registers for notifications with thecentral notification engine 148. In one implementation,central notification engine 148 creates folder modified condition advisors for all folders, event queues for new notifications, such as in the Inbox, and/or folder item count advisors for some or all of the folders (stage 304). If the session has not timed out or otherwise ended (decision point 306), then theclient notification engine 119 checks to determine whether the polling interval time has passed (decision 308). Theclient notification engine 119 waits until the polling interval passes by (decision point 308) to poll thecentral notification engine 148 for notifications (stage 310). If there are notifications to report (decision point 312), then thecentral notification engine 148 generates a response based on the information in the event queue(s), condition advisors, and folder unread count advisor(s) and sends them to the clientside notification engine 248 for further processing by the user interface 118 (stage 316).User interface 118 interprets and/or otherwise executes the response, and updates the appropriate user interface views (stage 318). - If there are no notifications to report (decision point 312), then the
central notification engine 148 generates an empty or blank response and sends it to the client side notification engine 248 (stage 314). The process then repeats for each polling interval (decision point 308) or until the user session times out or the user closes the application (decision point 306). If the session times out or the user otherwise ends the session or application (decision point 306), such as by closing the browser or program, then the event queue, condition advisors, and folder unread count advisor objects are destroyed (stage 320) to free up system resources. The process then ends atend point 322. -
FIG. 6 is asimulated screen 340 for one implementation of the system forFIG. 1 which illustrates allowing a user to specify messaging notification options. The user can select whether to enable or disable options that display a notification message when new mail arrives 342, display a notification message when a new voice mail arrives 344, display a notification when new voice message arrives 346, and/or to play a sound when new message arrives 348. In one implementation, if any one or more of these options are enabled (decision point 206 onFIG. 3 ), thenuser interface 118 ofclient computing device 100 registers for messaging event notifications withcentral notification engine 148 on front endserver computing device 130. -
FIG. 7 is asimulated screen 350 for one implementation of the system forFIG. 1 which illustrates allowing a user to specify reminder notification options. The user can select whether to enable or disable options that show reminder alerts forcalendar items 352, show reminder alerts fortask items 354, plays a sound when a reminder is due 356, and/or to set the defaultreminder time frame 358. In one implementation, if any one or more ofoptions decision point 206 onFIG. 3 ), thenuser interface 118 ofclient computing device 100 registers for reminder event notifications withcentral notification engine 148 on front endserver computing device 130. - After messaging and/or reminder notifications are registered with
central notification engine 148,user interface 118 then waits for the polling time to pass by (decision point 308), polls for and receives aggregated notifications from the central notification engine 148 (stage 310) and processes the response to update the user interface accordingly (stage 318). - Non-limiting examples of how the
user interface 118 can be updated based on the aggregated notifications are shown in simulated screens 8-13.FIG. 8 is asimulated screen 360 for one implementation of the system forFIG. 1 which illustrates an email application with unread totals that were updated based on the event subscription process ofFIGS. 3-5 .Simulated screen 360 is a browser-based communication/personal organizer application that has various folders, such asInbox 364, one or more user defined folder(s),Deleted Items 366,Calendar 368, and/or other folders, for displaying information to the user and allowing the user to manage his or her information and/or schedule. Upon receiving aggregated notifications from central notification engine (stage 210), folder counts are updated, such as “(7)” forInbox 364, and/or others shown onscreen 360. In one implementation, the totals represent the total number of unread items in the folder. In another implementation, the total represents the total number of items in the folder. Alternatively or additionally, the user interface can be updated automatically to display new content that is relevant to the context that the user is working in. For example, since the user has theInbox folder 364 selected, new messages can be displayed inmessage area 369 based upon a sort order setting specified by the user or by a system default setting. - As shown in
FIG. 9 , in one implementation, a status bar is updated based on the aggregated notifications received from central notification engine (stage 210). For example,status bar 377 onsimulated screen 370 includes four notification messages:New Email 375,New Voice Mail 371,New Fax 372, andNew Reminder 373 that represent the type of new messages and/or reminders (e.g. calendar and/or task reminders) that have been received by the user. Other variations are also possible that include some or additional message and/or reminder notifications than these. In one implementation, aHelp option 374 is displayed in the status bar. - Turning now to
FIG. 10 , in one implementation, when the user selects the New Email notification message 382 (or a particular notification) in the status bar ofscreen 380, a snippet of themessage 384 is shown near the status bar area to give the user a preview of the message. In one implementation, the New Email notification message 382 (or selected notification) then disappears after the user selects it from the status bar area. In another implementation, the New Email notification message 382 (or selected notification) is displayed until the user accesses the message in the Inbox folder and causes the status of the message to change to “read”. - Instead of or in addition to showing a snippet of the
message 384 when the user selects NewEmail notification message 382, thesnippet 384 can be displayed for a specified period of time (such as 5 seconds) when the screen is first updated. In another implementation, when the user selects NewEmail notification message 382,contents 386 of inbox folder are updated to include the new message(s). In yet another implementation,contents 386 of inbox folder are updated automatically when the aggregated notifications are received from thecentral notification engine 148. Other variations are also possible that include combinations of these, fewer, and/or additional variations. - Similarly to
FIG. 10 ,FIGS. 11-13 are simulated screens (390, 400, and 410, respectively) for one implementation of the system forFIG. 1 which illustrate what happens in the status bar area when the user selects the other options. For example,simulated screen 390 ofFIG. 11 illustrates what happens in the status bar area when the user selects the New VoiceMail notification message 392. A snippet of thevoice mail message 394 appears near the status bar and includes details such as the caller's phone number and the length of the message.Simulated screen 400 ofFIG. 12 illustrates an example of what happens in the status bar area when the user selects the NewFax notification message 402. A snippet of themessage 404 appears near the status bar and includes details such as the sender's fax number and/or the number of pages received. Alternatively or additionally,simulated screen 410 ofFIG. 13 illustrates an example of what happens in the status bar area when the user selects the NewReminders notification message 412. A snippet of thereminder message 414 appears near the status bar and additional details about the appointment and/or task. In one implementation, calendar and task reminders are grouped together in the same reminder area. In another implementation, calendar reminders have a separate notification message on the status bar from task reminders. - With respect to simulated screens 9-13, numerous other variations are also possible for determining when and where to display the respective snippet, if at all. In some implementations, part or all of the details related to the message and/or reminder are displayed and/or audibly rendered to the user in some fashion.
- The examples in
FIGS. 7-13 are for purposes of illustration only, and are not limiting in nature. For example, other variations are also possible, such as using the technologies and techniques discussed herein for receiving updated content from a server in applications other than communications programs, such as from a project planning application, such as MICROSOFT® Project. Other examples can include any type of application that does not maintain a constant connection with the server while a user is accessing the application. - 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. All equivalents, changes, and modifications that come within the spirit of the implementations as described herein and/or by the following claims are desired to be protected.
- For example, a person of ordinary skill in the computer software art will recognize that the client and/or server arrangements, user interface screen content, and/or data layouts as described in the examples discussed herein could be organized differently on one or more computers to include fewer or additional options or features than as portrayed in the examples.
Claims (20)
1. A method for improving client-side content updates comprising:
sending a registration from a computing system to a central notification engine to register for update notifications, the registration including information identifying a plurality of folders to monitor for changes;
after sending the registration, sending a request from the computing system to the central notification engine for update notifications associated with the plurality of folders identified by the registration;
if the central notification engine has notifications to report, receiving a notification response from the central notification engine, the notification response including an aggregation of updates from a first data store and a second data store;
if the central notification engine has no notifications to report, receiving a notification response from the central notification engine after a polling interval expires, the notification response indicating that no updates have occurred.
2. The method of claim 1 , wherein the updates include two or more of the following: email, calendar, contacts, notes, or tasks.
3. The method of claim 1 , wherein the request comprises a polling request.
4. The method of claim 1 , wherein the computing system includes a client-side notification engine.
5. The method of claim 1 , further comprising, if the notification response includes the aggregation of updates, updating a user interface in response to receiving the notification response.
6. The method of claim 1 , wherein, if the central notification engine has notifications to report, the notification response includes a list of updated folders, the list identifying folders that have updated contents.
7. The method of claim 1 , wherein if the central notification engine has no notifications to report, the notification is an empty response message.
8. The method of claim 1 , wherein the notification response is represented in XML.
9. The method of claim 1 , further comprising generating a visible indication of the notification in a status bar on a display.
10. The method of claim 1 , wherein if the central notification engine has notifications to report, the notification response is received after the polling interval expires.
11. The method of claim 1 , wherein the aggregation of updates includes a number of items in at least one of the plurality of folders identified by the registration.
12. A method executed at a central notification engine for updating content at a computing system, the method comprising:
receiving a registration from a computing system at a central notification engine, the registration including information identifying a plurality of folders to monitor for changes;
after receiving the registration, receiving a request from the computing system at the central notification engine for update notifications associated with the plurality of folders identified by the registration;
if the central notification engine has notifications to report, transmitting a notification response from the central notification engine, the notification response including an aggregation of updates from a first data store and a second data store;
if the central notification engine has no notifications to report, transmitting a notification response from the central notification engine after a polling interval expires, the notification response indicating that no updates have occurred.
13. The method of claim 12 , wherein the notifications are selected from the group consisting of an email message, a fax message, a voice mail message, and a reminder message.
14. The method of claim 12 , further comprising generating the notification response at the central notification engine, the notification response including information from at least one of a condition advisor and an item count advisor.
15. The method of claim 14 , further comprising checking at least the condition advisor and the item count advisor to determine whether there are notifications to report.
16. The method of claim 14 , wherein the condition advisor and item count advisor are associated with at least one of the plurality of folders identified by the registration.
17. The method of claim 12 , wherein if the central notification engine has no notifications to report, the notification is an empty response message transmitted to the computing system.
18. The method of claim 12 , wherein if the central notification engine has notifications to report, the notification response is transmitted after the polling interval expires.
19. The method of claim 12 , wherein the aggregation of updates includes a number of items in at least one of the plurality of folders identified by the registration.
20. The method of claim 12 , wherein the first data store and the second data store comprise first and second folders from among the plurality of folders identified in the request.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/196,528 US20120198053A1 (en) | 2006-01-24 | 2011-08-02 | Web Based Client/Server Notification Engine |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/338,039 US8015152B2 (en) | 2006-01-24 | 2006-01-24 | Web based client/server notification engine |
US13/196,528 US20120198053A1 (en) | 2006-01-24 | 2011-08-02 | Web Based Client/Server Notification Engine |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/338,039 Continuation US8015152B2 (en) | 2006-01-24 | 2006-01-24 | Web based client/server notification engine |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120198053A1 true US20120198053A1 (en) | 2012-08-02 |
Family
ID=38429689
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/338,039 Active 2027-01-03 US8015152B2 (en) | 2006-01-24 | 2006-01-24 | Web based client/server notification engine |
US13/196,528 Abandoned US20120198053A1 (en) | 2006-01-24 | 2011-08-02 | Web Based Client/Server Notification Engine |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/338,039 Active 2027-01-03 US8015152B2 (en) | 2006-01-24 | 2006-01-24 | Web based client/server notification engine |
Country Status (1)
Country | Link |
---|---|
US (2) | US8015152B2 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130185649A1 (en) * | 2012-01-18 | 2013-07-18 | Microsoft Corporation | System and method for blended presentation of locally and remotely stored electronic messages |
US8949283B1 (en) | 2013-12-23 | 2015-02-03 | Google Inc. | Systems and methods for clustering electronic messages |
US9015192B1 (en) | 2013-12-30 | 2015-04-21 | Google Inc. | Systems and methods for improved processing of personalized message queries |
US20150188870A1 (en) * | 2013-12-31 | 2015-07-02 | Google Inc. | Systems and methods for progressive message flow |
US9124546B2 (en) | 2013-12-31 | 2015-09-01 | Google Inc. | Systems and methods for throttling display of electronic messages |
US9152307B2 (en) | 2013-12-31 | 2015-10-06 | Google Inc. | Systems and methods for simultaneously displaying clustered, in-line electronic messages in one display |
US9542668B2 (en) | 2013-12-30 | 2017-01-10 | Google Inc. | Systems and methods for clustering electronic messages |
US9767189B2 (en) | 2013-12-30 | 2017-09-19 | Google Inc. | Custom electronic message presentation based on electronic message category |
US10033679B2 (en) | 2013-12-31 | 2018-07-24 | Google Llc | Systems and methods for displaying unseen labels in a clustering in-box environment |
US10110699B2 (en) | 2012-08-27 | 2018-10-23 | Samsung Electronics Co., Ltd. | Method and system to enable mobile users to receive personalized notifications |
Families Citing this family (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7720916B2 (en) * | 2006-02-28 | 2010-05-18 | Microsoft Corporation | Ordering personal information using social metadata |
US8134727B1 (en) | 2006-11-27 | 2012-03-13 | Ringcentral, Inc. | Message preview control |
US20090048894A1 (en) * | 2007-08-14 | 2009-02-19 | Michel Shane Simpson | Techniques for propagating changes in projects |
US8792118B2 (en) | 2007-09-26 | 2014-07-29 | Ringcentral Inc. | User interfaces and methods to provision electronic facsimiles |
US8670545B2 (en) | 2007-09-28 | 2014-03-11 | Ringcentral, Inc. | Inbound call identification and management |
US8600391B2 (en) | 2008-11-24 | 2013-12-03 | Ringcentral, Inc. | Call management for location-aware mobile devices |
US8275110B2 (en) | 2007-09-28 | 2012-09-25 | Ringcentral, Inc. | Active call filtering, screening and dispatching |
US9135073B2 (en) | 2007-11-15 | 2015-09-15 | International Business Machines Corporation | Server-processor hybrid system for processing data |
US8260864B2 (en) * | 2008-02-13 | 2012-09-04 | Microsoft Corporation | Push mechanism for efficiently sending aggregated data items to client |
US8055657B2 (en) * | 2008-10-09 | 2011-11-08 | International Business Machines Corporation | Integrated entity and integrated operations of personalized data resource across the world wide web for online and offline interactions |
US8780383B2 (en) | 2008-11-25 | 2014-07-15 | Ringcentral, Inc. | Authenticated facsimile transmission from mobile devices |
WO2010062981A2 (en) | 2008-11-26 | 2010-06-03 | Ringcentral, Inc. | Centralized status server for call management of location-aware mobile devices |
US9129254B2 (en) * | 2008-12-30 | 2015-09-08 | Blackboard Connect Inc. | Concatenating messages from multiple sources in a notification system |
CN101478432B (en) * | 2009-01-09 | 2011-02-02 | 南京联创科技集团股份有限公司 | Network element state polling method based on storage process timed scheduling |
TWI488103B (en) * | 2009-02-13 | 2015-06-11 | Htc Corp | Method, apparatus and computer program product for prompting and browsing related information of contacts |
US20110066974A1 (en) * | 2009-09-14 | 2011-03-17 | Research In Motion Limited | Method and apparatus for providing reminders associated with calendar event data |
US9172765B2 (en) * | 2010-07-01 | 2015-10-27 | Desktop Alert, Inc. | Polling-based secure network message notification system and method with performance enhancing features |
US8966377B2 (en) | 2010-08-20 | 2015-02-24 | Nokia Corporation | Method and apparatus for a virtual desktop |
US8312096B2 (en) * | 2010-12-08 | 2012-11-13 | Google Inc. | Priority inbox notifications and synchronization for mobile messaging application |
US8893033B2 (en) * | 2011-05-27 | 2014-11-18 | Microsoft Corporation | Application notifications |
US9110739B2 (en) * | 2011-06-07 | 2015-08-18 | Microsoft Technology Licensing, Llc | Subscribing to multiple resources through a common connection |
US20110307566A1 (en) * | 2011-07-18 | 2011-12-15 | Victor Yeung | System for automatically appending digital correspondence compositions with status updates outputted by an iteration of a qualified user defined function |
KR20130052374A (en) * | 2011-11-11 | 2013-05-22 | 삼성전자주식회사 | System and method for sharing application information |
US8670529B1 (en) | 2012-12-17 | 2014-03-11 | Ringcentral, Inc. | Context aware help system |
US8831191B1 (en) | 2013-06-28 | 2014-09-09 | Ringcentral, Inc. | Call preview system |
US9948502B2 (en) | 2013-11-15 | 2018-04-17 | Openpeak Llc | Method and system for self-healing of communication network |
US10291745B2 (en) * | 2014-03-28 | 2019-05-14 | Microsoft Technology Licensing, Llc | Cross-client integration of groups |
US20150381533A1 (en) * | 2014-06-29 | 2015-12-31 | Avaya Inc. | System and Method for Email Management Through Detection and Analysis of Dynamically Variable Behavior and Activity Patterns |
US11755635B2 (en) * | 2014-07-09 | 2023-09-12 | Splunk Inc. | Presentation and sorting of summaries of alert instances triggered by search queries |
US10356157B2 (en) * | 2015-04-16 | 2019-07-16 | Google Llc | Systems and methods for notifying users of changes to files in cloud-based file-storage systems |
US9756005B2 (en) * | 2015-11-04 | 2017-09-05 | Google Inc. | Notification bundles for affinities between notification data |
CN107809517B (en) * | 2016-09-08 | 2020-07-10 | 阿里巴巴集团控股有限公司 | Event display method and device |
WO2018057627A1 (en) * | 2016-09-20 | 2018-03-29 | Google Llc | System and method for transmitting a response in a messaging application |
US11863510B2 (en) * | 2017-03-29 | 2024-01-02 | Samsung Electronics Co., Ltd. | Systems and methods for notification delivery |
JP6604672B2 (en) * | 2017-10-31 | 2019-11-13 | デルタ ピーディーエス カンパニー,リミテッド | Folder-based file management device |
US11249948B2 (en) * | 2017-10-31 | 2022-02-15 | Delta Pds Co., Ltd. | Smart log file management device and method for creating a system log message containing information about an update to a folder or a file folder |
US10812435B2 (en) | 2018-02-28 | 2020-10-20 | Ringcentral, Inc. | Systems and methods for suppressing repetitive notifications about messages in messaging groups |
US11329940B2 (en) * | 2019-10-28 | 2022-05-10 | Microsoft Technology Licensing, Llc | Coordinated unread count for email applications |
US11175967B2 (en) * | 2019-12-18 | 2021-11-16 | Citrix Systems, Inc. | Intelligent contextual grouping of notifications in an activity feed |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020087643A1 (en) * | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified WAP alerts |
US20030069874A1 (en) * | 1999-05-05 | 2003-04-10 | Eyal Hertzog | Method and system to automate the updating of personal information within a personal information management application and to synchronize such updated personal information management applications |
US6598094B1 (en) * | 1998-03-20 | 2003-07-22 | Sun Microsystems, Inc. | Method and apparatus for determining status of remote objects in a distributed system |
US6654746B1 (en) * | 1999-05-03 | 2003-11-25 | Symantec Corporation | Methods and apparatuses for single-connection file synchronization workgroup file update |
US7127485B2 (en) * | 2002-01-18 | 2006-10-24 | Telcordia Technologies, Inc. | Adaptive polling for asynchronous notification |
US7219153B1 (en) * | 2002-12-02 | 2007-05-15 | Cisco Technology, Inc. | Methods and apparatus for distributing content |
US20070174487A1 (en) * | 2004-04-20 | 2007-07-26 | Pluck Corporation | Method, system, and computer program product for synchronizing information within a global computer network |
US7305672B2 (en) * | 2004-01-06 | 2007-12-04 | International Business Machines Corporation | Dynamic software update system, method and program product |
US8140718B2 (en) * | 2004-12-08 | 2012-03-20 | Hewlett-Packard Development Company, L.P. | Status notifications |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6963859B2 (en) * | 1994-11-23 | 2005-11-08 | Contentguard Holdings, Inc. | Content rendering repository |
US6598068B1 (en) * | 1996-01-04 | 2003-07-22 | Sun Microsystems, Inc. | Method and apparatus for automatically managing concurrent access to a shared resource in a multi-threaded programming environment |
US5721825A (en) * | 1996-03-15 | 1998-02-24 | Netvision, Inc. | System and method for global event notification and delivery in a distributed computing environment |
US6101541A (en) * | 1998-04-21 | 2000-08-08 | International Business Machines Corporation | Active polling by network LDAP directory |
US6167448A (en) * | 1998-06-11 | 2000-12-26 | Compaq Computer Corporation | Management event notification system using event notification messages written using a markup language |
US6763384B1 (en) * | 2000-07-10 | 2004-07-13 | International Business Machines Corporation | Event-triggered notification over a network |
US6725228B1 (en) * | 2000-10-31 | 2004-04-20 | David Morley Clark | System for managing and organizing stored electronic messages |
US6963919B1 (en) * | 2001-02-28 | 2005-11-08 | Agilent Technologies, Inc. | Method and system for improving computer network performance |
US7068189B2 (en) * | 2001-07-03 | 2006-06-27 | Nortel Networks Limited | Location and event triggered notification services |
US20040002958A1 (en) * | 2002-06-26 | 2004-01-01 | Praveen Seshadri | System and method for providing notification(s) |
US20050160335A1 (en) * | 2002-07-15 | 2005-07-21 | Peterson Alec H. | System and method for monitoring state information in a network |
US7076235B2 (en) * | 2002-12-03 | 2006-07-11 | Sony Ericsson Mobile Communications Ab | Automatic notification of personal emergency contacts from a wireless communications device |
US20050091319A1 (en) * | 2003-10-09 | 2005-04-28 | Kirsch Steven T. | Database for receiving, storing and compiling information about email messages |
US20050080857A1 (en) * | 2003-10-09 | 2005-04-14 | Kirsch Steven T. | Method and system for categorizing and processing e-mails |
US7739345B2 (en) * | 2003-03-31 | 2010-06-15 | Sap Ag | Alert notification engine |
US8150923B2 (en) * | 2003-10-23 | 2012-04-03 | Microsoft Corporation | Schema hierarchy for electronic messages |
US20050198159A1 (en) * | 2004-03-08 | 2005-09-08 | Kirsch Steven T. | Method and system for categorizing and processing e-mails based upon information in the message header and SMTP session |
US7298714B2 (en) * | 2005-10-04 | 2007-11-20 | Yahoo! Inc. | Peer-to-peer message chaining for initiating a data exchange with a server |
-
2006
- 2006-01-24 US US11/338,039 patent/US8015152B2/en active Active
-
2011
- 2011-08-02 US US13/196,528 patent/US20120198053A1/en not_active Abandoned
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6598094B1 (en) * | 1998-03-20 | 2003-07-22 | Sun Microsystems, Inc. | Method and apparatus for determining status of remote objects in a distributed system |
US6654746B1 (en) * | 1999-05-03 | 2003-11-25 | Symantec Corporation | Methods and apparatuses for single-connection file synchronization workgroup file update |
US20030069874A1 (en) * | 1999-05-05 | 2003-04-10 | Eyal Hertzog | Method and system to automate the updating of personal information within a personal information management application and to synchronize such updated personal information management applications |
US20020087643A1 (en) * | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified WAP alerts |
US6871214B2 (en) * | 2000-10-30 | 2005-03-22 | Nortel Networks Limited | Generating and providing alert messages in a communications network |
US7127485B2 (en) * | 2002-01-18 | 2006-10-24 | Telcordia Technologies, Inc. | Adaptive polling for asynchronous notification |
US7219153B1 (en) * | 2002-12-02 | 2007-05-15 | Cisco Technology, Inc. | Methods and apparatus for distributing content |
US7305672B2 (en) * | 2004-01-06 | 2007-12-04 | International Business Machines Corporation | Dynamic software update system, method and program product |
US20070174487A1 (en) * | 2004-04-20 | 2007-07-26 | Pluck Corporation | Method, system, and computer program product for synchronizing information within a global computer network |
US8140718B2 (en) * | 2004-12-08 | 2012-03-20 | Hewlett-Packard Development Company, L.P. | Status notifications |
Non-Patent Citations (2)
Title |
---|
Busey US Patent Application no 2007/0174487; hereinafter * |
TechTarget Network Website, http://searchsoa.techtarget.com/definition/table * |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130185649A1 (en) * | 2012-01-18 | 2013-07-18 | Microsoft Corporation | System and method for blended presentation of locally and remotely stored electronic messages |
US10255587B2 (en) * | 2012-01-18 | 2019-04-09 | Microsoft Technology Licensing, Llc | System and method for blended presentation of locally and remotely stored electronic messages |
US10110699B2 (en) | 2012-08-27 | 2018-10-23 | Samsung Electronics Co., Ltd. | Method and system to enable mobile users to receive personalized notifications |
US9654432B2 (en) | 2013-12-23 | 2017-05-16 | Google Inc. | Systems and methods for clustering electronic messages |
US8949283B1 (en) | 2013-12-23 | 2015-02-03 | Google Inc. | Systems and methods for clustering electronic messages |
US9542668B2 (en) | 2013-12-30 | 2017-01-10 | Google Inc. | Systems and methods for clustering electronic messages |
US9767189B2 (en) | 2013-12-30 | 2017-09-19 | Google Inc. | Custom electronic message presentation based on electronic message category |
US9015192B1 (en) | 2013-12-30 | 2015-04-21 | Google Inc. | Systems and methods for improved processing of personalized message queries |
US9306893B2 (en) * | 2013-12-31 | 2016-04-05 | Google Inc. | Systems and methods for progressive message flow |
US9124546B2 (en) | 2013-12-31 | 2015-09-01 | Google Inc. | Systems and methods for throttling display of electronic messages |
US20150188870A1 (en) * | 2013-12-31 | 2015-07-02 | Google Inc. | Systems and methods for progressive message flow |
US10021053B2 (en) | 2013-12-31 | 2018-07-10 | Google Llc | Systems and methods for throttling display of electronic messages |
US10033679B2 (en) | 2013-12-31 | 2018-07-24 | Google Llc | Systems and methods for displaying unseen labels in a clustering in-box environment |
US9152307B2 (en) | 2013-12-31 | 2015-10-06 | Google Inc. | Systems and methods for simultaneously displaying clustered, in-line electronic messages in one display |
US10616164B2 (en) | 2013-12-31 | 2020-04-07 | Google Llc | Systems and methods for displaying labels in a clustering in-box environment |
US11190476B2 (en) | 2013-12-31 | 2021-11-30 | Google Llc | Systems and methods for displaying labels in a clustering in-box environment |
US11483274B2 (en) | 2013-12-31 | 2022-10-25 | Google Llc | Systems and methods for displaying labels in a clustering in-box environment |
US11729131B2 (en) | 2013-12-31 | 2023-08-15 | Google Llc | Systems and methods for displaying unseen labels in a clustering in-box environment |
Also Published As
Publication number | Publication date |
---|---|
US8015152B2 (en) | 2011-09-06 |
US20070198677A1 (en) | 2007-08-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8015152B2 (en) | Web based client/server notification engine | |
RU2600102C2 (en) | Sorting electronic information exchange | |
US7716593B2 (en) | Conversation grouping of electronic mail records | |
JP5960215B2 (en) | Priority inbox notification and synchronization for mobile messaging applications | |
US8161125B2 (en) | Message data management | |
ES2373297T3 (en) | Procedures and systems to capture and retrieval. | |
US20160261613A1 (en) | Real-time asynchronous event aggregation systems | |
US7979501B1 (en) | Enhanced message display | |
KR101919180B1 (en) | Synchronizing conversation structures in web-based email systems | |
US20070100991A1 (en) | Method and program product for tracking a file attachment in an e-mail | |
US20160269341A1 (en) | Distribution of endorsement indications in communication environments | |
US20120005282A1 (en) | Collaborative ranking and filtering of electronic mail messages | |
US9542668B2 (en) | Systems and methods for clustering electronic messages | |
US9954807B2 (en) | Endorsement indications in communication environments | |
US20070124385A1 (en) | Preference-based content distribution service | |
US9002950B2 (en) | Method and system to file relayed e-mails | |
US20140173011A1 (en) | Methods and systems for structuring information of email messages | |
EP3342106B1 (en) | Conversation enrichment through component re-order | |
US10498680B2 (en) | Conversation enrichment through component re-order | |
US10432776B1 (en) | Managing unanswered digital communications | |
US7707258B2 (en) | Sending e-mail from a hosted system | |
US11777886B1 (en) | Management of queries in electronic mail messages | |
US11470031B2 (en) | Electronic mail format protocol for instructing automatic behavior of electronic devices executing an electronic mail client application | |
JP2023165249A (en) | System for measuring degree of interest in region, method of measuring degree of interest in region, and program | |
JPH11154972A (en) | Recording medium recording specific mail delivering situation tracking program or the like and specific mail delivering situation tracking method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0001 Effective date: 20141014 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |