1.1Fee based on rental time
The rental terminal records the start and return timestamps for each battery identifier. The billing server multiplies the elapsed rental time, rounded up to the next minute, by a per-minute rate.
Generated automatically. Not reviewed by a person. Not legal advice or an opinion.
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.
The rental terminal records the start and return timestamps for each battery identifier. The billing server multiplies the elapsed rental time, rounded up to the next minute, by a per-minute rate.
The vehicle controller records cumulative odometer readings at battery installation and removal. The billing server subtracts the installation reading from the removal reading and multiplies the difference by a per-kilometer rate.
A stationary battery feeds a regulated direct-current rail, and a collector on the vehicle transfers power to its traction inverter. The controller permits one vehicle at a time on each metered section and assigns the battery discharge measured during that interval to the vehicle's account.
The rental terminal settles the battery fee at return using a prepaid balance. The charging station multiplies metered grid energy by the electricity rate and sends that amount to a separate billing system.
The device exports the battery identifier and the opening and closing discharge readings for the billing period. The clerk subtracts the readings, applies the published per-kilowatt-hour rate, and enters the resulting amount on a paper bill.
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
A traction battery supplies the propulsion motors of an electric harbor ferry. A direct-current energy meter at the battery terminals accumulates discharged kilowatt-hours in a register. An onboard controller reads the register at dispatch and return, then multiplies the difference by a fixed battery usage rate per kilowatt-hour. The controller creates a billing record containing the ferry identifier, dispatch identifier, discharged energy, and battery usage fee.
A microcontroller on the vehicle gateway replaces the server-side fee calculator. It reads the cumulative discharge counter from the battery management unit at trip start and trip end. It subtracts the start reading from the end reading and multiplies the result in watt-hours by an integer rate in millionths of a currency unit per watt-hour. A record formatter stores the trip identifier, energy difference, and fee in the gateway's nonvolatile memory.
Eight removable 5 kWh traction packs connect to a common vehicle power bus, with one bidirectional energy meter on each pack branch. Each meter maintains a cumulative discharge register with 1 Wh resolution, and the controller reads it at pack connection and before commanded disconnection. The controller multiplies each register difference by a fixed fee per watt-hour. It generates one billing line for each pack connection and sums the lines for the vehicle session.
A forklift dispatch system assigns a vehicle and its installed battery to a warehouse job. The dispatch system records the battery identifier and cumulative discharge reading when the operator accepts the job and again when the operator closes it. A fee calculator multiplies the reading difference by a configured rate per kilowatt-hour. The billing generator posts the energy quantity and battery usage fee to the job's cost center in the warehouse accounting system.
A battery-side energy meter reports a cumulative charge register, and a charging inlet switch reports whether the connector is latched. Software saves the register reading at the latch transition and reads it again at the unlatch transition. The calculator multiplies the difference by a fixed battery usage rate per kilowatt-hour. The billing generator stores one record under the battery identifier and the timestamp of the latch transition.
A battery management unit and a separate direct-current meter each maintain a cumulative discharge counter at the traction battery terminals. The fee service calculates a session energy difference from each counter and checks each reading pair for reset flags and missing session boundaries. It uses the battery management reading when that pair passes the checks and uses the separate meter reading when only that pair passes. The billing generator multiplies the selected energy by the configured rate and records the meter source alongside the fee.
The fee calculator passes the charge and a session identifier to a stored-value controller. The controller applies the debit once per session identifier and returns a settlement status to the vehicle terminal.
A shunt measures outward current at the battery terminals, and a voltage sensor measures terminal voltage. The controller integrates the product of voltage and outward current over time and multiplies the resulting kilowatt-hours by the discharge rate.
A battery management controller integrates inward current and stores cumulative ampere-hours in nonvolatile memory. The billing server subtracts the opening counter value from the closing value and applies a rate per ampere-hour.
A billing process groups completed sessions by account and billing month. It creates one battery fee line per session and records the session identifier, measured quantity, unit rate, and line amount.
A receipt service reads the calculated battery fee when a session closes and writes it into a structured record alongside the battery identifier, session end time, and currency code. The service stores the receipt under the session identifier for retrieval by the account portal.
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.
In a first example of the usage charge calculation method, the calculation unit 134 calculates the basic usage charge based on the amount of radio resources consumed.B · US 2015/0011183 A1 · ¶ 85
The information will then be utilized by LRU in order to route the number to the proper destination, and to generate a single billing record reflecting the LRU and DRF usage.A · US 7,065,193 B2 · ¶ 150
An empty cell means only that no passage was reproduced there.
In some cases, attempting to duplicate existing LCCs would exhaust the serving switch's available supply of LCC translations.A · US 7,065,193 B2 · ¶ 8
Furthermore, it is desirable to perform this additional call processing in a centralized system to allow local service providers to change their preferences without requiring manual changes in hundreds of decentralized switches.A · US 7,065,193 B2 · ¶ 9
Therefore, MVNOs are not sufficiently motivated to efficiently use radio resources.B · US 2015/0011183 A1 · ¶ 8
With these circumstances in mind, it is desirable to provide an arrangement for motivating MVNOs to efficiently use radio resources so that efficient use of radio resources can be promoted when MVNOs are utilized.B · US 2015/0011183 A1 · ¶ 9
patent.fyi, US 2026/0356234 A1, claim 1, first published 2026-11-19T22:39:24-05:00, https://patent.fyi/US20260356234/, SHA-256 3388f8c8a794b9f7d8c9264f862af8cd77763846a10e4b42b6e4642efe21d1f2