Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.
1.2Independent electrical state sensing
What ifWhat if the control unit obtains ECU state data from independent electrical monitors?
Claim language“from the in-vehicle ECUs”
Separate monitor circuits measure the current on each ECU supply branch and the voltage across each branch fuse. The circuits send measurements on a diagnostic link, and the control unit flags a power loss when both readings match a stored fault pattern.
1.3Mechanical brake fallback
What ifWhat if a mechanical hydraulic path provides braking when the electronic brake ECU fails?
Claim language“specifies a redundant ECU”
A watchdog relay drops power to a spring-return valve when the brake ECU misses its watchdog deadline. The valve connects the pedal-driven master cylinder to the wheel circuits so pedal force generates brake pressure.
1.6Capacity by processor time
What ifWhat if the control unit measures substitution capacity as available processor time in each scheduling cycle?
Claim language“the number of the in-vehicle ECUs”
Each backup reports its unallocated processor time in microseconds per scheduling cycle. The control unit compares that value with the failed task's worst-case execution time per cycle and admits backups with enough time to run it.
1.7Highest capacity selection
What ifWhat if the control unit selects the eligible backup with the highest substitution capacity?
Claim language“with the lowest substitution capacity”
A configuration table lists the number of function types each backup supports. The control unit filters for backups that are healthy and support the failed function, then selects the one with the highest count and breaks ties by ECU address.
Section 2 · machine-generated
Variations
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
Component substitution
Hardware state machine for controller takeover
A field-programmable gate array state machine implements the supervisory control unit in place of a general-purpose processor. A vehicle bus interface delivers heartbeat counters and health flags to input registers, and each standby advertises a supported function bit mask. The state machine detects missing heartbeats, filters ready standbys by the required function mask, and selects the candidate with the lowest population count in its mask. It issues a takeover command and grants actuator output access after the selected standby acknowledges readiness.
Parameter or scale variation
Timed takeover across twelve vehicle controllers
A supervisory unit monitors twelve vehicle controllers and three standbys, with each unit transmitting a sequenced heartbeat every 20 milliseconds. A 60-millisecond timer resets on each new heartbeat, and expiration marks the corresponding controller unavailable. The three standbys support two, four, and eight service types respectively, and the supervisor selects the ready standby with the smallest count that supports every service required by the failed controller. The supervisor transfers output authority only after the selected standby acknowledges readiness within 20 milliseconds and keeps the affected outputs inhibited if that interval expires.
Combination with existing systems
Controller takeover with hardware output interlocks
A vehicle supervisor connects to a hardware interlock that gates the actuator command outputs of the primary and standby controllers. The supervisor monitors controller health messages and selects the ready standby that supports the affected function and has the lowest supported function count. It commands the interlock to disable the primary output and checks the interlock feedback before sending the takeover command. The interlock enables the selected standby output after receiving the supervisor's enable signal and the standby's ready signal.
Automated or data-driven variant
Sensor residuals trigger controller takeover
A supervisory processor receives timestamped steering angle requests from the steering controller and angle readings from an independent position sensor. It compares measured angle with the expected response from a calibrated model indexed by vehicle speed and steering rate. If the residual exceeds its calibrated threshold for five consecutive samples during normal supply voltage, the supervisor marks the primary steering control path unhealthy and selects the ready steering-capable standby with the lowest supported function count. The supervisor inhibits the primary command source and grants authority to the standby after the standby initializes its control state from the measured angle.
Continuous state replication for controller takeover
Each primary controller periodically publishes a sequence-numbered state snapshot containing its active mode, setpoint, and controller integrator values. Compatible standbys validate snapshot checksums, retain the most recent snapshot for each supported function, and report snapshot age to the supervisor. After a primary fails a health check, the supervisor selects the standby with the lowest supported function count among ready candidates that hold a snapshot within the function's freshness limit. The selected standby loads the snapshot, updates its state from current sensor values, and starts issuing commands when the supervisor transfers output authority.
Specific version of a part
Backup output switching
Both ECUs continuously process the same sensor samples and send commands on separate channels to an actuator interface. When the primary fails, the control unit changes the interface's input selection bit while both ECUs retain their existing execution schedules.
Per ECU health tracking
A supervisory microcontroller maintains a health record for each ECU address. A periodic task advances each record through normal, suspect, and failed states using timeout counters and reset notifications.
Periodic ECU status frames
Each ECU transmits a status frame every 50 milliseconds with a rolling sequence number, a reset counter, and a self-test bit field. The control unit records the frame arrival time and stores the decoded fields by source address.
Standby task activation
The control unit sends the standby ECU an activation message containing a function identifier and the latest validated state checkpoint. After the standby acknowledges that the task is running, the control unit updates the receiving interface to accept its commands.
Lowest function count selection
Each candidate has a capability bitmap with one bit per supported function type. After filtering for healthy candidates that support the required function, the control unit counts the set bits in each remaining bitmap and selects the candidate with the smallest count.
Section 3 · quoted from USPTO records
Other work
Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.
1.1a control unit configured to perform processing related to state management of the in-vehicle ECUs,
1.2wherein the control unit acquires state data related to states of the in-vehicle ECUs from the in-vehicle ECUs,
1.3if it is determined based on the acquired state data that an in-vehicle ECU of the in-vehicle ECUs is not operating normally, the control unit specifies a redundant ECU to substitute for the in-vehicle ECU determined not to be operating normally,
1.4the control unit performs processing for causing the redundant ECU to substitute for the in-vehicle ECU determined not to be operating normally,
1.5if there are a plurality of candidates for the redundant ECU to substitute for the in-vehicle ECU determined not to be operating normally, the control unit specifies one of the redundant ECUs based on substitution capacities of the plurality of redundant ECUs that are candidates,
For example, with capacity-based spare device assignment algorithms, the largest capacity hard drives are typically chosen as spare devices because they can provide the best coverage for the remaining hard drives due to their eligibility to replace any smaller capacity hard drive.
A · US 2008/0126789 A1 · ¶ 14
In block 504, the spare assignment module 130 identifies one or more candidate devices having certain closest fitting characteristics of desired type (e.g., largest capacity X) in the spare coverage group and assigns these candidate devices to be spare devices to provide redundancy protection for the global sparing domain.
B · US 7,661,012 B2 · ¶ 37
1.6each of the substitution capacities corresponds to the number of the in-vehicle ECUs that can be substituted for by the corresponding redundant ECU, or the number of types of services or functions provided by the in-vehicle ECU that can be substituted for by the corresponding redundant ECU, and
1.7the control unit specifies a redundant ECU with the lowest substitution capacity among the plurality of redundant ECUs that are candidates.
An empty cell means only that no passage was reproduced there.
Statements in these documents
In order to enhance the availability and reliability of RAID storage systems, RAID technology allows additional hard drives to be set up as spare devices capable of replacing any failed hard drives within a RAID array in the event of hard drive failures.
A · US 2008/0126789 A1 · ¶ 5
The present disclosure describes a method for generating an optimal number of spare devices for a RAID storage system having an intermix of nearline-class drives and server class drives.
A · US 2008/0126789 A1 · ¶ 7
In RAID storage systems that use spare assignment optimization techniques, it is not possible to define specific characteristics to ensure adequate performance attributes during failure of hard disk devices and/or repair of hard disk devices.
B · US 7,661,012 B2 · ¶ 6
Although RAID storage systems are useful, there is a need in the art for improved spare device management.
B · US 7,661,012 B2 · ¶ 7
Cite aspatent.fyi, US 2026/0356379 A1, claim 1, first published 2026-11-20T00:27:46-05:00, https://patent.fyi/US20260356379/, SHA-256 065b53b4b3749329df9c88b76e0984057dae8d2bb0ae0a5406b7112bd93cb30b