IP Library Granted Patent US 10,355,944
Granted Patent B2
US 10,355,944 · App. 15/799,303 · Granted Jul 16, 2019

Minimally invasive monitoring of path quality

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,355,944
App. No.
15/799,303
Granted
Jul 16, 2019
Kind
B2
Abstract

Systems and techniques are described for performing minimally invasive monitoring of path quality in a network. Specifically, path quality requests and measurements can be piggy-backed on the data traffic that is flowing through a secure connection between two network nodes. For example, path quality requests and measurements can be inserted into the TFC padding field of IP/ESP packets that are being communicated between two IPsec devices. The disclosed embodiments ensure that the number/frequency of measurements increases/decreases naturally in proportion to the amount of traffic flowing, and that the measurement data does not get differential treatment in the network as they are intrinsically bound to the data packets being monitored.

Claims (50)

1. A method for monitoring path quality, the method comprising:

adding, by a source node, a path quality record to a first Traffic Flow Confidentiality (TFC) padding field of a first Internet Protocol (IP)/Encapsulated Security Payload (ESP) packet;

sending, by the source node, the first IP/ESP packet to a destination node;

receiving, by the source node, a second IP/ESP packet from the destination node;

extracting, by the source node, a response path quality record from a second TFC padding field of the second IP/ESP packet; and

determining, by the source node, a path quality metric based on the response path quality record.

2. The method of claim 1 , wherein the path quality record includes a path identifier that corresponds to a network path, a class identifier that corresponds to a Quality of Service (QoS) class, and a sequence number that is used to distinguish between distinct path quality records.

3. The method of claim 2 , wherein the path quality metric is an IP/ESP packet throughput value corresponding to the network path and the QoS class.

4. The method of claim 2 , wherein the path quality metric is an IP/ESP packet loss value corresponding to the network path and the QoS class.

5. The method of claim 1 , wherein the path quality record includes (1) a latency measurement request, and (2) a first timestamp when the first IP/ESP packet was sent by the source node.

6. The method of claim 5 , wherein the response path quality record includes (1) the first timestamp when the first IP/ESP packet was sent by the source node, (2) a second timestamp when the first IP/ESP packet was received by the destination node, (3) a third timestamp when the second IP/ESP packet was sent by the destination node, and (4) a fourth timestamp when the second IP/ESP packet was received by the source node.

7. The method of claim 6 , wherein the path quality metric is a round trip delay time value corresponding to a network path and a QoS class.

8. The method of claim 6 , wherein system clocks of the source node and the destination node are synchronized, and wherein the path quality metric is a one-way latency value corresponding to a network path and a QoS class.

9. The method of claim 6 , wherein the path quality metric is a jitter value corresponding to a network path and a QoS class.

10. The method of claim 1 , comprising:

receiving, by the destination node, the first IP/ESP packet from the source node;

extracting, by the destination node, the path quality record from the first TFC padding field of the first IP/ESP packet;

using, by the destination node, the path quality record to determine path quality measurement data corresponding to a network path and a QoS class;

creating, by the destination node, the response path quality record, wherein the response path quality record includes the path quality measurement data;

adding, by the destination node, the response path quality record to the second TFC padding field of the second IP/ESP packet; and

sending, by the destination node, the second IP/ESP packet to the source node.

11. The method of claim 10 , wherein the path quality measurement data includes an IP/ESP packet throughput value corresponding to the network path and the QoS class.

12. The method of claim 10 , wherein the path quality measurement data includes an IP/ESP packet loss value corresponding to the network path and the QoS class.

13. The method of claim 10 , wherein the path quality measurement data includes (1) a first timestamp corresponding to when the first IP/ESP packet was received at the destination node, and (2) a second timestamp corresponding to when the second IP/ESP packet was sent to the source node.

14. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor in a source node, cause the source node to perform a method for monitoring path quality, the method comprising:

adding a path quality record to a first Traffic Flow Confidentiality (TFC) padding field of a first Internet Protocol (IP)/Encapsulated Security Payload (ESP) packet;

sending the first IP/ESP packet to a destination node;

receiving a second IP/ESP packet from the destination node;

extracting a response path quality record from a second TFC padding field of the second IP/ESP packet; and

determining a path quality metric based on the response path quality record.

15. The non-transitory computer-readable storage medium of claim 14 , wherein the path quality record includes a path identifier that corresponds to a network path, a class identifier that corresponds to a Quality of Service (QoS) class, and a sequence number that is used to distinguish between distinct path quality records.

16. The non-transitory computer-readable storage medium of claim 14 , wherein the path quality record includes (1) a latency measurement request, and (2) a first timestamp when the first IP/ESP packet was sent by the source node.

17. The non-transitory computer-readable storage medium of claim 16 , wherein the response path quality record includes (1) the first timestamp when the first IP/ESP packet was sent by the source node, (2) a second timestamp when the first IP/ESP packet was received by the destination node, (3) a third timestamp when the second IP/ESP packet was sent by the destination node, and (4) a fourth timestamp when the second IP/ESP packet was received by the source node.

18. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor in a destination node, cause the destination node to perform a method for monitoring path quality, the method comprising:

receiving a first Internet Protocol (IP)/Encapsulated Security Payload (ESP) packet from a source node;

extracting a path quality record from a first Traffic Flow Confidentiality (TFC) padding field of the first IP/ESP packet;

using the path quality record to determine path quality measurement data corresponding to a network path and a Quality of Service (QoS) class;

creating a response path quality record, wherein the response path quality record includes the path quality measurement data;

adding the response path quality record to a second TFC padding field of a second IP/ESP packet; and

sending the second IP/ESP packet to the source node.

19. The non-transitory computer-readable storage medium of claim 18 , wherein the path quality record includes a path identifier that corresponds to the network path, a class identifier that corresponds to a the QoS class, and a sequence number that is used to distinguish between distinct path quality records.

20. The non-transitory computer-readable storage medium of claim 18 , wherein the path quality record includes (1) a latency measurement request, and (2) a first timestamp when the first IP/ESP packet was sent by the source node, and wherein the response path quality record includes (1) the first timestamp when the first IP/ESP packet was sent by the source node, (2) a second timestamp when the first IP/ESP packet was received by the destination node, (3) a third timestamp when the second IP/ESP packet was sent by the destination node, and (4) a fourth timestamp when the second IP/ESP packet was received by the source node.

21. An apparatus, comprising:

a processor; and

a non-transitory storage medium storing instructions that, when executed by the processor, cause the processor to monitor path quality by performing a set of operations, comprising:

adding a path quality record to a first Traffic Flow Confidentiality (TFC) padding field of a first Internet Protocol (IP)/Encapsulated Security Payload (ESP) packet;

sending the first IP/ESP packet to a destination node;

receiving a second IP/ESP packet from the destination node;

extracting a response path quality record from a second TFC padding field of the second IP/ESP packet; and

determining a path quality metric based on the response path quality record.

Assignments (14)
RELEASE OF SECURITY INTEREST Recorded Aug 11, 2023
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC; RIVERBED HOLDINGS, INC.
Reel/Frame 064673/0739 →
CHANGE OF NAME Recorded Feb 18, 2022
From: RIVERBED TECHNOLOGY, INC.
To: RIVERBED TECHNOLOGY LLC
Reel/Frame 059232/0551 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0046 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0169 →
SECURITY INTEREST Recorded Dec 10, 2021
From: RIVERBED TECHNOLOGY LLC (FORMERLY RIVERBED TECHNOLOGY, INC.); ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
Reel/Frame 058486/0216 →
PATENT SECURITY AGREEMENT Recorded Oct 27, 2021
From: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 057943/0386 →
PATENT SECURITY AGREEMENT SUPPLEMENT - SECOND LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 057810/0559 →
PATENT SECURITY AGREEMENT SUPPLEMENT - FIRST LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 057810/0502 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORED AT REEL 056397, FRAME 0750 Recorded Oct 13, 2021
From: MACQUARIE CAPITAL FUNDING LLC
To: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 057983/0356 →
SECURITY INTEREST Recorded May 26, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MACQUARIE CAPITAL FUNDING LLC
Reel/Frame 056397/0750 →
PATENT SECURITY AGREEMENT Recorded Mar 5, 2021
From: RIVERBED TECHNOLOGY, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 055514/0249 →
PATENT SECURITY AGREEMENT Recorded Jul 10, 2019
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 049720/0808 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 20, 2017
From: FITZGIBBON, JOHN G.
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 044177/0624 →