Service latency monitoring using two way active measurement protocol

Patent metadata

Field	Value
Publication number	US-9705769-B1
Application number	US-201414573167-A
Country	US
Kind code	B1
Filing date	Dec 17, 2014
Priority date	Dec 17, 2014
Publication date	Jul 11, 2017
Grant date	Jul 11, 2017

Abstract

A device may establish a communication session, with a client device, for monitoring a latency of a service. The device may receive, from the client device, a request for a monitored service list. The monitored service list may identify one or more services for which service latency monitoring is supported. The device may provide, to the client device, the monitored service list. The device may receive, from the client device, a service latency monitoring session request that may identify the service to be monitored. The device may establish, with the client device, the service latency monitoring session based on the service latency monitoring session request. The device may cause the service to be performed. The device may generate information for determining the latency of the service. The device may transmit, to the client device and via the service latency monitoring session, the information for determining the latency of the service.

First claim

What is claimed is:

1. A device, comprising:
one or more processors to:
establish a communication session, with a client device, for monitoring a latency of a service;
receive, from the client device, a request for a monitored service list,
the monitored service list identifying one or more services for which service latency monitoring is supported;

provide, to the client device and based on the request for the monitored service list, the monitored service list;
receive, from the client device, a service latency monitoring session request,
the service latency monitoring session request identifying the service to be monitored,
the service being included in the monitored service list;

establish, with the client device, a service latency monitoring session based on the service latency monitoring session request;
cause the service to be performed;
generate information for determining the latency of the service,
the one or more processors, when generating the information, being to:
receive, at a first receipt time and from the client device, a packet,
 the packet being associated with a first time stamp,
associate, with the packet, a second time stamp,
 the second time stamp representing the first receipt time of the packet,
associate, with the packet, a third time stamp,
 the third time stamp representing a first transmission time of the packet,
transmit, at the first transmission time and to a particular device associated with performing the service, the packet,
receive, at a second receipt time, the packet from the particular device after the particular device has performed the service,
associate, with the packet, a fourth time stamp, and
 the fourth time stamp representing the second receipt time of the packet,
associate, with the packet, a fifth time stamp,
 the fifth time stamp representing a second transmission time of the packet; and

transmit, at the second transmission time, to the client device and via the service latency monitoring session, the packet and the information for determining the latency of the service, the information for determining the latency of the service including:
the first time stamp,
the second time stamp,
the third time stamp,
the fourth time stamp, and
the fifth time stamp.

2. The device of claim 1 , where the service latency monitoring session request identifies a plurality of services;
where the one or more processors, when generating the information, are to:
generate the information for determining a plurality of latencies of the plurality of services; and

where the one or more processors, when transmitting the information, are to:
transmit, to the client device and via the service latency monitoring session, the information for determining the plurality of latencies of the plurality of services.

3. The device of claim 1 , where the one or more processors, when generating the information, are to:
determine, based on the information, the latency of the service; and
where the one or more processors, when transmitting the information, are to:
transmit, to the client device, information indicating the latency of the service.

4. The device of claim 1 , where the one or more processors, when establishing the communication session, are to:
receive, from the client device, a session mode identifier,
the session mode identifier identifying a session mode,
the session mode supporting the service latency monitoring, and
the session mode allowing message authentication, and

the session mode identifier including a security key,
the message authentication being based on the security key; and

where the one or more processors, when transmitting, to the client device, the information for determining the latency, are to:
transmit, with the information for determining the latency of the service, a message authentication code,
the message authentication code being based on the security key, and
the message authentication code being used to authenticate the information.

5. The device of claim 1 , where the one or more processors, when establishing the communication session, are to:
receive, from the client device, a session mode identifier,
the session mode identifier identifying a session mode,
the session mode supporting the service latency monitoring, and
the session mode allowing encryption, and

the session mode identifier including a security key,
the encryption being based on the security key; and

where the one or more processors, when transmitting, to the client device, the information for determining the latency, are to:
encrypt the information based on the security key.

6. The device of claim 1 , where the service latency monitoring session further comprises a two-way active measurement protocol (TWAMP) session.

7. A computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
establish, with a client device, a communication session for monitoring latency of a service;
provide, to the client device and via the communication session, a monitored service list,
the monitored service list identifying one or more services for which latency monitoring is supported;

receive, from the client device, a request for a latency monitoring session,
the request for the latency monitoring session identifying the service to be monitored;

establish, with the client device, the latency monitoring session;
receive, from the client device, a packet,
the packet being encapsulated in a two way active measurement protocol (TWAMP) header,
the TWAMP header indicating that the packet is associated with the latency monitoring session;

generate, based on the TWAMP header, a packet identifier,
the packet identifier identifying the packet;

remove, from the packet, the TWAMP header;
attach, to the packet, the packet identifier;
associate, with the packet, a first time stamp,
the first time stamp representing a provision time of the packet;

provide, at the provision time and to a particular device associated with performing the service, the packet;
cause the service to be performed by the particular device;
receive, at a receipt time, the packet, from the particular device after the particular device has performed the service,
the packet being identified based on the packet identifier;

associate, with the packet, a second time stamp,
the second time stamp representing the receipt time of the packet;

determine the latency of the service based on the first time stamp and the second time stamp; and
provide, to the client device, the packet and information identifying the latency of the service.

8. The computer-readable medium of claim 7 , where the one or more instructions, that cause the one or more processors to establish the communication session, cause the one or more processors to:
receive, from the client device, a session mode identifier,
the session mode identifier identifying a session mode,
the session mode supporting latency monitoring of the service, and
the session mode allowing message authentication, and

the session mode identifier including a security key,
the message authentication being based on the security key; and

where the one or more instructions, that cause the one or more processors to provide, to the client device, the information for determining the latency, are to:
provide, with the information for determining the latency of the service, a message authentication code,
the message authentication code being based on the security key, and
the message authentication code being used to authenticate the information.

9. The compute

Assignees

• Juniper Networks Inc

Inventors

• Sarangapani Srivathsa
• Gupta Peyush
• Agarwal Amit Kumar

Classifications

• H04L9/3242

  involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC · CPC title

• H04L9/3297

  involving time stamps, e.g. generation of time stamps · CPC title

• H04L43/0864 Primary

  Round trip delays · CPC title

• H04L67/141

  Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title

• H04L43/106

  using time related information in packets, e.g. by adding timestamps · CPC title