Delay-sensitive services require path selection not only based on reachability but also on the latency characteristics of available network paths. To meet these requirements, path computation must account for accumulated link delays so that the selected path satisfies the intended latency objective. In dynamic network conditions, this also requires the controller to react to changes in delay across the topology and re-optimize existing paths when a better latency-compliant alternative becomes available.
An LSP was established between the selected source and destination. The computed path exhibited the lowest accumulated delay among available routes. LSP attributes reflected the configured latency optimization objective.
In subsequent test steps, we increased the advertised latency of a link within the topology. The controller updated its topology database with the updated latency information. The PCE computed an alternate path that satisfied the latency constraint and resulted in a lower accumulated delay. The LSP operational state reported a modified end-to-end latency value consistent with the adjusted link metrics. The LSP remained operational throughout the re-optimization process.