A method of checking a new entry in a calendar application having a cache that includes a first subset of existing entries falling within a first date range. Also, an electronic device implementing the method. The method includes determining whether the date of the new entry falls within the first date range. If so, the method determines whether the new entry directly conflicts with or is adjacent to one of the existing entries in the first subset, and provides a notification if appropriate. If the date is outside the first date range, the method creates a new calendar cache including a second subset of existing entries falling within a second date range around the new entry date, determines whether the new calendar entry directly conflicts with or is adjacent to one of the existing calendar entries in the second subset, and provides a notification if appropriate.
|
1. A method of managing a calendar application comprising:
receiving information relating to a new calendar entry associated with the calendar application having existing calendar entries, the information including a date of the new calendar entry;
performing automatically, without user intervention:
determining, based on a calendar cache having a first subset of the existing calendar entries previously created from an external database, whether the new calendar entry is adjacent to at least one of the first subset of the existing calendar entries;
updating the calendar cache from the external database only if the date of the new calendar entry falls outside of a date range of the first subset of the existing calendar entries to create an updated calendar cache with a second subset of the existing calendar entries covering a predetermined date range including the date of the new calendar entry; and
providing an adjacent-meeting notification upon determining that the new calendar entry is adjacent to the at least one of the second subset of the existing calendar entries.
20. A non-transient computer readable medium having recorded thereon statements and instructions for execution by a processor of an electronic device to carry out a method of managing a calendar application in the electronic device, the method comprising:
receiving information relating to a new calendar entry associated with the calendar application having existing calendar entries, the information including a date of the new calendar entry;
performing automatically, without user intervention:
determining, based on a calendar cache having a first subset of the existing calendar entries previously created from an external database, whether the new calendar entry is adjacent to at least one of the first subset of the existing calendar entries;
updating the calendar cache from the external database only if the date of the new calendar entry falls outside of a date range of the first subset of the existing calendar entries to create an updated calendar cache with a second subset of the existing calendar entries covering a predetermined date range including the date of the new calendar entry; and
providing an adjacent-meeting notification upon determining that the new calendar entry is adjacent to the at least one of the second subset of the existing calendar entries.
10. An electronic device having a calendar application, comprising:
a display;
a processor; and
a memory storing a plurality of existing calendar entries of the calendar application, the calendar application having a calendar cache associated therewith, the calendar cache previously created from an external database, the memory storing one or more routines executable by the processor, the one or more routines being adapted to:
receive information relating to a new calendar entry, the information including a date of the new calendar entry; and
perform automatically, without user intervention, the steps of:
determining, based on a calendar cache having a first subset of the existing calendar entries previously created from an external database, whether the new calendar entry is adjacent to at least one of the first subset of the existing calendar entries;
updating the calendar cache from the external database only if the date of the new calendar entry falls outside of a date range of the first subset of the existing calendar entries to create an updated calendar cache with a second subset of the existing calendar entries covering a predetermined date range including the date of the new calendar entry; and
providing an adjacent-meeting notification upon determining that the new calendar entry is adjacent to the at least one of the second subset of the existing calendar entries.
2. The method of
determining whether a start time or an end time of the new calendar entry is within a predetermined adjacent-meeting time period, the predetermined adjacent-meeting time period being a time period within the start time or the end time of the at least one of the existing calendar entries.
3. The method of
receiving an ignore adjacent-meeting notification input, and
entering the information relating to the new calendar entry into the calendar application.
4. The method of
sending an acceptance response to a third party upon entry of the information relating to the new calendar entry into the calendar application.
5. The method of
aborting entry of the information relating to a new calendar entry into the calendar application in response to the adjacent-meeting notification.
6. The method of
sending a rejection response to a third party upon aborting entry of the information relating to the new calendar entry into the calendar application.
7. The method according to
8. The method according to
9. The method according to
11. The electronic device of
12. The electronic device of
determining whether a start time or an end time of the new calendar entry is within a predetermined adjacent-meeting time period, the predetermined adjacent-meeting time period being a time period within the start time or the end time of the at least one of the existing calendar entries.
13. The electronic device of
receive an ignore adjacent-meeting notification input, and
enter the information relating to the new calendar entry into the calendar application.
14. The electronic device of
send an acceptance response to a third party upon entry of the information relating to the new calendar entry into the calendar application.
15. The electronic device of
abort entry of the information relating to a new calendar entry into the calendar application in response to the adjacent-meeting notification.
16. The electronic device of
send a rejection response to a third party upon aborting entry of the information relating to the new calendar entry into the calendar application.
17. The electronic device according to
18. The electronic device according to
19. The electronic device according to
|
This application is a Continuation of U.S. patent application Ser. No. 12/132,326, filed on Jun. 3, 2008, which is a Continuation of U.S. patent application Ser. No. 10/980,402, filed on Nov. 3, 2004, which issued as U.S. Pat. No. 7,519,924 on Apr. 14, 2009.
1. Field of the Invention
The invention relates generally to handheld electronic devices and, more particularly, to a handheld electronic device having an improved calendar application for managing appointments and meetings that automatically checks for and notifies the user of scheduling conflicts with new appointments and meetings. The invention also relates to a method of managing appointments and meetings in a handheld electronic device that includes automatic conflict notification.
2. Description of the Related Art
Numerous types of handheld electronic devices are known. Examples of such handheld electronic devices include, for instance, personal data assistants (PDAs), handheld computers, two-way pagers, cellular telephones, and the like. Such handheld electronic devices are generally intended to be portable and thus are relatively small. Many handheld electronic devices also feature wireless communication capability, although many such handheld electronic devices are stand-alone devices that are functional without communication with other devices.
Many handheld electronic devices include and provide access to a wide range of integrated applications, including, without limitation, email, telephone, short message service (SMS), multimedia messaging service (MMS), browser, calendar and address book applications, such that a user can easily manage information and communications from a single, integrated device. These applications are typically selectively accessible and executable through a user interface that allows a user to easily navigate among and within these applications.
A typical calendar application provided on a handheld electronic device enables the user to, among other things, track and manage appointments and meetings and set reminders for various events and/or tasks. Specifically, users are able to enter particular appointments and meetings, including, for example, information such as the day, time, duration and location thereof. This information is saved and may be selectively manipulated and displayed to the user in various known formats, such as in monthly, weekly or daily views. In addition, users are also typically able to both invite other individuals to meetings and be invited to meetings by other individuals using the wireless communication capability of the handheld electronic device (invitations are typically sent and received using email messages). In the former case, the particular invitees are specified by the user at the time the new meeting is entered.
Typically, new appointments and meetings may be entered into a handheld electronic device by a user through a subroutine of the calendar application that enables the user to enter the relevant information. Similarly, another subroutine of the calendar application enables a user to accept or reject meeting invitations received from third parties, with appropriate information for accepted meetings being saved. For obvious reasons, a user will want to avoid scheduling new appointments or meetings that directly conflict with or are located too close in time with previously scheduled appointments or meetings.
Some prior art calendar applications utilized by non-handheld computing devices, such as a personal computer, include functionality wherein the entire database of calendar information maintained thereby is searched each time a new appointment or meeting is entered in order to determine whether conflicts exist. An example of such an application is the calendar application forming a part of the Outlook software application sold by Microsoft Corporation. However, due to memory and processing constraints present in most handheld electronic devices, it is not possible or practical to search the entire database of calendar entries each time a new appointment or meeting is to be entered. Thus, with current known handheld electronic devices, if a user wants to avoid scheduling new appointments or meetings (including those to which they are invited by third parties) that directly conflict with or are located too close in time with previously scheduled appointments or meetings, the user must manually check the calendar maintained by the calendar application for conflicts, either before, during, or after the steps of creating a new appointment. This will typically require the user to navigate through various different parts of the calendar application. These steps, while ultimately achieving the purpose of checking for conflicts, are inconvenient and time consuming. Thus, there is a need for a handheld electronic device that will automatically check for previously scheduled appointments or meetings that directly conflict with or are located too close in time with proposed new appointments or meetings.
A full understanding of the invention can be gained from the following Description of the Preferred Embodiments when read in conjunction with the accompanying drawings in which:
Similar numerals refer to similar parts throughout the specification.
An improved handheld electronic device 4 in accordance with the invention is depicted generally in
As can be understood from
As is shown in
As is also shown in
In
In
According to an aspect of the invention, calendar application 54 includes a subroutine, executable by processor 20, that maintains and updates a cache of calendar information. As is known, cache refers to a section of a computing device's memory which retains certain data in order to speed up repeated access to the same data. The cache maintained by calendar application 54 consists of a predefined subset of the existing entries of calendar application 54. The predefined subset consists of all existing entries of calendar application 54, including instances of recurring entries such as weekly meetings, within a predetermined time period, such as two months, before and after a particular date. According to the invention, the calendar cache is created each time the user activates calendar application 54, in which case the cache is created around the then current date. The calendar cache is also updated each time (i) a calendar entry is added and/or modified by the user, and (ii) the calendar entry in question has a date associated with it that falls outside of the current calendar cache date range. In such a case, the cache is updated (re-created) around the date associated with the entry in question. For example, if a user activates calendar application 54 on Oct. 1, 2004, calendar application 54 will create a cache consisting of the existing entries of calendar application 54 that are within a predetermined time period, say two months in this example, before and after Oct. 1, 2004. If a user subsequently enters a new appointment for Oct. 10, 2004, the cache will not be recreated around Oct. 10, 2004 because that date falls within the current cache date range. If, however, a user subsequently enters a new appointment for Dec. 10, 2004, the cache will be recreated around Dec. 10, 2004 because that date falls outside of the current cache date range. As described below, this calendar cache is used in the invention to facilitate the automatic checking of calendar entries for previously scheduled appointments or meetings that directly conflict with or are located too close in time with proposed new appointments or meetings. The calendar cache obviates the need to search the entire database of existing calendar entries.
A flowchart depicting a routine performed by processor 20 for automatically checking for and providing notification of previously scheduled appointments or meetings that directly conflict with or are located too close in time with proposed new appointments or meetings according to the invention is shown in
Referring again to
Next, at 110, a determination is made as to whether the date of the proposed new appointment or meeting falls within the date range covered by the current calendar cache maintained by calendar application 54. If the answer is no, then, at 115, calendar application 54 recreates the calendar cache around the date of the proposed new appointment or meeting, and the method proceeds to 120. If, however, the answer at 110 is yes, the method proceeds directly to 120.
At 120, a determination is made as to whether the proposed new appointment or meeting directly conflicts with one or more existing entries of calendar application 54. Specifically, the date and start and end time of the proposed new appointment or meeting is compared to the existing entries of calendar application 54 that are contained in the then current calendar cache to determine whether there are any existing entries that have a date and start and end time that overlaps in any respect with the date and start and end time of the proposed new appointment or meeting. If the answer at 120 is yes, then, at 125, a message is displayed on display 12 notifying the user of the fact that the proposed new appointment or meeting directly conflicts with one or more existing entries of calendar application 54.
Next, at 130, a determination is made as to whether the user wishes to ignore the direct conflict and schedule the proposed new appointment or meeting. If the answer is yes, then, at 135, the proposed new appointment or meeting is entered into calendar application 54 (and saved in memory 44) notwithstanding the direct conflict, which will result in overlapping entries for the date and times in question. As will be appreciated, where the method of
If the answer at 120 is no, meaning there is no direct conflict, then, at 145, a determination is made as to whether the proposed new appointment or meeting is adjacent to one or more existing entries of calendar application 54. Specifically, the date and start and end time of the proposed new appointment or meeting is compared to the existing entries of calendar application 54 that are contained in the then current calendar cache to determine whether there are any existing entries that have the same date as the proposed new appointment or meeting and a start time or an end time that is within a predetermined time period, such as fifteen minutes, of the end time or start time, respectively, of the proposed new appointment or meeting. If it is determined that the current calendar cache has an existing entry that has the same date as the proposed new appointment or meeting and a start time or an end time that is within a predetermined time period of the end time or start time, respectively, of the proposed new appointment or meeting then, as used herein, the proposed new appointment or meeting is said to be “adjacent to” an existing entry. This will allow a user to gauge whether there is sufficient time between the proposed new appointment or meeting and the existing calendar entry to make scheduling of the proposed new appointment or meeting feasible. Preferably, the predetermined time period may be selectively adjusted by the user as he or she sees fit. If the answer at 145 is yes, then, at 150, a message is displayed on display 12 notifying the user of the fact that the proposed new appointment or meeting is adjacent to one or more existing entries of calendar application 54.
Next, at 155, a determination is made as to whether the user wishes to ignore the fact that adjacent pre-existing entries are present and schedule the proposed new appointment or meeting. If the answer is yes, then, at 135, the proposed new appointment or meeting is entered into calendar application 54 (and saved in memory 44). As will be appreciated, where the method of
As is known, appointments or meetings that are entered into calendar application 54 may be periodically recurring appointments or meetings. For example, a user may have a weekly staff meeting that he or she wishes to enter into calendar application 54. The method shown in
Thus, the invention provides a handheld electronic device having functionality for automatically checking for and providing notification of previously scheduled appointments or meetings that directly conflict with or are located too close in time with proposed new appointments or meetings. In this manner, the user is able to more easily and efficiently manage his or her schedule as maintained by the calendar application of the handheld electronic device.
While specific embodiments of the invention have been described in detail, it will be appreciated by those skilled in the art that various modifications and alternatives to those details could be developed in light of the overall teachings of the disclosure. Accordingly, the particular arrangements disclosed are meant to be illustrative only and not limiting as to the scope of the invention which is to be given the full breadth of the claims appended and any and all equivalents thereof.
Bocking, Andrew D., May, Darrell R., Hardy, Michael T.
Patent | Priority | Assignee | Title |
10798208, | Sep 26 2016 | Microsoft Technology Licensing, LLC | Availability data caching in meeting systems |
Patent | Priority | Assignee | Title |
4415271, | Jun 06 1980 | Casio Computer Co., Ltd. | Compact electronic device having calendar function |
4626836, | Nov 04 1983 | International Business Machines Corp. | Method of scheduling meetings |
5023851, | Apr 06 1988 | IBM Corp. | Method for presenting electronic calendar information in an interactive information handling system |
5070470, | Dec 18 1987 | INTERNATIONAL BUSINESS MACHINES CORPORATION, A CORP OF NY | Methods for handling calendar information in a data processing system |
5247438, | Mar 30 1992 | INFOASSIST, INC | Personal time management system and method |
5311423, | Jan 07 1991 | CILSTAR RESEARCH LLC | Schedule management method |
5519606, | Jan 21 1992 | Intellisync Corporation | System and methods for appointment reconciliation |
5701423, | Apr 10 1992 | Intellisync Corporation | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
5745110, | Mar 10 1995 | Microsoft Technology Licensing, LLC | Method and apparatus for arranging and displaying task schedule information in a calendar view format |
5761525, | Mar 17 1994 | International Business Machines Corporation | Method and system for scheduling the playback of a multimedia presentation |
5774867, | Mar 25 1993 | International Business Machines Corporation; IBM Corporation | Meeting conflict resolution for electronic calendars |
5778346, | Jan 21 1992 | Intellisync Corporation | System and methods for appointment reconcilation |
5790974, | Apr 29 1996 | Oracle America, Inc | Portable calendaring device having perceptual agent managing calendar entries |
5855006, | Mar 01 1996 | Humware | Personal activity scheduling apparatus |
5877753, | Oct 17 1994 | Sharp Kabushiki Kaisha | Electronic apparatus having a schedule management function |
5960406, | Jan 22 1998 | LTT GLOBAL CONSULTANTS | Scheduling system for use between users on the web |
6144371, | Mar 18 1998 | International Business Machines Corporation | Thinkscribe combined electronic and paper based scheduling |
6279000, | Dec 26 1996 | Canon Kabushiki Kaisha | Information processing apparatus for managing schedule data and a method therefor |
6781920, | Dec 05 2001 | International Business Machines Corporation | Method for resolving meeting conflicts within an electronic calendar application |
6799186, | Oct 11 2001 | International Business Machines Corporation | SLA monitor calendar buffering |
7046676, | Nov 01 2001 | International Business Machines Corporation | QoS scheduler and method for implementing quality of service with cached status array |
20010054072, | |||
20020154178, | |||
20030093706, | |||
20030103415, | |||
20030130882, | |||
20030204474, | |||
20040019571, | |||
20040064355, | |||
20050039142, | |||
20050065832, | |||
20060047557, | |||
20060067280, | |||
20060136241, | |||
20070219842, | |||
JP10021198, | |||
WO2075517, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Oct 29 2004 | BOCKING, ANDREW D | Research In Motion Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027724 | /0017 | |
Oct 29 2004 | MAY, DARRELL R | Research In Motion Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027724 | /0017 | |
Oct 29 2004 | HARDY, MICHAEL T | Research In Motion Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027724 | /0017 | |
Feb 17 2012 | BlackBerry Limited | (assignment on the face of the patent) | / | |||
Jul 09 2013 | Research In Motion Limited | BlackBerry Limited | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 035021 | /0768 | |
May 11 2023 | BlackBerry Limited | Malikie Innovations Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 064104 | /0103 | |
May 11 2023 | BlackBerry Limited | Malikie Innovations Limited | NUNC PRO TUNC ASSIGNMENT SEE DOCUMENT FOR DETAILS | 064269 | /0001 |
Date | Maintenance Fee Events |
Dec 03 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Dec 02 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Jun 02 2018 | 4 years fee payment window open |
Dec 02 2018 | 6 months grace period start (w surcharge) |
Jun 02 2019 | patent expiry (for year 4) |
Jun 02 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jun 02 2022 | 8 years fee payment window open |
Dec 02 2022 | 6 months grace period start (w surcharge) |
Jun 02 2023 | patent expiry (for year 8) |
Jun 02 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jun 02 2026 | 12 years fee payment window open |
Dec 02 2026 | 6 months grace period start (w surcharge) |
Jun 02 2027 | patent expiry (for year 12) |
Jun 02 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |