Patent Description:
Modern vehicles are becoming increasingly sophisticated, including in the amount of computer-based interactions they offer for the driver or passengers, and the complexity of such interactions and the powerful resources being provided to the user. Some previous efforts have provided a graphical user interface on one or more screens in a vehicle. However, such attempts have applied a monolithic perspective to the content or functions that are made available, and have not provided the user (e.g., the driver) with a technological framework that allows easy, high-level access to a variety of functions (e.g., for use while driving) and also provides the necessary tools for detailed and complex tasks (e.g., for use while parked). <CIT> discloses a method for synchronizing two display devices of a motor vehicle. The first display device already displays a first data set which comprises a first display content relating to a predetermined thematic context. A sensor device detects an operating gesture of a user, which comprises a movement of a body part of the operator carried out freely in space. A signal subsequently generated by the sensor device which describes the operating gesture is transmitted to a gesture recognition device which generates a control signal depending on the determined operating gesture. Depending on this control signal, a control device receiving the control signal determines the predetermined thematic context of the determined data set. Based on the determined predefined thematic context, a further data set with a second display content of the predefined thematic context is provided. This further data set is displayed on the second display device. <CIT> discloses a vehicle on-board display system comprising a first display unit, a second display unit, a vehicle information acquisition unit, and a CPU. <CIT> discloses an in-vehicle system including a meter cluster display arranged in a meter cluster and a head-up display that projects an image in an area above the meter cluster of a front window. <CIT> discloses a method and an arrangement for providing a user interface in a vehicle.

In a first aspect of the present invention, a computer-implemented method comprises: presenting a first drawer area on a first display device in an instrument panel of a vehicle, the first drawer area presented in an extended state where first content of a first application is visible in the first drawer area; presenting a second drawer area on a second display device in the instrument panel of the vehicle, the second drawer area presented in a retracted state where the first content of the first application is not visible in the second drawer area; receiving a first transition command regarding the first and second drawer areas; and in response to receiving the first transition command: presenting the first drawer area in the retracted state on the first display device instead of in the extended state, wherein the first content is not visible in the first drawer area in the retracted state; and presenting the second drawer area in the extended state on the second display device, wherein the first content of the first application is visible in the second drawer area, and wherein additional content of the first application that was not visible in the first drawer area is also visible in the second drawer area.

Implementations can include any or all of the following features. Receiving the first transition command comprises at least one of: detecting a tap on the first drawer area; detecting a tap on the second drawer area; detecting a swipe gesture on the first drawer area in a direction toward the second display device; or detecting a swipe gesture on the second drawer area in a direction away from the first display device. The retracted state on the second display device comprises that a header of the second drawer area, and not a body of the second drawer area, is presented on the second display device, wherein in the extended state on the second display device the header and the body of the second drawer area are presented on the second display device; and the retracted state on the first display device comprises that a header of the first drawer area, and not a body of the first drawer area, is presented on the first display device, wherein in the extended state on the first display device the header and the body of the first drawer area are presented on the first display device. In the retracted state on the second display device the header of the second drawer area is presented at a top edge of the second display device, and wherein in the retracted state on the first display device the header of the first drawer area is presented at a bottom edge of the first display device. Also a second application is associated with the first and second drawer areas. Presenting the first drawer area comprises: determining which of the first and second applications is active on the first display device; and in response determining that the first application is active on the first display device, providing the first content of the first application for presentation in the first drawer area. The computer-implemented method further comprises: receiving, while the first drawer area is presented in the retracted state and the second drawer area is presented in the extended state, a command to deactivate the first application on the first display device and to activate the second application on the first display device; and in response to receiving the command: ceasing to present the first content and the additional content of the first application in the second drawer area; and presenting in the second drawer area, with the second drawer area remaining in the extended state, second content of the second application and additional content of the second application. The computer-implemented method further comprises: receiving a second transition command regarding the first and second drawer areas, the second transition command received while the second content and the additional content of the second application are presented in the second drawer area; and in response to receiving the second transition command: presenting the first drawer area in the extended state on the first display device, where the second content of the second application is visible in the first drawer area and the additional content of the second application is not visible in the first drawer area; and presenting the second drawer area in the retracted state on the second display device, where the second content and the additional content are not visible in the second drawer area. The computer-implemented method further comprises: receiving a second transition command regarding the first and second drawer areas, the second transition command received while the second content and the additional content of the second application are presented in the second drawer area; and in response to receiving the second transition command: presenting the first drawer area in the extended state on the first display device, where the first content of the first application is visible in the first drawer area and the additional content of the first application is not visible in the first drawer area; and presenting the second drawer area in the retracted state on the second display device, where the first content and the additional content are not visible in the second drawer area. Receiving the second transition command comprises at least one of: detecting a tap on the first drawer area; detecting a tap on the second drawer area; detecting a swipe gesture on the first drawer area in a direction away from the second display device; or detecting a swipe gesture on the second drawer area in a direction toward the first display device.

In a second aspect of the present invention, a computer program product is tangibly embodied in a non-transitory storage medium, the computer program product including instructions that when executed cause a processor to perform operations, the operations comprising: presenting a first drawer area on a first display device in an instrument panel of a vehicle, the first drawer area presented in an extended state where first content of a first application is visible in the first drawer area; presenting a second drawer area on a second display device in the instrument panel of the vehicle, the second drawer area presented in a retracted state where the first content of the first application is not visible in the second drawer area; receiving a first transition command regarding the first and second drawer areas; and in response to receiving the first transition command: presenting the first drawer area in the retracted state on the first display device instead of in the extended state, wherein the first content is not visible in the first drawer area in the retracted state; and presenting the second drawer area in the extended state on the second display device, wherein the first content of the first application is visible in the second drawer area, and wherein additional content of the first application that was not visible in the first drawer area is also visible in the second drawer area.

In a third aspect of the present invention, a computer program product is tangibly embodied in a non-transitory storage medium, the computer program product including instructions that when executed cause a processor to generate a graphical user interface, the graphical user interface comprising: a first state in which: a first drawer area is presented on a first display device in an instrument panel of a vehicle, the first drawer area presented in an extended state where first content of a first application is visible in the first drawer area; and a second drawer area is presented on a second display device in the instrument panel of the vehicle, the second drawer area presented in a retracted state where the first content of the first application is not visible in the second drawer area, the second display device positioned lower in the instrument panel than the first display device; a second state in which: the first drawer area is presented in the retracted state on the first display device instead of in the extended state, wherein the first content is not visible in the first drawer area in the retracted state; and the second drawer area is presented in the extended state on the second display device, wherein the first content of the first application is visible in the second drawer area, and wherein additional content of the first application that was not visible in the first drawer area is also visible in the second drawer area; and an input control configured for generating a first transition command, wherein the graphical user interface is configured to switch between the first and second states in response to the first transition command.

Implementations can include any of the following features. The first transition command corresponds to at least one of: a tap detected on the first drawer area; a tap detected on the second drawer area; a swipe gesture detected on the first drawer area in a direction toward the second display device; or a swipe gesture detected on the second drawer area in a direction away from the first display device. The retracted state on the second display device comprises that a header of the second drawer area, and not a body of the second drawer area, is presented on the second display device, wherein in the extended state on the second display device the header and the body of the second drawer area are presented on the second display device; and the retracted state on the first display device comprises that a header of the first drawer area, and not a body of the first drawer area, is presented on the first display device, wherein in the extended state on the first display device the header and the body of the first drawer area are presented on the first display device. In the retracted state on the second display device the header of the second drawer area is presented at a top edge of the second display device, and wherein in the retracted state on the first display device the header of the first drawer area is presented at a bottom edge of the first display device.

This document describes examples of systems and techniques for providing flexible tools to a vehicle occupant (e.g., the driver) that allow easy, high-level access to certain functions, and to allow the vehicle occupant to perform more detailed or complex tasks relating to these functions on a device more suited for that kind of interaction. The tool(s) for tasks that are intended or suitable for interaction while driving can be provided approximately at an occupant eye level for use while driving, and the tool(s) for the richer, more detailed/complex operations can be provided elsewhere (e.g., at a center console). Moreover, the tools can be organized according to a paradigm that provides a flexible, intuitive, and continuous way of transitioning between two or more tasks. Such tasks can be directed toward consuming the content (e.g., viewing it and/or making basic inputs approximately at eye level), or actively interacting with the content at a deeper level (e.g., in a position more conducive to typing or making other screen inputs). Some implementations can provide a complex architecture of two or more display devices within the passenger compartment of a vehicle that seamlessly and transparently supports the vehicle occupant's transition between different types of tasks.

Examples herein refer to a vehicle. A vehicle is a machine that transports passengers or cargo, or both. A vehicle can have one or more motors using at least one type of fuel or other energy source (e.g., electricity). Examples of vehicles include, but are not limited to, cars, trucks, and buses. The number of wheels can differ between types of vehicles, and one or more (e.g., all) of the wheels can be used for propulsion of the vehicle. The vehicle can include a passenger compartment accommodating one or more persons. At least one vehicle occupant can be considered the driver; various tools, implements, or other devices, can then be provided to the driver. In some implementations, an instrument panel can be provided toward the front of the passenger compartment. For example, the instrument panel has a steering wheel or other steering device(s), and an instrument cluster including controls or indicators.

Examples herein refer to display devices. A display device visually outputs a graphical user interface for one or more computer devices. A display device can operate according to any of multiple display technologies used for presenting computer-based information. A display device can include a liquid crystal display (LCD), a light-emitting diode (LED) display, and/or a plasma display, to name just a few examples. A display device can be configured for receiving input for the computer device(s). In some implementations, a display device can feature one or more types of technology for detecting contact with, or proximity to, the screen by a user's hand or an implement such as a stylus. A display device can operate according to any of multiple touch-detecting, or gesture-recognizing, technologies. A display device can include a resistive touchscreen, a capacitive touchscreen, and/or a touchscreen based on optical imaging, to name just a few examples. A display device can have any of multiple shapes. In some implementations, a display device has a quadrilateral shape (e.g., rectangular), or a non-polygonal shape, to name just a few examples. A display device can have a substantially flat form factor (e.g., the screen is essentially planar), or a non-flat form factor (e.g., the screen is curved according to one or more radiuses. ) Two or more display devices can be positioned according to any of multiple spatial relationships with regard to each other. One display device can be placed substantially above another display device in a vertical direction. One display device can be placed substantially to the side of another display device in a horizontal direction. One display device can be placed diagonally from another display device in any direction. Two or more display devices can be positioned so as to face in a common direction. Two or more display devices can be positioned so as to face in different directions from each other.

Examples herein refer to a drawer area being presented on one or more display devices. A drawer area is a portion of screen real estate that is dedicated for holding or containing output from one or more applications. A graphical user interface can be configured so that the drawer area can be presented in either of at least two states. An extended state can comprise that all (or mostly all) of the drawer area and its associated contents are visible on the display device. For example, the display device can then show both a header and a body of the drawer area. A retracted state can comprise that only some (or almost none) of the drawer area is visible on the display device. For example, the display device can then show a header, but not a body, of the drawer area. The same drawer area can be associated with more than one display device. A drawer area can have different states on separate display devices at the same time. For example, the drawer area can have an extended state on one display device simultaneously with having a retracted state on another display device.

Examples herein refer to one or more transitions of a drawer area. A transition can involve changing the drawer area from one state to another state. For example, the drawer area can be transitioned from an extended state to a retracted state, or vice versa. A user can trigger the computer device to perform the transition by making one or more kinds of input corresponding to a transition command. In some implementations, a tap on a display device can be recognized. For example, the user can tap on a retracted drawer area to transition the drawer area into an extended state. As another example, the user can tap on an extended drawer area to transition the drawer area into a retracted state. In some implementations, a swipe gesture can be recognized on a display device. For example, the user can swipe on a retracted drawer area, in a direction of extending the drawer area, to transition the drawer area into an extended state. As another example, the user can swipe on an extended drawer area, in a direction of retracting the drawer area, to transition the drawer area into a retracted state. In some implementations, one or more voice control commands can be recognized by a computer device and trigger a transition of a drawer area. For example, a computing device <NUM> in <FIG> can recognize voice commands using a microphone <NUM>. In some implementations, pressing one or more buttons or keys can trigger a transition of a drawer area. For example, the computing device <NUM> can detect one or more buttons/keys being pressed on a keyboard <NUM>.

<FIG> show an example of an instrument panel <NUM> of a vehicle <NUM>. The vehicle <NUM> is mostly omitted in the present illustrations for simplicity. The vehicle <NUM> includes a steering wheel <NUM> (here shown in phantom for clarity), that can be used in connection with, or independently of, one or more controls or functions available at the instrument panel <NUM>. In some implementations, the steering wheel <NUM> can include one or more buttons, scroll wheels, or other controls by which the driver can make at least one input. For example, the driver can trigger a transition. The instrument panel <NUM> can be used in combination with one or more other examples described elsewhere herein.

The instrument panel <NUM> includes a display device <NUM> here positioned somewhat to the left of the steering wheel <NUM>. In some implementations, the display device <NUM> provides content <NUM> corresponding to controls and/or output for one or more functions that should be visible at all times. For example, the display device <NUM> can relate to one or more of door closure sensors; headlights; door locks; a hood closure sensor; a charge port closure sensor; or a trunk closure sensor.

The instrument panel <NUM> includes a display device <NUM> here positioned essentially behind the steering wheel <NUM>. In some implementations, the display device <NUM> provides content <NUM> corresponding to controls and/or output for one or more functions that form a digital cluster for the vehicle <NUM>. For example, the display device <NUM> can relate to one or more of a vehicle status; a vehicle suspension operating mode; gear selection; odometry; speed; vehicle range (based on remaining electric charge or fuel amount); road speed limit; or driver assistance system status.

The instrument panel <NUM> includes a display device <NUM> here positioned somewhat to the right of the steering wheel <NUM>. The display device <NUM> can be horizontally aligned with an instrument cluster in the vehicle <NUM>. For example, the instrument cluster can include at least the display device <NUM>. In some implementations, the display device <NUM> provides content <NUM> corresponding to controls and/or output for one or more applications. For example, the display device <NUM> can relate to infotainment applications. The display device <NUM> can include a persistent sidebar <NUM>. In some implementations, the persistent sidebar <NUM> includes controls for activating a home screen, a navigation application, a media application, or a phone application. The display device <NUM> can include a persistent status bar <NUM>. The persistent status bar <NUM> can provide visual non-interactive indicators. For example, the persistent status bar <NUM> can indicate a current driver profile, a current time, and/or a connectivity status.

In <FIG>, a control 118B for the navigation application has been activated, and the navigation application is providing output that is presented as the content <NUM>. The content <NUM> includes a map <NUM> and a drawer area <NUM>, both generated by the navigation application. The drawer area <NUM> is currently in an extended state. For example, a header 124A and a body 124B of the drawer area <NUM> are currently visible on the display device <NUM> when the drawer area <NUM> is in the extended state. The body 124B presently has content including a rubric "Categories," icons for respective charging, restaurants, and favorites, and a listing of recent destinations or points of interest. When the display device <NUM> is to be populated with the content <NUM>, a determination can be made as to which of the applications is active, and the content of that application (e.g., here the map <NUM> and the contents of the drawer area <NUM>) can be provided.

The instrument panel <NUM> includes a display device <NUM> here positioned lower than (e.g., essentially vertically below) the display device <NUM>. The display device <NUM> is considered to be positioned in the instrument panel <NUM>. For example, the display device <NUM> can be positioned lower in the same physical housing in which the display devices <NUM>, <NUM>, and <NUM> are mounted. As another example, the display device <NUM> can be mounted in a center console positioned between first-row seats in the vehicle <NUM>, so as to be reachable by the driver (and optionally a first-row passenger). In some implementations, the display device <NUM> provides content <NUM> including controls and/or output for one or more core applications for the vehicle <NUM>. For example, the content <NUM> can relate to heating, ventilation, and air conditioning (HVAC) functions or climate control; one or more vehicle functions; or system settings for the vehicle <NUM>. In <FIG>, the content <NUM> on the display device <NUM> relates to HVAC/climate control.

The display device <NUM> can include a drawer area <NUM>. The drawer area <NUM> is currently in a retracted state. For example, only a header 130A, and not a body, of the drawer area <NUM> is currently visible on the display device <NUM> when the drawer area <NUM> is in the retracted state. The header 130A is positioned at a top edge of the display device <NUM>. The drawer area <NUM> can correspond to the drawer area <NUM>. For example, when the drawer area <NUM> is in the retracted state, the drawer area <NUM> can be in the extended state, and vice versa.

The display devices <NUM>, <NUM>, <NUM>, and <NUM> can be driven by one or more graphics processors (e.g., by one or more graphics boards). In some implementations, separate graphics processors are used for at least two of the display devices <NUM>, <NUM>, <NUM>, and <NUM>. For example, one graphics board can be used for the display devices <NUM> and <NUM>, and another graphics board can be used for the display devices <NUM> and <NUM>.

An occupant of the vehicle <NUM> can trigger one or more transitions by generating a transition command. For example, the user can do one or more of tapping on the drawer area <NUM> (e.g., in the header 124A thereof); performing a swipe gesture on the drawer area <NUM> (e.g., swiping in a direction toward the display device <NUM>); tapping on the drawer area <NUM> (e.g., in the header 130A thereof); performing a swipe gesture on the drawer area <NUM> (e.g., swiping in a direction away from the display device <NUM>); issuing a voice command; or pressing a button/key.

<FIG> shows an example of the instrument panel <NUM> after a transition has been performed. Elements from <FIG> that are not mentioned below may remain essentially the same (e.g., remain in a same state) as in the examples above.

The drawer area <NUM> on the display device <NUM> is currently in a retracted state. In some implementations, only the header 124A, and not the body 124B, of the drawer area <NUM> is presently visible on the display device <NUM>. For example, the header 124A can be positioned at a bottom edge of the display device <NUM> when the drawer area <NUM> is in the retracted state.

The drawer area <NUM> on the display device <NUM> is currently in an extended state. In some implementations, the header 130A and a body 130B of the drawer area <NUM> are both presently visible on the display device <NUM>. The body 130B can include some or all content that was in the drawer area <NUM> in <FIG>. For example, the body 130B presently includes content including the rubric "Categories," icons for respective charging, restaurants, and favorites, and a listing of recent destinations or points of interest, all of which were presented in the body 124B of the drawer area <NUM> in <FIG>. The body 130B can include additional content that was not visible in the drawer area <NUM> in <FIG>. For example, the body 130B can include an additional function of the currently active application (here, the navigation application). In some implementations, the additional function can include a text entry field <NUM>. For example, an on-screen keyboard (e.g., the keyboard <NUM> in <FIG>) may be available on the display device <NUM>, whereas the on-screen keyboard may not be available on the display device <NUM>.

The above examples illustrate that a computer-implemented method can include presenting a first drawer area (e.g., the drawer area <NUM>) on a first display device (e.g., the display device <NUM>) in an instrument panel (e.g., the instrument panel <NUM>) of a vehicle (e.g., the vehicle <NUM>). The first drawer area can be presented in an extended state (e.g., as shown in <FIG>) where first content (e.g., content in the body 124B) of a first application is visible in the first drawer area. The method can include presenting a second drawer area (e.g., the drawer area <NUM>) on a second display device (e.g., the display device <NUM>) in the instrument panel of the vehicle. The second drawer area can be presented in a retracted state (e.g., as shown in <FIG>) where the first content of the first application is not visible in the second drawer area. The method can include receiving a first transition command regarding the first and second drawer areas. In response to receiving the first transition command, the method can include presenting the first drawer area in the retracted state (e.g., as shown in <FIG>) on the first display device instead of in the extended state. The first content may not be visible in the first drawer area in the retracted state. In response to receiving the first transition command, the method can also include presenting the second drawer area in the extended state (e.g., as shown in <FIG>) on the second display device. The first content of the first application may be visible in the second drawer area. Additional content of the first application (e.g., the text entry field <NUM>) that was not visible in the first drawer area may also be visible in the second drawer area. The second display device can be positioned lower (e.g., to facilitate on-screen typing) in the instrument panel than the first display device (e.g., which may be in the driver's line of sight).

One or more additional transitions can be performed. For example, this can be done when the user has finished performing a detailed or complex task using the display device <NUM>, or if the user changes his or her mind about performing the task(s). In some implementations, the user can generate another transition command to trigger a transition back to essentially the state shown in <FIG>. For example, the drawer area <NUM> can then be brought into the retracted state, and the drawer area <NUM> can be brought into the extended state.

<FIG> show another example of the instrument panel <NUM> of <FIG>. Here, only the display devices <NUM> and <NUM> are shown for simplicity. In <FIG>, the control 118B for the navigation application has been activated, and the navigation application is providing output that is presented as the content <NUM>. The navigation is currently being used for active route guidance. The content <NUM> includes the map <NUM> and the drawer area <NUM>, both generated by the navigation application. The drawer area <NUM> is currently in the extended state. For example, the body 124B of the drawer area <NUM>, and a turn direction <NUM> of the active route guidance, are currently visible on the display device <NUM> when the drawer area <NUM> is in the extended state. The body 124B presently has content including a time of arrival at the navigation destination; a remaining travel time to the destination; a distance to the destination; and an "End" control for terminating the navigation to the destination. When the display device <NUM> is to be populated with the content <NUM>, a determination can be made as to which of the applications is active, and the content of that application (e.g., here the map <NUM> and the contents of the drawer area <NUM>) can be provided.

The display device <NUM> currently provides content corresponding to a core application for the vehicle. The drawer area <NUM> is currently in the retracted state. For example, only the header 130A, and not the body, of the drawer area <NUM> is currently visible on the display device <NUM> when the drawer area <NUM> is in the retracted state. The header 130A is positioned at a top edge of the display device <NUM>.

An occupant of the vehicle can trigger one or more transitions by generating a transition command. For example, the user can do one or more of tapping on the drawer area <NUM>; performing a swipe gesture on the drawer area <NUM> (e.g., swiping in a direction toward the display device <NUM>); tapping on the drawer area <NUM> (e.g., in the header 130A thereof); performing a swipe gesture on the drawer area <NUM> (e.g., swiping in a direction away from the display device <NUM>); issuing a voice command; or pressing a button/key.

The drawer area <NUM> on the display device <NUM> is currently in a retracted state. In this example, the retracted state has the same appearance as the extended state for the drawer area <NUM>. In some implementations, the body 124B of the drawer area <NUM> is presently visible on the display device <NUM>.

The drawer area <NUM> on the display device <NUM> is currently in an extended state. In some implementations, the header 130A and the body 130B of the drawer area <NUM> are both presently visible on the display device <NUM>. The body 130B can include some or all content that was in the drawer area <NUM> in <FIG>. For example, the body 130B presently includes content including a time of arrival at the navigation destination; a remaining travel time to the destination; a distance to the destination; and an "End" control for terminating the navigation to the destination, all of which were presented in the body 124B of the drawer area <NUM> in <FIG>. The body 130B can include additional content that was not visible in the drawer area <NUM> in <FIG>. The body 130B can include a listing of turn-by-turn directions; more information about each turn direction; an overview map <NUM> showing an entire route of the navigation; and/or a control <NUM> for access to third party content. In some implementations, the navigation application may currently be focusing on an establishment (e.g., a restaurant) at a destination, and the control <NUM> can trigger presentation of an area <NUM> on the display device <NUM>. For example, the area <NUM> can present a reservation function (e.g., a booking or calendaring interface) relating to the establishment.

One or more additional transitions can be performed. For example, this can be done when the user has finished performing a detailed or complex task using the display device <NUM>, or if the user changes his or her mind about performing the task(s). In some implementations, the user can generate another transition command to trigger a transition back to essentially the state shown in <FIG>. For example, the drawer area <NUM> can then be brought into the retracted state, and the drawer area <NUM> can be brought into the extended state (which can have the same appearance as the extended state).

<FIG> show another example of the instrument panel <NUM> of <FIG>. Here, only the display devices <NUM> and <NUM> are shown for simplicity. In <FIG>, a control 118C for the media application has been activated, and the media application is providing output that is presented as the content <NUM>. The media application is currently outputting media content in a media player <NUM>. The content <NUM> includes the media player <NUM> and the drawer area <NUM>, both generated by the media application. The drawer area <NUM> is currently in the extended state. For example, the header 124A and the body 124B of the drawer area <NUM> are currently visible on the display device <NUM> when the drawer area <NUM> is in the extended state. The body 124B presently has content including a playlist of media content. When the display device <NUM> is to be populated with the content <NUM>, a determination can be made as to which of the applications is active, and the content of that application (e.g., here the media player <NUM> and the contents of the drawer area <NUM>) can be provided.

The drawer area <NUM> on the display device <NUM> is currently in an extended state. In some implementations, the header 130A and the body 130B of the drawer area <NUM> are both presently visible on the display device <NUM>. The body 130B can include some or all content that was in the drawer area <NUM> in <FIG>. For example, the body 130B presently includes the playlist of media content. The body 130B can include additional content that was not visible in the drawer area <NUM> in <FIG>. The body 130B can include media art <NUM> (e.g., album art) for the tracks on the playlist, and controls <NUM> for choosing among media providers (e.g., radio or streaming services).

The user can switch between applications. This can be done by generating a command that deactivates the current application and that activates another application. Here, if the user activates the control 118B the currently active media application would be replaced by the navigation application. The instrument panel <NUM> could then enter a state similar or identical to that shown in <FIG>. The drawer area <NUM> on the display device <NUM> can remain extended and can instead be populated with content from the newly activated application (here the navigation application). For example, the drawer area <NUM> can cease to present the playlist of media content, the media art <NUM>, and the controls <NUM>, and can instead present the contents of the body 130B in <FIG>. That is, if the drawer area <NUM> is in an extended state when the command is generated, the drawer area <NUM> can remain in the extended state after the other application is activated. Similarly, if the drawer area <NUM> is in an extended state when the command is generated, the drawer area <NUM> can remain in the extended state after the other application is activated. Assuming that the transition to the navigation application has occurred, if the user thereafter triggers transition of the drawer area <NUM> in the state shown in <FIG>, then as exemplified above the instrument panel <NUM> can instead assume a state similar or identical to that shown in <FIG>.

<FIG> show another example of the instrument panel <NUM> of <FIG>. Here, only the display devices <NUM> and <NUM> are shown for simplicity. In <FIG>, a control 118D for the phone application has been activated, and the phone application is providing output that is presented as the content <NUM>. The phone application is currently conducting a phone call using a dialer <NUM>. The content <NUM> includes the dialer <NUM> and the drawer area <NUM>, both generated by the phone application. The drawer area <NUM> is currently in the extended state. For example, the header 124Aand the body 124B of the drawer area <NUM> are currently visible on the display device <NUM> when the drawer area <NUM> is in the extended state. The body 124B presently has content including contact information for the other party of the current phone call. When the display device <NUM> is to be populated with the content <NUM>, a determination can be made as to which of the applications is active, and the content of that application (e.g., here the dialer <NUM> and the contents of the drawer area <NUM>) can be provided.

The drawer area <NUM> on the display device <NUM> is currently in an extended state. In some implementations, the header 130A and the body 130B of the drawer area <NUM> are both presently visible on the display device <NUM>. The body 130B can include some or all content that was in the drawer area <NUM> in <FIG>. For example, the body 130B presently includes the contact information for the other party of the current phone call. The body 130B can include additional content that was not visible in the drawer area <NUM> in <FIG>. The body 130B can include additional information <NUM> about the contact, and controls <NUM> for choosing outputs of the phone application. For example, the controls <NUM> can allow switching between contacts, messages, and a dial pad.

As another example, if the user activates a control 118A a home screen application can be activated instead of the phone application. In some implementations, the home screen application does not have a drawer associated with it. For example, the drawer area <NUM> can then be omitted from the display device <NUM>, and the drawer area <NUM> can be omitted from the display device <NUM>.

<FIG> shows an example of a state diagram <NUM> for a graphical user interface. The state diagram <NUM> can be used with one or more other examples described elsewhere herein. For example, one or more display devices described with reference to the instrument panel <NUM> can operate according to the state diagram <NUM>.

The state diagram <NUM> includes a home screen state <NUM>. In some implementations, the home screen state <NUM> can be the default state when the vehicle's infotainment system powers up. As another example, the user can switch to the home screen application by activating the control 118A (<FIG>).

The state diagram <NUM> includes a drawer up state <NUM>. The drawer up state <NUM> can involve at least one application (e.g., an infotainment application) being active and providing output. The drawer up state <NUM> can correspond to one or more of the situations illustrated in <FIG>, <FIG>, <FIG>, or <FIG>. In some implementations, the graphical user interface can enter the drawer up state <NUM> by a transition <NUM> from the home screen state <NUM>. For example, the transition <NUM> can be triggered by activating any of the controls 118B-118D in the instrument panel <NUM>. In some implementations, the graphical user interface can enter the home screen state <NUM> by a transition <NUM> from the drawer up state <NUM>. For example, the transition <NUM> can be triggered by activating the control 118A in the instrument panel <NUM>.

In the drawer up state <NUM>, a transition <NUM> can be performed while remaining in the drawer up state <NUM>. In some implementations, the transition <NUM> involves switching from one application (e.g., an infotainment application) to another application (e.g., another infotainment application), wherein the drawer area <NUM> on the display device <NUM> is in the extended state before, during, and after the transition <NUM>. For example, the transition <NUM> can involve switching from the state shown in one of <FIG>, <FIG>, <FIG>, or <FIG> to the state shown in another of <FIG>, <FIG>, <FIG>, or <FIG>.

The state diagram <NUM> includes a drawer down state <NUM>. The drawer down state <NUM> can involve at least one application (e.g., an infotainment application) being active and providing output. The drawer down state <NUM> can correspond to one or more of the situations illustrated in <FIG>, <FIG>, <FIG>, or <FIG>. In some implementations, the graphical user interface can enter the drawer down state <NUM> by a transition <NUM> from the drawer up state <NUM>. For example, the transition <NUM> can be triggered by a tap, a swipe gesture, a voice command, or a button/key press. In some implementations, the graphical user interface can enter the drawer up state <NUM> by a transition <NUM> from the drawer down state <NUM>. For example, the transition <NUM> can be triggered by a tap, a swipe gesture, a voice command, or a button/key press. In some implementations, the graphical user interface can enter the home screen state <NUM> by a transition <NUM> from the drawer down state <NUM>. For example, the transition <NUM> can be triggered by activating the control 118A in the instrument panel <NUM>.

In the drawer down state <NUM>, a transition <NUM> can be performed while remaining in the drawer down state <NUM>. In some implementations, the transition <NUM> involves switching from one application (e.g., an infotainment application) to another application (e.g., another infotainment application), wherein the drawer area <NUM> on the display device <NUM> is in the extended state before, during, and after the transition <NUM>. For example, the transition <NUM> can involve switching from the state shown in one of <FIG>, <FIG>, <FIG>, or <FIG> to the state shown in another of <FIG>, <FIG>, <FIG>, or <FIG>.

The terms "up" and "down" that occur in the previous examples are used for illustrative purposes only and do not necessarily indicate spatial position, or a relative spatial position, of any drawer area or display device. For example, in the drawer up state <NUM> a drawer area can be in an extended state on a display device that is not positioned higher than another display device where the corresponding drawer area is in a retracted state. As another example, in the drawer down state <NUM> a drawer area can be in an extended state on a display device that is not positioned lower than another display device where the corresponding drawer area is in a retracted state.

The above examples illustrate that a graphical user interface (e.g., in the instrument panel <NUM>) can include a first state (e.g., the drawer up state <NUM>) in which a first drawer area (e.g., the drawer area <NUM>) is presented on a first display device in an instrument panel of a vehicle, the first drawer area presented in an extended state (e.g., as shown in any of <FIG>, <FIG>, <FIG>, or <FIG>) where first content of a first application is visible in the first drawer area. In the first state, a second drawer area (e.g., the drawer area <NUM>) is presented on a second display device in the instrument panel of the vehicle, the second drawer area presented in a retracted state (e.g., as shown in any of <FIG>, <FIG>, <FIG>, or <FIG>) where the first content of the first application is not visible in the second drawer area. The second display device can be positioned lower in the instrument panel than the first display device.

The graphical user interface can include a second state in which the first drawer area is presented in the retracted state (e.g., as shown in any of <FIG>, <FIG>, <FIG>, or <FIG>) on the first display device instead of in the extended state, wherein the first content is not visible in the first drawer area in the retracted state. In the second state, the second drawer area is presented in the extended state (e.g., as shown in any of <FIG>, <FIG>, <FIG>, or <FIG>) on the second display device, wherein the first content of the first application is visible in the second drawer area, and wherein additional content of the first application that was not visible in the first drawer area is also visible in the second drawer area.

The graphical user interface can include an input control (e.g., a touchscreen, voice recognition function, or a button/keyboard) configured for generating a first transition command, wherein the graphical user interface is configured to switch between the first and second states in response to the first transition command.

<FIG> schematically shows an organization <NUM> of content from an application. The organization <NUM> can be used with one or more other examples described elsewhere herein. In some implementations, the organization <NUM> can be used with one or more infotainment applications. For example, the organization <NUM> can be used with one or more of the navigation, media, or phone applications described with regard to the instrument panel <NUM>.

The organization <NUM> here relates to at least one application <NUM>. The application <NUM> can include one or more applications described herein, or another application. The application <NUM> can generate output for a graphical user interface. For example, the output can be presented on one or more display devices. In some implementations, the application <NUM> can generate output to be presented on a display device <NUM> and/or on a display device <NUM>. The display devices <NUM> and <NUM> are here schematically illustrated as rectangles having dashed outlines.

The application <NUM> can generate drawer content <NUM>. In some implementations, the drawer content <NUM> can include high-level application output that a user can consume also while engaged in a relatively demanding activity (e.g., while driving a vehicle). For example, the drawer content <NUM> can include one or more types of content shown in the body 124B (e.g., in any of <FIG>, <FIG>, <FIG>, or <FIG>). As such, the drawer content <NUM> can be presented on the display device <NUM>, as schematically illustrated in <FIG>. Some or all of the content shown in the body 124B can also or instead be presented in the body 130B (e.g., as shown in any of <FIG>, <FIG>, <FIG>, or <FIG>). As such, the drawer content <NUM> can be presented on the display device <NUM>, as schematically illustrated in <FIG>.

The application <NUM> can generate top-screen content <NUM>. In some implementations, the top-screen content <NUM> can include high-level application output that a user can consume also while engaged in a relatively demanding activity (e.g., while driving a vehicle), and which may not be directly applicable to any detailed or complex task relating to the same application. For example, the top-screen content <NUM> can include the content <NUM> (e.g., in any of <FIG>, <FIG>, <FIG>, or <FIG>). As such, the top-screen content <NUM> can be presented on the display device <NUM>, as schematically illustrated in <FIG>, and the top-screen content <NUM> may not appear on the display device <NUM>.

The application <NUM> can generate bottom-screen content <NUM>. In some implementations, the bottom-screen content <NUM> can include detailed or otherwise complex application output that a user can consume or interact with when not engaged in a relatively demanding activity (e.g., in a parked vehicle). For example, the bottom-screen content <NUM> can include one or more types of content shown in the body 130B (e.g., in any of <FIG>, <FIG>, <FIG>, or <FIG>). As such, the bottom-screen content <NUM> can be presented on the display device <NUM>, as schematically illustrated in <FIG>, and the bottom-screen content <NUM> may not appear on the display device <NUM>.

The terms "top" and "bottom" that occur in the previous examples are used for illustrative purposes only and do not necessarily indicate spatial position, or a relative spatial position, of any drawer area or display device. For example, the display device <NUM> may not be positioned higher than the display device <NUM>.

<FIG> illustrates an example architecture of a computing device <NUM> that can be used to implement aspects of the present invention, including any of the systems, apparatuses, and/or techniques described herein, or any other systems, apparatuses, and/or techniques that may be utilized in the various possible embodiments.

The computing device illustrated in <FIG> can be used to execute the operating system, application programs, and/or software modules (including the software engines) described herein.

The computing device <NUM> includes, in some embodiments, at least one processing device <NUM> (e.g., a processor), such as a central processing unit (CPU). A variety of processing devices are available from a variety of manufacturers, for example, Intel or Advanced Micro Devices. In this example, the computing device <NUM> also includes a system memory <NUM>, and a system bus <NUM> that couples various system components including the system memory <NUM> to the processing device <NUM>. The system bus <NUM> is one of any number of types of bus structures that can be used, including, but not limited to, a memory bus, or memory controller; a peripheral bus; and a local bus using any of a variety of bus architectures.

Examples of computing devices that can be implemented using the computing device <NUM> include a desktop computer, a laptop computer, a tablet computer, a mobile computing device (such as a smart phone, a touchpad mobile digital device, or other mobile devices), or other devices configured to process digital instructions.

The system memory <NUM> includes read only memory <NUM> and random access memory <NUM>. A basic input/output system <NUM> containing the basic routines that act to transfer information within computing device <NUM>, such as during start up, can be stored in the read only memory <NUM>.

The computing device <NUM> also includes a secondary storage device <NUM> in some embodiments, such as a hard disk drive, for storing digital data. The secondary storage device <NUM> is connected to the system bus <NUM> by a secondary storage interface <NUM>. The secondary storage device <NUM> and its associated computer readable media provide nonvolatile and non-transitory storage of computer readable instructions (including application programs and program modules), data structures, and other data for the computing device <NUM>.

Although the example environment described herein employs a hard disk drive as a secondary storage device, other types of computer readable storage media are used in other embodiments. Examples of these other types of computer readable storage media include magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, compact disc read only memories, digital versatile disk read only memories, random access memories, or read only memories. Some embodiments include non-transitory media. For example, a computer program product can be tangibly embodied in a non-transitory storage medium. Additionally, such computer readable storage media can include local storage or cloud-based storage.

A number of program modules can be stored in secondary storage device <NUM> and/or system memory <NUM>, including an operating system <NUM>, one or more application programs <NUM>, other program modules <NUM> (such as the software engines described herein), and program data <NUM>. The computing device <NUM> can utilize any suitable operating system, such as Microsoft Windows™, Google Chrome™ OS, Apple OS, Unix, or Linux and variants and any other operating system suitable for a computing device. Other examples can include Microsoft, Google, or Apple operating systems, or any other suitable operating system used in tablet computing devices.

In some embodiments, a user provides inputs to the computing device <NUM> through one or more input devices <NUM>. Examples of input devices <NUM> include a keyboard <NUM>, mouse <NUM>, microphone <NUM> (e.g., for voice and/or other audio input), touch sensor <NUM> (such as a touchpad or touch sensitive display), and gesture sensor <NUM> (e.g., for gestural input). In some implementations, the input device(s) <NUM> provide detection based on presence, proximity, and/or motion. In some implementations, a user may walk into their home, and this may trigger an input into a processing device. For example, the input device(s) <NUM> may then facilitate an automated experience for the user. Other embodiments include other input devices <NUM>. The input devices can be connected to the processing device <NUM> through an input/output interface <NUM> that is coupled to the system bus <NUM>. These input devices <NUM> can be connected by any number of input/output interfaces, such as a parallel port, serial port, game port, or a universal serial bus. Wireless communication between input devices <NUM> and the input/output interface <NUM> is possible as well, and includes infrared, BLUETOOTH® wireless technology, <NUM>. 11a/b/g/n, cellular, ultra-wideband (UWB), ZigBee, or other radio frequency communication systems in some possible embodiments, to name just a few examples.

In this example embodiment, a display device <NUM>, such as a monitor, liquid crystal display device, light-emitting diode display device, projector, or touch sensitive display device, is also connected to the system bus <NUM> via an interface, such as a video adapter <NUM>. In addition to the display device <NUM>, the computing device <NUM> can include various other peripheral devices (not shown), such as speakers or a printer.

The computing device <NUM> can be connected to one or more networks through a network interface <NUM>. The network interface <NUM> can provide for wired and/or wireless communication. In some implementations, the network interface <NUM> can include one or more antennas for transmitting and/or receiving wireless signals. When used in a local area networking environment or a wide area networking environment (such as the Internet), the network interface <NUM> can include an Ethernet interface. Other possible embodiments use other communication devices. For example, some embodiments of the computing device <NUM> include a modem for communicating across the network.

The computing device <NUM> can include at least some form of computer readable media. Computer readable media includes any available media that can be accessed by the computing device <NUM>. By way of example, computer readable media include computer readable storage media and computer readable communication media.

Computer readable storage media includes volatile and nonvolatile, removable and non-removable media implemented in any device configured to store information such as computer readable instructions, data structures, program modules or other data. Computer readable storage media includes, but is not limited to, random access memory, read only memory, electrically erasable programmable read only memory, flash memory or other memory technology, compact disc read only memory, digital versatile disks or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the computing device <NUM>.

Computer readable communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, computer readable communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.

The computing device illustrated in <FIG> is also an example of programmable electronics, which may include one or more such computing devices, and when multiple computing devices are included, such computing devices can be coupled together with a suitable data communication network so as to collectively perform the various functions, methods, or operations disclosed herein.

The terms "substantially" and "about" used throughout this Specification are used to describe and account for small fluctuations, such as due to variations in processing. For example, they can refer to less than or equal to ±<NUM>%, such as less than or equal to ±<NUM>%, such as less than or equal to ±<NUM>%, such as less than or equal to ±<NUM>%, such as less than or equal to ±<NUM>%, such as less than or equal to ±<NUM>%, such as less than or equal to ±<NUM>%. Also, when used herein, an indefinite article such as "a" or "an" means "at least one.

In particular, all combinations of claimed subject matter appearing at the end of this invention are contemplated as being part of the inventive subject matter disclosed herein.

In addition, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other processes may be provided, or processes may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Accordingly, other implementations are within the scope of the following claims.

Claim 1:
A computer-implemented method comprising:
presenting a first drawer area (<NUM>) on a first display device (<NUM>) in an instrument panel (<NUM>) of a vehicle (<NUM>), the first drawer area (<NUM>) presented in an extended state where first content (<NUM>) of a first application is visible in the first drawer area (<NUM>),
the computer-implemented method being characterized by further comprising:
presenting a second drawer area (<NUM>) on a second display device (<NUM>) in the instrument panel (<NUM>) of the vehicle (<NUM>), the second drawer area (<NUM>) presented in a retracted state where the first content (<NUM>) of the first application is not visible in the second drawer area (<NUM>);
receiving a first transition command regarding the first and second drawer areas (<NUM>, <NUM>); and
in response to receiving the first transition command:
presenting the first drawer area (<NUM>) in the retracted state on the first display device (<NUM>) instead of in the extended state, wherein the first content (<NUM>) is not visible in the first drawer area (<NUM>) in the retracted state; and
presenting the second drawer area (<NUM>) in the extended state on the second display device (<NUM>), wherein the first content (<NUM>) of the first application is visible in the second drawer area (<NUM>), and wherein additional content (<NUM>) of the first application that was not visible in the first drawer area (<NUM>) is also visible in the second drawer area (<NUM>).