Detecting anomalies online using histograms of ECU processing activity
Disclosed embodiments relate to identifying Electronic Control Unit (ECU) anomalies in a vehicle. Operations may include monitoring, in the vehicle, data representing real-time processing activity of the ECU; accessing, in the vehicle, historical data relating to processing activity of the ECU, the historical data representing expected processing activity of the ECU; comparing, in the vehicle, the real-time processing activity data with the historical data, to identify at least one anomaly in the real-time processing activity of the ECU; and implementing a control action for the ECU when the at least one anomaly is identified.
1. A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for identifying Electronic Control Unit (ECU) anomalies in a vehicle, comprising:
monitoring, in the vehicle, data representing real-time processing activity of the ECU;
accessing, in the vehicle, historical data relating to processing activity of the ECU, the historical data representing expected processing activity of the ECU;
comparing, in the vehicle, the real-time processing activity data with the historical data, to identify at least one anomaly in the real-time processing activity of the ECU; and
implementing a control action for the ECU when the at least one anomaly is identified, wherein the control action includes issuing a prompt to adjust the ECU from executing a first version of ECU software to a second version of ECU software;
wherein software on the ECU is mapped to a plurality of functional units, and the ECU is configured to utilize a virtual file system to manage and track one or more versions of each of the plurality of functional units.
2. The non-transitory computer readable medium of claim 1 , wherein software on the ECU includes position-independent code, and the ECU is configured to utilize the position-independent code without requiring modification to the software.
3. The non-transitory computer readable medium of claim 1 , wherein adjusting the ECU from executing the first version of ECU software to the second version of ECU software comprises:
updating memory addresses of one or more functional units managed by the VFS based on a delta file corresponding to the second version of ECU software.
4. The non-transitory computer readable medium of claim 1 , wherein the instructions further comprise:
monitoring operations of the ECU to generate the historical data.
5. The non-transitory computer readable medium of claim 1 , wherein the monitoring, accessing, comparing, and implementing occur within an orchestrator in the vehicle, the orchestrator being separate from the ECU.
6. The non-transitory computer readable medium of claim 5 , wherein the orchestrator is configured to perform the monitoring, accessing, comparing, and implementing for a plurality of ECUs in the vehicle.
7. The non-transitory computer readable medium of claim 1 , wherein the at least one anomaly corresponds to specific memory locations used by the ECU.
8. The non-transitory computer readable medium of claim 1 , wherein the at least one anomaly corresponds to specific sequences of memory locations used by the ECU.
9. The non-transitory computer readable medium of claim 1 , wherein the at least one anomaly corresponds to at least one peak in data flow in or out of the ECU.
10. The non-transitory computer readable medium of claim 1 , wherein the at least one anomaly corresponds to at least one peak in data processing by a processor of the ECU.
11. The non-transitory computer readable medium of claim 1 , wherein the at least one anomaly corresponds to at least one anomaly in power consumption of the ECU.
12. The non-transitory computer readable medium of claim 1 , wherein the control action includes sending an alert associated with the ECU.
13. The non-transitory computer readable medium of claim 1 , wherein the control action includes blocking an instruction sent from the ECU.
14. The non-transitory computer readable medium of claim 1 , wherein the control action includes rolling back a version of ECU software running on the ECU to a prior version of ECU software.
15. A system for identifying Electronic Control Unit (ECU) anomalies in a vehicle, the system comprising:
one or more processors; and
one or more memories having instructions that, when executed by the one or more processors, cause the one or more processors to perform the operations of:
monitoring, in the vehicle, data representing real-time processing activity of the ECU;
accessing, in the vehicle, historical data relating to processing activity of the ECU, the historical data representing expected processing activity of the ECU;
comparing, in the vehicle, the real-time processing activity data with the historical data, to identify at least one anomaly in the real-time processing activity of the ECU; and
implementing a control action for the ECU when the at least one anomaly is identified, wherein the control action includes issuing a prompt to adjust the ECU from executing a first version of ECU software to a second version of ECU software;
wherein software on the ECU is mapped to a plurality of functional units, and the ECU is configured to utilize a virtual file system to manage and track one or more versions of each of the plurality of functional units.
16. The system of claim 15 , wherein the monitoring, accessing, comparing, and implementing occur within an orchestrator in the vehicle, the orchestrator being separate from the ECU.
17. The system of claim 16 , wherein the orchestrator is configured to perform the monitoring, accessing, comparing, and implementing for a plurality of ECUs in the vehicle.
18. A computer-implemented method for identifying Electronic Control Unit (ECU) anomalies in a vehicle, the method comprising:
monitoring, in the vehicle, data representing real-time processing activity of the ECU;
accessing, in the vehicle, historical data relating to processing activity of the ECU, the historical data representing expected processing activity of the ECU;
comparing, in the vehicle, the real-time processing activity data with the historical data, to identify at least one anomaly in the real-time processing activity of the ECU; and
implementing a control action for the ECU when the at least one anomaly is identified, wherein the control action includes issuing a prompt to adjust the ECU from executing a first version of ECU software to a second version of ECU software;
wherein software on the ECU is mapped to a plurality of functional units, and the ECU is configured to utilize a virtual file system to manage and track one or more versions of each of the plurality of functional units.