ICN Network Attachment Point for IP Multicast Channel Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IP multicast operations in IP networks face challenges with network-internal state management in intermediary routers, leading to high channel switching times, especially in IPTV applications, due to router reconfigurations when joining or leaving IP multicast sources.
Innovation Solution
Implementing a system that enables communication between IP-only wireless transmit/receive units (WTRUs) connected to an Information-Centric Network (ICN) by using the Generic Attribute Registration Multicast Registration Protocol (GMRP) and encapsulating IP multicast packets in ICN packets, allowing for efficient management of IP multicast groups through ICN Network Attachment Points (NAPs).
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If IP multicast operations are performed in traditional IP networks with intermediary routers, then multicast service delivery is achieved, but channel switching times increase due to router reconfigurations
Solution Approach 1:
The patent introduces an Information-Centric Network (ICN) as an intermediary layer between IP-only WTRUs and IP multicast groups. The ICN NAP acts as a mediator that translates IP multicast operations into ICN operations, eliminating the need for traditional router reconfigurations and thereby reducing channel switching times.
Solution Approach 2:
The patent replaces the mechanical router reconfiguration process with an information-centric approach where the ICN NAP manages multicast group state information. Instead of physically reconfiguring router forwarding tables, the system uses information naming and retrieval mechanisms to achieve faster channel switching.
2Adaptability or versatility
If IP-only WTRUs communicate directly over IP networks, then compatibility with existing infrastructure is maintained, but integration with ICN services is limited
Solution Approach 1:
The patent segments the network into distinct functional layers: IP-only WTRUs remain in the traditional IP domain while ICN services operate in the ICN domain. The ICN NAP serves as the boundary that enables IP-only devices to access ICN services without requiring them to be upgraded, thus maintaining compatibility while enhancing adaptability.
Solution Approach 2:
The ICN NAP is designed with multi-functionality, serving both as a gateway for IP-only WTRUs to access ICN services and as a router for traditional IP multicast traffic. This universal design allows a single device to handle multiple protocol types and service requirements without increasing overall network complexity.
3Loss of time
If traditional IP multicast protocols are used, then existing network infrastructure is utilized, but latency in join and leave operations increases
Solution Approach 1:
The ICN NAP pre-establishes multicast group state information and maintains ready-to-use forwarding paths for ICN packets. When IP-only WTRUs need to join or leave multicast groups, the pre-prepared ICN infrastructure enables immediate switching without the latency associated with traditional router reconfiguration and state propagation.
Data Source
AI summary
Some embodiments include systems, methods, and devices for enabling communication between at least two internet protocol (IP)-only wireless transmit/receive units (WTRUs), at least one of which is connected to an information centric network (ICN). The WTRU may send a generic attribute registration multicast registration protocol (GMRP) request on a local IP link to an information centric network (ICN) network attachment point (NAP). The NAP may receive and register the GMRP request with an internal data-base (DB) along with an IP multicast address entry matching the GMRP request. The WTRU may then send an IP multicast packet to the NAP for dissemination to an IP multicast group over an ICN by encapsulating the IP multicast packet in an ICN packet.