Disclosed are systems and techniques for using blockchain technology to maintain and validate a vehicle ledger. The technique includes receiving, at a master node in the system, a request to update a vehicle ledger associated with a first vehicle node comprising the system. If first criteria are met, the system updates the vehicle ledger, including: generating an updated version of the vehicle ledger using vehicle data stored in a master ledger associated with the master node, and transmitting the updated version of the vehicle ledger to the first vehicle node. If the first criteria are not met, the system forgoes updating the vehicle ledger. The vehicle data corresponds to a first vehicle associated with the first vehicle node. The master ledger is implemented using a blockchain that contains vehicle records for vehicles associated with the system. The blockchain includes a first block including vehicle data corresponding to the first vehicle.

A vehicle control system includes a plurality of devices, a first device included in the devices including: a storage configured to store consistency information including a permitted combination of versions of software installed on each of one or more devices in association with each of the control functions; a determination unit configured to determine whether the consistency information consistent with versions of software installed on a part of the devices exists when consistency does not exist in the versions of all software installed on each of the devices; and a performance control unit configured to permit performance of a part of control functions associated with the consistency information consistent with the versions of software installed on the part of the devices when the consistency information consistent with the versions of software installed on the part of the devices exists.

A vehicle control system includes a plurality of devices, a first device included in the devices including: a storage configured to store consistency information including a permitted combination of versions of software installed on each of one or more devices in association with each of the control functions; a determination unit configured to determine whether the consistency information consistent with versions of software installed on a part of the devices exists when consistency does not exist in the versions of all software installed on each of the devices; and a performance control unit configured to permit performance of a part of control functions associated with the consistency information consistent with the versions of software installed on the part of the devices when the consistency information consistent with the versions of software installed on the part of the devices exists.

While a vehicle is in an off state, expiration of a timer and receipt of a first message from a user device are monitored. Upon determining that at least one of the timer has expired or that the first message is received from the user device, a communication network onboard the vehicle is then monitored for a specified set of fault conditions. Upon detecting, on the onboard vehicle communication network, a fault condition included in the set of fault conditions, the fault condition is then identified as one of transient or persistent. A user assist feature of the vehicle is disabled upon identifying that the fault condition is transient and that a second message was received from the user device after the fault condition was detected.

An engine electronic control unit (ECU) for a vehicle includes a non-volatile memory and a microcontroller. The non-volatile memory is configured to store an indicator of ignition status having an initial off-status. The microcontroller is coupled to the non-volatile memory and is configured to receive a SOC of a battery for the engine ECU. The microcontroller is further configured to determine the SOC is insufficient to power-up the engine ECU following a reset condition. The microcontroller is further configured to disable over-writing the indicator of ignition status in response to determining the SOC is insufficient.

While a vehicle is in an off state, expiration of a timer and receipt of a first message from a user device are monitored. Upon determining that at least one of the timer has expired or that the first message is received from the user device, a communication network onboard the vehicle is then monitored for a specified set of fault conditions. Upon detecting, on the onboard vehicle communication network, a fault condition included in the set of fault conditions, the fault condition is then identified as one of transient or persistent. A user assist feature of the vehicle is disabled upon identifying that the fault condition is transient and that a second message was received from the user device after the fault condition was detected.

A vehicle activation system is configured so that when a switch is turned on, current is passed from a backup power supply circuit to a signal circuit and electric power is supplied from the backup power supply circuit to a power supply relay. The vehicle activation system includes an interruption circuit which is capable of interrupting the supply of electric power from the backup power supply circuit to the power supply relay.

An engine electronic control unit (ECU) for a vehicle includes a non-volatile memory and a microcontroller. The non-volatile memory is configured to store an indicator of ignition status having an initial off-status. The microcontroller is coupled to the non-volatile memory and is configured to receive a SOC of a battery for the engine ECU. The microcontroller is further configured to determine the SOC is insufficient to power-up the engine ECU following a reset condition. The microcontroller is further configured to disable over-writing the indicator of ignition status in response to determining the SOC is insufficient.

Disclosed are systems and techniques for using blockchain technology to maintain and validate a vehicle ledger. The technique includes receiving, at a master node in the system, a request to update a vehicle ledger associated with a first vehicle node comprising the system. If first criteria are met, the system updates the vehicle ledger, including: generating an updated version of the vehicle ledger using vehicle data stored in a master ledger associated with the master node, and transmitting the updated version of the vehicle ledger to the first vehicle node. If the first criteria are not met, the system forgoes updating the vehicle ledger. The vehicle data corresponds to a first vehicle associated with the first vehicle node. The master ledger is implemented using a blockchain that contains vehicle records for vehicles associated with the system. The blockchain includes a first block including vehicle data corresponding to the first vehicle.

A vehicle control system includes a plurality of devices, a first device included in the devices including: a storage configured to store consistency information including a permitted combination of versions of software installed on each of one or more devices in association with each of the control functions; a determination unit configured to determine whether the consistency information consistent with versions of software installed on a part of the devices exists when consistency does not exist in the versions of all software installed on each of the devices; and a performance control unit configured to permit performance of a part of control functions associated with the consistency information consistent with the versions of software installed on the part of the devices when the consistency information consistent with the versions of software installed on the part of the devices exists.