Method of and system for processing transactions

• US 7,870,032 B2
• Filed: 07/06/2006
• Issued: 01/11/2011
• Est. Priority Date: 09/29/1999
• Status: Active Grant

• Current Assignee: Charles Schwab & Company Incorporated (Charles Schwab Corporation)
• Original Assignee: Charles Schwab & Company Incorporated (Charles Schwab Corporation)
• Inventors: Goldstein, Neal L., Mullins, Chalon G., Richards, Adam J., Levy, David, Sherr, David
• Primary Examiner(s): Dunham; Jason
• Application Number:
  US11/481,498
• Publication Number:
  US 20060253341A1
• Time in Patent Office: 1,650 Days
• Field of Search: 705/26, 705/27, 705/37
• US Class Current: 705/26.1
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

A method of and system for conducting electronic commerce segments an enterprise is segmented into a single firm side system, and multiple customer facing and street side systems. The firm side system maintains a single system of record for the enterprise. The customer facing systems provide an interface between the enterprise and the customer. The street side systems are in communication with the customer facing systems. The street side systems provide an interface between the enterprise and various markets.

Claims

1. An electronic commerce system, which comprises:

a plurality of customer facing utility systems, each of said customer facing utility systems coupled to a customer facing communication network, wherein the plurality of customer facing utility systems are each configured to communicate with customer systems coupled to the customer facing communication network, and each of said customer facing utility systems having associated therewith authoritative data that is writable to by said customer facing utility system and read-only data,

wherein data written to said authoritative data of any one of said customer facing utility systems is replicated to the authoritative data of each of the other customer facing utility systems;

a firm side system, said firm side system having associated therewith authoritative data that is writable to by said firm side system and read-only data, wherein data written to said authoritative data of said firm side systems is replicated to the read-only data of each of said customer facing utility systems; and

a plurality of street side systems, each of said street side systems being adapted to communicate with street systems, each of said street side systems having associated therewith authoritative data that is writable to by said street side system and read-only data, wherein data written to said authoritative data of any one of said street side systems is replicated to the authoritative data of each of the other street side systems.

2. The system as claimed in claim 1,

wherein data written to said authoritative data of any one of said customer facing utility systems is replicated to the read-only data of said firm side system.

3. The system as claimed in claim 1,

wherein data written to said authoritative data of said firm side systems is replicated to the read-only data of each of said street side systems.

4. The system as claimed in claim 3,

wherein data written to said authoritative data of any one of said street side systems is replicated to the read-only data of said firm side system.

5. The system as claimed in claim 3,

wherein data written to said authoritative data of any one of said street side systems is replicated to the read-only data of each of said customer facing utility systems.

6. An electronic commerce system, which comprises:

a plurality of customer facing utility systems, each of said customer facing utility systems being adapted to communicate with customer systems, each of said customer facing utility systems including a server computer for processing customer orders received from customer systems, wherein processing customer orders includes creating a transaction record for said order and writing said transaction record to the authoritative data associated with said customer facing utility system, and for processing customer inquiries received from customer systems, wherein processing customer inquiries includes aggregating transaction records in said authoritative data to determine status of a transaction, and each of said customer facing utility systems having associated therewith authoritative data that is writable to by said customer facing utility system and read-only data,

wherein said customer facing utility systems replicate data records written to said authoritative data of any one of said customer facing utility systems to the authoritative data of each of the other customer facing utility systems;

a plurality of street side systems, each of said street side systems being adapted to communicate with street systems, each of said street side systems including a server computer for executing orders communicated from said customer facing utility systems, and each of said street side systems having associated therewith authoritative data that is writable to by said street side system and read-only data, wherein said street side systems replicate data records written to said authoritative data of any one of said street side systems to the authoritative data of each of the other street side systems; and

a firm side system, said firm side system having associated therewith authoritative data that is writable to by said firm side system and read-only data, wherein said firm side system replicates data written to said authoritative data of said firm side systems to the read-only data of each of said street side systems;

wherein data records written to said authoritative data of any one of said street side systems are replicated to the read-only data of each of said customer facing utility systems.

7. The system as claimed in claim 6

wherein data records written to said authoritative data of any one of said customer facing utility systems are replicated to the read-only data of said firm side system.

8. The system as claimed in claim 6

wherein data records written to said authoritative data of any one of said street side systems are replicated to the read-only data of said firm side system.

9. A method of processing customer transactions, which comprises the steps of:

receiving a customer transaction request at one customer facing utility system of a plurality of customer facing utility systems;

creating a record of said transaction request;

writing said transaction request record to data storage associated with said one customer facing utility system;

replicating said transaction request record to data storage data associated with each of the other customer facing utility systems of said plurality of customer facing utility systems;

sending said transaction request from said one customer facing utility system to one of a plurality of street side systems;

executing said transaction request at said one street side system;

creating a record of said transaction execution;

writing said transaction execution record to data storage associated with said one street side system;

replicating said transaction execution record to data storage associated with each of said customer facing utility systems; and

clearing said transaction through a firm side system, said firm side system having associated therewith authoritative data that is writable to by said firm side system and read-only data, wherein said firm side system replicates data written to said authoritative data of said firm side systems to the read-only data of each of said street side systems and each of said customer facing utility systems.

10. The method as claimed in claim 9, wherein said transaction request is a buy order.

11. The method as claimed in claim 9, wherein said transaction request is a sell order.

12. The method as claimed in claim 9, wherein said transaction request is a cancel order.

13. The method as claimed in claim 9, wherein said transaction execution includes the step of filling an order.

14. The method as claimed in claim 9, including the steps of:

receiving a customer transaction inquiry at one of said customer facing utility systems;

determining status of a transaction based upon transaction records in the data storage associated with said one customer facing utility system.