Multicast Router MFIB Entry Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multicast routing systems waste router resources by creating unnecessary entries in the Multicast Forwarding Information Base (MFIB) for locally sourced traffic, leading to increased memory usage and limited capacity to handle groups and interfaces.

Innovation Solution

Implement a method where router entries for locally sourced traffic are only created after a locally sourced multicast data packet is received, and entries are provisioned dynamically based on IGMP Report messages, reducing unnecessary MFIB space usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If router entries are created for all potential locally sourced traffic in the MFIB, then forwarding decisions can be made quickly for any local group member, but router memory resources are wasted and capacity to handle groups and interfaces is limited

Engineering Contradiction:
Improveforwarding decision speedVSAvoidmemory resource usage
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent implements dynamic provisioning of MFIB entries based on actual traffic patterns. Entries for locally sourced traffic are created only when a locally sourced multicast data packet is received, rather than pre-provisioning all possible entries. This dynamic approach maintains forwarding performance while optimizing memory resource utilization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent provisions entries for non-locally sourced traffic in advance based on IGMP Report messages, while delaying provisioning of locally sourced traffic entries until actually needed. This selective preliminary action optimizes the balance between having forwarding entries ready and avoiding unnecessary memory consumption.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If MFIB entries are provisioned in advance for all potential multicast groups and interfaces, then the router can immediately forward multicast packets, but the router's capacity to handle additional groups and interfaces is reduced due to limited memory

Engineering Contradiction:
Improvemulticast packet forwarding capabilityVSAvoidcapacity to handle groups and interfaces
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent dynamically adjusts MFIB entry provisioning based on actual multicast traffic patterns. Entries are created on-demand for locally sourced traffic when packets are received, allowing the router to adapt to varying traffic demands and maintain capacity for additional groups and interfaces while ensuring forwarding capability for active traffic.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the provisioning parameter from static (all entries pre-created) to conditional (entries created based on traffic type and actual reception). This parameter change allows the router to optimize between forwarding productivity and adaptability to different network conditions and traffic patterns.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10122615B2Delayed updating of forwarding databases for multicast transmissions over telecommunications networks
Publication Date: 2018.11.06 DELL PROD LP
  • US10122615B2 patent drawing
  • US10122615B2 patent drawing
  • US10122615B2 patent drawing

AI summary

A switch (110R.3) uses a forwarding database (140F) to forward multicast packets. The switch participates in a multicast protocol (e.g. PIM) with other switches, and also uses a snooping database (e.g. for IGMP snooping) to learn about local group members, i.e. members for which the router serves as a local multicast router (e.g. the local members do not participate in the multicast protocol). When the switch learns of a local member of a multicast group, the switch updates the snooping database but may or may not install the snooping information in the forwarding database. Thus, the forwarding database is not necessarily provisioned for locally sourced data packets addressed to the group until receipt of a locally sourced data packet addressed to the group. If no such packets are received, the forwarding database is not provisioned for such packets, and therefore its size is reduced. Other features are also provided.