# US 2021/0334199 A1 · Generating and signing a line-of-code behavior and relation model

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

- Number: US 2021/0334199 A1
- Document ID: US20210334199A1
- Status: Published application
- Kind: A1
- Application number: 17/369,039
- Filed: 2021-07-07
- Published: 2021-10-28
- Earliest claimed: 2019-03-25
- Assignees: Aurora Labs Ltd.
- Applicants: Aurora Labs Ltd.
- Inventors: Zohar Fox; Carmit Sahar
- Web page: https://patentgrep.com/patent/US20210334199A1

## CPC

- G06F 30/33: Design verification, e.g. functional simulation or model checking
- G06F 8/34: Graphical or visual programming
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 8/73: Program documentation
- G06F 8/75: Structural analysis for program understanding
- G06F 11/3604: Analysis of software for verifying properties of programs (testing of software G06F11/3668)
- G06F 11/3612: {by runtime analysis (performance monitoring G06F11/3466)}
- G06F 11/362: Debugging of software
- G06F 11/3692: {for test results analysis}
- G06F 16/9014: {hash tables}
- G06F 17/18: for evaluating statistical data {, e.g. average values, frequency distributions, probability functions, regression analysis (forecasting specially adapted for a specific administrative, business or logistic context G06Q10/04)}
- G06F 18/24: Classification techniques
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 21/563: {by source code analysis}
- 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/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06N 20/00: Machine learning
- H04L 9/3247: {involving digital signatures}
- G06F 30/15: Vehicle, aircraft or watercraft design
- G10H 1/0058: {Transmission between separate instruments or between individual components of a musical system (G10H1/0083 takes precedence)}
- H04L 2209/84: Vehicles
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G10H: ELECTROPHONIC MUSICAL INSTRUMENTS; INSTRUMENTS IN WHICH THE TONES ARE GENERATED BY ELECTROMECHANICAL MEANS OR ELECTRONIC GENERATORS, OR IN WHICH THE TONES ARE SYNTHESISED FROM A DATA STORE

## Abstract

Disclosed herein are techniques for generating and signing line-of-code behavior and relation models. Techniques include identifying executable code for a controller; performing a functional analysis of the executable code to determine a plurality of functions associated with the executable code and a plurality of relationships between the plurality of functions; generating, based on the determined plurality of functions and plurality of relationships, a line-of-code behavior and relation model for the executable code; performing a signature operation on the generated line-of-code behavior and relation model to produce a unique signature value associated with at least one of: the line-of-code behavior and relation model or a functional block of the line-of-code behavior and relation model; and linking the unique signature value to the line-of-code behavior and relation model.

## 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 steps for generating and signing a line-of-code behavior and relation model, comprising:
performing a functional analysis of controller code to determine a plurality of functions associated with the controller code and a plurality of relationships between the functions, the controller code being represented by a delta file and configured to change software on a controller;
generating, based on the determined functions and relationships, a line-of-code behavior and relation model for the controller code;
performing a signature operation on the generated line-of-code behavior and relation model to produce a unique signature value identifying the line-of-code behavior and relation model; and
linking the unique signature value to the line-of-code behavior and relation model.

### Claim 22 (depends on 21)

The non-transitory computer-readable medium of claim 21, the steps further comprising linking the unique signature value to the delta file.

### Claim 23 (depends on 21)

The non-transitory computer-readable medium of claim 21, further comprising compressing the line-of-code behavior and relation model.

### Claim 24 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein generating the line-of-code behavior and relation model is based on at least one of: a machine learning process, a statistical process, or a dynamic analysis process.

### Claim 25 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein:
the steps further comprise determining a sequence of functions associated with a segment of the controller code; and
the line-of-code behavior and relation model is based on the determined sequence of functions.

### Claim 26 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein performing the functional analysis of the controller code comprising parsing the controller code for a known segment.

### Claim 27 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the line-of-code behavior and relation model is configured for application of real-time or simulated controller operations to the line-of-code behavior and relation model to demonstrate a function of the controller code.

### Claim 28 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein linking the unique signature value to the line-of-code behavior and relation model comprises associating the unique signature value with an identifier of the line-of-code behavior and relation model in a table.

### Claim 29 (depends on 28)

The non-transitory computer-readable medium of claim 28, wherein the identifier comprises a nonce.

### Claim 30 (depends on 29)

The non-transitory computer-readable medium of claim 29, wherein the unique signature value comprises a hash value.

### Claim 31 (depends on 28)

The non-transitory computer-readable medium of claim 28, the steps further comprising associating a predecessor signature value with the unique signature value or the line-of-code behavior and relation model.

### Claim 32 (depends on 31)

The non-transitory computer-readable medium of claim 31, the predecessor signature value being generated for another line-of-code behavior and relation model prior to the unique signature value.

### Claim 33 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein linking the unique signature value to the line-of-code behavior and relation model comprises generating a file including both the unique signature value and line-of-code behavior and relation model.

### Claim 34 (depends on 21)

The non-transitory computer readable medium of claim 21, the line-of-code behavior and relation model comprising a functional block describing a functional profile of a segment of the controller code.

### Claim 35 (depends on 34)

The non-transitory computer readable medium of claim 34, wherein the functional profile is developed through at least one of a user input or machine-observed behavior.

### Claim 36

A computer-implemented method for generating and signing a line-of-code behavior and relation model, the method comprising:
performing a functional analysis of controller code to determine a plurality of functions associated with the controller code and a plurality of relationships between the functions, the controller code being represented by a delta file and configured to change software on a controller;
generating, based on the determined functions and relationships, a line-of-code behavior and relation model for the controller code;
performing a signature operation on the generated line-of-code behavior and relation model to produce a unique signature value identifying the line-of-code behavior and relation model; and
linking the unique signature value to the line-of-code behavior and relation model.

### Claim 37 (depends on 36)

The computer-implemented method of claim 36, further comprising assigning the unique signature value to the delta file.

### Claim 38 (depends on 36)

The computer-implemented method of claim 36, wherein generating the line-of-code behavior and relation model is based on at least one of: a machine learning process, a statistical process, or a dynamic analysis process.

### Claim 39 (depends on 36)

The computer-implemented method of claim 36, wherein:
the steps further comprise determining a sequence of functions associated with a segment of the controller code; and
the line-of-code behavior and relation model is based on the determined sequence of functions.

### Claim 40 (depends on 36)

The computer-implemented method of claim 36, wherein the line-of-code behavior and relation model is configured for application of real-time or simulated controller operations to the line-of-code behavior and relation model to demonstrate a function of the controller code.
