Stateless Multicast via Multi-Label Headers in MPLS Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication networks face challenges in efficiently supporting stateless multicast in label switched packet networks, particularly in accurately determining and forwarding packets to a group of egress routers without maintaining per-flow state.
Innovation Solution
The implementation of an apparatus and method that handles label switched packets by determining the set of egress routers, generating a header based on these routers, and replicating the packets using unicast Label Switched Paths (LSPs) signaled by protocols like LDP or Segment Routing, allowing for stateless multicast without requiring intermediate nodes to maintain per-flow state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If stateless multicast is implemented in label switched packet networks, then network scalability and flexibility are improved, but packet forwarding accuracy to multiple egress routers becomes more difficult
Solution Approach 1:
The patent segments the multicast packet handling by introducing a header with multiple label stacks, where each label stack corresponds to a specific egress router. This segmentation allows the network to forward packets to multiple egress routers independently without maintaining per-flow state, thus improving scalability while maintaining forwarding accuracy.
Solution Approach 2:
The patent adds a new dimension to packet forwarding by incorporating a header structure that contains multiple label stacks. This dimensional addition enables the packet to carry routing information for multiple egress routers simultaneously, allowing accurate forwarding to multiple destinations without requiring intermediate nodes to maintain per-flow state.
2Measurement precision
If per-flow state is maintained at intermediate nodes, then packet forwarding accuracy is improved, but network complexity and resource consumption increase
Solution Approach 1:
The patent extracts the per-flow state requirement from intermediate nodes and relocates it to the packet header itself. By embedding multiple label stacks directly in the header, the forwarding information needed for accurate packet delivery is contained within the packet, eliminating the need for intermediate nodes to maintain per-flow state and thus reducing network complexity.
Solution Approach 2:
The packet becomes self-service by carrying all necessary forwarding information (multiple label stacks) within its own header. Each packet independently contains the routing information needed to reach multiple egress routers, eliminating the need for intermediate nodes to maintain external per-flow state tables, thereby reducing device complexity while maintaining forwarding accuracy.
3Loss of information
If multiple label stacks are included in the header, then routing information completeness is improved, but packet header size and processing overhead increase
Solution Approach 1:
The label stack structure serves multiple functions: it provides routing information for a single egress router when used alone, and provides routing information for multiple egress routers when multiple label stacks are combined in the header. This multi-functionality allows the same structural mechanism to scale from unicast to multicast scenarios without requiring fundamentally different approaches, optimizing the balance between information completeness and header size.
Data Source
AI summary
Various example embodiments for supporting stateless multicast in label switched packet networks are presented. Various example embodiments for supporting stateless multicast in label switched packet networks may be configured to support stateless multicast in label switched packet networks based on support for handling a label switched packet associated with a multicast group, where the label switched packet includes a payload and a header and, further, where the header includes a set of labels indicative of a group of egress routers including at least a portion of the egress routers of the multicast group.