METHOD AND SYSTEM FOR MAINTAINING LOGIN PREFERENCE INFORMATION OF USERS IN A NETWORK-BASED TRANSACTION FACILITY

Abstract

The present invention relates to various aspects for maintaining and utilizing login preference information of users of a network-based transaction facility. In one embodiment, user interface information is communicated to a client via a communications network. The user interface information includes information concerning a plurality of features within the network-based transaction facility. The user interface information also specifies a login interface that facilitates user input of login preference information pertaining to each of the plurality of features. Further, the login preference information is received from the client via the communications network and utilized to control user access to any of the plurality of features within the network-based transaction facility via the communications network.

Description

FIELD OF THE INVENTION

The present invention relates generally to the field of access restriction and, more specifically, to the maintaining login preference information of users in a network-based transaction facility such as, for example, an Internet-based auction facility.

BACKGROUND OF THE INVENTION

A network-based transaction facility (e.g., a business-to-business, business-to-consumer and consumer-to-consumer Internet marketplace and retailer) may offer its users a variety of features. For instance, an Internet-based auction facility may provide such features as bidding, listing, feedback, chatting, etc. Typically, users of a network-based transaction facility must enter their user identifier (user id) and password every time they perform any significant activity within the transaction facility. For example, in an auction facility, a user is required to enter his or her user id and password each time the user wishes to access a bidding feature, a listing feature, a feedback feature, or any other feature provided by the auction facility. Requiring a user to enter his or her user id and password multiple times during the user session within a transaction facility causes inconvenience to the user and destructs the user's attention from the online activity being performed.

SUMMARY OF THE INVENTION

The present invention relates to various aspects for maintaining and utilizing login preference information of users of a network-based transaction facility. In one embodiment, user interface information is communicated to a client via a communications network. The user interface information includes information concerning a plurality of features within the network-based transaction facility. The user interface also specifies a login interface that facilitates user input of login preference information pertaining to each of the plurality of features. Further, the login preference information is received from the client via the communications network and utilized to control user access to any of the plurality of features within the network-based transaction facility via the communications network.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a block diagram of one embodiment of a network-based transaction facility;

FIG. 2 is a block diagram of one embodiment of a database maintained by a database engine server;

FIG. 3 is a diagrammatic representation of one embodiment of a user information table within the database;

FIG. 4 is a flow chart of one embodiment of a method for maintaining login preference information of users of a network-based transaction facility;

FIG. 5 is a flow chart of one embodiment of a method for utilizing user login preference information within a network-based transaction facility;

FIG. 6 is a block diagram of one embodiment of an interface sequence implemented to maintain and utilize login preference information of users of a network-based transaction facility;

FIGS. 7-15 are exemplary representations of various interfaces included in the sequence of interfaces shown in FIG. 6; and

FIG. 16 is a block diagram of one embodiment of a computer system.

DETAILED DESCRIPTION

A method and system for maintaining and utilizing login preference information of users of a network-based transaction facility are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details.

Terminology

For the purposes of the present specification, the term “transaction” shall be taken to include any communications between two or more entities and shall be construed to include, but not be limited to, commercial transactions including sale and purchase transactions, auctions and the like.

Transaction Facility

FIG. 1 is block diagram illustrating an exemplary network-based transaction facility in the form of an Internet-based auction facility 10. While an exemplary embodiment of the present invention is described within the context of an auction facility, it will be appreciated by those skilled in the art that the invention will find application in many different types of computer-based, and network-based, commerce facilities.

The auction facility 10 includes one or more of a number of types of front-end servers, namely page servers 12 that deliver web pages (e.g., markup language documents), picture servers 14 that dynamically deliver images to be displayed within Web pages, listing servers 16, CGI servers 18 that provide an intelligent interface to the back-end of facility 10, and search servers 20 that handle search requests to the facility 10. E-mail servers 21 provide, inter alia, automated e-mail communications to users of the facility 10.

The back-end servers include a database engine server 22, a search index server 24 and a credit card database server 26, each of which maintains and facilitates access to a respective database.

The Internet-based auction facility 10 may be accessed by a client program 30, such as a browser (e.g., the Internet Explorer distributed by Microsoft Corp. of Redmond, Wash.) that executes on a client machine 32 and accesses the facility 10 via a network such as, for example, the Internet 34. Other examples of networks that a client may utilize to access the auction facility 10 include a wide area network (WAN), a local area network (LAN), a wireless network (e.g., a cellular network), or the Plain Old Telephone Service (POTS) network.

Database Structure

FIG. 2 is a database diagram illustrating an exemplary database 23, maintain by and accessed via the database engine server 22, which at least partially implements and supports the auction facility 10. The database 23 may, in one embodiment, be implemented as a relational database, and includes a number of tables having entries, or records, that are linked by indices and keys. In an alternative embodiment, the database 23 may be implemented as collection of objects in an object-oriented database.

Central to the database 23 is a user table 40, which contains a record for each user of the auction facility 10. A user may operate as a seller, buyer, or both, within the auction facility 10. A user information table 41 is linked to the user table 40 and includes more detailed information about each user. The database 23 also includes item tables 42 that may be linked to the user table 40. Specifically, the tables 42 include a seller items table 44 and a bidder items table 46. A user record in the user table 40 may be linked to multiple items that are being, or have been, auctioned via the facility 10. A link indicates whether the user is a seller or a bidder (or buyer) with respect to items for which records exist within the item tables 42. The database 23 also includes a note table 48 populated with note records that may be linked to one or more item records within the item tables 42 and/or to one or more user records within the user table 40. Each note record within the table 48 may include, inter alia, a comment, description, history or other information pertaining to an item being auction via the auction facility 10, or to a user of the auction facility 10.

A number of other tables are also shown to be linked to the user table 40, namely a user past aliases table 50, a feedback table 52, a feedback details table 53, a bids table 54, an accounts table 56, an account balances table 58 and a transaction record table 60.

FIG. 3 is a diagrammatic representation of an exemplary embodiment of the user information table 41. The user information table 41 stores detailed information about each user participating in the action facility 10. The table 41 includes a user identifier column 72 that stores, for each entry, a user identifier providing a pointer to the user table 40. A name column 74 stores the full name of each user. A gender column 76 stores the gender of each user. An e-mail address column 78 stores each user's e-mail address. A password preferences column 80 stores user login preference information that pertains to a plurality of features offered by a network-based transaction facility (e.g., auction facility 10).

It will be appreciated that other descriptive information may also populate the user information table 41.

Maintaining Login Preference Information

In order to facilitate the convenience and efficiency of users conducting business transactions within a network-based transaction facility such as auction facility 10, the present invention proposes a method and system whereby a user may provide his or her login preference information pertaining to any of a plurality of features offered by the network-based transaction facility. This login preference information is stored in a database (e.g., database 23) and utilized when a determination is made as to whether to require the user to enter his or her user identifier (user id) and password for accessing a feature within the network-based transaction facility.

FIG. 4 is a flow chart of one embodiment of method 400 for maintaining login preference information of users of a network-based transaction facility.

Method 400 begins with communicating user interface information to a client via a communications network (processing block 404). The user interface information includes information concerning a plurality of features within the network-based transaction facility. For instance, the plurality of features within network-based auction facility 10 may include such features as bidding, listing, feedback, chatting, etc. The user interface information also specifies a login interface that facilitates user input of login preference information pertaining to the features offered by the network-based transaction facility. In one embodiment, the login preference information indicates whether a user password should be remembered for each of these features. In one embodiment, these features do not include the features that involve display of user personal information. For instance, the user will be always required to enter a password for any feature that may display the credit card information or registration information of the user.

At processing block 406, the login preference information is received from the client via the communications network (e.g., via Internet). In one embodiment, the login preference information is stored in a database (e.g., in table 41 of database 23). Further, at processing block 410, the login preference information is utilized when providing user access to one of the features offered by the network-based transaction facility. One embodiment for utilizing the login preference information is described in greater detail below in conjunction with FIG. 5.

In one embodiment, the user is presented with an interface that allows the user to change the login preference information. In this embodiment, the database is updated each time the user changes the login preference information.

In one embodiment, when the user logs on into the transaction facility, a determination is made as to whether the user has previously provided the login preference information. If the determination is positive, a welcome user interface is presented to the user. The welcome user interface includes information indicating that the user has previously provided the login preference information and contains a link to a login preference interface, which allows the user to modify the existing login preference information.

FIG. 5 is a flow chart of one embodiment of a method 500 for utilizing user login preference information within a network-based transaction facility.

Method 500 begins with initiating a user session (processing block 504). The user session is typically initiated when the user logs into the network-based transaction facility by providing his or her logon information (e.g., user id and password). Next, user login preference information is retrieved from a database (processing block 506) and stored in a session cookie (processing block 508). The session cookie may also store other information such as, for example, client's IP address, cookie ID, user ID, etc. In one embodiment, the information stored in the session cookie is encrypted. In one embodiment, the session cookie expires in a predefined time period (e.g., 20 minutes) if the user conducts no activity within the network-based transaction facility or if the user logs out (e.g., via the regular logout procedure or by closing the browser).

Subsequently, during the session, the user submits a request to access a particular feature within the network-based transaction facility (e.g., by activating a link or a button). Upon receiving the user request (processing block 510), a determination is made as to whether the requested feature always requires a password (decision box 512). In one embodiment, the password is always required for a feature involving display of user personal information such as, for example, the credit card information or registration information of the user. If the requested feature always requires a password, the user password is requested (processing block 514) and, upon receiving the correct password, access to the requested feature is provided (processing block 520).

Otherwise, if the requested feature is not designated as always requiring a password, login preference information pertaining to the requested feature is retrieved from the session cookie (processing block 514). Next, a determination is made as to whether the user has selected to require a password for this feature using the login preference information (processing block 516). If a password is required, the user is requested to enter a password (processing block 518), and if the entered password is correct, the access to the feature is provided (processing block 520). If the login preference information indicates that the password is not required, method 500 flows directly to processing block 520, which provides user access to the requested feature.

User Interfaces

FIG. 6 shows an interface sequence 700, according to an exemplary embodiment of the present invention, that may be implemented by auction facility 10 to maintain and utilize login preference information of users. Exemplary representations of the various interfaces included within sequence 700 are shown in FIGS. 7-15.

Interface sequence 700 commences with a login interface 708 through which a user of auction facility 10 provides at least a user identifier and associated password. Login interface 708 may be accessed via a number of interfaces communicating information pertaining to various features offered by auction facility 10 (e.g., bidding interface 702 or history and email request interface 704), each of which comprises a markup language document (e.g., HTML document) including a hypertext link to an object that generates login interface 708 as well as further interfaces of sequence 700. In one embodiment, login interface 708 also allows a user to request not to use a cookie during his or her online activity within auction facility 10.

If the user logs on into auction facility 10 via login interface 708 for the first time, the user is presented with setup preferences interface 710 which specifies various features offered by auction facility 10 and facilitates user input of login preference information pertaining to each of these features. That is, the user may indicate via setup preferences interface 710 whether the user wants to have his or her password remembered for each feature. After the user preferences are set, preferences confirmation interface 712 is displayed to inform the user that the preference settings have been saved and that the user may modify them upon accessing my preferences interface 716.

If the user logs on into auction facility 10 via login interface 708 not for the first time (i.e., the user has previously provided user login preference information), welcome interface 714 is displayed that welcomes the user by name and includes a link to my preferences interface 716. My preferences interface 716 displays existing user login preferences, i.e., identifies the features of auction facility 10 for which the user wishes to have the user password remembered, and allows the user to modify the existing preferences. Preferences confirmation interface 712 confirms that the user settings have been saved.

Further, when the user wishes to access a feature within auction facility 10, the user may or may not be required to enter a password depending on the user login preferences. For instance, if the user selected to have his or her password remembered for a bidding feature, bidding interface 720 is provided without requiring the user to enter the password. If the user chose not to have the password remembered for the bidding feature, the user is requested to enter the password before accessing bidding interface 720. In addition, bidding interface 720 includes a link to my preferences interface 716 to allow the user to modify the login preferences.

If the user wishes to view history or email address of another user, the user may be required to enter the password via history and email request interface 722 or, alternatively, directly receive the requested information depending on the user setting for this feature.

It should be noted that interfaces of other features may be included within sequence 700 instead of, or in addition to, any of bidding interface 720 and history and email request interface 722 depending on what features the user wishes to access during his or her online activity within auction facility 10.

FIGS. 7-15 are exemplary representations of various interfaces included in sequence 700. FIGS. 7 and 15 are exemplary representations of a bidding interface. Bidding interface 702 of FIG. 7 is displayed to a user who has not previously set his or her login preferences. Bidding interface 702 includes button 802 allowing the user to set the login preferences via login interface 708. Bidding interface 720 of FIG. 14 is displayed to a user who has already set the login preferences in a previous session. Bidding interface 720 provides link 1502 to my preferences interface 716 allowing the user to modify the existing login preferences.

FIGS. 8 and 15 are exemplary representations of a history and email request interface. History and email request interface 704 of FIG. 8 is displayed to a user who has not previously set his or her login preferences and includes button 902 allowing the user to set the login preferences via login interface 708. History and email request interface 722 of FIG. 15 is displayed to a user who has previously selected not to have a user password remembered for this feature and includes link 1606 to my preferences interface 712 allowing the user to modify the existing login preferences.

FIG. 9 is an exemplary representation of login interface 708. Login interface 708 provides user identifier field 1002 and password field 1004 into which the user may enter a user identifier and password. In addition, the user may request not to use a cookie during the user online activity within auction facility 10 using link 1006.

FIG. 10 is an exemplary representation of setup preferences interface 710 which specifies various features offered within auction facility 10, namely selling, chat, my page, bidding, feedback, and other features. Check boxes 1102, 1104, 1106, 1108, 1110 and 1112 allow the user to set his or her preference for each of these features. That is, if the user checks any of these check boxes, the user will not be required to provide a password before accessing a corresponding feature. Note 1114 indicates that the user may change his or her preferences at any time using my preferences interface 716.

FIG. 11 is an exemplary representation of preferences confirmation interface 712 which notifies the user that the user login preference information has been saved.

FIG. 12 is an exemplary representation of welcome interface 714 which is displayed if the user has already provided the login preference information in a previous session. Welcome interface 714 includes link 1302 to my preferences interface 716 which allows the user to change the existing login preferences.

FIG. 13 is an exemplary representation of my preferences interface 716. My preferences interface 716 specifies user preferences for various features such as selling, chat, my page, bidding, feedback, and others. The user may change any of the existing preferences via check boxes 1102, 1104, 1106, 1108, 1110 and 1112.

In summary, it will be appreciated that the above described interfaces, and underlying technologies, provide a convenient vehicle for the inputting and modifying of user login preferences pertaining to various features offered by auction facility 10.

Computer Architecture

FIG. 16 shows a diagrammatic representation of machine in the exemplary form of a computer system 1700 within which a set of instructions, for causing the machine to perform any one of the methodologies discussed above, may be executed. In alternative embodiments, the machine may comprise a network router, a network switch, a network bridge, Personal Digital Assistant (PDA), a cellular telephone, a web appliance or any machine capable of executing a sequence of instructions that specify actions to be taken by that machine.

The computer system 1700 includes a processor 1702, a main memory 1704 and a static memory 1706, which communicate with each other via a bus 1708. The computer system 1700 may further include a video display unit 1710 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 1700 also includes an alpha-numeric input device 1712 (e.g. a keyboard), a cursor control device 1714 (e.g. a mouse), a disk drive unit 1716, a signal generation device 1720 (e.g., a speaker) and a network interface device 1722.

The disk drive unit 1716 includes a computer-readable medium 1724 on which is stored a set of instructions (i.e., software) 1726 embodying any one, or all, of the methodologies described above. The software 1726 is also shown to reside, completely or at least partially, within the main memory 1704 and/or within the processor 1702. The software 1726 may further be transmitted or received via the network interface device 1722. For the purposes of this specification, the term “computer-readable medium” shall be taken to include any medium that is capable of storing or encoding a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methodologies of the present invention. The term “computer-readable medium” shall accordingly be taken to included, but not be limited to, solid-state memories, optical and magnetic disks, and carrier wave signals.

Thus, a method and system for maintaining login preference information of users of a network-based transaction facility have been described. Although the present invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims

1-20. (canceled)

21. A method, comprising: detecting, by a server, a successful login by a user to a network facility;accessing, by the server, user information to acquire login preference information for the user; andconfiguring, by the server, the network facility to selectively activate features for the network facility based on the login preference information.

22. The method of claim 21 further comprising, monitoring, by the server, selections of the features and inspecting the login preference information with each selection to determine whether the user has to supply a password for access to that selection.

23. The method of claim 21 further comprising, determining, by the server, whether to retain the login preference information for a session between the user and the network facility based on the login preference information.

24. The method of claim 21 further comprising, presenting, by the server, a link to the user to modify the login preference information.

25. The method of claim 21 further comprising, removing, by the server, a session cookie that houses the login preference information when an event indicates that the user has logged out of or was forced out of a session with the network facility.

26. The method of claim 21 further comprising, overriding, by the server, contrary directions defined in the login preference information and requesting that the user enter a password when accessing a particular feature of the network facility that is to display personal information associated with the user.

27. The method of claim 21, wherein detecting further includes receiving notification of the successful login from the network facility along with an indication that the user is accessing the network facility via a phone.

28. The method of claim 21, wherein accessing further includes acquiring the login preference information from a database associated with the network facility and indexed within the database based on an identity for the user.

29. A method, comprising: presenting, by a server, an interface to a user for defining preference information for a network facility;receiving, by the server, selections within the interface for the preference information, a number of the selections defining particular features of the network facility and how the user is to interact with those particular features when the user subsequently authenticates to the network facility for access; andrecording, by the server, the preference information and its association with the user for customized access to the network facility by the user with subsequent communication sessions between the user and the network facility.

30. The method of claim 29, wherein presenting further includes authenticating the user for initial access to the network facility.

31. The method of claim 29, wherein receiving further includes recording a particular selection as an instruction to force the user to supply a user password each time the user accesses a particular feature of the network facility.

32. The method of claim 29, wherein receiving further includes recording a particular selection as an instruction to automatically remember and supply a user password on behalf of the user each time the user accesses a particular feature of the network facility where the user password is requested.

33. The method of claim 29, wherein receiving further includes recording a particular selection as an instruction to set the preference information within a client of the user for the subsequent communication sessions.

34. The method of claim 29, wherein receiving further includes recording a particular selection as an instruction to exclude the setting of the preference information within a client of the user for the subsequent communication sessions.

35. The method of claim 29, wherein receiving further includes recording a particular selection as an instruction to encrypt the preference information before recording or setting the preference information for use with the subsequent communication sessions.

36. The method of claim 29, wherein recording further includes indexing the preference information in a database associated with the network facility based on an identifier for the user.

37. A system, comprising: a server configured and programmed with a network facility that executes on the server and that interacts with users over a network; andthe network facility configured to interact with each of the users to define preference information for each user that identifies how each user interacts with user-selected features of the network facility, the preference information enforced by the network facility each time a particular user logs into and interacts with the network facility.

38. The system of claim 37, wherein the network facility is configured to interact with particular users accessing the network facility via phones.

39. The system of claim 37, wherein the network facility is configured to override some aspects of the preference information during interactions with the users.

40. The system of claim 37, wherein the network facility is configured to set the preference information within applications that process on client devices of the users for use by the network facility during interactions with the users.