Apparatus and Method for Tracking Transaction Related Data

• US 20100228650A1
• Filed: 08/27/2007
• Published: 09/09/2010
• Est. Priority Date: 08/27/2007
• Status: Active Grant

• Current Assignee: Correlsense Incorporated
• Original Assignee: Correlsense Incorporated
• Inventors: Elias, Oren Shlomo, Shacham, Lanir Naftaly
• Granted Patent: US 9,277,012 B2
• Time in Patent Office: Days
• US Class Current: 705/34
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A method of tracking information in a multi-tier computerized environment, the method comprising: receiving an at least one packet; storing data associated with the at least one packet and with an at least one request or transaction associated with the at least one packet; parsing a byte stream generated from conversion of the at least one packet; detecting data associated with the at least one request or transaction related to the byte stream; matching a thread associated with the byte stream with the at least one request or transaction associated with the at least one packet according to predetermined fields within the byte stream, an apparatus for implementing the same and methods for determining resource consumption of requests or transactions.

Claims

1. A method of tracking information in a multi-tier computerized environment, the method comprising:

a. receiving an at least one packet;

b. storing data associated with the at least one packet and with an at least one request or transaction associated with the at least one packet;

c. parsing a byte stream generated from conversion of the at least one packet;

d. detecting data associated with the at least one request or transaction related to the byte stream;

e. matching a thread associated with the byte stream with the at least one request or transaction associated with the at least one packet according to predetermined fields within the byte stream.

2. The method according to claim 1, further comprising a step of storing data related to the at least one request or transaction associated with the at least one packet.

3. The method according to claim 2, further comprising a step of determining that at least one request or transaction is associated with another request by comparing an at least one previously stored parameter associated with the at least one request or transaction and with the other request.

4. The method according to claim 1, further comprising a step of tagging the at least one outgoing packet.

5. The method according to claim 3, further comprising a step of prioritizing the at least one request or transaction according to an entity associated with the at least one request or transaction.

6. The method according to claim 1, further comprising a step of determining measurable attributes related to consumption of resources within tiers by the at least one request or transaction.

7. The method according to claim 6, further comprising a step of determining a profile for the at least one request based on data associated with measurable attributes related to consumption of the resources tiers by the at least one request.

8. The method according to claim 6, further comprising a step of determining measurable attributes related to consumption of tiers by the transaction as a function of consumption of the resources within tiers by the at least one request associated with the transaction.

9. The method according to claim 8, further comprising a step of determining a profile for the at least one transaction based on data associated with measurable attributes related to consumption of the resources within tiers by the at least one transaction.

10. The method according to claim 9, further comprising a step of predicting consumption of measurable attributes of the resources within tiers according to profile and quantity of the at least one request or transaction handled by the tier during a predetermined period of time.

11. The method according to claim 8, further comprising a step of prioritizing the at least one request or transaction as a function of measurable attributes related to consumption of the resources within tiers by the at least one request or transaction.

12. The method according to claim 11, further comprising a step of determining whether to delay or pause a thread according to the priority of the at least one request or transaction related to the thread.

13. The method according to claim 9, further comprising a step of determining the tier'"'"'s required resources according to the profile of the transaction or request consuming the resource within the tier.

14. The method according to claim 11, further comprising a step of allocating the resources within tiers to the at least one request or transaction according to the priority of the at least one request or transaction.

15. The method according to claim 14, further comprising a step of limiting the resources within tiers allocated to the at least one request or transaction according to consumption of tiers required by another request or transaction.

16. A method of tracking information in a multi-tier computerized environment, the method comprising:

a. receiving an at least one incoming packet;

b. storing data associated with the at least one incoming packet and with an at least one request or transaction associated with the at least one incoming packet;

c. converting the at least one incoming packet into a byte stream;

d. parsing the byte stream and detecting data related to applicative events or requests;

e. logging IP;

port address related to the at least one request or transaction;

17. The method according to claim 16, further comprising a step of querying the operating system regarding IP address and port used by each request.

18. The method according to claim 16, further comprising a step of associating at least one request with an at least one request or transaction according to the thread ID, IP:

port address and time stamp related to the at least one request or transaction.

19. The method according to claim 16, further comprising steps of detecting numbers or characters that repeats in at least two requests and associating the requests according to the repeating number or characters.

20. A computerized apparatus for tracking information of a multi-tier computerized environment comprising:

a. a tagging unit located within each tier for detecting information related to an at least one request or transaction from a packet;

b. a parsing unit for detecting data associated with the at least one request or transaction from a byte stream;

c. a storage associated with the tagging unit and the parsing unit for storing data related to the at least one request or transaction from the packet and the byte stream;

d. a processing unit for associating data in the storage, related to the at least one request or transaction detected from the packet and from the byte stream.

21. The apparatus according to claim 20, wherein the tagging unit is located within the kernel level.

22. The apparatus according to claim 20, wherein the parsing unit is located within the kernel level.

23. The apparatus according to claim 20, further comprising a central storage for storing data related to a transaction resource consumption in an at least one tier.

24. The apparatus according to claim 20, further comprising a central processing module for determining resource consumption related to a transaction resource consumption in an at least one tier.

25. A method of determining the amount of money billed by an at least one consumer of IT infrastructure multi-tier computerized environment, the method comprising:

a. determining amounts of measurable attribute consumed by the at least one consumer of IT infrastructure;

b. determining the amount of money to be paid for consuming a measurable attribute of a resource;

c. determining a payment value as a function of the resource consumption of the at least one measurable attribute consumed by the at least one consumer of IT infrastructure.

26. The method according to claim 25, wherein the at least one entity is at least two entities consuming the resources, wherein payment values are determined as a function of the rate of resource consumption between the at least two entities.