US 11,960,807 B2
Proving whether software functionality has changed following a software change
Zohar Fox, Tel Aviv (IL); and Carmit Sahar, Tel Aviv (IL)
Assigned to Aurora Labs Ltd., Tel Aviv (IL)
Filed by Aurora Labs Ltd., Tel Aviv (IL)
Filed on Sep. 6, 2022, as Appl. No. 17/929,792.
Application 17/929,792 is a continuation of application No. 17/366,495, filed on Jul. 2, 2021, granted, now 11,467,953.
Application 17/366,495 is a continuation of application No. 16/828,679, filed on Mar. 24, 2020, granted, now 11,086,769, issued on Aug. 10, 2021.
Claims priority of provisional application 62/823,131, filed on Mar. 25, 2019.
Prior Publication US 2022/0414000 A1, Dec. 29, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 30/33 (2020.01); G06F 8/34 (2018.01); G06F 8/65 (2018.01); G06F 8/71 (2018.01); G06F 8/75 (2018.01); G06F 11/36 (2006.01); G06F 16/901 (2019.01); G06F 17/18 (2006.01); G06F 18/24 (2023.01); G06F 21/52 (2013.01); G06F 21/56 (2013.01); G06F 21/57 (2013.01); G06F 21/62 (2013.01); G06N 20/00 (2019.01); G06F 30/15 (2020.01); G10H 1/00 (2006.01)
CPC G06F 30/33 (2020.01) [G06F 8/34 (2013.01); G06F 8/65 (2013.01); G06F 8/71 (2013.01); G06F 8/75 (2013.01); G06F 11/3604 (2013.01); G06F 11/3612 (2013.01); G06F 11/362 (2013.01); G06F 11/3692 (2013.01); G06F 16/9014 (2019.01); G06F 17/18 (2013.01); G06F 18/24 (2023.01); G06F 21/52 (2013.01); G06F 21/563 (2013.01); G06F 21/57 (2013.01); G06F 21/6218 (2013.01); G06N 20/00 (2019.01); G06F 30/15 (2020.01); G10H 1/0058 (2013.01)] 18 Claims
OG exemplary drawing
 
1. 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 associated with a first version of software for a controller and a second portion of executable code based on a delta file configured to change software on the controller to a second version;
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 based on the delta file configured to change the software on the controller;
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; and
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.