Abstract: Disclosed embodiments relate to reporting Electronic Control Unit (ECU) errors or faults to a remote monitoring server. Operations may include receiving operational data from a plurality of ECUs in the vehicle, the operational data being indicative of a plurality of runtime attributes of the plurality of ECUs; generating, through a machine learning process, a statistical model of the operational data; receiving live, runtime updates from the plurality of ECUs in the communications network of the vehicle; identifying an ECU error associated with an ECU in the communications network of the vehicle, the ECU error being determined by a comparison of the live, runtime updates with the statistical model of the operational data to identify at least one deviation from the operational data; and wirelessly sending a report to the remote monitoring server based on the live, runtime updates, the report identifying the ECU and the identified ECU error.

Abstract: Disclosed embodiments relate to perform operations for receiving and integrating a delta file in a vehicle. Operations may include receiving, at an Electronic Control Unit (ECU) in the vehicle, a delta file, the delta file comprising a plurality of deltas corresponding to a software update for software on the ECU and startup code for executing the delta file in the ECU; executing the delta file, based on the startup code, in the ECU; and updating memory addresses in the ECU to correspond to the plurality of deltas from the delta file.

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.

Abstract: Disclosed herein are techniques for automatically reconfiguring code based on function and subfunction analysis. Techniques include determining, by parsing a code structure representing a plurality of functions, that at least one first function has a threshold degree of complexity; identifying, in response to the determination, a plurality of subfunctions based on the at least one first function, the plurality of subfunctions having a commonality with the at least one first function; and forming a second function by reconfiguring the first function to call at least one of the identified plurality of subfunctions.

Abstract: Disclosed embodiments relate to automatically providing updates to at least one vehicle. Operations may include receiving, at a server remote from the at least one vehicle, Electronic Control Unit (ECU) activity data from the at least one vehicle, the ECU activity data corresponding to actual operation of the ECU in the at least one vehicle; determining, at the server and based on the ECU activity data, a software vulnerability affecting the at least one vehicle, the software vulnerability being determined based on a deviation between the received ECU activity data and expected ECU activity data; identifying, at the server, an ECU software update based on the determined software vulnerability; and sending, from the server, a delta file configured to update software on the ECU with a software update corresponding to the identified ECU software update.

Abstract: Disclosed herein are techniques for improving data compression efficiency for RAM-restricted devices. Techniques include allocating a scratch buffer within a first memory space of a controller; storing a particular portion of a chunk of software change elements in the scratch buffer; flushing the particular portion of the chunk from the scratch buffer to a second memory space; storing at least one subsequent portion of the chunk in the scratch buffer; flushing the at least one subsequent portion of the chunk from the scratch buffer to a second memory space of the controller; and applying, using the flushed first and at least one subsequent portion of the chunk, the software change elements to the controller.

Abstract: Disclosed embodiments relate to identifying Electronic Control Unit (ECU) anomalies in a vehicle. Operations may include monitoring, in the vehicle, data representing real-time processing activity of the ECU; accessing, in the vehicle, historical data relating to processing activity of the ECU, the historical data representing expected processing activity of the ECU; comparing, in the vehicle, the real-time processing activity data with the historical data, to identify at least one anomaly in the real-time processing activity of the ECU; and implementing a control action for the ECU when the at least one anomaly is identified.

Abstract: Disclosed herein are techniques for training a model to predict data size. Techniques include initializing a model having model parameters; training the model to predict source code data size by: inputting first model input data to the model, the first model input data including a first set of source code parameters associated with a data size parameter associated with a first source code; and modifying at least one of the model parameters to improve prediction of source code data size by the model; and validating the model by inputting second model input data to the trained model, the second model input data including a second set of source code parameters associated with a data size parameter of a second source code.

Abstract: Disclosed herein are techniques for analyzing software build changes. Techniques include accessing first executable code associated with a first version; accessing second executable code associated with a second version; determining a code delta between the first executable code and the second executable code, the code delta being based on a change of at least one first element of code in the first executable code to at least one second element of code in the second executable code; determining a software vulnerability associated with at least one of the at least one first element of code or the at least one second element of code; and generating a report including a pairing of an indicator of the software vulnerability with an indicator of at least one of the at least one first element of code or the at least one second element of code.

Abstract: Disclosed herein are techniques for generating a linker script file. Techniques include accessing user definition code; accessing user configuration code; based on the user definition code and the user configuration code, identifying at least one linker script syntax; and generating a linker script file configured for generating executable code, the linker script file being based on the user definition code and the user configuration code.

Abstract: Disclosed herein are techniques for shrinking security patches. Techniques include accessing executable code; scanning the executable code for an indicator of 3rd-party code associated with a software vulnerability; identifying, based on the scanning, the indicator of 3rd-party code; determining, based on the scanning, that the executable code includes a local fix patching the software vulnerability or that the executable code is not configured to rely on the 3rd-party code; and based on the determination that the executable code includes a local fix patching the software vulnerability or that the executable code is not configured to rely on the 3rd-party code, performing at least one of: generating a security patch file that does not patch the software vulnerability; or removing, from a security patch file, a patch associated with the software vulnerability, thereby reducing a size of the security patch file.

Abstract: Disclosed herein are techniques for reducing processing load for software testing. Techniques include accessing code for testing; performing functional analysis of the code to construct a functional behavior representation of the code; determining, based on the functional behavior representation, a first testing interaction between a first test and the code; determining, based on the functional behavior representation, a second testing interaction between a second test and the code; determining that the first testing interaction is stronger than the second testing interaction; and based on the determination that the first testing interaction is stronger than the second testing interaction, applying the first test to the code.

Abstract: Disclosed herein are techniques for creating and using tokens representing portions of programming code. Techniques include identifying a first body of programming code associated with a hardware or software source attribute; associating a plurality of tokens with respective portions of the first body of programming code; configuring model input data for training a code language processing model customized in accordance with the hardware or software source attribute, the model input data comprising the plurality of tokens; and training, using the model input data, the code language processing model to analyze at least a part of the first body of programming code or a part of a second body of programming code, thus producing a customized and trained code language processing model in accordance with the hardware or software source attribute.

Abstract: Disclosed herein are techniques for creating and using tokens representing portions of programming code. Techniques include identifying a body of programming code; associating a plurality of tokens with respective portions of the body of programming code to generate a token-based representation of the body of programming code, wherein the associating comprises determining at least one canonical representation of at least one of the respective portions of the body of programming code; providing the token-based representation of the body of programming code to an emulator, the emulator being configured to interpret token-based representations; and receiving, from the emulator, an emulation result.

Abstract: Disclosed herein are techniques for training code language models. Techniques include making a plurality of programming code segments available to a code language processing model; providing an output of the code language processing model to one or more regression layers; determining, based on the one or more regression layers, a degree of functional similarity between two portions of the output; providing the degree of functional similarity to the code language processing model; and updating, based on the degree of functional similarity, the code language processing model.

Abstract: Disclosed herein are techniques for dynamically predicting resource usage for code changes. Techniques include identifying an element of programming code; identifying a programming code execution environment; accessing a code language processing model, wherein the code language processing model has been trained to associate programming code execution tasks with amounts of computing resource usage; and predicting, without requiring execution of the element of programming code, an amount of computing resource usage associated with an execution of the element of programming code in the programming code execution environment.

Abstract: Disclosed herein are techniques for analyzing control-flow integrity based on functional line-of-code behavior and relation models. Techniques include receiving data based on runtime operations of a controller; constructing a line-of-code behavior and relation model representing execution of functions on the controller based on the received data; constructing, based on the line-of-code behavioral and relation model, a dynamic control flow integrity model configured for the controller to enforce in real-time; and deploying the dynamic control flow integrity model to the controller.

Abstract: Disclosed embodiments relate to automatically providing updates to at least one vehicle. Operations may include receiving, at a server remote from the at least one vehicle, Electronic Control Unit (ECU) activity data from the at least one vehicle, the ECU activity data corresponding to actual operation of the ECU in the at least one vehicle; determining, at the server and based on the ECU activity data, a software vulnerability affecting the at least one vehicle, the software vulnerability being determined based on a deviation between the received ECU activity data and expected ECU activity data; identifying, at the server, an ECU software update based on the determined software vulnerability; and sending, from the server, a delta file configured to update software on the ECU with a software update corresponding to the identified ECU software update.

Abstract: Disclosed herein are techniques for reducing sizes of executable files. Techniques include identifying an executable file having a plurality of functions; determining, by parsing the executable file or a code structure representing the executable file, that a first and second function each comprise a common block; identifying a third function configured to perform the common block; changing the first and second functions by: removing the common block from at least one of the first or second functions; and inserting a call to the third function into at least one of the first or second functions; and updating the executable file by: replacing, in the executable file, at least one of the first or second functions with at least one of the updated first or second functions; and adding the third function to the executable file.

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.