System and method for electronic commerce and other uses

• US 8,001,013 B2
• Filed: 12/18/2007
• Issued: 08/16/2011
• Est. Priority Date: 12/18/2006
• Status: Expired due to Fees

• Current Assignee: Razz Serbanescu
• Original Assignee: Razz Serbanescu
• Inventors: Serbanescu, Razz
• Primary Examiner(s): Pond; Robert M.
• Application Number:
  US11/958,567
• Publication Number:
  US 20080154625A1
• Time in Patent Office: 1,337 Days
• Field of Search: 705/26, 705/27, 705/37
• US Class Current: 705/26.4
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0603 Catalogue ordering
• CPC Class Codes: G06Q 30/0611 Request for offers or quotes
• 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

A computer implemented method including steps of: storing, at a central server, an initialize business rule associated with a vendor and a DNS associated with the vendor, receiving, from a user a first user query for a product or service of the vendor; dynamically forming a universal code sequence forming a DNA field, having at least fields for a user identity, a transaction scope and a product definition; receiving, from the vendor a first vendor response based upon execution by the vendor of the initialize business rule; receiving, from the user a second user query; dynamically adding to the universal code sequence to form a request DNA; receiving from the vendor a second vendor response; dynamically forming an offer DNA; determining if the offer DNA matches the request DNA; and sending to the user and to the vendor a notification that the offer DNA matches the request DNA.

Claims

1. A computer implemented method, comprising:

storing, at a central server, an initialize business rule associated with a vendor and a DNS associated with the vendor, wherein the DNS comprises an address of a data store of the vendor;

receiving, from a user, at the central server, a first user query, wherein the first user query requests a product or service of the vendor;

dynamically forming in real-time at the central server a universal code sequence forming a DNA field, wherein the universal code sequence is associated with the first query, at least a part of the sequence being hierarchal;

wherein the universal codes comprise at least a field projecting a user identity, a-field projecting a transaction scope and a field projecting a product definition;

sending the initialize business rule from the central server to the DNS, wherein the initialize business rule causes the vendor to execute the initialize business rule;

receiving, from the vendor, at the central server, a first vendor response, wherein the first vendor response is based at least in part upon execution by the vendor of the initialize business rule and the first vendor response includes at least one next business rule;

receiving, from the user, at the central server, a second user query, wherein the second user query is a selection from a choice based upon the first vendor response;

dynamically adding to the universal code sequence in real-time at the central server to form a request DNA, wherein the addition comprises a universal code associated with the selection;

sending at least one of the at least one next business rules from the central server to the DNS, wherein the next business rule that is sent is associated with the selection and wherein the next business rule that is sent causes the vendor to execute the next business rule that is sent;

receiving from the vendor, at the central server, a second vendor response, wherein the second vendor response is based at least in part upon execution by the vendor of the next business rule that is sent;

dynamically forming in real-time, at the central server, an offer DNA, wherein the offer DNA is based at least in part upon the request DNA and the second vendor response; and

wherein the offer DNA comprises universal codes including at least a field projecting a vendor identity, a field projecting a transaction scope and a field projecting a product definition;

determining, at the central server, that the offer DNA matches the request DNA as to at least the field projecting a product definition; and

sending to at least one of the user and to the vendor, from the central server, a notification that the offer DNA matches the request DNA.

2. The method of claim 1, wherein the determining comprises determining that the offer DNA exactly matches the request DNA as to at least the field projecting a product definition.

3. The method of claim 1, wherein the determining comprises determining that the offer DNA exactly matches the request DNA as to at least the field projecting a product definition and taking into account at least one wildcard field in at least one of the offer DNA and the request DNA.

4. The method of claim 1, wherein the business rule comprises at least one store procedure.

5. The method of claim 1, wherein the DNS further comprises at least one credential necessary to access the data store.

6. The method of claim 1, wherein the data store comprise at least one database.

7. The method of claim 1, further comprising sending to each of the user and to the vendor, from the central server, a notification that the offer DNA matches the request DNA.

8. The method of claim 1, wherein the method is carried out in the order recited.