Transaction processing

• US 20050108147A1
• Filed: 11/03/2004
• Published: 05/19/2005
• Est. Priority Date: 11/03/2003
• Status: Abandoned Application

• Current Assignee: Web Component Trading Ltd.
• Original Assignee: Web Component Trading Ltd.
• Inventors: Scroope, Alan
• Application Number:
  US10/979,224
• Publication Number:
  US 20050108147A1
• Time in Patent Office: Days
• US Class Current: 705/37
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

Transaction processing is performed by an integration hub (100) communicating with :a number of broker systems B1, B2 . . . Bn; and a number of manufacturer client systems (200). The hub (100) has a client-side interface with an access control mechanism for interfacing with client systems (200), and a broker-side interface with a different access control mechanism for interfacing with the broker systems. When an upload is received from a client for an offer for sale or purchase of goods a broadcast is performed in which a notification with a unique reply URL is sent to each of a selected group of external systems. Each response identifies a log-on page (400), however the full URL is different for each due to the extension query string (such as, “link=10”and “link=57”). A detector function (420) monitors the incoming strings and, using a database (421) determines automatically the identity of the party responding. Thus, the recipient of the notification message can simply click on the link in the message and is then immediately directed to the log-on page (400) and the hub (100) automatically detects their identity without need for them to input any identification data. The log-on page (400) routes the party to the page (410).

Claims

1. An integration hub for transaction processing, the hub comprising:

a client interface for receiving and automatically validating uploads from client systems of data for offering purchase or sale of goods;

a web server for hosting a plurality of web sites, each associated with a client system, and for updating each web site with data which originates from an associated client system upload;

an access controller in the client interface for limiting access by each client system to only the associated web site;

a broadcast controller for transmitting a notification message to a plurality of external systems in response to receiving an upload from a client system; and

a transaction processor for processing purchase or sale of products in response to access by external systems to the web sites hosted by the hub.

2. An integration hub as claimed in claim 1, wherein the hub automatically validates an upload by sequentially performing a plurality of validation tests.

3. An integration hub as claimed in claim 1, wherein the hub automatically validates an upload by sequentially performing a plurality of validation tests, and wherein a validation test determines if the structure of an upload file matches criteria for the transmitting client system.

4. An integration hub as claimed in claim 1, wherein the hub automatically validates an upload by sequentially performing a plurality of validation tests, and wherein a validation test determines if format of data in the upload matches criteria for the transmitting client system.

5. An integration hub as claimed in claim 1, wherein the hub automatically validates an upload by sequentially performing a plurality of validation tests, and wherein a validation test determines if content of data in an upload satisfies criteria for the transmitting client system.

6. An integration hub as claimed in claim 5, wherein the hub dynamically retrieves a set of rules associated with a transmitting client system for validating content of said data.

7. An integration hub as claimed in claim 1, wherein the hub initiates a work flow process upon validation of an upload.

8. An integration hub as claimed in claim 7, wherein a work flow process stage comprises a validation step including interactively transmitting uploaded data to successive client system users identified in an approval work flow definition.

9. An integration hub as claimed in claim 7, wherein a work flow process stage comprises a validation step including interactively transmitting uploaded data to successive client system users identified in an approval work flow definition, and wherein failure to receive approval from any user identified in the work flow definition causes an error message to be transmitted and the work flow to be terminated.

10. An integration hub as claimed in claim 1, wherein the broadcast controller implements a work flow stage of transmitting notifications to members of either a list of external systems identified in the upload or to members of a list which it automatically generates.

11. An integration hub as claimed in claim 10, wherein external systems are characterized in a tiered structure according to classifications.

12. An integration hub as claimed in claim 11, wherein external systems are characterized in a tiered structure according to classifications, and wherein said classifications are associated with the uploading client system.

13. An integration hub as claimed in claim 11, wherein the broadcast controller stores an external system database indexed on said classifications, and dynamically interrogates said database to generate the list.

14. An integration hub as claimed in claim 1, wherein the broadcast controller generates a unique notification for each external system, each notification having a unique response code.

15. An integration hub as claimed in claim 14, wherein the response code is a query string of a URL directing a response to a log-on page, and the hub comprises a monitoring function for determining identities of responding external systems according to the query strings.

16. An integration hub as claimed in claim 14, wherein the response code is a query string of a URL directing a response to a log-on page, and the hub comprises a monitoring function for determining identities of responding external systems according-io the query strings, and wherein the URLs direct the responding external systems to a common log-on page.