Flow modification including shared context

Patent metadata

Field	Value
Publication number	US-12040968-B2
Application number	US-202017067052-A
Country	US
Kind code	B2
Filing date	Oct 9, 2020
Priority date	May 31, 2016
Publication date	Jul 16, 2024
Grant date	Jul 16, 2024

Abstract

Routing packets by a router involves establishing a first flow configured for forwarding the packets from a first ingress interface to a first egress interface of the router; determining a condition to modify the first flow; deactivating the first flow; establishing a second flow configured for forwarding the packets from at least one of (1) the first ingress interface to a second egress interface, (2) a second ingress interface to the first egress interface, or (3) a second ingress interface to a second egress interface; and activating the second flow.

First claim

What is claimed is:

1. A method comprising:
establishing, by a router, a first flow configured for forwarding, from an ingress interface to an egress interface of a plurality of interfaces of the router, packets of a session between a source device and a destination device;
forwarding, by the router and using the first flow, the packets of the session by:
modifying a first packet of the packets forwarded using the first flow to include metadata comprising a first session identifier for the session;
forwarding the modified first packet; and
forwarding subsequent packets of the packets forwarded using the first flow without the metadata comprising the first session identifier for the session;
in response to determining, by the router, a condition to modify the first flow:
deactivating, by the router, the first flow so that subsequent packets of the session are not forwarded using the first flow;
after deactivating the first flow, establishing, by the router, a second flow configured for forwarding the subsequent packets of the session, wherein the second flow uses at least one interface of the plurality of interfaces of the router that is different from the ingress interface or the egress interface used by the first flow; and
forwarding, by the router and using the second flow, the subsequent packets of the session by:
modifying a second packet of the subsequent packets forwarded using the second flow to include metadata comprising a second session identifier for the session;
forwarding the modified second packet; and
forwarding subsequent packets of the subsequent packets forwarded using the second flow without the metadata comprising the second session identifier for the session.

2. The method of claim 1 , wherein each flow of the first flow and the second flow comprises a descriptor that defines a corresponding egress interface over which packets are to be forwarded by the router and processing to be performed on packets by the router prior to forwarding to the corresponding egress interface.

3. The method of claim 1 , wherein establishing the first flow comprises running a stateful routing protocol to determine at least the egress interface.

4. The method of claim 1 , wherein determining the condition to modify the first flow comprises one of:
receiving a packet on the at least one interface of the plurality of interfaces of the router that is different from the ingress interface or the egress interface;
detecting a communication failure associated with the ingress interface; or
detecting a communication failure associated with the egress interface.

5. The method of claim 1 , wherein determining a condition to modify the first flow comprises:
determining, based at least in part on a routing protocol executed by the router, to change a route that affects the first flow.

6. The method of claim 1 ,
wherein the first flow comprises an action chain comprising a chain descriptor linked to a first set of functional blocks, and
wherein establishing the second flow comprises:
establishing a second set of functional blocks; and
linking the second set of functional blocks to the chain descriptor.

7. The method of claim 1 , further comprising:
storing context information associated with the first flow;
linking the second flow to the stored context information; and
using the stored context information to forward packets using the second flow.

8. The method of claim 1 , wherein establishing the first flow configured for forwarding packets for the session comprises:
prior to establishing the first flow, and in response to determining that first packets received via the ingress interface are not associated with an established flow, forwarding the first packets along a service path, wherein the service path is configured to establish the first flow configured for forwarding packets from the ingress interface to the egress interface; and
after establishing the first flow, and in response to determining that second packets received via the ingress interface are associated with the first flow, forwarding the second packets along a forwarding path, wherein the forwarding path is configured to use the first flow to forward the second packets from the ingress interface to the egress interface.

9. The method of claim 1 , further comprising:
after deactivating the first flow and prior to establishing the second flow, buffering, by the router, the subsequent packets of the session until the second flow is established.

10. The method of claim 1 , wherein the session identifier comprises a source address of the source device, a source port of the source device, a destination address of the destination device, a destination port of the destination device, and a network protocol identifier.

11. A router comprising:
a plurality of interfaces;
storage media; and
one or more processors configured to:
establish a first flow configured for forwarding, from an ingress interface to an egress interface of the plurality of interfaces, packets of a session between a source device and a destination device by:
modifying a first packet of the packets forwarded using the first flow to include metadata comprising a first session identifier for the session;
forwarding the modified first packet; and
forwarding subsequent packets of the packets forwarded using the first flow without the metadata comprising the first session identifier for the session;

in response to determining a condition to modify the first flow:
deactivate the first flow so that subsequent packets of the session are not forwarded using the first flow;
after deactivating the first flow, establish a second flow configured for forwarding the subsequent packets the session, wherein the second flow uses at least one interface of the plurality of interfaces of the router that is different from the ingress interface or the egress interface used by the first flow; and
forward, using the second flow, the subsequent packets of the session by:
modifying a second packet of the subsequent packets forwarded using the second flow to include metadata comprising a second session identifier for the session;
forwarding the modified second packet; and
forwarding subsequent packets of the subsequent packets forwarded using the second flow without the metadata comprising the second session identifier for the session.

12. The router of claim 11 , wherein each flow of the first flow and the second flow comprises a descriptor that defines a corresponding egress interface over which packets are to be forwarded by the router and processing to be performed on packets by the router prior to forwarding to the corresponding egress interface.

13. The router of claim 11 ,
wherein the one or more processors are configured to establish the first flow by running a stateful routing protocol to determine at least the egress interface.

14. The router of claim 12 , wherein determining the condition to modify the first flow comprises one of:
receiving a packet on the at least one interface of the plurality of interfaces of the router that is different from the ingress interface or the egress interface;
detecting a communication failure associated with the ingress interface; or
detecting a communication failure associated with the egress interface.

15. The router of claim 11 , wherein, to determine the condition to modify the first flow, the one or more processors are configured to:
determine, based at least in part on a routing protocol executed by the one or more processors, to change a route that affects the first flow.

16. The router

Assignees

• 128 Tech Inc

Inventors

• Menon Abilash
• Yungelson Anna
• Mcculley Scott A
• Penfield Robert

Classifications

• H04L45/247

  using M:N active or standby paths · CPC title

• H04L43/20

  the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV · CPC title

• H04L47/16

  in connection oriented networks, e.g. frame relay · CPC title

• H04L43/0811

  by checking connectivity · CPC title

• H04L41/0668

  by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure · CPC title