patent.fyi
Applications  /  US 2026/0356347
United States Patent Application Publication

US 2026/0356347 A1

Published
Nov 12, 2026
Filed
Nov 14, 2025
Earliest date on the face
May 8, 2025
Classification
B60W 20/13
First published here
Nov 20, 2026

Generated automatically. Not reviewed by a person. Not legal advice or an opinion.

Section 1 · machine-generated

What if?

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.1Route follows next turns

What ifWhat if the navigation system builds a route from the driver's queued turns without a set destination?
Claim language“a set destination”

The driver queues turns at upcoming junctions using a dashboard control. The navigation processor joins the corresponding road segments and sends their lengths and speed limits to the vehicle controller for battery charge planning.

1.2Junctions bound distance measurements

What ifWhat if the controller measures planned and actual distance between detected junction crossings without a preset duration?
Claim language“during a preset time period”

The controller sums the planned road segment lengths between consecutive junctions and accumulates wheel travel between detections of those junction crossings. It checks the distance difference at the second crossing and enables route-based charging when the difference stays within a calibrated tolerance.

1.2Road segments verify route

What ifWhat if the controller checks the reported road segment against the planned segment sequence without measuring actual driving distance?
Claim language“obtaining a second driving distance that is an actual driving distance”

A map-matching processor uses satellite position and vehicle heading to report the current directed road segment. The controller checks each segment transition against the planned sequence and suspends route-based charging when the vehicle enters an unexpected segment.

1.2Camera checks junction geometry

What ifWhat if the controller checks route consistency using observed junction geometry without comparing driving distances?
Claim language“comparing the first driving distance with the second driving distance”

A forward camera classifies junction features such as branch direction and the presence of a divider. The controller compares those features with the mapped geometry at the next planned junction and suspends route-based charging if the observations conflict.

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 control for hybrid yard tractors

A yard dispatch computer sends a hybrid tractor the lane sequence and planned stops for its next trailer move. The tractor controller calculates the distance scheduled during each 20-second interval and integrates axle encoder pulses over the same interval. It checks the paired distances and confirms the lane sequence using fixed radio tags at lane entrances. For a consistent route, it uses the remaining tow distance and trailer mass to set a battery state-of-charge target and requests engine charging when the measured charge falls below that target.

Component substitution

Ground radar for measured travel distance

A downward-facing Doppler radar replaces wheel odometry as the source of measured travel distance. The vehicle controller uses the radar mounting angle and measured vehicle pitch to convert the Doppler reading to longitudinal ground speed, then integrates its magnitude between the route forecast timestamps. The controller compares the resulting distance with the forecast distance and marks the route estimate unavailable if radar returns are missing for more than one second of the interval. When the distances agree within the configured tolerance and the radar data are valid, the controller uses the route-based charge target to decide whether to request engine charging.

Dispatch waypoints replace onboard route planning

A fleet dispatch server replaces the onboard navigation system as the route source and sends an ordered waypoint list with planned crossing times and cumulative distances. The vehicle controller linearly interpolates cumulative distance at the start and end of each 15-second window and uses the difference as the forecast travel distance. It compares that forecast with integrated wheel speed over the same window and resets the comparison when the server sends a new route revision. Following two consistent windows, the controller uses the remaining distance and scheduled stationary intervals to select a battery charge target and determine whether to request engine charging.

Parameter or scale variation

Route checks at two time scales

The controller compares route-predicted and measured travel distances over rolling 5-second and 60-second windows, updated once per second. It divides the sum of absolute distance errors for the twelve 5-second intervals in the long window by the greater of 100 meters and the predicted distance for that window. If the ratio exceeds 0.15 for three consecutive updates, the controller holds the last accepted route-based charge target and continues to use it for engine charging decisions. After ten consecutive updates below 0.08, it accepts updated targets from the navigation system.

Combination with existing systems

Route charging with battery thermal management

The hybrid controller receives battery temperature and the maximum permitted charging power from the battery thermal management controller. It first compares the navigation forecast distance with odometer distance over a common interval, then derives a charging energy requirement from the remaining route and the current battery state of charge. If the permitted power is too low to deliver that energy before the next scheduled electric driving segment, the hybrid controller requests battery heating through the thermal management controller. It recalculates the available charging time and requests engine-generator power up to the updated battery charging limit when the route still calls for additional charge.

Automated or data-driven variant

Traffic-conditioned distance confidence for charging control

A regression model uses road type, traffic speed, and scheduled stops to estimate the 10th and 90th percentiles of the difference between measured and navigation-predicted travel distance over a 30-second interval. The model trains on timestamp-aligned route forecasts and odometer logs, with separate records for moving and stopped traffic. At runtime the controller calculates the signed distance difference and checks whether it falls in the predicted interval. The share of the last ten checks that fall within their intervals sets the weight of the route-based charge target in a blend with a fixed charge target, and the blended target governs engine charging.

Specific version of a part

Onboard road graph routing

An onboard processor stores road segments with lengths, speed limits, and permitted turns. It computes a route from the vehicle's matched road position to the entered destination and sends the ordered segments to the vehicle controller.

Waypoint constrained destination routing

The navigation processor accepts a destination and intermediate stops entered on the dashboard. It calculates each leg in sequence and sends the combined route with segment lengths and turn instructions.

Wheel pulse distance comparison

The controller estimates planned distance over a 30-second interval using the route's segment lengths and expected speeds. It converts wheel pulses counted over the same interval to actual distance using a calibrated rolling circumference and compares the two distances against a calibrated tolerance.

Engine charging with hysteresis

When the distance comparison confirms route consistency, the controller uses the route-based state-of-charge target. It requests engine-driven generation below a lower threshold and removes the charging request at a higher threshold.

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.

Document AUS 8,000,893 B1
Published
Aug 16, 2011
Filed
Mar 25, 2010
Class
G01C 21/00
Document BUS 2019/0322284 A1
Published
Oct 24, 2019
Filed
Oct 30, 2018
Class
B60W 40/112
Document CUS 2021/0356289 A1
Published
Nov 18, 2021
Filed
Jul 13, 2021
Class
G01C 21/3644
Claim 1
Document A
Document B
1.1a navigation system that provides route information to a set destination; and
A SitNet can be used to provide navigation information, such as potential navigation hazards, optimal routes, alternate routes, traffic conditions, or unexpected occurrences (i.e., a herd of cows blocking a country road). A navigator can create an event node corresponding to their probable itinerary, which includes start, intermediate, and ending locations, as well as travel routes.
A · US 8,000,893 B1 · ¶ 156
1.2a vehicle controller operatively connected to the navigation system and obtaining a first driving distance during a preset time period based on the route information, obtaining a second driving distance that is an actual driving distance during the same time period as the preset time period, comparing the first driving distance with the second driving distance to determine consistency of the route information for a target SoC charging control, and determining whether to operate an engine of the vehicle for selective battery charging.
That is, the lean inspection apparatus 100 collects state information of the vehicle and measures an actual distance (AD) after passing through an inspection interval (for example, 100 m) at a constant speed (for example, 80 Km/h).
B · US 2019/0322284 A1 · ¶ 50

An empty cell means only that no passage was reproduced there.

Statements in these documents
It should be understood, however, that the various embodiments of the present invention are not limited to the precise arrangements and instrumentalities shown in the drawings.
A · US 8,000,893 B1 · ¶ 5
The present disclosure relates to a vehicle lean inspection apparatus and a method for a leaning test of a vehicle.
B · US 2019/0322284 A1 · ¶ 2
However, in the conventional vehicle lean inspection method, an incorrect inspection may occur due to an operation of a steering wheel by an operator during a driving inspection, and there is a problem that it is impossible to quantify the inspection due to the operator's sensitivity evaluation.
B · US 2019/0322284 A1 · ¶ 8
Cite aspatent.fyi, US 2026/0356347 A1, claim 1, first published 2026-11-20T00:27:46-05:00, https://patent.fyi/US20260356347/, SHA-256 d6b770d9bd6d5e447913039beec903026b24692110603502a561db0e5c927bdf
First published
Permanent addresshttps://patent.fyi/US20260356347/
Content fingerprint (SHA-256)d6b770d9bd6d5e447913039beec903026b24692110603502a561db0e5c927bdf
Methodv2026-11-18.2 · automated, not reviewed by a person
Correctionscorrections@patent.fyi