Computer-implemented method for configuring a vehicle's user interface based on function usage data, computer-readable storage medium, function usage suggestion module and system

Abstract

The present invention relates to a computer-implemented method for configuring a user interface of a vehicle (200) based on function usage data. The method comprises the following steps: - Receiving, from a backend server (110), function usage data of a user of the vehicle (200); - Determining a driving situation; - Generating a function usage profile for the driving situation based on the function usage data; and - Configuring a user interface of the vehicle (200) based on the function usage profile, such that at least one function usage suggestion for a vehicle function is output via the user interface of the vehicle (200).

Description

The present invention relates to a computer-implemented method for configuring a user interface of a vehicle, as well as a corresponding computer-readable storage medium, a function usage suggestion module and system. Modern vehicles offer a wide range of functions that can be activated by the driver depending on the driving situation and individual preferences. These functions include driver assistance systems (e.g., cruise control, lane keeping assist, parking assist, etc.) as well as comfort features (e.g., playing media content, adjusting the interior lighting, activating massage actuators in the seat, etc.). These functions can involve complex routines that control multiple vehicle components simultaneously. For example, activating a relaxation function might include controlling the infotainment system to play relaxing graphics and music, adjusting the interior lighting, and activating massage actuators in the driver's seat. Traditionally, such functions are developed by the vehicle manufacturer specifically for a given vehicle. However, by using appropriate software platforms within the vehicle, it is also possible for third-party providers (e.g., streaming providers or navigation app providers) to offer functions for using their services, which can be integrated into the vehicle in the form of apps. From a safety perspective, it is particularly important that drivers can activate desired vehicle functions quickly and easily. Conventional operating concepts, where the driver has to find and select a corresponding button on the dashboard or steering wheel, or navigate through a menu with potentially multiple sub-levels, are of very limited practical use, as they distract the driver's attention and concentration from the road for extended periods. Quick and easy activation of vehicle functions is also desirable with regard to driving comfort. To simplify the activation of vehicle functions, approaches exist in which the vehicle proactively alerts the driver to a function relevant to the current driving situation and provides the driver with a way to activate it. For example, after detecting that the vehicle is traveling on a section of highway with a speed limit, it can display a notification ("pop-up") in the vehicle's display, indicating the availability of the adaptive cruise control. The driver can accept this function usage suggestion by pressing a button on the steering wheel, the function of which has been programmed by the vehicle according to the suggested function usage. In general, however, more than one vehicle function may be relevant at any given time or in a specific driving situation. The problem here is that a vehicle's user interface offers very limited possibilities for interaction with the driver. For example, information can only be transmitted to a very limited extent via the vehicle's graphical user interface, as the display elements must be relatively large in relation to the screen size in order to be safely readable by the user while driving. For reasons of road safety, the graphical user interface can only be used to a limited extent anyway. Even when using speech output, not an unlimited amount of information can be transmitted to the user, as the user's capacity to absorb information is limited, especially while driving. Finally, situation-specific function usage suggestions must be provided to the driver promptly, as early activation of the function is desirable, particularly from a safety perspective. Furthermore, a function usage suggestion can become irrelevant after a short time due to a change in the driving situation (e.g., when leaving the motorway or a section of road with lane markings). DE 10 2023 100 086 A1 discloses a method for providing information about a vehicle's functional unit and / or vehicle function to a vehicle user, comprising the following steps: - Providing usage information, which characterizes the user's use of the functional unit and / or vehicle function, to an evaluation unit; - Determining functional information based on the usage information, providing user-specific information; - Automatically outputting the functional information with an output unit depending on a traffic situation and / or a vehicle state. DE 10 2018 211 973 A1 concerns a method for providing a service recommendation in a vehicle to a user of the vehicle, comprising: collecting data specific to the user's use of the vehicle; determining one or more suggestions for recommended services based on a predictive model, the predictive model comprising machine learning of patterns to map the data to suggestions for recommended services; providing the one or more suggestions to the user; collecting user feedback; and updating the predictive model based on the user feedback. Against this background, the object of the invention is to improve the human-machine interaction between driver and vehicle, in particular to increase the vehicle's safety and ease of use. Specifically, the object of the invention is to simplify the selection and activation of vehicle functions, with a particular aim of making more efficient use of the user interface resources. This problem is solved by a method according to claim 1, a computer-readable storage medium according to claim 9, a function usage suggestion module according to claim 10, and a system according to claim 11. Advantageous embodiments are set forth in the dependent claims. In particular, the task is solved by a computer-implemented method for configuring a vehicle's user interface based on function usage data.The procedure, which can be executed in particular by a function usage suggestion module of the vehicle, comprises the following steps: - Receiving, from a backend server, function usage data of a vehicle user, indicating previous function usage operations of the user; - Determining a driving situation, in particular based on sensor data and / or control signals of the vehicle; - Generating a function usage profile for the driving situation, based on the function usage data; and - Configuring a user interface of the vehicle based on the function usage profile, such that at least one function usage suggestion for a vehicle function is output via the user interface of the vehicle, in particular as a voice message and / or graphical indicator. One aspect of the present invention is to configure a vehicle's user interface based on function usage data. This function usage data indicates how the user has interacted with the vehicle in the past under specific driving conditions, particularly with regard to the use of vehicle functions. In this way, the user can be provided with information via the user interface that is relevant to the current driving situation and the driver's individual usage behavior. In particular, informational elements that provide (proactive) function usage suggestions graphically and / or audibly can be generated in terms of type and content depending on whether the user has used the corresponding vehicle function in the past. For example, the informational element can contain an explanation of the function the first time it is used, while subsequent uses will simply display a notification about the function. Centralized management of function usage data on a backend server allows for the tracking of a user's function usage behavior across multiple vehicles. This means that function usage data collected in one of the user's vehicles can be used to configure the user interface of a second vehicle. This simplifies the customization and configuration of the second vehicle. The vehicle's user interface can be understood as a software component running within the vehicle that controls the vehicle's various output and input devices to enable interaction with the driver or vehicle user. In particular, the user interface can be designed to control the graphical content displayed on screens (e.g., cockpit display, head-up display, instrument cluster display) and / or control the playback of voice messages or sounds via the vehicle's speakers. Likewise, the user interface can be designed to capture user input via corresponding input devices, such as voice command recognition, input from a touchscreen, and / or other controls. Function usage data can be understood as one or more data records that describe the activation or deactivation of a vehicle function, as well as contextual information at the time of activation or deactivation. For example, function usage data can specify one or more of the following attributes relating to a given vehicle function: duration of function use, time of activation and / or deactivation, and driving situation at the time of activation and / or deactivation. Additionally, the function usage data can indicate whether and how the user reacted to a function usage suggestion for a vehicle function (for example, by accepting, ignoring, or rejecting). The user's function usage data can be provided by the backend server, in particular as one or more lists, each containing function usage data relating to a specific driving situation. The lists thus indicate, in particular, which functions a user has used in a given driving situation. In the context of the present invention, a driving situation can be understood as one of several predefined driving situations, which is an abstract description of the current state of the vehicle, the environment of the vehicle, the destination and / or similar information. Predefined driving situations can be, for example, the following: START_LONG_TRIP, CHARGING_ACTIVE_PERSON_IN_CAR, CHARGING_CABLE_PLUGGED_IN, CAUGHT_IN_TRAFFIC_JAM, LEISURE_WITH_FAMILY, VACATION_TRIP, ON_WAY_TO_CHARGING_STATION, DRIVING_AUTONOMOUSLY, WAITING_IN_VEHICLE, RESTING_PAUSE_DURING_LONG_DISTANCE_TRIP, FROSTY_DAY, MORNING_DRIVE, EVENING_DRIVE, CRUISING_ON_HIGHWAY, LISTENING_TO_MUSIC_IN_CAR, FAMILY_TRIP, TRIP_WITH_FRIENDS, LOW_REMAINING_RANGE, ON_WAY_TO_CITY,ON_THE_WAY_TO_SERVICE, LOAD_UNLOAD_TRUNK, ENTER_SETUP_BEFORE_START, MANOEUVRING, DRIVE_END_UNTIL_EXIT, REFRESH_DURING_LONG_TRIP, LEAVING_THE_VEHICLE, ARRIVING_AT_DESTINATION. Some driving situations occur while the vehicle is in motion (e.g. autonomous driving, “DRIVING_AUTONOMOUSLY”), other driving situations occur while the vehicle is stationary (e.g. with a charging cable connected, “CHARGING_CABLE_PLUGGED_IN”). Determining the driving situation can be done by a lookup operation in a data structure which assigns sensor signals and / or control signals or respective intervals, or similar, to a fixed set of driving situations. These signals must be detected to determine the corresponding driving situation as such. The determination of the driving situation can be carried out additionally or alternatively to sensor signals using other information available in the vehicle, such as time, status and / or parameters of a control unit in the vehicle, navigation destination, traffic situation along a pre-programmed route, etc. The following table shows, as examples for some of the aforementioned driving situations, which sensor signals / information are used and under which conditions the corresponding driving situation is determined: START_LONG_TRIP Navigation destination; GPS sensor signal; Distance to navigation destination >200km CHARGING_ACTIVE_PERSON_IN_CARSeat sensor signal; Battery Management System (BMS) status: Charging active; Driver's seat occupied CHARGING_CABLE_PLUGGED_IN Charging port sensor signal Charging cable connected CAUGHT_IN_TRAFFIC_JAM Speed ​​sensor signal; GPS sensor signal Vehicle speed is less than threshold WAITING_IN_VEHICLE Seat sensor signal; Speed ​​sensor signal Driver's seat occupied; Vehicle stationary FROSTY_DAY Signal from the outdoor temperature sensor: Outdoor temperature < 0°C MORNING_DRIVE Time of day Time of day between 4am and 10am EVENING_DRIVE Time of day Time between 6 pm and 10 pm FAMILY_TRIPS Rear seat sensor signal At least one of the rear seats occupied LOW_REMAINING_RANGER range prediction value Remaining range < 30km REFRESH_DURING_LONG_TRIP Previous travel time Time since last break > 180 min ARRIVING_AT_DESTINATION time; Planned arrival time at destination; Remaining travel time < 10 minutes The function usage profile generated according to the invention based on the function usage data can be a data structure that indicates, for the determined driving situation and for each of a multitude of vehicle functions, whether (and if so, how) the user has used the respective vehicle function. In particular, the function usage profile indicates which vehicle functions the user has already used in the determined driving situation and which they have not. As already described above, this information can be used, in particular, to adapt the type and content of a function usage suggestion that is provided to the user via the user interface. A functional usage suggestion (or an indication thereof) can in particular be understood as a graphic element that is displayed on a screen in the vehicle, and / or a voice message, a warning tone or similar that is output via a loudspeaker of the vehicle. In one embodiment, generating the function usage profile includes filtering the function usage data based on one or more of the following criteria: - a vehicle configuration, in particular the vehicle's functional scope, and / or a vehicle condition; - respective expertise levels of vehicle functions; and - a blocking list determined from the function usage data. This embodiment takes into account that not all vehicle functions specified in the function usage data are relevant to the user in the vehicle. Filtering therefore has the advantage that the resources for outputting function usage suggestions in the vehicle can be used more efficiently, namely for function usage suggestions for relevant vehicle functions. Filtering function usage data based on a vehicle configuration, in particular a vehicle's functional scope, is related to the inventive idea of ​​capturing and using function usage data across vehicles. Filtering function usage data based on a vehicle's functional scope prevents a function usage suggestion from being issued for a vehicle function (e.g., a driver assistance system) that the user frequently uses in one vehicle but that is not available in a second vehicle. Accordingly, a (current) condition of the vehicle (e.g. the presence of errors in the fault memory, which temporarily renders a vehicle function unavailable) can also be such a filter criterion. Additionally or alternatively, filtering can be based on the respective expertise level of vehicle functions. A low expertise level can indicate that the corresponding vehicle function is particularly easy to use (e.g., media playback), while a higher expertise level indicates that a vehicle function requires greater complexity to operate (e.g., parking assistant). By using appropriate filtering, vehicle functions with a low level of expertise can be prioritized, thereby increasing the vehicle's operational safety. Additionally or alternatively, filtering can be based on a blocking list (a blacklist) derived from function usage data. A blocking list can specify vehicle functions related to function usage suggestions to which the user has reacted negatively in the past, particularly by rejecting the suggestion. In another embodiment, the output of the function usage suggestion includes at least one of the following actions: - Outputting a voice message via a loudspeaker of the vehicle; - Outputting a graphical information element via a screen of the vehicle. The voice message or graphical indicator can, for example, prompt the user to activate the vehicle function, e.g. by displaying the text "Activate active cruise control?" or by emitting a corresponding voice message. The use of voice is preferred because the user can hear and react to the message without taking their eyes off the road. The voice message can be pre-recorded or generated using speech synthesis, for example, by a deep neural network. In a further embodiment, the method also includes determining a usage value based on the usage data. The usage value indicates how often the user has used a particular vehicle function to date. In one variant of this embodiment, the value in use can specify not only the number of previous uses, but also, if applicable, qualitative characteristics such as the duration of use. In another embodiment, the voice message and / or the graphical information element is generated with regard to type and / or content depending on the utility value. For example, if the usage value is zero (i.e., the user has not used the vehicle function in the past), the function usage message can be issued as a voice message explaining the vehicle function, e.g., "Activate active cruise control? Your vehicle will then automatically regulate the speed and distance to the vehicle in front." If, on the other hand, the utility value is greater than zero, the function usage notification can be a shorter voice message that only indicates the availability of the vehicle function, e.g. "Activate active cruise control?". The type of voice message and / or graphical indicator can also be determined based on the usage value. For example, a usage value of zero might generate a graphical element of the type "unused function," which appears prominently on the screen. Conversely, a usage value greater than zero might generate a graphical element of the type "link," which provides the user with an easy way to activate the function while requiring less of the user's attention. The above-described adjustment of type and / or content depending on the function usage data, in particular the function usage value obtained from it, improves the human-machine interaction between the vehicle and its user. Configuring the user interface also results in at least one of the following actions: - Controlling a haptic actuator of the vehicle; - Controlling and / or programming a control element of the vehicle. By activating a haptic actuator, so that, for example, a vibration is caused in the steering wheel when the function usage suggestion is issued, the driver can also be made aware of the function usage suggestion. By controlling and / or programming a vehicle control element, the user can easily activate the corresponding vehicle function. For example, a universally programmable button on the steering wheel can be programmed so that pressing the button activates the vehicle function. Alternatively or additionally, activation can be achieved via a voice command. In another embodiment, the previous function usage processes were recorded in a second vehicle of the user, which is different from the vehicle (whose user interface is configured). This allows functional usage data to be collected in a user's first vehicle and used to configure the user interface of a second vehicle. This simplifies the configuration of the second vehicle, for example, during the initial setup. In a further embodiment, the method also includes the following steps: - Capturing a user's response to the output of the function usage suggestion; - Transmitting second function usage data, which includes the response, to the backend server. The response can be, in particular, acceptance, ignoring (i.e., no response to the output of the function usage suggestion for a specified period of time, for example, 30 seconds after playback), or rejection of the function usage suggestion. According to this embodiment, the method according to the invention can form an iterative process in which: 1. The user interface of the vehicle is configured based on function usage data received from a backend server; 2. A user response to a function usage suggestion is recorded, which is output via the configured user interface; 3. Further (second) function usage data, which includes the user's response, is transmitted to the backend server. In this way, it is possible to continuously improve human-machine interaction. Retrieving and transmitting the function usage data to and from the backend server has the advantage that the method according to the invention can be applied across vehicles. The problem is further solved by a computer-readable storage medium containing instructions that cause at least one processor to implement one or more steps of a procedure described above when the instructions are executed by the at least one processor. The task is further solved by a function usage proposal module for a vehicle. The function usage proposal module is designed to execute one or more steps of a procedure described above. In conjunction with the function utilization proposal module, similar technical advantages and effects result as those described in connection with the method according to the invention. The task is further solved by a system comprising: - at least one vehicle with a function usage suggestion module as described above; and - a backend with a backend server and a function usage database. The backend server is designed to transfer data records from the function usage database to at least one vehicle. The system offers similar technical advantages and effects as described in connection with the method according to the invention. In particular, the backend server can implement a REST API so that the data records can be retrieved from a communication unit of the respective vehicle. The data records can be structured in JSON or XML format, for example. Alternatively, they can be structured in a serial data format such as Protobuf (Protocol Buffers). Compared to text-based data formats, Protobuf offers the advantage of significantly more compact data storage. This allows for efficient transmission of function usage data to the vehicle via the internet. The backend server can be configured to perform server-side filtering of the data records from the function usage database in response to a corresponding request from a vehicle, by filtering the data records in the function usage database according to a transmitted user ID. Furthermore, the backend server can be configured to group the filtered function usage data according to driving situation and provide it as separate lists. In another embodiment, the backend server is further configured to receive function usage data from at least one vehicle, in particular via a REST API, and to store it in the function usage database. It should be noted here that the features, in particular embodiments, and the respective advantages achievable with them, which have been described in relation to the method according to the invention, are applicable or transferable to the devices according to the invention and vice versa. Specifically, the components of the devices in the context of this description of the invention are designed to carry out the process steps according to the invention. Likewise, the functions of the components of the devices according to the invention described above are applicable as process steps of the methods according to the invention. The invention is described below with reference to exemplary embodiments, which are explained in more detail with reference to the figures. These show: Fig. 1: a system according to the invention in one exemplary embodiment; Fig. 2: further components of the system from Fig. 1; Fig. 3: the sequence of a method according to the invention in one exemplary embodiment; Fig. 4: an interior view of a vehicle; and Fig. 5a, Fig. 5b: the output of function usage suggestions on a vehicle display in a vehicle. In the following description, the same reference numbers are used for identical and equivalent parts. Fig. 1 shows a system according to the invention in an exemplary embodiment. The system comprises a backend 100, which is communicatively connected to several vehicles 200, 300, 400. The vehicles 200, 300, 400 can each be assigned to different users (via corresponding user IDs), or multiple vehicles 200, 300, 400 can be assigned to the same user. Fig. 2 shows further components of the vehicle 200 and the backend 100 of the system from Fig. 1 . The components of vehicle 200 are described below. Vehicles 300 and 400 from Fig. 1 may have the same components as vehicle 200. The vehicle 200 has a user interface module 230. In particular, the user interface module 230 is designed to control a vehicle display 260 and / or a vehicle speaker 250 in order to provide the user with an intelligent personal assistant (IPA) service via the user interface. The user interface can, in particular, provide guidance elements for the use of vehicle functions (i.e., function usage suggestions) for which corresponding applications 241, 242, 243 are registered with the user interface module 230. The software applications 241, 242, 243 can be any applications through which vehicle functions (e.g., navigation, media playback, driver assistance systems) can be controlled. Registration allows, in particular, the specification of graphic and / or acoustic elements that the user interface module 230 displays via the user interface to indicate the vehicle functions of the registered applications (i.e., to output the function usage suggestions). The function usage suggestion module 220 determines which function usage suggestions are displayed via the user interface module 230 in a given driving situation. According to the invention, the function usage suggestion module 220 takes into account the individual usage behavior of the vehicle user. The function usage suggestion module 220 is communicatively connected to the backend server 110 and is configured to retrieve function usage data from a user of vehicle 200, particularly via a REST interface. From all function usage data stored in the function usage database 120, the backend server 110 determines those function usage data that indicate previous function usage operations of the user, either in the same vehicle 200 or in another vehicle belonging to the user. The function usage suggestion module 220 is further configured to query the context acquisition module 210 for a current driving situation and, by filtering the received function usage data, to generate a function usage profile for the driving situation. The function usage profile thus generated indicates which vehicle functions are relevant for the user in the driving situation, taking into account the user's previous usage behavior. This process is explained in more detail below with reference to Fig. 3. In particular, the function usage profile can indicate whether the user has previously used a vehicle function or not. For example, if the function usage profile indicates that the user has already used a specific vehicle function several times, the function usage suggestion module 220 can instruct the user interface module 230 to configure the user interface so that a message is displayed asking the user whether they wish to use the function again. Conversely, if the function usage profile indicates that the user has not yet used a vehicle function, a message is generated instead, explaining the function before asking the user whether they wish to use it. The function usage suggestion module 220 can also be configured to collect additional function usage data by recording how the user reacted to a proactive function usage suggestion (e.g., by accepting, ignoring, or rejecting it). This additional function usage data can initially be stored in the vehicle and then transmitted directly or regularly, for example, every 24 hours, to the backend server 110. The backend server 110 then stores this additional function usage data in the function usage database 120. The context detection module 210 is configured to continuously acquire sensor signals and / or control signals from the vehicle 200 and, based on predefined assignment criteria, to determine the current driving situation. The context detection module 210 can also be configured to notify the user interface module 230 and / or the function usage suggestion module 220, particularly when a change in the driving situation is detected. In response to the notification, the user interface module 230 can send a request for relevant vehicle functions or function usage suggestions to the function usage suggestion module 220. Alternatively, the function usage suggestion module 220 can send relevant vehicle functions or function usage suggestions to the function usage suggestion module 220 in response. Fig. 3 shows the sequence of a method according to the invention in an exemplary embodiment. The method can be carried out in particular with the system explained with reference to Fig. 1 and Fig. 2. In step S1, the function usage suggestion module 220 sends a request to the backend server 110 to transmit function usage data of a user of the vehicle to which the function usage suggestion module 220 is assigned. For this purpose, the request to the backend server 110 contains a user identifier ID. In step S2, the backend server 110 determines all function usage data assigned to the user with the transmitted user ID and generates one or more lists L1, L2, L3, in which the determined function usage data is grouped according to the respective driving situation. That is, list L1 contains data about the user's function usage recorded in a first driving situation (e.g., "Driving on the highway"), while list L2 contains data about the user's function usage recorded in a second driving situation (e.g., "Vehicle is at a charging station"). The lists L1, L2, L3 can be specified, for example, in JSON or XML format. In step S3, the function usage proposal module 220 receives the lists L1, L2, L3 from the backend server 110. In step S4, the function usage proposal module 220 receives a request from the user interface module 230 to configure the user interface according to the current driving situation. In step S5, the function usage suggestion module 220 queries the current driving situation from the context detection module 210. In step S6, the Function Usage Suggestion Module 220 selects and filters the function usage data received in step S3 to identify one or more relevant vehicle functions. To do this, the Function Usage Suggestion Module selects the list from L1, L2, or L3 that contains function usage data for the driving situation identified in step S5. Within the selected list, the Function Usage Suggestion Module 220 performs a filter, removing function usage data that meets one or more of the following criteria: - the vehicle function is not available in the vehicle; - the vehicle function has an assigned expertise level that exceeds a threshold; - the percentage of user rejection responses to function suggestions for the vehicle function exceeds a threshold. From the filtered list, the Function Usage Suggestion Module 220 generates a function usage profile that indicates relevant vehicle functions for the current driving situation. Relevance can arise in particular from a high proportion of positive interactions (i.e., acceptance responses) by the user in the past. However, the relevance of a vehicle function can also result from the fact that a user has not used the vehicle function before. In step S6, the function usage suggestion module 220 instructs the user interface module 230 to configure the user interface according to the function usage profile. This can include, in particular, ensuring that only function usage suggestions for applications 241, 242, and 243 whose vehicle functions are to be displayed according to the function usage profile are provided via the user interface. Furthermore, the type and content of the notification element displayed via the user interface for the function usage suggestion can depend on whether the vehicle function has been used in the past. Some of the steps S1 to S7 described above can also be performed independently and / or in a different sequence than shown in Fig. 3. For example, querying and transmitting the function usage data (steps S1 and S2) can be performed regularly, for example every 24 hours, or event-based, for example at each start of a journey. The querying of the current driving situation (step S5) can also be performed before the request to the user interface module (step S4). Furthermore, the querying of the current driving situation (step S5) can also be performed regularly. Finally, it is possible to execute at least some of the filter operations in step S6 server-side by the backend server 110. Fig. 4 shows an interior view of a vehicle with vehicle displays 260, 261, 262, which can be controlled by a user interface module (for example, the previously described module 230) to output a function usage suggestion via the user interface. In particular, the vehicle features a head-up display 261 that extends across the entire width of the windshield and on which information, especially operating instructions, can be projected onto the windshield. This type of display is particularly advantageous for time-critical operating instructions, as they are shown directly in the driver's field of vision without requiring them to take their eyes off the road. Alternatively or additionally, the center console display 260 or the instrument cluster display 262 can also be used to display function usage suggestions. It may be possible to display function usage suggestions on different displays depending on their relevance and / or urgency. For example, urgent function usage suggestions relating to safety-critical situations and / or functions can be displayed on the head-up display 261, so that they are visible to the driver without requiring them to take their eyes off the road. Less urgent function usage suggestions can be displayed on the center console display 260. Alternatively or additionally, a function usage suggestion can be played back via voice output through a loudspeaker in the vehicle (not shown in Fig. 4). The vehicle also features a button 263 on the steering wheel, which can be programmed by the user interface module 230 so that pressing the button activates the vehicle function corresponding to the function usage suggestion. The button 263 can be located in places other than the steering wheel. Alternatively or in addition to button 263, the vehicle can be equipped to recognize a voice command from the user, which activates the vehicle function corresponding to the function usage suggestion. Fig. 5a shows an example of the screen content of a center console display 260, on which the function usage suggestions generated according to the invention are shown. The graphical user interface includes a screen area 264 for displaying navigation data, for example, a map showing a current route. Additionally, the graphical user interface includes an area 265 for displaying function usage suggestions. In the example shown, area 265 contains two function usage suggestion widgets, 266a and 266b. In widgets 266a and 266b, the function usage suggestion can be represented by text and / or graphical elements, for example, the text "Activate MAX_DEFROST function?". Area 265 can display a list of widgets in the form of a rotating menu, showing only a small subset of the list at a time (for example, one or two items). This subset can be rotated by user command or after a predetermined time, allowing any item from the list to be displayed in widget 266a or 266b. The representation shown in Fig. 5a can be used to provide function usage suggestions, for example in the form of “smart shortcuts”, i.e. to make it easier for the user to activate frequently used vehicle functions in suitable driving situations. As previously described, the user can react to an active widget 266a, 266b, for example, by activating the vehicle function by pressing a button programmed according to the function usage suggestion, by voice command, etc. In this way, the corresponding vehicle function is activated, and reaction data is recorded. Rejecting a function usage suggestion, which can be implemented accordingly, also results in the recording of reaction data. Fig. 5b shows another way of displaying function usage suggestions on a center console display 260. Here, too, there is a large area 264 for navigation data, but this is overlaid by a function usage suggestion pop-up 267. This type of display is particularly suitable for function usage suggestions that are intended to attract greater attention (for example, a suggestion to activate a driver assistance system). Figures 5a and 5b illustrate, by way of example, elements of a graphical user interface displayed on the center console display 260. Corresponding user interface elements can also be used when displayed on the head-up display 261. The units described in this description by the terms "module", "unit", "component", etc., can in principle be implemented in either hardware or software, regardless of how this is described. Likewise, the described units can be combined or implemented separately without altering the essence of the invention. It should be noted that all the parts described above, individually—even without additional features described in the respective context, even if these have not been explicitly identified as optional features in the respective context, e.g., by using: in particular, preferably, for example, e.g., parentheses, etc.—and in combination or any sub-combination, are to be regarded as independent embodiments or further developments of the invention as defined in particular in the introduction and the claims. Deviations from this are possible. Specifically, it should be noted that the word "in particular" or parentheses do not denote features that are mandatory in the respective context. Reference symbol list 100 Backend 110 Backend Server 120 Function Usage Database 200, 300, 400 Vehicle 210 Context Capture Module 220 Function Usage Suggestion Module 230 User Interface Module 241, 242, 243 Applications 250 Vehicle Speakers 260-262 Vehicle Display 263 Buttons 264 Navigation Data Screen Area 265 Function Usage Suggestion Screen Area 266a, 266b Function Usage Suggestion Widgets 267 Function Usage Suggestion Pop-Up S1 Requesting Function Usage Data S2 Determining Function Usage Data S3 Receiving Function Usage Data S4 Receiving a Request from the User Interface Module S5 Querying the Current Driving Situation S6 Selecting and Filtering Function Usage Data S7 Configuring the User Interface

Claims

A computer-implemented method for configuring a vehicle user interface (200) based on function usage data, wherein the method comprises the following steps: - Receiving, from a backend server (110), function usage data of a user of the vehicle (200), which indicates previous function usage operations of the user; - Determining a driving situation, in particular based on sensor data and / or control signals of the vehicle (200); - Generating a function usage profile for the driving situation, based on the function usage data;and- Configuring a user interface of the vehicle (200) based on the function usage profile, such that at least one function usage suggestion for a vehicle function is output via the user interface of the vehicle (200), in particular as a voice message and / or graphical indicator, wherein the configuration of the user interface furthermore performs at least one of the following actions: - Controlling a haptic actuator of the vehicle (200); - Controlling and / or programming a control element (263) of the vehicle (200).; Method according to claim 1, wherein generating the function usage profile comprises filtering the function usage data based on one or more of the following criteria: - a vehicle configuration, in particular a functional scope of the vehicle (200), and / or a state of the vehicle (200); - respective expertise levels of vehicle functions; and - a blocking list determined from the function usage data. Method according to one of the preceding claims, wherein the output of the function usage suggestion comprises at least one of the following actions: - Outputting a voice message via a loudspeaker of the vehicle (200); - Outputting a graphical indicator element via a screen (260, 261, 262) of the vehicle (200). Method according to one of the preceding claims, further comprising determining a usage value based on the usage data, wherein the usage value indicates how often the user has used a respective vehicle function to date. Method according to claim 4, wherein the voice message and / or the graphical indicator element is generated with regard to type and / or content depending on the utility value. Method according to one of the preceding claims, wherein the previous functional usage processes were recorded in a second vehicle (300, 400) of the user, which is different from the vehicle (200). Method according to one of the preceding claims, further comprising the following steps: - capturing a user's response to the output of the function usage suggestion; - transmitting second function usage data, which includes the response, to the backend server (110). Method according to claim 7, wherein the response is an acceptance, ignoring or rejection of the function usage suggestion. A computer-readable storage medium containing instructions that cause at least one processor to implement the steps of a method according to any of the preceding claims when the instructions are executed by the at least one processor. Function usage proposal module (220) for a vehicle (200) which is configured to perform the steps of a method according to any one of claims 1 to 8. System comprising: - at least one vehicle (200, 300, 400) with a function usage suggestion module (220) according to claim 10; and - a backend (100) with a backend server (110) and a function usage database (120), wherein the backend server (110) is configured to transfer data records from the function usage database (120) to at least one vehicle (200, 300, 400), in particular via a REST API. System according to claim 11, wherein the backend server (110) is further configured to receive function usage data from at least one vehicle (200, 300, 400), in particular via a REST API, and to store it in the function usage database (120).

Images