PCE Label Database Synchronization via Version Flags
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current stateful Path Computation Element (PCE) systems lack efficient mechanisms for managing label database synchronization between the PCE and Path Computation Clients (PCCs), particularly during session restarts or changes, which can lead to unnecessary data exchanges and network instability.
Innovation Solution
Implementing a LABEL-DB synchronization mechanism that includes basic and advanced features, such as full database synchronization on initial sessions or session flaps, and incremental updates based on database version differences, using synchronization flags and version management within the PCEP protocol to optimize label database alignment between PCECC and PCCs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full LSPDB synchronization is performed after every PCEP session restart, then label database alignment between PCE and PCC is ensured, but control-plane data exchanges increase and operational time is wasted
Solution Approach 1:
The patent applies partial action by performing synchronization only when necessary. Instead of always synchronizing the full LSPDB after PCEP session restart, the system checks whether synchronization is actually needed by comparing database versions or checking for changes. This reduces unnecessary data exchanges and operational time while maintaining label database alignment when required.
2Productivity
If incremental LSPDB synchronization is implemented, then data exchange overhead is reduced, but complexity of synchronization management increases
Solution Approach 1:
The patent applies preliminary action by establishing version indicators or change tracking mechanisms during the initial synchronization phase. This preliminary setup enables subsequent incremental synchronizations to efficiently identify and transfer only changed entries, improving productivity while managing complexity through structured version control.
Solution Approach 2:
The patent segments the LSPDB synchronization process into identifiable entries with version markers. By dividing the database into discrete synchronizable units with version information, the system can efficiently perform incremental updates, transferring only necessary portions and reducing overall data exchange overhead.
3Reliability
If LSP state synchronization is performed immediately after initialization, then state consistency is achieved, but control-plane data exchanges increase unnecessarily
Solution Approach 1:
The patent implements feedback mechanisms where the PCE and PCC exchange version information or change status indicators. This feedback allows the system to determine whether actual synchronization is needed before initiating data transfer, reducing unnecessary control-plane data exchanges while maintaining state consistency when changes have occurred.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
Disclosed is a method that provided for label database synchronization in a packet switched communication network comprising steps of establishing a communication path between stateful path computation element (PCE) and a path computation client (PCC), modifying label update message at the PCE to include a synchronization flag and transmitting the label update message to the PCC.