Patent Grant
9129264
The present invention is a divisional application of co-pending U.S. application Ser. No. 11/548,570, filed on Oct. 11, 2006, the contents of which are incorporated herein by reference in its entirety.
The invention generally relates to a system and method of electronic calendar automatic event resolution and, more particularly, to a system and method configured to provide event resolution for both pre-scheduled and post-scheduled events.
Electronic office tools are ubiquitous in today's business environments. These electronic office tools include, for example, calendars, appointment books, address books and contact lists, to name a few. In fact, these tools are typically an extension of features provided by time management software such as desk accessory packages and mainframe office automation systems. These tools are often packaged by original equipment manufacturers. For example, International Business Machines Corp. (IBM) packages many of these features in Lotus Notes®. (IBM and Lotus Notes are trademarks of International Business Machines Corporation in the United States, other countries, or both).
Calendaring and other time management systems are very powerful tools. For example, these tools allow a user to schedule appointments such as team meetings or other appointments and notify and/or remind participants by email of such appointments. Calendar features also include automatic event reminders, including mobile phone notifications, which instantly bring up calendar events with built-in search tools.
By way of a more specific example, electronic calendars have special functionality which allows users to track scheduled events, add events to a calendar, and notify/invite other individuals of the scheduled events. In addition, many electronic calendars permit the user to denote blocks of time for scheduled vacation, either as half day vacations or full day vacations, site holidays and other customized out of the office events. In fact, some calendars permit a sharing feature to allow other users to see upcoming events on another user's calendar.
These functions are all very useful when organizing and scheduling events and, in particular managing time. However, it is not uncommon for scheduled events to conflict with one another, unbeknownst to the user. For example, a user may have scheduled a block of time for an out of office event such as a vacation, but also accepted an appointment for a business meeting during this same time. This would typically occur, as one example, by a colleague sending a recipient an email invitation requesting a meeting at a certain time and date. The recipient would accept the invitation by “hitting” the “accept” button, which, in turn, would automatically notify the sender of such acceptance. By doing so, the business meeting would automatically be placed into the recipient's calendar at the accepted time and date. However, unwittingly, the accepted invitation may conflict with a scheduled vacation. This may not be realized, at all, or may be realized only after the recipient was looking through his/her calendar for other scheduled events.
Accordingly, there exists a need in the art to overcome the deficiencies and limitations described hereinabove.
In a first aspect of the invention, a method comprises determining whether a scheduled event is confirmed and whether a user is designated as a chair of a meeting. When the user is designated as the chair and the scheduled event is confirmed, for each meeting conflicting with the scheduled event, the method cancels, reschedules the meeting to a non-conflicting time or performs an action. When the user is not designated as the chair and the scheduled event is confirmed, the method performs an action.
In another aspect of the invention, a method comprises determining whether a post-scheduled event or a pre-scheduled event conflicts with a scheduled event. The method further includes extracting details of the post-scheduled event or the pre-scheduled event and automatically populating a response with at least some of the extracted details. The method further includes sending the response with an accept indication when the post-scheduled event or the pre-scheduled event does not conflict with the scheduled event, or sending the response with a cancel indication when the post-scheduled event or the pre-scheduled event conflicts with the scheduled event, or sending the response with a tentatively accept indication when the post-scheduled event or the pre-scheduled event conflicts with the scheduled event.
In another aspect of the invention, a method is provided for deploying an application for event resolution. The method comprises providing a computer infrastructure being operable to: determine whether a post-scheduled event or a pre-scheduled event conflicts with a scheduled event; extract details of the post-scheduled event or the pre-scheduled event; automatically populate a response with at least some of the extracted details; and send the response. The response may include an accept indication when the post-scheduled event or the pre-scheduled event does not conflict with the scheduled event. The response may include a cancel indication when the post-scheduled event or the pre-scheduled event conflicts with the scheduled event. The response may include a tentatively accept indication when the post-scheduled event or the pre-scheduled event conflicts with the scheduled event.
In yet another aspect of the invention, a system comprising at least one of a hardware and software component is provided for event resolution between a scheduled event and at least one of a pre-scheduled event and post-scheduled event. The hardware and/or software component is configured to: determine whether there is a conflict between the scheduled event and at least one of the pre-scheduled event and post-scheduled event, if existing; update a calendar with a non-conflicting event; and notify a sender of the at least one of the pre-scheduled event and post-scheduled event that a recipient accepts, declines or tentatively accepts a time for the at least one of the pre-scheduled event and post-scheduled event, depending on a conflict.
In a further aspect of the invention, a computer program product comprises a computer usable medium having readable program code embodied in the medium. The computer program product includes at least one component to provide the method steps of the invention. The at least one component can also provide the functionality of the system of the invention.
The invention is directed to a system and method of electronic calendar automatic event resolution. In an embodiment of the invention, the method and system is configured to provide event resolution for both pre-scheduled and post-scheduled events that coincide with times in which the user will (or may) be unavailable, e.g., out of the office. The system and method of the invention will save the user time by automatically resolving meeting information using a set of predetermined choices to automate the process of dealing with events that coincide with scheduled conflicts such as, for example, time out of the office. Meetings are defined broadly to encompass teleconferences, lectures/seminars, or other events which require participation from the intended user. Possible resolutions may include, but not be limited to, automatically rescheduling and/or declining meetings. Additionally, by implementing the system and method of the invention, time to schedule events and notify others will be greatly reduced, compared with conventional systems. The invention can be implemented over any distributed network or stand-alone server, for example.
In general, the processor 20 executes computer program code, which is stored in memory 22A and/or storage system 22B. While executing computer program code, the processor 20 can read and/or write data to/from memory 22A, storage system 22B, and/or I/O interface 24. The bus 26 provides a communications link between each of the components in the computing device 14. The I/O device 28 can comprise any device that enables an individual to interact with the computing device 14 or any device that enables the computing device 14 to communicate with one or more other computing devices using any type of communications link.
The computing device 14 can comprise any general purpose computing article of manufacture capable of executing computer program code installed thereon (e.g., a personal computer, server, handheld device, etc.). However, it is understood that the computing device 14 is only representative of various possible equivalent computing devices that may perform the processes described herein. To this extent, in embodiments, the functionality provided by computing device 14 can be implemented by a computing article of manufacture that includes any combination of general and/or specific purpose hardware and/or computer program code. In each embodiment, the program code and hardware can be created using standard programming and engineering techniques, respectively.
Similarly, the computer infrastructure 12 is only illustrative of various types of computer infrastructures for implementing the invention. For example, in embodiments, the computer infrastructure 12 comprises two or more computing devices (e.g., a server cluster) that communicate over any type of communications link, such as a network, a shared memory, or the like, to perform the process described herein. Further, while performing the process described herein, one or more computing devices in the computer infrastructure 12 can communicate with one or more other computing devices external to computer infrastructure 12 using any type of communications link. The communications link can comprise any combination of wired and/or wireless links; any combination of one or more types of networks (e.g., the Internet, a wide area network, a local area network, a virtual private network, etc.); and/or utilize any combination of transmission techniques and protocols. As discussed herein, the management system 30 enables the computer infrastructure 12 to provide electronic calendar automatic event resolution.
In embodiments, the invention provides a business method that performs the process steps of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to perform the processes described herein. In this case, the service provider can create, deploy, maintain, and support, etc., a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
In one embodiment, the invention is configured to reconcile both pre-scheduled and post-scheduled events. Pre-scheduled events may include events that are pre-scheduled prior to a time being denoted as out-of-office or other event blocked on the schedule. Post-scheduled events may include events that are scheduled after an out-of-office or other conflicting event is already blocked on the scheduled. A conflicting event may denote any event in which there is time blocked on the calendar, whether that is a meeting or other scheduled event on the calendar.
In embodiments, the system and method is configured to determine if the out-of-office or other conflicting event (hereinafter referred to as “conflicting event”) is definite or tentative. This may be accomplished by creating a profile that allows a user to indicate the number of days prior to an event to confirm the conflicting event. The system will prompt the user several days or other predetermined time period prior to the conflicting event to confirm the conflicting event. If the conflicting event is confirmed, automatic event notifications will be sent to other persons attempting to schedule an appointment, which would otherwise conflict with the conflicting event.
In further embodiments, in the event that the user cancels the conflicting event, it is possible to retrieve the pre-scheduled or post-scheduled event. By way of one example, pre-scheduled or post-scheduled events may be saved in a log file for future reference. Additional details can be included in the log file such as the original meeting date and the date rescheduled meeting date. The system and method further provides the ability to automatically restore the meeting details to the calendar after they have been removed. The log file will be utilized to allow this functionality.
In the case of a pre-scheduled event (e.g., an event is listed on the user's calendar prior to scheduling the conflicting event), the system and method can perform certain functions when a conflicting event is later scheduled. For example, for events that are chaired by a third party, the system and method of the invention is configured to perform the following functions:
For events that are chaired by the user (recipient), the system and method of the invention is configured to perform the following functions:
In the case of a post-scheduled event, the system and method can perform certain functions when a conflicting event is scheduled as block of time on the calendar. For example, for conflicting events that are tentatively scheduled, the system and method of the invention is configured to perform the following functions:
In the case of a conflicting event is definitely scheduled, the system and method of the invention is configured to perform the following functions:
In any of the above exemplary embodiments, the user may create a profile which could reside on both the server and the client machine, with the main copy being housed on the server for easy access from any client. In the profile, there may be a set threshold, e.g., percentage of individuals available, to select a reschedule date. The profile may contain but is not limited to:
In one example, the template 200 includes a “to” field 202, a “CC” field 203 and a “subject” line field 204. In addition, the template 200 includes a “delegate chair” field 206, “accept” field 208, “decline” field 210 and “tentatively scheduled” field 212. Additionally, in embodiments, the template may include a “time/date” field 214 and “reschedule” field 216. Moreover, a “subject” field 218 may also be provided in the template 200. The template 200 may be an email, itself, or converted to an email, which one of ordinary skill in the art could easily implement.
In use, information may be extracted from an invitation email in order to populate or append to the template 200. For example, an invitation email may request “N” number of recipients to attend a meeting on a certain date and time, with recipient “1” being delegated as a chair. Recipient “1” may have a conflicting event, in which case, the system and method would extract the information from the invitation to populate the template 200. This information would include, for example, time and date of meeting, the recipients' email addresses, the subject of the meeting, etc. The recipient “1” may designate a new chair in field 218 and may decline the meeting via “decline” field 210 or alternatively reschedule the meeting using the “reschedule” field 216. Once all of the appropriate fields are populated, recipient “1” would then send the email to the remaining recipients.
In an embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc. Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. The software and/or computer program product can be implemented in the environment of
Referring back to
At step 304, the scheduled event may be confirmed. This may be accomplished by user input such as, for example, a pop up window that requires a user input, e.g., “confirm” or “not confirm” buttons. If the event is not confirmed, the process proceeds to step 306. At step 306, the process will maintain (e.g., not modify) the meeting details on the scheduled event day(s). As an option, the process will remove the scheduled event days from the calendar.
If the scheduled event is confirmed at step 304, the process proceeds to step 308. At step 308, a determination is made as to whether the user is designated as the chair of the meeting. If the user is designated as the chair of the meeting, at step 310, for each meeting being held on the scheduled event, the process will automatically cancel or reschedule the meeting to a non-conflicting time. At step 312, the process will compose a template email. The composition of the template email may be accomplished by extracting the invited attendees from meeting details and using this extracted information to populate (or append) the “to” section of the email. The process may additionally extract other information from the invitation such as, for example, the subject and use this extracted information to populate (or append) the “subject” line of the template. Similarly, the process may extract additional information such as, for example, meeting date, time, and subject and populate (or append) such information in the body of the template.
At step 314, the process will convert the template to an email. In an optional step, the template may already be an email, in which case the extracted information will be appended or populated directly to such email. At step 316, the email is sent to the invited attendees. At step 318, any or all of the extracted information may be written to a log file. The user can then refer back to the log file in the case that the scheduled event has been canceled. In such a case, the information in the log can be used to populate (or append) the appropriate fields of the email, requesting that the event be reinstated for the original date and time or rescheduled for another date and time. Also, the information from the log can be used to repopulate the calendar, thus setting up the meeting automatically.
If the user is not designated as the chair of the meeting at step 308, the process will proceed to step 320. At step 320, the process will automatically decline the meeting and thereafter process according to the steps 312, 314 and 316. In the composed email, a decline notification will be provided to the invited attendees.
As an alternative approach, if the scheduled event is confirmed at step 304, the process proceeds to step 322. At step 322, the process will provide an automatic decline message for each meeting invitation received. As discussed above, the decline message (e.g., email) may automatically be populated (or appended) with the event, event dates, etc. in the appropriate fields. The meeting details may also be written to a log for future use, as discussed above.
An example algorithm implementing the steps of
While the invention has been described in terms of embodiments, those skilled in the art will recognize that the invention can be practiced with modifications and in the spirit and scope of the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4807154 | Scully et al. | Feb 1989 | A |
| 4817018 | Cree et al. | Mar 1989 | A |
| 4866611 | Cree et al. | Sep 1989 | A |
| 5050077 | Vincent | Sep 1991 | A |
| 5070470 | Scully et al. | Dec 1991 | A |
| 5093901 | Cree et al. | Mar 1992 | A |
| 5113380 | Levine | May 1992 | A |
| 5124912 | Hotaling et al. | Jun 1992 | A |
| 5261045 | Scully et al. | Nov 1993 | A |
| 5323314 | Baber et al. | Jun 1994 | A |
| 5692125 | Schloss et al. | Nov 1997 | A |
| 5732399 | Katiyar et al. | Mar 1998 | A |
| 5774867 | Fitzpatrick et al. | Jun 1998 | A |
| 5933810 | Okawa | Aug 1999 | A |
| 5963913 | Henneuse et al. | Oct 1999 | A |
| 6016478 | Zhang et al. | Jan 2000 | A |
| 6101480 | Conmy et al. | Aug 2000 | A |
| 6167379 | Dean et al. | Dec 2000 | A |
| 6216110 | Silverberg | Apr 2001 | B1 |
| 6370566 | Discolo et al. | Apr 2002 | B2 |
| 6636888 | Bookspan et al. | Oct 2003 | B1 |
| 6732103 | Strick et al. | May 2004 | B1 |
| 6781920 | Bates et al. | Aug 2004 | B2 |
| 6988128 | Alexander et al. | Jan 2006 | B1 |
| 7082402 | Conmy et al. | Jul 2006 | B2 |
| 7096232 | Doss et al. | Aug 2006 | B2 |
| 7222156 | Gupta et al. | May 2007 | B2 |
| 7283970 | Cragun et al. | Oct 2007 | B2 |
| 7299193 | Cragun et al. | Nov 2007 | B2 |
| 7343313 | Dorenbosch et al. | Mar 2008 | B2 |
| 7379888 | Mahapatro | May 2008 | B1 |
| 7395221 | Doss et al. | Jul 2008 | B2 |
| 7421401 | Demsky et al. | Sep 2008 | B2 |
| 7519663 | Bostick et al. | Apr 2009 | B1 |
| 7679518 | Pabla et al. | Mar 2010 | B1 |
| 7747752 | Pedersen | Jun 2010 | B2 |
| 7752066 | Doss et al. | Jul 2010 | B2 |
| 7865387 | Mansour | Jan 2011 | B2 |
| 20010014866 | Conmy et al. | Aug 2001 | A1 |
| 20010037229 | Jacobs et al. | Nov 2001 | A1 |
| 20010054072 | Discolo et al. | Dec 2001 | A1 |
| 20020049733 | Orlick | Apr 2002 | A1 |
| 20020131565 | Scheuring et al. | Sep 2002 | A1 |
| 20020194246 | Moskowitz et al. | Dec 2002 | A1 |
| 20030061087 | Srimuang | Mar 2003 | A1 |
| 20030103415 | Bates et al. | Jun 2003 | A1 |
| 20030130882 | Shuttleworth et al. | Jul 2003 | A1 |
| 20030149605 | Cragun et al. | Aug 2003 | A1 |
| 20030149606 | Cragun et al. | Aug 2003 | A1 |
| 20030233265 | Lee et al. | Dec 2003 | A1 |
| 20040064585 | Doss et al. | Apr 2004 | A1 |
| 20040078436 | Demsky et al. | Apr 2004 | A1 |
| 20040088362 | Curbow et al. | May 2004 | A1 |
| 20040093290 | Doss et al. | May 2004 | A1 |
| 20040111307 | Demsky et al. | Jun 2004 | A1 |
| 20040128304 | Rokosz | Jul 2004 | A1 |
| 20040193458 | Bear | Sep 2004 | A1 |
| 20040221010 | Butler | Nov 2004 | A1 |
| 20040261013 | Wynn et al. | Dec 2004 | A1 |
| 20050038687 | Galdes | Feb 2005 | A1 |
| 20050065832 | Virta | Mar 2005 | A1 |
| 20050091095 | Wilbrink et al. | Apr 2005 | A1 |
| 20050202817 | Sudit | Sep 2005 | A1 |
| 20050256754 | Nastacio | Nov 2005 | A1 |
| 20050273372 | Bowne et al. | Dec 2005 | A1 |
| 20050288987 | Sattler et al. | Dec 2005 | A1 |
| 20060031326 | Ovenden | Feb 2006 | A1 |
| 20060047557 | Bieselin et al. | Mar 2006 | A1 |
| 20060047577 | Dietz et al. | Mar 2006 | A1 |
| 20060123011 | Stillion et al. | Jun 2006 | A1 |
| 20060184885 | Hayes et al. | Aug 2006 | A1 |
| 20060218027 | Carrion | Sep 2006 | A1 |
| 20060293943 | Tischhauser et al. | Dec 2006 | A1 |
| 20070005409 | Boss et al. | Jan 2007 | A1 |
| 20070008911 | MacFarlane et al. | Jan 2007 | A1 |
| 20070022075 | Horvitz et al. | Jan 2007 | A1 |
| 20070239509 | Kaminsky et al. | Oct 2007 | A1 |
| 20070250366 | Nurmi | Oct 2007 | A1 |
| 20070282654 | Sarkar | Dec 2007 | A1 |
| 20080033778 | Boss et al. | Feb 2008 | A1 |
| 20080046514 | Daughtry et al. | Feb 2008 | A1 |
| 20080134041 | Zinn | Jun 2008 | A1 |
| 20080162250 | Carrion | Jul 2008 | A1 |
| 20080189624 | Chotai et al. | Aug 2008 | A1 |
| 20080243582 | Chen et al. | Oct 2008 | A1 |
| 20090125818 | Ritter et al. | May 2009 | A1 |
| 20090138283 | Brown | May 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 1109121 | Jun 2001 | EP |
| Entry |
|---|
| “Participation Status on Computer Calendar Systems,” Research Disclosure. No. 298. Feb. 1989. Kenneth Mason Publications Ltd. |
| Number | Date | Country | |
|---|---|---|---|
| 20100217644 A1 | Aug 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11548570 | Oct 2006 | US |
| Child | 12722151 | US |
