Subscriber-aware TWAMP data monitoring in computer networks
Techniques are described for performing subscriber aware two-way active measurement protocol (TWAMP) data session provisioning between two endpoints in a computer network. For example, the disclosed techniques include extending TWAMP control messaging to include a communication mode for negotiating subscriber-aware TWAMP data monitoring. If the communication mode is supported by both endpoints, a subscriber identifier is specified when a TWAMP data session is provisioned (negotiated) over the control session. The disclosed techniques further include extending TWAMP data messaging to include the subscriber identifier in each test packet for the data session. In this way, each of the endpoints may identify a subscriber corresponding to one or more received TWAMP test packets based on the subscriber identifier included in the received TWAMP test packets.
1. A method comprising:
establishing a control connection between a two-way active measurement protocol (TWAMP) control client and a TWAMP server;
negotiating, by the TWAMP control client and the TWAMP server over the control connection, a data session between a TWAMP session sender executed on a first network device and a TWAMP session reflector executed on a second network device, wherein negotiating the data session includes specifying a subscriber identifier to an individual subscriber of a service provider network; and
exchanging one or more TWAMP test packets for the data session between the TWAMP session sender and the TWAMP session reflector, each of the one or more TWAMP test packets including the subscriber identifier of the subscriber.
2. The method of claim 1 , wherein negotiating the data session comprises receiving, with the TWAMP server and from the TWAMP control client, a TWAMP session request that specifies the subscriber identifier for the individual subscriber.
3. The method of claim 2 , wherein the TWAMP session request includes a subscriber identifier type field that specifies the subscriber identifier for the individual subscriber.
4. The method of claim 3 , wherein the subscriber identifier type field specifies one of an (IMSI), an International Mobile Equipment Identity (IMEI), an accounting identifier or an IP address for the individual subscriber.
5. The method of claim 1 , wherein establishing the control connection comprises:
sending, by the TWAMP server and to the TWAMP control client, a greeting message that identifies a plurality of communication modes that are supported by the TWAMP server, wherein one of the plurality of communication modes indicates that subscriber-aware data sessions are supported by the TWAMP server; and
receiving, by the TWAMP server and from the TWAMP control client, a set up message that identifies at least one of the plurality of communication modes that is also supported by the TWAMP control client, wherein the at least one of the plurality of communication modes indicates that subscriber-aware data sessions are supported by the TWAMP control client.
6. The method of claim 1 , wherein establishing the control connection comprises:
receiving, by the TWAMP control client and from the TWAMP server, a greeting message that identifies a plurality of communication modes that are supported by the TWAMP server, wherein one of the plurality of communication modes indicates that subscriber-aware data sessions are supported by the TWAMP server;
selecting, by the TWAMP control client, at least one of the plurality of communication modes that is also supported by the TWAMP control client; and
sending, by the TWAMP control client and to the TWAMP server, a set up message that identifies the at least one of the plurality of communication modes, wherein the at least one of the plurality of communication modes indicates that subscriber-aware data sessions are supported by the TWAMP control client.
7. The method of claim 1 , wherein exchanging the one or more TWAMP test packets for the data session comprises:
receiving, by the TWAMP session reflector, the one or more TWAMP test packets for the data session from the TWAMP session sender, each of the one or more TWAMP test packets including the subscriber identifier associated with the data session; and
sending, by the TWAMP session reflector, the one or more TWAMP test packets back to the TWAMP session sender, each of the one or more TWAMP test packets including the subscriber identifier associated with the data session and at least one metric for the data session used to measure network performance between the first network device and the second network device.
8. The method of claim 7 , further comprising, for each of the one or more TWAMP test packets and prior to sending the one or more TWAMP test packets back to the TWAMP session sender:
extracting, by the TWAMP session reflector, a subscriber packet embedded within a payload of the respective TWAMP test packet;
selecting, based on the subscriber identifier associated with the data session, a network service;
directing the subscriber packet to be processed by the selected network service;
receiving a processed subscriber packet from the network service after processing by the network service; and
sending, by the TWAMP session reflector, the respective TWAMP test packet back to the TWAMP session sender in response to receive the processed subscriber packet from the network service.
9. The method of claim 8 , further comprising, for each of the one or more TWAMP test packets and prior to sending the one or more TWAMP test packets back to the TWAMP session sender:
setting a timestamp within the TWAMP test packet indicating when the TWAMP test packet was received by the TWAMP session reflector;
setting a timestamp within the TWAMP test packet indicating when the subscriber packet of the TWAMP test packet was directed by the TWAMP session reflector to the selected network service;
setting a timestamp within the TWAMP test packet indicating when the processed subscriber packet was received back from the network service by the TWAMP session reflector; and
setting a timestamp within the TWAMP test packet indicating when the TWAMP test packet was send by the TWAMP session reflector to the TWAMP session sender.
10. The method of claim 1 , wherein exchanging the one or more TWAMP test packets for the data session comprises:
sending, by the TWAMP session sender, the one or more TWAMP test packets for the data session to the TWAMP session reflector, each of the one or more TWAMP test packets including the subscriber identifier;
receiving, by the TWAMP session sender, the one or more TWAMP test packets back from the TWAMP session reflector, each of the one or more TWAMP test packets including the subscriber identifier and at least one metric for the data session used to measure network performance between the first network device and the second network device; and
associating, by the TWAMP session sender, the one or more TWAMP test packets with the subscriber of the service provider network based on the subscriber identifier included in the one or more TWAMP test packets.
11. The method of claim 10 ,
wherein each of the one or more TWAMP test packets sent by the TWAMP session sender to the TWAMP session reflector includes a subscriber packet embedded within a payload of the respective TWAMP test packet,
wherein each of the TWAMP test packets received by the TWAMP session sender from the TWAMP session reflector includes:
a timestamp within the TWAMP test packet indicating when the TWAMP test packet was received by the TWAMP session reflector,
a timestamp within the TWAMP test packet indicating when the subscriber packet embedded of the TWAMP test packet was extracted and directed by the TWAMP session reflector to a network service for processing,
a timestamp within the TWAMP test packet indicating when a processed subscriber packet was received back from the network service by the TWAMP session reflector, and
a timestamp within the TWAMP test packet indicating when the TWAMP test packet was sent by the TWAMP session reflector back to the TWAMP session sender.
12. A network device comprising:
a memory; and
one or more processors in communication with the memory and executing a two-way active measurement protocol (TWAMP) control client and a TWAMP session sender, the one or more processors configured to:
establish a control connection between the TWAMP control client and a TWAMP server,
negotiate a data session between the TWAMP session sender and a TWAMP session reflector executed on a second network device, wherein negotiating the data session includes specifying a subscriber identifier for an individual subscriber of a service provider network,
send the one or more TWAMP test packets for the data session to the TWAMP session reflector, each of the one or more TWAMP test packets including the subscriber identifier, and
receive the one or more TWAMP test packets back from the TWAMP session reflector, each of the one or more TWAMP test packets including the subscriber identifier and at least one metric for the data session used to measure network performance between the first network device and the second network device.
13. The network device of claim 12 ,
wherein each of the one or more TWAMP test packets sent by the TWAMP session sender to the TWAMP session reflector includes a subscriber packet embedded within a payload of the respective TWAMP test packet,
wherein each of the TWAMP test packets received by the TWAMP session sender from the TWAMP session reflector includes:
a timestamp within the TWAMP test packet indicating when the TWAMP test packet was received by the TWAMP session reflector,
a timestamp within the TWAMP test packet indicating when the subscriber packet of the TWAMP test packet was directed by the TWAMP session reflector to a network service for processing,
a timestamp within the TWAMP test packet indicating when the processed subscriber packet was received back from the network service by the TWAMP session reflector, and
a timestamp within the TWAMP test packet indicating when the TWAMP test packet was sent by the TWAMP session reflector back to the TWAMP session sender.
14. A network device comprising:
a memory; and
one or more processors in communication with the memory and executing a two-way active measurement protocol (TWAMP) server and a TWAMP session reflector, the one or more processors configured to:
establish a control connection between the TWAMP server and a TWAMP control client,
receive, with the TWAMP server and from the TWAMP control client, a TWAMP session request for a data session between the TWAMP session reflector and a TWAMP session sender executed on a second network device, wherein the TWAMP session request specifies a subscriber identifier to an individual subscriber of a service provider network,
receive one or more TWAMP test packets for the data session by the TWAMP session reflector from the TWAMP session sender, each of the one or more TWAMP test packets including the subscriber identifier associated with the data session, and
send, by the TWAMP session reflector, the one or more TWAMP test packets back to the TWAMP session sender, each of the one or more TWAMP test packets including the subscriber identifier associated with the data session and at least one metric for the data session used to measure network performance between the network device and the second network device.
15. The network device of claim 14 , wherein the processor is further configured to, for each of the one or more TWAMP test packets and prior to sending the one or more TWAMP test packets back to the TWAMP session sender:
extract a subscriber packet embedded within a payload of the respective TWAMP test packet,
select, based on the subscriber identifier associated with the data session, a network service,
direct the subscriber packet to be processed by the selected network service,
receive a processed subscriber packet from the network service after processing by the network service, and
send the respective TWAMP test packet back to the TWAMP session sender in response to receive the processed subscriber packet from the network service.
16. The network device of claim 15 , wherein the processor is further configured to, for each of the one or more TWAMP test packets and prior to sending the one or more TWAMP test packets back to the TWAMP session sender:
set a timestamp within the TWAMP test packet indicating when the TWAMP test packet was received by the TWAMP session reflector,
set a timestamp within the TWAMP test packet indicating when the subscriber packet of the TWAMP test packet was directed by the TWAMP session reflector to the selected network service,
set a timestamp within the TWAMP test packet indicating when the processed subscriber packet was received back from the network service by the TWAMP session reflector, and
set a timestamp within the TWAMP test packet indicating when the TWAMP test packet was sent by the TWAMP session reflector to the TWAMP session sender.
17. The network device of claim 15 , wherein TWAMP session request includes a service identifier specifying the network service to apply the subscriber packets embedded within the TWAMP test packets sent over the data session.