TECHNICAL FIELD

[0001] The disclosed embodiments relate generally to mapping and navigation and in particular, but not exclusively, to an interactive mapping scheme for use in a car.

BACKGROUND

[0002] Car navigation system have revolutionized driving by providing accurate step- by-step instruction on how to go to a specified destination. But despite their enormous benefits, one problem with existing navigation system is that data entry is awkward. Each destination must generally be entered into the system one at a time, and the data entry process can be made difficult by awkward user interfaces. Even after all the destination data is entered, the user interfaces usually make any follow-on interaction with the navigation system awkward as well.

SUMMARY

[0003] The disclosure describes embodiments of an apparatus and method for interactive mapping. The apparatus includes a computer to which are coupled a user identification device to identify an authorized user, a transceiver to receive and transmit user data between the computer and one or more user data sources associated with the authorized user, a navigation system, and one or more displays coupled to the computer. The computer constructs a timeline for the authorized user based on the user data over a specified time interval, wherein the timeline displays every user event that falls within the specified time interval, and simultaneously display the timeline and a map on one of the one or more displays, wherein the user's current position and the position of at least one user event from the timeline are identified on the map.

[0004] The method includes synchronizing local user data in a local user data storage with user data received from one or more user data sources, wherein the local user data includes one or more user events and each user event is described by a dataset including at least a start time, an end time, and a location. A timeline is constructed for an authorized user based on the local user data over a specified time interval, wherein the timeline displays every user event that falls within the specified time interval. The timeline and a map are simultaneously displayed on one of one or more displays, wherein the user's current position and the position of at least one user event from the timeline are identified on the map.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Non-limiting and non-exhaustive embodiments of the present invention are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified.

[0006] Fig. 1 is a block diagram of an embodiment of an interactive mapping system. [0007] Fig. 2 is a flowchart illustrating an embodiment of operation of an interactive mapping system such as the one in Fig. 1.

[0008] Figs. 3A-3C are diagrams of a car embodiment of an interactive mapping system.

[0009] Figs. 4A-4D are diagrams of embodiments of a map display for an interactive mapping system.

[0010] Fig. 5 is a diagram of an embodiment of interaction and data exchange between an interactive mapping system and other devices.

[0011] Figs. 6A-6D are diagrams of embodiments of interaction to change the number or size of software-defined displays.

[0012] Figs. 7A-7C are diagrams of an embodiment of user interaction with multiple displays.

[0013] Figs. 8A-8C are diagrams of embodiments of user interaction to select information from a display.

[0014] Figs. 9A-9D are diagrams of embodiments of user interaction to select and delete information from a display.

[0015] Figs. lOA-lOC are diagrams of embodiments of user interaction to rotate a three-dimensional interface shown on a display.

[0016] Fig. 11 is a diagram of an embodiment of user interaction to zoom in and zoom out items shown on a display.

[0017] Fig. 12 is a diagram of an embodiment of user interaction to activate and deactivate a gesture recognition system.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODFMENTS

[0018] Embodiments are described of an apparatus, system and method for interactive mapping. Specific details are described to provide an understanding of the embodiments, but one skilled in the relevant art will recognize that the invention can be practiced without one or more of the described details or with other methods, components, materials, etc. In some instances, well-known structures, materials, or operations are not shown or described in detail but are nonetheless encompassed within the scope of the invention.

[0019] Reference throughout this specification to "one embodiment" or "an embodiment" means that a described feature, structure, or characteristic can be included in at least one described embodiment. Appearances of "in one embodiment" or "in an embodiment" thus do not necessarily all refer to the same embodiment. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. [0020] Fig. 1 illustrates an embodiment of an interactive mapping system 100 that can be used in a car. System 100 includes elements outside the car as well as elements inside or on the car. Outside the car, a user account 104 can be coupled to one or more remote user data sources 102a-102c to exchange data with the remote user data sources. User account 104 can receive data from, transmit data to, and process data exchanged with remote user data sources. User account 104 can, for example, be an account established on servers set up by the car manufacturer. Remote user data sources 102a-102c can include user accounts established on remoter servers such as a user's contacts, calendar, health-related accounts, and social media accounts. In other embodiments user account 104 can be omitted and its functions of assembling the events and their datasets can instead be performed by computer 112; in such cases, transceiver 108 can communicate directly with remote user data sources 102a-102c through antenna 106, rather than communicating with the remote user data sources through user account 104.

[0021] User account 104 is set up by the user and linked to remote user data sources 102a-102c so that user account 104 can retrieve data from remote user data sources 102a-102c to determine what events a user has upcoming and so that user account 104 can use the retrieved data to assemble a dataset for each event. In one embodiment, the dataset for each event can include at least a starting time, an ending time, and a location. In other embodiments the dataset can also include additional data, such as names, photos, and contact information for people associated with each event. By aggregating information this way, the mapping scheme makes information from various apps accessible on a single display.

[0022] For instance, user account 104 could retrieve appointments from a user's calendar. The events retrieved from the calendar might include location information, but if they don't user account 104 can obtain that information from a different remote user data source, such as the user's contacts or social media account, or by searching the Internet. For example, if an event on the user's calendar is an appointment with Dr. Smith from 2-3 pm but the calendar has no location for Dr. Smith, user account 104 can access another user data source— the user's contacts, for instance— to establish a location for Dr. Smith. And if a location for Dr. Smith cannot be deduced from a remote user data source, it can also be looked up on the Internet, for example based on the user's current location.

[0023] Inside the car, a computer 112 is communicatively coupled to various elements including to: a transceiver 108 via security gateway 110; car systems 114; a navigational system 116 that includes a position sensor or GPS 118 as well as a database including map data 120; a user identification system 122 coupled to one or more user ID sensors 124; a local user data storage 126 and a second transceiver 130 through which computer 112 can exchange data with a local user data source 128. A controller/graphic user interface (GUI) interface 132 is communica- tively coupled to computer 112, and one or more displays 136a-136c are coupled to controller/GUI interface 132. A user input device such as gesture recognition system 134 with at least one camera 135 is also communicatively coupled to computer 112.

[0024] Computer 112 is the hub of system 100. In the illustrated embodiment computer 112 is a programmable general-purpose computer that includes at least memory, one or more microprocessors, and storage. Other embodiments, however, can include one or more other types of computers, such as application specific integrated circuits (ASIC). Although represented as a single computer in the illustrated embodiment, in other embodiments computer 112 can include multiple processors or, in some embodiments, can comprise multiple separate computers that can communicate and coordinate with each other. In the illustrated embodiment the elements communicatively coupled to computer 112 are represented as components separate from the computer, but in other embodiments one or more of these other components can be implemented in software and run on the computer 112; in other words, in other embodiments one or more of the elements communicatively coupled to computer 112 can actually be processes running on computer 112.

[0025] Transceiver 108 is communicatively coupled via security gateway 110 to computer 112. Transceiver 108 is also coupled to antenna 106 to allow it to wirelessly exchange data with user account 104, for instance via Wi-Fi, cellular, or satellite communication. Security gateway 110 is communicatively coupled in the link between transceiver 108 and computer 112 to avoid downloading viruses, malicious code, or other data that could damage system 100 or, in particular, that could adversely influence car systems 114 and thus compromise vehicle safety. Security gateway 110 in one embodiment can be a computer running software such as anti -virus or anti -mal ware software

[0026] User identification system 122 is coupled to one or more user ID sensors 124, and together they are used to identify authorized users of system 100. In one embodiment user ID sensor 124 can include one or more facial recognition cameras, but in other embodiments other types of sensors such as biometric sensors (e.g., fingerprint or retinal scan) can be used. In still other embodiments, user identification system 122 can be the traditional username/password system in which a user enters their username and password via a keypad or other user input system. User ID sensors 124 can be positioned inside or outside the car (see, e.g., Figs. 3 A-3C) and used to identify the driver and/or passengers in the car, all of whom can be users of interactive mapping system 100.

[0027] Car systems 114 or coupled to computer 112 so that they can be controlled and/or adjusted by the driver or passengers of the car. Among other things, car systems 114 can include those that control the engine, steering, suspension, air-conditioning, interior lighting, exterior lighting, locking, and so on.

[0028] Navigation system 116 is coupled to computer 112 to provide navigation capability for the car. Among other things, navigation system 116 includes a position sensor such as a global positioning system (GPS) system 118, as well as a database that includes map data 120. Map data 120 can be commercially available map data obtained from map data sources such as Google, Bing (Microsoft), TomTom, Garvin, etc. Navigation system 116 uses GPS 118 to determine the current position of the car and uses map data 120 to show the current position of the car on a map, as well as the map locations of future events, on at least one of displays 136a-136c (see below).

[0029] Local user data storage 126 is coupled to computer 112 to locally store data retrieved from user account 104. The data stored in local user data storage 126 may be raw data obtained directly from user account 104, or can be data that has been further processed by computer 112. Data stored in local user data storage 126 can then be used to construct an interactive mapping timeline and map (see, e.g., Figs. 4A-4D).

[0030] In some embodiments, rather than obtain user data from remote user data sources 102a-102c through user account 104, it may be desirable to obtain the user data from a local user data source 128. In one embodiment, local user data source 128 can be a mobile phone that the user carries with them in the car. Local user data source 128 can have versions of remote user data sources 102a-102c on it, as well as a version of user account 104. For instance, if remote data source 102a is a calendar application— Google calendar, for instance— and the user has a Google calendar app on their mobile phone that synchronizes with Google's calendar server, then all the data available from remote data source 102a is also available from local user data source 128. In another embodiment, it could be necessary to use local user data source 128 if, for instance, a connection cannot be established between transceiver 108 and user account 104 or between user account 104 and remote user data sources 102.

[0031] Transceiver 130 is coupled to computer 112 to access data from local user data source 128 and transfer it to local user data storage 126. Local user data source 128 can then communicate, wirelessly or by wire, with transceiver 130. Wireless communication between local user data source 128 and transceiver 130 can be accomplished, for instance, using short-range wireless protocols such as Bluetooth, but in other embodiments it can communicate using other wireless communication formats such as Wi-Fi.

[0032] Controller/graphic user interface (GUI) 132 is coupled to computer 112 and also coupled to at least one display. In the illustrated embodiment three displays 136a-136c are coupled to controller/GUI interface 132, but in other embodiments the number of displays cou- pled to the interface can be different than shown. Although illustrated and referred to as separate displays, displays 136a-136c can be different parts of a single display. As further discussed below (see Figs. 2, 4A-4D, and 5), one of displays 136a-136c can be used to display a combined timeline/map of the user's events and another of displays 136a-136c can be used to show other information, such as events which can be added to the user's timeline and shown on the map.

[0033] A gesture recognition system 134 coupled to one or more cameras 135 serves as a user input device for users within the automobile to interact with the system 100, in particular to interact with the timeline/map display and other displays. In other embodiments other user input devices can be used, instead of or in addition to gesture recognition system 134, to perform the same functions and actions that can be performed with gesture recognition system 134.

[0034] Gesture recognition system 134 is coupled to computer 112 and in some embodiments can be directly coupled to controller/GUI interface 132. The one or more cameras 135 coupled to gesture recognition system 134 can be located in various places within a car's cabin; for instance, in one embodiment that there can be cameras for the driver and every passenger. The one or more cameras 135 can capture gestures, motions, or gesture/motion combinations made by the driver and one or more of the passengers. In one embodiment the gestures and motions can be hand gestures and motions, but other embodiments can, instead of or in addition to hand gestures and motions, use facial gestures and motions. The gesture control essentially provides a remote touch pad. Examples of hand gestures that can be used are: the user zooms in with gestures by grabbing and pulling towards the user; moving the user hand up and down, and left and right, to move objects up and down, and left and right; and rotating objects such as the map with a scoop gesture.

[0035] Among other things, gesture recognition system 134 allows the user to use gestures, motions, or gesture/motion combinations to interact with the timeline and map shown on one of displays 136a-136c. Interaction with the timeline can include deleting existing events, modifying existing events, or adding new events. In one embodiment, (see Fig. 5) events displayed on another of screens 136a-136c can be added to the timeline by selecting them from the screen from the display on which they are shown and dragging them to the display on which the timeline is shown. User interaction with a map can include panning, zooming, and rotating the map.

[0036] Fig. 2 illustrates an embodiment of an operation process 200 for system 100. The process starts at block 202 and proceeds to block 204, where it attempts to identify a user trying to use the system. At block 206 the process checks whether the user identified at block 204 is a known and authorized. If the user at block 204 is unknown or unauthorized the process goes to block 208, where it provides user feedback indicating that the user is unknown or unau- thorized, and then returns to block 204 to attempt to identify another user. But if at block 206 the user identified at block 204 is known and authorized, at block 210 the process accesses the authorized user's user account 104 and then proceeds to block 212, where it synchronizes the event data from user account 104 with the data contained in local user data storage 126.

[0037] At block 214, the event data from local user data storage 126 is used to construct a timeline and at block 216 the process associates each timeline event with its map location. At block 218, the process displays the timeline, the map, and the map locations of each timeline event on a display. At block 220, the map display shows a path among all the event locations shown on the map and a connection from at least one of the events on the timeline to its corresponding map location. At block 222 the process checks whether the user has modified the timeline, for instance by modifying an event shown on the timeline, deleting event found on the timeline, or adding a new event to the timeline. If at block 222 the process determines that the timeline has been modified, it proceeds to block 224 where it updates the local user data storage 126 and synchronizes the local user data storage with user account 104, remote user data sources 102, and, if applicable, local user data source 128.

[0038] If at block 222 the process determines that there are no timeline modifications, the process proceeds to block 228, where it navigates the car to the location of the first event on the timeline— that is, the event closest in time to the current time. Having arrived at the destination associated with the selected timeline event, at block 230 the process checks whether there is a new user, for instance if the original user was a passenger who has now arrived at their destination and the and the driver now wants to go to another location associated with an event on their schedule. If at block 230 the process determines that there is a new user the process returns to block 204 to identify and authorize the user. But if at block 230 the process determines that there is no new user, it goes to block 232 were it checks whether there are more events on the current user's timeline. If at block 232 there are more events on the current user's timeline, the process returns to block 218 were displays the timeline, the map, and the locations of the events remaining on the timeline and then proceeds to the remainder of the process. But if at block 232 the process determines that there are no more timeline events for the current user and that there are no new users, the process stops a block 234.

[0039] Figs. 3A-3C illustrate details of an automobile implementation of system 100. The different components described are coupled to each other substantially as system 100 and the elements of system 100 not shown in the drawings can be put elsewhere in the car, for instance in the dashboard or in the trunk.

[0040] Fig. 3A illustrates an embodiment 300 of the placement of user ID sensors on the exterior of a car 301. An automobile usually includes 3 pillars: an A pillar on both the driver and passenger sides between the windshield and the front side windows; a B pillar on both the driver and passenger sides between the front and rear side windows; and a C pillar on both the passenger and driver sides between the rear side window and the rear window.

[0041] In an embodiment, the user ID sensors are facial recognition cameras positioned on the B pillar on both the driver and passenger sides of the car to identify the driver and passengers before they enter the car. But in other embodiments cameras can be positioned differently. For instance, a facial recognition camera 305 can be placed in the car's interior pointing outward through the side window so as to capture an image of the face of the driver. In yet another embodiment, a facial recognition camera 307 can be put on the driver's side mirror. In other embodiments other types of sensors can be used and can be positioned differently than shown. For example, in an embodiment using fingerprint recognition fingerprint sensors could be put on the doors along the bottom of the windows.

[0042] Fig. 3B illustrates an automobile dashboard 302 which includes a plurality of displays. In the illustrated embodiment dashboard 302 includes a single display which can be configured to display different things in three software-configurable display regions 304, 306, and 308, but in other embodiments dashboard 302 can have a different number of display regions than shown and in still other embodiments regions 304, 306, and 308 can be physically separate displays. Dashboard 302 also includes hand gesture recognition cameras 310 and 312 positioned below display regions 304, 306, and 308, where they can capture video or images of a at least one of the driver's hands and both hands or a front passenger. Facial cameras 311 can also be positioned in the cabin, for instance where a rear-view mirror is or, if not present, where it normally would be, to capture video or still images of a driver and front passenger's faces. Cameras 311 can be used for facial recognition in embodiments that do not have external cameras as shown in Fig. 3A, or can be used for gesture recognition systems that support facial gesture or motion recognition. A display 313 can be positioned in the center of the steering wheel to act as a user input device and to provide additional display capabilities for the driver.

[0043] Fig. 3C is a plan view of an automobile interior 300. Automobile interior 300 includes dashboard 302 and also includes a driver's seat, a front passenger seat, and two rear passenger seats. As described above display regions 304, 306, and 308 in dashboard 302 provide displays for persons seated in the driver's seat and the front passenger seat. To provide displays for persons sitting in the rear passenger seats, rear passenger displays 314 can be positioned in the backs of the driver's seat and the front passenger seat. Each rear passenger display 314 includes a display unit on which a timeline and map can be displayed for each passenger as well as a facial camera 315 to capture selfies or facial gestures and motions and a hand camera 316 to capture hand gestures and motions of each passenger. [0044] A feedback mechanism 318 is positioned in the back of the driver's seat, as well as in the back of the front passenger seat and the backs of the rear passenger seats to provide haptic feedback to users regarding use of the mapping system. Each person occupying a seat in the car can thus control the timeline and map on their own display via gestures, be they hand gestures, facial gestures, etc., and receive feedback on their interaction with the system.

[0045] Figs. 4A-4D illustrate embodiments of a map display. Fig. 4A illustrates an embodiment of the basic layout of a map display 400 before addition of a user's events to the timeline and map. Timeline 402 is positioned horizontally across the top of display 400 with navigation map 406 below it. Timeline 402 includes one or more tick marks along the top of the line, and each tick mark is labeled below the line with a corresponding time 404. The time span of timeline 402 can be specified by the user or can be determined from the time span of the user events that will be displayed on the timeline. Map 406 is shown as a three-dimensional navigation map, but in other embodiments map 406 can be two-dimensional. Whether three- dimensional or two-dimensional, map 406 can also include additional features such as satellite views, street views, or three-dimensional views (e.g., like Google Earth).

[0046] In the illustrated embodiment map 406 appears below timeline 402, but in other embodiments the timeline and map can be arranged differently in the display. For instance, timeline 402 could appear horizontally across the bottom of the screen with map 406 positioned above it, or timeline 402 could appear vertically along the left or right sides of the display with map 406 positioned next to it.

[0047] Fig. 4B illustrates an embodiment of map display 400 with a user's events added to timeline 402. A current-time indicator 408 is shown on timeline 402 to indicate the current time. One or more events 410a-410d are also shown at their respective times on timeline 402. Each event 410 can be shown on timeline 402 using an icon as shown for events 410a, 410c and 410d, or can be shown without an icon such as shown for event 410b. For timeline events with an icon, the icon can include additional information obtained from remote user data sources 102a-102c— for instance, a photo of a person associated with the event (see, e.g., event 410c)— or can have some sort of other graphic associated with the icon (see, e.g., events 410a and 410d). Additional or different information can also be associated with each event and displayed on the timeline. For instance, events with or without an icon can include a title (e.g., "tennis practice" or "pick up son from school"), or a display of the start and end times in text instead of graphics (for example, tennis practice is from 9:30 am-10:30 am). Color can also be used, for instance to improve the clarity of the display or highlight certain events.

[0048] A circle 412 corresponding to each event 410 is shown on map 406 to indicate the location of the event: circle 412a indicates the location on the map of event 410a, circle 412b indicates the location on the map of event 410b, and so on. The route from event to event over the time span of the timeline is calculated and a line 414 indicating the expected path to all the events is shown on map 406. To make it easier for the user to see which location corresponds to which event, the display also draws a line 416 between each event 410 and its corresponding location 412. An icon 418 indicating the car's current location is also shown on map 406. Thus, the system provides route guidance based on the activities on the time line.

[0049] Timeline 402 can be modified by user interaction with the map display using a user input device such as gesture recognition system 134. Modifying the timeline can involve at least deleting existing events, modifying existing events, and adding new events. Modifications to the timeline are automatically reflected on timeline 402 and map 406, and are automatically transmitted to local user data storage 126, user account 104, remote user data sources 102a-102c, and local user data source 128 so that the data in those places can be updated to reflect changes made by the user's interaction with the map display. In some embodiments, changes made by user interaction with the map display can also be transmitted, for instance via e-mail or text message, to persons associated with that event.

[0050] To modify an existing event, the user can simply select the desired event and modify it accordingly. For instance, if the user wants to change event 104b to a time before event 410a, they could use a gesture or motion to select event 410b and, having selected it, use a motion to slide the event to the left over the timeline to a time before event 410a, then use another gesture to fix the event at the new time. To delete event 410b, the user can simply select item 410b and use a gesture to delete it. To add an event, the user can either add it via another user input device connected to the system, or can select the item from another display and drag it to the mapping display (see, e.g., Fig. 5). Events can be modified even if not currently shown on the timeline. For instance, if the user wants to modify an event that happens later this week but the timeline shows only today's events, the user can select the timeline and then use a gesture or motion to scroll to the right to advance to a later time period until the event the user wants to modify appears on the timeline.

[0051] Fig. 4C illustrates another embodiment of mapping display 400. The mapping display of Fig. 4C is similar in most respects to the one of Fig. 4B; the primary difference is that in Fig. 4C each event has an indicator 420 that shows the start time and end time, and hence the duration, of each event on the timeline that has a duration exceeding a certain threshold. Fig 4D is similar in most respects to Fig. 4B, the primary difference being that, to avoid clutter, in Fig. 4D only the earliest event— presumably the first one to navigate to or the one currently being navigated to— has a line joining the event on the timeline to its location in the map. [0052] Fig. 5 illustrates an embodiment of a system 500 in which there can be interaction and data exchange between interactive mapping system 100 and other devices. In system 500 the driver, the passenger, or both, can have devices like a smartwatch 502 and a smartphone 504. These kinds of devices are usually carried on the user, so if they belong to the driver and passenger they will be inside the car. In the illustrated embodiment, smartphone 504 can communicate wirelessly with transceiver 130 via a wireless connection such as Bluetooth, and smartwatch 502 can also communicate with transceiver 103, either directly or through smartphone 504, also via a wireless connection such as Bluetooth protocol. In other embodiments one or more of the connections shown, such as between smartphone 504 and transceiver 130, can be wired instead of wireless.

[0053] A remote person— that is, someone outside the car— can also have one or both of a smart watch 506 and a mobile phone 508. Smartphone 508 can communicate with an antenna 512, for instance the antenna on a Wi-Fi router or a cellular antenna located on a tower. Smart watch 506 can communicate with smart phone 508 via a protocol such as Bluetooth or Wi-Fi, or in some instances can communicate directly with antenna 512, for instance via Wi-Fi or cellular connection. Antenna 512 and its associated electronics can exchange information, for instance via the internet, with another antenna 514, such as a cellular antenna or Wi-Fi. Antenna 514 can then send data to and receive data from antenna 106, which is on or in the car (see Fig. 1).

[0054] System 500 allows the driver and/or passengers to exchange data with one or more persons remote from the car and shown on a map. For instance, if smartwatches 502 and 506 can both measure heart rate, that information can be collected from both smartwatches and shown on map 510. In the illustrated embodiment, map 501 shows that the driver currently has a heart rate of 72 beats per minute (bpm), while the remote person has a heart rate of 89 beats per minute. Other types of data can also be exchanged. For instance, the remote person smart watch or smartphone can transmit the person's current location or, can transmit messages from the remote user to the driver or passenger, can change a meeting time with the driver or passenger (which would also be reflected in the map's timeline), etc.

[0055] Figs. 6A-6D illustrate embodiments of gesture interactions that resize the display regions in a software-defined display such as the one shown in Fig. 3B. In the illustrated embodiments, the screen is initially partitioned into two software-defined regions 602 and 604. In the illustrated embodiment, region 602 shows car-related information and an electronic rear- view mirror, while region 604 shows the map display for the mapping system. To create a third software-defined display region 606, the user can use gestures to shrink region 604. Figs. 6A-6B illustrate a first embodiment. The user first makes a gesture in which they extend their index finger and then they position their hand such that circular cursor, which tracks the motion of the finger in substantially real time, is positioned at a location 610 that roughly corresponds to the location of an inter-region (or intra-di splay) separator. With the index finger still extended, the user moves their hand from position 610 to position 612. As the hand moves the inter-region separator follows, tracking the hand's motion in substantially real time, and stopping when the hand stops. And as inter-region separator 608 follows, a new software-defined display region 606 appears on one side of it, the right side in this embodiment, When the hand reaches position 612, the user simply lowers the hand to indicate that inter-region separator is now in the desired location and the three display regions are of the desired size (see Fig. 6B).

[0056] Figs. 6C-6D illustrate a second embodiment. The user first makes a gesture in which they extend their index finger and then they position their hand such that circular cursor, which tracks the motion of the finger in substantially real time, is positioned at a location 610 that roughly corresponds to the location of an inter-region (or intra-di splay) separator 608. To select inter-region separator 608, the user then forms a fist, as if gripping separator 608. With the hand still in a fist, the user moves the fist from position 610 to position 612. As the fist moves the inter-region separator follows, tracking the fist's motion in substantially real time, and stopping when the fist stops. And as inter-region separator 608 follows, a new software-defined display region 606 appears on one side of it, the right side in this embodiment, When the fist reaches position 612, the user simply spreads their fingers into an open hand (see Fig. 6D), thereby releasing their grip on inter-region separator 608 to indicate that inter-region separator is now in the desired location and that display regions 604 and 606 have their desired size.

[0057] Figs. 7A-7C together illustrate an embodiment of adding an event from another display region to the map timeline. Display 700 is a display such as the car dashboard display shown in Fig. 3B: it is a unitary display 700 configured to display different things on different software-define display regions 702, 704, and 706. In the illustrated embodiment the map and timeline are displayed in center region 704, while region 706 shows information such as available dining options. If a user wants to add one of the dining options from display region 706 to their schedule, they can use hand gestures and motionsto select the desired entertainment event from region 706 and drag it to region 704.

[0058] As shown in Fig. 7 A, in the illustrated embodiment, the user extends their index finger, causing circular cursor 708 to appear. With the index finger still extended, the user moves their hand and, as the hand moves cursor 708 follows the index finger, tracking the finger's motion in substantially real time, and stopping when the finger stops. When cursor 708 reaches desired item 710, the item highlights. As shown in Fig. 7B, when the desired item highlights the user changes to a pinching gesture, with the index, middle, and possibly the ring and pinky fingers brought together with the thumb, as if grasping the item. With the hand still mak- ing the pinching gesture, the user moves their hand toward the map display, as shown by the arrow, and cursor 708 and selected item 710 correspondingly move from display region 706 to display region 708, tracking the hand's motion in substantially real time, as shown by the arrow. As shown in Fig. 7C, the hand stops when cursor 708 and selected item 710 appear on the map. To release selected item 710 onto the map, the user extends all their finger, so that the hand is completely open with the palm facing the display. When released in display region 704, selected item 710 is added to the timeline and all the appropriate user data sources, local or remote, are updated accordingly to include the new event.

[0059] Fig. 8A illustrates an embodiment of a user selecting an item from a display. Display 800 is a single display with three software-definable display regions 802, 804, and 806. Among other things, display region 806 shows entertainment options, such as music that can be played in the car. In the illustrated embodiment, the user extends their index finger and points toward display region 806, causing circular cursor 808 to appear. To select an item from the display, the user moves their hand with the index finger still extended and, as the hand moves, cursor 808 follows the index finger, tracking the finger's motion in substantially real time, and stopping when the finger stops. When cursor 808 reaches desired item 810, the user thrusts the hand, or just the index finger, toward the screen— as if trying to poke the screen, as shown by the arrow— to confirm that item 810 is the desired selection.

[0060] Fig. 8B illustrates an embodiment of a user selecting an item from display 800. In the illustrated embodiment, the user selects an item by extending the thumb, index, middle, ring, and pinky fingers to form an open hand with the palm facing display region 806, causing circular cursor 808 to appear. To select an item from the display the user moves the hand and, as the hand moves, cursor 808 follows the hand, tracking the hand's motion in substantially real time, and stopping when the hand stops. When cursor 808 reaches desired item 810, the user confirms this item as their selection by quickly closing the hand to a fist, then opening the hand again to return to an open hand with the palm facing the display. Although the illustrated embodiment uses an open hand gesture with all four of the index, middle, ring, and pinky fingers extended, other embodiments need not use all four fingers; a gesture using one, two, or three of these fingers can be used, with the number of fingers that need to be closed to form the confirmation gesture (e.g., closing the hand to form a fist or a pinching gesture) being modified accordingly.

[0061] Fig. 8C illustrates an embodiment of a user selecting an item from display 800. In the illustrated embodiment, the user selects an item by extending the thumb, index, middle, ring, and pinky fingers to form an open hand with the palm facing display region 806, causing circular cursor 808 to appear. To select an item from the display the user moves the hand and, as the hand moves, cursor 808 follows the hand, tracking the hand's motion in substantially real time, and stopping when the hand stops. When cursor 808 reaches desired item 810, the user confirms this item as their selection by nodding their head in an up-and-down motion 812 to indicate yes. In an embodiment where the user suggests something to the user, the user can decline the suggestion by shaking their head in a side-to-side motion 814, indicating no. Although the illustrated embodiment uses an open hand gesture with all four of the index, middle, ring, and pinky fingers extended, other embodiments need not use all four fingers; a gesture using one, two, or three of these fingers can be used. Other embodiments can also use different head motions than shown.

[0062] Figs. 9A-9D illustrate an embodiment of selecting and deleting an item from the timeline. Display 900 is a single display with three software-definable display regions 902, 904, and 906. The map and timeline are shown in center display region 904. In some embodiments, user account 104 can use the data from remote user data sources 102a-102c, or computer 112 can use data from the local data storage 126, to provide suggestions to the user on another display, which the user can then add to their schedule using the map display. For instance, if a health app indicates that the user plays tennis, the map indicates that the user is near a tennis club, and the schedule indicates that there is a three-hour gap in the afternoon, the system can suggest a tennis practice to the user during that three-hour gap.

[0063] Figs. 9A-9B illustrate a first embodiment. In the illustrated embodiment, the system has suggested event 908 by automatically showing it on the timeline. If the user wants to decline suggested event 908, the user extends their index finger and points toward the timeline in display region 904. With the index finger still extended, the user moves their hand and, as the hand moves circular cursor 907 tracks the finger's motion along the timeline in substantially real time. When circular cursor 907 is over event 908, the user thrusts the hand, or just the index finger, toward the screen— as if trying to poke the screen, as shown by the arrow— to select event 908. Having selected event 908, as shown in Fig. 9B, the user changes to a pinching gesture, with the index, middle, and possibly the ring and pinky fingers brought together with the thumb, as if grasping the item. With the hand still making the pinching gesture, the user moves their hand toward the display region 902, as shown by the arrow, and selected item 908 correspondingly move from display region 904 to display region 902, tracking the hand's motion in substantially real time, as shown by the arrow. As soon event 908 is no longer in display region 904 it is automatically deleted from the timeline and all necessary data sources are uploaded accordingly.

[0064] Figs. 9C-9D illustrate another embodiment. If a user wants to decline suggested event 908, the user extends their thumb, index, middle, ring, and pinky fingers to form an open hand with the palm facing the display. With the hand still open, the user moves their hand and, as the hand moves the hand's motion is tracked by cursor 907 and displayed in substantially real time. As shown in Fig. 9D, when cursor 907 reaches suggested event 908, the user closes the hand to make a fist— as if grabbing suggested event 908— to select event 908. Having selected suggested event 908, the user, with the hand still forming a fist, moves their hand toward the display region 902, thus dragging suggested event 908 toward display region 902. Item 908 correspondingly moves from display region 904 to display region 902, tracking the hand's motion in substantially real time, as shown by the arrow. When event 908 is no longer in display region 904, the user releases the item, thus deleting it, by opening the hand again to return to an open hand with the palm facing the display. Although the illustrated embodiment uses an open hand gesture with the index, middle, ring, and pinky fingers extended, other embodiments need not use all four fingers; a gesture using one, two, or three of these fingers can be used, with the number of fingers that need to be closed to form the selection gesture (e.g., closing the hand to form a fist or a pinching gesture) being modified accordingly.

[0065] Figs. lOA-lOC illustrate embodiments of a user selecting an item from a display. Display 1000 is a single display with three software-definable display regions 1002, 1004, and 1006. Among other things, display region 1004 shows a three-dimensional user interface object 1008, with various selectableuser options 1012 positioned around it. I Fig. 10A illustrates an embodiment. In the illustrated embodiment, the user holds their hand in a cradling position, as if cradling object 1008. With the hand still in the cradling position, the user rotates the hand and, as the hand rotates object 1008 follows the hand rotation, tracking the hand's motion in substantially real time, and stopping when the hand stops. When object 1008 is stops with a particular user option positioned in front (i.e., appearing closest to the user), that option is automatically selected.

[0066] Fig. 10B illustrates another embodiment. In this embodiment, the user holds their hand with the thumb, index, middle, ring, and pinky fingers extended, so that the hand is open with the palm facing the display. With the hand open, the user then moves their hand up and down or side-to-side and, as the hand moves, the rotation of three-dimensional interface object 1008 follows the hand movement, tracking the hand's motion in substantially real time, and stopping when the hand stops. When the user has the desired selectable user option 1012 in the front (i.e., appearing closest to the user), the user then confirms that option 1012 as their selection by quickly closing the hand to a fist, then opening the hand again to return to an open hand with the palm facing the display. Although the illustrated embodiment uses an open hand gesture with the index, middle, ring, and pinky fingers extended, other embodiments need not use all four fingers; a gesture using one, two, or three of these fingers can be used, with the number of fingers that need to be closed to form the confirmation gesture (e.g., closing the hand to form a fist or a pinching gesture) being modified accordingly.

[0067] Fig. IOC illustrates an embodiment of a gesture for reversing an action. In the illustrated embodiment the user has selected a user option 1012 from three-dimensional user interface object 1008. Selection of that item has caused a menu 1014 to appear. But if upon reviewing menu 1014 the user finds that what they wanted does not appear in the menu, they can return to three-dimensional user interface object 1008 by holding their hand open— with the thumb, index, middle, ring, and pinky fingers extended so that the palm faces sideways— and making a swiping motion, as if slapping something. In the illustrated embodiment the hand motion is from right to left, with some acceleration of the hand during the motion. But in other embodiments the hand motion can be from left to right. Although illustrated in the context of three- dimensional user interface object 1008 and associated menus, the illustrated gesture can be used in any contact in which the user wishes to reverse an action to return to a previous state. Although the illustrated embodiment uses an open hand gesture with the index, middle, ring, and pinky fingers extended, other embodiments need not use all four fingers; a gesture using one, two, or three of these fingers can be used.

[0068] Fig. 11 illustrates an embodiment of gestures and motions that can be used to modify the appearance of items on a display, for instance by making them appear larger (i.e., zooming in) or smaller (i.e., zooming out). In the illustrated embodiment the user extends their thumb, index, middle, ring, and pinky fingers to form an open hand with the palm facing the display. With the hand still open, the user moves their hand and, as the hand moves the hand's motion is tracked and displayed by cursor 1108 in substantially real time. When cursor 1108 is in the display region in which the user wants to zoom in or out (center display region 1104 with a map display in this embodiment), the user closes the hand to make a fist— as if grabbing display region 1104— to select it. Having selected display region 1104 the user, with their hand still forming a fist, moves their hand toward display region 1104 (i.e., toward the screen and/or the gesture camera), to enlarge (i.e., zoom in on) what is shown in the display, or moves their hand away from display region 1104 (i.e., away from the screen and/or the gesture camera), to make smaller (i.e., zoom our of) what is shown in the display.

[0069] Fig. 12 illustrates an embodiment of gestures and motions that can be used to activate or deactivate the gesture recognition system. In some instances, it can be useful for the gesture recognition system not to be active all the time. In a car, for instance, the driver and passenger might use many hand gestures and motions during a conversation, but might not intend for those gestures or motions to be seen or interpreted by the gesture recognition system. If the gesture recognition does see and interpret these gestures or motions, it could cause setting, selec- tions, etc., to be inadvertently modified or it could cause items on a display to move around constantly, causing driver distraction. To prevent this, the system can be deactivated or, if not fully deactivated, set to where it doesn't show display motions that result from gestures. As a result, it can be necessary to have gestures and motions that partially or fully activate or deactivate the system.

[0070] In the illustrated embodiment, the system can examine an area 1208 for a specified time period and, if it sees no gestures or motions in the area for the specified time period it can partially or fully deactivate the gesture recognition. Alternatively, the gesture recognition system can be partially or fully deactivated by another event, such as when a hand touches steering wheel 1210. If the gesture recognition system has been partially or fully deactivated, it can be reactivated by the user by extending the thumb, index, middle, ring, and pinky fingers to form an open hand with the palm facing downward. This gesture is then held substantially stationary for a fixed period to activate the display.

[0071] The mapping system also has additional capabilities. The mapping system tracks how the user's day plays out. The mapping system can make adjustments based on changes. For example, if the location of an activity changes, the system automatically changes the location on the 3D map. If the start or end date of a meeting changes, for example, the system will automatically update the route. The system will automatically send the time changes to the people who will be at the meeting. Gestures can be used to change an appointment time. With very little input by the user, the car adjusts the pertinent information. For example, the system updates the calendar and tells friends about activities and changes to the activities.

[0072] The above description of embodiments, including what is described in the abstract, is not intended to be exhaustive or to limit the invention to the described forms. Specific embodiments of, and examples are described for illustrative purposes, but various equivalent modifications are possible within the scope of the invention in light of the above detailed description, as those skilled in the relevant art will recognize.