Multi-Source Multicasting in Content-Centric Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current content-centric networks (CCNs) face inefficiencies in supporting multicasting with multiple sources, as existing approaches like PIM-based methods are not scalable and do not effectively manage routing for large numbers of sources, leading to inefficient tree maintenance and data dissemination.
Innovation Solution
The implementation of an information-centric multicasting (ICM) system that establishes a multi-instantiated destination spanning tree (MIDST) for each multicast group, allowing all anchors to be connected and enabling efficient routing through a distributed protocol that reduces unnecessary signaling and tree establishment, using data structures like link cost tables, neighbor tables, and multipoint routing tables to manage routing updates and anchor connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If PIM-based multicast methods are used in content-centric networks, then routing can be established for multicast groups, but the system becomes non-scalable and inefficient when managing large numbers of sources
Solution Approach 1:
The patent segments the multicast routing problem by introducing content-specific routing tables that separate multicast routing state per content object, rather than maintaining global multicast group state. This allows independent management of routing for each content item, reducing overall system complexity and improving scalability when handling multiple sources.
Solution Approach 2:
The patent introduces content routers as intermediary nodes that maintain content-specific routing tables and facilitate multicast delivery. These intermediaries manage the complexity of multi-source routing by localizing routing decisions at each content router rather than requiring global coordination, thereby reducing overall routing management complexity.
2Speed
If traditional address-based routing is used, then routing paths can be established, but the system cannot efficiently support content-centric multicasting with multiple sources
Solution Approach 1:
The patent makes content routers universal by enabling them to handle both unicast and multicast traffic using the same content-name-based routing infrastructure. Content-specific routing tables allow a single routing mechanism to serve multiple functions (unicast and multicast), eliminating the need for separate routing protocols and improving both efficiency and multi-source multicast support.
Solution Approach 2:
The patent changes the routing parameter from destination address to content name. By routing based on content identifiers rather than endpoint addresses, the system achieves both high routing efficiency through content-aware forwarding and versatile multi-source multicast support, as content names naturally identify the data regardless of which source produces it.
3Productivity
If content-specific routing tables are maintained at content routers, then efficient multi-source multicast routing is achieved, but more routing state information must be stored and managed
Solution Approach 1:
The patent applies local quality by maintaining routing state locally at each content router specific to the content it caches or forwards. Each content router maintains content-specific routing tables only for content relevant to its local context, rather than maintaining global routing state for all content in the network. This localizes the routing state information, reducing the total quantity while maintaining high dissemination efficiency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
One embodiment of the present invention provides a system for updating routing information associated with a multicast group in an information-centric network (ICN). During operation, a first node in the ICN receives an update message for the multicast group from a neighbor node. The multicast group includes a root anchor node and a number of anchor nodes with the root anchor node having a smaller name than the anchor nodes. The update message specifies a prefix associated with the multicast group and the root anchor node of the multicast group. The system selects, based on topology information stored on the first node, from neighbors of the first node one or more next-hop neighbors that meet a notification condition, and forwards the update message to the one or more next-hop neighbors.