Distributed on-line data communications system and method

• US 5,964,831 A
• Filed: 10/29/1996
• Issued: 10/12/1999
• Est. Priority Date: 10/29/1996
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Inventors: Jahanian, Teresa R., Kearns, Kevin A., Jeffery, Raymond E.
• Primary Examiner(s): Asta, Frank J.
• Assistant Examiner(s): VU, THONG H
• Application Number:
  US08/741,148
• Time in Patent Office: 1,078 Days
• Field of Search: 235/379, 709/168, 709/246, 709/201, 395/214, 395/600, 395/700, 395/604, 395/185.01, 395/185.04, 395/609, 364/408, 707/205, 707/3
• US Class Current: 709/201
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

The system and method of the present invention provide distributed on-line communications for electronic commerce applications. The system includes at least one system node having multiple processes for communicating with outside devices, such as ATMs and financial institutions. A configuration database accessible by the processes stores the logical name of each process and outside device, and the corresponding physical address. A system library is coupled to the processes for supplying a plurality of routines for transmitting and receiving messages to and from one another process and to and from another node in the system.

Claims

1. A distributed on-line data communication system, comprising:

more than one system site each having a plurality of entities operable to communicate with one another and with outside devices, said entities including a plurality of processes;

a configuration database accessible by said plurality of entities for storing logical names and physical addresses for said plurality of entities and outside devices, each entity in a system site has at least one predetermined backup entity located on another system site defined in said system configuration database; and

a system library coupled to said plurality of entities and having a plurality of messaging routines that may be called by said entities and processes for queuing, transmitting, routing, and receiving messages to and from one another, said configuration database being further accessible to said system library.

2. The system, as set forth in claim 1, wherein said plurality of processes comprise at least one line handler communicating to said outside devices according to a predefined communication protocol.

3. The system, as set forth in claim 1, wherein said plurality of processes comprise a system monitor process for monitoring the operational status of all entities at said at least one system site.

4. The system, as set forth in claim 3, further comprising a system monitor backup process for monitoring the operational status of all entities at said at least one system site in a non-stop manner.

5. The system, as set forth in claim 1, wherein said plurality of processes in each system site comprise at least one line handler process for communicating with another system node.

6. The system, as set forth in claim 1, further comprising a system monitor process located in one of said system sites for monitoring the operational status of all processes in all system site.

7. The system, as set forth in claim 1, wherein said plurality of processes in each system site comprise a system monitor process for detecting a failure at a system site.

8. The system, as set forth in claim 7, wherein said system configuration database further includes an identification of a backup entity for at least one entity in the system.

9. The system, as set forth in claim 7, wherein said system configuration database further includes an identification of a backup entity for all entities in the system.

10. The system, as set forth in claim 1, wherein said system configuration database contains logical names and physical addresses of all processes and outside devices in all system sites.

11. The system, as set forth in claim 1, wherein said system configuration database is replicated and resides at more than one system site.

12. The system, as set forth in claim 1, wherein said system configuration database is distributed across more than one system site.

13. The system, as set forth in claim 1, wherein said system configuration database includes system entity records, where each system entity record contains information on each system site.

14. The system, as set forth in claim 1, wherein said plurality of processes comprise a control point process for collecting commands issued by an operator for controlling the operation of all entities and processes at said system site.

15. The system, as set forth in claim 1, wherein said plurality of processes comprise a command facility process for interfacing to an operator and receiving commands therefrom.

16. The system, as set forth in claim 1, wherein said plurality of processes comprise a log process and an associated database for logging messages transmitted between said processes.

17. The system, as set forth in claim 1, wherein said plurality of processes comprise a tracer process and an associated database for logging messages transmitted between selected processes for diagnostic purposes.

18. The system, as set forth in claim 1, further comprising a plurality of application processes at said system site each performing well-defined functions related to the processing of a transaction and using said plurality of processes for communicating among said application processes and to said outside devices.

19. The system, as set forth in claim 1, wherein said system library comprises a SEND routine for queuing a message from a first process on a second process.

20. The system, as set forth in claim 19, wherein said system library comprises a RECEIVE routine for receiving a message queued from a first process to a second process.

21. The system, as set forth in claim 1, wherein said entities and processes communicate with messages in a message format using token identifiers.

22. The system, as set forth in claim 21, further comprising a multi-level architecture including a system library level and an application library level.

23. The system, as set forth in claim 22, wherein said message format includes a system header for reading by system library level entities and processes, and an optional application header for reading by application library processes.

24. A multi-layer on-line data communication system distributed across more than one system site, comprising:

a communications layer having data communications equipment and lines operating according to certain protocols;

a system library layer providing a messaging service for communications between a plurality of entities residing on at least one system site, and for communications with a plurality of outside devices, said system library layer including a configuration database accessible by said plurality of entities for storing logical names and physical addresses for said plurality of entities and outside devices, said configuration database being distributed across said more than one system site; and

at least one application layer having at least one application process for performing application-specific functions by using said messaging service performed by said system library layer.

25. The system, as set forth in claim 24, wherein said system library layer comprises at least one line handler process communicating to said outside devices according to a predefined communication protocol.

26. The system, as set forth in claim 24, wherein said system library layer comprises a system monitor process for monitoring the operational status of all entities at said system site.

27. The system, as set forth in claim 26, further comprising a system monitor backup process for monitoring the operational status of all entities at said system site in a non-stop manner.

28. The system, as set forth in claim 24, wherein said system configuration database further includes an identification of a backup entity for at least one entity in the system.

29. The system, as set forth in claim 24, wherein said system configuration database further includes an identification of a backup entity for at least one entity residing on another system node.

30. The system, as set forth in claim 24, wherein said system configuration database is replicated and resides at more than one system site.

31. The system, as set forth in claim 24, wherein said system library layer further comprises a control point process for collecting commands issued by an operator for controlling the operation of all entities and processes at said system site.

32. The system, as set forth in claim 24, wherein said system library layer further comprises a command facility process for interfacing to an operator and receiving commands therefrom.

33. The system, as set forth in claim 24, wherein said system library layer further comprises a log process and an associated database for logging messages transmitted between said processes.

34. The system, as set forth in claim 24, wherein said system library layer further comprises a tracer process and an associated database for logging messages transmitted between selected processes for diagnostic purposes.

35. The system, as set forth in claim 24, wherein said system library layer comprises a SEND routine for queuing a message from a first process on a second process.

36. The system, as set forth in claim 35, wherein said system library layer comprises a RECEIVE routine for receiving a message queued from a first process to a second process.

37. A method for on-line data communications across more than one system site, comprising the steps of:

for each application process, binding a plurality of system library messaging service processes therewith;

storing logical names and physical addresses of all entities residing in said more than one system site and outside devices associated with the system in a system configuration database at each system site; and

accessing a private data structure maintained by the system library messaging service processes to obtain information for performing routing and receiving services for application processes.

38. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a line handler process for communicating to said outside devices according to a predefined communication protocol.

39. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a system monitor process for monitoring the operational status of entities.

40. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a system monitor backup process for monitoring the operational status of entities in a non-stop manner.

41. The method, as set forth in claim 37, wherein the storing step further comprises the step of storing an identification of a backup entity for at least one entity in the system.

42. The method, as set forth in claim 37, wherein the storing step further comprises the step of storing an identification of a backup entity for at least one entity in the system residing on another system node.

43. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a control point process for collecting commands issued by an operator for controlling the operation of all entities and processes.

44. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a command facility process for interfacing to an operator and receiving commands therefrom.

45. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a log process and an associated database for logging messages transmitted between said processes.

46. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a tracer process and an associated database for logging messages transmitted between selected processes for diagnostic purposes.

47. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a SEND routine for queuing a message from a first process on a second process.

48. The method, as set forth in claim 37, wherein the binding step comprises the step of binding a RECEIVE routine for receiving a message queued from a first process to a second process.

49. A distributed on-line data communication system, comprising:

at least one system site having a plurality of entities operable to communicate with one another and with outside devices, said entities including a plurality of processes;

a configuration database accessible by said plurality of entities for storing logical names and physical addresses for said plurality of entities and outside devices, each entity in a system site has at least one predetermined backup entity defined in said system configuration database; and

a system library coupled to said plurality of entities and having a plurality of messaging routines that may be called by said entities and processes for queuing, transmitting, routing, and receiving messages to and from one another, said configuration database being further accessible to said system library.