Zone Routing Network Controller LSP Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Segment Routing (SR) networks face challenges such as high hardware requirements for label stacks, inefficient bandwidth usage due to packet overhead, and limited scalability due to flooding mechanisms for route information exchange, making network migration difficult and multicast support complex.
Innovation Solution
The proposed Zone Routing (ZR) scheme simplifies network operations by allowing a ZR controller to manage edge nodes without communicating with internal nodes, using a single local label for packet forwarding instead of label stacks, and employing Constrained Shortest Path First (CSPF) for path computation, enabling efficient creation and deletion of Label-Switched Paths (LSPs) without RSVP or LDP.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Segment Routing uses label stacks for packet forwarding, then routing flexibility is improved, but hardware requirements and device complexity increase
Solution Approach 1:
The patent divides the network into hierarchical zones (core zone and access zones) with boundary nodes managing LSP creation within zones. This segmentation allows simplified forwarding in access zones while maintaining routing flexibility through hierarchical LSP management, resolving the contradiction between routing flexibility and device complexity.
Solution Approach 2:
Boundary nodes act as intermediaries between core zone and access zones, handling LSP creation and management tasks. This intermediary approach allows core nodes to maintain routing flexibility while access nodes use simplified forwarding, reducing overall device complexity while preserving adaptability.
2Loss of information
If Segment Routing uses flooding mechanisms for route information exchange, then routing information completeness is improved, but network scalability deteriorates
Solution Approach 1:
The network is segmented into zones with boundary nodes that aggregate routing information. Instead of flooding all nodes with complete routing information, each zone maintains information relevant to its boundaries, reducing overhead while preserving necessary routing completeness through hierarchical aggregation.
Solution Approach 2:
Different parts of the network have different information requirements. Core nodes maintain comprehensive routing information for inter-zone paths, while access nodes maintain only local forwarding information. This local quality approach ensures routing information completeness where needed while improving scalability by reducing information overhead elsewhere.
3Extent of automation
If Segment Routing requires RSVP or LDP for LSP management, then LSP creation control is improved, but protocol complexity and overhead increase
Solution Approach 1:
The patent extracts LSP creation and management functions from individual nodes and consolidates them at boundary nodes. Access nodes simply forward packets using pre-established LSPs, while boundary nodes handle the complex RSVP/LDP signaling. This extraction reduces protocol complexity at most nodes while maintaining automated LSP creation control through centralized boundary node management.
4Measurement precision
If packet headers contain detailed source routing information, then routing precision is improved, but packet overhead increases
Solution Approach 1:
LSPs are established in advance with pre-computed paths and pre-allocated labels. Once an LSP is created, packets simply carry a label identifying the pre-established path rather than detailed routing instructions. This preliminary action ensures routing precision through careful path planning while dramatically reducing packet overhead during actual data transmission.
Data Source
AI summary
An apparatus for zone routing, comprising a transmitter, a receiver, and a processor coupled to the transmitter and the receiver, wherein the processor is configured to determine a path through a network, wherein the path extends from an ingress edge node of the network to a first egress edge node of the network, obtain a global identifier (ID) for identifying a label-switched path (LSP) along the path, send, via the transmitter, a first LSP creation request message to the first egress edge node requesting creation of the LSP, wherein the first LSP creation request message comprises the global ID, and receive, via the receiver, a LSP creation response message from the ingress edge node indicating a creation status of the LSP in response to the first LSP creation request message.