IPv6 Session Continuity via Mobility Context Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current standards for IPv6 over Low Power Wireless Personal Area Networks (6LoWPAN) are inadequate for mobility, leading to session disruptions and increased power consumption when low power nodes, such as IoT devices, move and reconnect to different routers, as they struggle to maintain state information and re-establish IP layer sessions.
Innovation Solution
The implementation of a Mobility Context Identifier (MCID) allows low power nodes to retain and re-establish connection state information across router changes, minimizing power consumption and maintaining session continuity by using a unique identifier to query and transfer context information between routers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If low power nodes move and reconnect to different routers using current 6LoWPAN standards, then the nodes can maintain mobility and access different routers, but session disruptions occur and power consumption increases due to inability to maintain state information and re-establish IP layer sessions
Solution Approach 1:
The source router performs preliminary actions by storing context information (including IP layer session state) of the low power node before the node moves. When the node reconnects to a target router, this pre-stored context enables rapid session restoration without full re-establishment procedures, thus maintaining session continuity during mobility
Solution Approach 2:
Context information acts as an intermediary carrier that transfers session state between the source router and target router. The target router retrieves and applies this context information to restore the low power node's sessions, enabling seamless handover without direct node involvement in state transfer
2Adaptability or versatility
If low power nodes move and reconnect to different routers using current 6LoWPAN standards, then the nodes can maintain mobility and access different routers, but power consumption increases due to extensive re-establishment procedures
Solution Approach 1:
The source router performs preliminary actions by storing context information (including IP layer session state) of the low power node before the node moves. When the node reconnects to a target router, this pre-stored context enables rapid session restoration without full re-establishment procedures, thus maintaining session continuity during mobility
Solution Approach 2:
By using the transferred context information, the reconnection process skips the time-consuming steps of full IP layer session re-establishment, neighbor discovery, and address resolution. The target router can directly restore sessions using the pre-captured context, significantly reducing power consumption during mobility events
3Adaptability or versatility
If low power nodes move and reconnect to different routers using current 6LoWPAN standards, then the nodes can maintain mobility and access different routers, but session disruptions occur due to inability to maintain state information
Solution Approach 1:
The source router performs preliminary actions by storing context information (including IP layer session state) of the low power node before the node moves. When the node reconnects to a target router, this pre-stored context enables rapid session restoration without full re-establishment procedures, thus maintaining session continuity during mobility
Solution Approach 2:
The source router creates a copy of the low power node's context information (including IP addresses, port mappings, and session state) and transfers it to the target router. This copying mechanism preserves the original session state without requiring the node to maintain it locally, enabling seamless session continuation after movement
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and apparatus, including computer program products, are provided for communications. In one aspect there is provided a method. The method may include sending, by a low power node, an indicator to a target low power router, wherein the indicator at least represents a request to operate with a prior context used at a source low power router; and receiving, by the low power node, a message in response to the indicator, wherein the message at least indicates whether the low power node can operate at the target low power router with a same context that corresponds to the prior context used previously at the source low power router. Related apparatus, systems, methods, and articles are also described.