# US 2024/0004779 A1 · Framework for distributed open-loop vehicle simulation

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

- Number: US 2024/0004779 A1
- Document ID: US20240004779A1
- Status: Published application
- Kind: A1
- Application number: 17/853,326
- Filed: 2022-06-29
- Published: 2024-01-04
- Earliest claimed: 2022-06-29
- Assignees: Embark Trucks Inc.
- Applicants: Embark Trucks, Inc.
- Inventors: Liam BENSON; Konstantine MUSHEGIAN
- Web page: https://patentgrep.com/patent/US20240004779A1

## CPC

- G06F 11/3624: {by performing operations on the source code, e.g. via a compiler}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 11/3684: {for test design, e.g. generating new test cases}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Provided is a system and method that provides an open-loop simulation system for testing self-driving software for autonomous vehicles. As self-driving code is updated, a developer may test the self-driving code against previously-captured driving data captured while on the road. In one example, the method may include receiving a request to simulate self-driving code against previously-captured driving data via a host platform, dividing the driving data into a plurality of data chunks, compressing the self-driving code to create compressed self-driving code, generating a plurality of simulation tasks for testing the self-driving code based on the plurality of driving data chunks, respectively, executing the plurality of simulation tasks in parallel via a plurality of workers of the host platform, respectively, and storing execution results of the plurality of simulation tasks via a memory.

## Claims

### Claim 1

An apparatus comprising:
a network interface configured to receive a request to execute a simulation of self-driving code against previously-captured driving data via a host platform; and
a processor configured to
slice the driving data into a plurality of data segments that comprise driving data from a plurality of mutually exclusive intervals of driving time, respectively, from among a total driving time of the driving data;
identify a software program to be tested within the self-driving code based on a file included within the self-driving code;
generate a plurality of simulation tasks for testing the self-driving code based on the plurality of data segments, wherein each simulation task includes the software program to be tested and a different data segment from among the plurality of data segments with driving data from a different mutually-exclusive interval of driving time, respectively;
execute the plurality of simulation tasks on the plurality of data segments in parallel, to test the software program on the driving data as a whole; and
store execution results of the plurality of simulation tasks via a data store.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the processor is configured to identify one or more executables that are to be executed during the simulation from a launch file used to launch software processes included in the self-driving code.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the processor is configured to receive the driving data over a computer network, and store the received driving data in a plurality of files corresponding to the plurality of mutually-exclusive intervals of driving time.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein the processor is configured to break-up the driving data into a plurality of data chunks that each include a same amount of time of driving data.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the processor is configured to remove the plurality of simulation tasks from a queue and assign the plurality of simulation tasks to a plurality of workers based on predefined instructions within a script.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the self-driving code comprises an update to a previously-created self-driving code previously stored on a vehicle, and the driving data is captured from a previous run of the vehicle.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the processor is further configured to spawn a plurality of workers, compile the software program into a binary file, and execute the binary file on each of the plurality of workers.

### Claim 8 (depends on 7)

The apparatus of claim 7, wherein the processor is configured to assign each data segment from among the plurality of data segments to a different worker from among the plurality of workers, respectively, such that each worker executes a different interval of driving time data.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the driving data comprises sensor data captured and recorded by a vehicle, decisions made by an autonomous vehicle (AV) system of the vehicle, and planning data created by the AV system of the vehicle.

### Claim 10

A method comprising:
receiving a request to simulate self-driving code against previously-captured driving data via a host platform;
slicing the driving data into a plurality of data segments that comprise driving data from a plurality of mutually-exclusive intervals of driving time, respectively, from among a total driving time of the driving data;
identifying a software program to be tested within the self-driving code based on a file included within the self-driving code;
generating a plurality of simulation tasks for testing the self-driving code based on the plurality of data segments, wherein each simulation task includes the software program to be tested and a different data segment from among the plurality of data segments with driving data from a different mutually-exclusive interval of driving time, respectively;
executing the plurality of simulation tasks on the plurality of data segments in parallel to test the software program on the driving data as a whole; and
storing execution results of the plurality of simulation tasks via a data store.

### Claim 11 (depends on 10)

The method of claim 10, wherein the identifying comprises identifying one or more executables that are to be executed during the simulation from a launch file used to launch software processes included in the self-driving code.

### Claim 12 (depends on 10)

The method of claim 10, wherein the receiving comprises receiving the driving data over a computer network from a vehicle on a road, and storing the received driving data in a plurality of files corresponding to the plurality of mutually-exclusive intervals of driving time.

### Claim 13 (depends on 12)

The method of claim 12, wherein the dividing comprises breaking-up the driving data into a plurality of data chunks that each include a same amount of time of driving data.

### Claim 14 (depends on 10)

The method of claim 10, wherein the method further comprises removing the plurality of simulation tasks from a queue and assigning the plurality of simulation tasks to a plurality of workers based on predefined instructions within a script.

### Claim 15 (depends on 10)

The method of claim 10, wherein the self-driving code comprises an update to a previously-created self-driving code previously stored on a vehicle, and the driving data is captured from a previous run of the vehicle.

### Claim 16 (depends on 10)

The method of claim 10, wherein the method further comprises spawning a plurality of workers, compiling the software program into an executable file, and executing the executable file on each of the plurality of workers.

### Claim 17 (depends on 16)

The method of claim 16, wherein the executing comprises assigning each data segment from among the plurality of data segments to a different worker from among the plurality of workers, respectively, such that each worker executes a different interval of driving time data.

### Claim 18 (depends on 10)

The method of claim 10, wherein the driving data comprises sensor data captured and recorded by a vehicle, decisions made by an autonomous vehicle (AV) system of the vehicle, and planning data created by the AV system of the vehicle.

### Claim 19

A non-transitory computer-readable medium comprising instructions which when executed by a processor cause a computer to perform a method comprising:
receiving a request to simulate self-driving code against previously-captured driving data via a host platform;
slicing the driving data into a plurality of data segments that comprise driving data from a plurality of mutually-exclusive intervals of driving time, respectively, from among a total driving time of the driving data;
identifying a software program to be tested within the self-driving code based on a file included within the self-driving code;
generating a plurality of simulation tasks for testing the compressed self-driving code based on the plurality of data segments, wherein each simulation task includes the software program to be tested and a different data segment from among the plurality of data segments with driving data from a different mutually-exclusive interval of driving time, respectively;
executing the plurality of simulation tasks on the plurality of data segments in parallel to test the software program on the driving data as a whole; and
storing execution results of the plurality of simulation tasks via a data store.

### Claim 20 (depends on 19)

The non-transitory computer-readable medium of claim 19, wherein the slicing comprises slicing the driving data into a plurality of data chunks that each include a predefined amount of driving time from the driving data.
