An application is a bet; a grant is a position. The application published on July 2, 2026 as US20260184225A1, "System for Charge Management and Method Thereof," assigned to Hyundai Motor Company, is a bet — and worth reading as one, because its independent claim covers an idea that sounds like a product but is written at the breadth of a first filing. The label first: this is a published application, not a granted patent. It records what Hyundai put before an examiner, not anything it can enforce. With that fixed, the question is what claim 1 actually covers.

A charging management system comprising: at least one first electric vehicle configured to supply power to at least one second electric vehicle that requests a charging service; and a charging management server configured to monitor the first electric vehicle and the second electric vehicle and manage the charging service, wherein the charge management server is configured to dispatch the first electric vehicle corresponding to a request of the second electric vehicle based on status information of the first electric vehicle.— System for Charge Management and Method Thereof, US20260184225A1

Three elements, one function. A first electric vehicle that supplies power. A second electric vehicle that requests a service. A server that monitors both and dispatches the first based on its status. That is the whole of claim 1, and it is deliberately spare — it does not say how the server chooses, what the vehicles say to each other, or how anyone gets paid. Everything specific lives below, in the dependent chain, which is where an examiner and a competitor will both look to find the edges.

Walking the dependents to the operative limitations

Claim 2 gives the server structure: a communication module, a memory, and a processor executing instructions to generate request information from the second vehicle's data, select the first vehicle, transmit request information to it, and dispatch it based on the response. Claim 3 names the protocol — the communication protocol supports at least one of OCPP, ISO 15118, or IEC 61850 — which is a meaningful limitation because it ties the claim to established charging standards rather than an abstract "network." Claim 4 enumerates the status information (identifier, charger information, position, price, protocol, customer information); claim 5 enumerates the request information (user identifier, battery information, position, request message). These are definitional narrowings — they pin down what data the abstract "status" and "request" of claim 1 must contain.

The limitation that does real work is claim 6: the instructions select "the first electric vehicle that is positioned closest to the second electric vehicle by considering positions of the first electric vehicle and the second electric vehicle." A dispatch system's whole novelty pressure sits on the selection rule, and here the disclosed rule is proximity. That is a narrow, literal limitation an examiner can test against prior art directly — closest-resource dispatch is a well-trodden idea in logistics — so the scope that survives may turn on whether proximity-based selection, applied to a vehicle giving power to another vehicle over a charging protocol, reads as more than the sum of known parts. Claim 7 then defines the donor vehicle's structure (communication, control, and charging modules), claim 8 defines the response information (response message, dispatch information, expected fee, expected time), and claims 9 and 10 add the closing report: on completing the power supply the donor generates charging service information — a supply identifier, charging rate, charging time — and transmits it to the server. The dependent chain reads as a full transaction assembled one limitation at a time.

Two independent claims, and a payment sibling

It is worth noting that claim 11 is a second independent claim, not a refinement of claim 1 — it recasts the same system as a method (supplying, monitoring, managing, dispatching), and it carries its own dependent chain. Within it, claim 15 adds a step absent from the claim-1 family: the server verifies "validity of a certificate for the communication protocol received from the first electric vehicle" and receives status information only if the certificate is valid. That certificate gate is the security seam, and it is the same subject a same-day sibling application, US20260184224A1 — identically titled — is directed to, adding payment support keyed to protocol-certificate verification. Filing the dispatch logic and the authenticated-payment logic as parallel applications is a portfolio move: it lets each surface be prosecuted, and potentially narrowed, on its own record. A third same-day filing, US20260184216A1, claims the charging-control mechanics — pausing charging and generating a discharge pulse from the vehicle's battery — at the layer below.

Where the classification places it

The CPC tells you how the office reads the filing. The lead classes are in B60L 53 — the branch for methods and devices for charging electric vehicles — reaching subgroups for vehicle-side and coordinated charging, and they are paired with G06Q 10/06315 (resource and logistics planning) and G06Q 50/06 (energy/electricity services). That B60L-plus-G06Q pairing is the signature of a charging invention claimed as a coordinated service, and it situates the hero away from the cell-chemistry and pack-topology filings elsewhere in the same Hyundai drop. Those neighbors are real and cited here for context, not scope: US20260189136A1, a multi-PFC converter controller in the B60L 53/20 on-board-charging subgroup; US20260184196A1, a supercapacitor-buffered drivetrain in B60L 50/60; US20260186060A1, a model-based battery-pack abnormality detector in B60L 58/16; and US20260188777A1, a pack cooling structure in the H01M thermal classes, joined by US20260190288A1, a direct-cooling manifold for a power module in the H05K packaging classes.

Read as filed, the hero is a broad system claim over a dispatched EV-to-EV charging service, hardened by a proximity-selection dependent and a certificate-verification step, and backstopped by a separately-filed payment sibling. What the record shows is the shape of the bet — a donor vehicle, a requester, and a server between them. What the issued claims will cover, and how far the proximity and certificate limitations get read into claim 1, is for prosecution to decide.