Layer 2 and Layer 3 Path Computation Engine Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In network management, particularly in time-sensitive networking environments, existing technologies face challenges in effectively managing path selection and reservation between OSI layer 3 devices and across layer 2/layer 3 boundaries, leading to issues like unintentional loops and errors in path detection, especially for low-latency multimedia data.
Innovation Solution
A system comprising a processor with both layer 2 and layer 3 path computation engines, where the layer 2 engine determines and summarizes its topology and switching capabilities, and the layer 3 engine computes paths between devices, allowing independent management and reservation across layers using protocols like PCEP, IS-IS, and Netconf, enabling efficient path selection and reservation without requiring layer 2 path reservation protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If path selection and reservation are managed across layer 2/layer 3 boundaries using existing technologies, then network connectivity is established, but unintentional loops and errors in path detection occur
Solution Approach 1:
The patent segments the network management function into separate layer 2 and layer 3 path computation engines. The layer 2 PCE handles layer 2 topology and the layer 3 PCE handles layer 3 topology independently, preventing loop issues that occur when trying to manage both layers simultaneously. This segmentation allows each engine to operate autonomously within its own layer context.
Solution Approach 2:
The patent introduces an intermediary mechanism where the layer 2 PCE provides an aggregated summary of layer 2 topology to the layer 3 PCE, but does not allow direct cross-layer path computation. This intermediary approach enables necessary information exchange while maintaining independent management boundaries that prevent path detection errors.
2Adaptability or versatility
If multiple routers are connected in series or parallel to create multiple network segments, then network versatility and routing options increase, but path selection and reservation management becomes problematic
Solution Approach 1:
The patent divides the path computation function into separate layer 2 and layer 3 segments that operate independently. Each segment manages its own topology information and path computation, making it easier to operate complex multi-router networks without the complexity of unified cross-layer management.
Solution Approach 2:
Each path computation engine serves itself by independently managing its layer's topology and path computation. The layer 2 PCE self-manages layer 2 paths while the layer 3 PCE self-manages layer 3 paths, eliminating the need for complex inter-layer coordination and simplifying operation.
3Reliability
If layer 2 and layer 3 topologies are managed independently, then path selection reliability improves, but coordination between layers is required
Solution Approach 1:
The patent uses an intermediary mechanism where the layer 2 PCE provides an aggregated summary of layer 2 topology to the layer 3 PCE. This summary contains essential information for layer 3 path computation without requiring detailed layer 2 topology data, maintaining independent management while enabling necessary coordination.
Solution Approach 2:
The aggregated summary mechanism serves multiple functions: it provides topology information for path computation, maintains independent layer management, and enables coordination when needed. This universal interface allows the system to handle both independent operation and coordinated operation as required.
Data Source
AI summary
In some aspects, the disclosure is directed to methods and systems for management of path selection and reservation between layer 3 devices, as well as path selection and reservation across L2/L3 boundaries. In one implementation, path selection can be managed by separating independent but “cooperating” layers, with layer 3 topology and non-adjacent layer 2 topologies handled separately. A first layer 3 router can be identified as a path computation engine (PCE), while other layer 3 routers can be implemented as path control clients (PCC(s)). One layer 2 PCE can be assigned per layer 2 topology, preventing competing path assignments and reservations.