throbber
(12) United States Patent
`Suzuki
`
`USOO6680675B1
`(10) Patent No.:
`US 6,680,675 B1
`(45) Date of Patent:
`Jan. 20, 2004
`
`(54) INTERACTIVE TO-DO LIST ITEM
`NOTIFICATION SYSTEM INCLUDING GPS
`INTERFACE
`
`(75) Inventor: Hikaru Suzuki, Gunma-machi (JP)
`(73) Assignee: Fujitsu Limited, Kanagawa (JP)
`(*) Notice:
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 380 days.
`(21) Appl. No.: 09/598,094
`1-1.
`Jun. 21, 2000
`(22) Filed:
`(51) Int. Cl." ................................................ G08G 1/123
`(52) U.S. Cl. .................. 340/988; 340/825.49; 455/456;
`455/457; 342/357.01; 342/357.17; 342/450;
`701/213; 701/300
`(58) Field of Search ................................. 340/988,995,
`340/996, 825.49, 425.5; 701/207, 208, 201,
`211, 213, 214, 300; 455/456, 457; 342/357.01,
`357.17, 450, 357.06, 357.08, 357.13
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`4,831,526 A 5/1989 Luchs et al. ................ 364/401
`5,111,391 A
`5/1992 Fields et al. ................ 364/401
`5,182,705 A
`1/1993 Barr et al. .................. 364/401
`5,557.515 A
`9/1996 Abbruzzese et al.
`... 364/401
`5,559,548 A 9/1996 Davis et al. ................... 348/6
`5,644,722 A 7/1997 Miyamoto et al.
`... 395/209
`5,648,770 A
`7/1997 Ross .......................... 340/988
`5.684990 A * 11/1997 Boothby ..................... 707/203
`5,826,260 A 10/1998 Byrd, Jr. et al. ................ 707/5
`5,844.558 A 12/1998 Kumar et al. .....
`... 345/339
`5,850,214 A * 12/1998 McNally et al. ............ 345/173
`
`5.948,041 A * 9/1999 Abo et al. .................. 455/456
`6,085,148 A
`7/2000 Jamison et al. ........ 342/357.01
`6,208.974 B1 * 3/2001 Campbell et al. .............. 705/3
`6.212,393 B1 * 4/2001 Suarez et al. .......... 340/825.49
`6,266,612 B1 * 7/2001 Dussell et al. ......... 342/357.17
`6,360,101 B1
`3/2002 Irvin .......................... 455/456
`* cited by examiner
`Primary Examiner Daniel J. Wu
`(74) Attorney, Agent, or Firm-Christie, Parker & Hale,
`LLP
`ABSTRACT
`(57)
`A System and method for alerting a user of an item on a to-do
`list if the user is detected to be close to the item's perfor
`mance location. Each to-do list item is entered to a mobile
`user terminal Such as one that might be Supported in an
`automobile. The mobile terminal includes a GPS interface
`that allows an automatic detection of the mobile terminal
`when the automobile is in motion. Using the GPS interface,
`the mobile terminal periodically compares the position of
`the user with various to-do list item locations to determine
`whether the user will pass within a pre-defined proximity
`metric of the listed item. Whenever a particular criteria is
`Satisfied, the System provides a notification to the user of a
`potential to-do list item. In response to the notification, the
`user indicates that the user has accepted the notification by
`transmitting a “confirmed Status, or has completed the item
`by transmitting a "completed” status. A to-do list may be
`shared by multiple terminals for family or business use. In
`this case, to-do list items are identified Specific user identi
`fiers. Notifications and Status flags for a particular user's
`to-do list item are shared among the multiple terminals to
`update the list once a particular item Status has been “con
`firmed” or “completed.”
`
`13 Claims, 9 Drawing Sheets
`
`se ENTER TO-DO LIST
`
`RUN CONVERSION
`ROUTINE
`
`-100
`STORE TO-DO LIST IN MEMORY
`102 -
`ENTER DESTINATION LOCATION
`
`
`
`-106.
`iO4.
`NO RUN CONVERSION
`ROUTINE
`
`108
`MONITOR CURRENT LOCATION
`- - -
`- /
`110
`COMPARE CURRENT LOCATION
`WITH PERFORMANCE ADDRESS
`
`G
`
`- Cogic
`NOTF. AGA
`NOTIFY USER(S)
`
`114
`
`YES
`
`-..u.
`
`115
`
`
`
`
`
`
`
`
`
`ALREADY
`UPDATED
`
`ES
`
`12O
`NO
`
`3. <s (B)
`
`MO
`UPDATE STATUS
`
`118
`
`YES
`UPDATE STATUS
`
`
`
`126
`
`Page 1 of 17
`
`SNAP EXHIBIT 1006
`
`

`

`U.S. Patent
`US. Patent
`
`Jan. 20, 2004
`Jan. 20, 2004
`
`Sheet 1 of 9
`Sheet 1 0f 9
`
`US 6,680,675 B1
`
`US 6,680,675 B1
`
`
`
`/ "f)I, H.
`
`N65%
`
`
` mtjmzmmmo
`
`Z |
`
`
`
`
`
`Page 2 of 17
`
`Page 2 of 17
`
`

`

`U.S. Patent
`
`Jan. 20, 2004
`
`Sheet 2 of 9
`
`US 6,680,675 B1
`
`FIC.2
`
`1 Of
`
`1 OC
`
`PROCESSOR
`
`r
`
`1 Oe
`
`1 OC
`
`DEVICE
`
`1 Ob
`
`1 OC
`
`CPS
`RECEIVER
`
`1 Og
`
`MODEM
`
`Page 3 of 17
`
`

`

`U.S. Patent
`US. Patent
`
`Jan. 20, 2004
`Jan.20,2004
`
`Sheet 3 of 9
`Sheet3 0f9
`
`US 6,680,675 B1
`US 6,680,675 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`9mm:
`
`mZOC<QOJZO_F<QO._
`
`
`
`mmmmoa<QmEmEZm
`
`
`
`momCom09.;nowCOMM
`
`miQNK
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`EEmEm:NNNEméfiaammmm3::5Ll.‘_|_|JWuEOZ<mO:_
`amgmzzooPOOmmjmoz<mO._Hmmmfim222e:Emtx>3m
`mmdoz<m9EEmGm:a\r8:528838
`EmEmz_<_2_:$.onHzaouma<<<
`
`
`
`
`
`
`
`
`
` HI.
`
`
`BEBZmmdoz<m3zfidléa
`
`52Soflag5%2mmfizfidlEg80nirvai
`
`
`
`Page 4 of 17
`
`om
`
`Page 4 of 17
`
`
`
`

`

`U.S. Patent
`
`Jan. 20, 2004
`
`Sheet 4 of 9
`
`US 6,680,675 B1
`
`H—
`
`| EB? || S NO IN Q ZZZ
`
`
`
`| BE}}}|_S NIV/WN | | |
`
`fz "f)I, H.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SETTE ONV SOTI
`
`
`
`
`
`SETTE ONV SOTI
`
`
`
`
`
`SETTE ON\7 SOTI
`
`
`
`
`
`SÈJENWETO Åà?0 000
`
`–
`
`Of7
`
`Page 5 of 17
`
`

`

`U.S. Patent
`US. Patent
`
`Jan. 20, 2004
`Jan. 20, 2004
`
`Sheet 5 of 9
`Sheet 5 0f 9
`
`US 6,680,675 B1
`US 6,680,675 B1
`
`
`
`3,7
`
`ID
`
`TERMINAL
`
`Lu
`
`2<Z [
`
`Z
`L1_l
`(f)
`I)
`
`
`
`
`JANEDOE
`
`MARYDOE
`
`| 7
`
`FIG.5
`
`
`
`Page 6 of 17
`
`Page 6 of 17
`
`

`

`U.S. Patent
`
`Jan. 20, 2004
`
`Sheet 6 of 9
`
`US 6,680,675 B1
`
`STARD
`
`RETRIEVE LOCATION
`TABLE
`
`44
`SEARCH FOR STORE
`NAME
`
`FIG. 6
`
`46
`NO
`
`SEARCH ENTRY
`FOR CITY
`
`
`
`STREET
`SPECIFIED
`?
`
`5O
`NO RETRIEVE ALL
`ENTRES FOR STORE
`
`54
`
`
`
`SEARCH ENTRY
`FOR STREET
`
`56
`
`MULTIPLE
`ENTRIES RETRIEVED
`?
`
`
`
`YES - 5
`8
`DISPLAY ALL
`ENTRIES TO USER
`6
`O
`
`REQUEST USER
`SELECTION
`
`62
`STORE LOCATION
`ADDRESS
`
`Page 7 of 17
`
`

`

`U.S. Patent
`US. Patent
`
`Jan. 20, 2004
`Jan.20,2004
`
`Sheet 7 of 9
`Sheet7 0f9
`
`US 6,680,675 B1
`US 6,680,675 B1
`
`fiw
`
`ownmm
`
`”>to
`
`mu
`
`
`
`lummmmog555,
`
`mxm<F
`
`
`
`8:92:mmozWEEéEm:
`
`
`
`filllllilallxnlulmwwgAmmm:40mmv
`
`
`
`H£32mmoFm
`
`
`
`on
`
`
`
`a335comv333nngEommeme
`
`Page 8 of 17
`
`Page 8 of 17
`
`
`
`

`

`U.S. Patent
`
`Jan. 20, 2004
`
`Sheet 8 of 9
`
`US 6,680,675 B1
`
`CSTARD
`94
`ENTER TO-DO LIST
`
`FIG. BA
`
`98
`
`9
`6
`coung as NO
`YES
`1 OO
`STORE TO-DO LIST IN MEMORY
`1 O2
`ENTER DESTINATION LOCATION
`
`
`
`
`
`1 O4
`1 O6
`NO RUN CONVERSION
`SPECIFIC
`ROUTINE
`stan ADDRESS
`YES
`
`". (B)
`
`11
`O
`
`
`
`
`
`
`
`MONITOR CURRENT LOCATION
`
`COMPARE CURRENT LOCATION
`WITH PERFORMANCE ADDRESS
`
`112
`
`PROXIMITY
`CRITERIA SATISIFIED
`?
`
`YES
`
`g 113
`
`114
`
`NOTF, AGAIN
`YES
`NOTIFY USER(S)
`
`Page 9 of 17
`
`

`

`U.S. Patent
`
`Jan. 20, 2004
`
`Sheet 9 of 9
`
`US 6,680,675 B1
`
`FIC. BB
`
`
`
`
`
`ALREADY
`UPDATED
`?o
`
`12O
`
`126
`
`
`
`OTHER
`NON-COMPLETED
`TASKS 2
`
`Page 10 of 17
`
`

`

`US 6,680,675 B1
`
`1
`INTERACTIVE TO-DO LIST TEM
`NOTIFICATION SYSTEM INCLUDING GPS
`INTERFACE
`
`FIELD OF THE INVENTION
`The present invention relates generally to electronic noti
`fication Systems, and more particularly, to an electronic
`System and method for providing an alert of an entry in a
`to-do list when a user is within a pre-defined proximity
`location to perform the to-do list item.
`BACKGROUND OF THE INVENTION
`In today's fast-paced world, “efficiency” is a motto
`adopted by many people. Such efficiency does not only
`apply to the work place, but also to every-day living. AS the
`tasks that need to be accomplished within a day grow in
`number, and the amount of time in a day to accomplish Such
`tasks Seem to decrease, it becomes more and more important
`to efficiently manage one's time and plan the tasks that need
`to be accomplished within that time in a practical and
`organized manner. The amount of planning carried out by an
`individual as the order in which to accomplish the tasks
`efficiently become futile if the individual forgets the order or
`a task to be accomplished.
`Thus, various devices exist in the prior art to aid indi
`viduals in the organization and reminder of tasks. For
`instance, personal notes and post-its placed on refrigerator
`doors, calendars, and the like, help remind individuals of
`tasks to be accomplished in a day. Schedule books and
`personal organizers also help individuals keep track of
`time-Sensitive tasks and appointments. If electronic calen
`dars and organizers are used, users may be electronically
`notified via the device's alarm or notification proceSS when
`it is time to carry out a particular task or appointment.
`If a task is not time-Sensitive, users often place Such a task
`in a separate to-do list. Typical tasks entered into a to-do list
`include, for example, buying an article X at Store A, an
`article Y at Store B, Stopping by the bank, going to the post
`office, going to the dry-cleaner, and running other types of
`errands. Whether such a to-do list is maintained manually or
`electronically, the user must make an effort to check the list
`in order to not forget a particular task that needs to be
`accomplished. Failure to check the to-do list at a particular
`time and be reminded of the task might cause inefficient
`management of the user's time. For instance, a user who is
`heading to Store B might forget to Stop by the bank which is
`on the way to Store B. This might cause the user to waste
`additional time to retrace his or her Steps to make the Visit
`to the bank, or forego this task completely. In either case, the
`user has made ineffective usage of his or her time.
`The prior art also fails to provide an effective method to
`share a to-do list among various individuals. For instance,
`one family member may have already accomplished a task
`on the to-do list which a Second family member has also Set
`out to accomplish. This again results in ineffective usage of
`both family members times. Either member could have
`devoted his or her time to a different task on the to-do list.
`Accordingly, there is a need for an electronic System and
`method for providing an alert when a user is in a pre-defined
`proximity location to a facility, Store, or the like, which has
`an entry on a to-do list. The reminder allows the user to then
`accomplish the task at the location. Such System should also
`maintain track of other users Sharing a to-do list item, and
`notify the other users when the shared to-do list item has
`been accomplished.
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`SUMMARY OF THE INVENTION
`The present invention addresses and alleviates the above
`mentioned deficiencies associated with the prior art. More
`particularly, the present invention comprises a System and
`method for notifying a user of a to-do list item if the user is
`detected to be in a particular proximity location to the to-do
`list item.
`In one aspect of the invention, a method for providing
`electronic notification of a to-do list item includes entering
`the to-do list to a mobile user terminal. The mobile user
`terminal includes a global positioning System (GPS) inter
`face allowing the automatic detection of the user's current
`position as the user embarks on his or her errands. The
`mobile terminal periodically compares the current position
`of the mobile terminal with the performance location of a
`to-do list item. Electronic notifications are then Sent to the
`user if a proximity criteria of the to-do list item has been
`Satisfied. The user might then Send a confirmation that the
`notification has been received.
`The proximity criteria is based on numerous factors, Such
`as the user's current position, the user's destination, the
`route chosen to reach the destination and the like. The
`proximity criteria may also vary from task to task. If the
`proximity criteria is based on the user's current position, the
`criteria is Satisfied if the distance between a detected current
`location and a performance address is within a pre
`determined proximity metric (i.e. one mile, one half mile, or
`the like).
`In another aspect of the invention, a particular to-do list
`item may be shared by multiple users. In this Scenario, one
`or more user IDs are associated with a to-do list item.
`Electronic notifications for the item are then sent to all the
`users with the associated user IDs. When one of these users
`transmits a confirmation of the notification, an update Status
`message is transmitted to the other users sharing the to-do
`list item. The update Status message changes the Status of the
`to-do list item from “Not Notified to “Confirmed. Further
`notifications of the confirmed item are then transmitted only
`to the confirming user. The other users Sharing the confirmed
`to-do list item are excluded from receiving further notifica
`tions.
`In yet another aspect of the invention, the sharing of a
`to-do list among multiple users is effectuated via a central
`host computer. In this Scenario, the to-do list is entered into
`the host computer and downloaded to the Sharing mobile
`terminals. A confirmation message from one of the mobile
`terminals is transmitted to the host computer, and the host
`computer transmits the update Status message to the Sharing
`mobile terminals.
`It will be appreciated, therefore, that the present invention
`allows for efficient time and Schedule management for
`dealing with multiple tasks in a Single excursion. With the
`System's alert mechanism, users no longer run the risk of
`forgetting an errand that could have been efficiently been
`performed during a trip to a destination location.
`The present invention also allows a to-do list to be
`effectively shared among various individuals. By maintain
`ing track of the users sharing a to-do list item and the Status
`of each of the items, the Sharing users will know when a
`particular task has been confirmed or completed.
`BRIEF DESCRIPTION OF THE DRAWINGS
`These and other features, aspects and advantages of the
`present invention will be more fully understood when con
`sidered with respect to the following detailed description,
`appended claims and accompanying drawings wherein:
`
`Page 11 of 17
`
`

`

`3
`FIG. 1 is a Schematic block diagram of an interactive
`to-do list item notification System including a mobile user
`terminal;
`FIG. 2 is a more detailed schematic block diagram of the
`mobile user terminal of FIG. 1;
`FIG. 3 is a schematic layout diagram of a To-Do List
`database;
`FIG. 4 is a Schematic layout diagram of a Location
`database;
`FIG. 5 is a Schematic layout diagram of a user database;
`FIG. 6 is a proceSS flow diagram of an address conversion
`routine according to one embodiment of the invention;
`FIG. 7 is an illustration of a Screen display for entering a
`to-do list to the system of FIG. 1; and
`FIGS. 8A-8B are process flow diagrams of an interactive
`to-do list item notification Software program.
`DETAILED DESCRIPTION OF THE
`INVENTION
`In general terms, the present invention is directed to a
`particular System and method for alerting a user of an item
`on a to-do list if the user is detected to be close to the items
`performance location, thereby allowing the user to accom
`plish the task. Each to-do list item is entered to a mobile user
`terminal Such as one that might be Supported in an automo
`bile. The mobile terminal includes a GPS interface that
`allows an automatic detection of the mobile terminal when
`the automobile is in motion. Using the GPS interface, the
`mobile terminal periodically compares the position of the
`user with various to-do list item locations to determine
`whether the user will pass within a pre-defined proximity
`metric (e.g. one mile, half mile, or the like) of the listed item.
`The proximity metric is calculated according to various
`criteria, including the user's current position, the user's
`destination, the route chosen to reach the destination, and the
`like. Whenever a particular criteria is Satisfied, the System
`provides a notification to the user of a potential to-do list
`item.
`In response to the notification, the user indicates that the
`user has accepted the notification by transmitting a “con
`firmed” status. Once the to-do item has been completed, the
`user might change the item's Status by indicating that the
`item has been “completed.” The present system and method
`thus allow for efficient time and Schedule management for
`dealing with multiple tasks in a single excursion.
`According to one embodiment of the invention, the
`present System and method incorporates a single mobile
`terminal for personal use. Alternatively, the present System
`and method incorporates multiple terminals for family or
`busineSS use. In the case of multiple terminals and/or mul
`tiple users, particular items may be identified with a specific
`user ID so that the to-do list item is performed by the
`appropriate perSon. Notifications and Status flags for a
`particular users to-do list item are shared among the mul
`tiple terminals to update the list once a particular item status
`has been “confirmed” or “completed.”
`Considering the foregoing, FIG. 1 depicts a Schematic
`block diagram of an interactive to-do list item notification
`system. In the exemplary embodiment of FIG. 1, a mobile
`user terminal 10 storing a to-do list receives GPS signals
`from a GPS satellite system 12. The mobile terminal 10
`processes the GPS Signals for automatically detecting the
`position of the terminal 10, and hence, the position of the
`user of the terminal as the user embarks on his or her
`errands. If the user is in a proximity location to an items
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,680,675 B1
`
`4
`performance location, the mobile terminal 10 displays an
`alert reminding the user of the to-do list item.
`A to-do list may be shared by multiple users and/or
`multiple mobile terminals (collectively referred to as 10) via
`a central host computer 14. The communication between the
`mobile terminals 10 and the host computer 14 may be wired
`16 and/or wireleSS 18, using traditional computer networks,
`cellular phone networks, public telephone networks, and/or
`Satellite System networks.
`To effectuate notification of to-do list items to the multiple
`mobile terminals 10, the host computer 14 preferably hosts
`three databases: a To-Do List database 20, Location database
`22, and user database 23. In the illustrated embodiment, the
`three databaseS reside in three Separate mass Storage devices,
`each taking the form of a hard disk drive or drive array. It is
`noted, however, that the three databases may also reside in
`a single mass Storage device. If the to-do list is not to be
`shared among multiple users or terminals 10, the To-Do List
`database 20 and Location database 22 reside within the
`mobile terminals themselves.
`The To-Do List database 20 stores a to-do list along with
`one or more user IDS and a performance address for each
`item on the to-do list, as is explained in further detail below
`in conjunction with FIG. 3. The user IDs indicate the
`individuals who are responsible for accomplishing the indi
`cated task. The performance address indicates a specific
`address where the task is to be accomplished.
`The Location database 22 maps performance locations to
`Specific performance addresses, as is also described in
`further detail below in conjunction with FIG. 4. Thus, if the
`user enters a performance location, Such as the name of a
`Store or a branch, instead of a specific address, the host
`database 14 searches the Location database 22 to find the
`Specific address of the indicated task. The host computer 14
`then Stores the to-do list item with the Specific performance
`address in the To-Do List database 20.
`The user database 23 maps particular users to particular
`mobile terminals 10, as is also explained below in conjunc
`tion with FIG. 5. Thus, communications received from a
`particular terminal may be mapped to the user transmitting
`the communication. Furthermore, communications may be
`transmitted to particular users by identifying the terminals
`asSociated with Such users.
`In downloading the to-do list to the multiple mobile
`terminals 10, the host computer 14 retrieves the to-do list
`from the To-Do List database 20 and examines the user IDs
`associated with the to-do list items. The host computer 14
`then transmits the entire to-do list along with the user IDs
`and the performance addresses to the mobile terminals 10
`indicated by the user IDs, via wired 16 or wireless 16 media.
`Alternatively, the host computer 14 creates Separate to-do
`lists from the retrieved master to-do list based on the user
`IDS, and transmits the individualized to-do list to each user.
`If a particular task is assigned to more than one perSon, the
`task is included in the to-do list for all the assigned users.
`In an alternative embodiment, a to-do list is shared by
`multiple terminals 10 without the aid of a central host
`computer 14. For instance, a to-do list may be shared among
`various family members by maintaining a separate user ID
`for each member of the family. Each task is then associated
`with one or more user IDs. The to-do list along with the
`asSociated user IDs are then Stored in each family members
`mobile terminal.
`FIG. 2 is a more detailed schematic block diagram of the
`mobile user terminal 10 of FIG.1. According to one embodi
`ment of the invention, the mobile terminal is installed into
`
`Page 12 of 17
`
`

`

`S
`an automobile. If the automobile already includes a GPS
`System, the mobile terminal may make use of the automo
`bile’s GPS interface for location detection. In an alternative
`embodiment, the mobile terminal 10 is not installed into the
`automobile, but is a Stand-alone unit capable of being
`hand-carried by a user.
`In the situation where the central host computer 14 is not
`used, a user enters a to-do list including the performance
`location of each to-do list item directly into the mobile
`terminal 10 using an input device 10a. The user also uses the
`input device 10a to change the status of a to-do list item. The
`input device may take the form of a keyboard or a numeric
`or alphanumeric button or keypad arrangement. Specialized
`keys or buttons on the input device 10a relate to Specialized
`functions performed with respect to the to-do list, Such as
`entering or downloading the to-do list, and transmitting
`“confirmed” and “accepted Status messages.
`In a multiple user and/or multiple mobile user terminal
`Scenario including the central host computer 14, the to-do
`list is entered directly into the host computer and down
`loaded to each mobile terminal 10. Alternatively, the to-do
`list is entered through the mobile terminal 10 and uploaded
`to the host computer 14. The host computer 14 is configured
`with similar input devices as the mobile terminal 10 to allow
`entry of the to-do list. The mobile terminal 10 includes a
`modem 10g for downloading/uploading the to-do list from/
`to the host computer 14. The modem 10g may take the form
`of a traditional modem for wired communication, and/or a
`wireleSS modem for communication with the host computer
`14 via wireless media.
`The mobile terminal 10 also includes an output device
`10b to alert the user of a to-do list item via visual and/or
`audio instruments according to well known methods. The
`audio component of the output device 10b includes one or
`more Speakers and a voice Synthesizer for providing audio
`alerts to the user. The Speakers may optionally be coupled to
`the speakers of the automobile. The mobile terminal 10 may
`further emit vibrations to alert the user of a to-do list item.
`The visual component of the output device 10b preferably
`comprises a VGA, SVGA liquid-crystal-display (LC)
`Screen, an LED display Screen, or any other Suitable display
`apparatus. Pressure Sensitive (touch Screen) technology may
`be incorporated into the display 10b so that the user may
`interact with the mobile terminal 10 by merely touching
`certain portions of the Screen. Alternatively, the keyboard or
`keypad arrangement is provided in combination with the
`display screen to define the input device 10a.
`A GPS receiver 10c also incorporated to the mobile
`terminal 10 allows communication with the GPS satellite
`system 12. The GPS receiver 10c is a specialized radio
`receiver designed to listen to radio Signals transmitted by the
`GPS satellite system 12. The radio signals provide latitude
`and longitude information to the mobile terminal 10 accord
`ing to well-known methods. The latitude and longitude
`information allows the mobile terminal 10 to detect the
`user's current location and provide alerts based on the
`detected location.
`The mobile terminal 10 further includes a processor 10d
`for taking the input list from the input device 10a or the input
`list that has been downloaded via the modem 10g, and
`Storing it into memory 10for an external storage device (not
`shown). The memory 10f is a RAM or other suitable
`variations of a RAM. If the performance location entered by
`the user for a particular to-do list item is not a specific
`performance address, the processor 10d converts the perfor
`mance location to a specific performance address before
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,680,675 B1
`
`6
`storing the to-do list into the memory 10f. In this regard, the
`processor 10d accesses the mobile terminal's Location data
`base 10e mapping performance locations with performance
`addresses, as is described in further detail below in conjunc
`tion with FIG. 4. In its simplest form, the Location database
`is a yellow-page directory of Schools, Stores, businesses, and
`other facilities in a Specified geographic area. The Location
`database 10e resides in a mass Storage device Such as a CD
`ROM, DVD, or hard disk drive. According to one embodi
`ment of the invention, the Location database 10e also
`includes digital or graphic maps of the geographic area.
`FIG. 3 is a schematic layout diagram of a To-Do List
`database 20 stored by the host computer 14 and downloaded
`to the mobile terminal's memory 10for the external storage
`device. A similar database is created by the mobile terminal
`10 itself if the to-do list is entered directly by a user. The
`database 20 includes a to-do list table 30 with a plurality of
`to-do list items. The to-do list items may be arranged in a
`variety of ways, but is most advantageously configured as
`Sequential entries, with each entry Specific to a particular
`task to be accomplished. A particular task entry includes a
`“Task” field 30a, typically implemented as a series of text
`Strings, for describing a particular task to be accomplished.
`A particular task entry further includes a “Location
`Entered” field 30b and a “Location Address' field 30c, also
`implemented as a Series of text Strings. The “Location
`Entered” field 30b reflects the performance location of the
`task identified by the user. A user might give an exact
`address as the performance location. In this case, the “Loca
`tion Address' field 30c includes the exact address entered by
`the user. Alternatively, the user might not know the exact
`address of a performance location, or might know only a
`portion of the address, Such as the Street name. In this case,
`the host computer 14 (or the mobile terminal 10) converts
`the performance location entered by the user into a specific
`performance address, and Stores the performance address in
`the “Location Address' field 30c. The address conversion
`routine is described in further detail in conjunction with FIG.
`6.
`In the event of multiple users and/or multiple mobile
`terminals 10, each task entry of the to-do list table 30 also
`includes a “User ID' field for indicating one or more unique
`user identifierS Such as identification numbers responsible
`for accomplishing the particular task. Aparticular task might
`be assigned to more than one individual.
`A “Status' field also included in each task entry indicates
`the Status of a particular task. Initially, all tasks are initial
`ized as being “Not Notified.” When a user receives notifi
`cation for a particular to-do list item, and transmits a
`confirmation that the alert was received, the Status of the
`particular item is changed to a "Confirmed Status. In a
`multi-user Scenario, the “Status' field includes the user ID of
`the user transmitting the confirmed Status. The user transmits
`a completion of a particular to-do list item if the task has
`been accomplished. In this event, the Status of the particular
`task entry is again changed to reflect a “Completed Status.
`FIG. 4 is a Schematic layout diagram of a Location
`database 22, 10e maintained either by the host computer 14
`or the mobile terminal itself 10, depending on whether the
`to-do list is to be shared among multiple users/terminals.
`The database 22, 10e includes a location table 40 with a
`plurality of location-specific information. The location
`Specific information may be arranged in a variety of ways,
`but is most advantageously configured alphabetically in
`Sequential entries, with each entry Specific to a particular
`Store, business, facility, and the like (collectively referred to
`
`Page 13 of 17
`
`

`

`7
`as Stores), in a particular geographic area. According to one
`embodiment of the invention, the Location database 22
`Stores a plurality of location tables for different geographic
`areas. For instance, Separate location tables 40 might be
`maintained for different cities, counties, States, and the like.
`A particular store entry in the location table 40 includes a
`“Name” field 40a, typically implemented as a series of text
`Strings, for describing a name of the Store. A location entry
`further includes a “City” field 40b and an “Address” field
`40c, also implemented as a series of text strings. The “City”
`field indicates the city where the Store is located, and the
`“Address' field” 40c indicates the exact address in the city.
`As illustrated in FIG. 4, stores with several locations
`throughout the geographic area will have multiple entries in
`the location table 40.
`FIG. 5 is a schematic layout diagram of a user database 23
`preferably maintained by the host computer 14 according to
`one embodiment of the invention. The user database 23
`includes a user table 41 with a plurality of user-specific
`information. The user-specific information may be arranged
`in a variety of ways, but is most advantageously configured
`in Sequential entries, with each entry Specific to a particular
`user. A particular user entry includes a “user ID' field 41a
`for Storing an identification for each user. A particular user
`entry further includes a user name 41b associated with the
`user ID, as well as a terminal ID 41c for identifying the
`particular terminal used by the user. The user database 23 is
`preferably used in a multiple user/terminal Scenario for
`identifying the source of a “confirmed” or a “completed”
`message, as well as for Sending notifications to the appro
`priate users.
`FIG. 6 is a proceSS flow diagram of an address conversion
`routine implemented as a Software program according to one
`embodiment of the invention. The address conversion rou
`tine is performed by the host computer 14 or the mobile
`terminal 10 if the performance location entered for a to-do
`list item is not an exact address. The program illustrated in
`FIG. 6 starts, and in step 42, retrieves the location table 40
`from the location database 22 or 10e. According to one
`embodiment of the invention, the user, at a minimum, enters
`the Store name as the performance location of the to-do list
`item. Thus, in step 44, the program searches the “Name”
`field of the location table 40 for the entered store name and
`retrieves all matching entries for the Store.
`In Step 46, the program inquires if the user has specified
`a city where the store is located. If the answer is YES, the
`program, in Step 48, Searches the matching entries retrieved
`So far for the Store in the Specified city, and thus filters-out
`any Stores located in the other cities. The program further
`inquires in Step 50 if the user has specified a Street name
`where the store is located. If the answer is YES, the program,
`in Step 52, Searches the currently matching entries for the
`Store on the Specified Street.
`If the user provided neither a city nor a Street name for the
`Store, the program retrieves in Step 54 all the matching
`entries for the Store. Alternatively, the program assumes as
`a default that the desired city is the city where the user
`resides. In this case, the program retrieves all the matching
`entries for the store in the default city.
`In Step 56, the program inquires if multiple matching
`entries exist. If the answer is YES, the user preferably
`manually narrows-down the matches to a single match.
`Accordingly, the program, in Step 58, displays all the match
`ing entries to the user. In Step 60, the us

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket