IP Library › Granted Patent US 12,555,419
Granted Patent B2
US 12,555,419 · App. 17/865,030 · Granted Feb 17, 2026

Method for real-time ECU crash reporting and recovery

Inventors: Richard Edward Slindee (Gardena, CA); Shayan Mukhtar (Mississauga, CA)
Assignee: RIVIAN IP HOLDINGS, LLC
G07C5/0808G07C5/0816G07C5/085
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,555,419
App. No.
17/865,030
Granted
Feb 17, 2026
Kind
B2
Abstract

The present disclosure is directed to systems and methods directed to improving the functions of a vehicle. Systems and methods are provided that provide a custom tool that autogenerates a set of software agents that allows a system to separate processing, transmission and receiving of messages to achieve better synchronization. The disclosure herein also provides a simplified method of key provisioning by designating one client as a server and assigning a symmetric key to every other client permanently provisioned between that client and the server. Systems and method are further provided that predict faults in a vehicle. Systems and methods are also provided that preserve data in the event of a system crash. Systems and methods are also provided in which an operating system of a vehicle detects the presence of a new peripheral and pulls the related interface file for that new peripheral. Further, a data synchronization solution is provided herein which provides optimized levels of synchronization.

Claims (48)

1 . A method comprising:

generating, by processing circuitry, information comprising a snapshot of a state of software in a system at a time of a fault event,

causing, by the processing circuitry, the information to be stored in a portion of volatile memory of the system, wherein the portion of the volatile memory is configured to retain stored data during a reboot of an operating system of the system,

causing, using the processing circuitry, the operating system to be rebooted, and

after rebooting,

validating the information stored in the volatile memory based on integrity data stored in the portion of the volatile memory, and

causing the information to be stored in non-volatile memory of the system, in response to the validating.

2 . The method of claim 1 , further comprising:

generating the integrity data based on the information; and

causing the integrity data to be stored in the portion of the volatile memory.

3 . The method of claim 1 , wherein the volatile memory comprises random access memory (RAM).

4 . The method of claim 1 , wherein the portion of the volatile memory is a dedicated portion of the volatile memory reserved for the information.

5 . The method of claim 1 , further comprising detecting the fault event by detecting a system crash.

6 . The method of claim 1 , wherein generating the information and causing the information to be stored is performed by an emergency stack that is programmed to be executed in the event of the fault event.

7 . The method of claim 1 , wherein the system comprises a vehicle.

8 . A system comprising:

volatile memory,

non-volatile memory,

processing circuitry coupled to the volatile memory and to the non-volatile memory and configured to:

generate information comprising a snapshot of a state of software in the system at a time of a fault event,

cause the information to be stored in a portion of the volatile memory, wherein the portion of the volatile memory is configured to retain stored data during a reboot of an operating system of the system,

cause the operating system to be rebooted, and

after rebooting,

validate the information stored in the volatile memory based on integrity data stored in the portion of the volatile memory, and

cause the information to be stored in the non-volatile memory, in response to the validation.

9 . The system of claim 8 , wherein the processing circuitry is further configured to:

generate the integrity data based on the information; and

cause the integrity data to be stored data in the portion of the volatile memory.

10 . The system of claim 8 , wherein the volatile memory comprises random access memory (RAM).

11 . The system of claim 8 , wherein the portion of the volatile memory is a dedicated portion of the volatile memory reserved for the information.

12 . The system of claim 8 , wherein the processing circuitry is further configured to detect the fault event by detecting a system crash.

13 . The system of claim 8 , wherein to generate the information and cause the information to be stored is performed by an emergency stack that is programmed to be executed in the event of the fault event.

14 . The system of claim 8 further comprising a vehicle that comprises the volatile memory, the non-volatile memory, and the processing circuitry.

15 . A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor of a system, causes the processor to:

generate information comprising a snapshot of a state of software in the system at a time of a fault event,

cause the information to be stored in a portion of volatile memory of the system, wherein the portion of the volatile memory is configured to retain stored data during a reboot of an operating system of the system,

cause the operating system to be rebooted, and

after rebooting,

validate the information stored in the volatile memory based on integrity data stored in the portion of the volatile memory, and

cause the information to be stored in non-volatile memory of the system, in response to the validation.

16 . The computer-readable medium of claim 15 , wherein the instructions, when executed by the processor, further cause the processor to:

generate the integrity data based on the information; and

cause the integrity data to be stored in the portion of volatile memory.

17 . The computer-readable medium of claim 15 , wherein the volatile memory comprises random access memory (RAM).

18 . The computer-readable medium of claim 15 , wherein the portion of volatile memory is a dedicated portion of the volatile memory reserved for the information.

19 . The computer-readable medium of claim 15 , wherein the instructions, when executed by the processor, further cause the processor to detect the fault event by detecting a system crash.

20 . The computer-readable medium of claim 15 , wherein generating the information and causing the information to be stored is performed by an emergency stack that is programmed to be executed in the event of the fault event.

21 . The computer-readable medium of claim 15 , wherein the system comprises a vehicle.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 14, 2022
From: SLINDEE, RICHARD EDWARD; MUKHTAR, SHAYAN
To: RIVIAN AUTOMOTIVE, LLC
Reel/Frame 060509/0417 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 14, 2022
From: RIVIAN AUTOMOTIVE, LLC
To: RIVIAN IP HOLDINGS, LLC
Reel/Frame 060509/0431 →
Continuity (3)
Continuation 17567062 · Dec 31, 2021
Provisional Application 63240190 · Sep 2, 2021
Related Publication 20230071884A1 · Mar 9, 2023
References Cited (11)
US 6948098B2 · Pillay · 2005 [cited by examiner]
US 7716523B2 · Shah · 2010 [cited by examiner]
US 11188407B1 · Swanson et al. · 2021 [cited by applicant]
US 20120084496A1 · Rudelic · 2012 [cited by examiner]
US 20170277463A1 · Yoon · 2017 [cited by applicant]
US 20180239609A1 · Jang et al. · 2018 [cited by applicant]
US 20200156651A1 · Golov · 2020 [cited by applicant]
US 20210118054A1 · Turner et al. · 2021 [cited by applicant]
CN 207529370U · 2018 [cited by applicant]
CN 113302614A · 2021 [cited by applicant]
FR 3106677A1 · 2021 [cited by applicant]