System and method for management of network monitoring information
US-9210053-B2 · Dec 8, 2015 · US
US9432269B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9432269-B2 |
| Application number | US-201313858009-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 6, 2013 |
| Priority date | Apr 6, 2013 |
| Publication date | Aug 30, 2016 |
| Grant date | Aug 30, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure is directed towards systems and methods for lightweight identification of flow information by application. A flow monitor executed by a processor of a device may maintain a counter. The flow monitor may associate an application with the value of the counter and transmit, to a data collector executed by a second device, the counter value and a name of the application. The flow monitor may monitor a data flow associated with the application to generate a data record. The flow monitor may transmit the data record to the data collector, the data record including an identification of the application consisting of the counter value and not including the name of the application. The data collector may then re-associate the data record with the application name based on the previously received counter value.
Opening claim text (preview).
What is claimed is: 1. A method for lightweight identification of flow information by application, comprising: maintaining, by a flow monitor executed by a processor of a device, a counter; associating, by the flow monitor, an application with the value of the counter; transmitting, by the flow monitor to a data collector executed by a second device, the counter value and a name of the application; monitoring, by the flow monitor, a data flow associated with the application to generate a data record; and transmitting the data record, by the flow monitor to the data collector, the data record including an identification of the application consisting of the counter value. 2. The method of claim 1 , further comprising incrementing the counter prior to associating a second application with the value of the counter. 3. The method of claim 1 , further comprising maintaining a second counter, incrementing the second counter upon rebooting the device, and transmitting the value of the second counter to the data collector with the counter value and the name of the application. 4. The method of claim 1 , further comprising maintaining a second counter, incrementing the second counter responsive to a configuration change of the device, and transmitting the value of the second counter to the data collector with the counter value and the name of the application. 5. The method of claim 1 , wherein the name of the application is an order of magnitude longer than the counter value. 6. The method of claim 1 , wherein transmitting the counter value and the name of the application further comprises transmitting a device identifier associated with the application. 7. The method of claim 1 , wherein transmitting the data record including an identification of the application consisting of the counter value further comprises transmitting the data record for re-association with the name of the application by the data collector, based on a mapping of the name of the application to the counter value maintained by the data collector. 8. The method of claim 1 , further comprising re-transmitting the counter value and the name of the application responsive to expiration of a timer. 9. A method for lightweight identification of flow information by application, comprising: receiving, by a data collector executed by a processor of a device, from a second device, a name of an application and a value of a counter maintained by a flow monitor executed by the second device; mapping, by the data collector, the received name of the application to the counter value; receiving, by the data collector from the flow monitor, a data flow record including an identification of the application consisting of the counter value; and re-associating the received data flow record with the name of the application, by the data collector, responsive to the mapping of the name of the application to the counter value. 10. The method of claim 9 , wherein receiving the name of the application and value of the counter further comprises receiving a value of a second counter, and further comprising: receiving, by the data collector, the name of the application, a second value of the counter, and an incremented value of the second counter, transmitted by the flow monitor responsive to a change in configuration of the second device; and replacing the mapping of the name of the application to the counter value with a mapping of the name of the application to the second counter value. 11. The method of claim 9 , wherein the name of the application is an order of magnitude longer than the counter value. 12. The method of claim 9 , further comprising receiving, by the data collector, a device identifier, and mapping the name of the application to the device identifier and the counter value. 13. A system for lightweight identification of flow information by application, comprising: a device comprising a processor executing a flow monitor, the flow monitor configured for: maintaining a counter, associating an application with the value of the counter, transmitting, to a data collector executed by a second device, the counter value and a name of the application, monitoring a data flow associated with the application to generate a data record, and transmitting the data record, to the data collector, the data record including an identification of the application consisting of the counter value. 14. The system of claim 13 , wherein the flow monitor is further configured for incrementing the counter prior to associating a second application with the value of the counter. 15. The system of claim 13 , wherein the flow monitor is further configured for maintaining a second counter, incrementing the second counter responsive to a configuration change of the device, and incrementing the second counter upon rebooting the device. 16. The system of claim 13 , wherein the flow monitor is further configured for maintaining a second counter, incrementing the second counter responsive to a configuration change of the device, and incrementing the second counter responsive to a configuration change of the device. 17. The system of claim 13 , wherein the name of the application is an order of magnitude longer than the counter value. 18. The system of claim 13 , wherein the flow monitor is further configured for transmitting a device identifier associated with the application. 19. The system of claim 13 , wherein the flow monitor is further configured for transmitting the data record for re-association with the name of the application by the data collector, based on a mapping of the name of the application to the counter value maintained by the data collector. 20. The system of claim 13 , wherein the flow monitor is further configured for re-transmitting the counter value and the name of the application responsive to expiration of a timer.
by filtering · CPC title
Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title
Hypervisors; Virtual machine monitors · CPC title
above the transport layer · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.