WO2003107129A2 - Method and apparatus for a calendar tracking and monitoring service - Google Patents

Method and apparatus for a calendar tracking and monitoring service Download PDF

Info

Publication number
WO2003107129A2
WO2003107129A2 PCT/US2003/018717 US0318717W WO03107129A2 WO 2003107129 A2 WO2003107129 A2 WO 2003107129A2 US 0318717 W US0318717 W US 0318717W WO 03107129 A2 WO03107129 A2 WO 03107129A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
schedule
true
day schedule
true day
Prior art date
Application number
PCT/US2003/018717
Other languages
French (fr)
Other versions
WO2003107129A3 (en
Inventor
Samir Lehaff
Martin E. Miller
Original Assignee
Gp Ware
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Gp Ware filed Critical Gp Ware
Priority to AU2003236513A priority Critical patent/AU2003236513A1/en
Publication of WO2003107129A2 publication Critical patent/WO2003107129A2/en
Publication of WO2003107129A3 publication Critical patent/WO2003107129A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/109Time management, e.g. calendars, reminders, meetings or time accounting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/04Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G06Q10/047Optimisation of routes or paths, e.g. travelling salesman problem

Definitions

  • the present invention relates generally to a method and apparatus for a calendar tracking and monitoring service. More specifically, the present invention relates to a method and apparatus for generating and monitoring a user's schedule utilizing a desktop calendar application and an address and mapping database.
  • Personal calendaring systems are becoming more widespread as a necessary tool in organizing business as well as personal schedules.
  • Personal calendaring systems have been implemented in desktop systems and laptop systems alike. It is also common for personal calendaring systems to be implemented on personal digital assistants (PDAs) or other handheld devices, including portable telephones.
  • PDAs personal digital assistants
  • Personal calendaring systems in a desktop or laptop system can be synchronized to a compatible system on a handheld device. Synchronization allows a user to keep schedule information current on both the handheld device as well as on the host system. Appointments are readily kept on the aforementioned calendaring systems.
  • Such appointments usually contain scheduled times, location data, participants, duration and other data associated with the appointment as specified by the user.
  • Such databases are able to map locations based on address data supplied by a user and can also provide driving routes based on two addresses.
  • GPS Global Positioning System
  • the present invention is a system and method that provides the scheduling capabilities of a personal calendaring system while incorporating the services available to address and mapping database users and GPS users.
  • the present invention is a system and method that utilizes a user's existing personal digital assistant or equivalent and contact information residing on a host system to automatically compile appointments, trips and travel times to create a travel schedule.
  • the system and method can then concatenate the calendar schedule with the travel schedule to get a true day schedule.
  • the true day schedule may include departure times for appointments, lists of participants in the scheduled meetings, may notify departing parties of correct departure times and may notify the hosting parties of the anticipated time of arrival.
  • An embodiment of the present invention includes a calendar tracking, monitoring and communication system having a desktop calendar application containing a daily schedule wherein a user selects a specific day having at least one appointment, a service bureau coupled with the desktop calendar application, the service bureau containing an address and mapping database and a handheld device coupled with the desktop calendar application, wherein when the user activates a scheduling command for the specific day, the daily schedule concatenates with the service bureau, sending a true day schedule to the handheld device.
  • the handheld device containing the true day schedule is selectively decoupled after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule.
  • the true day schedule generates a departure time based on a travel time for each of the at least one appointments, a list of participating individuals for each of the at least one appointments wherein the list of participating individuals is notified by an email with a map or a voice mail when the user is late, a suggested route for the user to follow to attend each of the at least one appointments and an approximate travel time estimation.
  • the true day schedule includes an estimated time of arrival and an alerting means that activates when the user can not arrive before the estimated time of arrival.
  • the handheld device includes a means for notifying the user of any of the at least one appointments as specified by the user wherein the means for notifying includes a voice notification system.
  • the true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
  • the handheld device includes global positioning and wireless transmission capabilities so that the true day schedule is selectively navigated in real time by wireless transmission to the service bureau.
  • the handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities, of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities and to transmit and receive information between a group of one or more handheld devices.
  • the information includes global positioning system coordinates and relative movement and proximity of the handheld device to the group of one or more remote handheld devices.
  • the system of the present invention also includes an accounting application.
  • the accounting application records and organizes data, including mileage covered while navigating the true day schedule and expenses and costs associated with the true day schedule.
  • the service bureau is a desktop-based application coupled with the desktop calendar application. The scheduling command is activated from the desktop calendar application or from the handheld device.
  • a further embodiment of the present invention includes a method of managing and navigating a personal calendar including selecting a specific day having at least one appointment from a desktop calendar application containing a daily schedule, executing a command activated by a user for the specific day, concatenating the daily schedule with a service bureau, wherein the service bureau is coupled with the desktop calendar application and contains an address and mapping database and sending a true day schedule to a handheld device, wherein the handheld device is coupled with the desktop calendar application.
  • the method further includes decoupling the handheld device containing the true day schedule after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule.
  • the true day schedule includes a departure time for each of the at least one appointments, a list of participating individuals for each of the at least one appointments wherein the list of participating individuals is notified by an email with a map or a voice mail when the user is late, a suggested route for the user to follow to attend each of the at least one appointments and an approximate travel time estimation.
  • the true day schedule includes an estimated time of arrival and an alerting means that activates when the user can not arrive before the estimated time of arrival.
  • the handheld device includes a means for notifying the user of any of the at least one appointments as specified by the user wherein the means for notifying includes a voice notification system.
  • the true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
  • the method further includes navigating the true day schedule by wireless transmission to the service bureau by equipping the handheld device with global positioning and wireless transmission capabilities.
  • the handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities and of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities.
  • the method further includes wirelessly communicating with a group of one or more remote handheld devices in order to exchange information, including global positioning system coordinates.
  • the method further includes recording and organizing data using an accounting application, including mileage covered while navigating the true day schedule and expenses and costs associated with the true day schedule.
  • the service bureau is a desktop-based application coupled with the desktop calendar application. The scheduling command is activated from the desktop calendar application or from the handheld device.
  • Figure 1 illustrates a graphical representation of an embodiment of the present invention.
  • Figure 2 illustrates a graphical representation of the generation of the true day schedule of an embodiment of the present invention.
  • Figure 3 illustrates a flow chart representation of the preferred embodiment of the present invention.
  • Figure 4 illustrates a graphical representation of the preferred embodiment of the present invention.
  • Figure 5 illustrates a graphical representation of a further embodiment of the present invention.
  • Figure 6a illustrates a graphical representation of the generation of the true day schedule of the preferred embodiment of the present invention.
  • Figure 6b illustrates a graphical representation of the generation of the true day schedule of a further embodiment of the present invention.
  • the present invention is a method and apparatus, which combines a User's 101 existing Personal Digital Assistant (PDA) 102 and a Personal Calendar Application (Calendar Application) 104, having both calendar and contact information with locator and mapping services from a Service Bureau 112 or a Mapping Program 106 to provide a Calendar Tracking and Monitoring Service (Service) 100.
  • PDA Personal Digital Assistant
  • Calendar Application Calendar Application
  • Service 100 concatenates the Daily Schedule 202, as illustrated in Figure 2, from the PDA 102 with a travel schedule produced with the aid of the Service Bureau 112 or Mapping Program 106, to get a True Day Schedule 204, as will be discussed in detail below.
  • FIG. 1 depicts an embodiment of the present invention. This embodiment displays a "passive" operation which will be described herein.
  • a User 101 utilizes the System 100 of the present invention by first coupling a PDA 102 to a Host System 108.
  • the PDA 102 utilizes the Microsoft® Windows® for Pocket PC Operating System.
  • any handheld device having synchronization capabilities and a calendar system that is compatible with that of the Host System 108 maybe used as a PDA 102 in this System 100.
  • the term PDA preferably includes any appropriate handheld device including devices such as a handheld computer, laptop computer, portable telephone, pager, and messaging device.
  • the PDA 102 is coupled with the Host System 108 so as to allow synchronization between the PDA 102 and the Host System 108.
  • the Host System 108 can be a desktop system or a laptop, or any personal computing system able to support the Calendar Application 104, which is contained in the memory of the Host System 108.
  • the Calendar Application 104 is Microsoft Outlook®.
  • any Calendar Application 104 configurable to be synchronized to the PDA 102 maybe utilized.
  • the Service Bureau 112 is an address and mapping database that is coupled with the Host System 108.
  • the Service Bureau 112 provides mapping and directional information, as well as travel time data to the Host System 108 when prompted to do so.
  • One embodiment includes the Fixed Service Bureau 106 in a disk multi media format such as, but not limited to, a CD-ROM, DVD or Floppy Disk.
  • Another embodiment includes the Service Bureau 112 accessible to the Host System 108 through the Internet 110.
  • the User 101 initiates the operation of System 100 by coupling the PDA 102 to the Host System 108.
  • the User 101 selects a particular day from the Calendar Application 104 that the User 101 wishes to schedule. If the User 101 had previously entered the data for this selected day into the PDA 102 or previously synchronized the Calendar Application 104 to the PDA 102, then a Daily Schedule 202 will appear on the particular day selected. A typical Daily Schedule 202 would appear on the PDA 102 as shown in Figure 2. The view of the Daily Schedule 202 as it typically appears on a PDA 102 view will be shown for ease in explanation.
  • the User 101 then activates the Make My Day 206 command from either the PDA 102 or from the Calendar Application 104.
  • the User 101 is able to execute the Make My Day 206 command from the Calendar Application 104 due to a Make My Day 206 command button that is added to the graphical user interface of the Calendar Application 104.
  • This feature maybe added to any embodiment of the present invention. If the Daily Schedule 202 does not contain a single Appointment 208, the Calendar Application 104 will prompt the User 101 as to whether the User 101 wishes to select another day. If so, the User 101 may again select a particular Daily Schedule 202 from the Calendar Application 104 for which the User 101 wishes to schedule. If the User 101 does not wish to select a new day, then the operation is finished.
  • the Calendar Application 104 will concatenate with the Service Bureau 112 or the Mapping Program 106 to create a True Day Schedule 204.
  • the True Day Schedule 204 is sent to the PDA 102. If the User 101 does not wish to schedule another day, then the operation is finished. The User
  • the PDA 102 may then decouple the PDA 102 from the Host System 108 in order to navigate the True Day Schedule 204.
  • the User 101 may couple the PDA 102 to the Host System 108 in order to start another operation.
  • the PDA 102 will presumably contain a Daily Schedule 202 having at least one Appointment
  • the Host System 108 will concatenate with the Service Bureau 112 or the Mapping Program 106 to create a True Day Schedule 204.
  • the Host System 108 will then send, through a synchronization process, the True Day Schedule 204 to the PDA 102.
  • the User 101 may decouple the PDA 102 from the Host System 108 in order to navigate the True Day Schedule 204. h other words, the User 101 may take the PDA 102 into an automobile or other means of transportation and follow the True Day Schedule 204 in order to attend the True Day Appointments 210.
  • the PDA 102 will contain the True Day Schedule 204 having a True Day Appointment 210 corresponding to the Appointments 208 in the Daily Schedule 202.
  • the True Day Appointments 210 Based on data received from the Service Bureau 112 or the Mapping Program 106, the True Day Appointments 210 selectively contain departure times, suggested routes and approximate travel times for the User 101 to utilize in navigating the True Day Schedule 204. These suggested routes and approximate travel times are calculated from one True Day Appointment 210 to another. For example, the True Day Appointment 210 in
  • Figure 2 indicating that the User 101 should "Depart for Appt. B" can contain a suggested route and approximate travel time from the address at which the True Day Appointment 210 (A) occurred to the address where the True Day Appointment 210 (B) is scheduled to occur.
  • the True Day Appointment 210 will oftentimes take up a larger portion of the True Day Schedule 204 than an Appointment 208 does in the daily Schedule 202. This is due to the
  • True Day Appointment 210 expanding to include approximate travel time.
  • the PDAs 102, 402 or the Calendar Applications 104, 404 on the Host Systems 108, 408 contain the address data for both of the True Day Appointments 210.
  • suggested routes and approximate travel times will be calculated by the Service Bureau 112, 412 or the Mapping Program 106, 406 from the address data of the Host System 108, 408.
  • the True Day Appointments 210 may also contain a list of participants or other important data as required by the User 101.
  • the True Day Schedule 204 includes a Notification Means 212 or alert that will prompt a User 101 of a departure time or any other event in a True Day Appointment 210 that a User 101 may wish to be notified of.
  • any embodiment of the present invention may also include a PDA 102, 402, 502a-c having an ETA Notification 215, 615 ( Figures 2, 6a & 6b) as well as a Late Signal 216, 616 ( Figures 2, 6a & 6b).
  • the ETA Notification 215, 615 is set to notify the User 101, 401, 501a-c of his estimated time of arrival to the next True Day Appointment 210, 610 on the True Day Schedule 204, 604.
  • the Late Signal 215, 615 will change color or otherwise notify the User 101, 401, 501a-c by a change in appearance that the User 101, 401, 501 a-c cannot make it to the next True Day Appointment 210, 610 by the time displayed on the ETA Notification 215, 615, allowing the User 101, 401, 501a-c to notify a meeting participant that he is rumiing late.
  • the "passive" embodiment of the present invention will be described. A particular day is chosen on the User's 101 Outlook® calendar (Calendar Application 104) and the Daily Schedule 202 is displayed for which a True Day Schedule 204 is to be made.
  • This Daily Schedule 202 includes a number of Appointments 208 to be included in the True Day Schedule 204.
  • the User 101 executes the Make My Day 206 command and an existing location and mapping database (Service Bureau 112 or Mapping Program 106) is accessed to generate the True Day Schedule 204.
  • the mapping and location database (Service Bureau 112 or Mapping Program 106) will either be through an internet service such as Yahoo® or Mapquest® (Service Bureau 112 through the Internet 110), or through a fixed multi media device such as a CD-ROM (Mapping Program 106). Using this location and mapping database (Service Bureau 112 or mapping Program 106), the mapping and location database (Service Bureau 112 or mapping Program 106).
  • Outlook® schedule (Calendar Application 104) is then synchronized to the PDA 102 and the desired day is transformed into the True Day Schedule 204 and displayed on the User's 101 PDA 102.
  • the True Day Schedule 204 includes departure times for appointments, a list of participants in the scheduled meetings, suggested routes, approximated travel times (True Day Appointments 210) and Notification Means 212 to prompt the User 101 of these occurrences if desired. Additionally, the True Day Schedule 204 will include an accounting application to track mileage, expenses and costs for the User 101. The accounting application may be incorporated entirely in the PDA 102, entirely in the Calendar Application 104 or implemented in both the PDA 102 and the Calendar Application
  • FIG. 3 illustrates a flowchart of a preferred method of the present invention, h the first step 302 of this method, a handheld device is coupled to a host system. This step can be bypassed as shown by 'the path 320 in an "active" embodiment of the present invention as will be discussed below.
  • the next step 304 allows the user to select a day from the user's desktop calendar.
  • the "Make My Day" command is activated. It is then determined at the step 307 if the selected day contains an appointment. If the selected day does not contain an appointment, then at the step 309, it is determined if the user desires to schedule another day.
  • the system returns to the step 304 to allow the user to select another day from the user's desktop calendar. If, at the step 309, it is determined that the user does not want to schedule another day, then the method is finished at the step 318. If it is determined at the step 307 that the selected day does indeed contain an appointment, then at the next step 308 the system concatenates with the service bureau to generate a true day schedule. Then at the step 310, the true day schedule is sent to the handheld device. If he wishes, the user may then decouple the handheld device and navigate the true day schedule. At the step 316, it is then determined if the user wants to schedule another day. If the user does want to schedule another day, then the system jumps to the step 302 in the active embodiment or to the step 304 in the passive embodiment. If the user does not want to scheduled another day, the process ends at the step
  • Figure 4 depicts a preferred embodiment of the present invention.
  • the User 401 utilizes a GPS enabled PDA 402 with wireless capabilities.
  • the System 400 of this further embodiment includes a Calendar Application 404 located on a Host System 408.
  • a Mapping Program 406 is loaded on to the Host System 408 or a Service Bureau 412 is coupled to the Host System 408 via the Internet 410.
  • the operation of the System 400 in this preferred embodiment is similar to that of the previous embodiment.
  • the GPS enabled PDA 402 allows the User 401 to execute the Make My Day 206 command without Coupling 302 the PDA 402 to the Host System 408.
  • the User 401 may still execute the Make My Day 206 command and receive the True Day Schedule 204 through a hard wired synchronization to the Host System 408 as was explained in the previous embodiment.
  • the User 401 is able to navigate the True Day Schedule 204 with the wirelessly connected PDA 408 by connecting to the Service Bureau 412 through a wireless Internet 410 connection, or to the Mapping Program 406 through a wireless connection to the Host System 408.
  • This wireless navigation allows a User 401 to navigate the True Day Schedule 204 in real time as either Service Bureau 406, 412 would relay driving directions to the User 401 through the PDA 402, while tracking the GPS enabled PDA 402.
  • This preferred embodiment is referred to as an "active" form of the present invention and preferably includes a GPS enabled PDA 402 which will enable the User 401 to navigate the
  • This preferred "active" embodiment of Figure 4 also allows a User 401 to book a new meeting using the PDA 402 Address Database in conjunction with the Service Bureau 412 or Mapping Program 406, as well as outside sources that the PDA 402 will be able to access remotely.
  • the GPS enabled PDA 402 has the ability to be tracked by the Host System 408, enabling the Host System 408 to notify the User 401 through the PDA 402 of any changes to the True Day Schedule 604, as pictured in Figure 6a.
  • Figures 4 and 6a depict the preferred embodiment of the present invention, while Figure 6b depicts a further embodiment of the present invention.
  • the Notification Means 612 will also notify the User 410 of navigation events that occur while the User 401 navigates the True Day Schedule 604. For example, the Notification Means 612 can tell a User 401 to "turn right here" or "stop at signal in one mile.”
  • the Notification Means 612 as described with reference to Figures 4, 6a and 6b may also be incorporated in any embodiment of the present invention. Still referring to Figures 4, 6a and 6b, upon receiving such a notification from the Host System 408, the PDA 402 will add or modify the new True Day Appointment 610 to the True Day Schedule 604.
  • the PDA 402 may communicate with a desired meeting participant and enable that participant to accept or deny a meeting request. Upon receiving an acceptance, the PDA 402 will add or modify the new True Day Appointment 610 to the True Day Schedule 604. Further, the PDA 402 is able to notify the meeting participant when the User 401 is going to be late for a True Day Appointment 610. In such a case, the PDA 402 may prompt the User 401 for instruction to either send the meeting participant a phone message or an email informing the meeting participant that the User 401 is running late. In this embodiment, if the User 401, elects to send an email to the meeting participant, the email will include a map indicating the User's 401 present location and estimated time of arrival. Of course, this feature of the present invention may be incorporated into further embodiments as well.
  • the preferred "active" embodiment System 400 allows a User 401 to essentially bypass the step 302 of coupling at the beginning of System 400 operation as shown by path 320, or after the step 314 of navigating a True Day Schedule 204, as shown bypath 322.
  • This preferred "active" embodiment provides the User 401 greater mobility as well as an added freedom, as the User 401 would not be required to visit his or her office to complete the step 302 of coupling 302 the PDA 402 to the Host System 408.
  • the preferred "active" embodiment of the present invention also includes the capability to track a User 401 throughout a particular day or more specifically, throughout a particular True Day Schedule 204 (Figure 2), while notifying customers or participants in a meeting when the User 401 is rumiing late, early, rescheduling, stuck in traffic, etc.
  • the "active"embodiment of Figure 4 includes a GPS enabled PDA 402.
  • the Host System 408 is able to track the GPS enabled PDA 402 as the User 401 navigates the
  • the Host system 408 will concatenate with the Mapping Program 406 or the Service Bureau 412 through the Internet 410 to estimate a new True Day Appointment 210, and further, regenerate the User's 401 True Day Schedule 204 if needed.
  • the Host System 408 will also have the capability to contact participants or customers by email through the internet 410 in order to notify them of the User's 401 change in True Day Schedule 204.
  • Appointments 210 will be able to notify meeting participants, through email, pager, prerecorded phone messages about possible delays due to traffic, car troubles or earlier meetings that have gone over time.
  • the Host System 408 also has the capability to inquire to the meeting participants of future True Day Appointments 210 as to whether a new meeting time can be scheduled. A response to this inquiry received by the Host System 408 through the
  • Internet 410 will be re-concatenated with either the Service Bureau 412 or the Mapping Program 406, before being wirelessly transmitted to the User's 401 PDA 402, amending the current True Day Schedule 204 accordingly.
  • This preferred embodiment may also be used in the field of service calls.
  • utility installation workers or other workers employed to make house calls tend to have several appointments a day and generally have schedules that change during the course of the day due to unforeseen problems such as equipment failure or technical difficulties as well as the usual traffic problems, etc.
  • the preferred embodiment described above would be able to notify a customer of the serviceman's progress and essentially shorten the service time window given to the customer. For example, if a customer had an appointment for installation between the hours of 12PM and 2PM and the installation technician encountered a time consuming problem at his 10AM installation, the Host System 408 could call the customer after receiving an estimate of the additional time it will take for the technician to solve the problem, thus allowing the customer to alter his or her schedule accordingly. If the technician then is delayed in heavy traffic on his way to the 12PM appointment, the Host
  • This embodiment allows a customer to be apprized of the technicians' progress at all stages of the day at which the technician is delayed so that the customer may alter his or her schedule accordingly, thus allowing the customer to make his or her day as productive as possible instead of simply waiting for the technician and wasting valuable hours .
  • FIG. 5 depicts a further embodiment of the present invention. This embodiment displays a "connected" operation which will be described herein.
  • a plurality of Users 501a-c utilize the System 500 by first coupling the PDAs 502a-c to a Host System 508.
  • the PDAs 502a-c for each individual User 501a-c must either be attached to the Host System 508 separately, or alternatively, each PDA 502a-c will be connected to the Host System 508 one at a time, and a separate Make My Day 606 command ( Figures 6a & 6b) will be activated for each individual PDA 502a-c, before that particular PDA 502a-c is disconnected, hi other words, the PDAs 502a-c will "stand in line” to activate the Make My Day 606 command and receive the True Day Schedule 604.
  • the number of Users 502a-c may vary, but must include at least two.
  • the use of three (502a-c) PDAs here is for purely illustrative purposes.
  • the PDAs 502a-c utilize the Microsoft® Windows® for Pocket PC Operating System.
  • any handheld device having synchronization capabilities and a calendar system that is compatible with that of the Host System 508 may be used as a PDA 502a-c in this System 500.
  • Each of the PDAs 502a-c is coupled with the Host System 508 so as to allow synchronization between the PDAs 502a-c and the Host System 508
  • System 508 can be a desktop system or a laptop, or any personal computing system able to support the Calendar Application 504, which is contained in the memory of the Host System 508.
  • the Calendar Application 504 is Microsoft Outlook®.
  • any Calendar Application 504 configurable to be synchronized to the PDAs 502a-c maybe utilized.
  • the Service Bureau 512 and Mapping Program 506 are address and mapping databases that are coupled with the Host System 508.
  • the Service Bureau 512 and Mapping Program 506 provide mapping, directional as well as travel time data to the Host System 508 when prompted to do so.
  • One embodiment includes the fixed Mapping Program 506 in a hard disk multi media format such as, but not limited to, a CD-
  • Another embodiment includes the Service Bureau 512 coupled to the Host System 508 through the Internet 510.
  • each of the Users 501a-c initiate System 500 operation by coupling his PDA 502a-c to the Host System 508.
  • the User 501a-c selects a particular day from the Calendar Application 504 that the User 501a-c wishes to schedule. If the User 501a-c had previously entered the data for this selected day into the PDA 502a-c or previously synchronized the Calendar Application 504 to the PDA 502a-c, then a Daily Schedule 602 will appear on the particular day selected. A typical Daily Schedule 602 would appear on the PDA 502a-c as shown in Figure 6a. The PDA 502a-c view will be shown for ease in explanation.
  • the User 501 a-c then activates the Make My
  • the Calendar Application 504 will prompt the User 501a-c as to whether the User 501a-c wishes to select another day. If so, the User 501 a-c may again select a particular Daily Schedule 602 from the Calendar Application 504 the User 501a-c wishes to schedule. If the User 501a-c does not wish to select a new day, then the operation is finished. As stated earlier, this method can be repeated for each of the User's 501a-c PDA 502a-c.
  • the Calendar Application 504 will concatenate with the Service Bureau 512 and Mapping Program 506 to create a True Day Schedule 604.
  • the True Day Schedule 604 is sent to the appropriate PDA 502a-c.
  • the User 501 a-c may then decouple the PDA from the Host System 508 in order to navigate the True Day Schedule 604.
  • the User 501 a-c may couple the PDA 502a-c to the Host System 508 in order to start another operation. If the User 501a-c does not wish to schedule another day, then the operation is finished.
  • the PDA 502a-c will presumably contain a Daily Schedule 602 having at least one Appointment 608.
  • the Host System 508 will concatenate with the Service Bureau 512 or Mapping Program 506 to create a True Day Schedule 604.
  • the Host System 508 will then send, through a synchronization process, the True Day Schedule 604 to the PDA 502a-c.
  • the User 501a-c may decouple the PDA 502a-c from the Host System 508 in order to navigate the True Day Schedule 604.
  • the User 501 a-c may take the PDA 502a-c into an automobile or other means of transportation and follow the True Day Schedule 604 in order to attend the True Day Appointment 610.
  • the PDA 502a-c will contain the True Day Schedule 604 having a True Day Appointment 610 corresponding to the Appointments 608 in the Daily Schedule 602. Based on data received from the Service
  • the True Day Appointments 610 preferably contain departure times, suggested routes and approximate travel times for the User 501 a-c to utilize in navigating the True Day Schedule 604. These suggested routes and approximate travel times can be calculated from one True Day Appointment 610 to another. For example, the True Day Appointment 610 in Figure 6a indicating that the User 501a-c should "Depart for Appt. B" can contain a suggested route and approximate travel time from the address at which the True Day Appointment 610 (A) occurred to the address where the True Day Appointment 610 (B) is scheduled to occur.
  • the PDA 502a-c or the Calendar Application 504 on the Host System 508 contains the address data for both of the True Day Appointments 610.
  • suggested routes and approximate travel times will be calculated by the Service Bureau 512 or Mapping Program 506 from the address data of the Host System 508.
  • the True Day Schedule 604 includes a Notification Means 612 that will prompt a User 501 a-c of a departure time or any other event in a True Day Appointment 610 that a User 501a-c may wish to be notified of.
  • an alternative embodiment of the present invention includes a True Day Appointment 610 having the Travel Times 620 separate and not incorporated in to the Appointments 608 and the Participants/Instructions 614 list.
  • the True Day Appointments 610 may also contain a list of Participants/Instructions 614 as required by the User 501a-c.
  • This list of Participants/histructions 614 will provide the User 501a-c with a list of all of the Users 501a- c currently navigating the common True Day Schedule 604.
  • This list of Participants/Instructions 614 will also contain the location of each User 501a-c in GPS coordinates and directions and travel time to connect with those Users 501a-c.
  • Such an application will prove useful in such cases as a caravan whereby one User 501 a-c may or may not be deemed the leader, allowing the Users 501a-c to coordinate routes, rest stops and to generally track the fleet in the event that one or more Users 501a-c gets lost.
  • This embodiment may also be useful in a dispatch or house call type application as well.
  • This "connected" embodiment of the present invention will include the elements of the previous embodiments, and also will include Means for Notifying 612 the departing parties (Users 501 a-c) of the right time of departure and means for notifying the hosting or lead party (if one is selected) of the anticipated time of arrival, e.g. on time, too early, too late, etc.
  • the "connected" model then may utilize a dynamic or persistent buddy list definition (Participants/Instructions 614) for the trip which would reveal to Users 501a-c their location and expected time of arrival with a text message or with a map.
  • the True Day Schedule 604 after tracking the stray car through its GPS enabled PDA 502a-c, will be altered by providing new driving instructions in the specific True Day Appointment 610 in the Participants/Instructions 614 portion.
  • Such an embodiment will allow a group of cars to stay together and provide information to correct driving errors or occurrences through the PDAs 502a-c.
  • the "connected" embodiment of Figure 5 also allows a User 501 a-c to book a new meeting using the PDA 502a-c Address Database in conjunction with the Service Bureau 512 or Mapping Program 506, as well as outside sources that the PDA 502a-c will be able to access remotely.
  • the GPS enabled PDA 502a-c has the ability to be tracked by the Host System 508, enabling the Host System 508 to notify the User 501 a-c through the PDA 502a-c of any changes to the True Day Schedule 604, as pictured in Figures 5, 6a and 6b. Still referring to Figures 5, 6a and 6b, upon receiving such a notification from the Host System 508, the PDA 502a-c will add or modify the new True Day Appointment 610 to the True Day Schedule 604. Alternatively, the PDA 502a-c may communicate with a desired meeting participant and enable that participant to accept or deny a meeting request. Upon receiving an acceptance, the PDA 502a-c will add or modify the new True Day Appointment 610 to the

Abstract

The present invention is a system and method that provides the scheduling capabilities of a personal calendaring system while incorporating the services available to address and mapping databases users and GPS users. The present invention is a system and method that utilizes a user’s existing personal digital assistant or equivalent and contact information residing on an enterprise server to automatically compile appointments, trips and travel times to create a travel schedule. The system and method can then concatenate the calendar schedule with the travel schedule to get a true day schedule. The true day schedule may include departure times for appointments, lists of participants in the scheduled meetings, may notify departing parties of correct departure times and may notify the hosting parties of the anticipated time of arrival.

Description

METHOD AND APPARATUS FOR A CALENDAR TRACKING AND
MONITORING SERVICE
RELATED APPLICATIONS: This Patent Application claims priority under 35 U.S.C. §119(e) of the co-pending
United States Provisional Patent Application, Serial No. 60/389,037, filed June 13, 2002, and entitled "METHOD OF AND APPARATUS FOR IN VEHICLE OPERATION OF HANDHELD DEVICES INCLUDING LOW VOLTAGE POWER SOURCE AND CALENDAR TRACKING AND MONITORING SERVICE". The Provisional Patent Application, Serial No. 60/389,037, filed June 13, 2002, and entitled "METHOD OF AND APPARATUS FOR IN VEHICLE OPERATION OF HANDHELD DEVICES INCLUDING LOW VOLTAGE POWER SOURCE AND CALENDAR TRACKING AND MONITORING SERVICE" is also hereby incorporated by reference in its entirety.
FIELD OF THE INVENTION:
The present invention relates generally to a method and apparatus for a calendar tracking and monitoring service. More specifically, the present invention relates to a method and apparatus for generating and monitoring a user's schedule utilizing a desktop calendar application and an address and mapping database.
BACKGROUND OF THE INVENTION:
Personal calendaring systems are becoming more widespread as a necessary tool in organizing business as well as personal schedules. Personal calendaring systems have been implemented in desktop systems and laptop systems alike. It is also common for personal calendaring systems to be implemented on personal digital assistants (PDAs) or other handheld devices, including portable telephones. Personal calendaring systems in a desktop or laptop system (host system) can be synchronized to a compatible system on a handheld device. Synchronization allows a user to keep schedule information current on both the handheld device as well as on the host system. Appointments are readily kept on the aforementioned calendaring systems. Such appointments usually contain scheduled times, location data, participants, duration and other data associated with the appointment as specified by the user.
Address and mapping databases are also available through internet outlets such as
Yahoo® and Mapquest®, and also through similar vendors in a disk or CD-Rom format. Such databases are able to map locations based on address data supplied by a user and can also provide driving routes based on two addresses.
Further, there is currently available a Global Positioning System (GPS) whereby a device or person having GPS capabilities can be located or tracked using GPS satellites.
Such capabilities are now becoming available in cellular phones, automobiles, wrist watches and pagers, as well as other handheld devices such as PDAs. There is currently no system that provides the scheduling capabilties of a personal calendaring system that incorporates the services available to address and mapping databases users and GPS users.
SUMMARY OF THE INVENTION:
The present invention is a system and method that provides the scheduling capabilities of a personal calendaring system while incorporating the services available to address and mapping database users and GPS users. The present invention is a system and method that utilizes a user's existing personal digital assistant or equivalent and contact information residing on a host system to automatically compile appointments, trips and travel times to create a travel schedule. The system and method can then concatenate the calendar schedule with the travel schedule to get a true day schedule. The true day schedule may include departure times for appointments, lists of participants in the scheduled meetings, may notify departing parties of correct departure times and may notify the hosting parties of the anticipated time of arrival.
An embodiment of the present invention includes a calendar tracking, monitoring and communication system having a desktop calendar application containing a daily schedule wherein a user selects a specific day having at least one appointment, a service bureau coupled with the desktop calendar application, the service bureau containing an address and mapping database and a handheld device coupled with the desktop calendar application, wherein when the user activates a scheduling command for the specific day, the daily schedule concatenates with the service bureau, sending a true day schedule to the handheld device.
The handheld device containing the true day schedule is selectively decoupled after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule. The true day schedule generates a departure time based on a travel time for each of the at least one appointments, a list of participating individuals for each of the at least one appointments wherein the list of participating individuals is notified by an email with a map or a voice mail when the user is late, a suggested route for the user to follow to attend each of the at least one appointments and an approximate travel time estimation. The true day schedule includes an estimated time of arrival and an alerting means that activates when the user can not arrive before the estimated time of arrival. The handheld device includes a means for notifying the user of any of the at least one appointments as specified by the user wherein the means for notifying includes a voice notification system. The true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
The handheld device includes global positioning and wireless transmission capabilities so that the true day schedule is selectively navigated in real time by wireless transmission to the service bureau. The handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities, of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities and to transmit and receive information between a group of one or more handheld devices. The information includes global positioning system coordinates and relative movement and proximity of the handheld device to the group of one or more remote handheld devices. The system of the present invention also includes an accounting application. The accounting application records and organizes data, including mileage covered while navigating the true day schedule and expenses and costs associated with the true day schedule. The service bureau is a desktop-based application coupled with the desktop calendar application. The scheduling command is activated from the desktop calendar application or from the handheld device.
A further embodiment of the present invention includes a method of managing and navigating a personal calendar including selecting a specific day having at least one appointment from a desktop calendar application containing a daily schedule, executing a command activated by a user for the specific day, concatenating the daily schedule with a service bureau, wherein the service bureau is coupled with the desktop calendar application and contains an address and mapping database and sending a true day schedule to a handheld device, wherein the handheld device is coupled with the desktop calendar application.
The method further includes decoupling the handheld device containing the true day schedule after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule. The true day schedule includes a departure time for each of the at least one appointments, a list of participating individuals for each of the at least one appointments wherein the list of participating individuals is notified by an email with a map or a voice mail when the user is late, a suggested route for the user to follow to attend each of the at least one appointments and an approximate travel time estimation. The true day schedule includes an estimated time of arrival and an alerting means that activates when the user can not arrive before the estimated time of arrival. The handheld device includes a means for notifying the user of any of the at least one appointments as specified by the user wherein the means for notifying includes a voice notification system. The true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
The method further includes navigating the true day schedule by wireless transmission to the service bureau by equipping the handheld device with global positioning and wireless transmission capabilities. The handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities and of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities. The method further includes wirelessly communicating with a group of one or more remote handheld devices in order to exchange information, including global positioning system coordinates. The method further includes recording and organizing data using an accounting application, including mileage covered while navigating the true day schedule and expenses and costs associated with the true day schedule. The service bureau is a desktop-based application coupled with the desktop calendar application. The scheduling command is activated from the desktop calendar application or from the handheld device.
BRIEF DESCRIPTION OF THE DRAWINGS: Figure 1 illustrates a graphical representation of an embodiment of the present invention.
Figure 2 illustrates a graphical representation of the generation of the true day schedule of an embodiment of the present invention.
Figure 3 illustrates a flow chart representation of the preferred embodiment of the present invention.
Figure 4 illustrates a graphical representation of the preferred embodiment of the present invention.
Figure 5 illustrates a graphical representation of a further embodiment of the present invention. Figure 6a illustrates a graphical representation of the generation of the true day schedule of the preferred embodiment of the present invention.
Figure 6b illustrates a graphical representation of the generation of the true day schedule of a further embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT:
As illustrated in Figure 1, the present invention is a method and apparatus, which combines a User's 101 existing Personal Digital Assistant (PDA) 102 and a Personal Calendar Application (Calendar Application) 104, having both calendar and contact information with locator and mapping services from a Service Bureau 112 or a Mapping Program 106 to provide a Calendar Tracking and Monitoring Service (Service) 100. This
Service 100 concatenates the Daily Schedule 202, as illustrated in Figure 2, from the PDA 102 with a travel schedule produced with the aid of the Service Bureau 112 or Mapping Program 106, to get a True Day Schedule 204, as will be discussed in detail below.
Figure 1 depicts an embodiment of the present invention. This embodiment displays a "passive" operation which will be described herein. A User 101 utilizes the System 100 of the present invention by first coupling a PDA 102 to a Host System 108. Preferably, the PDA 102 utilizes the Microsoft® Windows® for Pocket PC Operating System. However, any handheld device having synchronization capabilities and a calendar system that is compatible with that of the Host System 108 maybe used as a PDA 102 in this System 100. Also, as used herein, the term PDA preferably includes any appropriate handheld device including devices such as a handheld computer, laptop computer, portable telephone, pager, and messaging device. The PDA 102 is coupled with the Host System 108 so as to allow synchronization between the PDA 102 and the Host System 108. The Host System 108 can be a desktop system or a laptop, or any personal computing system able to support the Calendar Application 104, which is contained in the memory of the Host System 108. Preferably, the Calendar Application 104 is Microsoft Outlook®. However, any Calendar Application 104 configurable to be synchronized to the PDA 102 maybe utilized.
Referring still to Figure 1, the Service Bureau 112 is an address and mapping database that is coupled with the Host System 108. The Service Bureau 112 provides mapping and directional information, as well as travel time data to the Host System 108 when prompted to do so. One embodiment includes the Fixed Service Bureau 106 in a disk multi media format such as, but not limited to, a CD-ROM, DVD or Floppy Disk. Another embodiment includes the Service Bureau 112 accessible to the Host System 108 through the Internet 110.
Referring simultaneously now to Figure 1 and Figure 2, the User 101 initiates the operation of System 100 by coupling the PDA 102 to the Host System 108. The User 101 then selects a particular day from the Calendar Application 104 that the User 101 wishes to schedule. If the User 101 had previously entered the data for this selected day into the PDA 102 or previously synchronized the Calendar Application 104 to the PDA 102, then a Daily Schedule 202 will appear on the particular day selected. A typical Daily Schedule 202 would appear on the PDA 102 as shown in Figure 2. The view of the Daily Schedule 202 as it typically appears on a PDA 102 view will be shown for ease in explanation. The User 101 then activates the Make My Day 206 command from either the PDA 102 or from the Calendar Application 104. The User 101 is able to execute the Make My Day 206 command from the Calendar Application 104 due to a Make My Day 206 command button that is added to the graphical user interface of the Calendar Application 104. This feature maybe added to any embodiment of the present invention. If the Daily Schedule 202 does not contain a single Appointment 208, the Calendar Application 104 will prompt the User 101 as to whether the User 101 wishes to select another day. If so, the User 101 may again select a particular Daily Schedule 202 from the Calendar Application 104 for which the User 101 wishes to schedule. If the User 101 does not wish to select a new day, then the operation is finished.
Referring still to Figure 1 and Figure 2, if the selected Daily Schedule 202 does contain at least one Appointment 208, the Calendar Application 104 will concatenate with the Service Bureau 112 or the Mapping Program 106 to create a True Day Schedule 204. Through a synchronization operation, the True Day Schedule 204 is sent to the PDA 102. If the User 101 does not wish to schedule another day, then the operation is finished. The User
101 may then decouple the PDA 102 from the Host System 108 in order to navigate the True Day Schedule 204. When the User 101 is done navigating the True Day Schedule 204, the User 101 may couple the PDA 102 to the Host System 108 in order to start another operation. Referring now to Figure 2, as stated previously, through normal synchronization, the PDA 102 will presumably contain a Daily Schedule 202 having at least one Appointment
208. h this case, after activating the Make My Day 206 command as described previously, the Host System 108 will concatenate with the Service Bureau 112 or the Mapping Program 106 to create a True Day Schedule 204. The Host System 108 will then send, through a synchronization process, the True Day Schedule 204 to the PDA 102. Now, the User 101 may decouple the PDA 102 from the Host System 108 in order to navigate the True Day Schedule 204. h other words, the User 101 may take the PDA 102 into an automobile or other means of transportation and follow the True Day Schedule 204 in order to attend the True Day Appointments 210.
Referring now to Figure 2 and Figure 4, the PDA 102 will contain the True Day Schedule 204 having a True Day Appointment 210 corresponding to the Appointments 208 in the Daily Schedule 202. Based on data received from the Service Bureau 112 or the Mapping Program 106, the True Day Appointments 210 selectively contain departure times, suggested routes and approximate travel times for the User 101 to utilize in navigating the True Day Schedule 204. These suggested routes and approximate travel times are calculated from one True Day Appointment 210 to another. For example, the True Day Appointment 210 in
Figure 2 indicating that the User 101 should "Depart for Appt. B" can contain a suggested route and approximate travel time from the address at which the True Day Appointment 210 (A) occurred to the address where the True Day Appointment 210 (B) is scheduled to occur. The True Day Appointment 210 will oftentimes take up a larger portion of the True Day Schedule 204 than an Appointment 208 does in the daily Schedule 202. This is due to the
True Day Appointment 210 expanding to include approximate travel time. Of course, this type of information will only be available if the PDAs 102, 402 or the Calendar Applications 104, 404 on the Host Systems 108, 408 contain the address data for both of the True Day Appointments 210. As a default, suggested routes and approximate travel times will be calculated by the Service Bureau 112, 412 or the Mapping Program 106, 406 from the address data of the Host System 108, 408. The True Day Appointments 210 may also contain a list of participants or other important data as required by the User 101. Lastly, the True Day Schedule 204 includes a Notification Means 212 or alert that will prompt a User 101 of a departure time or any other event in a True Day Appointment 210 that a User 101 may wish to be notified of.
Referring now to all Figures, any embodiment of the present invention may also include a PDA 102, 402, 502a-c having an ETA Notification 215, 615 (Figures 2, 6a & 6b) as well as a Late Signal 216, 616 (Figures 2, 6a & 6b). The ETA Notification 215, 615 is set to notify the User 101, 401, 501a-c of his estimated time of arrival to the next True Day Appointment 210, 610 on the True Day Schedule 204, 604. The Late Signal 215, 615 will change color or otherwise notify the User 101, 401, 501a-c by a change in appearance that the User 101, 401, 501 a-c cannot make it to the next True Day Appointment 210, 610 by the time displayed on the ETA Notification 215, 615, allowing the User 101, 401, 501a-c to notify a meeting participant that he is rumiing late. Referring back to Figure 1 and Figure 2, the "passive" embodiment of the present invention will be described. A particular day is chosen on the User's 101 Outlook® calendar (Calendar Application 104) and the Daily Schedule 202 is displayed for which a True Day Schedule 204 is to be made. This Daily Schedule 202 includes a number of Appointments 208 to be included in the True Day Schedule 204. The User 101 executes the Make My Day 206 command and an existing location and mapping database (Service Bureau 112 or Mapping Program 106) is accessed to generate the True Day Schedule 204. The mapping and location database (Service Bureau 112 or Mapping Program 106) will either be through an internet service such as Yahoo® or Mapquest® (Service Bureau 112 through the Internet 110), or through a fixed multi media device such as a CD-ROM (Mapping Program 106). Using this location and mapping database (Service Bureau 112 or mapping Program 106), the
Outlook® schedule (Calendar Application 104) is then synchronized to the PDA 102 and the desired day is transformed into the True Day Schedule 204 and displayed on the User's 101 PDA 102.
Still referring to Figure 1 and Figure 2, the True Day Schedule 204 includes departure times for appointments, a list of participants in the scheduled meetings, suggested routes, approximated travel times (True Day Appointments 210) and Notification Means 212 to prompt the User 101 of these occurrences if desired. Additionally, the True Day Schedule 204 will include an accounting application to track mileage, expenses and costs for the User 101. The accounting application may be incorporated entirely in the PDA 102, entirely in the Calendar Application 104 or implemented in both the PDA 102 and the Calendar Application
104.
Figure 3 illustrates a flowchart of a preferred method of the present invention, h the first step 302 of this method, a handheld device is coupled to a host system. This step can be bypassed as shown by 'the path 320 in an "active" embodiment of the present invention as will be discussed below. After the step 302 of coupling the handheld device to the host system, the next step 304 allows the user to select a day from the user's desktop calendar. After selecting a day from the desktop calendar, at the next step 306 the "Make My Day" command is activated. It is then determined at the step 307 if the selected day contains an appointment. If the selected day does not contain an appointment, then at the step 309, it is determined if the user desires to schedule another day. If the user chooses to schedule another day, then the system returns to the step 304 to allow the user to select another day from the user's desktop calendar. If, at the step 309, it is determined that the user does not want to schedule another day, then the method is finished at the step 318. If it is determined at the step 307 that the selected day does indeed contain an appointment, then at the next step 308 the system concatenates with the service bureau to generate a true day schedule. Then at the step 310, the true day schedule is sent to the handheld device. If he wishes, the user may then decouple the handheld device and navigate the true day schedule. At the step 316, it is then determined if the user wants to schedule another day. If the user does want to schedule another day, then the system jumps to the step 302 in the active embodiment or to the step 304 in the passive embodiment. If the user does not want to scheduled another day, the process ends at the step
318.
Figure 4 depicts a preferred embodiment of the present invention. In this preferred embodiment, the User 401 utilizes a GPS enabled PDA 402 with wireless capabilities. As in the previous embodiment, the System 400 of this further embodiment includes a Calendar Application 404 located on a Host System 408. Likewise, a Mapping Program 406 is loaded on to the Host System 408 or a Service Bureau 412 is coupled to the Host System 408 via the Internet 410. The operation of the System 400 in this preferred embodiment is similar to that of the previous embodiment. However, the GPS enabled PDA 402 allows the User 401 to execute the Make My Day 206 command without Coupling 302 the PDA 402 to the Host System 408. Preferably, the User 401 may still execute the Make My Day 206 command and receive the True Day Schedule 204 through a hard wired synchronization to the Host System 408 as was explained in the previous embodiment.
Still referring to Figure 4, the User 401 is able to navigate the True Day Schedule 204 with the wirelessly connected PDA 408 by connecting to the Service Bureau 412 through a wireless Internet 410 connection, or to the Mapping Program 406 through a wireless connection to the Host System 408. This wireless navigation allows a User 401 to navigate the True Day Schedule 204 in real time as either Service Bureau 406, 412 would relay driving directions to the User 401 through the PDA 402, while tracking the GPS enabled PDA 402. This preferred embodiment is referred to as an "active" form of the present invention and preferably includes a GPS enabled PDA 402 which will enable the User 401 to navigate the
True Day Schedule 204 in real time according to a location and mapping application (Service Bureau 406, 412) via a wireless connection.
This preferred "active" embodiment of Figure 4 also allows a User 401 to book a new meeting using the PDA 402 Address Database in conjunction with the Service Bureau 412 or Mapping Program 406, as well as outside sources that the PDA 402 will be able to access remotely. The GPS enabled PDA 402 has the ability to be tracked by the Host System 408, enabling the Host System 408 to notify the User 401 through the PDA 402 of any changes to the True Day Schedule 604, as pictured in Figure 6a.
Figures 4 and 6a depict the preferred embodiment of the present invention, while Figure 6b depicts a further embodiment of the present invention. The Notification Means 612 will also notify the User 410 of navigation events that occur while the User 401 navigates the True Day Schedule 604. For example, the Notification Means 612 can tell a User 401 to "turn right here" or "stop at signal in one mile." The Notification Means 612 as described with reference to Figures 4, 6a and 6b may also be incorporated in any embodiment of the present invention. Still referring to Figures 4, 6a and 6b, upon receiving such a notification from the Host System 408, the PDA 402 will add or modify the new True Day Appointment 610 to the True Day Schedule 604. Alternatively, the PDA 402 may communicate with a desired meeting participant and enable that participant to accept or deny a meeting request. Upon receiving an acceptance, the PDA 402 will add or modify the new True Day Appointment 610 to the True Day Schedule 604. Further, the PDA 402 is able to notify the meeting participant when the User 401 is going to be late for a True Day Appointment 610. In such a case, the PDA 402 may prompt the User 401 for instruction to either send the meeting participant a phone message or an email informing the meeting participant that the User 401 is running late. In this embodiment, if the User 401, elects to send an email to the meeting participant, the email will include a map indicating the User's 401 present location and estimated time of arrival. Of course, this feature of the present invention may be incorporated into further embodiments as well.
Referring back to Figure 3 while still referring to Figure 4, the preferred "active" embodiment System 400 allows a User 401 to essentially bypass the step 302 of coupling at the beginning of System 400 operation as shown by path 320, or after the step 314 of navigating a True Day Schedule 204, as shown bypath 322. This preferred "active" embodiment provides the User 401 greater mobility as well as an added freedom, as the User 401 would not be required to visit his or her office to complete the step 302 of coupling 302 the PDA 402 to the Host System 408. The preferred "active" embodiment of the present invention also includes the capability to track a User 401 throughout a particular day or more specifically, throughout a particular True Day Schedule 204 (Figure 2), while notifying customers or participants in a meeting when the User 401 is rumiing late, early, rescheduling, stuck in traffic, etc. As stated earlier, the "active"embodiment of Figure 4 includes a GPS enabled PDA 402. Here, the Host System 408 is able to track the GPS enabled PDA 402 as the User 401 navigates the
True Day Schedule 204 (Figure 2). If the User 401 is not navigating the True Day Schedule 204 according to the True Day Appointments 210 (Figure 2), the Host system 408, will concatenate with the Mapping Program 406 or the Service Bureau 412 through the Internet 410 to estimate a new True Day Appointment 210, and further, regenerate the User's 401 True Day Schedule 204 if needed. The Host System 408 will also have the capability to contact participants or customers by email through the internet 410 in order to notify them of the User's 401 change in True Day Schedule 204.
Referring to Figure 2 and Figure 4 simultaneously, the all day tracking capability described in the preceding paragraph will be useful in a number of applications. A salesperson or business professional having a True Day Schedule 204 full of True Day
Appointments 210 will be able to notify meeting participants, through email, pager, prerecorded phone messages about possible delays due to traffic, car troubles or earlier meetings that have gone over time. The Host System 408 also has the capability to inquire to the meeting participants of future True Day Appointments 210 as to whether a new meeting time can be scheduled. A response to this inquiry received by the Host System 408 through the
Internet 410 will be re-concatenated with either the Service Bureau 412 or the Mapping Program 406, before being wirelessly transmitted to the User's 401 PDA 402, amending the current True Day Schedule 204 accordingly.
This preferred embodiment may also be used in the field of service calls. For example, utility installation workers or other workers employed to make house calls, tend to have several appointments a day and generally have schedules that change during the course of the day due to unforeseen problems such as equipment failure or technical difficulties as well as the usual traffic problems, etc. The preferred embodiment described above would be able to notify a customer of the serviceman's progress and essentially shorten the service time window given to the customer. For example, if a customer had an appointment for installation between the hours of 12PM and 2PM and the installation technician encountered a time consuming problem at his 10AM installation, the Host System 408 could call the customer after receiving an estimate of the additional time it will take for the technician to solve the problem, thus allowing the customer to alter his or her schedule accordingly. If the technician then is delayed in heavy traffic on his way to the 12PM appointment, the Host
System could again notify the customer of this delay. This embodiment allows a customer to be apprized of the technicians' progress at all stages of the day at which the technician is delayed so that the customer may alter his or her schedule accordingly, thus allowing the customer to make his or her day as productive as possible instead of simply waiting for the technician and wasting valuable hours .
Figure 5 depicts a further embodiment of the present invention. This embodiment displays a "connected" operation which will be described herein. A plurality of Users 501a-c utilize the System 500 by first coupling the PDAs 502a-c to a Host System 508. The PDAs 502a-c for each individual User 501a-c must either be attached to the Host System 508 separately, or alternatively, each PDA 502a-c will be connected to the Host System 508 one at a time, and a separate Make My Day 606 command (Figures 6a & 6b) will be activated for each individual PDA 502a-c, before that particular PDA 502a-c is disconnected, hi other words, the PDAs 502a-c will "stand in line" to activate the Make My Day 606 command and receive the True Day Schedule 604. Of course, the number of Users 502a-c may vary, but must include at least two. The use of three (502a-c) PDAs here is for purely illustrative purposes. Preferably, the PDAs 502a-c utilize the Microsoft® Windows® for Pocket PC Operating System. However, any handheld device having synchronization capabilities and a calendar system that is compatible with that of the Host System 508 may be used as a PDA 502a-c in this System 500. Each of the PDAs 502a-c is coupled with the Host System 508 so as to allow synchronization between the PDAs 502a-c and the Host System 508 The Host
System 508 can be a desktop system or a laptop, or any personal computing system able to support the Calendar Application 504, which is contained in the memory of the Host System 508. Preferably, the Calendar Application 504 is Microsoft Outlook®. However, any Calendar Application 504 configurable to be synchronized to the PDAs 502a-c maybe utilized.
Referring still to Figure 5, the Service Bureau 512 and Mapping Program 506 are address and mapping databases that are coupled with the Host System 508. The Service Bureau 512 and Mapping Program 506 provide mapping, directional as well as travel time data to the Host System 508 when prompted to do so. One embodiment includes the fixed Mapping Program 506 in a hard disk multi media format such as, but not limited to, a CD-
ROM, DVD or Disk. Another embodiment includes the Service Bureau 512 coupled to the Host System 508 through the Internet 510.
Referring simultaneously now to Figures 5, 6a and 6b, each of the Users 501a-c initiate System 500 operation by coupling his PDA 502a-c to the Host System 508. The User 501a-c then selects a particular day from the Calendar Application 504 that the User 501a-c wishes to schedule. If the User 501a-c had previously entered the data for this selected day into the PDA 502a-c or previously synchronized the Calendar Application 504 to the PDA 502a-c, then a Daily Schedule 602 will appear on the particular day selected. A typical Daily Schedule 602 would appear on the PDA 502a-c as shown in Figure 6a. The PDA 502a-c view will be shown for ease in explanation. The User 501 a-c then activates the Make My
Day 606 command from either the PDA 502a-c or from the Calendar Application 504. If the Daily Schedule 602 does not contain a single Appointment 608, the Calendar Application 504 will prompt the User 501a-c as to whether the User 501a-c wishes to select another day. If so, the User 501 a-c may again select a particular Daily Schedule 602 from the Calendar Application 504 the User 501a-c wishes to schedule. If the User 501a-c does not wish to select a new day, then the operation is finished. As stated earlier, this method can be repeated for each of the User's 501a-c PDA 502a-c.
Referring still to Figures 5, 6a and 6b, if the selected Daily Schedule 602 does contain at least one Appointment 608, the Calendar Application 504 will concatenate with the Service Bureau 512 and Mapping Program 506 to create a True Day Schedule 604. Through a synchronization operation, the True Day Schedule 604 is sent to the appropriate PDA 502a-c. ( The User 501 a-c may then decouple the PDA from the Host System 508 in order to navigate the True Day Schedule 604. When the User 501a-c is done navigating the True Day Schedule 604, the User 501 a-c may couple the PDA 502a-c to the Host System 508 in order to start another operation. If the User 501a-c does not wish to schedule another day, then the operation is finished.
Referring now to the preferred embodiment as depicted in Figure 6a, as stated previously, through normal synchronization, the PDA 502a-c will presumably contain a Daily Schedule 602 having at least one Appointment 608. In this case, after activating the Make My Day 606 command as described previously in Figure 3, the Host System 508 will concatenate with the Service Bureau 512 or Mapping Program 506 to create a True Day Schedule 604. The Host System 508 will then send, through a synchronization process, the True Day Schedule 604 to the PDA 502a-c. Now, the User 501a-c may decouple the PDA 502a-c from the Host System 508 in order to navigate the True Day Schedule 604. In other words, the User 501 a-c may take the PDA 502a-c into an automobile or other means of transportation and follow the True Day Schedule 604 in order to attend the True Day Appointment 610.
Referring still to the preferred embodiment as depicted in Figure 6a, the PDA 502a-c will contain the True Day Schedule 604 having a True Day Appointment 610 corresponding to the Appointments 608 in the Daily Schedule 602. Based on data received from the Service
Bureau 512 or Mapping Program 506, the True Day Appointments 610 preferably contain departure times, suggested routes and approximate travel times for the User 501 a-c to utilize in navigating the True Day Schedule 604. These suggested routes and approximate travel times can be calculated from one True Day Appointment 610 to another. For example, the True Day Appointment 610 in Figure 6a indicating that the User 501a-c should "Depart for Appt. B" can contain a suggested route and approximate travel time from the address at which the True Day Appointment 610 (A) occurred to the address where the True Day Appointment 610 (B) is scheduled to occur. Of course, this type of information will only be available if the PDA 502a-c or the Calendar Application 504 on the Host System 508 contains the address data for both of the True Day Appointments 610. As a default, suggested routes and approximate travel times will be calculated by the Service Bureau 512 or Mapping Program 506 from the address data of the Host System 508. Lastly, the True Day Schedule 604 includes a Notification Means 612 that will prompt a User 501 a-c of a departure time or any other event in a True Day Appointment 610 that a User 501a-c may wish to be notified of. Referring to Figure 6b, an alternative embodiment of the present invention includes a True Day Appointment 610 having the Travel Times 620 separate and not incorporated in to the Appointments 608 and the Participants/Instructions 614 list.
Referring now to Figures 6a and 6b, the True Day Appointments 610 may also contain a list of Participants/Instructions 614 as required by the User 501a-c. This list of Participants/histructions 614 will provide the User 501a-c with a list of all of the Users 501a- c currently navigating the common True Day Schedule 604. This list of Participants/Instructions 614 will also contain the location of each User 501a-c in GPS coordinates and directions and travel time to connect with those Users 501a-c. Such an application will prove useful in such cases as a caravan whereby one User 501 a-c may or may not be deemed the leader, allowing the Users 501a-c to coordinate routes, rest stops and to generally track the fleet in the event that one or more Users 501a-c gets lost. This embodiment may also be useful in a dispatch or house call type application as well.
This "connected" embodiment of the present invention will include the elements of the previous embodiments, and also will include Means for Notifying 612 the departing parties (Users 501 a-c) of the right time of departure and means for notifying the hosting or lead party (if one is selected) of the anticipated time of arrival, e.g. on time, too early, too late, etc. The "connected" model then may utilize a dynamic or persistent buddy list definition (Participants/Instructions 614) for the trip which would reveal to Users 501a-c their location and expected time of arrival with a text message or with a map. Referring simultaneously to Figures 5, 6a and 6b, one example of how this embodiment will be particularly useful is in the case of a "convoy" or group of travelers embarking on a car trip. For example, if each auto leaving on a car trip from the San Francisco Bay Area to Lake Tahoe has a GPS enabled PDA 501a-c as described in the "connected" embodiment of the present invention, the cars will be wirelessly connected and have identical True Day Schedules 604 with identical True Day Appointments 610. If one of the cars gets separated, the True Day Schedule 604, through the Host System 508 may be altered to show how far behind the stray car is and the new expected travel times, arrival time, etc. This is effectuated by utilizing the GPS and wireless capabilities of the PDAs 502a-c. Further, if one car is separated and actually gets lost from the group, the True Day Schedule 604, after tracking the stray car through its GPS enabled PDA 502a-c, will be altered by providing new driving instructions in the specific True Day Appointment 610 in the Participants/Instructions 614 portion. Such an embodiment will allow a group of cars to stay together and provide information to correct driving errors or occurrences through the PDAs 502a-c. The "connected" embodiment of Figure 5 also allows a User 501 a-c to book a new meeting using the PDA 502a-c Address Database in conjunction with the Service Bureau 512 or Mapping Program 506, as well as outside sources that the PDA 502a-c will be able to access remotely. The GPS enabled PDA 502a-c has the ability to be tracked by the Host System 508, enabling the Host System 508 to notify the User 501 a-c through the PDA 502a-c of any changes to the True Day Schedule 604, as pictured in Figures 5, 6a and 6b. Still referring to Figures 5, 6a and 6b, upon receiving such a notification from the Host System 508, the PDA 502a-c will add or modify the new True Day Appointment 610 to the True Day Schedule 604. Alternatively, the PDA 502a-c may communicate with a desired meeting participant and enable that participant to accept or deny a meeting request. Upon receiving an acceptance, the PDA 502a-c will add or modify the new True Day Appointment 610 to the
True Day Schedule 604.
The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of the principles of construction and operation of the invention. Such reference herein to specific embodiments and details thereof is not intended to limit the scope of the claims appended hereto. For example, the application of the true day schedule of the present invention is not limited to business ventures. It will be apparent to those skilled in the art that modifications can be made in the embodiment chosen for illustration without departing from the spirit and scope of the invention.

Claims

C L A I M SWhat is claimed is:
1. A calendar tracking, monitoring and communication system, comprising: a. a desktop calendar application containing a daily schedule wherein a user selects a specific day having at least one appointment; b. a service bureau coupled with the desktop calendar application, the service bureau containing an address and mapping database; and c. a handheld device coupled with the desktop calendar application, wherein when the user activates a scheduling command for the specific day, the daily schedule concatenates with the service bureau, sending a true day schedule to the handheld device.
2. The system as claimed in claim 1, wherein the handheld device containing the true day schedule is selectively decoupled after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule.
3. The system as claimed in claim 1, wherein the true day schedule generates a departure time based on a travel time for each of the at least one appointments.
4. The system as claimed in claim 1 , wherein the true day schedule includes a list of participating individuals for each of the at least one appointments.
5. The system as claimed in claim 4, wherein the list of participating individuals is notified when the user is late for any of the at least one appointments.
6. The system as claimed in claim 5, wherein the list of participating individuals is notified by email, the email including a map showing the current location of the user.
7. The system as claimed in claim 5, wherein the list of participating individuals is notified by voice mail.
8. The system as claimed in claim 1, wherein the true day schedule includes a suggested route for the user to follow to attend each of the at least one appointments.
9. The system as claimed in claim 1, wherein the true day schedule includes an approximate travel time estimation.
10. The system as claimed in claim 1, wherein the true day schedule includes an estimated time of arrival for each of the at least one appointments.
11. The system as claimed in claim 10, wherein the true day schedule includes an alerting means for late notification that activates when the user will not arrive at one of the at least one appointments before the estimated time of arrival.
12. The system as claimed in claim 1, wherein the handheld device includes a means for notifying the user of any of the at least one appointments as specified by the user.
13. The system as claimed in claim 12, wherein the notification means includes a voice notification system to assist the user in navigation of the true day schedule.
14. The system as claimed in claim 1, wherein the true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
15. The system as claimed in claim 1, wherein the handheld device includes global positioning and wireless transmission capabilities so that the true day schedule is selectively navigated by wireless transmission to the service bureau.
16. The system as claimed in claim 15, wherein the handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities.
17. The system as claimed in claim 15, wherein the handheld device has the capability of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities.
18. The system as claimed in claim 15, wherein the handheld device has the capability to transmit and receive information between a group of one or more handheld devices.
19. The system as claimed in claim 18, wherein the information includes global positioning system coordinates and relative movement and proximity of the handheld device to the group of one or more remote handheld devices.
20. The system as claimed in claim 1, further comprising an accounting application, wherein the accounting application records and organizes data.
21. The system as claimed in claim 20, wherein the data includes mileage covered while navigating the true day schedule.
22. The system as claimed in claim 20, wherein the data includes expenses and costs associated with the true day schedule.
23. The system as claimed in claim 1 , wherein the service bureau is coupled with the desktop calendar application through an internet connection.
24. The system as claimed in claim 1 , wherein the service bureau is a desktop-based application.
25. The system as claimed in claim 1, wherein the scheduling command is activated by the user from the desktop calendar application.
26. The system as claimed in claim 1, wherein the scheduling command is activated by the user from the handheld device.
27. A method of managing and navigating a personal calendar, comprising: a. selecting a specific day having at least one appointment from a desktop calendar application containing a daily schedule; b. executing a command activated by a user for the specific day, concatenating the daily schedule with a service bureau, wherein the service bureau is coupled with the desktop calendar application and contains an address and mapping database; and c. sending a true day schedule to a handheld device, wherein the handheld device is coupled with the desktop calendar application.
28. The method as claimed in claim 27, further comprising the step of decoupling the handheld device containing the true day schedule after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule.
29. The method as claimed in claim 27, wherein the true day schedule includes a departure time for each of the at least one appointments.
30. The method as claimed in claim 27, wherein the true day schedule includes a list of participating individuals for each of the at least one appointments.
31. The method as claimed in claim 30, wherein the list of participating individuals is notified when the user is late for any of the at least one appointments.
32. The method as claimed in claim 31, wherein the list of participating individuals is notified by email, the email including a map showing the current location of the user.
33. The method as claimed in claim 31, wherein the list of participating individuals is notified by voice mail.
34. The method as claimed in claim 27, wherein the true day schedule includes a suggested route for the user to follow to attend each of the at least one appointments.
35. The method as claimed in claim 27, wherein the true day schedule includes an approximate travel time estimation.
36. The method as claimed in claim 27, wherein the true day schedule includes an estimated time of arrival for each of the at least one appointments.
37. The method as claimed in claim 36, wherein the true day schedule includes an alerting means for late notification that activates when the user will not arrive at one of the at least one appointments before the estimated time of arrival.
38. The method as claimed in claim 27, wherein the handheld device includes a means for notifying the user of any of the at least one appointment as specified by user.
39. The method as claimed in claim 38, wherein the notification means includes a voice notification system to assist the user in navigation of the true day schedule.
40. The method as claimed in claim 27, wherein the true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
41. The method as claimed in claim 27, further comprising the step of navigating the true day schedule by wireless transmission to the service bureau by equipping the handheld device with global positioning and wireless transmission capabilities.
42. The method as claimed in claim 41 , wherein the handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities.
43. The method as claimed in claim 41 , wherein the handheld device has the capability of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities.
44. The method as claimed in claim 41, further comprising the step of wirelessly communicating with a group of one or more remote handheld devices in order to exchange information.
45. The method as claimed in claim 44, wherein the information includes global positioning system coordinates.
46. The method as claimed in claim 27, further comprising the step of recording and organizing data using an accounting application.
47. The method as claimed in claim 46, wherein the data includes mileage covered while navigating the true day schedule.
48. The method as claimed in claim 46, wherein the data includes expenses and costs associated with the true day schedule.
49. The method as claimed in claim 27, wherein the service bureau is coupled with the desktop calendar application through an internet connection.
50. The method as claimed in claim 27, wherein the service bureau is a desktop-based application.
51. The method as claimed in claim 27, wherein the scheduling command is activated by the user from the desktop calendar application.
52. The method as claimed in claim 27, wherein the scheduling command is activated by the user from the handheld device.
53. A calendar tracking, monitoring and communication system, comprising: a. means for selecting a specific day having at least one appointment from a desktop calendar application containing a daily schedule; b. means for executing a command activated by a user for the specific day, concatenating the daily schedule with a service bureau, wherein the service bureau is coupled with the desktop calendar application and contains an address and mapping database; and c. means for sending a true day schedule to a handheld device, wherein the handheld device is coupled with the desktop calendar application.
54. The system as claimed in claim 53, further comprising means for decoupling the handheld device containing the true day schedule after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule.
55. The system as claimed in claim 53, wherein the true day schedule includes a departure time for each of the at least one appointments.
56. The system as claimed in claim 53, wherein the true day schedule includes a list of participating individuals for each of the at least one appointments.
57. The system as claimed in claim 56, wherein the list of participating individuals is notified when the user is late for any of the at least one appointments.
58. The system as claimed in claim 57, wherein the list of participating individuals is notified by email, the email including a map showing the current location of the user.
59. The system as claimed in claim 57, wherein the list of participating individuals is notified by voice mail.
60. The system as claimed in claim 53, wherein the true day schedule includes a suggested route for a user to follow to attend each of the at least one appointments.
61. The system as claimed in claim 53, wherein the true day schedule includes an approximate travel time estimation.
62. The system as claimed in claim 53, wherein the true day schedule includes an estimated time of arrival for each of the at least one appointments.
63. The system as claimed in claim 62, wherein the true day schedule includes an alerting means for late notification that activates when the user will not arrive at one of the at least one appointments before the estimated time of arrival.
64. The system as claimed in claim 53, wherein the handheld device includes a means for notifying the user of any of the at least one appointment as specified by user.
65. The system as claimed in claim 64, wherein the notification means includes a voice notification system to assist the user in navigation of the true day schedule.
66. The system as claimed in claim 53, wherein the true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
67. The system as claimed in claim 53, further comprising means for navigating the true day schedule by wireless transmission to the service bureau by equipping the handheld device with global positioning and wireless transmission capabilities.
68. The system as claimed in claim 67, wherein the handheld device has the capability of being tracked using the global positioning and wireless transmission capabilities.
69. The system as claimed in claim 67, wherein the handheld device has the capability of being notified of a change to the true day schedule using the global positioning and wireless transmission capabilities.
70. The system as claimed in claim 67, further comprising means for wirelessly communicating with a group of one or more remote handheld devices in order to exchange information.
71. The system as claimed in claim 56, wherein the information includes global positioning system coordinates.
72. The system as claimed in claim 53, further comprising means for recording and organizing data using an accounting application.
73. The system as claimed in claim 72, wherein the data includes mileage covered while navigating the true day schedule.
74. The system as claimed in claim 72, wherein the data includes expenses and costs associated with the true day schedule.
75. The system as claimed in claim 53, wherein the service bureau is coupled with the desktop calendar application through an internet connection.
76. The system as claimed in claim 53, wherein the service bureau is a desktop-based application.
77. The system as claimed in claim 53, wherein the scheduling command is activated by the user from the desktop calendar application.
78. The system as claimed in claim 53, wherein the scheduling command is activated by the user from the handheld device.
79. A calendar tracking, monitoring and communication system, comprising: a. a desktop calendar application containing a daily schedule wherein a user selects a specific day having at least one appointment; b. a service bureau coupled with the desktop calendar application, the service bureau containing an address and mapping database; and c. a handheld device including global positioning and wireless transmission capabilities coupled with the desktop calendar application; wherein when the user activates a scheduling command for the specific day, the daily schedule concatenates with the service bureau, sending a true day schedule to the handheld device and further wherein the true day schedule is selectively navigated by wireless transmission to the service bureau, thereby having the capability of being tracked and notified of a change to the true day schedule using the global positioning and wireless transmission capabilities.
80. The system as claimed in claim 79, wherein the handheld device containing the true day schedule is selectively decoupled after receiving the true day schedule from the desktop calendar application to facilitate mobile access to the true day schedule.
81. The system as claimed in claim 79, wherein the true day schedule generates a departure time based on a travel time for each of the at least one appointments.
82. The system as claimed in claim 79, wherein the true day schedule includes a list of participating individuals for each of the at least one appointments.
83. The system as claimed in claim 82, wherein the list of participating individuals is notified when the user is late for any of the at least one appointments.
84. The system as claimed in claim 83, wherein the list of participating individuals is notified by email, the email including a map showing the current location of the user.
85. The system as claimed in claim 83, wherein the list of participating individuals is notified by voice mail.
86. The system as claimed in claim 79, wherein the true day schedule includes a suggested route for the user to follow to attend each of the at least one appointments.
87. The system as claimed in claim 79, wherein the true day schedule includes an approximate travel time estimation.
88. The system as claimed in claim 79, wherein the true day schedule includes an estimated time of arrival for each of the at least one appointments.
89. The system as claimed in claim 88, wherein the true day schedule includes an alerting means for late notification that activates when the user will not arrive at one of the at least one appointments before the estimated time of arrival.
90. The system as claimed in claim 79, wherein the handheld device includes a means for notifying the user of any of the at least one appointments as specified by the user.
91. The system as claimed in claim 90, wherein the notification means includes a voice notification system to assist the user in navigation of the true day schedule.
92. The system as claimed in claim 79, wherein the true day schedule is selectively concatenated for any day in the daily schedule having at least one appointment.
93. The system as claimed in claim 79, wherein the handheld device has the capability to transmit and receive information between a group of one or more handheld devices.
94. The system as claimed in claim 93, wherein the information includes global positioning system coordinates and relative movement and proximity of the handheld device to the group of one or more remote handheld devices.
95. The system as claimed in claim 79, further comprising an accounting application, wherein the accounting application records and organizes data.
96. The system as claimed in claim 95, wherein the data includes mileage covered while navigating the true day schedule.
97. The system as claimed in claim 95, wherein the data includes expenses and costs associated with the true day schedule.
98. The system as claimed in claim 79, wherein the service bureau is coupled with the desktop calendar application through an internet connection.
99. The system as claimed in claim 79, wherein the service bureau is a desktop-based application.
100. The system as claimed in claim 79, wherein the scheduling command is activated by the user from the desktop calendar application.
101. The system as claimed in claim 79, wherein the scheduling command is activated by the user from the handheld device.
PCT/US2003/018717 2002-06-13 2003-06-13 Method and apparatus for a calendar tracking and monitoring service WO2003107129A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003236513A AU2003236513A1 (en) 2002-06-13 2003-06-13 Method and apparatus for a calendar tracking and monitoring service

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US38903702P 2002-06-13 2002-06-13
US60/389,037 2002-06-13
US34650803A 2003-01-15 2003-01-15
US10/346,508 2003-01-15

Publications (2)

Publication Number Publication Date
WO2003107129A2 true WO2003107129A2 (en) 2003-12-24
WO2003107129A3 WO2003107129A3 (en) 2004-04-15

Family

ID=29739381

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/018717 WO2003107129A2 (en) 2002-06-13 2003-06-13 Method and apparatus for a calendar tracking and monitoring service

Country Status (2)

Country Link
AU (1) AU2003236513A1 (en)
WO (1) WO2003107129A2 (en)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102005046153A1 (en) * 2005-09-27 2007-04-05 Siemens Ag Tuning time determining method for e.g. conference, involves comparing actually determined geographic position of participants with preset position of scheduled events, based on determined distance of positions/motion speed of participants
EP1944724A1 (en) 2007-01-11 2008-07-16 Harman Becker Automotive Systems GmbH Method for destination setting for a navigation system
EP1944578A2 (en) 2007-01-11 2008-07-16 Harman Becker Automotive Systems GmbH Method for calculating a route to a destination for a navigation system
FR2919743A1 (en) * 2007-07-31 2009-02-06 Alcatel Lucent Sas METHOD AND SOFTWARE FOR VERIFYING ELECTRONIC AGENDA
US20090070708A1 (en) * 2007-09-12 2009-03-12 Palm, Inc. Display of Information of Interest
EP2395462A1 (en) * 2010-06-10 2011-12-14 Research In Motion Limited Automated calendar reconciliation
US20120066629A1 (en) * 2010-09-15 2012-03-15 Seungwon Lee Method and apparatus for displaying schedule in mobile communication terminal
US8335494B2 (en) 2010-12-30 2012-12-18 Ford Global Technologies, Llc Provisioning of callback reminders on a vehicle-based computing system
US8375320B2 (en) 2010-06-22 2013-02-12 Microsoft Corporation Context-based task generation
US8386929B2 (en) 2010-06-22 2013-02-26 Microsoft Corporation Personal assistant for task utilization
US8406938B2 (en) 2011-05-19 2013-03-26 Ford Global Technologies, Llc Remote operator assistance for one or more user commands in a vehicle
US8738574B2 (en) 2010-12-20 2014-05-27 Ford Global Technologies, Llc Automatic wireless device data maintenance
US8812065B2 (en) 2010-06-07 2014-08-19 Ford Global Technologies, Llc System and method for monitoring the location of a communication device in a vehicle based on signal strength
US8855909B2 (en) 2008-01-07 2014-10-07 Harman International Industries, Inc. Route determining system for a vehicle with navigation system
US9071568B2 (en) 2013-01-07 2015-06-30 Ford Global Technologies, Llc Customer-identifying email addresses to enable a medium of communication that supports many service providers
EP2885933A4 (en) * 2012-08-16 2016-03-23 Samsung Electronics Co Ltd Schedule management method, schedule management server, and mobile terminal using the method
US9612797B2 (en) 2011-08-25 2017-04-04 Ford Global Technologies, Llc Method and apparatus for a near field communication system to exchange occupant information
US9752890B2 (en) 2006-03-31 2017-09-05 Facebook, Inc. Identifying a result responsive to a current location of a client device
US9789788B2 (en) 2013-01-18 2017-10-17 Ford Global Technologies, Llc Method and apparatus for primary driver verification
US9867014B2 (en) 2006-12-29 2018-01-09 Facebook, Inc. Meeting notification and modification service
US10089310B2 (en) 2014-01-14 2018-10-02 Microsoft Technology Licensing, Llc Complementary and shadow calendars
US10163074B2 (en) 2010-07-07 2018-12-25 Ford Global Technologies, Llc Vehicle-based methods and systems for managing personal information and events
US10192176B2 (en) 2011-10-11 2019-01-29 Microsoft Technology Licensing, Llc Motivation of task completion and personalization of tasks and lists
US11120408B2 (en) 2014-05-06 2021-09-14 Microsoft Technology Licensing, Llc Scheduling conflict notification

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9361090B2 (en) 2014-01-24 2016-06-07 Ford Global Technologies, Llc Apparatus and method of software implementation between a vehicle and mobile device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5790974A (en) * 1996-04-29 1998-08-04 Sun Microsystems, Inc. Portable calendaring device having perceptual agent managing calendar entries
US5991742A (en) * 1996-05-20 1999-11-23 Tran; Bao Q. Time and expense logging system
US6529136B2 (en) * 2001-02-28 2003-03-04 International Business Machines Corporation Group notification system and method for implementing and indicating the proximity of individuals or groups to other individuals or groups

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5790974A (en) * 1996-04-29 1998-08-04 Sun Microsystems, Inc. Portable calendaring device having perceptual agent managing calendar entries
US5991742A (en) * 1996-05-20 1999-11-23 Tran; Bao Q. Time and expense logging system
US6529136B2 (en) * 2001-02-28 2003-03-04 International Business Machines Corporation Group notification system and method for implementing and indicating the proximity of individuals or groups to other individuals or groups

Cited By (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102005046153A1 (en) * 2005-09-27 2007-04-05 Siemens Ag Tuning time determining method for e.g. conference, involves comparing actually determined geographic position of participants with preset position of scheduled events, based on determined distance of positions/motion speed of participants
US9752890B2 (en) 2006-03-31 2017-09-05 Facebook, Inc. Identifying a result responsive to a current location of a client device
US9867014B2 (en) 2006-12-29 2018-01-09 Facebook, Inc. Meeting notification and modification service
EP1944578A3 (en) * 2007-01-11 2011-11-30 Harman Becker Automotive Systems GmbH Method for calculating a route to a destination for a navigation system
EP1944724A1 (en) 2007-01-11 2008-07-16 Harman Becker Automotive Systems GmbH Method for destination setting for a navigation system
EP1944578A2 (en) 2007-01-11 2008-07-16 Harman Becker Automotive Systems GmbH Method for calculating a route to a destination for a navigation system
FR2919743A1 (en) * 2007-07-31 2009-02-06 Alcatel Lucent Sas METHOD AND SOFTWARE FOR VERIFYING ELECTRONIC AGENDA
EP2026263A1 (en) * 2007-07-31 2009-02-18 Alcatel Lucent Electronic diary verification method and software
US20090070708A1 (en) * 2007-09-12 2009-03-12 Palm, Inc. Display of Information of Interest
US8855909B2 (en) 2008-01-07 2014-10-07 Harman International Industries, Inc. Route determining system for a vehicle with navigation system
US9774717B2 (en) 2010-06-07 2017-09-26 Ford Global Technologies, Llc System and method for detecting the location of a communication device in a vehicle based on camera detection
US8812065B2 (en) 2010-06-07 2014-08-19 Ford Global Technologies, Llc System and method for monitoring the location of a communication device in a vehicle based on signal strength
EP2395462A1 (en) * 2010-06-10 2011-12-14 Research In Motion Limited Automated calendar reconciliation
US8375320B2 (en) 2010-06-22 2013-02-12 Microsoft Corporation Context-based task generation
US8386929B2 (en) 2010-06-22 2013-02-26 Microsoft Corporation Personal assistant for task utilization
US10163074B2 (en) 2010-07-07 2018-12-25 Ford Global Technologies, Llc Vehicle-based methods and systems for managing personal information and events
US20120066629A1 (en) * 2010-09-15 2012-03-15 Seungwon Lee Method and apparatus for displaying schedule in mobile communication terminal
US9558254B2 (en) 2010-12-20 2017-01-31 Ford Global Technologies, Llc Automatic wireless device data maintenance
US8738574B2 (en) 2010-12-20 2014-05-27 Ford Global Technologies, Llc Automatic wireless device data maintenance
US8457608B2 (en) 2010-12-30 2013-06-04 Ford Global Technologies, Llc Provisioning of callback reminders on a vehicle-based computing system
US8335494B2 (en) 2010-12-30 2012-12-18 Ford Global Technologies, Llc Provisioning of callback reminders on a vehicle-based computing system
US8406938B2 (en) 2011-05-19 2013-03-26 Ford Global Technologies, Llc Remote operator assistance for one or more user commands in a vehicle
US8972081B2 (en) 2011-05-19 2015-03-03 Ford Global Technologies, Llc Remote operator assistance for one or more user commands in a vehicle
US9612797B2 (en) 2011-08-25 2017-04-04 Ford Global Technologies, Llc Method and apparatus for a near field communication system to exchange occupant information
US9940098B2 (en) 2011-08-25 2018-04-10 Ford Global Technologies, Llc Method and apparatus for a near field communication system to exchange occupant information
US10261755B2 (en) 2011-08-25 2019-04-16 Ford Global Technologies, Llc Method and apparatus for a near field communication system to exchange occupant information
US10192176B2 (en) 2011-10-11 2019-01-29 Microsoft Technology Licensing, Llc Motivation of task completion and personalization of tasks and lists
EP2885933A4 (en) * 2012-08-16 2016-03-23 Samsung Electronics Co Ltd Schedule management method, schedule management server, and mobile terminal using the method
US10643134B2 (en) 2012-08-16 2020-05-05 Samsung Electronics Co., Ltd. Schedule management method, schedule management server, and mobile terminal using the method
US9071568B2 (en) 2013-01-07 2015-06-30 Ford Global Technologies, Llc Customer-identifying email addresses to enable a medium of communication that supports many service providers
US9789788B2 (en) 2013-01-18 2017-10-17 Ford Global Technologies, Llc Method and apparatus for primary driver verification
US10089310B2 (en) 2014-01-14 2018-10-02 Microsoft Technology Licensing, Llc Complementary and shadow calendars
US11120408B2 (en) 2014-05-06 2021-09-14 Microsoft Technology Licensing, Llc Scheduling conflict notification

Also Published As

Publication number Publication date
AU2003236513A1 (en) 2003-12-31
AU2003236513A8 (en) 2003-12-31
WO2003107129A3 (en) 2004-04-15

Similar Documents

Publication Publication Date Title
WO2003107129A2 (en) Method and apparatus for a calendar tracking and monitoring service
US7990266B2 (en) Location- and direction-enhanced automatic reminders of appointments
US10044851B2 (en) Methods, systems, and computer program products for schedule management based on locations of wireless devices
US6898569B1 (en) Method and apparatus for advanced scheduling and messaging system
US20030027558A1 (en) Method for executing a service for organisation of meetings for participants in a communications network, and service computer and program module for this
US6732080B1 (en) System and method of providing personal calendar services
US9146115B2 (en) Location enhanced meetings and collaboration
EP1363221B1 (en) Increasing the level of automation when scheduling and managing meetings
CN1319360C (en) System and method of access and recording information on reference course point
US20060058948A1 (en) Recordable location-based reminder system organizer
US8254962B2 (en) Scheduling tasks dynamically depending on the location of a mobile user
JP3427063B2 (en) System and method for accessing and recording messages at coordinated waypoints
US20060155591A1 (en) Systems, methods, and media for managing a travel itinerary
US20150312713A1 (en) Location based event reminder for mobile device
US20100274865A1 (en) Travel time dependent notification system
US20110054976A1 (en) Scheduling Recurring Calendar Events
JP5010821B2 (en) Resource selection based on skills and availability of telecommunication systems
US20070233635A1 (en) Systems and methods for organizing an event and tracking attendance status
CN102750627A (en) Methods for using and managing electronic calendars in vehicle
JP2005228020A (en) Schedule management system
US20090153353A1 (en) Method and apparatus for generating a notification at a computing device
US6871141B2 (en) Vehicle navigation system
JP3040233U (en) PHS navigation system
Martin Tradies working with virtual assistants
US20140278680A1 (en) Method for alerting people to events

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP