Selective Multicast Processing Using Classification Engine
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Provider Backbone (PBB) network environments, multicast traffic replication decisions are handled by end points like Backbone Edge Bridge (BEB) switches, leading to bandwidth waste due to lack of early pruning and segregation mechanisms, as conventional systems are not equipped to handle dynamic classification changes.
Innovation Solution
A method and system for selective multicast processing using a classification engine to derive a service identifier from a source virtual port, enabling early pruning of (S,G) multicast streams by isolating them based on unique ISIDs, utilizing a VLAN classification engine and network communication chips like Broadcom Apollo family chips to support Mac-in-Mac capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multicast traffic replication decisions are handled by end points (BEB switches), then traditional PBB architecture is maintained, but bandwidth is wasted due to lack of early pruning
Solution Approach 1:
The patent applies preliminary action by performing service identifier derivation and multicast group identification at the ingress BEB before traffic enters the core network. This early classification enables pruning decisions to be made upstream, preventing unnecessary traffic replication in the core while maintaining traditional PBB architecture at endpoint switches.
Solution Approach 2:
The patent segments the multicast processing function by separating service identifier derivation and initial classification at the ingress BEB from the pruning decisions made at core switches. This segmentation allows different parts of the network to perform specialized functions, with endpoints maintaining traditional PBB compatibility while the core implements efficient selective multicast.
2Ease of manufacture
If ISID is assigned based on initial classification in hardware pipeline, then conventional PBB systems operate as designed, but dynamic classification changes cannot be implemented
Solution Approach 1:
The patent applies dynamics by making the service identifier derivation process configurable and adaptable. The system can dynamically derive service identifiers from various sources including source virtual ports, destination virtual ports, or other packet fields, allowing classification behavior to change without hardware reconfiguration. This enables flexible adaptation to different multicast scenarios while working within existing hardware pipeline constraints.
Solution Approach 2:
The patent changes parameters by allowing the service identifier derivation method to be modified through software configuration rather than hardware redesign. The system can switch between different derivation strategies (source port-based, destination port-based, or hybrid approaches) by changing operational parameters, providing adaptability within the fixed hardware architecture.
3Device complexity
If multicast traffic is not pruned early in the network, then simple endpoint processing is used, but bandwidth efficiency deteriorates in the backbone core
Solution Approach 1:
The patent performs preliminary classification and service identifier derivation at the ingress BEB, preparing traffic for efficient core network handling. This upfront work enables core switches to make quick pruning decisions based on derived service identifiers and multicast group memberships, achieving early pruning in the backbone without adding significant complexity to endpoint devices.
Solution Approach 2:
The patent introduces an intermediary mechanism where the ingress BEB derives service identifiers and identifies multicast groups, acting as a mediator between traditional endpoint processing and efficient core pruning. This intermediary function bridges the gap by preparing traffic metadata that enables core switches to perform selective multicast without requiring complex processing at traditional endpoints.
4Device complexity
If no staged classification approach is implemented, then hardware pipeline remains simple, but multicast traffic segregation capability is lost
Solution Approach 1:
The patent segments classification into multiple stages: first stage at ingress BEB derives service identifiers and identifies multicast groups, while subsequent stages in the core network perform pruning based on this classification. This staged approach divides the complex classification task across different network points, achieving multicast segregation without requiring complete hardware pipeline redesign at any single location.
Solution Approach 2:
The patent performs preliminary classification actions at the ingress BEB by deriving service identifiers and identifying multicast group memberships before traffic enters the core. This preliminary work enables downstream switches to perform efficient pruning based on pre-computed classification data, achieving staged classification functionality through a combination of upfront preparation and downstream execution.
Data Source
AI summary
A method, system and computer readable medium for selective multicast processing. The method can include obtaining, using one or more processors, an association between a multicast data stream and a service identifier. The method can also include programming, using the one or more processors, a classification engine with a match that classifies a VLAN. The method can further include receiving, at the one or more processors, a data stream, and classifying, using the one or more processors, the data stream based on a mapping to a source virtual port. The method can also include deriving, using the one or more processors, a service identifier from the source virtual port.