Abstract: METHODS FOR ANALYZING NETWORK TRAFFIC AND DEVICES THEREOF A method, non-transitory computer readable medium and traffic analysis computing device for analyzing network traffic comprising sending to one or more network devices a request to capture one or more network information upon identifying a fault within a network. Next, one or more network reporting files comprising the captured one or more network information is received from each of the one or more network devices. Upon receiving the network reporting files, a location at which the identified fault occurred within the network is determined. Based on the determination, one or more corrective actions is performed at the location of the identified fault within the network.
CLIAMS:We claim:
1. A method for analyzing network traffic comprising:
sending by a traffic analysis computing device to one or more network devices a request to capture one or more network information upon identifying a fault within a network;
receiving by the traffic analysis computing device one or more network reporting files comprising the captured one or more network information from each of the one or more network devices;
determining by the traffic analysis computing device a location at which the identified fault occurred within the network; and
performing by the traffic analysis computing device one or more corrective actions at the location of the identified fault within the network based on the determination.
2. The method as set forth in claim 1 further comprising providing by the traffic analysis computing device one or more instructions to each of the one or more network devices to include a source internet protocol address of the one or more network device in a header portion of the one or more network reporting files.
3. The method as set forth in claim 1 wherein the determining the location further comprises:
comparing by the traffic analysis computing device each of the received one or more network reporting files against a standard network reporting file to identify at least one of the one or more network reporting files which is deviating from the standard network reporting file; and
identifying by the traffic analysis computing device a place at which the deviating network reporting file was captured to determine the location at which the identified network fault occurred.
4. The method as set forth in claim 3 further comprising scanning by the traffic analysis computing device the header portion of the deviating network reporting file to identify the source internet protocol address of the deviating network reporting file to identify the place at which the deviating network reporting file was captured.
5. The method as set forth in claim 1 further comprising analyzing by the traffic analysis computing device the network traffic at the determined location at which the fault was identified prior to the performing.
6. A non-transitory computer readable medium having stored thereon instructions for analyzing network traffic comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:
sending to one or more network devices a request to capture one or more network information upon identifying a fault within a network;
receiving one or more network reporting files comprising the captured one or more network information from each of the one or more network devices;
determining a location at which the identified fault occurred within the network; and
performing one or more corrective actions at the location of the identified fault within the network based on the determination.
7. The medium as set forth in claim 6 further comprising providing one or more instructions to each of the one or more network devices to include a source internet protocol address of the one or more network device in a header portion of the one or more network reporting files.
8. The medium as set forth in claim 6 wherein the determining the location further comprises:
comparing each of the received one or more network reporting files against a standard network reporting file to identify at least one of the one or more network reporting files which is deviating from the standard network reporting file; and
identifying a place at which the deviating network reporting file was captured to determine the location at which the identified network fault occurred.
9. The medium as set forth in claim 8 further comprising scanning the header portion of the deviating network reporting file to identify the source internet protocol address of the deviating network reporting file to identify the place at which the deviating network reporting file was captured.
10. The medium as set forth in claim 6 further comprising analyzing the network traffic at the determined location at which the fault was identified prior to the performing.
11. A traffic analysis computing device comprising:
one or more processors;
a memory, wherein the memory coupled to the one or more processors which are configured to execute programmed instructions stored in the memory comprising:
sending to one or more network devices a request to capture one or more network information upon identifying a fault within a network;
receiving one or more network reporting files comprising the captured one or more network information from each of the one or more network devices;
determining a location at which the identified fault occurred within the network; and
performing one or more corrective actions at the location of the identified fault within the network based on the determination.
12. The device as set forth in claim 11 wherein the one or more processors is further configured to execute programmed instructions stored in the memory further comprising providing one or more instructions to each of the one or more network devices to include a source internet protocol address of the one or more network device in a header portion of the one or more network reporting files.
13. The device as set forth in claim 11 wherein the one or more processors is further configured to execute programmed instructions stored in the memory for the determining further comprising:
comparing by the traffic analysis computing device each of the received one or more network reporting files against a standard network reporting file to identify at least one of the one or more network reporting files which is deviating from the standard network reporting file; and
identifying by the traffic analysis computing device a place at which the deviating network reporting file was captured to determine the location at which the identified network fault occurred.
14. The device as set forth in claim 13 wherein the one or more processors is further configured to execute programmed instructions stored in the memory further comprising scanning the header portion of the deviating network reporting file to identify the source internet protocol address of the deviating network reporting file to identify the place at which the deviating network reporting file was captured.
15. The device as set forth in claim 11 wherein the one or more processors is further configured to execute programmed instructions stored in the memory further comprising analyzing the network traffic at the determined location at which the fault was identified prior to the performing.
Dated this 28th day of February 2013
R Ramya Rao
Of K&S Partners
Agent for the Applicant
,TagSPECI:FIELD
This technology generally relates to traffic analysis, more particularly, to methods for analyzing network traffic and devices thereof.
| # | Name | Date |
|---|---|---|
| 1 | 877-CHE-2013 FORM-9 28-02-2013.pdf | 2013-02-28 |
| 2 | IP22988-spec.pdf | 2013-03-08 |
| 3 | IP22988-Drawings.pdf | 2013-03-08 |
| 4 | FORM 5.pdf | 2013-03-08 |
| 5 | FORM 3.pdf | 2013-03-08 |
| 6 | 877-CHE-2013 FORM-18 17-04-2013.pdf | 2013-04-17 |
| 7 | 877-CHE-2013 CORRESPONDENCE OTHERS 19-04-2013.pdf | 2013-04-19 |
| 8 | 877-CHE-2013 FORM-3 16-05-2013.pdf | 2013-05-16 |
| 9 | 877-CHE-2013 CORRESPONDENCE OTHERS 16-05-2013.pdf | 2013-05-16 |
| 10 | 877-CHE-2013-FER.pdf | 2019-02-19 |
| 11 | 877-CHE-2013-Information under section 8(2) (MANDATORY) [19-08-2019(online)].pdf | 2019-08-19 |
| 12 | 877-CHE-2013-FORM 3 [19-08-2019(online)].pdf | 2019-08-19 |
| 13 | 877-CHE-2013-FER_SER_REPLY [19-08-2019(online)].pdf | 2019-08-19 |
| 14 | 877-CHE-2013-US(14)-HearingNotice-(HearingDate-13-01-2023).pdf | 2023-01-02 |
| 15 | 877-CHE-2013-POA [06-01-2023(online)].pdf | 2023-01-06 |
| 16 | 877-CHE-2013-FORM 13 [06-01-2023(online)].pdf | 2023-01-06 |
| 17 | 877-CHE-2013-Correspondence to notify the Controller [06-01-2023(online)].pdf | 2023-01-06 |
| 18 | 877-CHE-2013-AMENDED DOCUMENTS [06-01-2023(online)].pdf | 2023-01-06 |
| 19 | 877-CHE-2013-Written submissions and relevant documents [27-01-2023(online)].pdf | 2023-01-27 |
| 20 | 877-CHE-2013-PETITION UNDER RULE 137 [27-01-2023(online)].pdf | 2023-01-27 |
| 21 | 877-CHE-2013-FORM-26 [27-01-2023(online)].pdf | 2023-01-27 |
| 22 | 877-CHE-2013-FORM 3 [27-01-2023(online)].pdf | 2023-01-27 |
| 23 | 877-CHE-2013-PETITION UNDER RULE 137 [02-06-2023(online)].pdf | 2023-06-02 |
| 24 | 877-CHE-2013-PatentCertificate07-06-2023.pdf | 2023-06-07 |
| 25 | 877-CHE-2013-IntimationOfGrant07-06-2023.pdf | 2023-06-07 |
| 1 | searchstrat_13-02-2019.pdf |