Anchor Server Mobility Support for ICN
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current information-centric networks face challenges in handling device mobility, particularly in maintaining seamless communication and resource efficiency when devices frequently change their points of attachment, leading to issues like dropped connections and increased resource consumption due to state maintenance in routers.
Innovation Solution
The system employs a namespace-based approach with anchor servers that manage registration and deregistration, queueing requests, and re-route them upon re-registration, allowing content routers to operate as anchors dynamically and reducing the need for per-request state maintenance, enabling seamless mobility and load balancing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If devices frequently change their points of attachment in information-centric networks, then mobility flexibility is improved, but connection reliability deteriorates due to dropped connections and communication interruptions
Solution Approach 1:
The system performs preliminary actions by queueing data requests at the anchor server before the device actually moves. When a device deregisters from its current point of attachment, any incoming data requests are not dropped but are instead queued at the anchor server. The device can then re-register at a new point of attachment and retrieve the queued requests, ensuring continuous connectivity despite frequent movements.
Solution Approach 2:
The anchor server acts as an intermediary between the mobile device and the network. It maintains the association between the device and its data requests even when the device changes points of attachment. The anchor server receives data requests, queues them if the device is temporarily unavailable, and forwards them once the device re-registers, thereby mediating the connection and ensuring reliability during mobility transitions.
2Reliability
If anchor servers maintain state information for mobile devices, then connection reliability is improved through seamless handover, but resource consumption increases due to state maintenance overhead
Solution Approach 1:
The patent extracts the state maintenance function from individual content routers and concentrates it at the anchor server level. Instead of every router needing to maintain device state, only the anchor server maintains the association between devices and their data requests. This extraction reduces the overall resource consumption in the network while maintaining connection reliability through the anchor server's state management.
Solution Approach 2:
The anchor server serves multiple functions: it acts as a registration point for devices, maintains state information for mobile devices, queues data requests, and performs load balancing. By consolidating these functions at the anchor server, the system avoids duplicating state maintenance across multiple routers, thereby reducing overall resource consumption while maintaining reliability.
3Measurement precision
If content routers maintain per-request state information, then routing accuracy is improved, but device complexity increases due to state maintenance requirements
Solution Approach 1:
The system segments the routing function into two parts: the anchor server handles state maintenance and device association, while content routers handle actual data forwarding based on simple routing rules. This segmentation allows content routers to operate with minimal state information, reducing their complexity, while the anchor server maintains the necessary state for accurate routing decisions.
Solution Approach 2:
The anchor server acts as an intermediary that maintains the complex state information about device locations and request associations. Content routers don't need to maintain this complex state themselves; they simply forward requests to the anchor server, which then routes them appropriately. This intermediary approach maintains routing accuracy while reducing the complexity burden on individual routers.
4Adaptability or versatility
If devices re-register at new points of attachment, then mobility adaptability is improved, but service continuity deteriorates due to dropped data requests
Solution Approach 1:
The system performs preliminary action by pre-queueing data requests at the anchor server before the device completes its re-registration process. When a device moves and deregisters from its current point of attachment, any data requests that arrive during the transition are queued at the anchor server. Once the device re-registers at its new point of attachment, the anchor server retrieves and forwards the queued requests, preventing any loss of information.
Solution Approach 2:
The anchor server ensures continuity of useful action by maintaining the queue of data requests throughout the device's mobility transition. Instead of losing requests during the deregistration/re-registration process, the anchor server holds them in a continuous state, ensuring that the data delivery process continues uninterrupted once the device re-establishes its connection.
Data Source
AI summary
An anchor server in an information-centric network (ICN) receives registration and deregistration requests from one or more producers in the ICN. In response to a producer initially registering, the anchor server stores records associating the producer with content available from the producer via a first point of attachment. In response to the producer deregistering, the records are marked as deactivated. While the records are deactivated, requests for the content from consumers may be queued. In response to the producer reregistering as being connected to the ICN via a second point of attachment, the queued requests are forwarded to the producer via the second point of attachment.