System and method for administration of network financial transaction terminals

• US 20020123966A1
• Filed: 06/20/2001
• Published: 09/05/2002
• Est. Priority Date: 06/23/2000
• Status: Abandoned Application

• Current Assignee: Citicorp Development Center Incorporated (Citigroup Incorporated)
• Original Assignee: Citicorp Development Center Incorporated (Citigroup Incorporated)
• Inventors: Sullivan, Mark, Chu, Luke
• Application Number:
  US09/885,674
• Publication Number:
  US 20020123966A1
• Time in Patent Office: Days
• US Class Current: 705/43
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/1085 involving automatic teller machines [ATMs]
• CPC Class Codes: G06Q 20/18 involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G07F 19/20 Automatic teller machines [ATMs]
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection

Abstract

A system and method for administration of network transaction terminals, such as automated teller machines (ATMs) utilizes queued components to allow a synchronized guaranteed delivery of messages, such as log event messages. The messages, which are formatted as Extensible Markup Language (XML) documents, are sent over a network via a secure authenticated and encrypted delivery mechanism. Once the messages reach a data collector in a secure data center, the messages are propagated into a data repository, and the stored messages can be analyzed using a management tool. A distributed secure instrumentation query tool and a message filtering and event alert feature of the system facilitate a data query by a user.

Claims

1. A method for administration of network financial transaction terminals, comprising:

sending an event query to a management instrumentation application by a queued component client on one of the financial transaction terminals;

receiving an event notification from the management instrumentation application by the queued component client;

sending an event message to a server site event queue by the queued component client via message queuing services components;

removing the event message from the server site event queue by a queued component server; and

storing the event message into a database by the queued component server.

2. The method of claim 1, wherein sending the event query further comprises sending a log event type of event query to the management instrumentation application.

3. The method of claim 2, wherein sending the log event type of event query further comprises subscribing to the log event type by the queued component client.

4. The method of claim 1, wherein receiving the event notification further comprises receiving log event type of event notification by the queued component client.

5. The method of claim 4, wherein receiving the event notification further comprises receiving the event notification by the queued component client acting as an event consumer.

6. The method of claim 5, wherein receiving the event notification by the queued component client acting as the event consumer further comprises capturing and consuming a log event message by the queued component client.

7. The method of claim 6, wherein receiving the event notification by the queued component client further comprises capturing and consuming the log event message by the queued component client before the log event message is written into an event log.

8. The method of claim 7, wherein receiving the event notification further comprises placing the log event message in a client site event queue by the queued component client.

9. The method of claim 8, wherein receiving the event notification further comprises creating the client site event queue by the queued component client.

10. The method of claim 4, wherein receiving the event notification further comprises receiving the event notification by the queued component client from the management instrumentation application when a log event occurs.

11. The method of claim 1, wherein sending the event message further comprises sending a log event message in extensible markup language to the server site event queue by the queued component client.

12. The method of claim 11, wherein sending the log event message further comprises placing the log event message in a client site event queue by the queued component client.

13. The method of claim 12, wherein placing the log event message in the client site event queue further comprises creating the client site event queue by the queued component client

14. The method of claim 11, wherein sending the log event message further comprises sending the log event message to the server site event queue over a network.

15. The method of claim 14, wherein sending the log event message over the network further comprises sending the log event message to the server site event queue over a proprietary network.

16. The method of claim 14, wherein sending the log event message over the network further comprises sending the log event message to the server site event queue over a public network.

17. The method of claim 1, wherein removing the event message further comprises removing a log event message from the server site event queue by the queued component server.

18. The method of claim 17, wherein removing the log event message further comprises removing the log event message in extensible markup language format from the server site event queue by the queued component server.

19. The method of claim 18, wherein removing the log event message further comprises removing the log event message from the server site event queue by the queued component server acting as an event processor.

20. The method of claim 1, wherein storing the event message further comprises storing a log event message into the database by the queued component server.

21. The method of claim 20, wherein storing the log event message further comprises storing the log event message in extensible markup language format into the database by the queued component server.

22. The method of claim 21, wherein storing the log event message further comprises storing the log event message into a structured query language server data warehouse by the queued component server.

23. The method of claim 22, wherein storing the log event message further comprises analyzing the stored log event message.

24. The method of claim 23, wherein analyzing the stored log event message further comprises analyzing the stored log event message using an online analytical processing application.

25. The method of claim 1, further comprising allowing a user to query the database via a web browser user interface.

26. The method of claim 25, wherein allowing the user to query the database further comprises filtering query results based on selections entered by the user on the user interface.

27. The method of claim 26, wherein filtering the query results further comprises displaying a report of the filtered results for the user via the user interface.

28. The method of claim 1, further comprising sending a notice of a security related event as an event notification to a predefined terminal for a system administrator.

29. The method of claim 28, wherein sending the notice of the security related event further comprises detecting the security event by a filtering mechanism associated with the database.

30. A system for administration of network financial transaction terminals, comprising:

means for sending an event query to a management instrumentation application by a queued component client on one of the financial transaction terminals;

means for receiving an event notification from the management instrumentation application by the queued component client;

means for sending an event message to a server site event queue by the queued component client via message queuing services components;

means for removing the event message from the server site event queue by a queued component server; and

means for storing the event message into a database by the queued component server.

31. The system of claim 30, wherein the means for sending the event query further comprises means for sending log event type of event query to the management instrumentation application.

32. The system of claim 31, wherein the means for sending the log event type of event query further comprises means for subscribing to the log event type by the queued component client.

33. The system of claim 30, wherein the means for receiving the event notification further comprises means for receiving a log event type of event notification by the queued component client.

34. The system of claim 33, wherein the means for receiving the event notification further comprises means for receiving the event notification by the queued component client acting as an event consumer.

35. The system of claim 34, wherein the means for receiving the event notification by the queued component client acting as the event consumer further comprises means for capturing and consuming a log event message by the queued component client.

36. The system of claim 35, wherein the means for receiving the event notification by the queued component client further comprises means for capturing and consuming the log event message by the queued component client before the log event message is written into an event log.

37. The system of claim 36, wherein the means for receiving the event notification further comprises means for placing the log event message in a client site event queue by the queued component client.

38. The system of claim 37, wherein the means for receiving the event notification further comprises means for creating the client site event queue by the queued component client.

39. The system of claim 33, wherein the means for receiving the event notification further comprises means for receiving the event notification by the queued component client from the management instrumentation application when a log event occurs.

40. The system of claim 30, wherein the means for sending the event message further comprises means for sending a log event message in extensible markup language to the server site event queue by the queued component client.

41. The system of claim 40, wherein the means for sending the log event message further comprises means for placing the log event message in a client site event queue by the queued component client.

42. The system of claim 41, wherein the means for placing the log event message in the client site event queue further comprises means for creating the client site event queue by the queued component client

43. The system of claim 40, wherein the means for sending the log event message further comprises means for sending the log event message to the server site event queue over a network.

44. The system of claim 43, wherein the means for sending the log event message over the network further comprises means for sending the log event message to the server site event queue over a proprietary network.

45. The system of claim 43, wherein the means for sending the log event message over the network further comprises means for sending the log event message to the server site event queue over a public network.

46. The system of claim 30, wherein the means for removing the event message further comprises means for removing a log event message from the server site event queue by the queued component server.

47. The system of claim 46, wherein the means for removing the log event message further comprises means for removing the log event message in extensible markup language format from the server site event queue by the queued component server.

48. The system of claim 47, wherein the means for removing the log event message further comprises means for removing the log event message from the server site event queue by the queued component server acting as an event processor.

49. The system of claim 30, wherein the means for storing the event message further comprises means for storing a log event message into the database by the queued component server.

50. The system of claim 49, wherein the means for storing the log event message further comprises means for storing the log event message in extensible markup language format into the database by the queued component server.

51. The system of claim 50, wherein the means for storing the log event message further comprises means for storing the log event message into a structured query language server data warehouse by the queued component server.

52. The system of claim 51, wherein the means for storing the log event message further comprises means for analyzing the stored log event message.

53. The system of claim 52, wherein the means for analyzing the stored log event message further comprises means for analyzing the stored log event message using an online analytical processing application.

54. The system of claim 30, further comprising means for allowing a user to query the database via a web browser user interface.

55. The system of claim 54, wherein the means for allowing the user to query the database further comprises means for filtering query results based on selections entered by the user on the user interface.

56. The system of claim 55, wherein the means for filtering the query results further comprises means for displaying a report of the filtered results for the user via the user interface.

57. The method of claim 30, further comprising means for sending a notice of a security related event as an event notification to a predefined terminal for a system administrator.

58. The method of claim 57, wherein the means for sending the notice of the security related event further comprises means for detecting the security event by a filtering mechanism associated with the database.