Aurora Labs Ltd.

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; configuring model input data for a code language processing model, the model input data comprising the plurality of tokens; and analyzing at least a part of the body of programming code using the code language processing model influenced by the model input data.

Disclosed herein are techniques for detecting anomalous computing environment behavior. Techniques include fusing computer code parameters with hardware performance data associated with at least one device to form a kernel, the computer code parameters being associated with computer code configured for the at least one device; inputting the kernel to a trained model configured to detect execution performance anomalies of the at least one device, the trained model having been trained with a plurality of reference data patterns; and receiving, from the trained model, a detection output based on the kernel, the detection output indicating an anomalous behavior.

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.

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.

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.

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.

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.

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.

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.

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.