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.1Station controller processes local data
What ifWhat if each station processed its own sensor data on an embedded controller and sent only maintenance events to a fleet dashboard?
Claim language“at an application server”
The embedded controller samples the station’s current and temperature sensors and keeps a rolling buffer in local memory. When a fault rule fires, the controller sends the station identifier, fault code, and event timestamp to the fleet dashboard.
1.1Contact resistance indicates wear
What ifWhat if the station sent electrical measurements of connector wear without sending temperature readings?
Claim language“temperature sensor data”
A connector with separate voltage sense leads measures the voltage drop across a power contact during a steady-current part of a charging session. The station divides the voltage drop by the measured current and sends the calculated contact resistance with the connector identifier.
1.2Forecast from tabular telemetry
What ifWhat if the server used a model trained on tabular station records to estimate maintenance risk?
Claim language“using a knowledge graph”
The server builds one row per connector from the past seven days of failed session counts, peak temperatures, and voltage excursions. A gradient-boosted decision tree model scores each row for the likelihood of a maintenance event in the next seven days.
1.2Maintenance follows session counts
What ifWhat if the server opened an inspection record when a connector reached a fixed session count?
Claim language“predicting, by at least one processor of the application server”
The server increments a per-connector counter for each completed charging session and compares it with a configured service interval, such as 2,000 sessions. The server opens an inspection record at the interval and resets the counter after the inspection is recorded.
1.3Maintenance changes charging availability
What ifWhat if the server withheld an affected connector from new reservations through an availability flag without issuing a maintenance message?
Claim language“an alert or notification”
The server clears the connector’s eligibility flag in the reservation database when the maintenance condition is recorded. The reservation service selects connectors with the flag set, and the server restores the flag after a successful service check.
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
Maintenance prediction for refrigerated display cases
Refrigeration controllers send case temperatures, compressor currents, and defrost states to an application server. A knowledge graph links each display case to its evaporator, temperature probe, and shared compressor rack. When several cases on one rack warm outside their defrost cycles while rack suction pressure falls, the server identifies the rack as the likely source of a cooling fault. It alerts maintenance staff and opens an inspection ticket for the rack.
Component substitution
Decision trees for charging contactor wear
An application server uses a gradient boosted decision tree model in place of a knowledge graph. Each station reports the elapsed time from a contactor close command to auxiliary contact closure, the voltage drop across the closed contactor, and cumulative switching cycles. The server trains the model on telemetry windows labeled with contactor inspection results, then scores the latest window for each station. When the score exceeds a configured threshold, the server sends an alert and creates an inspection ticket for the contactor.
Parameter or scale variation
Staggered telemetry for regional charger fleets
A fleet of 2,400 charging stations uses 24 site gateways, each serving 100 stations. Stations sample connector temperatures and charging currents at 1 Hz, and each gateway uploads per-connector summaries every 30 seconds using a site-specific offset. The server links connectors to their cable assemblies in a knowledge graph and flags an assembly when its connector temperature exceeds 70 °C in three consecutive summaries while mean current stays within 10 percent of the first interval. The server sends a maintenance alert and disables new sessions on the affected connector.
Combination with existing systems
Charging station maintenance with parts reservation
The application server connects to a computerized maintenance management system that shares station and component identifiers with the charging network. A knowledge graph links each connector to its latch actuator and the matching replacement part number. When repeated latch commands take longer to complete at stable supply voltage, the server flags actuator wear, sends an alert, and opens a work order. The maintenance system reserves the matching actuator at the nearest depot with available stock and records the pickup location on the work order.
Automated or data-driven variant
Automatic recovery after controller restart loops
Each station reports controller boot times, reset causes, and firmware slot status to an application server. A knowledge graph links each controller to its active firmware slot and its last confirmed working slot. After three watchdog resets within 15 minutes, the server flags a restart loop and alerts the operations console. Once the station confirms that all charging sessions have ended and the output contactors are open, the server commands a reboot from the last confirmed working slot and checks for five minutes of uninterrupted heartbeats.
Fan wear prediction with load derating
A station reports fan speed, fan drive duty cycle, heat sink temperature, and charging current to the application server. A knowledge graph links each fan to the power modules it cools, and the server compares measured fan speed with a baseline for the same drive duty cycle. When fan speed falls below 75 percent of baseline for 60 seconds while the heat sink temperature rises, the server generates a fan inspection alert and sends a reduced output current limit for the affected modules. The station enforces the limit until a technician confirms that the fan passes a post-service speed test.
Specific version of a part
Per-connector telemetry every second
Each station publishes one record per connector every second over an encrypted network connection to the application server. Each record contains a station identifier, connector identifier, timestamp, DC bus voltage, output current, and connector temperature.
Fault prediction from component relationships
The knowledge graph links each station to its power modules and connectors and links each module to the connectors it supplies. The server estimates an impending power module fault when voltage excursions recur across multiple connectors supplied by that module.
Connector alert with evidence
The application server generates a maintenance alert containing the station and connector identifiers, the predicted issue, and the latest sensor readings that contributed to the prediction. It groups repeated detections for the same connector and issue under a single alert identifier.
Server queues a diagnostic test
The application server sends a command that queues a diagnostic self-test on the affected station after the active charging session ends. The station returns a result code and measured values, which the server attaches to the maintenance record.
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.1receiving, at an application server from a plurality of electrical vehicle (EV) charging stations, data including one or more of real-time operational data, real-time maintenance data, power consumption data, charging frequency data, voltage level data, and/or temperature sensor data;
A method comprising: retrieving, by a predictive maintenance dispatch server comprising a processing system including a processor, device diagnostic data from equipment of a service provider network for a group of devices that provide communication services to a plurality of customer premises of a plurality of users over a network, wherein the device diagnostic data is based on performance monitoring of the group of devices, wherein the device diagnostic data is retrieved fro
A · US 10,607,194 B2 · claim 1
A predictive maintenance alerting device (40) comprises a server computer (42) operatively connected with an electronic in network (46) to receive time stamped machine log data (30) and time stamped service log data (32) from a medical imaging device (10), and to transmit maintenance alerts (44) to a service center (12).
B · US 2020/0185085 A1 · abstract
1.2predicting, by at least one processor of the application server, based on the received data and using a knowledge graph, an issue or a need for maintenance of an EV charging station of the plurality of EV charging station;
The server can detect a subset of customer premises from among the plurality of customer premises that are not satisfying the quality threshold. The server can analyze a subset of the device diagnostic data that corresponds to the subset of customer premises to determine equipment associated with the subset of customer premises for maintenance.
A · US 10,607,194 B2 · ¶ 13
A non-transitory storage medium stores instructions readable and executable by the server computer to perform a predictive maintenance alerting method including deriving features from the received time stamped machine log data and time stamped service log data, and applying a set of models of component groups to the derived features to generate the maintenance alerts.
B · US 2020/0185085 A1 · ¶ 7
1.3generating, by the at least one processor of the application server, an alert or notification to convey the issue or the need for maintenance of the EV charging station; and
The predictive maintenance alerting device 40 processes the machine log 30 and service log 32 of the medical imaging device 10 generate maintenance alerts 44 that are transmitted to the service center 12 (e.g., more particularly transmitted to the service center workstation or computer 20 in the illustrative embodiment).
B · US 2020/0185085 A1 · ¶ 36
1.4initiating, by the at least one processor of the application server, an action to resolve the issue or need of the identified EV charging station.
The server can determine corrective actions for the equipment of the subset of customer premises according to the history of dispatch repair.
A · US 10,607,194 B2 · ¶ 13
For example, an electronic service schedule 48 may be implemented on a server or other computer to automatically or semi-automatically schedule a service call based on the maintenance alert 44.
B · US 2020/0185085 A1 · ¶ 37
An empty cell means only that no passage was reproduced there.
Statements in these documents
The amount of time that a customer spends engaging with service provider personnel and experiencing the quality issue can increase the likelihood of the customer obtaining service from a different provider and can reduce the customer's willingness to recommend the service to others.
A · US 10,607,194 B2 · ¶ 2
FIG. 4 depicts an illustrative embodiment of a communication system that provide media services and that enables proactive maintenance in providing those services;
A · US 10,607,194 B2 · ¶ 7
A further difficulty in diagnosis of problems with a medical imaging device is that some data resources may have data quality issues.
B · US 2020/0185085 A1 · ¶ 4
Moreover, certain machine problems may be addressed in multiple ways (calibration versus component replacement) leading to ambiguities when using past service histories to predict future problem solutions.
B · US 2020/0185085 A1 · ¶ 4
Cite aspatent.fyi, US 2026/0356232 A1, claim 1, first published 2026-11-19T22:39:24-05:00, https://patent.fyi/US20260356232/, SHA-256 b62a511d04e01e5ceb90d0ca8745c4d182a6f43e3fa0234775ed4b19c65d45e3