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.1Vehicle controls charge completion
What ifWhat if the vehicle controls completion at its selected battery percentage through a wired pilot signal?
Claim language“via a charging station server”
The vehicle's battery controller compares measured state of charge with the percentage selected by the driver. At that percentage, the onboard charger stops drawing current and the vehicle changes the wired pilot signal to request that the pedestal open its contactor.
1.1Metered energy per session
What ifWhat if the station dispenses a fixed quantity of energy per session regardless of the resulting battery percentage?
Claim language“reach a desired charge level”
The station controller records a baseline from the connector's energy meter when the session starts. It requests a current ramp-down when the meter registers 12 kWh above the baseline, then opens the output contactor after current falls to zero.
1.2Pedestal controls session termination
What ifWhat if a pedestal controller ends the charging session directly using wait times from a wired check-in terminal?
Claim language“stopping, via the charging station server”
The check-in terminal sends each waiting vehicle's check-in timestamp to the pedestal over a wired bus. When the oldest entry exceeds 15 minutes, the pedestal requests a current ramp-down and opens its output contactor after current falls to zero.
1.2Scheduled connector handover
What ifWhat if a connector changes hands at a scheduled handover time regardless of the number of vehicles waiting?
Claim language“greater than a threshold number of EVs”
The scheduler assigns each connector consecutive 30-minute slots and records the current slot's end time when charging starts. At that time, the charging controller ramps current to zero and releases the connector for the next slot after the present vehicle disconnects.
1.2Site power limit controls dispatch
What ifWhat if the station stops a charging session when the site's power allocation falls below the combined minimum demand of the active sessions?
Claim language“for a time greater than the other EVs”
The station controller subtracts measured building load from the site's import limit and compares the remaining capacity with the sum of the active sessions' minimum stable charging power. If demand exceeds capacity, the controller sheds sessions in a configured connector priority order until the remaining demand fits.
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
Charging rotation for warehouse lift trucks
A warehouse controller connects to lift truck chargers and to a check-in terminal beside the charging bays. Operators enter a target battery percentage and register waiting trucks at the terminal. The controller permits each connected truck to charge toward its target while it tracks the waiting queue and reads battery percentages from the chargers. When the oldest wait exceeds a configured limit, the controller stops the connected session with the highest battery percentage and lists its bay for the next truck.
Component substitution
Charge control on a local controller
A programmable logic controller replaces the charging station server and connects to a check-in panel and the charging point controllers over a wired fieldbus. The check-in panel supplies queue timestamps and target battery percentages, and each charging point controller supplies its vehicle's reported battery percentage. The programmable logic controller maintains a charge-enable output for each session until the vehicle reaches its target or the waiting count exceeds a configured limit. At that limit it clears the output for the longest-running session, and the corresponding charging point controller ramps current to zero before opening its contactor.
Parameter or scale variation
Timed turnover at a twelve point station
A station server manages twelve charging points and records a target battery percentage and an energy delivery start time for each session. Every 15 seconds it checks whether all twelve points are occupied and whether at least four vehicles are waiting or the oldest wait exceeds 10 minutes. When both full occupancy and either queue condition apply, the server stops the longest-running session that has delivered energy for at least 20 minutes. The server issues at most one queue-triggered stop every two minutes.
Combination with existing systems
Charge turnover tied to parking access
A parking access controller records vehicle check-ins at the entrance to a garage and passes their timestamps to the charging station server. Charging point controllers report connector status, and bay occupancy sensors report when vehicles leave. The server permits charging toward each driver's selected target and stops the longest-running session when the oldest checked-in vehicle exceeds the waiting limit. After the connector is unplugged and the bay sensor reports vacancy, the server assigns the bay to the next vehicle and sends its entry authorization to the parking access controller.
Charge turnover coordinated with feeder metering
A feeder meter reports station demand to a site energy controller that allocates a power budget among charging points. The charging station server grants each connected vehicle permission to charge toward its requested target while the energy controller sets the point's power limit. When vehicles are waiting and available feeder capacity keeps an active session below a configured power level for five minutes, the server stops the session with the highest battery percentage among those below that power level. The energy controller reallocates the released power when the next vehicle connects.
Automated or data-driven variant
Queue prediction from charger telemetry
Station software samples each active vehicle's reported battery percentage and stores the requested target with timestamps. It estimates the time to target from recent percentage changes and uses recorded unplugging delays to forecast when each bay clears. When the forecast waiting time for the first queued vehicle exceeds the configured limit, the software selects the active session with the highest battery percentage above its driver's minimum setting. It sends a controlled stop command to that charging point and confirms that current has fallen to zero.
Specific version of a part
Driver selects a charge target
A touchscreen sends the driver's 80% target to the charging station server with the connector identifier. The server keeps the direct-current session authorized while the state of charge reported by the vehicle remains below 80% and no stop condition applies.
Vehicle supplies the charge target
The vehicle sends its selected charge target and current battery percentage over the connector's data link when the session starts. The charging station server retains the target in the session record and uses periodic battery percentage updates to permit charging up to that target.
Oldest check-in exceeds limit
A kiosk records check-in timestamps, and the server removes each waiting entry when the corresponding vehicle begins charging. When the oldest remaining entry exceeds 15 minutes, the server issues a stop command to the active connector.
Queue count triggers session stop
Bay occupancy sensors and kiosk check-ins identify distinct waiting vehicles, and the station server counts them after excluding bays with active charging sessions. When the count exceeds three, the server sends a stop command to the connector serving the vehicle whose session is under review.
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.1allowing, via a charging station server, an ability for an electric vehicle (EV) to reach a desired charge level when the EV is receiving energy at a charging station;
FIG. 8 is a flow chart to determine the optimal charge setpoint. This flow chart may be implemented on a microprocessor, microcontroller, programmable logic device, ASIC, or other digital or analog system, furthermore, this flowchart may be implemented using a deterministic model, probabilistic model, fuzzy logic, or other means.
A · US 2015/0097512 A1 · ¶ 38
If for a given segment the state of charge setpoint is 75% and the current state of charge is 70%, the controllers 40 may operate the engine 34 to run the electric machine 30 in known fashion to charge the traction battery 32, etc.
B · US 2022/0169145 A1 · ¶ 22
1.2stopping, via the charging station server, the ability for the EV to achieve the desired charge level when one or more of a following occurs: an amount of time that a number of other EVs waiting to receive energy at the charging station is greater than a threshold time; the number of other EVs waiting to receive energy at the charging station is greater than a threshold number of EVs; the EV is receiving the energy for a time greater than the other EVs at the charging station; and a state of charge (SoC) of a battery in the EV is greater than a SoC of batteries in other EVs at the charging station.
An empty cell means only that no passage was reproduced there.
Statements in these documents
In order to improve performance and battery life, it is necessary to operate the battery within certain limits.
A · US 2015/0097512 A1 · ¶ 2
Operating the battery outside of the limits may decrease the performance or life of the battery.
A · US 2015/0097512 A1 · ¶ 2
However, various combinations and modifications of the features consistent with the teachings of this disclosure may be desired for particular applications or implementations.
B · US 2022/0169145 A1 · ¶ 8
Corresponding algorithms should be computationally efficient in terms of time and resources required.
B · US 2022/0169145 A1 · ¶ 9
Cite aspatent.fyi, US 2026/0356236 A1, claim 1, first published 2026-11-19T22:39:24-05:00, https://patent.fyi/US20260356236/, SHA-256 921a016b72eb499d2c35bc35cb45751ebe53590bdced534bbe4641e3713a4b80