Lightweight flow reporting in constrained networks

• US 9,923,832 B2
• Filed: 07/21/2014
• Issued: 03/20/2018
• Est. Priority Date: 07/21/2014
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Wetterwald, Patrick, Thubert, Pascal, Vasseur, Jean-Philippe
• Primary Examiner(s): Moutaouakil, Mounir
• Application Number:
  US14/336,175
• Publication Number:
  US 20160021014A1
• Time in Patent Office: 1,338 Days
• CPC Class Codes: H04L 45/48 Routing tree calculation
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/2483 involving identification of individual flows
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

In one embodiment, a device in a network receives one or more packets that are part of a traffic flow. The device provides a sample packet to a path computation element (PCE) that includes a signature that uniquely identifies the traffic flow. The device receives a traffic flow policy for the traffic flow from a policy engine and enforces the traffic flow policy for the traffic flow.

Claims

1. A method, comprising:

receiving, at a device in a low power and lossy network (LLN), one or more packets that are part of a traffic flow;

providing, by the device, a sample packet including a packet header to a path computation element (PCE), wherein the sample packet includes a flow signature and flow description computed by one or more nodes in the LLN and inserted into the packet header, wherein the flow signature and flow description are different, the signature uniquely identifying the traffic flow;

receiving, at the device, a traffic flow policy for the traffic flow from a policy engine; and

enforcing, by the device, the traffic flow policy for the traffic flow.

2. The method as in claim 1, further comprising:

identifying, by the device, the traffic flow as a new traffic flow based on the signature.

3. The method as in claim 1, wherein the signature comprises a hash value that uniquely identifies a type and a source of the traffic flow.

4. The method as in claim 1, wherein one or more quality of service (QoS) parameters are included in a header of the sample packet.

5. The method as in claim 1, wherein the traffic flow policy for the traffic flow is enforced by at least one of:

imposing a traffic flow rate on the traffic flow, dropping packets of the traffic flow, adjusting a channel hopping schedule used by one or more nodes associated with the traffic flow, or causing the traffic flow to be rerouted.

6. The method as in claim 1, further comprising:

receiving, from the PCE, data indicative of a sample rate for the traffic flow;

and wherein providing the sample packet to the PCE comprises;

sending, by the device, sample packets of the traffic flow to the PCE according to the received sample rate.

7. A method, comprising:

generating, by a device in an LLN, a flow signature for a particular traffic flow;

generating, by the device, a flow description for the traffic flow, wherein the flow signature and flow description are different;

inserting, by the device, the flow signature and description into a header of a packet belonging to the traffic flow; and

sending, by the device, the packet to another device in the LLN for providing to a PCE.

8. The method as in claim 7, wherein the other device is the PCE.

9. The method as in claim 7, wherein the signature comprises a hash value that uniquely identifies a type and a source of the traffic flow.

10. The method as in claim 7, wherein the flow description includes one or more quality of service (QoS) parameters.

11. A method, comprising:

receiving, at a device, a sample packet including a packet header that is part of a traffic flow in an LLN, the sample packet including a flow signature and a flow description computed by one or more nodes in the LLN and inserted into the packet header, wherein the flow signature and flow description are different, the signature uniquely identifying the traffic flow;

inspecting, by the device, the sample packet to identify properties of the traffic flow;

generating, by the device, flow data based on the identified properties of the traffic flow; and

providing, by the device, the flow data to a network traffic policy engine.

12. The method as in claim 11, further comprising:

determining, by the device, a packet sampling rate for the traffic flow; and

providing, by the device, a packet sampling strategy to the one or more network nodes based on the determined sampling rate.

13. The method as in claim 12, wherein the packet sampling rate is determined based on a traffic policy associated with the traffic flow.

14. The method as in claim 12, wherein the packet sampling rate is based on measured traffic congestion in the network.

15. An apparatus, comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

receive one or more packets that are part of a traffic flow in an LLN;

provide a sample packet including a packet header to a path computation element (PCE), wherein the sample packet includes a flow signature and flow description computed by one or more nodes in the LLN and inserted into the packet header, wherein the flow signature and flow description are different, the signature uniquely identifying the traffic flow;

receive a traffic flow policy for the traffic flow from a policy engine; and

enforce the traffic flow policy for the traffic flow.

16. The apparatus as in claim 15, wherein the process when executed is further operable to:

identify the traffic flow as a new traffic flow based on the signature.

17. The apparatus as in claim 15, wherein the signature comprises a hash value that uniquely identifies a type and a source of the traffic flow.

18. The apparatus as in claim 15, wherein one or more quality of service (QoS) parameters are included in a header of the sample packet.

19. The apparatus as in claim 15, wherein the traffic flow policy for the traffic flow is enforced by at least one of:

imposing a traffic flow rate on the traffic flow, dropping packets of the traffic flow, adjusting a channel hopping schedule used by one or more nodes associated with the traffic flow, or causing the traffic flow to be rerouted.

20. The apparatus as in claim 15, wherein the process when executed is further operable to:

receive, from the PCE, data indicative of a sample rate for the traffic flow; and

send sample packets of the traffic flow to the PCE according to the received sample rate.

21. An apparatus, comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

generate a flow signature for a particular traffic flow in an LLN;

generate a flow description for the traffic flow, wherein the flow signature and flow description are different;

insert the flow signature and description into a header of a packet belonging to the traffic flow; and

send the packet to another device in the LLN for providing to a PCE.

22. The apparatus as in claim 21, wherein the other device is the PCE.

23. The apparatus as in claim 21, wherein the flow signature comprises a hash value that uniquely identifies a type and a source of the traffic flow.

24. The apparatus as in claim 21, wherein the flow description includes one or more quality of service (QoS) parameters.

25. An apparatus, comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

receive a sample packet including a packet header that is part of a traffic flow in an LLN, the sample packet including a flow signature and a flow description computed by one or more nodes in the LLN and inserted into the packet header, wherein the flow signature and flow description are different, the signature uniquely identifying the traffic flow;

inspect the sample packet to identify properties of the traffic flow;

generate flow data based on the identified properties of the traffic flow; and

provide the flow data to a network traffic policy engine.

26. The apparatus as in claim 25, wherein the process when executed is further operable to:

determine a packet sampling rate for the traffic flow; and

provide a packet sampling strategy to the one or more network nodes based on the determined sampling rate.

27. The apparatus as in claim 26, wherein the packet sampling rate is determined based on a traffic policy associated with the traffic flow.

28. The apparatus as in claim 26, wherein the packet sampling rate is based on measured traffic congestion in the network.