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.1Direct receiver status contacts
What ifWhat if the collection unit read train and wayside status through dedicated electrical inputs?
Claim language“a network isolation device”
Train equipment presents selected states on relay contacts, and an onboard receiver decodes wayside messages from track loops into discrete outputs. The collection unit samples these inputs and timestamps each state change.
1.3Fault lookup by signature code
What ifWhat if the analysis unit used one subsystem diagnostic code per incident to locate the fault and identify its cause and operational impact?
Claim language“fusion analysis of collected and processed data”
A subsystem controller runs a built-in test and sends a diagnostic code that encodes the affected module and failure mode. The analysis unit uses the code as the sole key into a table that returns the module location, diagnosed cause and affected train functions.
1.4Fixed onboard assistance terminal
What ifWhat if on-duty personnel used a terminal bolted to an onboard equipment cabinet?
Claim language“a portable on-duty unit”
A wired connection carries live alarms and train status to the cabinet terminal. Personnel select a fault code on the touchscreen to display the corresponding troubleshooting procedure.
1.5Client polled status updates
What ifWhat if the portable unit requested fault and operation updates once per second?
Claim language“push the key fault and the operation information”
The portable unit sends its last received sequence number with each request over the cellular link. The train server responds with newer fault events and changed train and station status records.
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.
Other field of use
Monitoring autonomous warehouse transport vehicles
A warehouse monitoring gateway collects vehicle position and drive status together with fixed door states and aisle occupancy through an isolated telemetry interface. A processor maps the records to common timestamps, vehicle identifiers, and zone identifiers, then writes them to a real-time database. An analysis service correlates stopped vehicles with blocked zones, identifies queued vehicles that share the affected route, and pushes the findings and inspection guidance to a supervisor’s handheld device over a private cellular link.
Component substitution
Optical data diode for collection
An optical data diode replaces the network isolation device between a telemetry concentrator and the train data processor. The concentrator packages train and wayside samples with source identifiers, timestamps, and sequence numbers and sends them through the diode to a receiving gateway. The gateway checks sequence continuity, marks stale sources, and passes the received records to the processor for normalization and alarm generation.
Parameter or scale variation
Fleet monitoring with two sampling rates
An operations server receives telemetry from 40 trains across two lines and stores the records by train identifier and timestamp. Onboard collectors sample routine status at 1 hertz and retain 30 seconds of selected diagnostic signals sampled at 10 hertz in a rolling buffer. When a fault occurs, the onboard collector sends the alarm immediately and uploads the buffered samples separately, while the operations server pushes the fault summary to the handheld assigned to that train.
Combination with existing systems
Fault alerts linked to maintenance records
The train analysis service connects to a computerized maintenance management system through a gateway on the operations network. The gateway maps the train and subsystem identifiers in each confirmed fault to an asset record and retrieves open work orders and the current inspection procedure. The handheld presents those references alongside the live fault location, affected functions, and troubleshooting guidance.
Automated or data-driven variant
Software correlation of recurring fault patterns
A rules engine reads normalized train and wayside events from the real-time database and groups them by train identifier, route segment, and a 10-second time window. Each rule specifies required event types, their order, and the maximum interval between them. A matching sequence produces a diagnostic record with the inferred fault location, likely cause, affected functions, and supporting event timestamps, which the server pushes to the handheld with an inspection checklist.
Temperature monitoring for onboard equipment cabinets
Temperature sensors at the air inlet and outlet of an onboard equipment cabinet report measurements alongside the cooling fan speed and commanded state. The analysis service compares the inlet-to-outlet temperature difference with a stored range for the current inlet temperature and fan speed. A sustained temperature deviation with the fan running triggers an airflow inspection alert, while a sustained low fan speed under a run command triggers a fan inspection alert on the handheld.
Specific version of a part
Subsystem generated fault alarms
Each subsystem controller evaluates its own signals and emits an alarm record with a fault code and timestamp when a local condition persists beyond a configured interval. The processing unit normalizes and forwards those records while processing status samples separately.
One way optical gateway
A source gateway collects train and wayside records, then transmits framed telemetry over a fiber strand with a transmitter at the source and a receiver at the collection unit. The receiver checks frame checksums and flags sequence gaps.
Time aligned traction diagnostics
The analysis unit aligns raw traction controller events with processed current and speed readings in a one-second window. It correlates a converter trip with current loss at the associated bogie and uses the remaining enabled drives to determine available traction capacity.
Handheld fault procedure display
A battery-powered handheld displays incoming alarms with the car number, subsystem and timestamp. Personnel tap an alarm to open its locally stored procedure and query the current equipment status.
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 train data collection unit configured to collect fully automatic operating train data and key wayside operation information by means of a network isolation device;
1.2a train data processing unit connected with the train data collection unit and configured to homogenize collected data and write homogenized data into real-time database and to generate fault alarms according to status information;
The system 200 may generate error reports 202, include a database of expanded information 204, monitor system status 206, provide a repository 208, a regulating machine 210, and a user interface 212, and facilitate troubleshooting 214.
A · US 2009/0125757 A1 · ¶ 42
Returning to FIG. 5, at operation 502, the training unit 111 determines a training input data object based on the training telemetry data object. As used herein, an input data object is a data object configured to be supplied to a predictive maintenance convolutional neural network.
B · US 2021/0285672 A1 · ¶ 54
1.3a train data analysis unit configured for fusion analysis of collected and processed data and for positioning, cause analysis and impact analysis of complex fault;
Alternatively, the system monitoring tool 206 may automatically identify faulty or problematic individual components. The problem identified or collected by the system monitoring tool 206 may be expanded, or expounded upon, by a component-related piece of information associated with troubleshooting and/or error correction that is stored in a database of expanded information 204.
A · US 2009/0125757 A1 · ¶ 44
As a further example, a maintenance prediction may describe one or more affected hardware units of the hardware units associated with a monitored system, where the one or more affected hardware units are determined based on processing predictive telemetry data using a trained predictive maintenance convolutional neural network
B · US 2021/0285672 A1 · ¶ 66
1.4a portable on-duty unit configured to obtain key fault and operation information related to train in real time, allowing on-duty personnel to quickly and actively obtain fully automatic train operation information and provide relevant troubleshooting guidance;
By performing a user operation on one of the components or subcomponents, such as by clicking with a mouse, detailed troubleshooting guidance related to the component or subcomponent, respectively, may be presented in the details window 506.
A · US 2009/0125757 A1 · ¶ 77
1.5an LTE communication unit configured to communicate with the portable on-duty unit via an LTE network and push the key fault and the operation information of the train and stations to the portable on-duty unit.
The network 104 can include any wired or wireless communication network including, for example, a wired or wireless local area network (LAN), personal area network (PAN), metropolitan area network (MAN), wide area network (WAN), or the like, as well as any hardware, software and/or firmware required to implement it (such as, e.g., network routers, etc.). For example, the network 104 can include a cellular telephone, an 802.11, 802.16, 802.20, and/or WiMax network.
B · US 2021/0285672 A1 · ¶ 24
An empty cell means only that no passage was reproduced there.
Statements in these documents
The systems may be directed toward other types of workflows as well, both medical and non-medical.
A · US 2009/0125757 A1 · ¶ 2
As a result, in response to generic system faults being detected by the system monitor, technicians attempting to remedy the situation may perform manually determined troubleshooting that is inefficient, inconsistent, and/or erroneous.
A · US 2009/0125757 A1 · ¶ 3
Various methods, apparatuses, and systems are configured to provide techniques for performing predictive maintenance data based on telemetry data.
B · US 2021/0285672 A1 · ¶ 1
Cite aspatent.fyi, US 2026/0356402 A1, claim 1, first published 2026-11-20T01:05:31-05:00, https://patent.fyi/US20260356402/, SHA-256 df3a4d6d69550afa68226626e283f949077aaff1b286b970f51ca1a3dc52b636