Method and an Arrangement of Identifying Traffic Flows in a Communication Network

• US 20120072612A1
• Filed: 12/23/2008
• Published: 03/22/2012
• Est. Priority Date: 12/23/2008
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Flinta, Christofer, Mängs, Jan-Erik, Melander, Bob
• Application Number:
  US13/141,501
• Publication Number:
  US 20120072612A1
• Time in Patent Office: Days
• US Class Current: 709/235
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]

Abstract

A method of identifying traffic flows is provided in a traffic generating node, where each traffic flow is being associated with an application process running on the traffic generating node. The method is configured to perform a mapping operation, such that an application process is being linked to a signature that uniquely identifies a traffic flow and an associated socket, and such that the obtained linked information is maintained in a list. The mapping operation is configured to be executed in response to recognising a change to a socket associated with the application process at the traffic generating node. Based on accumulated mapping information, one or more processing element located at the traffic generating node, or at another node, may classify and/or control traffic flows associated with any of the application processes of the traffic generating node.

Claims

1-25. -25. (canceled)

26. A method of identifying traffic flows in a traffic generating node, each traffic flow being associated with a respective application process running on said traffic generating node, said method comprising:

recognizing a change to a socket associated with an application process; and

performing a mapping operation with respect to that application process responsive to recognizing said change, wherein performing said mapping operation comprises linking the application process to a signature that uniquely identifies a traffic flow and an associated socket, and maintaining information regarding said linking in a list.

27. The method according to claim 26, wherein said signature is based on information associated with said socket.

28. The method according to claim 27, wherein said information comprises an indication of a protocol used by the respective application process, a source Internet Protocol (IP) address, a source port, a destination IP address, and a destination port associated with said socket.

29. The method according to claim 27, wherein recognizing a change to a socket associated with an application process comprises recognizing that a socket has been created by the application process, and wherein performing said mapping operation further comprises generating said signature.

30. The method according to claim 27, wherein recognizing a change to a socket associated with an application process comprises recognizing that a socket has been removed by the application process, and wherein performing said mapping operation further comprises removing a respective entry of said list.

31. The method according to claim 26, wherein said recognizing comprises monitoring said application process for socket related changes.

32. The method according to claim 26, wherein said recognizing comprises receiving a notification of a socket related change from said application process.

33. The method according to claim 26, further comprising classifying at least one of said one or more traffic flows on the basis of accumulated content of said list and at least one predefined classification rule.

34. The method according to claim 33, wherein said classifying is executed by at least one processing element of said traffic generating node.

35. The method according to claim 26, further comprising controlling at least one of said one or more traffic flows on the basis of accumulated content of said list and at least one predefined rule.

36. The method according to claim 35, wherein said controlling is executed by at least one processing element of said traffic generating node.

37. The method according to claim 26, further comprising, each time a mapping operation has been performed:

generating a notification comprising the content of a mapping entry created or updated in said list by way of said mapping operation, and

forwarding said notification to at least one server, thereby enabling said server to create and maintain a copy of said list.

38. A method implemented by a server for classifying traffic flows transmitted to or received from a traffic generating node, wherein the server comprises at least one processing element, wherein the method comprises:

maintaining a copy of a list created by the traffic generating node, wherein the list contains accumulated content regarding linking of each of one or more application processes running on the traffic generating node to a respective signature that uniquely identifies a traffic flow and an associated socket, wherein said maintaining comprises receiving one or more notifications from the traffic generating node comprising the content of one or more mapping entries created or updated in said list by the traffic generating node; and

classifying traffic flows on the basis of at least one predefined rule and the accumulated content of said list .

39. A method implemented by a server for controlling traffic flows transmitted to or received from a traffic generating node, wherein the server comprises at least one processing element, wherein the method comprises:

maintaining a copy of a list created by the traffic generating node, wherein the list contains accumulated content regarding linking of each of one or more application processes running on the traffic generating node to a respective signature that uniquely identifies a traffic flow and an associated socket, wherein said maintaining comprises receiving one or more notifications from the traffic generating node comprising the content of one or more mapping entries created or updated in said list by the traffic generating node; and

controlling traffic flows on the basis of at least one predefined rule and the accumulated content of said list .

40. A traffic generating node comprising a client for identifying traffic flows, each traffic flow being associated with a respective application process running on said traffic generating node, said client comprising a signature engine configured to:

recognize a change to a socket associated with an application process; and

perform a mapping operation with respect to that application process responsive to recognizing said change, wherein performing said mapping operation comprises linking the application process to a signature that uniquely identifies a traffic flow and an associated socket, and maintaining information regarding said linking in a list.

41. The traffic generating node according to claim 40, wherein said signature engine is configured to generate said signature to be based on information associated with said socket.

42. The traffic generating node according to claim 41, wherein said signature engine is configured to recognize a change to a socket associated with an application process by recognizing that a socket has been created by the application process, and to perform said mapping operation by generating said signature.

43. The traffic generating node according to claim 42, wherein said signature engine is configured to recognize a change to a socket associated with an application process by recognizing that a socket has been removed by the application process, and to perform said mapping operation by removing a respective entry of said list.

44. The traffic generating node according to claim 40, wherein said signature engine is configured to recognize a change to a socket by monitoring said application process for socket related changes.

45. The traffic generating node according to claim 40, wherein said signature engine is configured to recognize a change to a socket in response to receiving a notification of a socket related change from said application process.

46. The traffic generating node according to claim 40, further comprising a processing element that is configured to classify at least one traffic flow on the basis of accumulated content of said list and at least one predefined classification rule.

47. The traffic generating node according to claim 40, further comprising a processing element that is configured to control at least one of said one or more traffic flows on the basis of accumulated content of said list and at least one predefined control rule.

48. The traffic generating node according to claim 40, wherein said client further comprises an updating unit that is configured, each time a mapping operation has been performed, to:

generate a notification comprising the content of a mapping entry created or updated in said list by way of said mapping operation; and

forward said notification to at least one server via a communication unit, thereby enabling said server to create and maintain a copy of said list.

49. A server comprising at least one processing element that is configured to classify traffic flows transmitted to or received from a traffic generating node, wherein the processing element is configured to:

maintain a copy of a list created by the traffic generating node, wherein the list contains accumulated content regarding linking of each of one or more application processes running on the traffic generating node to a respective signature that uniquely identifies a traffic flow and an associated socket, wherein said maintaining comprises receiving one or more notifications from the traffic generating node comprising the content of one or more mapping entries created or updated in said list by the traffic generating node; and

classify traffic flows on the basis of at least one predefined classification rule and the accumulated content of said list.

50. The server according to claim 49, further comprising a traffic controller that is configured to create and maintain said copy of said list, and a communication unit for receiving said one or more notifications.

51. A server comprising at least one processing element that is configured to control traffic flows transmitted to or received from a traffic generating node, wherein the processing element is configured to:

maintain a copy of a list created by the traffic generating node, wherein the list contains accumulated content regarding linking of each of one or more application processes running on the traffic generating node to a respective signature that uniquely identifies a traffic flow and an associated socket, wherein said maintaining comprises receiving one or more notifications from the traffic generating node comprising the content of one or more mapping entries created or updated in said list by the traffic generating node; and

control traffic flows on the basis of at least one predefined classification rule and the accumulated content of said list.

52. The server according to claim 51, further comprising a traffic controller that is configured to create and maintain said copy of said list, and a communication unit for receiving said one or more notifications.