ADJUSTING AND/OR CUSTOMISING A USER INTERFACE OF A VEHICLE

20230350555 · 2023-11-02

    Inventors

    Cpc classification

    International classification

    Abstract

    A computer-implemented method for adjusting and/or customising a user interface of a vehicle including: providing, by the vehicle, user interface data of the vehicle to a separate computing unit, including at least information about the visualization parameters of at least one user interface; providing, by the computing unit, user interface control data for the at least one user interface based on the provided user interface data; transmitting the user interface control data to the vehicle; and adjusting and/or customising, by the vehicle, the at least one user interface based on the user interface control data in real time.

    Claims

    1. A computer-implemented method for adjusting and/or customizing a user interface of a vehicle, comprising: providing, by the vehicle, user interface data of the vehicle to a separate computing unit, comprising at least information about visualization parameters of at least one user interface; providing, by the computing unit, user interface control data for the at least one user interface responsive to the provided user interface data; transmitting the user interface control data to the vehicle; adjusting and/or customizing, by the vehicle, the at least one user interface based on the user interface control data in real time, wherein real time is defined as within a time frame having a predetermined lower limit and a predetermined upper limit, such that the at least one user interface is suitable for use in a prototyping platform; and using the at least one user interface in the prototyping platform.

    2. The method according to claim 1, further comprising: providing, by the vehicle, vehicle data comprising information about vehicle parameters and providing, by the computing unit, user interface control data for the at least one user interface further based on the provided vehicle data.

    3. The method according to claim 2, wherein the user interface control data comprises information about a selection of vehicle parameters for displaying by the at least one user interface.

    4. The method according to claim 2, wherein the vehicle data comprises a vehicle speed of the vehicle, a vehicle gear level of the vehicle, a vehicle fuel range of the vehicle and/or a GPS location of the vehicle.

    5. The method according to claim 2, wherein the vehicle data is provided by a vehicle bus system comprising a Flexray bus system, Controller Area Network bus system, CAN, Local Interconnect Network bus system, LIN, and/or automotive Ethernet bus system.

    6. The method according to claim 1, wherein the user interface is configured to process web technology comprising HTML data, CSS data and/or JavaScript data.

    7. The method according to claim 1, further comprising: providing request data and providing user interface control data further based on the request data.

    8. The method according to claim 1, wherein the user interface is an augmented reality user interface of the vehicle, a head-up display interface of the vehicle and/or a cockpit display interface of the vehicle.

    9. The method according to claim 1, wherein the vehicle is provided by means of a vehicle software model.

    10. The method according to claim 1, wherein the method is performed as virtual reality model based on simulated vehicle data.

    11. The method according to claim 1, wherein real time is defined in a timeframe of 10 milliseconds (ms) to 1000 ms.

    12. A system for adjusting and/or customizing a user interface of a vehicle, comprising: a first providing unit of the vehicle configured to provide user interface data of the vehicle to a separate computing unit, comprising at least information about visualization parameters of at least one user interface; a second providing unit of a computing unit configured to provide user interface control data for the at least one user interface responsive to the provided user interface data; a transmitting unit configured to transmit the user interface control data to the vehicle; and an adjusting and/or customizing unit of the vehicle configured to adjust and/or customize the at least one user interface based on the user interface control data in real time, wherein real time is defined as within a time frame having a predetermined lower limit and a predetermined upper limit, such that the at least one user interface is suitable for use in a prototyping platform.

    13. The system according to claim 12, further comprising: a gateway unit; a message broker unit; a custom logic unit; a remote control unit; and a HMI unit.

    14. The method according to claim 1, wherein the method is implemented in the vehicle and/or the computing unit.

    15. A non-transitory computer-readable medium stored in a memory and executed by a processor to carry out computer-implemented method steps for adjusting and/or customizing a user interface of a vehicle, comprising: providing, by the vehicle, user interface data of the vehicle to a separate computing unit, comprising at least information about visualization parameters of at least one user interface; providing, by the computing unit, user interface control data for the at least one user interface responsive to the provided user interface data; transmitting the user interface control data to the vehicle; and adjusting and/or customizing, by the vehicle, the at least one user interface based on the user interface control data in real time, wherein real time is defined as within a time frame having a predetermined lower limit and a predetermined upper limit, such that the at least one user interface is suitable for use in a prototyping platform; and using the at least one user interface in the prototyping platform.

    Description

    BRIEF DESCRIPTION OF THE DRAWINGS

    [0051] In the following, the disclosure is described exemplarily with reference to the enclosed figures, in which:

    [0052] FIG. 1 is a schematic diagram of an example of a process of the disclosed method;

    [0053] FIG. 2 is a schematic illustration of an example of a vehicle with the disclosed system;

    [0054] FIG. 3 is a schematic illustration of an example architecture of the disclosed method and system;

    [0055] FIG. 4 is a schematic illustration of a first example of a user interface of a vehicle with the disclosed system and disclosed method;

    [0056] FIG. 5 is a schematic illustration of a second example of a user interface of a vehicle with the disclosed system and disclosed method;

    [0057] FIG. 6 is a schematic illustration of a third example of a user interface of a vehicle with the disclosed system and disclosed method; and

    [0058] FIG. 7 is a schematic illustration of a fourth example of a user interface of a vehicle with the disclosed system and disclosed method.

    [0059] Notably, the figures are merely schematic representations and serve only to illustrate examples of the present disclosure. Identical or equivalent elements are in principle provided with the same reference signs.

    DETAILED DESCRIPTION

    [0060] FIG. 1 shows a schematic diagram of a process of the disclosed method, whereby the method includes the steps of providing, by the vehicle, user interface data 10 of the vehicle to a separate computing unit, including at least information about the visualization parameters of at least one user interface. Further, a providing, by the computing unit, user interface control data 20 for the at least one user interface based on the provided user interface data. Further, a transmitting the user interface control data 30 to the vehicle. Further, an adjusting and/or a customising, by the vehicle, the at least one user interface 40 based on the user interface control data in real time.

    [0061] FIG. 2 shows a schematic illustration of an example of a system for adjusting and/or customising a user interface of a vehicle 100 including different units.

    [0062] A first providing unit 101 of the vehicle configured to provide user interface data of the vehicle to a separate computing unit 120, including at least information about the visualization parameters of at least one user interface, e.g., a cockpit user interface of the vehicle 100. The user interface data of the vehicle may be provided to the computing unit 120 by any wireless communication method, e.g. any wireless communication technology, like a mobile communication, a Bluetooth communication, etc. In a further use case, the user interface data of the vehicle 100 may be provided to the computing unit 120 by any wire based communication standard, for example, a smart grid communication for electric vehicles during charging the electric vehicle or by means of a wired control device.

    [0063] A second providing unit 121 of the computing unit 120 configured to provide user interface control data for the at least one user interface based on the provided user interface data.

    [0064] A transmitting unit 122 configured to transmit the user interface control data to the vehicle 100. In addition, here, the above-mentioned communication methods may be applied/used.

    [0065] An adjusting and/or customising unit 102 of the vehicle 100 configured to adjust and/or customise the at least one user interface based on the user interface control data in real time.

    [0066] Further, a gateway unit 103, a message broker unit 104, a custom logic unit 105, a remote control unit 106 and a HMI unit 107 are provided in the shown example. Whereby, the HMI unit 107 is configured to display the user interface.

    [0067] FIG. 3 shows a schematic illustration of an example architecture of a method and a system 110, including a vehicle 100, a (prototype) database and/or a software (prototype) tool 110.1 of the system 110, a gateway unit 103, a message broker unit 104, a custom logic unit 105, a remote control unit 106 and a HMI unit 107. Whereby the (prototype) database and/or software (prototype) tool 110.1 may include additional devices that may be included in the user interface setup and provide, for example, a configuration of buttons and/or new buttons for a steering wheel of a vehicle. Furthermore, the (prototype) database and/or software (prototype) tool 110.1 may simulate an environment for augmented reality and/or virtual reality.

    [0068] The vehicle 100 and the database 110.1 aggregated as a first stage 111 and the gateway unit 103, the message broker unit 104, the custom logic unit 105, the remote control unit 106 and the HMI unit 107 aggregated as a second stage 112. Whereby the first stage 111 and the second stage 112 are configured to communicate in a bidirectional way with each other. Moreover, the first stage 111 and/or the second stage 112 may be further configured to communication with further units/entities, e.g. server systems. Further, the first stage 111 provides data to the second stage 112 and the second stage 112 process the provided data.

    [0069] In other words, data is received by the vehicle 100, whereby, the custom logic unit 105 receives a list of signals of the vehicle 100 requested by the remote control unit 106 and the HMI unit 107. The gateway unit 103 reads the signals from the vehicle busses, e.g. Flexray, CAN, LIN and/or automotive Ethernet, in real time. Whereby, the gateway unit 103 decodes the requested signals of the vehicle to human readable values and passes them to the custom logic unit 105. The custom logic unit 105 allows combining, process or simply passing through the incoming data, as needed. Further, the custom logic unit 105 publishes the data to the message broker unit 104 as requested. The HMI unit 107 displays the received data, for example, vehicle speed, gear, fuel range and/or GPS of the vehicle 100.

    [0070] Further, data is received by the database 110.1, whereby the database 110.1 publish the data to the message broker unit 104. The custom logic unit 105 combines and/or process the data of the database 110.1, as needed. Further, the custom logic unit 105 publishes the data to the message broker unit 104. The HMI unit 107 displays the received data for example turn-by-turn indications and/or steering wheel button inputs.

    [0071] Further, data is received by the remote control unit 106, whereby the remote control unit 106 publishes the data to the message broker unit 104. The custom logic unit 105 combines and/or processes the data of the remote control unit 106, as needed. Further, the custom logic unit 105 publishes the data to the message broker unit 104. The HMI unit 107 displays the received data, for example, notifications and/or user interface context changes.

    [0072] Further, data is send to the vehicle 100, whereby received data being sent via the remote control unit 106 and/or database 110.1 from the custom logic unit 105 via the message broker unit 104 to the vehicle 100.

    [0073] For example, a set of steering wheel buttons may be send to the vehicle, which should be pressed to activate a vehicle function. The request is received by the custom logic unit 105. The custom logic unit 105 translates the request to a vehicle readable format: a set of vehicle signals that will activate the vehicle function. This set of signals are injected into the vehicle's busses by the gateway unit 103.

    [0074] FIG. 4 shows a schematic illustration of a first example of a user interface on a HMI unit 107 of a vehicle. The user interface include at least a first field 201, a second field 202, third field 203, fourth field 204 and a fifth field 205.

    [0075] Further, in the first field 201, the user interface shows a first field view of a speed of the vehicle including the actual speed and the unit of the speed.

    [0076] Further, in the second field 202, the user interface shows a first field view of a used gear of a transmission of the vehicle, including the possible gears of the transmission and a highlighting of the used gear.

    [0077] Further, in the third field 203, the user interface shows a first field view of navigation instructions for reaching a desired destination that includes a distance for the next change of direction, a direction for the change of direction, and a location that will be reached next.

    [0078] Further, in the fourth field 204, the user interface shows a remaining range of the vehicle, for example, based on the remaining fuel and/or charge of a battery of the vehicle.

    [0079] Further, in the fifth field 205, the user interface shows a map of the location of the vehicle with an indication of a driving direction of the vehicle.

    [0080] FIG. 5 shows a schematic illustration of a second example of a user interface on a HMI unit 107 similar to FIG. 4. Whereby, here, in the third field 203, the user interface shows a second field view of autopilot information for the usage of the vehicle. Moreover, the steering wheel buttons are configured or reconfigured to activate an autopilot mode of the vehicle. It is further displayed in the third field 203 that a driver may activate the autopilot by holding the steering wheel buttons, i.e. the HMI unit 107 displays a notification on the availability of a specific vehicle function, here an autopilot function of the vehicle.

    [0081] FIG. 6 shows a schematic illustration of a third example of a user interface on a HMI unit 107 similar to FIG. 4. Whereby, here, the in the third field 203, the user interface shows an autopilot information, here that the autopilot mode of the vehicle is actually used.

    [0082] FIG. 7 shows a schematic illustration of a fourth example of a user interface on a HMI unit 107 similar to FIG. 4. Whereby, in the first field 201, the user interface shows a second field view of a speed of the vehicle including the speed. As well as, in the second field 202 that the autopilot mode is activated.

    [0083] In contrast to FIG. 4, the user interface in FIG. 7 does not include a fourth field 204.

    [0084] Other variations to the disclosed examples can be understood and effected by those skilled in the art in practicing the claimed subject matter, from the study of the figures, the disclosure, and the appended claims. In particular, respective parts/functions of the respective example described above may also be combined with each other. In particular, the present disclosure is not limited to specific modules, vehicle functions, user interfaces, user interface areas/fields and/or communication methods. In the claims, the word “comprising” does not exclude other elements or steps and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. Any reference signs in the claims should not be construed as limiting the scope of the claims.