Maintained message delivery during routing domain migration

• US 9,154,407 B2
• Filed: 07/16/2014
• Issued: 10/06/2015
• Est. Priority Date: 06/01/2011
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Hui, Jonathan W., Vasseur, Jean-Philippe
• Primary Examiner(s): Moore, Jr., Michael J
• Application Number:
  US14/332,871
• Publication Number:
  US 20140328346A1
• Time in Patent Office: 447 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04W 28/14 using intermediate storage
• CPC Class Codes: H04W 40/32 for defining a routing cluster membership
• CPC Class Codes: H04W 40/36 due to handover

Abstract

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.

Claims

1. A method, comprising:

buffering all received packets at an ingress device of a first routing domain in a computer network;

receiving a request from a particular node indicating that the particular node has migrated from the first routing domain to a second routing domain; and

in response to receiving the request from a particular node indicating that the particular node has migrated from the first routing domain to the second routing domain,

determining how to reach the particular node in the second routing domain; and

forwarding the buffered received packets to the particular node in the second routing domain.

2. The method as in claim 1, wherein each received packet is buffered for a configured length of time.

3. The method as in claim 1, wherein forwarding comprises:

encapsulating one of the buffered received packets in a corresponding packet for forwarding having a destination address of the particular node in the second routing domain.

4. The method as in claim 1, wherein forwarding comprises:

encapsulating one of the buffered received packets in a corresponding multicast packet for forwarding having a unicast prefix, wherein the particular node in the second routing domain is configured to join a corresponding unicast-prefix-based multicast group to receive the forwarded multicast packet.

5. The method as in claim 1, wherein the request contains a timestamp indicating which packets have already been received by the particular node prior to migrating from the first routing domain, and wherein forwarding comprises:

forwarding only those packets not already received by the particular node prior to migrating from the first routing domain based on the timestamp.

6. The method as in claim 1, further comprising:

continuing to receive additional packets at the ingress device for a period of time after receiving the request from the particular node indicating that the particular node has migrated from the first routing domain to a second routing domain; and

forwarding the received additional packets to the particular node in the second routing domain.

7. The method as in claim 1, wherein the ingress device is a field area router (FAR), and wherein the routing domain is a Low power and Lossy Network (LLN) Personal Area Network (PAN).

8. An apparatus, comprising:

one or more network interfaces to communicate as an ingress device within a first routing domain in a computer network;

a processor coupled to the network interfaces and adapted to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

buffer all received packets;

receive a request from a particular node indicating that the particular node has migrated from the first routing domain to a second routing domain; and

in response the request from a particular node indicating that the particular node has migrated from the first routing domain to the second routing domain,

determine how to reach the particular node in the second routing domain; and

forward the buffered received packets to the particular node in the second routing domain.

9. The apparatus as in claim 8, wherein each received packet is buffered for a configured length of time.

10. The apparatus as in claim 8, wherein the process when executed to buffer is operable to:

buffer a select set of packets received by the ingress device, wherein the select set is selected from a group consisting of;

a particular type of packet, a particular class of service of packet, a particular priority of packet, and a particular destination of the packets.

11. The apparatus as in claim 8, wherein the request contains a timestamp indicating which packets have already been received by the particular node prior to migrating from the first routing domain, and wherein the process when executed to forward is operable to:

forward only those packets not already received by the particular node prior to migrating from the first routing domain based on the timestamp.

12. The apparatus as in claim 8, wherein the apparatus is a field area router (FAR), and wherein the routing domain is a Low power and Lossy Network (LLN) Personal Area Network (PAN).

13. A tangible non-transitory computer readable medium storing program instructions that cause a computer to execute a process, the process comprising:

buffering all received packets at an ingress device of a first routing domain in a computer network;

receiving a request from a particular node indicating that the particular node has migrated from the first routing domain to a second routing domain; and

in response to receiving the request from a particular node indicating that the particular node has migrated from the first routing domain to the second routing domain,

determining how to reach the particular node in the second routing domain; and

forwarding the buffered received packets to the particular node in the second routing domain.

14. The tangible non-transitory computer readable medium as in claim 13, wherein each received packet is buffered for a configured length of time.

15. The tangible non-transitory computer readable medium as in claim 13, wherein forwarding comprises:

encapsulating one of the buffered received packets in a corresponding packet for forwarding having a destination address of the particular node in the second routing domain.

16. The tangible non-transitory computer readable medium as in claim 13, wherein forwarding comprises:

encapsulating one of the buffered received packets in a corresponding multicast packet for forwarding having a unicast prefix, wherein the particular node in the second routing domain is configured to join a corresponding unicast-prefix-based multicast group to receive the forwarded multicast packet.

17. The tangible non-transitory computer readable medium as in claim 13, wherein the request contains a timestamp indicating which packets have already been received by the particular node prior to migrating from the first routing domain, and wherein forwarding comprises:

forwarding only those packets not already received by the particular node prior to migrating from the first routing domain based on the timestamp.

18. The tangible non-transitory computer readable medium as in claim 13, further comprising:

continuing to receive additional packets at the ingress device for a period of time after receiving the request from the particular node indicating that the particular node has migrated from the first routing domain to a second routing domain; and

forwarding the received additional packets to the particular node in the second routing domain.

19. The tangible non-transitory computer readable medium as in claim 13, wherein the ingress device is a field area router (FAR), and wherein the routing domain is a Low power and Lossy Network (LLN) Personal Area Network (PAN).