Router with bilateral TCP session monitoring

• US 9,985,872 B2
• Filed: 10/03/2016
• Issued: 05/29/2018
• Est. Priority Date: 10/03/2016
• Status: Active Grant

• Current Assignee: 128 Technology, Inc. (Juniper Networks Incorporated)
• Original Assignee: 128 Technology, Inc. (Juniper Networks Incorporated)
• Inventors: Jaffer, Sarah V., Menon, Abilash, Yungelson, Anna, Timmons, Patrick
• Primary Examiner(s): Thompson, Jr., Otis L
• Application Number:
  US15/283,946
• Publication Number:
  US 20180097720A1
• Time in Patent Office: 603 Days
• Field of Search: None
• CPC Class Codes: H04L 45/021 Ensuring consistency of routing table updates, e.g. by using epoch numbers
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/70 Routing based on monitoring results
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

A router is specially configured to implement a bilateral TCP state machine to monitor the status of TCP sessions based on TCP sequence numbers in both forward session packets and return session packets received by the router for a TCP bi-flow session. Among other things, the router may determine the status of a TCP session, for example, based on statistical information such as the number or rate of errors detected (e.g., the number of dropped packets, duplicated packets, out-of-sequence packets, and/or out-of-window packets). Each router is typically configured to collect and store status information and optionally also to use the status information in making intelligent routing decisions, such as, for example, deciding whether or not to forward a particular packet, deciding whether to reconfigure a bi-flow routing session, or updating routing table information used for routing packets.

Claims

1. A Transmission Control Protocol (TCP) augmented router capable of monitoring TCP sessions, the TCP augmented router comprising

a plurality of network interfaces;

a computer memory storing a bilateral TCP state database; and

a packet router configured to implement, for each of a number of TCP bi-flow sessions established by the packet router, a bilateral TCP state machine that performs a process comprising;

establishing, in the bilateral TCP state database, a bilateral TCP state record for the TCP bi-flow session including reference TCP sequence information for monitoring the TCP bi-flow session and statistical information regarding TCP errors detected by the bilateral TCP state machine;

receiving, via a first network interface, forward session packets in transit from a source node to a target node;

receiving, via a second network interface, return session packets in transit from the target node to the source node;

monitoring the TCP bi-flow session based on received TCP sequence information from both the received forward session packets and the received return session packets and the reference TCP sequence information maintained in the bilateral TCP state record, including detecting TCP errors based on the received and reference TCP sequence information; and

updating the bilateral TCP state record for the TCP bi-flow session, including updating the reference TCP sequence information in the bilateral TCP state record based on the received TCP sequence information from the received forward and return session packets and updating the statistical information in the bilateral TCP state record when a TCP error is detected.

2. A TCP augmented router according to claim 1, wherein at least one TCP bi-flow route is a stateful bi-flow route.

3. A TCP augmented router according to claim 1, wherein monitoring the TCP bi-flow session comprises:

(a) for each received forward session packet;

(i) determining a next sequence number expected from the source node based on the reference TCP sequence information maintained in the bilateral TCP state record;

(ii) comparing a TCP sequence number in the received forward session packet with the next sequence number expected from the source node to determine if a TCP error occurred for the TCP bi-flow session; and

(iii) updating the bilateral TCP state record, including updating the reference TCP sequence information in the bilateral TCP state record based on the TCP sequence number in the received forward session packet and updating the statistical information in the bilateral TCP state record when a TCP error is detected; and

(b) for each received return session packet;

(i) determining a next sequence number expected from the target node based on the reference TCP sequence information maintained in the bilateral TCP state record;

(ii) comparing a TCP sequence number in the received return session packet with the next sequence number expected from the target node to determine if a TCP error occurred for the TCP bi-flow session; and

(iii) updating the bilateral TCP state record, including updating the reference TCP sequence information in the bilateral TCP state record based on the TCP sequence number in the received return session packet and updating the statistical information in the bilateral TCP state record when a TCP error is detected.

4. A TCP augmented router according to claim 1, wherein monitoring the TCP bi-flow session comprises monitoring the TCP bi-flow session based on received TCP sequence and acknowledgment numbers from the received forward and return session packets, including detecting TCP errors based on the received TCP sequence and acknowledgment numbers and the reference TCP sequence information, and wherein updating the bilateral TCP state record for the TCP bi-flow session includes updating the reference TCP sequence information based on the received TCP sequence and acknowledgment numbers from the received forward and return session packets.

5. A TCP augmented router according to claim 1, wherein the process further comprises:

determining if the number or rate of TCP errors exceeds a predetermined threshold; and

reconfiguring the TCP bi-flow session when the number or rate of TCP errors exceeds the predetermined threshold.

6. A TCP augmented router according to claim 5, wherein the TCP bi-flow route is associated with a forward flow and a return flow using the first and second network interfaces, and wherein reconfiguring the TCP bi-flow route comprises:

modifying the forward and return flows to utilize at least one network interface other than the first and second network interfaces; and

transmitting stateful routing session metadata in at least one session packet following such modifying of the forward and return flows.

7. A TCP augmented router according to claim 1, wherein detecting TCP errors based on the received and reference TCP sequence information comprises:

determining a location of TCP errors based on the received and reference TCP sequence information.

8. A TCP augmented router according to claim 7, wherein the process further comprises at least one of:

updating a routing table of the TCP augmented router based on the determined location of TCP errors;

or

selecting a route based on the determined location of TCP errors.

9. A TCP augmented router according to claim 1, wherein the process further comprises:

determining if a received session packet is outside of an advertised window size for the TCP bi-flow session based on received TCP sequence information from the received session packet and the reference TCP sequence information maintained in the bilateral TCP state record; and

dropping said packet without forwarding said packet when the bilateral TCP state machine determines that the received session packet is outside of the advertised window size for the TCP bi-flow session.

10. A TCP augmented router according to claim 1, wherein the process further comprises:

monitoring status of the TCP bi-flow session including determination of at least initiation, establishment, and termination of the TCP bi-flow session; and

storing statistical information related to the status of the TCP bi-flow session.

11. A computer program product comprising a tangible, non-transitory computer readable medium having embodied therein a computer program that, when run on at least one computer processor, implements a packet router for a Transmission Control Protocol (TCP) augmented router having a plurality of network interfaces and a computer memory storing a bilateral TCP state database, the packet router configured to implement, for each of a number of TCP bi-flow sessions established by the packet router, a bilateral TCP state machine that performs a process comprising:

establishing, in the bilateral TCP state database, a bilateral TCP state record for the TCP bi-flow session including reference TCP sequence information for monitoring the TCP bi-flow session and statistical information regarding TCP errors detected by the bilateral TCP state machine;

receiving, via a first network interface, forward session packets in transit from a source node to a target node;

receiving, via a second network interface, return session packets in transit from the target node to the source node;

monitoring the TCP bi-flow session based on received TCP sequence information from both the received forward session packets and the received return session packets and the reference TCP sequence information maintained in the bilateral TCP state record, including detecting TCP errors based on the received and reference TCP sequence information; and

updating the bilateral TCP state record for the TCP bi-flow session, including updating the reference TCP sequence information in the bilateral TCP state record based on the received TCP sequence information from the received forward and return session packets and updating the statistical information in the bilateral TCP state record when a TCP error is detected.

12. A computer program product according to claim 11, wherein at least one TCP bi-flow route is a stateful bi-flow route.

13. A computer program product according to claim 11, wherein monitoring the TCP bi-flow session comprises:

(a) for each received forward session packet;

(i) determining a next sequence number expected from the source node based on the reference TCP sequence information maintained in the bilateral TCP state record;

(ii) comparing a TCP sequence number in the received forward session packet with the next sequence number expected from the source node to determine if a TCP error occurred for the TCP bi-flow session; and

(iii) updating the bilateral TCP state record, including updating the reference TCP sequence information in the bilateral TCP state record based on the TCP sequence number in the received forward session packet and updating the statistical information in the bilateral TCP state record when a TCP error is detected; and

(b) for each received return session packet;

(i) determining a next sequence number expected from the target node based on the reference TCP sequence information maintained in the bilateral TCP state record;

(ii) comparing a TCP sequence number in the received return session packet with the next sequence number expected from the target node to determine if a TCP error occurred for the TCP bi-flow session; and

(iii) updating the bilateral TCP state record, including updating the reference TCP sequence information in the bilateral TCP state record based on the TCP sequence number in the received return session packet and updating the statistical information in the bilateral TCP state record when a TCP error is detected.

14. A computer program product according to claim 11, wherein monitoring the TCP bi-flow session comprises monitoring the TCP bi-flow session based on received TCP sequence and acknowledgment numbers from the received forward and return session packets, including detecting TCP errors based on the received TCP sequence and acknowledgment numbers and the reference TCP sequence information, and wherein updating the bilateral TCP state record for the TCP bi-flow session includes updating the reference TCP sequence information based on the received TCP sequence and acknowledgment numbers from the received forward and return session packets.

15. A computer program product according to claim 11, wherein the process further comprises:

determining if the number or rate of TCP errors exceeds a predetermined threshold; and

reconfiguring the TCP bi-flow session when the number or rate of TCP errors exceeds the predetermined threshold.

16. A computer program product according to claim 15, wherein the TCP bi-flow route is associated with a forward flow and a return flow using the first and second network interfaces, and wherein reconfiguring the TCP bi-flow route comprises:

modifying the forward and return flows to utilize at least one network interface other than the first and second network interfaces; and

transmitting stateful routing session metadata in at least one session packet following such modifying of the forward and return flows.

17. A computer program product according to claim 11, wherein detecting TCP errors based on the received and reference TCP sequence information comprises:

determining a location of TCP errors based on the received and reference TCP sequence information.

18. A computer program product according to claim 17, wherein the process further comprises at least one of:

updating a routing table of the TCP augmented router based on the determined location of TCP errors;

or

selecting a route based on the determined location of TCP errors.

19. A computer program product according to claim 11, wherein the process further comprises:

determining if a received session packet is outside of an advertised window size for the TCP bi-flow session based on received TCP sequence information from the received session packet and the reference TCP sequence information maintained in the bilateral TCP state record; and

dropping said packet without forwarding said packet when the bilateral TCP state machine determines that the received session packet is outside of the advertised window size for the TCP bi-flow session.

20. A computer program product according to claim 11, wherein the process further comprises:

monitoring status of the TCP bi-flow session including determination of at least initiation, establishment, and termination of the TCP bi-flow session; and

storing statistical information related to the status of the TCP bi-flow session.

21. A method for monitoring Transmission Control Protocol (TCP) sessions by a TCP augmented router having a plurality of network interfaces and a computer memory storing a bilateral TCP state database, the method comprising, for each of a number of TCP bi-flow sessions established by the TCP augmented router, implementing a bilateral TCP state machine that performs a process comprising:

establishing, in the bilateral TCP state database, a bilateral TCP state record for the TCP bi-flow session including reference TCP sequence information for monitoring the TCP bi-flow session and statistical information regarding TCP errors detected by the bilateral TCP state machine;

receiving, via a first network interface, forward session packets in transit from a source node to a target node;

receiving, via a second network interface, return session packets in transit from the target node to the source node;

monitoring the TCP bi-flow session based on received TCP sequence information from both the received forward session packets and the received return session packets

and the reference TCP sequence information maintained in the bilateral TCP state record, including detecting TCP errors based on the received and reference TCP sequence information; and

updating the bilateral TCP state record for the TCP bi-flow session, including updating the reference TCP sequence information in the bilateral TCP state record based on the received TCP sequence information from the received forward and return session packets and updating the statistical information in the bilateral TCP state record when a TCP error is detected.

22. A method according to claim 21, wherein at least one TCP bi-flow route is a stateful bi-flow route.

23. A method according to claim 21, wherein monitoring the TCP bi-flow session comprises:

(a) for each received forward session packet;

(i) determining a next sequence number expected from the source node based on the reference TCP sequence information maintained in the bilateral TCP state record;

(ii) comparing a TCP sequence number in the received forward session packet with the next sequence number expected from the source node to determine if a TCP error occurred for the TCP bi-flow session; and

(iii) updating the bilateral TCP state record, including updating the reference TCP sequence information in the bilateral TCP state record based on the TCP sequence number in the received forward session packet and updating the statistical information in the bilateral TCP state record when a TCP error is detected; and

(b) for each received return session packet;

(i) determining a next sequence number expected from the target node based on the reference TCP sequence information maintained in the bilateral TCP state record;

(ii) comparing a TCP sequence number in the received return session packet with the next sequence number expected from the target node to determine if a TCP error occurred for the TCP bi-flow session; and

(iii) updating the bilateral TCP state record, including updating the reference TCP sequence information in the bilateral TCP state record based on the TCP sequence number in the received return session packet and updating the statistical information in the bilateral TCP state record when a TCP error is detected.

24. A method according to claim 21, wherein monitoring the TCP bi-flow session comprises monitoring the TCP bi-flow session based on received TCP sequence and acknowledgment numbers from the received forward and return session packets, including detecting TCP errors based on the received TCP sequence and acknowledgment numbers and the reference TCP sequence information, and wherein updating the bilateral TCP state record for the TCP bi-flow session includes updating the reference TCP sequence information based on the received TCP sequence and acknowledgment numbers from the received forward and return session packets.

25. A method according to claim 21, wherein the process further comprises:

determining if the number or rate of TCP errors exceeds a predetermined threshold; and

reconfiguring the TCP bi-flow session when the number or rate of TCP errors exceeds the predetermined threshold.

26. A method according to claim 25, wherein the TCP bi-flow route is associated with a forward flow and a return flow using the first and second network interfaces, and wherein reconfiguring the TCP bi-flow route comprises:

modifying the forward and return flows to utilize at least one network interface other than the first and second network interfaces; and

transmitting stateful routing session metadata in at least one session packet following such modifying of the forward and return flows.

27. A method according to claim 21, wherein detecting TCP errors based on the received and reference TCP sequence information comprises:

determining a location of TCP errors based on the received and reference TCP sequence information.

28. A method according to claim 27, wherein the process further comprises at least one of:

updating a routing table of the TCP augmented router based on the determined location of TCP errors;

or

selecting a route based on the determined location of TCP errors.

29. A method according to claim 21, wherein the process further comprises:

determining if a received session packet is outside of an advertised window size for the TCP bi-flow session based on received TCP sequence information from the received session packet and the reference TCP sequence information maintained in the bilateral TCP state record; and

dropping said packet without forwarding said packet when the bilateral TCP state machine determines that the received session packet is outside of the advertised window size for the TCP bi-flow session.

30. A method according to claim 21, wherein the process further comprises:

monitoring status of the TCP bi-flow session including determination of at least initiation, establishment, and termination of the TCP bi-flow session; and

storing statistical information related to the status of the TCP bi-flow session.