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.2Steering command differencing
What ifWhat if the controller measures the steering change directly from consecutive steering commands?
Claim language“by comparing a first travel path”
A register retains the front wheel angle command issued during the preceding control cycle. A subtractor computes the absolute difference between that command and the current command before the current command replaces the stored value.
1.3Trigger on planner revision
What ifWhat if a change in the planner's route revision counter starts the transition?
Claim language“the change value being greater than or equal a preset value”
The planner increments a revision counter whenever it commits a new route. The controller compares the received counter with the last processed counter and starts a transition when the two differ.
1.4Start at measured vehicle pose
What ifWhat if the transition starts at the measured rear axle position while the vehicle is displaced from the first path?
Claim language“a first position in the first travel path”
A state estimator fuses wheel speed, yaw rate, and position measurements to estimate the rear axle position and vehicle heading. The path generator uses that position and heading directly as initial conditions.
1.5Finish within an alignment region
What ifWhat if the transition ends when the vehicle enters a region of acceptable tracking error?
Claim language“a second position in the second travel path”
The controller checks lateral offset and heading error against limits of 0.15 meters and 2 degrees on each control cycle. When both errors stay within their limits for five cycles, the controller switches from transition control to routine tracking.
1.6Steer from tracking error
What ifWhat if the controller steers toward the updated path through feedback without generating a connecting path?
Claim language“generate, based on the start point and the end point, a convergence path”
The controller computes lateral offset and heading error relative to the updated path on each cycle. It combines those errors with curvature feedforward and limits the rate of change of the steering command.
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
Route transitions for warehouse transport carts
An autonomous warehouse cart stores successive routes from an aisle planner as arrays of floor coordinates. At each route update, the controller projects the cart pose onto both routes and computes the corresponding steering commands at the same look-ahead distance. When the absolute command difference reaches a preset threshold, the controller joins a point ahead on the earlier route to a point on the updated route with a curve that matches the heading at each endpoint. The controller checks the swept footprint against the warehouse occupancy grid and sends a valid curve to the cart steering controller.
Component substitution
Clothoid segments for steering transitions
A piecewise clothoid solver generates the convergence path when the difference between steering commands from successive plans reaches the preset threshold. The solver takes position, heading and curvature from the selected point on each plan. It solves for segment lengths and curvature rates that match both endpoint poses and curvatures and maintain continuous curvature at the segment joins. The path generator samples the solution by arc length and sends position, heading and curvature samples to the steering controller.
Curvature error as the transition metric
The controller uses a root-mean-square curvature difference in place of a difference between steering commands at a single look-ahead point. It projects the vehicle pose onto both plans and samples signed curvature at equal forward arc-length offsets over their shared preview distance. When the curvature difference reaches a preset threshold in inverse meters, the controller joins a point on the earlier plan to a point on the updated plan with a curve that matches both endpoint headings and curvatures. The path tracker converts the curve samples into steering commands using the vehicle wheelbase and lateral position feedback.
Parameter or scale variation
Timed path sampling for yard tractors
An autonomous yard tractor compares successive plans every 100 milliseconds at speeds up to 3 meters per second. It projects its current pose onto each plan and computes a front-wheel steering command using a target 2 meters ahead of each projection. When the commands differ by at least 3 degrees, it connects points 0.5 meters ahead on the earlier plan and 4 meters ahead on the updated plan with a curve that matches the path headings and curvatures at both ends. The controller sends samples at 0.1-meter intervals to the path tracker after checking the curve against the tractor's steering limits.
Combination with existing systems
Convergence paths checked against parking obstacles
An automated parking controller receives a local occupancy grid built from ultrasonic range measurements and wheel odometry. When the steering change between successive parking plans reaches the preset threshold, it generates candidate curves from a point on the earlier plan to several points on the updated plan. For each candidate, the controller sweeps the vehicle footprint along the curve and checks for intersections with occupied or unknown grid cells. It sends the shortest clear candidate within the steering limits to the parking path tracker and commands a stop if no candidate passes the checks.
Automated or data-driven variant
Steering response data sets the trigger
A calibration routine groups logged steering commands and measured front-wheel angles by vehicle speed and aligns each measurement with its command using the measured actuator delay. For each speed band, it sets the trigger to the larger of a configurable minimum and the 95th percentile of absolute tracking error during steady path following. At each plan update, the controller interpolates the trigger from the table and compares it with the absolute difference between the two requested wheel angles. When the difference reaches the trigger, it generates a curve between selected points on the earlier and updated plans and sends the curve to the steering controller.
Specific version of a part
Lockstep processor cores
Two processor cores execute the same control instructions in lockstep. A hardware comparator checks their execution results and raises a fault signal when they differ.
Steering difference at fixed lookahead
The processor samples each path 10 meters ahead of a common vehicle pose and estimates curvature from neighboring samples. It converts each curvature to a front wheel angle using the vehicle wheelbase and takes the absolute difference between the angles.
Quintic curve with matched curvature
The processor fits a planar quintic curve between the start and end points. It constrains the first and second derivatives at each point so that the curve matches the heading and curvature of the corresponding travel path.
Preview steering with speed control
The motion controller samples the convergence path indicated by the received signal and computes steering from a forward target point. A longitudinal controller derives a speed target from upcoming curvature and commands propulsion or braking to track that target.
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.
In a typical implementation, the microcontroller device 205 is a low-to-medium speed processor, is capable of power moding, has internal ROM storing the microprocessor control code, has RAM, and has other IPs to handle timers, interrupts, GPIO, etc.
A · US 2007/0260900 A1 · ¶ 26
1.2a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: determine a change value of a steering control amount associated with the vehicle by comparing a first travel path of the vehicle at a first time point with a second travel path of the vehicle at a second time point after the first time point,
1.3a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: based on the change value being greater than or equal a preset value:
1.4a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: set a first position in the first travel path at the first time point as a start point,
FMS 24 calculates departure waypoint 46 from first flight path trajectory 36, and calculates second flight path trajectory 38 to include a period of time required to complete second flight path trajectory 38, and calculates an ETA at merge waypoint 44 that is approximately equal to the RTA.
B · US 2012/0179368 A1 · ¶ 20
1.5a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: set a second position in the second travel path at the second time point as an end point,
The calculated second flight path trajectory includes a departure waypoint along the first flight path trajectory, an intercept waypoint along the first flight path trajectory, and a departure vector from the departure waypoint to the intercept waypoint.
B · US 2012/0179368 A1 · abstract
1.6a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: generate, based on the start point and the end point, a convergence path,
A second flight path trajectory based at least in part on the tactical command is calculated. The calculated second flight path trajectory includes a departure waypoint along the first flight path trajectory, an intercept waypoint along the first flight path trajectory, and a departure vector from the departure waypoint to the intercept waypoint.
B · US 2012/0179368 A1 · abstract
1.7a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: output a signal indicating the convergence path, and
1.8a memory storing at least one instruction that, when executed by the processor, is configured to cause the apparatus to: control, based on the signal, autonomous driving of the vehicle.
In the exemplary embodiment, FMS 24 may be configured to command autoflight subsystem 318 to move the flight control surfaces of the aircraft without direct human intervention to achieve flight along flight path trajectory 26.
B · US 2012/0179368 A1 · ¶ 39
An empty cell means only that no passage was reproduced there.
Statements in these documents
When developing the vehicle network, the automotive industry realized the complexity of wiring each module to every other module.
A · US 2007/0260900 A1 · ¶ 6
This design is easy to manufacture, easy to maintain and provides the flexibility to add and remove options without affecting the entire vehicle's wiring architecture.
A · US 2007/0260900 A1 · ¶ 6
An integrated autoflight system is needed that eliminates the undesired uncertainty of an aircraft's intent during implementation of tactical commands.
B · US 2012/0179368 A1 · ¶ 5
In one embodiment, a flight management system for use in automatically generating a flight path trajectory for an aircraft is provided.
B · US 2012/0179368 A1 · ¶ 6
Cite aspatent.fyi, US 2026/0356375 A1, claim 1, first published 2026-11-20T00:27:46-05:00, https://patent.fyi/US20260356375/, SHA-256 664c81c267cbab486962aae1a614bc033be5d6c393633156d05225ec18f7c077