Transaction identification in a network environment

• US 10,049,403 B2
• Filed: 07/06/2015
• Issued: 08/14/2018
• Est. Priority Date: 07/06/2015
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Zaidi, Farrukh, Abu-Zaydeh, Husam, Doyle, Brian E., Alizzi, Jason A., Bangad, Sunil R., Seetharaman, Sridhar M., Wu, Benjamin N., Bosi, Robert, Allen, Morgan S.
• Primary Examiner(s): Scott, Randy
• Application Number:
  US14/792,101
• Publication Number:
  US 20170012837A1
• Time in Patent Office: 1,135 Days
• Field of Search: 709220, 709223, 709224, 709225, 709226, 705 1436, 705 1449, 705 1453
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing

Abstract

In one embodiment, a system for analyzing and reporting electronic transactions in a network environment includes an interface that may receive a transaction request at a first network device. A processor communicatively coupled to the interface may execute a task associated with the transaction request generate a transaction report associated with the transaction request and the task. The transaction report may include a request identifier, a request field comprising a task identifier and a uniform resource locator (URL) resource name, a time stamp field, a status code field, and a duration field. The interface may communicate the transaction report to a transaction module operable to aggregate the transaction report with one or more additional transaction reports associated with the transaction request using the unique identifier associated with the transaction request.

Claims

1. A system for analyzing and reporting electronic transactions in a network environment, comprising:

a hardware interface configured to;

receive a transaction request at a first network device;

a hardware processor communicatively coupled to the interface, the processor operable to;

execute a task associated with the transaction request, wherein executing the task comprises calling one or more backend systems;

generate a uniform resource locator (URL) safe identifier, wherein the URL safe identifier identifies related transaction reports;

generate a transaction report associated with the transaction request and the task, wherein the transaction report comprises;

a request identifier comprising the URL safe identifier associated with the transaction request;

a request field comprising a task identifier and a URL resource name;

a time stamp field indicating a date and a time that the first network device received the transaction request;

a status code field indicating a status of the transaction request received by the first network device;

a duration field indicating a time period for the first network device to process the transaction request; and

a backend call summary field identifying the one or more backend systems called by the first network device to process the transaction request;

combine fields of the transaction report to format the transaction report as a single one-line string; and

insert the URL safe identifier into the transaction report as a header field; and

the interface is further operable to communicate the transaction report to a device comprising one or more hardware processors configured to implement a transaction module operable to aggregate the transaction report with one or more additional transaction reports associated with the transaction request using the unique identifier associated with the transaction request.

2. The system of claim 1, further comprising:

an entry point, the entry point operable to communicate the transaction request to the first network device, wherein the entry point is one selected from the group comprising a webserver and an automatic teller machine (ATM); and

the transaction report further comprises a source Internet Protocol (IP) field, the source IP field comprises an address of the entry point communicating the transaction request to the first network device.

3. The system of claim 2, wherein the transaction report further comprises a response size field, the response size field comprises a size of a response returned to the entry point.

4. The system of claim 1, wherein the transaction report further comprises a user identification field, the user identification field comprises a login name of a user associated with the transaction request.

5. The system of claim 1, wherein the transaction report further comprises a session identification field, the session identification field comprises a common identifier used for each of one or more additional transaction requests associated with a user.

6. A method for analyzing and reporting electronic transactions in a network environment, comprising:

receiving, at an interface, a transaction request at a first network device;

executing, using a hardware processor communicatively coupled to the interface, a task associated with the transaction request, wherein executing the task comprises calling one or more backend systems;

generating, using the hardware processor, a uniform resource locator (URL) safe identifier, wherein the URL safe identifier identifies related transaction reports;

generating, using the hardware processor, a transaction report associated with the transaction request and the executed task, wherein the transaction report comprises;

a request identifier comprising the URL safe identifier associated with the transaction request;

a request field comprising a task identifier and a URL resource name;

a time stamp field indicating a date and a time that the first network device received the transaction request;

a status code field indicating a status of the transaction request received by the first network device;

a duration field indicating a time period for the first network device to process the transaction request; and

a backend call summary field identifying the one or more backend systems called by the first network device to process the transaction request;

combining, using the hardware processor, fields of the transaction report to format the transaction report as a single one-line string;

inserting, using the hardware processor, the URL safe identifier into the transaction report as a header field; and

communicating, using the interface, the transaction report to a device comprising one or more hardware processors configured to implement a transaction module operable to aggregate the transaction report with one or more additional transaction reports associated with the transaction request.

7. The method of claim 6, further comprising:

communicating, using a network entry point, the transaction request to the first network device, wherein the entry point is one selected from the group comprising a webserver and an automatic teller machine (ATM); and

the transaction report further comprises a source Internet Protocol (IP) field, the source IP field comprises an address of the entry point communicating the transaction request to the first network device.

8. The method of claim 7, wherein the transaction report further comprises a response size field, the response size field comprises a size of a response returned to the entry point.

9. The method of claim 6, wherein the transaction report further comprises a user identification field, the user identification field comprises a login name of a user associated with the transaction request.

10. The method of claim 6, wherein the transaction report further comprises a session identification field, the session identification field comprises a common identifier used for each of one or more additional transaction requests associated with a user.

11. A non-transitory computer readable medium comprising logic, the logic operable, when executed by a hardware processor, to:

receive a transaction request at a first network device;

execute a task associated with the transaction request, wherein executing the task comprises calling one or more backend systems;

generate a uniform resource locator (URL) safe identifier, wherein the URL safe identifier identifies related transaction reports;

generate a transaction report associated with the transaction request and the executed task, wherein the transaction report comprises;

a request identifier comprising the URL safe identifier associated with the transaction request;

a request field comprising a task identifier and a URL resource name;

a time stamp field indicating a date and a time that the first network device received the transaction request;

a status code field indicating a status of the transaction request received by the first network device;

a duration field indicating a time period for the first network device to process the transaction request; and

a backend call summary field identifying the one or more backend systems called by the first network device to process the transaction request;

insert the URL safe identifier into the transaction report as a header field; and

combine fields of the transaction report to format the transaction report as a single one-line string; and

communicate the transaction report to a device comprising one or more hardware processors configured to implement a transaction module operable to aggregate the transaction report with one or more additional transaction reports associated with the transaction request.

12. The non-transitory medium of claim 11, wherein the logic is further operable to:

communicate, using a network entry point, the transaction request to the first network device, wherein the entry point is one selected from the group comprising a webserver and an automatic teller machine (ATM); and

the transaction report further comprises;

a source Internet Protocol (IP) field, the source IP field comprises an address of the entry point communicating the transaction request to the first network device; and

a response size field, the response size field comprises a size of a response returned to the entry point.

13. The non-transitory medium of claim 11, wherein the transaction report further comprises a user identification field, the user identification field comprises a login name of a user associated with the transaction request.

14. The non-transitory medium of claim 11, wherein the transaction report further comprises a session identification field, the session identification field comprises a common identifier used for each of one or more additional transaction requests associated with a user.