Toyota Jidosha Kabushiki Kaisha is the standout name in the USPTO grant drop dated June 30, 2026: it is the assignee on 43 issued US grants in the batch, the largest single-assignee block in a drop that also carried grants to Ford, Hyundai, BMW, Subaru and Honda. Counting patents is not counting strategy, but the composition of a grant block is a signal about where a company has been pointing its R&D, because a grant reflects work filed and prosecuted years earlier. Inside Toyota’s block, one grant is more revealing about commercial direction than any battery or engine filing: US12669818B2 (“Remote control request system”), which is directed at the operational machinery a company needs if it intends to run driverless vehicles as a service rather than sell driver-assist features to owners.

The reason that distinction matters commercially is cost structure. A privately owned car with driver assistance keeps a human in the seat; the human is the fallback, and it is free to the manufacturer. A driverless fleet moves that fallback into a control room, where remote operators become an operating expense that scales with the fleet — and where the ratio of vehicles to operators largely determines whether the unit economics work. The Toyota grant is directed squarely at that ratio. It distinguishes remote assistance, in which one operator can supervise many cars because each interaction is a brief judgment call while the car keeps driving, from remote driving, in which an operator is tied up steering a single vehicle in real time. A system that defaults to the lighter-touch mode whenever conditions allow is, in business terms, a system designed to keep the operator-to-vehicle ratio high.

The remote control request system according to claim 1, wherein following the negative determination, the processor is configured to request the remote control driving after verifying that one or more remote control driving conditions are satisfied, wherein the one or more remote control driving conditions must be satisfied in order for the remote control driving be permitted on the autonomous driving vehicle, and the processor is configured to stop the autonomous driving vehicle or change the planned trajectory of the autonomous driving vehicle when one or more of the remote control driving conditions are not satisfied.— Remote control request system, remote control request method, and nontransitory storage medium, US12669818B2

What the fallback logic implies about deployment

The claim above spells out the conservative path the system takes when full remote control is warranted but its conditions are not met: the car stops or reroutes. Read as an operational tell, that is Toyota disclosing a design in which availability is deliberately sacrificed for safety at the domain edge — a vehicle that would rather pull over than be driven remotely under conditions it cannot verify. The independent claim’s gating factors — a speed limit below a threshold, available map coverage, and the absence of rain — also describe, in effect, the kind of service area such a fleet would launch in first: mapped, lower-speed, urban or suburban corridors, in fair weather. That is the same conservative envelope visible in every commercial driverless pilot to date, and the grant suggests Toyota has been building the request-routing infrastructure to operate inside it.

The rest of the block reads as fleet-operations plumbing

The remote-control grant does not stand alone. Toyota’s June 30 block clusters other grants that read like the supporting systems of a monitored, service-operated fleet rather than features sold to a private buyer. US12670795B2 (“Monitoring device”) and US12670793B2 (“Alarm device and alarm method”) both address deciding when to raise a warning and how to prioritize among several at once — the arbitration a supervising system needs so it does not drown its operators in alerts. US12669336B2 handles road-geometry perception at branch points, and US12670738B2, assigned to Toyota Industries, covers pedestrian detection. Two grants from Toyota Research Institute, the group’s U.S. R&D arm — US12670211B2 on scoring the complexity of natural-language questions about video and US12670187B2 on clustering high-dimensional data — point at the data-and-reasoning layer behind fleet analytics.

The count itself frames the point. In the same June 30 drop, Ford Global Technologies holds 11 grants and Hyundai Motor Company 11, with BMW at nine and Subaru at eight — respectable blocks, but a fraction of Toyota’s 43. Raw grant counts lag current strategy by years and say nothing about claim value, so the number is context, not a scoreboard. What gives it weight is composition: a block this size, carrying a formal advice-versus-takeover switch plus the monitoring, alarm-arbitration and perception grants around it, is the patent footprint of a company that has spent years building the systems a supervised fleet needs, not just the features a driver wants. The operator-to-vehicle ratio those systems protect is the single line item that separates a driverless service that clears its costs from one that does not.

None of this is a revenue disclosure, and a granted patent is not a product roadmap; Toyota has not said it will commercialize any of these systems, and the claims describe what its engineers built and protected, not what it ships. But the shape of the block is informative. A company pointed primarily at selling cars to individual owners does not need a formal switch between advice and takeover for a remote operator; a company preparing to run vehicles does. The June 30 grant drop shows Toyota holding the patent scaffolding for the second business, and holding more of this drop’s grants, by count, than any other automaker in it.