Configuring Speed‑Aware Cache TTL for Railway Train Position Updates

Dynamic TTL Calculation for Spatial Staleness

To ensure that cached train-position data does not exceed a distance-based staleness limit, the Time-To-Live (TTL) must be inversely proportional to the train's current velocity. A fixed 30-second TTL is insufficient because the distance a train travels in 30 seconds varies drastically between a stationary train and one at cruising speed.

Required Dynamic Parameters

The TTL should be calculated using the following parameters:

• Current Speed (v): The most critical variable; as speed increases, the time window for acceptable staleness decreases.
• Maximum Permissible Distance Staleness (dmax): The maximum distance a train can travel beyond its last reported position before the data is considered unsafe for signaling (e.g., 100 meters).
• System Reaction Time (tr): The overhead for network latency and processing that must be subtracted from the total TTL.

Functional Form and Implementation

A clamped linear function is the most reliable approach. A pure linear formula (TTL = d / v) fails when velocity is zero (division by zero) and can lead to cache thrashing at extreme speeds.

The recommended logic is:

TTL = clamp( (d_max / v) - t_r, TTL_min, TTL_max )

Speed Regime	TTL Behavior	Constraint
Stationary (v ≈ 0)	Maximum Ceiling	Prevents unnecessary updates for idle trains.
Moderate Speed	Linear Decay	Maintains constant distance staleness.
High Speed	Minimum Floor	Prevents system collapse from cache stampedes.

Enforcement Bounds

To maintain safety and system stability, apply these bounds:

• Maximum Staleness: Enforce a distance-based limit (e.g., 100m) rather than a time-based limit. If v * TTL > d_max, the cache must be invalidated.
• TTL Floor (TTLmin): Set a minimum threshold (e.g., 1 second) to avoid overloading the backend during high-speed transit.
• TTL Ceiling (TTLmax): Set a maximum threshold (e.g., 60 seconds) to ensure that even stationary trains are heartbeat-verified periodically.

Verification Steps

1. Acceleration Test: Simulate a train increasing from 0 to max speed; verify that the TTL value decreases monotonically.
2. Distance Validation: Multiply the current speed by the assigned TTL to ensure the result never exceeds d_max.
3. Zero-Velocity Test: Confirm that when v = 0, the system defaults to TTL_max without throwing a division-by-zero error.

Missing Diagnostic: Please provide the current network latency (round-trip time) between the position sensors and the cache layer, as this value must be factored into tr to avoid overestimating data freshness.