# US 2021/0334198 A1 · Proving whether software functionality has changed following a software change

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

- Number: US 2021/0334198 A1
- Document ID: US20210334198A1
- Status: Published application
- Kind: A1
- Application number: 17/366,495
- Filed: 2021-07-02
- 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/US20210334198A1

## 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 using a line-of-code behavior and relation model to determine software functionality changes. Techniques include identifying a first portion of executable code and a second portion of executable code; accessing a first line-of-code behavior and relation model representing execution of functions of the first portion of executable code; constructing, based on the second portion of executable code, a second line-of-code behavior and relation model representing execution of functions of the second portion of executable code; performing a functional differential comparison of the first line-of-code behavior and relation model to the second line-of-code behavior and relation model; determining, based on the functional differential comparison, a status of functional equivalence between the first portion of executable code and the code portion of executable code; and generating, based on the determined difference, a report identifying the status of functional equivalence.

## 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 using a line-of-code behavior and relation model to determine software functionality changes, comprising:
identifying a first portion of executable code and a second portion of executable code;
accessing a first line-of-code behavior and relation model modeling first symbols and first symbol relationships of the first portion of executable code;
accessing a second line-of-code behavior and relation model modeling second symbols and second symbol relationships of the second portion of executable code;
performing a functional differential comparison of the first line-of-code behavior and relation model to the second line-of-code behavior and relation model, wherein performing the functional differential comparison comprises determining functional effects of the first and second portions of executable code;
determining, based on the functional differential comparison, a status of functional equivalence between the first portion of executable code and the second portion of executable code, wherein the status of functional equivalence is based on multiple determinations of equivalence between portions of the first and second line-of-code behavior and relation models; and
generating a report identifying the status of functional equivalence.

### Claim 22 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein accessing the second line-of-code behavior and relation model comprises constructing the second line-of-code behavior and relation model based on the second portion of executable code.

### Claim 23 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the operations further comprise linking at least one function of the second portion of executable code to at least a segment of the second portion of executable code.

### Claim 24 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second line-of-code behavior and relation models models execution of the first or second portion of executable code on a virtualized or physical controller.

### Claim 25 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second symbols represents at least one of: a variable, a buffer, a function, a call, an object, a segment of code, or a controller.

### Claim 26 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the at least the first or second portions of executable code is associated with a delta file executable on a controller.

### Claim 27 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second symbols comprises a functional block describing a functional profile of a segment of code.

### Claim 28 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second symbol relationships represents an interdependency or dependency between two of the first or second symbols.

### Claim 29 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the line-of-code behavior and relation model is stochastic or deterministic.

### Claim 30 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least the first or second line-of-code behavior and relation model is based on data of real-time controller operations or historical controller operations.

### Claim 31 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second line-of-code behavior and relation models models execution of the first or second portion of executable code on a personal computing device.

### Claim 32 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the second portion of executable code is configured to change code on a device having the first portion of executable code.

### Claim 33 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second line of code behavior and relation models are generated according to a machine learning process.

### Claim 34 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the status of functional equivalence includes a degree of equivalence.

### Claim 35 (depends on 34)

The non-transitory computer-readable medium of claim 34, the operations further comprising:
determining that the degree of equivalence does not reach a threshold; and
based on determining that the degree of equivalence does not reach the threshold, generating a prompt.

### Claim 36 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein the functional differential comparison is based on at least one of a difference of: response time, sequence of function execution, or memory leakage.

### Claim 37 (depends on 21)

The non-transitory computer-readable medium of claim 21, wherein at least one of the first or second line-of-code behavior and relation model was generated statically or dynamically.

### Claim 38 (depends on 21)

The non-transitory computer readable medium of claim 21, wherein the report further identifies at least one instance of functionality drift.

### Claim 39

A computer-implemented method for using a line-of-code behavior and relation model to determine software functionality changes, the method comprising:
identifying a first portion of executable code and a second portion of executable code;
accessing a first line-of-code behavior and relation model modeling first symbols and first symbol relationships of the first portion of executable code;
accessing a second line-of-code behavior and relation model modeling second symbols and second symbol relationships of the second portion of executable code;
performing a functional differential comparison of the first line-of-code behavior and relation model to the second line-of-code behavior and relation model, wherein performing the functional differential comparison comprises determining functional effects of the first and second portions of executable code;
determining, based on the functional differential comparison, a status of functional equivalence between the first portion of executable code and the second portion of executable code, wherein the status of functional equivalence is based on multiple determinations of equivalence between portions of the first and second line-of-code behavior and relation models; and
generating a report identifying the status of functional equivalence.

### Claim 40 (depends on 39)

The computer-implemented method of claim 39, the method further comprising linking at least one function of the second portion of executable code to at least a segment of the second portion of executable code.
