IP Library Granted Patent US 10,271,244
Granted Patent B2
US 10,271,244 · App. 14/977,984 · Granted Apr 23, 2019

System and method for managing traffic detection

Inventors: Said Zaghloul (Waterloo, CA); Yuval Lifshitz (Kfar Haoranim, IL)
Assignee: Sandvine Corporation
H04W28/10H04L41/0893H04L43/026H04L47/2441H04M15/66H04W4/24H04L43/12
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,271,244
App. No.
14/977,984
Granted
Apr 23, 2019
Kind
B2
Abstract

A method for managing traffic detection including: receiving predetermined traffic monitoring conditions; processing at least one packet to determine packet properties; determining an application identifier to associate with the traffic flow based on the packet properties; determining at least one policy to apply to the traffic flow based on the traffic monitoring conditions, packet properties and the application identifier; and communicating the at least one policy to be applied to the traffic flow. A system including: a traffic detection function (TDF) configured to receive predetermined traffic monitoring conditions, wherein the TDF includes: a processor configured to process at least one packet to determine packet properties; and a control engine configured to: determine an application identifier to associated with the flow; determine at least one policy to apply to the flow based on the traffic monitoring conditions, the packet properties and application identifier; and communicate the at least one policy.

Claims (29)

1. A method for managing traffic detection on a network comprising:

receiving, at a traffic detection function (TDF), predetermined traffic monitoring conditions;

retrieving and processing, at a processor associated with the TDF, at least one packet from a traffic flow of a subscriber to determine packet properties and a subscriber location associated with the at least one packet from the traffic flow, wherein the TDF retrieves the at least one packet between a Radio Access Network and a Core Network;

determining, at a control engine associated with the TDF, an application identifier to associate with the traffic flow based on the packet properties;

determining, at the control engine, at least one policy to apply to the traffic flow based on the traffic monitoring conditions, packet properties, subscriber location, and the application identifier; and

communicating the at least one policy to be applied to the traffic flow.

2. A method according to claim 1 , wherein the application identifier is a multi-dimensional application identifier, wherein the multi-dimensional application identifier comprises a definition of an application and characteristics of the subscriber's traffic flow.

3. A method according to claim 2 , wherein the characteristics of the subscriber's traffic flow of the multi-dimensional application identifier indicates whether the traffic flow is associated with a tethered device.

4. A method according to claim 2 , further comprising determining at least one multi-dimensional policy to be applied to the traffic based at least in part on the multi-dimensional application identifier.

5. A method according to claim 2 , wherein the characteristics of the subscriber's traffic comprise: charging condition, subscriber's device; subscriber cell location.

6. A method according to claim 5 , further comprising determining at least one personalized subscriber notification based at least in part on the multi-dimensional application identifier.

7. A method according to claim 1 , wherein communicating the at least one policy comprises communicating a request to create a new charging session for the traffic flow.

8. A method according to claim 1 , wherein, if the processor determines a change in subscriber location, the method further comprises creating a new charging session for the subscriber.

9. A method according to claim 1 , further comprising reporting the application identifier to a network operator.

10. A method according to claim 1 , further comprising determining at least one policy based on the subscriber location.

11. A method according to claim 1 , wherein retrieving the at least one packet between a Radio Access Network and a Core Network reduces the signaling flow within the Core Network.

12. A system for managing traffic detection on a network comprising:

a traffic detection function (TDF) configured to receive predetermined traffic monitoring conditions, wherein the TDF comprises:

a processor configured to retrieve and process at least one packet from a traffic flow of a subscriber to determine packet properties and a subscriber location associated with the at least one packet from the traffic flow, wherein the TDF retrieves the at least one packet between a Radio Access Network and a Core Network; and

a control engine configured to:

determine an application identifier to associated with the traffic flow based on the packet properties;

determine at least one policy to apply to the traffic flow based on the traffic monitoring conditions, the packet properties, the subscriber location, and application identifier; and

communicate the at least one policy to apply to the traffic flow.

13. A system according to claim 12 , wherein the application identifier is a multi-dimensional application identifier, wherein the multi-dimensional application identifier comprises a definition of an application and characteristics of the subscriber's traffic flow.

14. A system according to claim 13 , wherein the characteristics of the subscriber's traffic flow of the multi-dimensional application identifier indicates whether the traffic flow is associated with a tethered device.

15. A system according to claim 12 , wherein the control engine is further configured to communicate a request to create a new charging session for the traffic flow.

16. A system according to claim 12 , wherein, if the processor determines a change in the subscriber location, the control engine is configured to communicate at least one policy to create a new charging session for the subscriber.

17. A system according to claim 12 , wherein the control engine is configured to report the application identifier to a network operator.

18. A system according to claim 12 , wherein the control engine is configured to associate the subscriber location with the packet and determine at least one policy based on the subscriber location.

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 Dec 22, 2015
From: ZAGHLOUL, SAID; LIFSHITZ, YUVAL
To: SANDVINE INCORPORATED ULC
Reel/Frame 037348/0494 →
Continuity (1)
Related Publication 20170181037A1 · Jun 22, 2017