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.1Coupling within a fixed block
What ifWhat if the controller used a fixed track block identified by its boundary detectors?
Claim language“determining a length”
Two axle-counter heads define the boundaries of a dedicated coupling block. The controller uses the block identifier to request protection, and the interlocking holds conflicting routes while the coupling movement is active.
1.1Track geometry sets approach limits
What ifWhat if a track survey and a measured stopping envelope set the approach length and speed limit?
Claim language“according to a train coupling type and coupler attribute information”
A configuration table stores an approach length based on the surveyed grade and the distance between the entry marker and the standing train's stop marker. An onboard controller enforces a fixed crawl speed commissioned through stopping trials and verified against the lowest permitted contact speed in the fleet.
1.2Measured motion sets protection distance
What ifWhat if the protection distance used the train's measured approach speed as its speed input?
Claim language“the maximum coupling collision speed limit of the BCA”
The controller adds a speed measurement margin and the acceleration possible during the brake response interval to the latest odometry reading. It computes the stopping distance using the train's minimum service brake deceleration and holds the reserved distance until updated measurements confirm that a shorter distance suffices.
1.3Protection starts at the coupler
What ifWhat if the controller measured the protection distance from the standing train's reported coupler position?
Claim language“starting, from an end point of the BCA”
The standing train reports a track identifier and a track-relative coupler coordinate derived from a position marker and a stored vehicle offset. The controller accounts for position uncertainty and follows connected track from that coordinate in the coupling direction until the required protection distance is covered.
1.3One locked route defines protection
What ifWhat if confirmed switch positions defined a single protected route?
Claim language“compute all possible chains”
The interlocking proves and locks the required switch positions and holds signals on conflicting approaches at stop before issuing coupling authority. The controller follows the locked route from the operation area endpoint and reserves the track sections that cover the computed protection distance.
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
Coupling protection in a mine yard
An underground ore haulage yard uses a wayside controller to supervise coupling between a locomotive and stationary ore cars. The controller selects the coupling zone length and impact speed limit from the consist type and coupler ratings. It calculates the protection distance from loaded car mass, track grade, brake delay, and the impact speed limit. It traces every reachable track path from the coupling zone exit for that distance and requests switch locks and conflicting movement restrictions before authorizing approach.
A bit mask of track detection sections and switch positions replaces the stored list of individual protection chains. Starting at the coupling zone exit, the controller traverses a directed track graph and subtracts each traversed segment length from the remaining protection distance. It sets bits for every section reached within that distance and for each switch position associated with the traversed paths. The interlocking uses the mask to block conflicting routes and lock each affected switch in its detected position before the controller authorizes coupling.
Parameter or scale variation
Two coupling speeds in one siding
A terminal siding controller stores coupling profiles with illustrative impact speed limits of 2 km/h and 4 km/h for two coupler classes. The profiles use coupling zones of 35 m and 60 m respectively for consists whose full coupling movements fit those lengths. The controller selects the profile from the consist and coupler records and computes the corresponding protection distance using brake response, minimum braking deceleration, and local gradient. It converts that distance to a set of track paths beyond the selected zone and locks the affected routes before authorizing coupling.
Combination with existing systems
Coupling limits in onboard train protection
A wayside coupling controller exchanges movement authorities and speed profiles with an onboard automatic train protection unit. After the interlocking confirms the downstream protection locks, the wayside controller transmits the coupling zone entry coordinate and the permitted impact speed. The onboard unit uses odometry and track reference markers to enforce a braking curve that brings the approaching train to the permitted speed before it enters the zone. The wayside controller retains the locks until it receives coupling completion and verifies that the coupled consist is stationary.
Remote coupling supervision with axle counters
A terminal coupling controller receives section occupancy from axle counters and lock confirmations from the interlocking. It maps every downstream path within the calculated protection distance to the corresponding axle-counter sections, including any section that the distance boundary intersects. It checks that the mapped sections are clear and that conflicting entries are locked before granting the coupling authority. After a coupling-complete indication, it verifies that the protection sections are clear and that onboard standstill is confirmed before releasing the locks.
Automated or data-driven variant
Measured brake response sets protection distance
An onboard recorder measures brake command time, brake cylinder pressure, and vehicle speed during low-speed brake applications. The controller groups the records by consist type and load band and extracts a conservative brake response delay and a minimum effective deceleration for each group. It combines those values with the coupling speed limit, local grade, and a positioning margin to calculate the distance to protect. A fixed conservative profile applies when the matching records are missing or stale, and the controller traces all reachable paths to the resulting distance before requesting locks.
Specific version of a part
Coupler class lookup table
The controller indexes a configuration table by coupling type and the two reported coupler classes. Each entry supplies an operation area length and a maximum coupling contact speed for that combination.
Grade corrected stopping distance
The controller uses the area's maximum coupling contact speed as the initial speed and selects a minimum braking rate from the train's load class and brake configuration. It reduces the braking rate by the downhill component of gravity and adds the distances traveled during brake response and braking, plus a position margin.
Directed track graph traversal
The controller represents track as directed segments with stored lengths and branch connections at switches. Starting at the operation area endpoint, it follows every connected path in the coupling direction and records each ordered segment chain when its cumulative length reaches the safety distance or the path ends at a physical track termination.
Protection chains from section lengths
The controller initializes the chain with the portion of the first axle-counter section between the operation area endpoint and the next section boundary. It extends a separate chain along each continuation in the coupling direction, subtracts section lengths from the remaining safety distance, and includes the entire final section when the distance falls within it.
Cite aspatent.fyi, US 2026/0356404 A1, claim 1, first published 2026-11-20T01:05:31-05:00, https://patent.fyi/US20260356404/, SHA-256 b61793ec735fdc8cf572b5b42855f7aadd3f7f006d10cc29beafd41c1cd671d5