IP Library Granted Patent US 9,154,431
Granted Patent B2
US 9,154,431 · App. 13/889,420 · Granted Oct 6, 2015

System and method for managing bitrate on networks

Inventor: Scot Loach (Waterloo, CA)
Assignee: SANDVINE INCORPORATED ULC
H04L47/32
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 9,154,431
App. No.
13/889,420
Granted
Oct 6, 2015
Kind
B2
Abstract

A method and system for managing bitrate of network traffic are provided. The method for managing bitrate of network traffic includes: receiving a packet; retrieving metadata from the packet and associating the packet with at least one traffic aggregate; determining a drop rate for the at least one traffic aggregate based on network flow data; and determining, based on the drop rate and the metadata, to forward or drop the packet. The system includes a packet processing module configured to receive a packet; a deep packet inspection module configured to retrieve metadata from the packet and associate at least on traffic aggregate with the packet; a control module configured to determine a drop rate for the at least one traffic aggregate based on network flow data; and a policy decision module configure to determine whether to forward or drop the packet based on the drop rate and the metadata of the packet.

Claims (41)

1. A method for managing bitrate of network traffic comprising:

receiving a packet;

retrieving metadata from the packet, wherein the metadata comprises the direction of the packet, and associating the packet with at least one traffic aggregate;

determining a drop rate for the at least one traffic aggregate based on network flow data; and

determining, based on the drop rate and the direction of the packet,

to forward or drop the packet, wherein if the direction of the packet is in one direction, the packet is a candidate to be dropped to control an opposite direction bitrate of the network traffic.

2. The method of claim 1 wherein the packet direction is upstream and the packet is a candidate to be dropped to control the downstream bitrate of the network traffic.

3. The method of claim 1 wherein retrieving the metadata includes retrieving the protocol associated with the packet.

4. The method of claim 3 wherein if the protocol is a non-congestion controlled protocol, the packet is a candidate to be dropped, otherwise the packet is forwarded without management.

5. The method of claim 3 wherein if the protocol is User Datagram Protocol (UDP) the packet is a candidate to be dropped.

6. The method of claim 1 further comprising:

determining a bitrate of the at least one traffic aggregate; and

determining the drop rate for the at least on traffic aggregate based on the bitrate.

7. The method of claim 1 further comprising:

determining a quality score based on the metadata; and

determining the drop rate for the at least one traffic aggregate based on the quality score.

8. The method of claim 1 further comprising:

determining a maximum bitrate for the at least one traffic aggregate;

measuring a total bitrate of the network traffic; and

determining the drop rate for the at least one traffic aggregated based on maximum bitrate compared to the total bitrate.

9. The method of claim 1 wherein determining to drop the packet is a random drop decision.

10. The method of claim 1 wherein determining to drop the packet is based on protocol awareness.

11. The method of claim 1 further comprises determining if the dropping of the packets is reducing the bitrate at the traffic aggregate on the network.

12. A system for managing bitrate of network traffic comprising:

a packet processing module configured to receive a packet;

a deep packet inspection module configured to retrieve metadata from the packet, wherein the metadata comprises the direction of the packet, and

associate at least on traffic aggregate with the packet;

a control module configured to determine a drop rate for the at least one traffic aggregate based on network flow data; and

a policy decision module configure to determine whether to forward or drop the packet based on the drop rate and the direction of the packet wherein if the direction of the packet is in one direction, the packet is a candidate to be dropped to control an opposite direction bitrate of the network traffic.

13. The system of claim 12 wherein if the packet direction is upstream the packet is a candidate to be dropped to control the downstream bitrate of the network traffic.

14. The system of claim 12 wherein the deep packet inspection module is further configured to retrieve the protocol associated with the packet.

15. The system of claim 14 wherein if the protocol is a non-congestion controlled protocol, the packet is a candidate to be dropped, otherwise the packet is forwarded without management.

16. The system of claim 12 further comprising:

a signaling engine configured to determine a bitrate of the at least one traffic aggregate; and

the policy decision module configured to determine the drop rate for the at least on traffic aggregate based on the bitrate.

17. The system of claim 12 further comprising:

a signaling engine configured to determine a quality score based on the metadata; and

the policy decision module configured to determine the drop rate for the at least one traffic aggregate based on the quality score.

18. The system of claim 12 further comprising:

a signaling engine configured to determine a maximum bitrate for the at least one traffic aggregate and further configured to measure a total bitrate of the network traffic; and

the policy decision module configured to determine the drop rate for the at least one traffic aggregated based on maximum bitrate compared to the total bitrate.

Assignments (4)
MERGER Recorded Dec 7, 2018
From: SANDVINE CORPORATION; SANDVINE INCORPORATED ULC; SANDVINE LTD.; SANDVINE TECHNOLOGIES (CANADA) INC.
To: SANDVINE CORPORATION
Reel/Frame 047750/0077 →
MERGER Recorded Dec 7, 2018
From: PNI CANADA ACQUIRECO CORP.; SANDVINE CORPORATION
To: PNI CANADA ACQUIRECO CORP.
Reel/Frame 047750/0326 →
CHANGE OF NAME Recorded Dec 7, 2018
From: PNI CANADA ACQUIRECO CORP.
To: SANDVINE CORPORATION
Reel/Frame 048897/0558 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 8, 2013
From: LOACH, SCOT
To: SANDVINE INCORPORATED ULC
Reel/Frame 030371/0793 →
Continuity (1)
Related Publication 20140334302A1 · Nov 13, 2014