Method and device utilizing polymorphic data in e-commerce

• US 20060143089A1
• Filed: 01/30/2006
• Published: 06/29/2006
• Est. Priority Date: 12/05/2000
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: Brian Hayes, Charles Boyle, Jari Koistinen, Mudita Jain
• Inventors: Jain, Mudita, Koistinen, Jari, Boyle, Charles, Hayes, Brian
• Granted Patent: US 7,895,079 B2
• Time in Patent Office: Days
• US Class Current: 705/21
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0619 Neutral agent
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

An aspect of the present invention includes a protocol for conveying data during an e-commerce session with a polymorphic response, comprising initiating a session with a message from a buyer application to a broker application and a session identifier assigned by the broker application; conducting the session between the buyer application and a supplier application; and concluding the session with a additional message which includes a schema identifier for the additional message, resolvable in a context of a system identifier; and a polymorphic response comprising a type and a version, wherein the polymorphic response includes additional data elements corresponding to values assigned to the type and version.

Claims

1. A method of facilitating brokered web services, including:

sending to an e-commerce routing hub a first request to start a supplier service session with a service identified by a unique name that is not a routing address;

relying on the e-commerce routing hub to look up the unique name in a directory, to resolve the unique name to a routing address and to send an additional request to start the supplier service session to the service, corresponding to the first request to start the supplier service;

conducting a message exchange with the service identified by the unique name;

to bring the message exchange to an end, sending the e-commerce routing hub a first service session end message and relying on the e-commerce routing hub to match the first service session end message with a second service session end message from the service identified by the unique name and to record results of the session, the results reported with the first and/or the second service session end message.

2. The method of claim 1, wherein the additional request to start the service reiterates the first request to start the service.

3. The method of claim 1, wherein the message exchange is conducted through the e-commerce routing hub.

4. The method of claim 1, wherein the sending is accomplished from a web browser by selecting a link on a web page.

5. The method of claim 1, further including, prior to the sending, registering with the e-commerce hub and subscribing to the service identified by the unique name.

6. The method of claim 1, further including receiving from the service a polymorphic message including:

a schema identifier for the additional message, resolvable in a context of a system identifier; and

a polymorphic response including a message type and version that, in combination with the schema identifier, define one or more additional data elements of the message type and version.

7. The method of claim 1, further including sending to the service a polymorphic message including:

a schema identifier for the additional message, resolvable in a context of a system identifier; and

a polymorphic response including a message type and version that, in combination with the schema identifier, define one or more additional data elements of the message type and version.