# US 2023/0384750 A1 · Efficient controller data generation and extraction

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

- Number: US 2023/0384750 A1
- Document ID: US20230384750A1
- Status: Published application
- Kind: A1
- Application number: 18/330,806
- Filed: 2023-06-07
- Published: 2023-11-30
- Earliest claimed: 2020-06-29
- Assignees: Aurora Labs Ltd.
- Applicants: Aurora Labs Ltd.
- Inventors: Zohar Fox; Oren Sokoler; Kfir Ben Shimon
- Web page: https://patentgrep.com/patent/US20230384750A1

## CPC

- G05B 19/0426: {Programming the control sequence}
- G06F 8/658: Incremental updates; Differential updates
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G05B 2219/23301: Load program from file system of a controller
- G06F 8/63: {Image based installation; Cloning; Build to order}
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Disclosed herein are techniques for efficiently providing controller data as part of a maintenance or update process. Techniques include receiving, from a first remote computing device, a message associated with at least one controller extracting, based on the received message, an image of software associated with the at least one controller; accessing, based on the extracted image, a delta file; and transmitting the accessed delta file to a second remote computing device.

## 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 efficiently providing controller data as part of a maintenance or update process, the operations comprising:
receiving a delta file;
identifying one or more deltas from the delta file;
constructing a software image based on the identified one or more deltas; and
providing the software image to one or more controllers.

### Claim 22 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the delta file is received by a first device from a second device remote from the first device.

### Claim 23 (depends on 22)

The non-transitory computer-readable medium of claim 22, wherein the delta file is received in response to a request transmitted by the first device or a third device to the second device.

### Claim 24 (depends on 21)

The non-transitory computer-readable medium of claim 21, the operations further comprising, after receiving the delta file, verifying an authenticity of the delta file.

### Claim 25 (depends on 24)

The non-transitory computer-readable medium of claim 24, wherein verifying the authenticity of the delta file comprises validating a signature associated with a system from which the delta file was received.

### Claim 26 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein identifying the one or more deltas from the delta file comprises:
determining a file format of the delta file; and
parsing the delta file for the one or more deltas based on the determined file format.

### Claim 27 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein constructing the software image comprises modifying a stored software image based on changes represented by the one or more identified deltas.

### Claim 28 (depends on 27)

The non-transitory computer-readable medium of claim 27, wherein:
the operations further comprise accessing, by a device distinct from the one or more controllers, the stored software image; and
the stored software image is stored on at least one of the one or more controllers or a memory device accessible by the device distinct from the one or more controllers.

### Claim 29 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein constructing the software image comprises constructing a serialized image.

### Claim 30 (depends on 29)

The non-transitory computer-readable medium of claim 29, wherein the serialized image is configured to be deserialized by the one or more controllers.

### Claim 31 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein providing the software image to one or more controllers comprises flashing the software image to the one or more controllers.

### Claim 32 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the one or more controllers are identified as at least one of damaged, malfunctioning, having outdated software, or underperforming according to an operation criterion.

### Claim 33 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the delta file is generated by comparing two distinct software images.

### Claim 34

A method for efficiently providing controller data as part of a maintenance or update process, the method comprising:
receiving a delta file;
identifying one or more deltas from the delta file;
constructing a software image based on the identified one or more deltas; and
providing the software image to one or more controllers.

### Claim 35 (depends on 34)

The method of claim 34, wherein identifying the one or more deltas from the delta file comprises:
determining a file format of the delta file; and
parsing the delta file for the one or more deltas based on the determined file format.

### Claim 36 (depends on 34)

The method of claim 34, wherein constructing the software image comprises modifying a stored software image based on changes represented by the one or more identified deltas.

### Claim 37 (depends on 36)

The method of claim 36, wherein:
the method further comprises accessing, by a device distinct from the one or more controllers, the stored software image; and
the stored software image is stored on at least one of the one or more controllers or a memory device accessible by the device distinct from the one or more controllers.

### Claim 38 (depends on 34)

The method of claim 34, wherein providing the software image to one or more controllers comprises flashing the software image to the one or more controllers.

### Claim 39 (depends on 34)

The method of claim 34, wherein the one or more controllers are identified as at least one of damaged, malfunctioning, having outdated software, or underperforming according to an operation criterion.

### Claim 40 (depends on 34)

The method of claim 34, wherein the delta file is generated by comparing two distinct software images.
