On-Demand Mobile EV Charging: The Roadside Rescue Network for Electric Cars

The Engineering Decision That Defined Mobile EV Charging's IP Landscape

In 2017, SparkCharge founder Josh Aviv was staring at a hardware prototype that worked perfectly in a lab and was nearly useless on a roadside. The portable charging unit could store enough energy to give a stranded EV thirty miles of range — but the moment it connected to a vehicle's charge port, the handshake failed. The car's battery management system (BMS) did not recognize the portable unit as a certified charger; it read it as an unknown power source and refused the session. Aviv's team spent the better part of a year solving not the battery-capacity problem the market assumed was the hard part, but the protocol-compliance problem nobody was talking about: how do you convince a vehicle's onboard software that a portable, non-grid-connected device is a legitimate charging partner? That engineering detour — from energy-storage problem to protocol-negotiation problem — is also the precise boundary that separates defensible IP from a patent portfolio that collapses under scrutiny. Founders entering this space in 2025 are making the same category error Aviv's team nearly made: they are patenting the wrong layer.

What the Technology Actually Does (and Where the Prior Art Lives)

On-demand mobile EV charging has three distinct technical layers, and each carries a different patent-eligibility risk profile.

Layer 1: The Dispatch and Routing Platform

The software platform that receives a distress call, locates the nearest available charging unit, routes a technician, and estimates arrival time is the most visible part of the system and the most Alice-exposed. Under the two-step Alice Corp. v. CLS Bank framework, routing and demand-prediction algorithms are abstract ideas. A claim written as "a method for dispatching a mobile charging unit to a location based on vehicle battery state and technician proximity" will not survive §101 scrutiny without a concrete inventive concept tied to a specific physical transformation. Uber's dispatch patents faced identical scrutiny; most survived only where claims were tethered to specific sensor-data transformations, not optimization logic in the abstract. Founders who lead with dispatch software claims are building on sand.

Layer 2: The Portable Energy-Storage Unit

The physical battery pack itself — high-density lithium cells, modular stacking architecture, thermal management housing — is eminently patentable as a hardware invention under §101. The challenge here is prior art density. UPS (uninterruptible power supply) systems, portable generator patents, and the existing battery-pack literature from consumer electronics create a crowded landscape. SparkCharge's Roadie system uses a modular stacking configuration that increases capacity without a proportional increase in unit weight; the specific stacking geometry, cell interconnect architecture, and thermal-isolation mechanism between modules represent genuine novelty over the UPS prior art. These claims are defensible — but they are also the easiest for a well-capitalized competitor to design around by changing connector geometry or stack orientation.

Layer 3: The Protocol Handshake and Tether-State Transition

This is the layer Aviv's team discovered by accident, and it is the most strategically valuable claim surface in the entire technology stack. When a portable charging unit physically connects to a vehicle, it must complete a session-authentication handshake with the vehicle's BMS before any energy transfer begins. Under CCS (Combined Charging System) and CHAdeMO protocols, this handshake involves power-line communication (PLC) negotiation, charge-rate authorization, and continuous BMS state monitoring throughout the session. A portable, non-grid-connected device must emulate the electrical signature of a fixed EVSE (Electric Vehicle Supply Equipment) while simultaneously managing its own internal state — transitioning from a storage device drawing no external power to an active charger delivering up to 50 kW DC. The claims written around this transition sequence — the exact protocol steps, timing parameters, and state-machine logic that govern the unit's shift from transport mode to charge mode — are both highly specific and not anticipated by any prior-art genus. Grid-tied EVSE patents do not teach it; portable battery patents do not anticipate it. This is the Tether-State Transition Surface.

The Tether-State Transition Surface: Your Core Claim Architecture

The Tether-State Transition Surface defines the only Alice-resistant patent claim surface in mobile EV charging: the engineered protocol sequence that converts a portable energy-storage unit from a roving battery into a standards-compliant vehicle charger. Claiming the dispatch software alone reads on abstract optimization. Claiming the portable battery alone reads on prior-art UPS systems. But claiming the CCS/CHAdeMO protocol negotiation handshake — specifically tied to the vehicle's real-time BMS state, dynamic charge-rate authorization, and session-authentication sequence — describes a concrete physical-electrical transformation that neither prior-art genus can anticipate or design around.

In practice, this means your independent claims should recite the state machine explicitly: the transition from "storage mode" (internal BMS active, charge port unpowered) through "handshake mode" (PLC negotiation, EVSE emulation signal active) to "active charge mode" (DC power delivery at BMS-authorized rate, continuous state monitoring loop). Each state transition is a concrete physical event, not an abstract step. A competitor who wants to design around this cannot simply change the dispatch algorithm or restack the battery modules — they must re-engineer the protocol compliance layer, which is expensive, time-consuming, and likely to generate its own prior-art entanglement with CCS/CHAdeMO licensing bodies.

For founders, threading the Tether-State Transition Surface through the patent portfolio means filing claims at three levels of granularity: (1) the overall state-machine architecture as a system claim, (2) the specific PLC negotiation sub-sequence as a method claim, and (3) the hardware components — the PLC modem, the isolation circuitry, the charge-rate arbitration logic — as apparatus claims. This three-axis claim structure forces a competitor to find prior art that invalidates all three simultaneously, which is dramatically harder than attacking a single claim type.

Prior Art Landscape and Freedom-to-Operate Risks

Conducting a prior art search in this space requires looking beyond obvious EV charging databases. The relevant prior art clusters are: (a) EVSE standards bodies — SAE J1772, IEC 62196, and CHAdeMO Association filings contain substantial technical disclosure that can be treated as prior art even without formal patent status; (b) portable power station patents from manufacturers like EcoFlow and Jackery, particularly claims covering DC-output management and BMS state monitoring; and (c) Tesla's Supercharger architecture patents, several of which describe charge-rate negotiation sequences that partially overlap with the mobile use case even though they were drafted for fixed infrastructure.

Freedom-to-operate (FTO) analysis in this space must specifically probe whether your protocol handshake implementation reads on any existing EVSE manufacturer's claims. ChargePoint, ABB, and BTC Power all hold patents on EVSE communication protocols. A mobile charging device that achieves CCS compliance by replicating a ChargePoint protocol module may infringe, even if the physical form factor is entirely novel. FTO is not a one-time exercise here — as CCS2 and NACS (North American Charging Standard, now adopted by Tesla and backed by SAE) evolve, new protocol patents will be filed, and your compliance approach may need to be re-evaluated with each hardware generation.

Filing Strategy: Provisional Windows and the Claims That Matter at Series A

A provisional application buys twelve months of priority date protection at roughly $1,600 (small entity) or $320 (micro entity) in USPTO fees. For a hardware startup at pre-seed, this is the right move — but only if the provisional contains a complete technical disclosure of the Tether-State Transition Surface. A provisional that describes the portable battery and the dispatch app but omits the protocol handshake mechanics will not support non-provisional claims directed at that layer when the twelve-month window closes. Provisional applications that fail to disclose the actual inventive concept are one of the most common IP errors in hardware startups; they provide a filing date that protects only what was written, not what was built.

At Series A, institutional investors will run a patent due-diligence check. The questions they are actually asking are: (1) Does your IP protect the thing that is hardest to replicate, not just the thing that is easiest to describe? (2) Do your claims survive an Alice challenge at the Federal Circuit level? (3) Can a Tier 1 auto manufacturer or a ChargePoint-scale incumbent design around your core claims within eighteen months? A portfolio built on dispatch software claims fails question two. A portfolio built solely on battery-stack geometry fails question three. A portfolio anchored to the Tether-State Transition Surface — the protocol compliance layer — answers all three affirmatively, because it is both Alice-resistant and structurally difficult to circumvent without re-entering a crowded prior-art field.

Practical Action Steps for Founders

1. Map your state machine before you file anything. Document every state transition in your protocol handshake — from charge-port detect through session authentication to active power delivery — with specific timing parameters and conditional logic. This documentation becomes the written description that supports your narrowest and most defensible claims.
2. File a micro-entity provisional within 12 months of your first public demo or investor pitch. USPTO fees for micro-entity provisional: $320. Missing this window — particularly if you demo at a trade show or post a technical explainer — creates a §102(b)(1) public-disclosure bar that can eliminate your priority date entirely.
3. Commission a prior-art search scoped to EVSE communication patents, not just EV charging broadly. Standard patent searches using "electric vehicle charging" as a keyword will miss the SAE J1772 and IEC 62196 technical literature, which is the most dangerous prior-art territory for your handshake claims.
4. File apparatus, method, and system claims as a coordinated set in your non-provisional. Each claim type requires a different invalidity attack; forcing a competitor to simultaneously invalidate all three is your structural moat.
5. Reassess FTO every time you add a new vehicle compatibility tier. Adding NACS compatibility, for example, requires a fresh FTO pass against Tesla's NACS-related portfolio, which as of 2024 includes active patents on connector-state detection and session-initiation logic.

FAQ

Why is the dispatch algorithm — the most obvious IP asset — actually the weakest claim surface for a mobile EV charging startup?

Because routing and demand-prediction logic is abstract under Alice step one, and most mobile EV dispatch claims cannot clear step two without a concrete inventive concept tied to a specific physical transformation. The dispatch algorithm is also the layer most susceptible to competitive replication: any logistics software company with mapping APIs can rebuild it. Investors who pressure founders to protect the "platform" are inadvertently pushing them toward the most Alice-exposed and least defensible claim surface in the stack. The claim that actually creates a moat is the one that requires a competitor to re-engineer hardware-level protocol compliance — not one that requires them to rewrite a routing algorithm.

If I achieve CCS compliance by licensing SAE J1772 protocol specifications, does that undermine my own patent claims on the handshake sequence?

Not automatically, but the risk is real. Licensing a standard gives you freedom to implement it; it does not give competitors freedom to implement your specific implementation. The patentable layer is not the CCS protocol itself — that is a published standard — but the specific state-machine architecture, timing logic, and BMS-state arbitration sequence your device uses to achieve compliance in a non-grid-connected context. That specific implementation can be novel and non-obvious over the standard, provided your claims are written around the implementation, not the compliance outcome. This distinction is critical at due diligence: a claims set that reads on "a device that performs CCS charging" will be invalidated by the standard itself, while a claims set that reads on "a device that transitions from storage-mode to EVSE-emulation mode via a specific PLC negotiation sequence" survives.

Does filing broad battery-pack claims create a false sense of IP security that can mislead a Series A investor?

Yes, and this is one of the more consequential IP errors a hardware founder can make before an institutional raise. Battery-pack geometry and modular stacking claims are real property, but a sophisticated investor's patent counsel will quickly identify that a Tier 1 competitor — an automotive OEM with an in-house battery division, for instance — can design around stack geometry in a single hardware cycle. If your IP narrative at Series A centers on battery architecture, you are implicitly conceding that your moat is an 18-month lead time, not a structural barrier. The Tether-State Transition Surface is investor-facing IP precisely because it answers the design-around question with a credible "no" — not because it is legally unassailable, but because the alternative implementation paths lead directly into occupied prior-art territory.

What happens to my priority date if a competitor files a nearly identical provisional before my non-provisional converts?

Under the AIA first-inventor-to-file system, the priority date is your provisional filing date — provided your non-provisional claims are fully supported by the provisional disclosure. If a competitor files a provisional after yours but their non-provisional contains claims your provisional did not support, they may secure rights to that specific claim scope while you hold the earlier date on the claims your provisional did support. This is why the content of your provisional matters as much as its filing date. A thin provisional that captures the filing date but omits the protocol handshake mechanics hands a well-advised competitor a window to claim that specific layer, even if you built it first.

Should a mobile EV charging startup pursue international filing under PCT, and at what stage does that decision become strategically urgent?

The PCT window opens 12 months from your priority date and closes at 30 months for most national-phase entries. The decision is urgent at the Series A stage because international filing costs ($3,000–$8,000 in USPTO/ISA fees, plus national-phase translation and attorney costs) are material for pre-revenue hardware companies, but the strategic calculus is asymmetric: automotive OEMs operate globally, and a patent portfolio with no international coverage is a negotiating liability in any licensing or partnership conversation with a European or Asian manufacturer. Priority markets for mobile EV charging are the EU (strong EV adoption, active regulatory mandates), Japan (CHAdeMO installed base, Toyota/Nissan partnerships), and South Korea (Hyundai/Kia EV expansion). A PCT application preserves optionality for all three without requiring immediate national-phase investment.

This article is for informational purposes only and does not constitute legal advice.