Ingress Router Packet Buffering for Routing Domain Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

During routing domain migration in Low Power and Lossy Networks (LLNs), devices face challenges in ensuring that messages are properly routed due to changes in IP addresses, leading to dropped traffic as services continue to use the old address, resulting in inefficiencies and resource constraints.

Innovation Solution

Ingress routers buffer received packets and, upon notification of a node's migration, determine how to reach the node in the new routing domain, forwarding these packets using tunneling techniques with the new IP address, thereby ensuring seamless message delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a device migrates from one routing domain to another, then the device can optimize communication performance or regain connectivity, but messages sent to the device's old address will not be properly routed

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidmessage loss during migration
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The ingress router pre-establishes a mapping between the device's old address and new address before the device fully migrates. When the router receives a message for the old address, it proactively redirects the message to the new address, preventing message loss during the migration transition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The ingress router acts as an intermediary that receives messages destined for the device's old address and forwards them to the device's new address in the new routing domain. This mediator approach ensures seamless message delivery during migration without requiring the sending device to know about the address change.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If services continue to use the old address after device migration, then service configuration remains simple, but traffic is dropped and cannot reach the migrated device

Engineering Contradiction:
Improveservice configuration simplicityVSAvoidtraffic delivery efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The ingress router serves as an intermediary that transparently redirects traffic from the old address to the new address. Services continue to use the old address without reconfiguration, while the router automatically forwards this traffic to the migrated device's new address, maintaining both operational simplicity and traffic delivery efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system maintains a copy of the address mapping information in the ingress router, allowing the old address to continue functioning as a valid destination. The router uses this copied mapping to redirect traffic to the new address, ensuring services don't need to be reconfigured while traffic still reaches the migrated device.

Inventive Principle:
Principle #26Copying

3Reliability

If the device obtains a new address in the new routing domain, then proper routing can be established, but message delivery to the device is interrupted during the transition

Engineering Contradiction:
Improverouting correctnessVSAvoidmessage delivery delay during migration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The ingress router is notified of the device's migration and establishes the new address mapping before the migration is complete. This preliminary setup ensures that as soon as the device obtains its new address, traffic can be immediately redirected without interruption or delay.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous message delivery capability during migration by keeping the old address mapping active in the ingress router. Messages continue to flow through the router which forwards them to the new address, ensuring uninterrupted communication throughout the transition period.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS9154407B2Maintained message delivery during routing domain migration
Publication Date: 2015.10.06 CISCO TECHNOLOGY INC
  • US9154407B2 patent drawing
  • US9154407B2 patent drawing
  • US9154407B2 patent drawing

AI summary

In one embodiment, an ingress device of a first routing domain in a computer network buffers received packets, and in response to receiving a request from a particular node indicating that the particular node has migrated from the first routing domain to a second routing domain, determines how to reach the particular node in the second routing domain, and forwards the buffered received packets to the particular node in the second routing domain, accordingly. In another embodiment, a device in the first routing domain migrates from the first routing domain to a second routing domain, and determines its new IP address. The device may then send a request to the first ingress router to forward buffered packets for the device to the second routing domain at the new IP address, and may thus receive buffered packets forwarded from the first ingress router at the device in the second routing domain.