Opaque PCE Profile Identifiers for Network Path Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network communication systems face challenges in centralizing path definition and policy while maintaining distributed path setup control, particularly in managing network paths with distributed service state and local policies.
Innovation Solution
The introduction of opaque identifiers in the Path Computation Element Communication Protocol (PCEP) enables centralized path definition and policy with distributed path setup control, allowing path computation clients (PCCs) and path computation elements (PCEs) to communicate using profile identifiers that influence path computation and utilization constraints, thereby centralizing path definition while leveraging distributed network intelligence.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If path definition and policy are centralized, then network operation simplicity is improved, but path setup flexibility and local adaptability deteriorate
Solution Approach 1:
The patent segments path computation into two independent phases: path definition (centralized at PCE) and path setup (distributed at PCC). This segmentation allows centralized policy enforcement while maintaining distributed flexibility in path instantiation, resolving the contradiction between operational simplicity and setup flexibility.
Solution Approach 2:
The patent introduces opaque profile identifiers as an intermediary mechanism between centralized path definition and distributed path setup. These identifiers carry policy constraints from the centralized PCE to distributed PCCs, enabling local adaptability while maintaining centralized control over path characteristics.
2Adaptability or versatility
If distributed network intelligence is leveraged, then path setup control flexibility is improved, but path definition consistency deteriorates
Solution Approach 1:
The opaque profile identifier acts as a mediator that carries path definition constraints from the centralized PCE to distributed PCCs. This ensures that all distributed path setup operations maintain consistency with centralized path definitions while preserving local flexibility in execution.
Solution Approach 2:
The patent implements preliminary path definition at the centralized PCE before distributed path setup. The PCE pre-defines path characteristics and constraints using opaque profile identifiers, ensuring consistency is established beforehand before distributed elements perform local path setup operations.
3Productivity
If opaque profile identifiers are used in PCEP, then communication efficiency between PCC and PCE is improved, but protocol complexity increases
Solution Approach 1:
The patent changes the parameter representation in PCEP messages by using opaque profile identifiers instead of explicit path parameter lists. This parameter transformation consolidates multiple path constraints into single identifier fields, improving communication efficiency while the opacity masks the underlying complexity.
Solution Approach 2:
The patent uses opaque profile identifiers as simplified copies or references to full path definitions. Instead of transmitting complete path parameter sets, the system transmits compact identifier copies that reference pre-defined path profiles, reducing message size and improving efficiency while hiding complexity.
Data Source
AI summary
Methods and systems are disclosed for enabling centralized path definition and policy with distributed path setup, and centralized path setup control with distributed path utilization constraints. In one example, a path computation client (PCC) requests, utilizing opaque PCE profile identifiers, path computation from a path computation element (PCE). The PCE profile identifier corresponds to path computation constraints, stored local to PCE, and are unknown to the PCC. Advantageously, the PCE profile identifiers allow the PCC to initiate path computation requests based on information local the PCC while leveraging centralized computation by the PCE. In another example, a PCE requests, utilizing opaque PCC profile identifiers, that a PCC initiate a path. The PCC profile identifier corresponds to path usage constraints, stored local to PCC, and are unknown to the PCE. Advantageously, the PCC identifiers allow the PCE to marshal path initiation while leveraging distributed resources to enforce compliance with usage parameters.