Link State Packet Originator ID for Traffic Matrix
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network monitoring systems, such as NetFlow, struggle to maintain information about the originator of prefixes when routing updates cross Area Border Routers (OSPF) or level 1-2 routers (IS-IS), preventing the creation of a complete core traffic matrix at routers outside the originating area.
Innovation Solution
Incorporating additional adjacency information, such as an originator-ID and link-ID, into Link State Packets (LSPs) allows any router in the network to identify the egress point and maintain prefix attributes across areas, enabling the creation of a core traffic matrix directly within routers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If routing updates are propagated across Area Border Routers using standard Link State Packets, then network routing functionality is maintained, but information about the originator of prefixes is lost
Solution Approach 1:
The patent embeds additional originator information fields within the existing Link State Packet structure. Specifically, it adds an Originator ID field and optionally a Link ID field nested inside the LSP, allowing originator identification without fundamentally changing the overall packet architecture. This nesting approach preserves information while maintaining compatibility with existing routing protocols.
Solution Approach 2:
The patent segments the routing information by separating the originator identification data from the standard routing metrics. The Originator ID and Link ID are treated as distinct informational segments within the LSP, allowing routers to process and preserve this information independently while maintaining standard routing functionality. This segmentation enables information retention without overwhelming the packet structure.
2Productivity
If flow records are exported to remote collectors for traffic matrix creation, then network-wide traffic monitoring is achieved, but the number of exported records increases processing overhead
Solution Approach 1:
The patent performs preliminary action by enabling individual routers to create local traffic matrices using the originator information embedded in LSPs. Routers can pre-calculate traffic matrices locally by combining flow record data with the originator identification available in received LSPs, eliminating the need to export and process all raw flow records centrally. This preliminary local processing significantly reduces the quantity of data that needs to be exported to remote collectors.
3Loss of information
If originator information is maintained in Link State Packets, then egress point identification is enabled, but the size of routing updates increases
Solution Approach 1:
The patent applies local quality by making the additional originator information fields optional and selectively applicable. The Originator ID and Link ID fields are only added to LSPs where originator identification is needed, rather than universally to all routing updates. This selective approach enables egress point identification for relevant prefixes while minimizing the overall increase in routing update size across the network.
Data Source
AI summary
A method of identifying an egress point to a network location in a data communications network comprising a plurality of nodes and links there between comprises the step, performed at the identifying node, of receiving a notification through the network advertising an adjacency to a network location. The method further comprises the steps, performed at the identifying node, of deriving from the notification adjacency information and identifying, from the adjacency information, the egress point.