# US 2021/0064359 A1 · Self-healing learning system for one or more controllers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0064359 A1
- Document ID: US20210064359A1
- Status: Published application
- Kind: A1
- Application number: 17/096,413
- Filed: 2020-11-12
- Published: 2021-03-04
- Earliest claimed: 2017-07-25
- Assignees: Aurora Labs Ltd.
- Applicants: Aurora Labs Ltd.
- Inventors: Zohar Fox
- Web page: https://patentgrep.com/patent/US20210064359A1

## CPC

- G06F 8/658: Incremental updates; Differential updates
- B60W 50/02: Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
- B60W 50/0205: {Diagnosing or detecting failures; Failure detection models}
- B60W 50/0225: {Failure correction strategy}
- B60W 50/04: Monitoring the functioning of the control system
- B60W 50/045: {Monitoring control system parameters}
- G06F 8/60: Software deployment
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/654: using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
- G06F 8/656: while running
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57)
- G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading}
- G06F 11/0721: {within a central processing unit [CPU]}
- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/1433: {during software upgrading}
- G06F 11/1629: {Error detection by comparing the output of redundant processing systems}
- G06F 11/3612: {by runtime analysis (performance monitoring G06F11/3466)}
- G06F 12/0284: {Multiple user address space allocation, e.g. using different base addresses (interprocessor communication G06F15/163)}
- G06F 12/0646: {Configuration or reconfiguration}
- G06F 16/188: Virtual file systems
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F 21/572: {Secure firmware programming, e.g. of basic input output system [BIOS]}
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- B60W 2050/021: {Means for detecting failure or malfunction}
- G06F 8/66: {of program code stored in read-only memory [ROM]}
- G06F 2212/1008: Correctness of operation, e.g. memory ordering
- G06F 2212/1044: Space efficiency improvement
- G06F 2212/1056: Simplification
- G06F 2221/033: Test or assess software
- G06N 20/00: Machine learning
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- B60W: CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Disclosed embodiments relate to automatically providing updates to at least one vehicle. Operations may include receiving, at a server remote from the at least one vehicle, Electronic Control Unit (ECU) activity data from the at least one vehicle, the ECU activity data corresponding to actual operation of the ECU in the at least one vehicle; determining, at the server and based on the ECU activity data, a software vulnerability affecting the at least one vehicle, the software vulnerability being determined based on a deviation between the received ECU activity data and expected ECU activity data; identifying, at the server, an ECU software update based on the determined software vulnerability; and sending, from the server, a delta file configured to update software on the ECU with a software update corresponding to the identified ECU software update.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

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 providing software changes, comprising:
identifying a software vulnerability of a controller, wherein:
the software vulnerability is identified based on a deviation of first activity data from an allowed envelope of at least one operational attribute; and
the allowed envelope is based on second activity data received from a plurality of controllers;
determining a controller software change based on the identified software vulnerability, the controller software change being configured to adjust the controller from executing a first version of controller software to a second version of controller software; and
sending, to the controller and based on the determining, a delta file configured to execute the controller software change on the controller to link execution of current code stored on the controller with execution of a segment of code from the delta file.

### Claim 22 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the linked execution of the current code and the segment of code from the delta file form a functional equivalent of a software update that is operable prior to rebooting the controller.

### Claim 23 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the delta file comprises position-independent code or is multidimensional.

### Claim 24 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the operational attribute is associated with processor activity or memory content.

### Claim 25 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the allowed envelope comprises a threshold number of executions of a function within a time interval.

### Claim 26 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the second version of controller software was deployed prior to the first version of controller software.

### Claim 27 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the controller is a first controller of a first device and the operations further comprise:
determining a second controller of a second device; and
sending a second delta file to the second controller, the second delta file corresponding to the delta file.

### Claim 28 (depends on 27)

The non-transitory computer readable medium of claim 27, wherein the first controller is monitored as part of a first group and the second controller is monitored as part of a second group.

### Claim 29 (depends on 28)

The non-transitory computer readable medium of claim 28, the operations further comprising identifying the second controller to be similar to the first controller, wherein the delta file is sent to the second controller based on the identified similarity.

### Claim 30 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the allowed envelope is based on a statistical model based on at least one of: an amount of processor usage, an amount of memory usage, a memory sequence accessed, cache content history, cache access history, a page fault, a correlation of processes at a footprint of memory at a discrete time slice, a frequency of an execution, an execution path, or an on-board diagnostic (OBD) message.

### Claim 31 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the second version of controller software is the first version of controller software having one or more functional units disabled.

### Claim 32 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the delta file is configured to update a program counter of the controller to execute an instruction from the delta file without erasing existing content of a memory component of the controller.

### Claim 33 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the delta file is configured to extract code for updating memory addresses in the controller and update the memory addresses in the controller.

### Claim 34 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the delta file is further configured to cause the first version of controller software on the controller to become non-executable.

### Claim 35 (depends on 21)

The non-transitory computer readable medium of claim 21, the operations further comprising determining the first version of controller software by examining a record of a software version previously deployed to the controller.

### Claim 36

A method for performing operations for automatically providing software changes, the method comprising:
identifying a software vulnerability of a controller, wherein:
the software vulnerability is identified based on a deviation of activity data from an allowed envelope of at least one operational attribute; and
the allowed envelope is based on activity data received from a plurality of controllers;
determining a controller software change based on the identified software vulnerability, the controller software change being configured to adjust the controller from executing a first version of controller software to a second version of controller software; and
sending, to the controller and based on the determining, a delta file configured to execute the controller software change on the controller to link execution of current code stored on the controller with execution of a segment of code from the delta file.

### Claim 37 (depends on 36)

The method of claim 36, wherein the linked execution of the current code and the segment of code from the delta file form a functional equivalent of a software update that is functioning prior to rebooting the controller.

### Claim 38 (depends on 36)

The method of claim 36 further comprising:
comparing attributes of the first version of controller software to attributes of the second version of controller software to determine differences between the first version of controller software and the second version of controller software; and
generating the delta file representing the determined differences.

### Claim 39 (depends on 36)

The method of claim 36, wherein the software vulnerability is identified based on a deviation of activity data of the controller from an allowed envelope of at least one operational attribute.

### Claim 40 (depends on 39)

The method of claim 39, wherein the at least one operational attribute is associated with processor activity or memory contents.
