Contextualized Flow Tags for Ethernet Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional network element architectures fail to efficiently manage and route traffic flows in multi-function Ethernet aggregation networks, particularly in scenarios requiring protection switching and distributed traffic management, due to limitations in identifying specific egress destinations and internal links, and scalability issues with traditional labeling systems.
Innovation Solution
The method involves assigning virtual destination addresses and VLAN ingress/egress connection identifiers to frames, allowing internal switching and translation to actual egress ports, and distributing traffic management tasks among multiple traffic managers, enabling efficient routing and classification of traffic flows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional network element architectures are used to route traffic flows, then basic routing functionality is provided, but scalability and efficiency in multi-function Ethernet aggregation networks deteriorate due to limitations in identifying specific egress destinations and internal links
Solution Approach 1:
The patent introduces flow tags as intermediary identifiers that bridge the gap between traditional routing architectures and multi-function Ethernet aggregation requirements. These flow tags contain both egress port identifiers and internal link identifiers, enabling efficient traffic routing without requiring complex architecture modifications. The flow tags act as mediators that carry necessary routing information through the network element.
Solution Approach 2:
The patent segments the routing information into distinct components within the flow tag structure, including egress port identifiers and internal link identifiers. This segmentation allows the network element to process different routing aspects independently, improving traffic management efficiency while maintaining manageable architectural complexity.
2Reliability
If protection switching is implemented to ensure high reliability, then network availability is improved, but scalability deteriorates due to the need to switch flows as groups rather than individual flows
Solution Approach 1:
The patent implements dynamic flow tag assignment where individual flows can be dynamically switched while maintaining protection group integrity. The system can switch flows individually when needed while still supporting group switching for protection purposes, providing both high reliability and flow-level flexibility simultaneously.
Solution Approach 2:
The patent performs preliminary classification and tagging of flows with protection group identifiers before switching decisions are made. This preliminary action enables the system to quickly determine whether individual or group switching is appropriate, maintaining both reliability through protection switching and flexibility through selective individual flow handling.
3Measurement precision
If device-unique labels are assigned to flows for precise classification, then flow identification accuracy is improved, but scalability deteriorates due to the need to double labels for working and protection paths
Solution Approach 1:
The patent merges the egress port identifier and internal link identifier into a single flow tag structure. This consolidation eliminates the need for separate labels for working and protection paths, as the flow tag inherently contains all necessary routing information. The merged structure maintains precise flow identification while improving scalability by avoiding label multiplication.
4Ease of operation
If internal links are specified for traffic routing, then path control is improved, but device complexity increases due to the need to manage both egress destinations and internal links
Solution Approach 1:
The patent implements self-service routing where the flow tag carries its own routing information (egress port identifier and internal link identifier) that enables automatic routing decisions. Network elements can process flows based on the embedded information in the flow tags without requiring complex external routing management, achieving precise path control while reducing routing management complexity.
Data Source
AI summary
According to one embodiment, a method may include assigning a virtual local area network (VLAN) ingress connection identifier (iXid) to a frame upon ingress. The method may also include classifying a traffic flow for which the frame is a part through ingress engines of the network element based on the iXid. The method may further include swapping the iXid for an egress connection identifier (eXid) in the frame. The method may additionally include policing or shaping the traffic flow based on at least one of the iXid and the eXid. Moreover, the method may include classifying the traffic flow through egress engines of the network element based on the eXid.