Content-Centric Network Hub Handover Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Internet structures, based on a one-to-one host-to-host communication paradigm, often lead to redundant operations due to the mismatch between the host-centric configuration and user's content-centric needs, making it inefficient for users to access desired data.
Innovation Solution
A communication method in a content-centric network where a terminal requests content by sending an interest message, and a hub manages the transmission by using a pending interest table and content cache to forward the message, allowing seamless handover and data transfer across subnets while updating face information to ensure continuous service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a host-to-host communication paradigm is used in current Internet structures, then the network configuration is simple and straightforward, but redundant operations occur and data accessibility deteriorates due to the mismatch between host-centric configuration and user content-centric needs
Solution Approach 1:
The patent introduces a content-centric network engine as an intermediary component within hubs that mediates between traditional host-to-host communication and content-centric data retrieval. This engine enables the network to resolve data based on content identifiers rather than host addresses, reducing redundant operations while maintaining network structure simplicity through a layered architectural approach.
Solution Approach 2:
The network architecture is segmented into multiple functional layers: traditional IP routing layer and content-centric layer. The content-centric network engine operates as a separate functional segment within hubs, allowing content-based routing to coexist with traditional host-to-host communication without requiring complete network restructuring.
2Productivity
If content-centric routing is implemented to improve data accessibility, then user content needs are better met, but the network structure and routing complexity increase
Solution Approach 1:
The content-centric network engine pre-processes interest packets by extracting content identifiers and consulting content routing tables before forwarding decisions are made. This preliminary action of resolving content names to routing information simplifies subsequent data transmission by establishing content-to-face mappings in advance, reducing real-time routing complexity.
Solution Approach 2:
The content-centric network engine autonomously manages content routing by maintaining local content routing tables and making independent forwarding decisions based on content identifiers. This self-service capability eliminates the need for complex centralized content routing control, allowing each hub to independently resolve content retrieval requests while improving overall network efficiency.
3Reliability
If handover procedures are implemented during terminal movement between subnets, then service continuity is maintained, but communication delays and service interruption risks increase
Solution Approach 1:
The content-centric network engine proactively updates content routing tables with new face information before service interruption occurs. When a terminal moves to a new subnet, the hub receives the updated interest packet with new face information and preemptively updates its routing table, ensuring that subsequent data packets are immediately routed to the correct new location without delay or interruption.
Solution Approach 2:
The content-centric routing mechanism maintains continuous service by decoupling data transmission from traditional host addressing. Interest packets and data packets are routed based on content identifiers rather than terminal locations, allowing seamless handover as terminals move between subnets. The content routing table dynamically updates face information while maintaining continuous content-to-face mappings, eliminating service interruptions during mobility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of communication for a terminal and/or a hub in a content-centric network is provided. The method includes suspending a data message associated with a content from being provided to a face before a handover when the handover is expected to occur in the terminal that requests the content, and transmitting, to a hub, a new interest message after the handover associated with the content so that the hub may provide the data message associated with the content to the face after the handover. The invention further relates to a terminal, a hub and a combined communication system comprises at least one terminal and at least one hub.