VEHICLE STATE BASED GRAPHICAL USER INTERFACE

Abstract

An intelligent system, and its corresponding method, is disclosed that is capable of rendering a user interface operation version that is most appropriate given a certain state of the vehicle ensuring the driver of the vehicle continues to drive safely without distractions. The method disclosed herein provides for operating a user interface of a vehicle infotainment device or an in-car entertainment device, the user interface being operable to present one or more applications. The method comprises retrieving vehicle state input data, processing the vehicle state input data at the processing module to select one of a plurality of different user interface operation versions based on the vehicle state input data, and operating the user interface according to the selected user interface operation version by the user interface operation module.

Claims

1. A method for operating a user interface of a vehicle infotainment device, the user interface operable to present one or more applications, the method comprising: retrieving vehicle state input data; processing the vehicle state input data to select one of a plurality of different user interface operation versions based on the vehicle state input data; and operating the user interface according to the selected user interface operation version.

2. The method according to claim 1, wherein each of the plurality of different user interface operation version comprises: a respective set of operations based on a past event training log; and/or a respective set of different applications.

3. The method according to claim 1 further comprising at least one application for operation in each of the different user interface versions, wherein the application is operable in different application versions, wherein each of the application versions is associated with a respective one of the different user interface operation versions.

4. The method according to claim 3, wherein the application comprises a plurality of functions, wherein a reduced set of the plurality of functions is available for operation in at least one the application versions.

5. The method according to claim 4, wherein each version of the application is associated with a respective version of representation of the application and/or functions thereof to a user via the user interface.

6. The method according to claim 3, wherein the applications comprise one or more of network and connectivity application, communication application, navigation application, video player application, messaging application, multimedia application, social media application or news and information application.

7. The method according to claim 1 further comprising: operating different versions of the user interface associated with different applications; and rendering all or a subset of applications to the user interface based on the vehicle state input data.

8. The method according to claim 1 further comprising: monitoring the vehicle state input data for a change; processing the changed vehicle state input data to select a user interface operation version based on the changed vehicle state input data; and operating the user interface by transitioning to the selected user interface operation version.

9. The method according to claim 1, wherein the vehicle state input data comprises at least one of speed of vehicle, acceleration of vehicle, deceleration of vehicle, inside temperature of vehicle, engine temperature, GPS location of the vehicle, fuel level information, terrain traversed by the vehicle, driving condition, road condition, vehicle occupant and/or driver information, engine control unit-ECU output or sensor information.

10. The method according to claim 1, wherein a past event training log comprises a log of a user's interaction with the user interface of the vehicle infotainment device corresponding to one or more events.

11. A system for operating a user interface of a vehicle infotainment device, the user interface operable to present one or more applications, the system comprising: a processing module to receive vehicle state input data and process the vehicle state input data to select a user interface operation version based on the vehicle state input data; a user interface operation module to operate the user interface according to the selected user interface operation version.

12. The system according to claim 11, wherein the user interface comprises a display for displaying one or more applications and/or different application versions corresponding to the user interface operation version.

13. The system according to claim 11, wherein the processing module is operable to receive the vehicle state input data from one or more sensors, wherein the one or more sensors are integrated in the vehicle and/or the one or more sensors are external to the vehicle.

14. The system according to claim 11, wherein the processing module is operable to access a database comprising rules to select a user interface operation version corresponding to a vehicle state input data value.

15. A computer-program product having a non-transitory computer readable medium storing computer executable code which, when executed by computer, performs the following operations: retrieves vehicle state input data; processes the vehicle state input data to select one of a plurality of different user interface operation versions based on the vehicle state input data; and operates a user interface according to the selected user interface operation version.

16. The computer-program product of claim 15, wherein each of the plurality of different user interface operation version comprises: a respective set of operations based on a past event training log; and/or a respective set of different applications.

17. The computer-program product according to claim 15 further performing providing at least one application for operation in each of the different user interface versions, wherein the at least one application is operable in different application versions, wherein each of the application versions is associated with a respective one of the different user interface operation versions.

18. The computer-program product according to claim 17, wherein the application comprises a plurality of functions, wherein a reduced set of the plurality of functions is available for operation in at least one the application versions.

19. The computer-program product according to claim 18, wherein each version of the application is associated with a respective version of representation of the application and/or functions thereof to a user via the user interface.

20. The computer-program product according to claim 17, wherein the at least one application comprises one or more of network and connectivity application, communication application, navigation application, video player application, messaging application, multimedia application, social media application or news and information application.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The present invention may be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein:

[0026] FIG. 1 schematically shows an example system in accordance with one of a number of embodiments;

[0027] FIG. 2 schematically shows yet another example system in accordance with one of a number of embodiments;

[0028] FIG. 3 schematically shows an exemplary infotainment device of a car in accordance with one of a number of embodiments;

[0029] FIG. 4A-4C schematically show different versions of the use interface in accordance with one of a number of embodiments;

[0030] FIG. 5A-5C schematically show different versions of an application available to the user interface in accordance with one of a number of embodiments; and

[0031] FIG. 6 is a flow chart for an example method in accordance with one of a number of embodiments.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] In modern day cars, when a user launches an application on an in-car-entertainment (ICE) system or a vehicle infotainment device of the car, from HMI (Human Machine Interface) or display, the system launches that application and the application gets displayed on display screen or HMI. The rendered application is in its original format and its corresponding user interface is not affected by the driving circumstances.

[0033] This disclosure presents a system, which takes decision based on factors, external or internal which are relevant to the driving situation, before launching any application or displaying anything on screen. This offers a safety measure in a vehicle environment when it is in motion.

[0034] FIG. 1 discloses a system 100 according to one of many embodiments of the present invention. According to FIG. 1, the system 100 comprises a processing module 104 and a user interface operation module 106. The processing module 104 receives the vehicle state input data and processes the vehicle state input data to select a user interface operation version from a plurality of different interface operation versions based on the vehicle state input data. The user interface operation module 106 operates the user interface according to the selected user interface operation version.

[0035] FIG. 2 shows yet another example system 200 in accordance with one of a number of embodiments. According to FIG. 2, the system 200 comprises a vehicle state observer module 202. This module 202 is connected to a sensor 210. The sensor 210 retrieves information related to vehicle state in the form of vehicle state input data 212, for example, the speed of the vehicle. The sensor then transmits this vehicle state input data 212 to the vehicle state observer module 202. The system 200 may comprise one or more such sensors 210 which may be internal or external to the vehicle. According to an embodiment the sensor may even retrieve information from sources not connected with the vehicle, for example, information about the traffic condition in the approaching city. Next the vehicle state observer module 202 receives the vehicle state input data 212 from the sensor 210.

[0036] The system 200 as shown in FIG. 2 further comprises a processing module 204 which is connected to the vehicle state observer module 202. Through this connection the application decision module 204 receives the vehicle state input data 212. The processing module 204 is connected to a database 214. This database 214 contains a list of rules wherein each vehicle state input data has a corresponding rule associated with it. According to another embodiment a combination of one or more vehicle state input data 212 has a corresponding combination of one or more rules associated to it. The rule identifies which user interface operation version is appropriate for the given vehicle state input data.

[0037] On receiving the vehicle state input data 212 from the vehicle state observer module 202, the processing module 204 refers to the database 214 to check which rule corresponds to the received vehicle state input data 212. On determining the correct rule the processing module 204 selects the corresponding appropriate user interface operation version 216 to be rendered to the user. Therefore, the decision as to which user interface application version 216 is to be rendered to the user is processed and made by the processing module 204.

[0038] The system 200 further constitutes a user interface operation module 206. This module 206 is connected to the processing module 204. Once the decision about which user interface operation version 216 is to be rendered has been made, the processing module 204 passes over the information of the selected user interface operation version 216 to the user interface operation module 206. The user interface operation module 206 is connected to a display 208 for displaying one or more applications and/or different application versions, corresponding to the user interface operation version 216, for use by the user/driver of the car.

[0039] Now referring to FIG. 3, it depicts an example of an infotainment device 300 of a vehicle in accordance with one of a number of embodiments. The infotainment device 300 or the in-car-entertainment device comprises a display 302. It further constitutes a memory unit 304. The infotainment device 300 may comprise of several other devices or units as are well known in the art and is not limited to the device 300 as shown in FIG. 3. For example, the infotainment device 300 may further comprise of speakers, keypad, other input-output devices, jacks, a further display screen, controller or logic unit etc.

[0040] Referring now to FIG. 4A-C, they schematically show different example versions of the user interface in accordance with one of a number of embodiments. Only three examples are shown for illustrative purposes, it is understood that many more similar versions of the user interface may be possible. Depending on the user interface operation version selected by the application decision module based on the retrieved vehicle state input data, the application framework renders the selected user interface operation version for display. According to FIG. 4A, when the vehicle state input data reflects a value, for example, speed of the vehicle, above a certain threshold value/speed, the application decision module selects a user interface operation version 416a which comprises a user interface containing only those bare minimum applications that are most urgent and need to be available to the user while driving the vehicle, such as a navigation application. The other, less urgent applications, for example, applications related to social networking sites, may be hidden from the user interface. Therefore, only those applications will be displayed on the home screen of the infotainment device that are deemed safe by the system under the current vehicle state input data.

[0041] According to FIG. 4B, when the vehicle state input data reflects a value, for example, speed of the vehicle, as below or equal to a certain threshold value/speed, the application decision module selects a user interface operation version 416b which comprises a user interface containing not only those applications that are needed urgently by the driver, but also certain other additional applications which do not distract the driver from his driving. For example, music applications offering a choice of music to play, call receive/calling function related applications etc.

[0042] In a third example, as shown in FIG. 4C, when the vehicle state input data reflects a value, for example, speed of the vehicle, as zero or the vehicle is stationary, the application decision module selects a user interface operation version 416c which comprises a user interface containing all the applications that are supported by the infotainment device.

[0043] FIG. 5A-5C schematically show different exemplary versions of an application available to the user interface in accordance with one of a number of embodiments. Only three examples are shown for illustrative purposes, it is understood that many more similar application versions may be possible. Depending on the user interface operation version selected by the application decision module based on the retrieved vehicle state input data, the application framework renders the selected user interface operation version for display.

[0044] According to FIG. 5A, as an example, when the vehicle state input data reflects a value, for example, speed of the vehicle, above a certain threshold value/speed, the application decision module selects a user interface operation version 516a which comprises a light version of the user application that the user wishes to use. As seen in FIG. 5A the light version of the application version displays very minimal features in the form of a basic version of the application with lowest level of UI complexity. This means that the driver does not have to distract himself from the main task of driving the car and with minimalistic driver involvement the application can run smoothly. In other words, the user interface corresponding to the application is simplified in this light version.

[0045] According to FIG. 5B, as a second example, when the vehicle state input data reflects a value, for example, speed of the vehicle, below or equal to a certain threshold value/speed, the application decision module selects a user interface operation version 516b which comprises a medium version of the user application that the user wishes to use. As seen in FIG. 5B the medium version of the application version displays very still reduced user interface complexity with less features as compared to the usual application complexity. This means that the driver does not have to distract himself from the main task of driving the car but can also run the application with some features that were not available during the light version of the application.

[0046] According to FIG. 5C, as yet another example, when the vehicle state input data reflects a value, for example, speed of the vehicle, as zero or the vehicle being stationary, the application decision module selects a user interface operation version 516c which comprises a high version of the user application that the user wishes to use. As seen in FIG. 5C the high version of the application version displays all the features in the form of full version of the application with full-fledged or highest level of UI complexity. No features of the application are simplified, compressed or minimized for display.

[0047] FIG. 6 is a flow chart for an example method 600 in accordance with one of a number of embodiments. The method 600 comprises a first step 602 of request for launching of an application by a user who is the driver of the vehicle. On receiving the launch request, the method 600 follows a step 604 of fetching or retrieving vehicle state input data which relates to the current state of the vehicle. In the next step 606, the method 600 comprises processing of the fetched vehicle input data. Now this step of processing 606 involves selecting a user interface operation version based on the vehicle state input data fetched.

[0048] The processing step 606 may involve comparing the vehicle state input data to a threshold value, finding a rule for selecting a user interface operation version given the vehicle state input data or identifying a user interface operation version based on a past event training log. The disclosed system may store user inputs, which he/she takes frequently while driving, and use such inputs under the similar conditions instead of asking user or seeking user intervention. Such a user input corresponding to an event is stored for later retrieval in the past event training log. For example, an event of incoming call can have a corresponding operation of cancelling of the incoming phone call while driving, or an event of a pop up coming up on the display screen can have a corresponding operation of dismissing of such pop-ups etc. This will allow the user to have lesser distractions while driving.

[0049] The next step 610 of the method 600 involves displaying the selected user interface operation version on a display screen of the vehicle infotainment device. This user interface operation version can be one or a combination of different operations based on a past event training log, different versions of the user interface associated with different applications and/or different versions of the application comprising one of a light version, a medium version or a high version.

[0050] The method 600 further comprises a step 612 of tracking a change in the vehicle state input data. As long as there is no change in the vehicle state input data, the same selected user interface operation version can be available to the user for use on the display unit of the infotainment device. However, when there is a change detected to vehicle state input data, for example, the vehicle has come to a stop from a speed of 60 km/h, the step 606 of processing of the vehicle state input data is repeated to select a new user interface operation version based on the changed vehicle state input data.

[0051] The description of embodiments has been presented for purposes of illustration and description. Suitable modifications and variations to the embodiments may be performed in light of the above without departing from the scope of protection as determined by the claims.

[0052] In particular, whilst some of the above examples are described in connection with speed of the vehicle, the embodiments disclosed herein may also be implemented with other vehicle state input data as disclosed in the claims.