Systems and methods for database registration

• US 7,433,897 B1
• Filed: 11/07/2001
• Issued: 10/07/2008
• Est. Priority Date: 11/07/2001
• Status: Expired due to Fees

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Devulapalli, Ravi R., Harris, Keith R., Webb, Sandra S.
• Primary Examiner(s): Rones; Charles
• Assistant Examiner(s): Betit; Jacob F
• Application Number:
  US09/986,168
• Time in Patent Office: 2,526 Days
• Field of Search: 707/9, 707/1, 707/102, 707/10, 707/201, 707/6, 707/103, 707/104, 707/204, 705/27, 705/40, 705/39, 705/21, 705/26, 705/41, 370/546, 370/352, 713/200
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit

Abstract

Embodiments of the present invention relate to systems and methods for database registration. According to an embodiment of the present invention, a method for database registration includes receiving a user identifier of a user and then sending a query to a first database based at least in part on the user identifier. A first data value associated with the user is received from the first database. A second data value associated with the user is received from a data source, which is different from the first database. The first data value and the second data value are stored in a second database, which is different from the first database.

Claims

1. A method for online purchasing utilizing database registration information in an online purchasing system, comprising:

beginning database registration of a user in the online purchasing system by requesting a user identifier from the user computer via a first input field of a first graphical user interface displaying a web page;

receiving the user identifier via the first input field of the first graphical user interface;

sending a query to the first database based at least in part on the user identifier;

receiving a first data value from the first database, the first data value being associated with the user for purposes of identifying the user and being displayed in a display field of the first graphical user interface;

prompting for and receiving a second data value from a data source via a second input field of the first graphical user interface, the second data value being associated with the user for purposes of electronic procurement authorization, the data source being different from the first database;

prompting the user to enter one or more additional data values via one or more corresponding input fields of the first graphical user interface, wherein the user has an option to input the one or more additional data values and if the user chooses not to enter one or more of the one or more additional data values then accepting a null value for the one or more additional data values not entered;

storing the first data value, the second data value and the one or more additional data values in a second database such that the first data value, the second data value and the one or more additional data values are contained within the second database concurrently and persistently, the second database being different from the first database;

prompting the user to enter a payment method for future online purchases under the registration provided by the second database;

in response to prompting for the payment method, receiving identification of a purchasing card as the method of payment, where purchasing card information has been previously stored in the second database;

in response to receiving the identification of the purchasing card as the method of payment, determining that the purchasing card has an owner different than the user based on information previously stored in the second database;

in response to determining that the purchasing card has an owner different than the user, then sending an email to the owner that includes a link to a web page;

receiving a selection by the owner of the link to the web page;

in response to receiving the selection of the link, displaying a validation panel user interface for the owner that provides selections for indicating whether the user is authorized to use the purchasing card and for entering an identification of the owner;

in response to receiving the selection that indicates that the user is authorized to use the purchasing card and receiving the identification of the owner, then determining whether the identification matches an identification of the owner stored in the second database; and

in response to determining that the received identification of the owner matches the stored identification of the owner, then completing the registration of the user by storage an indication that the user is authorized to use the purchasing card as the payment method.

2. The method of claim 1, wherein receiving the second data value includes receiving the second data value via a computer.

3. The method of claim 2, further comprising sending at least in part an applet to the computer.

4. The method of claim 3, wherein sending at least in part the applet to the computer includes sending graphical user interface data.

5. The method of claim 2, further comprising receiving purchasing card information.

6. The method of claim 5, wherein the purchasing card information includes a purchasing card number of a purchasing card and an identification of an owner of the purchasing card.

7. The method of claim 6, wherein the purchasing card is selected from the group consisting of a credit card and a debit card.

8. The method of claim 1, further comprising storing a third data value and a fourth data value in the second database, the third data value and the fourth data value being associated with the user, the third data value and the fourth data value being received from one of the data source and the first database.

9. The method of claim 8, further comprising providing the user the option for selectively not storing one or more of the first data values, the second data value, the third data value, and the fourth data value in the second database.

10. A system for database registration, the system comprising:

a first server including database registration instructions;

a first database coupled to the first server, the first database to store at least in part a first set of data values associated with a user;

a computer coupled to the first server, the computer to receive a second set of data values associated with the user for purposes of electronic procurement authorization via a second set of input fields of the first graphical user interface, the computer to receive the first set of data values from the from the first database for purposes of identifying the user and display the first set of data values via a display field of the graphical user interface in response to receiving a user identifier via a first input field of the graphical user interface, wherein the computer allows the user to enter one or more additional data values via one or more additional input fields of the first graphical user interface; and

an online purchasing system comprising a second database and one or more interrelated databases, the second database to receive the first set of data values, the second set of data values and the additional data values from the display field, the second input field and the one or more additional input fields of the graphical user interface of the computer, the second database to store the first set of data values, the second set of data values and the additional data values such that the first data value from the first database, the second set of data values and the additional data values are contained within the second database concurrently and persistently;

wherein an applet implemented on the computer receives a purchase request from the user that identifies the user with the user identification previously stored in the second database and prompts the user to enter a payment method;

wherein the applet, in response to prompting for the payment method, receives identification of a purchasing card as the method of payment, where purchasing card information has been previously stored in the second database;

wherein the applet, in response to receiving the identification of the purchasing card as the method of payment, provides the identification of the purchasing card to the first server which determines that the purchasing card has an owner different than the user based on information previously stored in the second database;

in response to determining that the purchasing card has an owner different than the user, the first server then sends an email to the owner that includes a link to a web page provided by the first server;

in response to owner having selected the link, the first server displays a validation panel user interface for the owner that provides selections for indicating whether the user is authorized to use the purchasing card and for entering an identification of the owner;

in response to receiving the selection that indicates that the user is authorized to use the purchasing and receiving the identification of the owner, the first server then determines whether the identification matches an identification of the owner stored in the second database; and

in response to determining that the received identification of the owner matches the stored identification of the owner, the first server then completes the registration of the user by indicating in the second database that user is authorized to use the purchasing card as the form of payment.

11. The system of claim 10, wherein:

the first server includes a first server processor and a first server memory, the first server memory including a plurality of instructions configured to be executed by the server, the plurality of instructions configured to be executed by the server including the database registration instructions; and

the computer includes a processor and a memory, the memory including a plurality of instructions configured to be executed by the processor, the plurality of instructions configured to be executed by the processor including at least a portion of the database registration instructions, the at least a portion of the database registration instructions being received from the first server.

12. The system of claim 10, wherein:

the computer is to receive purchasing card information corresponding to one of the transactional account numbers; and

the second database is to store the received purchasing card information.

13. A computer-readable medium storing a plurality of instructions to be executed by a processor for database registration, the plurality of instructions comprising instructions to:

receive a user identifier of a user via a first set of input fields of a graphical user interface to begin registration for online purchasing;

send a query to a first database based at least in part on the user identifier;

receive a first set of data values of a first set of data fields from the first database, the first set of data values being associated with the user for purposes of identifying the user and being displayed in a display field of the graphical user interface;

receive a second set of data values from a data source via a second set of input fields of the graphical user interface, the second set of data values being associated with the user for purposes of electronic procurement authorization, the data source being different from the first database;

prompt the user to enter one or more additional data values via one or more corresponding input fields of the first graphical user interface;

store the first set of data values, the second set of data values and the one or more additional data values in a second database such that the first set of data values, the second set of data values and the one or more additional data values are contained within the second database concurrently and persistently, the second database being different from the first database;

prompt the user to enter a payment method for future online purchases under the registration provided by the second database;

in response to prompting for the payment method, receive identification of a purchasing card as the method of payment where purchasing card information has been previously stored in the second database;

in response to receiving the identification of the purchasing card as the method of payment, determine that the purchasing card has an owner different than the user based on information previously stored in the second database;

in response to determining that the purchasing card has an owner different than the user, then send an email to the owner that includes a link to a web page;

receiving a selection by the owner of the link to the web page;

in response to receiving the selection of the link, display a validation panel user interface for the owner that provides selections for indicating whether the user is authorized to use the purchasing card and for entering an identification of the owner;

in response to receiving the selection that indicates that the user is authorized to use the purchasing card and receiving the identification of the owner, then determine whether the identification matches an identification of the owner stored in the second database;

in response to determining that the received identification of the owner matches the stored identification of the owner, then complete the registration of the user by storing an indication that the user is authorized to use the purchasing card as the payment method;

if the user is not authorized to use the purchasing card then providing an option to the user to bill to an entity'"'"'s general ledger, and

if the user chooses to not bill to the general ledger, then prompting the user to enter a personal charge card number as the method of payment while indicating to the user that online purchases via the registration with the second database will not be possible without the personal charge card number.