Adaptive Input Countermeasures on Human-Machine Interface

By using controller circuits to predict and process user input in automotive systems, identifying and avoiding potential failures, the user experience and safety problems caused by automotive system failures are solved, and a more stable and safe vehicle operation is achieved.

CN112541518BActive Publication Date: 2024-11-05APTIV TECHNOLOGIES AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010845204.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-09-06
Filing Date
2020-08-20
Publication Date
2024-11-05
Estimated Expiration
2040-08-20

AI Technical Summary

Technical Problem

Car system failures can lead to poor user experience, increased warranty claims, and potential safety issues, and the cause of the failure is unknown.

Method used

A vehicle system is designed to receive user input through a human-machine interface (HMI) and to predict potential second input using controller circuits, determine potential faults based on system status and historical data, and perform countermeasures to avoid or reduce the impact of faults, including Modify the HMI display, disable the input icon, process the input through alternative circuits, preload the data to reduce latency and learn user history input.

Benefits of technology

Effectively avoid or reduce system failures, improve user experience, reduce the risk of warranty claims, enhance driver safety, and take timely measures to reduce system delays and crash risks by predicting and handling potential failures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112541518B_ABST
    Figure CN112541518B_ABST
Patent Text Reader

Abstract

A vehicle system includes a human machine interface (HMI) and a controller circuit. The HMI accepts input from a user. The controller circuit is configured to receive a first input from the user via the HMI, anticipate a potential second input from the user via the HMI, determine a potential system fault based on at least one of an operating state of the system and the potential second input, determine based on historical data whether an input sequence including the first input from the user and the second input from the user is likely to affect the performance of the system and / or one or more components of the system, and if the input sequence is likely to cause an impact on the performance of the system and / or one or more components of the system, execute at least one countermeasure to avoid or reduce the impact.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to vehicle systems that avoid system failures. Background Art

[0002] System failures in automotive applications can lead to a poor user experience, increased warranty claims, and potential safety issues due to driver distraction. The root cause of the system failure and / or system failure may be unknown when the vehicle goes into production. Summary of the invention

[0003] An example of a vehicle system includes a human-machine interface (HMI) for a vehicle that accepts input from a user; and a controller circuit that is communicatively coupled to the HMI. The controller circuit is configured to receive a first input from the user via the HMI. The controller circuit is further configured to anticipate a potential second input from the user via the HMI. The controller circuit is further configured to determine a potential system fault based on at least one of an operating state of the system and a potential second input. The controller circuit is further configured to determine, based on historical data, whether an input sequence including a first input from the user and a potential second input from the user is likely to affect the performance of the system and / or one or more components of the system. If the input sequence is likely to cause an impact on the performance of the system and / or the one or more components of the system, the controller circuit is further configured to execute at least one countermeasure to avoid or reduce the impact.

[0004] In an example of a vehicle system having one or more features of the previous paragraph, the controller circuit modifies the HMI display to prevent the user from selecting an input.

[0005] In an example having one or more features of the vehicle system of the previous paragraph, an icon representing the input on the HMI display is disabled.

[0006] In an example of a vehicle system having one or more features of any of the above paragraphs, the controller circuit processes the second user input through an alternate circuit and / or logic path to suppress a potential system failure.

[0007] In an example of a vehicle system having one or more features of any of the above paragraphs, the controller circuit preloads a memory of the system with data associated with the most likely potential second input, thereby reducing system latency.

[0008] In the example having one or more features of the vehicle system of the previous paragraph, the most likely potential second input is based on user input history.

[0009] In an example having one or more features of the vehicle system of any of the above paragraphs, the most likely potential second input is based on crowd-sourced data collected from the same system installed in other vehicles.

[0010] In an example having one or more features of a vehicle system of any of the above paragraphs, the controller circuit learns potential system faults based on a user input history.

[0011] In an example of a vehicle system having one or more features of any of the above paragraphs, the controller circuit learns potential system faults based on crowd-sourced data collected from the same system installed in other vehicles.

[0012] In an example having one or more features of a vehicle system of any of the above paragraphs, the controller circuit downloads data indicative of a potential system fault.

[0013] In an example having one or more features of the vehicle system of any of the above paragraphs, the controller circuit further categorizes potential system faults by severity rating.

[0014] In an example having one or more features of a vehicle system of any of the above paragraphs, the severity rating indicates a level of distraction of the user.

[0015] In an example having one or more features of the vehicle system of any of the above paragraphs, the severity rating indicates at least one of a system delay, a system crash, and a system restart.

[0016] In an example having one or more features of a vehicle system of any of the above paragraphs, data collected from one or more vehicles experiencing a system failure includes at least one of a timestamp, an input sequence, and a system state prior to the system failure event.

[0017] A method of operating a vehicle system includes: receiving, with a controller circuit, a first input from a user via a human machine interface (HMI) for the vehicle, the controller circuit being communicatively coupled to the HMI; anticipating, with the controller circuit, a potential second input from the user via the HMI; determining, with the controller circuit, a potential system fault based on an operating state of the system and at least one of the potential second inputs; determining, with the controller circuit, based on historical data, whether a sequence of inputs including the first input from the user and the potential second input from the user is likely to affect performance of the system and / or one or more components of the system; and if the sequence of inputs is likely to result in an impact on performance of the system and / or the one or more components of the system, executing, with the controller circuit, at least one countermeasure to avoid or reduce the impact.

[0018] In an example having one or more features of the method of operating a vehicle system of the preceding paragraphs, the controller circuit modifies the HMI display to prevent the user from selecting the input.

[0019] In an example having one or more features of any of the above methods of operating a vehicle system, an icon representing the input on the HMI display is disabled.

[0020] In an example having one or more features of any of the above methods of operating a vehicle system, the controller circuit processes the second user input via an alternate circuit and / or logic path to suppress a potential system failure.

[0021] In an example having one or more features of any of the above methods of operating a vehicle system, the controller circuit preloads a memory of the system with data associated with the most likely potential second input, thereby reducing system latency.

[0022] In an example having one or more features of any of the above methods of operating a vehicle system, the most likely potential second input is based on a user input history.

[0023] In an example having one or more features of any of the above methods of operating a vehicle system, the most likely potential second input is based on crowd-sourced data collected from the same system installed in other vehicles.

[0024] In an example having one or more features of any of the above methods of operating a vehicle system, the controller circuit learns the potential system fault based on a user input history.

[0025] In an example having one or more features of any of the above methods of operating a vehicle system, the controller circuit learns the potential system fault based on crowd-sourced data collected from the same system installed in other vehicles.

[0026] In an example having one or more features of any of the above methods of operating a vehicle system, the controller circuit downloads data indicative of a potential system fault.

[0027] In an example having one or more features of any of the above methods of operating a vehicle system, the controller circuit further categorizes the potential system faults by severity rating.

[0028] In an example having one or more features of any of the above methods of operating a vehicle system, the severity rating indicates a level of distraction of the user.

[0029] In an example having one or more features of any of the above methods of operating a vehicle system, the severity rating indicates at least one of a system delay, a system crash, and a system restart.

[0030] In an example having one or more features of any of the above methods of operating a vehicle system, data collected from one or more vehicles experiencing a system failure includes at least one of a timestamp, an input sequence, and a system state prior to the system failure event. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The present invention will now be described by way of example with reference to the accompanying drawings, in which:

[0032] Figure 1 is a diagram of a vehicle system according to one embodiment;

[0033] Figure 2 According to an embodiment Figure 1 Graphic representation of the human-machine interface of the vehicle system;

[0034] Figure 3 According to an embodiment Figure 1 a graphical representation of another human-machine interface of a vehicle system; and

[0035] Figure 4 is a diagram showing the operation according to another embodiment Figure 1 A flow chart of a method for a vehicle system. DETAILED DESCRIPTION

[0036] Reference will now be made in detail to the embodiments, examples of which are shown in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, known methods, procedures, components, circuits, and networks are not described in detail in order to avoid unnecessarily obscuring aspects of the embodiments.

[0037] Figure 1A vehicle system 10 is shown that avoids system failures that may be caused by a sequence of user inputs, hereinafter referred to as system 10. As used herein, system failures include any undesirable changes in system performance, including but not limited to system crashes, system restarts, delayed responses or delays of system 10 to inputs, audio glitches, dropped calls, etc. System 10 includes one or more human-machine interfaces (HMI 12) for a vehicle, which accept inputs from a user. HMI 12 can be any HMI 12 associated with a vehicle subsystem, including but not limited to an audio interface, a navigation interface, a communication interface, a climate control interface, or any vehicle operating system interface that can be configured to accept inputs from a user. In an example, HMI 12 includes a touch screen having icons representing specific input commands unique to a vehicle subsystem. In another example, HMI 12 includes switches and / or knobs that can be adjusted to input specific commands (such as adjusting the volume of an audio speaker and / or turning lights on and off). In another example, HMI 12 includes buttons on a steering wheel of a vehicle that are inputs to a driver information center displayed on a dashboard of the vehicle.

[0038] The system 10 includes a controller circuit 14 that is communicatively coupled to the HMI 12. The controller circuit 14 may include a processor (not shown) such as a microprocessor or other control circuits such as analog and / or digital control circuits. The control circuit may include one or more application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) programmed to perform the technology, or may include one or more general purpose hardware processors programmed to perform the technology according to program instructions in firmware, memory, other storage, or a combination. The controller circuit 14 may also combine customized hardwired logic, ASICs, or FPGAs with customized programming to implement the technology. The controller circuit 14 may include a memory or storage medium (not shown), including non-volatile memory such as an electrically erasable programmable read-only memory (EEPROM) for storing one or more routines, thresholds, and captured data. The EEPROM stores data and allows individual bytes to be erased and reprogrammed by applying specific programming signals. The controller circuit 14 may include other examples of non-volatile memory such as flash memory, read-only memory (ROM), programmable read-only memory (PROM), and erasable programmable read-only memory (EPROM). The controller circuit 14 may include volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM). One or more routines may be executed by the processor to perform steps for avoiding system failures based on signals received by the controller circuit 14 from the HMI 12 as described herein. In an example, the HMI 12 includes the controller circuit 14 (i.e., the controller circuit 14 is integrated into the HMI 12 electrical package). In another example, the HMI 12 and the controller circuit 14 are separate devices.

[0039] Figure 2 An example of an HMI 12 isolated from the system 10 is shown. In this example, the HMI 12 is an audio interface on the vehicle console that indicates a song being played from a user's remote device (e.g., a smartphone—not shown). The remote device may be connected via a cable, or via a wireless connection (such as a Wi-Fi, ultra-wideband (UWB), or near field communication (NFC)) connected to the system 10.

[0040] The controller circuit 14 is configured to receive a first input 16 from a user via the HMI 12. In an example, the first input 16 is a user selection of a particular function via the HMI 12. Examples of the first input 16 include, but are not limited to, selecting an audio function, a phone function, a navigation function, or other vehicle functions such as vehicle headlights, vehicle interior lights, advanced driver safety system (ADAS) functions, cruise control, vehicle information center functions, etc. Figure 2In the example shown, the first input 16 is the user selecting the AUX icon to access music stored on the user's smartphone.

[0041] The controller circuit 14 is further configured to anticipate a potential second input 18 from the user via the HMI 12. That is, before the user makes a selection, the controller circuit 14 determines the next selection that the user is likely to make via the HMI 12. In an example, the potential second input 18 is based on the current HMI 12 options being displayed to the user. In this example, the potential second input 18 can be any of the icons displayed on the audio interface HMI 12, such as forward and / or back icons to move between songs, a pause icon, a song list icon, etc. In another example, the potential second input 18 can be made to any of the other vehicle interfaces other than the audio interface HMI 12, such as those described above.

[0042] In the example, the controller circuit 14 anticipates a potential second input 18 based on historical interaction data between the user and the HMI 12. In this example, the controller circuit 14 learns over time using any of the known machine learning routines that the user will be likely to select a particular icon (e.g., a forward icon on the HMI 12 to skip a song) based on the user's input history.

[0043] Machine learning is a data analysis technique that teaches computers to learn from experience. Machine learning routines or algorithms use computational methods to learn information from data without relying on predetermined equations as models. These routines improve their performance as the number of samples available for learning increases. Machine learning uses two types of techniques: supervised learning, which trains a model based on known input and output data in order to predict future outputs; and unsupervised learning, which discovers hidden patterns or intrinsic structures in the input data. Supervised learning uses classification and regression techniques to develop predictive models. Common algorithms used to perform classification include support vector machines (SVMs), boosted and bagged decision trees, k-nearest neighbors, naive Bayes, discriminant analysis, logistic regression, and neural networks. Common regression algorithms include linear models, nonlinear models, regularization, stepwise regression, boosted and bagged decision trees, neural networks, and adaptive neuro-fuzzy learning. Unsupervised learning discovers hidden patterns or intrinsic structures in data. It is used to draw inferences from a data set consisting of input data without labeled responses. Clustering is a commonly used unsupervised learning technique. Common algorithms used to perform clustering include k-means and K-medoids, hierarchical clustering, Gaussian mixture models, hidden Markov models, self-organizing maps, fuzzy c-means clustering, and subtractive clustering.

[0044] In another example, the controller circuit 14 anticipates a potential second input 18 based on crowdsourced data from other users of the same system in other vehicles. In this example, a memory in the controller circuit 14 includes information about the likelihood of a potential second input 18 from a user based on the crowdsourced data, as will be described in more detail below. The crowdsourced data is processed using any of the known machine learning routines described above to determine the likelihood of a potential second input 18 from a user. In an example, the controller circuit 14 downloads crowdsourced data indicating a potential system failure from a cloud computing environment (sometimes referred to as the "cloud") via an over-the-air (OTA) transmission. In another example, data indicating a potential system failure is downloaded to the controller circuit 14 during vehicle assembly. In another example, data indicating a potential system failure is downloaded to the controller circuit 14 during a vehicle service visit.

[0045] Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services). In a typical cloud computing system, one or more large cloud data centers house machines used to deliver services provided by the cloud. A cloud computing environment includes one or more cloud data centers. In general, a cloud data center refers to the physical arrangement of servers that make up a cloud or a specific part of a cloud. For example, servers are physically arranged as rooms, groups, rows, and racks in a cloud data center. The cloud includes a cloud data center and networks and networking resources (e.g., networking equipment, nodes, routers, switches, and networking cables) that interconnect cloud data centers and help facilitate access to cloud computing services by the system 10. In an example, a network represents any combination of one or more local networks, wide area networks, or internetworks coupled using wired or wireless links, which are deployed using terrestrial or satellite connections. Data exchanged through the network is transmitted using any number of network layer protocols (such as Internet Protocol (IP), Multi-Protocol Label Switching (MPLS), Asynchronous Transfer Mode (ATM), Frame Relay, etc.). In addition, in examples where the network represents a combination of multiple subnetworks, different network layer protocols are used at each of the underlying subnetworks. In some examples, the network represents one or more interconnected interconnected networks, such as the public Internet. In an example, system 10 is connected to the cloud via a network link and a network adapter.

[0046] The controller circuit 14 determines a potential system fault based on at least one of the operating state of the system 10 and a potential second input 18 from a user. The controller circuit 14 includes a data collection software component that uses various data sources inherent in the operating system (OS), hardware, and / or other knowledge of the system 10 to periodically collect and package data representing the current state of the system 10 based on a fault event and / or the user's input. The data collected from one or more vehicles experiencing a system fault includes at least one of a timestamp, an input sequence 20, and a system state prior to the system fault event. The current state of the system 10 is characterized by, but not limited to, the current software version, a set of installed applications and their versions, processes currently running on the system 10, central processor unit (CPU) usage, memory usage, system temperature, error messages, system crashes, etc. The collected data from the various data sources described above is combined with a historical record of system fault events to more completely define the current state of the system 10. The data is analyzed by the controller circuit 14 and / or transmitted to a cloud computing environment for storage and further data analysis.

[0047] The controller circuit 14 determines whether an input sequence 20 including a first input 16 from a user and a potential second input 18 from a user is likely to affect the performance of the system 10 and / or affect the performance of one or more components of the system 10 based on historical data. The historical data analyzed and downloaded from the cloud and / or analyzed on the vehicle identifies potential system faults and associated input sequences 20 that result in known historical system fault events. In an example, the system fault includes error message content (e.g., a "SIGSEG" memory error message). In another example, the system fault includes a response latency (i.e., delay) to a user input that exceeds a predetermined threshold (e.g., a screen change takes more than two seconds after a button or icon is pressed). In another example, the system fault includes an anomaly identified by a machine learning model or other statistically derived metric, indicating a degradation in the performance characteristics of the system 10. In this example, the machine learning anomaly detection model can be trained based on data from a single user / single vehicle and / or can be trained based on data from a fleet of similarly configured vehicles (i.e., from crowd-sourced data) to identify "normal" system behavior versus "abnormal" system behavior that indicates a system fault. In an example, the trained model analyzes the current data to indicate an "abnormal probability" metric that can be used with a threshold to identify a system failure. For example, if the abnormal probability is greater than a threshold of 90%, a system failure is likely to occur. Other threshold levels can be defined by the user based on failure rates.

[0048] In an example, system states and fault events are also captured and stored with timestamps. In this example, the identified fault mode can be further characterized by the system state and event history before the system fault.

[0049] In the example, data collected and transmitted to the cloud, and / or stored on the vehicle is analyzed to obtain user behavior patterns. Users can develop behavior patterns so that the likelihood of the next user input (i.e., potential second input 18) can be predicted using associated probabilities. The user input sequence 20 is stored by the controller circuit 14 when it occurs, and / or uploaded to the cloud. The current system state is also stored by the controller circuit 14 with an associated timestamp. In the example, the controller circuit 14 accesses a lookup table of historical user input sequences 20 with timestamps and associated system states to identify historical events similar to the current system state and the current user's first input 16 (e.g., the currently activated application and the last button press match the data in the lookup table). Based on the current system state and the input sequence 20 history, the probability of each potential second input 18 can be calculated.

[0050] In an example, the controller circuit 14 further classifies potential system failures by indicating a severity rating of at least one of a user distraction level, a system delay, a system crash, and a system restart. In an example, a higher severity rating is applied to a potential system failure that may cause a safety issue (such as distracting a user who may also be a vehicle operator). In another example, a lower severity rating is applied to a system failure that may only cause a minor inconvenience to the user, such as a system delay that does not exceed a time threshold. In another example, a system delay failure that exceeds a time threshold may receive an increased severity rating due to an increased delay time that may result in an increased level of user distraction. In another example, a system crash and / or a system restart may receive an increased severity rating due to the unavailability of the system 10 and / or an increased level of user distraction. Other factors may be used to determine the severity rating, including but not limited to the likelihood of a system failure occurring, the time it takes the system 10 to recover from the failure, the ability of the system 10 to apply countermeasures to avoid the failure, historical user data, the current vehicle environment, and historical crowd-sourced data.

[0051] In an example, the controller circuit 14 determines that the input sequence 20 is likely to have a predicted effect on the performance of the system 10 and / or the performance of one or more components of the system 10, and executes at least one countermeasure to avoid or reduce the effect on the system 10. In an example, the controller circuit 14 enacts a countermeasure based on a severity rating threshold. In this example, when the controller circuit determines that the severity rating is greater than the severity rating threshold, the controller circuit 14 enacts a countermeasure to avoid a system failure. The controller circuit 14 may evaluate the feasibility of one or more countermeasures before selecting a preferred countermeasure to be executed. In addition, when the controller circuit 14 determines that the severity rating is less than the severity rating threshold, the controller circuit 14 may not execute the countermeasure, or may execute an alternative strategy based on the current system state.

[0052] In an example, the controller circuit 14 executes a countermeasure that modifies the HMI 12 display to prevent the user from selecting an input. In this example, the icon representing the input on the HMI 12 display is disabled (ie, grayed out and / or removed from the HMI 12). Return to Reference Figure 2 In the example of the HMI 12 shown in , the audio system is operating and the controller circuit 14 determines that the CPU usage is 90% with a memory usage of 15%. The HMI 12 displays a media player screen showing options such as "Pause", "Next", "Previous", and "Song List". Historical data downloaded from the cloud from 100,000 other vehicles with the same version of the media player application indicates that there is a 95% chance that the media player application will crash when the CPU usage is greater than 80% and the user selects the "Song List" option. In this example, the severity rating of the fault is above the severity rating threshold (i.e., if the "Song List" option is selected, a system crash is likely to occur), and the controller circuit 14 avoids a system fault by disabling the "Song List" option until the system state changes to a situation where the likelihood of a system fault is reduced. In this example, when the user selects the "Song List" option, the HMI 12 can display a message to the user that the function is currently unavailable.

[0053] In another example, the controller circuit 14 implements a countermeasure to process the second user input through an alternative path (such as an alternative circuit) to suppress a potential system failure. Referring again to the previous example, where the "Song List" option, if selected, would likely cause a system crash, the controller circuit 14 can first determine whether there is an alternative path in the infotainment system to display the song list to the user and still avoid a system crash. That is, the controller circuit 14 evaluates whether there is another way to display the song list on the HMI 12 without causing the infotainment system to crash. In this example, an alternative path for displaying the song list is defined for the controller circuit 14, and when the user selects the "Song List" icon, the controller circuit 14 displays the song list. In this example, the icon on the HMI 12 remains unchanged to allow the user to select the icon, even if an alternative path is used to display the song list.

[0054] In another example, the controller circuit 14 implements a countermeasure to preload the memory of the system 10 with data associated with the most likely potential second input 18, thereby reducing system latency. Figure 2 In the example of the HMI 12 shown in FIG. 1 , the audio system is operating and the controller circuit 14 determines that the CPU usage is 95% with the memory usage being 20%. The HMI 12 displays a media player screen showing options such as “Pause”, “Next”, “Previous”, and “Song List”. Historical data downloaded from the cloud from 100,000 other vehicles with the same version of the media player application indicates that the likelihood that the user may make a second input 18 within the next 10 seconds is as follows: “Pause” 2%; “Next” 65%; “Previous” 5%, and “Song List” 2%. Based on exceeding a threshold of likelihood that the user will select the “Next” option (e.g., greater than 50%), the controller circuit 14 preloads the next song into memory, thereby reducing latency time for the audio system when the user eventually selects the “Next” option.

[0055] While the above examples describe using crowd-sourced data to determine a user's potential second input 18 , it will be appreciated that data from a single user and / or a single vehicle may be used alone or in conjunction with crowd-sourced data to avoid system failure.

[0056] Figure 3 is an illustration of another example of an HMI 12 for a vehicle. In this example, the HMI 12 is the driver information portion of a dashboard display screen that can be interacted with via buttons on a steering wheel. It will be appreciated that the above description Figure 2 The example of the audio system HMI 12 will also apply to Figure 3 Driver information HMI 12.

[0057] Figure 4 is a flow chart illustrating an example of method 100 .

[0058] Step 102, receiving a first input, includes receiving a first input 16 from a user via a human machine interface (HMI) 12 for the vehicle using the controller circuit 14 as described above. The controller circuit 14 is communicatively coupled to the HMI 12. The first input 16 can be a user selection of a particular function via the HMI 12, including selecting an audio function, a phone function, a navigation function, or other vehicle functions, such as vehicle headlights, vehicle interior lights, advanced driver safety system (ADAS) functions, cruise control, and vehicle information center functions, etc.

[0059] Step 104, anticipating a second input, includes anticipating a potential second input 18 from the user via the HMI 12 using the controller circuit 14 as described above. As described above, the controller circuit 14 anticipates or predicts the most likely potential second input 18 from the user based on historical data collected from the user or the vehicle and / or crowd-sourced data collected from many vehicles.

[0060] Step 106, determining a potential fault, includes determining a potential system fault based on the operating state of the system 10 and at least one of the potential second input 18 using the controller circuit 14 as described above. The data collected from the one or more vehicles experiencing the system fault includes at least one of a timestamp, an input sequence 20, and a system state prior to the system fault event.

[0061] Step 108, determining the impact, includes determining, using the controller circuit 14, based on the historical data, whether the input sequence 20 including the first input 16 from the user and the potential second input 18 from the user is likely to affect the performance of the system 10 and / or one or more components of the system 10. As described above, the historical data analyzed and downloaded from the cloud and / or analyzed on the vehicle identifies potential system faults and associated input sequences 20 that resulted in known historical system fault events.

[0062] Step 110, executing countermeasures, includes executing at least one countermeasure, using the controller circuit 14, to avoid or reduce the impact. If the input sequence 20 is likely to cause an impact on the performance of the system 10 and / or one or more components of the system 10, then the controller circuit 14 determines a preferred countermeasure to avoid a system failure. As described above, in an example, the controller circuit 14 executes a countermeasure based on a severity rating threshold. In an example, the controller circuit 14 disables a function of the HMI 12 to avoid a system failure. In another example, the controller circuit 14 finds an alternative path to avoid a system failure. In yet another example, the controller circuit 14 preloads data to avoid a system failure.

[0063] Thus, a vehicle system 10 and method 100 of operating the vehicle system 10 are provided. The vehicle system 10 may provide advantages over other vehicle systems because the vehicle system 10 adapts based on historical data to avoid system failures.

[0064] Although the present invention has been described according to the preferred embodiments of the present invention, it is not intended to be limited thereto, but only to the scope set forth in the appended claims. "One or more" includes: a function performed by one element; a function performed by more than one element, for example, in a distributed manner; several functions performed by one element; several functions performed by several elements; or any combination of the above. It will be understood that, although in some instances, the terms first, second, etc. are used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact may be referred to as a second contact, and similarly, a second contact may be referred to as a first contact without departing from the scope of each described embodiment. Both the first contact and the second contact are contacts, but they are not the same contact. The terms used in the description of the various described embodiments herein are only for the purpose of describing specific embodiments and are not intended to be restrictive. As used in the description of the various described embodiments and the appended claims, the singular forms "a", "an", and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any of the associated listed items and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "include," "including," "comprise," and / or "comprising" when used in this specification indicate the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term "if" is optionally interpreted to mean "when" or "after" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if determined" or "if [stated situation or event] is detected" is optionally interpreted to mean "after determining" or "in response to determining" or "after detecting [stated situation or event]" or "in response to detecting [stated situation or event]," depending on the context.

Claims

1. A vehicle system, include: a human machine interface (HMI) for a vehicle, the human machine interface (HMI) receiving input from a user; as well as a controller circuit communicatively coupled to the HMI, the controller circuit being configured to: receiving a first input from the user via the HMI, the first input being a selected function of the vehicle; prior to receiving a second input from the user via the HMI, anticipating a potential second input from the user via the HMI, the potential second input being a selectable option associated with the selected function; determining a potential system fault based on an operating state of the system and the potential second input; determining, based on crowdsourced data, whether a probability that a sequence of inputs including the first input from the user and the potential second input from the user is likely to affect performance of the selected function is above a predetermined threshold; and If the probability that the input sequence affects the performance of the selected function is above the predetermined threshold, at least one countermeasure is executed to avoid or reduce the impact.

2. The system according to claim 1, It is characterized in that The controller circuit modifies the HMI display to prevent the user from selecting an input.

3. The system according to claim 2, It is characterized in that The icon representing the input on the HMI display is disabled.

4. The system according to claim 1, It is characterized in that The controller circuit processes the second user input via an alternate circuit to suppress the potential system failure.

5. The system according to claim 1, It is characterized in that The controller circuit preloads the system's memory with data associated with the most likely potential second input, thereby reducing system latency.

6. The system according to claim 5, It is characterized in that The most likely potential second input is based on user input history.

7. The system according to claim 5, It is characterized in that The most likely potential second input is based on crowd-sourced data collected from the same system installed in other vehicles.

8. The system of claim 1, It is characterized in that The controller circuit learns the potential system faults based on a history of user inputs.

9. The system of claim 1, It is characterized in that The controller circuit learns the potential system fault based on crowd-sourced data collected from identical systems installed in other vehicles.

10. The system of claim 1, It is characterized in that The controller circuitry downloads data indicative of the potential system fault.

11. The system of claim 1, It is characterized in that The controller circuit further categorizes the potential system faults by severity rating.

12. The system according to claim 11, It is characterized in that The severity rating indicates a level of distraction for the user.

13. The system of claim 11, It is characterized in that The severity rating indicates at least one of a system delay, a system crash, and a system restart.

14. The system of claim 1, It is characterized in that The data collected from the one or more vehicles experiencing the system failure includes at least one of a timestamp, an input sequence, and a system state prior to the system failure event.

15. A method of operating a vehicle system, include: receiving, with the controller circuit, a first input from a user via a human machine interface (HMI) for a vehicle, the first input being a selected function of the vehicle; the controller circuit being communicatively coupled to the HMI; prior to receiving a second input from the user via the HMI, anticipating, with the controller circuitry, a potential second input from the user via the HMI, the potential second input being a selectable option associated with the selected function; determining, with the controller circuit, a potential system fault based on an operating state of the system and the potential second input; determining, with the controller circuitry, based on crowdsourced data, whether a probability that a sequence of inputs including the first input from the user and the potential second input from the user is likely to affect performance of the selected function is above a predetermined threshold; and If the probability that the input sequence affects the performance of the selected function is above the predetermined threshold, at least one countermeasure is executed, using the controller circuit, to avoid or reduce the impact.

16. The method of claim 15, It is characterized in that The controller circuit modifies the HMI display to prevent the user from selecting an input.

17. The method of claim 16, It is characterized in that The icon representing the input on the HMI display is disabled.

18. The method of claim 15, It is characterized in that The controller circuit processes the second user input via an alternate circuit to suppress the potential system failure.

19. The method of claim 15, It is characterized in that The controller circuit preloads the system's memory with data associated with the most likely potential second input, thereby reducing system latency.

20. The method of claim 19, It is characterized in that The most likely potential second input is based on user input history.

21. The method of claim 19, It is characterized in that The most likely potential second input is based on crowd-sourced data collected from the same system installed in other vehicles.

22. The method of claim 15, It is characterized in that The controller circuit learns the potential system faults based on a history of user inputs.

23. The method of claim 15, It is characterized in that The controller circuit learns the potential system fault based on crowd-sourced data collected from identical systems installed in other vehicles.

24. The method of claim 15, It is characterized in that The controller circuitry downloads data indicative of the potential system fault.

25. The method of claim 15, It is characterized in that The controller circuit further categorizes the potential system faults by severity rating.

26. The method of claim 25, It is characterized in that The severity rating indicates a level of distraction for the user.

27. The method of claim 25, It is characterized in that The severity rating indicates at least one of a system delay, a system crash, and a system restart.

28. The method of claim 15, It is characterized in that The data collected from the one or more vehicles experiencing the system failure includes at least one of a timestamp, an input sequence, and a system state prior to the system failure event.