Deterministic Path-Finding for Optical Network Headend Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In optical communication networks, multiple headend nodes independently determining new routes in response to changes in network conditions can lead to conflicts due to simultaneous use of the same hardware or software resources, resulting in delays in network recovery.
Innovation Solution
Implementing a deterministic path-finding method for headend nodes to generate new routes in a coordinated manner, ensuring that configuration instructions are provided in a specific order to avoid resource conflicts and optimize network configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple headend nodes independently determine new routes in response to network changes, then network adaptability is improved, but resource conflicts occur causing service interruptions
Solution Approach 1:
The patent applies preliminary action by having headend nodes pre-calculate and store multiple candidate routes before network changes occur. When a network change is detected, the affected headend node can immediately switch to a pre-calculated alternative route without waiting for real-time pathfinding, thus maintaining service continuity while preserving adaptability.
Solution Approach 2:
The patent introduces a centralized path computation element (PCE) or control server as an intermediary that coordinates route determination across multiple headend nodes. This intermediary manages the global network state and provides coordinated path computations, preventing resource conflicts while maintaining network adaptability through centralized control.
2Speed
If headend nodes contemporaneously search for new routes, then network recovery speed is improved, but resource conflicts cause delays
Solution Approach 1:
The patent applies preliminary action by pre-computing and caching multiple alternative routes for critical network paths before failures occur. When a failure happens, headend nodes can immediately activate pre-computed routes without engaging in time-consuming real-time pathfinding or conflict resolution, thus achieving fast network recovery without delays.
Solution Approach 2:
The patent applies dynamics by implementing a dynamic route selection mechanism where headend nodes can switch between pre-computed routes based on real-time network conditions. The system dynamically adjusts route selection priorities and can re-compute paths if pre-computed routes become invalid, maintaining fast recovery while adapting to changing conditions.
3Extent of automation
If independent route determination is performed by each headend node, then system autonomy is improved, but coordination overhead increases
Solution Approach 1:
The patent applies segmentation by dividing the network into autonomous domains or regions, each managed by a headend node with local decision-making authority. Within each domain, nodes independently determine routes maintaining autonomy. Between domains, a standardized coordination protocol manages interactions, reducing overall system complexity while preserving local autonomy.
Solution Approach 2:
The patent introduces a centralized control server or path computation element as an intermediary that handles cross-domain route coordination. Individual headend nodes maintain autonomy for local decisions while delegating inter-domain path computation to the intermediary, which provides coordinated solutions without requiring direct peer-to-peer coordination between autonomous nodes, thus reducing coordination complexity.
Data Source
AI summary
Headend nodes on a communication network can be configured to recover from a change of network conditions by generating new paths for demands. A headend node can generate paths both for demand(s) managed by the headend and other demand(s) managed by other headend(s). The headend nodes can be initialized with the same network representation and can deterministically identify paths, such that each headend identifies the same path for the same demand. The headend nodes can provide configuration instructions for the demands that they manage, but can provide them according to a deterministic schedule, to avoid conflicts.