System and method for selective information exchange

[0001] This application claims priority under 35 U.S.C. § 120 as a continuation-in-part to co-pending U.S. patent application Ser. No. ______, filed Mar. 31, 2000, entitled “System and Method for Selective Information Exchange,” which claimed priority under 35 U.S.C. § 119(e), of U.S. Provisional Application No. 60/127,114, filed Mar. 31, 1999. Both applications are specifically incorporated herein, in their entirety, by reference.

[0002] 1. Field of the Invention

[0003] The present invention relates to systems and methods for storing, accessing and exchanging information, and in particular to a system and method for providing users with granular control over arbitrary information that allows for selective, real-time information sharing in a communications network such as the Internet.

[0004] 2. Description of Related Art

[0005] Information exchange is a common facet of everyday life. For many years, individuals have manually distributed their personal information, such as by passing out business cards, filling out forms, surveys and warranty cards with their names and addresses, providing career and educational information on their resumes and reciting their credit card numbers over the telephone while making purchases. In addition, individuals have manually collected the personal information of others, such as by collecting business cards, maintaining an address book or Rolodex™ and storing telephone books and catalogs. As the amount of exchanged information has grown, the drawbacks and limitations of manual information exchange have become more glaring—i.e., manual information exchange is disorganized, error-prone, repetitive and time-consuming.

[0006] In the last decade the amount of exchanged information has exploded, in large part due to the widespread use of computer systems and other electronic devices. Many individuals now have several home and work telephone numbers (used for different purposes such as fax or modem access, pagers, and mobile communication), web site addresses, electronic mail (“e-mail”) addresses, electronic bank account numbers, and a variety of other personal identification information. This information is typically stored electronically in databases tied to applications such as personal calendars and personal contact managers, and is typically exchanged through electronic systems such as e-mail and voicemail. Businesses, organizations and other entities have faced even greater growth in the amount of information that is stored and exchanged.

[0007] To exchange information, a copy of the information is typically transmitted to the intended recipient. The recipient may desire the information for a transient purpose (e.g., a credit card number for a one-time purchase), in which case the information copy may be discarded after use, or the recipient may desire the information for a continuing use, in which case the information copy may be stored by the recipient in a database. Each time the individual transmits the information to a new recipient, a new copy of the information is generated, and potentially stored in an additional database. This approach to information exchange is characterized with certain drawbacks, such as the lack of control over the copy of the information once it is transmitted and the excessive redundancy that results each time the copied information is stored in another database. Another problem is that copies of the data often become out-of-synchronization, and thus obsolete, as information such as telephone numbers and addresses change.

[0008] The tasks of managing, protecting and updating information has grown increasingly burdensome, especially in cases where the information is accessed by a plurality of applications and systems and the stored information is copied to many databases located in different locations. For example, an individual may provide personal address information to hundreds of recipients, such as creditors, subscription, delivery and repair services, friends, family, business associates, etc. Each of these recipients may then store this personal address information in their own databases, such as address books and customer lists. If this personal address information changes (e.g., when the individual changes residence), updating the information requires the individual to transmit a copy of the new information to every individual, business and organization that has a copy of the personal address information. Each recipient must then update each of its databases that have this personal address information. Information such as telephone numbers, home addresses, e-mail addresses and credit card numbers change frequently, making the process of synchronizing information extremely time consuming, burdensome and prone to error. The accuracy and timeliness of this information is important for business communications, interpersonal communications, purchases and various other purposes. Thus, there exists a need in the art for information exchange that is simple, efficient, timely, and is not error-prone.

[0009] Certain modern applications provide electronic solutions to some of these problems by synchronizing data in limited contexts. For example, personal digital assistants (“PDAs”) are handheld devices that include an internal memory for storing a copy of the user's personal calendar, address and e-mail information. Another copy of the information is typically stored on a personal computer through applications such as Microsoft Outlook™ and CorelCENTRAL™. When the user adds or updates stored information on either the personal computer or the PDA, the stored information on the other system will be temporarily out of date. A typical PDA includes a cradle that may be connected to the personal computer to provide a communications link between the two systems. When the PDA is inserted into the cradle, the user can press a button on the PDA to synchronize the stored information in the two devices. While this solution is adequate for some personal information, it is characterized with much of the same drawbacks discussed above. The data will be untimely until the PDA is physically placed into the cradle and the synchronization function is performed. Further, stored information that has been exchanged with third parties will not be updated through this synchronization procedure. The third parties will need to be individually contacted with the new information and the third party will then need to update each of its databases.

[0010] Another solution in the prior art is to provide a centralized database that multiple individuals may access. For example, a university may keep its alumni information in a centralized database that is accessible to its alumni through the Internet. Individual alumni may edit their information profiles and view the profiles of other alumni through a university web site. Because the same copy of the stored personal information is used for both updating and viewing, there is no need to transmit copies of the personal information to other alumni when the information is updated. Although the centralized database simplifies information exchange between alumni, there are still many drawbacks. For example, the user would still need to notify non-alumni (e.g., creditors, family, friends, business contacts) of the changed information. Further, the data may not be gathered in a manner that is useful for the user. Many individuals would prefer to maintain their own database of contacts that are relevant to the individual, and this database would likely include non-alumni (e.g., creditor information, family, friends), and exclude many alumni. As a result, information stored in centralized databases is still copied to individuals' personal address books and other databases.

[0011] Another problem in the prior art is controlling access to stored information. For example, an individual may want to provide broad access to personal contact information such as address and telephone number, but may not wish to publicly share credit card information that is stored in the same database. While making an online purchase, the individual may need to provide the public address information as well as the personal credit card information. Thus, it would be desirable for a secure system and method that would provide individuals with control over their stored information so that the individual can control who and for how long that information is accessible.

[0012] In view of these problems with the prior art, there exists a need for a system and method for information exchange that provides control over the content of stored information, as well as control over the access to the stored information. Individuals, businesses, and other entities should be able to group and customize the stored information in a useful manner. The system and method should be easy to use, efficient and allow for timely sharing of information with selected individuals on a granular level and provide security against unwanted disclosures and edits to the stored information.

[0013] The present invention provides a system and method for information exchange that provides control over the content of stored information, as well as control over the access to the stored information. Each user of the system and method has granular control over its own user profile information, and can control access to each stored data element of its user profile information on a user-by-user basis.

[0014] In accordance with a preferred embodiment of the present invention, an information exchange system includes a storage system adapted to store profile data for a plurality of users. The information exchange system is connected to one or more registered users through a communications network, such as the Internet, to allow each respective registered user to access, edit and manage the registered user's profile data through a network device. The network device may be any device that is adapted to communicate with the information exchange system through the network, such as a personal computer running a standard Internet web browser application, a personal digital assistant (“PDA”), a wireless application protocol telephone (“WAP phone”), a pager or a network appliance. The information exchange system includes a plurality of online applications that are accessible to the registered user and generate or make use of profile data having attributes that are proprietary to the registered user. In the preferred embodiment, the applications available to the registered user include personal e-mail, chat rooms, personal calendars, contact management and document management applications.

[0015] The registered user's attributes may be stored in pre-defined data fields created by the information exchange system and its applications, or in user-defined data fields created by each respective registered user. One or more of these attributes (both pre-defined and user-defined) may be logically grouped into views that also may be either pre-defined or user-defined. The registered user may selectively grant access to each view to one or more third parties, such as friends or family members. Preferably the registered user's profile data is kept private by the information exchange system until the registered user provides access to a view of the stored data.

[0016] In addition to profile data generated through applications such as e-mail and personal calendar, the information exchange system may be used to track the registered user's use of the network, including places visited, pages read, items purchased online, etc. This data, along with the other profile data, is valuable to both the registered user and vendors who may wish to direct advertisements or product offers to the registered user. In a preferred embodiment of the present invention, the vendors will not receive this information unless and until the registered user provides access to the vendor. Further, the registered user may selectively “push” certain subsets of profile data to one or more vendors, or to a centralized recommendation engine. Each vendor may use the pushed profile information to direct advertisements, product offers and other information to the registered user, as well as to automatically fill in data entry forms with relevant profile information. If the profile information is pushed to a centralized recommendation engine, then the profile information is processed and appropriate vendor information from one or more vendors (such as a product offer) may be selectively provided to the registered user. The registered user may have control over which vendors have access to its profile data, and which subsets of the profile data are provided to those vendors.

[0017] The information exchange system and its storage system may be distributed across a plurality of devices, which may be physically located in one or more geographic locations. Further, one or more affiliated entities, including its own storage system for storing profile data, may also be connected to the network. The affiliated entity may be any entity that desires to maintain control over its internal information, such as a corporation running an intranet. The affiliated entity may include e-mail, document management, calendaring, internal contact databases and other applications, and the data from these various applications may be stored on the data storage system.

[0018] In operation, the registered user may access profile data located on any information exchange system or affiliated entity that is connected to the network, provided access has been granted to the registered user. The registered user logs onto either an affiliated entity or an information exchange system, preferably through a World Wide Web address. When the registered user requests profile data, the profile data is automatically retrieved from the various locations and made available to the registered user. In a preferred embodiment, the affiliate includes a software firewall that can prevent external access to a subset of the profile data stored on its affiliate storage system. Through the software firewall, the affiliate, on a field-by-field and person-by-person basis, may prevent a certain subset of information from being accessed through the network, while allowing the remainder of the information to be freely accessed through the network if its associated registered user has granted access thereto.

[0019] The information exchange system may also be used with unaffiliated data storage sites such as an external e-mail system including an e-mail data storage, an external personal calendar database or an external file system. The information from such sites may be centrally accessed through the information exchange system.

[0020] In a preferred embodiment, intelligent synchronization software is loaded onto the network device of certain registered users. The intelligent synchronization software operates in the background to detect network activity, and then automatically pulls newly updated information from the information exchange system, such as new addresses, e-mail addresses and messages, meeting invitations, and new files stored on the information exchange system, onto the network device and updates any local databases with the new information. The intelligent synchronization software may also be used to update profile information stored on the information exchange system. The intelligent synchronization software may be used to provide Internet capabilities to standalone database applications and systems. An extensible synchronization engine is also provided that is operable with any device type, any record type, any transport protocol and any synchronization logic.

[0021] A preferred embodiment of the information exchange system includes a secure hardware configuration to protect the registered user's stored profile information from hackers. The information exchange system includes a main server and a plurality of secondary servers, connected through a first network. Each server is also connected directly to the network. The secondary servers are further connected, through a second network, to a storage system, a database management system and an e-mail system. The database management system stores user profile information and is additionally connected to a key management system.

[0022] When a user first registers with the information exchange system, a unique user identification (“ID”) is generated, as well as a random public/private key pair which is generated by the key management system. In order to store information on the information exchange system, the key management system generates a secret key for each separately stored data element. Each data element is encrypted with its secret key, and then stored in a database table, along with a universal identifier (“ID”) for the data element. The secret key is encrypted using the user's public key, and the encrypted secret key is then stored in a key chain database, along with the user's unique ID and the universal ID. Because all of the data is encrypted, other users of the information exchange system cannot view the content of any stored data element of user profile information unless access is provided to that content's secret key.

[0023] To grant access to stored data, the registered user first selects a data element from the user's stored profile information. The registered user then selects one or more third party users to which access to the selected data element is to be granted. The information exchange system then retrieves the third party's public key from its user profile. The registered user's copy of the encrypted secret key for the selected data element is located, and it is decrypted using the registered user's private key. The secret key is then encrypted using the third party's public key, and stored in the key chain database, along with the third party's user ID and the universal ID for the data element. The registered user may create a view of one or more data elements, and access to one or more views may be granted to one or more groups of users created by the registered user. In the preferred embodiment, pre-defined views and groups are also provided.

[0024] After access has been granted, it can be denied on an element-by-element and person-by-person basis. First, the registered user selects one or more users and one or more data elements. For each user, the key chain database is searched for every record including the associated user ID and a universal ID of a selected data element. Each record, which includes the encrypted secret key generated by the registered user when access was first granted to the user, is then deleted.

[0025] In the preferred embodiment, if the registered user forgets his password, then the registered user's private key cannot be recovered from the key management system due to the system's security features. Without the proper private key, the registered user's encrypted secret keys cannot be decrypted, and consequently, none of the encrypted data elements can be decrypted. As a result, the registered user cannot access its own user profile. To solve this lost password problem, a preferred embodiment includes a key escrow feature that tracks a virtual registered user. The virtual registered user includes many of the same features as an actual registered user, including a public/private key pair. Every time a data element is stored on the information exchange system, the virtual registered user is automatically granted access to the data. In other words, a copy of the secret key for the new data element is encrypted using the public key of the virtual registered user and stored in the key chain database.

[0026] A preferred embodiment of a password recovery process includes the steps of, generating a new password; creating a new public/private key pair; generating a temporary password; searching the key chain database for every instance of the registered user's ID, and for each record found decrypting an associated secret key with the virtual registered user's private key; encrypting the secret key using the new public key; and storing the new encrypted secret key in the key chain database.

[0027] A more complete understanding of the SYSTEM AND METHOD FOR SELECTIVE INFORMATION EXCHANGE will be afforded to those skilled in the art, as well as a realization of additional advantages and objects thereof, by a consideration of the following detailed description of the preferred embodiment. Reference will be made to the appended sheets of drawings which will first be described briefly.

[0028] FIG. 1 illustrates a first preferred embodiment of the present application;

[0029] FIG. 2 illustrates a preferred embodiment of element-by-element, user-by-user access to profile information;

[0030] FIG. 3 is a preferred embodiment of the information exchange system hardware system;

[0031] FIG. 4 illustrates a preferred embodiment of the data flow through the information exchange system of FIG. 3;

[0032] FIG. 5 illustrates a preferred embodiment of the information exchange of the present invention;

[0033] FIG. 6 is a flow diagram illustrating the encryption of data elements in a preferred embodiment of the present invention;

[0034] FIG. 7 is a flow diagram illustrating the preferred steps for granting an arbitrary third party user access to an arbitrary data element;

[0035] FIGS. 8a-c illustrate a preferred embodiment for providing one or more groups of arbitrary users access to one or more views of arbitrary data elements;

[0036] FIG. 9 is a flow diagram illustrating preferred steps for granting to an arbitrary group access to an arbitrary view;

[0037] FIG. 10 is a flow diagram illustrating preferred steps for retrieving stored information from the information exchange system;

[0038] FIG. 11 is a flow diagram illustrating a preferred password recovery process;

[0039] FIG. 12 illustrates a decentralized information exchange system;

[0040] FIG. 13 illustrates a preferred embodiment of a software firewall;

[0041] FIG. 14 is a flow diagram illustrating preferred steps for retrieving stored information from an affiliate system through its software firewall;

[0042] FIGS. 15a-b illustrate database structures in accordance with a preferred embodiment of the present application;

[0043] FIG. 16 is a block diagram illustrating a system architecture;

[0044] FIG. 17 is a block diagram showing a system database schema of an embodiment of the present invention;

[0045] FIG. 18 is a block diagram showing a calendar module database schema of an embodiment of the present invention;

[0046] FIG. 19 is a block diagram showing a mail module and storage module database schemas of an embodiment of the present invention;

[0047] FIG. 20 is a block diagram showing a chat module database schema of an embodiment of the present invention;

[0048] FIG. 21 is a block diagram of a structure of one web site embodiment of the present invention showing the interrelationship of the various modules;

[0049] FIG. 22 is a flow diagram showing an initial login sequence for both new users and members;

[0050] FIG. 23 is a block diagram of a registration page;

[0051] FIG. 24 is a block diagram of the initial selection screen;

[0052] FIG. 25 is a block diagram showing the system information management module;

[0053] FIG. 26 is a block diagram of the system information management module;

[0054] FIG. 27 is a block diagram of a primary information section of the information management module of FIG. 26;

[0055] FIG. 28 is a diagram of the information view requests page;

[0056] FIG. 29 is a block diagram showing the structure of a contacts management and address book module;

[0057] FIG. 30 is a block diagram for adding a contact to the contacts management and address modules;

[0058] FIG. 31 is a block diagram for searching for a number while using the contacts management and address modules;

[0059] FIG. 32 is a block diagram of the group editor of the group management section of the address book module;

[0060] FIG. 33 is a block diagram of the information views section of the information management module;

[0061] FIG. 34 is a block diagram showing a calendar system structure;

[0062] FIG. 35 is a block diagram showing an e-mail system structure;

[0063] FIG. 36 is a block diagram showing a virtually unlimited storage system, which may be called the ZDRIVE system;

[0064] FIG. 37 is a block diagram showing a chat system structure;

[0065] FIG. 38 is a block diagram showing a search system structure;

[0066] FIG. 39 is a flow diagram showing the steps for a member to grant access to one or more information views to other members;

[0067] FIG. 40 is a flow diagram showing the steps for a member to grant access to one or more information views;

[0068] FIG. 41 is a flow diagram showing the steps for a member to view personal information from other members to which they have previously been granted access;

[0069] FIG. 42 is a flow diagram showing the steps for accessing an information view previously created by a member;

[0070] FIG. 43 is a flow diagram showing the steps for a member to grant access to files uploaded to selectively access an infinite storage system;

[0071] FIG. 44 is a flow diagram showing the steps for a member to grant access to the one or more files by using instant access codes;

[0072] FIG. 45 is a flow diagram showing the steps for a user to access one or more of the files;

[0073] FIG. 46 is a flow diagram showing the steps of accessing the files using one or more instant access codes;

[0074] FIG. 47 is a flow diagram showing the steps for a member to grant access to a chat event created by the member;

[0075] FIG. 48 is a flow diagram showing the steps for a member to grant access to the chat event by using instant access codes;

[0076] FIG. 49 is a flow diagram showing the steps for a member to enter the chat event;

[0077] FIG. 50 is a flow diagram showing the steps for entry into the chat event by using an instant access code;

[0078] FIG. 51 is a flow diagram showing the steps for displaying context sensitive ads throughout navigation of the system;

[0079] FIG. 52 illustrates information snarfing in accordance with a preferred embodiment of the present invention;

[0080] FIG. 53 illustrates a preferred embodiment of preference pushing in accordance with a preferred embodiment of the present invention;

[0081] FIG. 54 illustrates a preferred embodiment of the preference pushing information flow;

[0082] FIG. 55 illustrates an alternate embodiment of the preference pushing information flow;

[0083] FIG. 56 provides an example of an application utilizing a preferred embodiment of preference pushing;

[0084] FIG. 57 illustrates a preferred embodiment of intelligent synchronization in accordance with a preferred embodiment of the present application;

[0085] FIG. 58 illustrates a preferred embodiment of the information flow between a server and a client during intelligent synchronization;

[0086] FIG. 59 is a flow diagram illustrating preferred steps performed by the server while processing records received from a client during intelligent synchronization;

[0087] FIG. 60 illustrates a preferred database structure of a mapping database;

[0088] FIG. 61 is a flow diagram illustrating preferred steps performed by the server during intelligent synchronization to process information stored on the server;

[0089] FIG. 62 is a flow diagram illustrating preferred steps performed by a client in processing instructions received from the server during intelligent synchronization; and

[0090] FIG. 63 illustrates a synchronization engine in accordance with a preferred embodiment of the present invention.

[0091] In the detailed description that follows, like element numerals are used to describe like elements illustrated in one or more of the aforementioned figures.

[0092] A preferred embodiment of the present invention will be described with reference to FIG. 1. An information exchange system 10 includes a storage system 10a adapted to store profile data for a plurality of users, such as registered user 12. The information exchange system 10 and the registered user 12 are connected to a communications network 14, such as the Internet, thereby allowing the registered user 12 to access, edit and manage the registered user's profile data through a network device 12a. The network device 12a may be any device that is adapted to communicate with the information exchange system 10 through the network 14, such as a personal computer running a standard Internet web browser application, a personal digital assistant (“PDA”), a wireless application protocol telephone (“WAP phone”), a pager or a network appliance.

[0093] A profile is any non-trivial application that is used to access and manipulate a collection of attributes associated with the registered user 12. The information exchange system 10 includes a plurality of online applications that are accessible to the registered user 12 and include profile data having attributes that are proprietary to the registered user 12. In the preferred embodiment, the applications available to the registered user 12 include personal e-mail, chat rooms, personal calendars, contact management and document management applications. In addition, the information exchange system 10 includes facilities that allow the registered user 12 to enter, edit and store attributes in the storage system 10a, including profile data generated from any of the applications.

[0094] The registered user's attributes may be stored in pre-defined data fields created by the information exchange system 10 and its applications, or in user-defined data fields created by the registered user 12. One or more of these attributes (both pre-defined and user-defined) may be logically grouped into views that also may be either pre-defined or user-defined. The registered user 12 may selectively grant access to each view to one or more third parties 16, such as friends or family members, connected to the network 14 through a network device 16a. The third parties 16 may include registered users of the information system 10, unregistered users, or both.

[0095] In the preferred embodiment, the registered user's profile data is kept private by the information exchange system 10 until the registered user 12 provides access to a view of the stored data. As illustrated in FIG. 2, the registered user 12 can securely control access to its stored profile data on an element-by-element and user-by-user basis. Registered user 12 stores profile data 18, such as telephone number, street address and a credit card number, in the storage device 10a; through a data entry application accessed by the registered user 12 through the information exchange system 10. The information exchange system 10 further includes facilities that allow the registered user 12 to selectively grant access to this stored profile data to one or more third parties 17a-c on an element-by-element basis. As illustrated in tables 18 and 20, the registered user 12 granted an online vendor 17a access to its telephone number, street address and credit card number, and a business contact 17b was granted access to the registered user's telephone number.

[0096] The online vendor 17a can retrieve the registered user's telephone number, street address and credit card number 22a from the information exchange system 10 to fulfill an online purchase request. The business contact 17b can retrieve the registered user's telephone number 22b from the information exchange system 10, but cannot access any other profile data (such as street address and/or credit card number) because access to that information was not granted by the registered user 12. Finally, a telemarketer 17c who was not granted access from the registered user 12 to any of the registered user's profile data can attempt to retrieve the profile data from the information exchange system 10, but no profile data will be provided 22c.

[0097] In addition to profile data generated through applications such as e-mail and personal calendar, the information exchange system 10 may be used to track the registered user's 12 use of the network 14, including places visited, pages read, items purchased online, etc. This data, along with the other profile data, is valuable to both the registered user 12 and vendors who may wish to direct advertisements or product offers to the registered user 12. In a preferred embodiment of the present invention, the vendors will not receive this information unless and until the registered user 12 provides access to the vendor. Referring back to FIG. 1, the registered user 12 may selectively “push” certain subsets of profile data to one or more vendors 24. Each vendor 24 may use the profile information to direct advertisements, product offers and other information to the registered user 12 that may be of interest to the registered user 12 based on the pushed data. Alternatively, the profile data may be pushed to a recommendation database. The recommendation database processes the received data and, where appropriate, selectively provides vendor information, from one or more vendors, to the registered user.

[0098] The vendor may also use the pushed data to automatically fill in data entry forms or process electronic transactions. The registered user 12 has control over which vendors 24 have access to its profile data, and which subsets of the profile data are provided to those vendors 24. Because the control is in the hands of the registered user 12, the registered user 12 will likely receive intelligent commerce recommendations which provide actual value to the registered user 12. For example, the registered user 12 may provide access to profile information such as its favorite musical or play, its travel schedule and its online calendar to selected vendors 24. The vendors 24 may review the available time periods in the online calendar, review the travel schedule to determine the registered user's 12 location (such as city and hotel) on a given date, and recommend to the registered user 12 a local musical or play based on the registered user's 12 preferences. Using the automatic form fill and data pushing features of this embodiment, the vendor could, upon acknowledgement from the registered user (e.g., by a single click of a screen button), charge tickets for the musical or play to the registered user's credit card account.

[0099] The information exchange system 10 and its storage system 10a, may be distributed across a plurality of devices, which may be physically located in one or more geographic locations. Further, one or more affiliated entities 20, including a storage system 20a for storing profile data, may also be connected to the network 14. Each affiliated entity 20, such as a corporation with a private intranet, incorporates information exchange features of the present invention into its internal database system. The affiliated entity 20 may include e-mail, document management, calendaring, internal contact databases and other applications, and the data from these various applications may be stored on the data storage system 20a.

[0100] In operation, the registered user 12 may access profile data located on any information exchange system 10 or affiliated entity 20 that is connected to the network 14, provided access has been granted to the registered user 12. The registered user 12 first logs onto either an affiliated entity 20 or an information exchange system 10, preferably through a World Wide Web address, to identify itself to the system. When the registered user 12 requests profile data, the profile data is automatically retrieved from the appropriate location and made available to the registered user 12. The location of the data is transparent to the registered user 12, who may create, edit, access, store and provide access to profile data without regard to its physical storage location.

[0101] In a preferred embodiment, the affiliate 20 includes a software firewall that is used by the affiliate 20 to prevent external access to a certain subset of the profile data stored in the storage system 20a. Through the software firewall, the affiliate 20, on a field-by-field, user-by-user basis, may prevent a certain subset of information 20b from being accessed through the network 14, while allowing the remainder of the information to be freely accessed if its associated registered user has granted access thereto.

[0102] The information exchange system 10 may also be used with unaffiliated data storage sites such as an external e-mail system 30 including an e-mail data storage 30a, an external personal calendar database or an external file system. The information from such sites may be centrally accessed through the information exchange system 10. For example, if a registered user 12 has one or more external e-mail accounts, such as a work e-mail account at an unaffiliated business, or a personal e-mail account through the registered user's 12 Internet Service Provider (“ISP”), the information exchange system 12 may provide a centralized location to receive and send these e-mails. If the registered user 12 grants access to its external e-mail account, then the information exchange system 10 will periodically access the external e-mail system 30 to determine whether there is any new e-mail information. All new e-mail information is transmitted to, and stored on the information exchange system 10, where it can be accessed through the e-mail application on the information exchange system 10.

[0103] The information exchange system 10 may also be used with a plurality of existing software, such as CorelCENTRAL™ or Lotus Smartsuite™. In a preferred embodiment, intelligent synchronization software is loaded onto the registered user's 12 network device 1 2a. The intelligent synchronization software operates to detect network activity and, when network activity is detected, automatically pulls newly updated information from the information exchange system 10, such as new addresses, e-mail addresses and messages, meeting invitations, and new files stored on the information exchange system 10, onto the network device 12a and updates the local databases so that the local database, and the information exchange system, include synchronized information. This synchronization procedure may also include uploading new information stored on the network device 12a to the information exchange system 10. The intelligent synchronization software transmits the information between the information exchange system 10 and the network device 12a in the background, during periods of low traffic on the communications link between the network device 12a and the network 14, making the download process virtually imperceptible to the registered user 12. Through the intelligent synchronization software, standalone applications operating on the network device 12a are provided with a level of Internet functionality.

[0104] A preferred embodiment of the information exchange system 10 includes a secure hardware configuration such as illustrated in FIG. 3, to protect the registered user's stored profile information from hackers or other intruders who attempt to gain unsolicited access to the information exchange system 10. The information exchange system 10 includes a main server 40 and a plurality of secondary servers 44a-d, connected through a first network 42. Preferably, the main server 40 and each of the secondary servers 44a-d includes a Netfinity 5000™ web server, running a hardened Linux kernel to protect against unsolicited attacks. The main server 40 and each of the secondary servers 44a-d are additionally connected to the network 14, through high speed connections such as T1 lines.

[0105] The secondary servers 44a-d are further connected, through a second network 46, to a storage system 48, a database management system 50 and an e-mail system 54. The storage system 48 is used to provide general file storage for registered users of the information exchange system 10. The database management system 50 is connected to a key management system 52, and stores user profile information. In a preferred embodiment, the database management system 50 includes a Netfinity 7000™ server executing Oracle™ database software. The key management system 52 is preferably dedicated hardware adapted to securely generate and store encryption keys and perform certain encryption/decryption functions, such as nForce™ by nCipher Corporation, Woburn, Mass. For security purposes, the second network 46 is not directly accessible from the network 14.

[0106] FIG. 4 illustrates the flow of information between the various components of the information exchange system 10 and the network device 56. The network device 56 connects to the main server 40 through the network 14. The main server 40, performing workload balancing operations, distributes the user request to one of the secondary computers 44a-d in a manner that optimizes the processing resources of the information exchange system 10. In a preferred embodiment, the main server 40 distributes requests on a round-robin basis; however, other workload balancing approaches may also be used. The resource request is then processed by a secondary computer 44b which communicates with the network device 56 through the network 14.

[0107] In this embodiment, the network device 56 cannot communicate directly to a secondary server 44 through the network 14—all communications into the information exchange system 10 first pass through the main server 40. The secondary server 44b has full access to the storage system 48, the database management system 50 and the e-mail system 54 through the second network 46. However, the main server 40 and the secondary server 44b are adapted so that the main server 40 cannot communicate with the storage system 48, the database management system 50 and the e-mail system 54, either directly or through the secondary server 44. Because all outside communications pass through the main server 40, the network device 56 does not have direct access to the secondary server 44b or the stored profile information, making the stored profile information difficult to compromise from outside the information exchange system.

[0108] The operation of a preferred embodiment of the information exchange system will now be described with reference to FIGS. 5-8. An information exchange system 100 is connected to a network such as the Internet 102. A registered user 104, using a network device 104a, such as a personal computer, can manage personal information stored in a storage system 100a of the information exchange system 100, and control access to that information from third parties, such as merchant 108 connected to the Internet 102 through a network device 108a.

[0109] When the user 104 is first registered with the information exchange system 100, a unique user ID is generated for the user, as well as a public/private key pair which is generated by the key management system 100b. The public/private key pair are selected for use in a public key cryptography system, such as RSA cryptography. As known in the art, in RSA cryptography data is encrypted by using a public key, and can only be decrypted by the corresponding private key. Once encrypted, the data is virtually secure, subject to modern computational, economic and mathematical constraints. In a preferred embodiment, the private key is maintained by the key management system 100b and is not accessible from outside the key management system 100b.

[0110] Referring to FIG. 6, a preferred procedure for storing new profile information in the information exchange system 100 is illustrated. First, at step 120, the registered user 104 provides data content for storage in the information exchange system 100. The data content can include any information that may be stored in the information exchange system 100. For example, data content may be entered into a data entry form having fields such as name, address, telephone number and credit card number, or may include data that is entered into applications such as a personal calendar program, an e-mail program or any other application that generates user profile information.

[0111] After the user provides the desired information, the key management system 100b randomly generates a secret key in step 122 for each discrete data element. Each secret key will be used for encrypting and decrypting its respective data element. In the preferred embodiment, the encryption-decryption algorithm is a symmetrical algorithm, such as DES or Blowfish, in which the same secret key is used for both data encryption and data decryption. In step 124, each data element of the new user information is encrypted with its respective secret key, and then in step 126, each respective encrypted data element is stored, along with a unique universal identifier and the user's ID in a database table 110. The universal identifier is a unique serial number that is used to reference the location of its respective data element in the information management system 100, and includes information such as a domain name and a database name. In step 128, the secret key for each respective encrypted data element is itself encrypted using the registered user's public key. The encrypted secret key is then stored, in step 130, in a key chain database 112, along with the user's ID and the universal ID that identifies the location of the stored data element.

[0112] In the preferred embodiment, each separate data element of the user profile information stored on the information exchange system 100 is separately encrypted as described in the flow diagram of FIG. 6, on a field-by-field and record-by-record basis. Because all of the data is encrypted, other users of the information exchange system 100 cannot view the content of any data element of user profile information unless access is provided to that data element's secret key. Consequently, if the registered user 104 desires to provide access to certain profile information to a merchant 108, such as the registered user's credit card number, the user must first provide the merchant 108 with access to the secret key for each data element. The flow diagram of FIG. 7 illustrates the steps for granting an arbitrary third party user, such as merchant 108, access to an arbitrary data element, such as a credit card number. In step 140, the user selects a data element from the user's stored profile information. In step 142, the user selects a third party user, such as merchant 108, to which access to the selected data element will be granted. In step 144, the information exchange system 100 retrieves the merchant's 108 public key from the merchant's user profile. Next, in step 146, the registered user's copy of the encrypted secret key for the selected data element is located in the key chain database 112. The registered user's 104 private key is located by the KMS 100b and is used by the KMS 100b, in step 148, to decrypt the secret key. In step 150, the secret key is then encrypted using the third party's public key, and the encrypted secret key, the third party's user ID and the universal identifier for the data element are then stored in the key chain database 112.

[0113] After access has been granted, access can be subsequently denied on an element-by-element and person-by-person basis. First, an event occurs triggering the denial of access. For example, the registered user may select one or more user/data element pairs for which to deny access. It is further contemplated that access may automatically expire after the passing of a certain amount of time or a certain amount of accesses to the data element. For each user designated through the triggering event, the key chain database is searched for every record including the associated user ID and a universal ID of a selected data element. Each located record, which includes the encrypted secret key generated by the registered user when access was first granted to the user, is then deleted.

[0114] Referring to FIGS. 8a-c, a preferred embodiment for providing a plurality of arbitrary users access to a plurality of arbitrary data elements is described. Each registered user controls a plurality of profile data elements 160, which preferably include all of the registered user's stored profile information. Using the plurality of profile data elements 160, the registered user may create a plurality of views 162, each view including one or more arbitrary data elements selected by the registered user, and/or including one or more of the other views 162. For example, the registered user may group data elements such as first name, last name, employer name, business telephone, business e-mail, business street address, business city, business state and business zip, into a view for business contact information. To simplify the process of granting a third party access to a plurality of data elements, the registered user merely provides access to one or more view. Access to each data element in a view may be granted on an element-by-element basis according to the process illustrated in FIG. 7. In the preferred embodiment, the view is stored in a database table 163, which includes fields for storing a unique view ID for each respective view, a user ID for the owner of the view and a universal ID for each data element in the respective view. In another embodiment, the registered user may also designate a password for each view to provide instant access to third party users who are not registered users of the information management system. The registered user need only provide the third party user with the access code (e.g., verbally communicating the access code to a merchant over a telephone) to allow the third party user instant access to the desired information. Access to the unregistered user may be provided through a virtual registered user, as described herein.

[0115] Each registered user may selectively provide access to each view 162 to one or more third party users of the information exchange system. Selecting from a set of users 164 of the information exchange system, the registered user may create groups of third party users 166, each including one or more third party users and/or one or more groups of third party users 166. For example, the registered user may create separate groups for business associates, family members and friends. The registered user may then selectively grant any group of third party users 166 access to any view 162. As a result, each respective third party user in the selected group is granted access to each respective data element in the selected view. In the preferred embodiment, the group is stored in a database table 167, which includes fields for storing a unique group ID for each respective group, a user ID for the owner of the group and a user ID for each member of the respective group.

[0116] A preferred embodiment for granting a group of users 166 access to a selected view is illustrated in FIG. 9. In step 170, the registered user selects a view. In step 172, the registered user selects a group of third party users to which access to the selected view will be granted. In step 174, the information exchange system 100 retrieves, for each third party user in the group, the third party user's public key from its user profile. Next, in step 176, the registered user's copy of the encrypted secret key for each data element in the view is located. The registered user's private key is located by the KMS 100b and is used by the KMS 100b, in step 178, to decrypt each respective secret key for each respective data element in the selected view. In step 180, for each data element in the view, its associated secret key is separately encrypted with each third party user's public key, creating an encrypted secret key for each third party user, for each data element. In step 182, each separately encrypted secret key, the associated third party's user ID and the universal identifier for the associated data element is stored in the key chain database, thereby providing each third party user in the group with access to each data element in the view.

[0117] Selected third party users who have been granted access to selective elements of the registered user's profile information can retrieve the stored profile information. A preferred embodiment of the process of retrieving stored information from the information exchange system is illustrated in the flow diagram of FIG. 10, and will now be described with reference to FIG. 5. In step 190, the third party user, such as the merchant 108, requests access to a data element of the registered user's stored profile information. Each stored data element includes a unique universal ID. Records in the key chain database having the data element's universal ID and the third party user's ID are located in step 192. If no matching records are found, then access cannot be granted to the third party user (steps 194, 196). This should be apparent because, in accordance with the preferred embodiment, the data element is encrypted by a secret key, and all copies of the secret key are encrypted using the public keys of users of the system; the third party cannot gain access to the data element without access to, and a way to decrypt, the secret key. If a matching record is found in the key chain database, then the encrypted secret key from the matching record is decrypted using the third party user's private key in step 198. The decrypted secret key is then used to decrypt the requested data element in step 200.

[0118] Referring back to FIG. 5, in operation, the registered user 104 will have some stored personal profile information in information exchange system 100, such as a name, address, telephone number and credit card number. Further, the registered user 104 may provide access to selective views of the profile information to selected third parties, such as merchant 108. If the registered user 104 desires to purchase an item from the merchant 108 for delivery to the user's home, the registered user 104 need only provide the merchant 108 with a universal identifier for the view. The merchant 108 may then access the information exchange system 100, and gain access to the registered user's 104 stored data, including mailing address, telephone number and credit card information for payment.

[0119] In a preferred embodiment, all of the data that is accessible to a registered user, whether the data belongs to the registered user or another user, may be accessed by the registered user by using its public/private key pair. When the registered user logs onto the information exchange system and enters a password, the registered user is identified to the information exchange system, which can then locate the registered user's public key in the user profile data, and access the registered user's private key through the key management system. However, in the preferred embodiment, if the registered user forgets his password, then the registered user's private key cannot be recovered from the key management system due to the system's security features. Without the proper private key, the registered user's encrypted secret keys, which are used to decrypt accessible data elements, cannot be decrypted and consequently, none of the encrypted data elements can be decrypted.

[0120] To solve this lost password problem, a preferred embodiment includes a key escrow feature that tracks a virtual registered user. The virtual registered user includes many of the same features as an actual registered user, including a public/private key pair. Every time a data element is stored on the information exchange system, the virtual registered user is automatically granted access to the data. In other words, a copy of the secret key for the new data element is encrypted using the public key of the virtual registered user and stored in the key chain database.

[0121] The algorithm of FIG. 11 illustrates a preferred embodiment of the password recovery process. When a registered user loses its password, the system has no way of recovering the lost password and a new password must be generated. In step 200, a new public/private key pair is created for the registered user. Next, at step 202, a temporary password is generated for the user. The key chain database is then searched for every instance of the registered user's ID in steps 204-212. For each record found, there will be a corresponding secret key stored by the virtual registered user. This secret key is decrypted using the virtual registered user's private key at step 208. In step 210, the secret key is then encrypted using the new public key for the user. Finally, at step 212, the encrypted secret key is stored in the key chain database in place of the old encrypted secret key for the universal ID and user ID pair.

[0122] Referring now to FIG. 12 and as discussed above, in a preferred embodiment there may be a plurality of information exchange systems 300 and 302, and affiliate systems 304 connected to a network 306, such as the Internet. A registered user 308 may connect to any of the systems 300-304 to access data stored in one of the storage systems 300a-304a. To retrieve data, the registered user 306 enters a query for profile information and each data element is located using its respective universal ID. Each universal ID may be used to determine the location of its associated data element, including the storage systems 300a-304a on which the data element resides, and the database to search within that storage location for the record in the database that includes that data element.

[0123] Preferably, when a universal ID is entered by the registered user 306, or utilized by an application, the universal ID is processed through a naming service 300b-304b that converts the universal key into a network address and database name. As known in the art, naming services, such as Internet domain name services, include software that converts a name, such as the universal ID, into a physical address on a network. By identifying every data element through a universal ID, and processing the universal ID through a naming service 300b-304b located on each system 300-304, a distributed information exchange system is achieved, with all of the functionality of the information exchange system described herein.

[0124] In a preferred embodiment, when a data element is accessed from a remote location, all decryption of the data element is performed locally—i.e., its secret key is decrypted, and the decrypted secret key is used to decrypt the data element, on the same information exchange system where the data element was located. The decrypted data is transferred across the Internet 304 using the Internet's secure socket layer for data security during transfer of the data.

[0125] As discussed above, an affiliate system may include a software firewall that allows the affiliate, on a field-by-field, person-by-person basis, to prevent a certain subset of information from being accessed through the Internet. A preferred embodiment of the software firewall is illustrated in FIG. 13. An affiliate system 350, is connected to the Internet 354 through a physical firewall 352. As known in the art, a firewall is a combination of hardware technologies such as one or more routers, that are used to give users in a private computer network or system, such as affiliate system 350, secure access to the Internet while protecting the internal network from unsolicited users. The affiliate system 350 includes data storage 356a-c which includes user profile information. A local registered user 360 and an external registered user 362 may access the profile data stored in data storage 356, data stored on information exchange system 358, or data stored on any other information exchange system or affiliate that is connected to the Internet 354.

[0126] In many circumstances, the affiliate system 350 will include a subset of data 356a that may be shared publicly across the Internet 354 (e.g., business contact information), and another subset of data 356b that the affiliate desires to maintain private (e.g., employee salaries, billing information). However, under the data access system described herein, each user may grant access to any other user on a field-by-field, person-by-person basis. In the preferred embodiment, a software firewall is implemented on the affiliate system 350 to prevent certain data fields from being accessed from the Internet 354. The software firewall includes a database 356c which includes a table 358 of fields and related public or private access information. Fields that are marked “public” may be accessed by users, such as registered user 362, through the Internet 354 and physical firewall 352. Fields that are marked “private” may only be accessed from inside the affiliate system's intranet or other local network.

[0127] A preferred embodiment of the process of retrieving stored information from the affiliate system 350 through its software firewall is illustrated in the flow diagram of FIG. 14. In step 370, affiliate system 350 receives a request for access to a data element of stored profile information. The unique universal ID of the requested data element and the requesting party's user ID are searched for in the key chain database in step 372. If no matching records are found, then access cannot be granted to the requesting party (steps 374, 376). If a matching record is found in the key chain database, then a determination is made in step 378 whether the requested data element belongs to a data field that has been designated public or private. A query is run for the data field in the table 358, and if the field is deemed private, the network location of the requestor is determined in step 380. If the requesting user is located outside the physical firewall 352 then the requesting user is denied access to the data element. In the preferred embodiment, the affiliate system 350 denies access to a data element by preventing the decryption of the requesting user's secret key. Because the requesting user's private key is securely stored in the key management system, by denying access to the private key, the affiliate system 350 effectively denies access to the requested data element. If the requested data element is public, or the requester is located within the physical firewall, the encrypted secret key associated with the data element and the requestor is decrypted using the requestor's private key in step 382. In step 384, the decrypted secret key is used to decrypt the requested data element, which is then provided to the requester.

[0128] In accordance with a preferred embodiment, the registered user may dynamically add arbitrary data fields to user profile information. A database structure for storing profile information in such a manner is illustrated in FIGS. 15a-b. A table 390 includes a universal ID field 400 for storing a location identifier of each record in the table, a user ID field 402 for storing the user identification of the registered user associated with the data record, a “field name” field 404 for storing the names of user profile fields, and a field type field 406 for storing the a data type associated with the field name.

[0129] In the preferred embodiment, a new record is added to the table 390 for each new data element associated with the registered user. The table may include pre-defined data fields, such as first_name and last_name, or arbitrary fields (e.g., favorite beer) dynamically created by the registered user. To define a new field, a new field name is created and a field type describing the stored information (e.g., numeric, character, date) is determined by the registered user. Next a new record is added to the table 390 including this new information. Preferably, there is a separate table 392 for each field type, which is used to store the data content for each field. The structure of these tables 390 and 392 is transparent to the registered user, who may be presented with the data from the information exchange system as single record, such as illustrated in FIG. 15b.

[0130] A preferred embodiment of the present invention will now be described with reference to a ZKEY system. The ZKEY system is comprised of five software components: (1) the information entry and editing sub-system; (2) the information views sub-system; (3) the information view requests sub-system; (4) the sub-system for changing the ZKEY; and (5) a subsystem for changing the site password. It should be apparent that other software components can be added to the ZKEY system without significant modification to the system design.

[0131] With reference to FIG. 16, a block diagram illustrating a system architecture which can be used with the ZKEY system is shown. A ZKEY server 500 includes a central processing unit 502 for running a server application 504, processing network transactions and issuing structured query language (SQL) instructions to a relational database management system (RDBMS) 506. RDBMS 506 is used to store records containing information about one or more entities.

[0132] Server 500 is connected to a network 508, such as the Internet, an intranet, local area network, wide area network or the like. An Internet client 510, a wireless application protocol phone (“WAP phone”) 512, a kiosk unit 514, and a plurality of other network devices may be connected to network 508. A vendor 516, such as a retail establishment, product delivery service, distributor, food delivery service, or the like may further be connected to network 508. Alternatively, vendor 516 may be directly connected to server 500 for direct access to server 500. For example direct access may be facilitated either by modem through a telephone network, or by a high-speed digital T1, DSL or Integrated Services Digital Network (ISDN) connection.

[0133] A voice response system (VAS) 520 may be connected between network 508 and server 500 to provide the network 508 and server 500 with voice response capabilities. One skilled in the art would recognize that VAS 520 may comprise a tone detection/translation device, analog-to-digital sampler, tone recognition component, and other components which are typical of voice response systems. Signals from access systems which require voice or tone translation for communicating with server 500 are diverted through VAS 520 for translation. VAS 520 may also be connected to a telephone network 522. A telephone 524 may be connected to the telephone network 522 and can be used to access server 500 through the VAS 520.

[0134] Kiosk 514 may be connected to VAS 520 if the kiosk 514 has voice recognition or a tone keypad. Alternatively, kiosk unit 514 may also be directly connected to server 500 if not through network 508 and no voice or tone translation is needed.

[0135] With reference to FIG. 17, a spoke diagram is presented illustrating a preferred database schema of the user information and authorization tables. It would be apparent to one of ordinary skill that other schemas could be used. Each of the fields in the database are keyed on a field having a prefix “SDN.” The tables within this database schema are comprised of the following:

• • [0136] ACTIVE SESSIONS: contains user authorizations, keeps track of who is logged into a web site, and maintains global variables;
  • [0137] AUTH_USER: verifies the users' identity using cookie technology or other electronic data transfer protocols;
  • [0138] Z_MAIN: contains the main user information registration data, and assigns an SDN internal key number to link all other relational data tables;
  • [0139] SDN_SEARCHABLES: stores searchable information for easy retrieval;
  • [0140] FIELD_TYPES: keeps track of descriptions of field values, for example, text, date, number, etc. allowed in the underlying database management system, which in this embodiment may be an “ORACLE” based database;
  • [0141] PREDEFINED_FIELDS: stores personal information fields defined for information input, for example, home phone, work phone, birthday, and the like;
  • [0142] INPUT_FIELD_INFO: keeps track of what field is displayed on what web page, and in what order the field appears;
  • [0143] DISPLAY_FIELDS: determines the ordering of fields within any profile information view;
  • [0144] PHOTO: enables a user to upload a photo image file directly into a database using Binary Large Object (BLOB) technology for the “ORACLE” based database;
  • [0145] REQUESTS: manages personal information requests and access grants;
  • [0146] Z_NOTES: stores personal notes describing another ZMEMBER within a contact list;
  • [0147] Z_WEBSITES: lists the users' favorite websites;
  • [0148] Z_ADDBOOK: the main address book table that lists other ZMEMBERS in an existing ZMEMBERS' address books;
  • [0149] Z_ADDGROUPS: contains customized user group descriptions;
  • [0150] Z_ADDGROUPS_USERS: contains the ZMEMBERS belonging to specific address book groups;
  • [0151] PREDEFINED_VIEWS: may specify predefined views;
  • [0152] SDN_FIELD_VALUES: stores and maintains all user personal information;
  • [0153] SDN_VIEW_FIELDS: keeps track of specific fields belonging to specific profile information views;
  • [0154] SDN_VIEW_SECURITY: the main table for information view access and keeps track of ZMEMBER access to particular profile information views;
  • [0155] SDN_VIEWS: the main table for customized profile information view data;
  • [0156] VALUE SET DEFINITIONS: contains a set of choices for a particular field, for example the field “State” would have 50 pre-set choices allowed, so this table keeps track of the actual data inside the value sets;
  • [0157] VALUE_SETS: a description of all value (validation) sets; and
  • [0158] INPUT_PAGE INFO: contains default information for input page setup and order information.

[0159] With reference to FIG. 18, a preferred database schema for a calendar module is shown. As would be apparent to one of ordinary skill in that art, other schemas could be used. Each of the database tables, are keyed on the SDN field described above.

[0160] The tables within the database schema are comprised of the following:

• • [0161] Z_CAL: contains the main calendar event setup and information on an event;
  • [0162] Z_CAL_ATTENDEES: contains users attending an event and their attendance status (either accepted or rejected);
  • [0163] Z_CAL_LOCATIONS: contains locations of events for future use by member;
  • [0164] Z_CAL_RIGHTS: stores and maintains access control for an individual's calendar;
  • [0165] VAL_HOLIDAY_SETS: contains descriptions of various holiday sets (United States, Chinese, Jewish, etc.);
  • [0166] VAL_HOLIDAYS: contains dates and descriptions of actual holidays to add to the calendar;
  • [0167] VAL_APPT_TYPES: defines the type of the appointment a person can set (e.g., meals, birthday, conference call, etc.);
  • [0168] VAL_TIMEZONES: sets the calendar to the user's default time zone; and
  • [0169] VAL_CAL_ATT_STATUS: contains attendee's acceptance or rejection of an invitation to an event.

[0170] With reference to FIG. 19, a preferred database schema for the virtually infinite storage module is shown. Again, one of ordinary skill would recognize that other schemas could be used. Each of the database tables are keyed on the SDN field. The tables within this database schema are comprised of the following:

• • [0171] IMP_PREF: sets e-mail preferences;
  • [0172] IMP_LOG: logs e-mail activity; and
  • [0173] ZDRIVE_FILESHARE: maintains access control of files on the ZDRIVE.

[0174] With reference to FIG. 20, a preferred database schema for the chat module is shown. One of ordinary skill would recognize that other schemas could be used. Each of the database tables are keyed on the SDN field. The tables within this database schema are comprised of the following:

• • [0175] ZCHAT_GUESTS: contains and maintains chat room guest lists and member access information;
  • [0176] ZCHAT_MESSAGES: contains all messages posted in chat rooms; and
  • [0177] ZCHAT_SESSIONS: contains and maintains a list of which ZMEMBERS are currently in a particular chat area also known as a ZROOM.

[0178] With reference to FIG. 21, a generic block diagram illustrating some of the modular components of an embodiment of the present invention is shown. This diagram is not meant to be an exhaustive description of a preferred embodiment, which will be detailed below. An initial selection screen 550 inviting members to provide information is an initially displayed component of the system. From this initial selection screen 550, a member can select among various modules, including a home screen module 552; an information exchange system 554; a contacts/address book 558, which may be called ZADDRESS; a calendar 560, which may be called ZCALENDAR; an email system 562; a secure-access storage system 564, which may be called the ZDRIVE; a chat room 566, which may be called ZROOM or ZCHAT; a search sub-system 568, which may be called ZSEARCH; and the system logout module 570. Many of these modules allow direct access from one to the other without returning to the initial selection screen.

[0179] With reference to FIG. 22, a preferred login sequence flow diagram for an embodiment of the present system is shown. A user who enters the site for the first time is presented with a splash screen (step 572) that provides an information about the system features. The system gives users an opportunity to identify themselves as previously registered members (step 574). If the user is an existing member, then the system proceeds directly to a user home page (step 586). Otherwise, from the splash screen, the user can either request a descriptive tour of the system (step 576), and then receive a tour (step 577), or proceed directly to a registration page (step 578). After entering appropriate registration information on the registration page (step 578), the user may optionally have a legal information page presented to them (step 580). The system checks to see if the user agrees with the terms and conditions presented on the legal information page (step 582). If so agreed, then the user is permitted to proceed to a user home page (step 586). Otherwise, the user is presented with a disagreement page (step 584). After the disagreement screen is shown, processing moves to the splash screen display and prevents access to the system (step 588).

[0180] With reference to FIG. 23, a block diagram of a preferred registration page sequence 578 is shown in an Internet browser screen 500. The user may view relevant descriptive information on the registration page and may enter its first name in field 522, their last name in field 524, and their e-mail address in field 526. Users also enter a universal identification code, which may be called a ZKEY, in field 528. This code will be used as the universal identification code to uniquely identify the new member. The user is asked to choose a password in field 530 that will be requested whenever the user accesses their information on the system, whether by Internet client 510 (FIG. 16), WAP phone 512, kiosk unit 514, telephone 524, or other systems which are used to access server 500 by a member. The password is confirmed in field 532. In field 534, the user is asked which time zone they are in. In a selection list field 536, the user is asked how the user found out about the system. By actuation of selection icon or button 538, the information entered thus far is submitted to RDBMS 506. In other embodiments of the invention, additional information may be gathered on this registration page.

[0181] FIG. 24 shows one form of a web-based embodiment of the initial selection screen 700, also called the home area. The content of the home area can be customized by the user through a drag-and-drop interface. Information related to a user's stored address book 720 and calendar 722 can be provided. Also, in a preferred embodiment, among other things, today's weather 724, horoscopes 726, web search capability 728 and stock information 740 can be provided. Hypertext markup language (HTML) tabs can be selected to create or edit the member's profile, edit a contact/address personal database, or to set up profile information views explained below. Context sensitive advertising appears throughout the screens as the user navigates through the system, such as the screen region shown at location 702. Also, a universal selection menu, generally indicated at 704, is used to navigate through various features of the system described below. Quick access to the information view exchange is provided through icon 706, to address book through an Address Book Icon 708. Similarly, the user has quick access to the calendar through the Calendar Icon 710 and to an e-mail and chat facility through the E-mail Icon 712 and ZROOM Icon 719 respectively. Additionally, access to the file storage facility is provided through the ZDRIVE Icon 716 and to the search facility (e.g., ZSEARCH), described below, through the Search Icon 718.

[0182] With reference to FIG. 25, a block diagram representing a detailed sub-module overview of a preferred embodiment of the information exchange system 804 is shown. The information exchange system is comprised of five sections: (1) an information entry and editing sub-system 806; (2) an information views sub-system 808; (3) an information view requests sub-system 810; (4) sub-system 812 for changing ZKEY; and (5) a sub-system for changing the site password 814. The information entry and editing sub-system 806 in turn allows a user to enter or edit profile information, including one or more of the following: primary information 816, phone numbers 818, addresses 820, home information 822, work information 824, gift preferences 826, schools attended 830, hobbies 832, favorite web sites 834, and other information that is not shown. The information views sub-system 808 allows a user to create 836 and edit 838 information views. The creation of an information view 836 allows a user to enter a profile information view name and associated personal information number (PIN) 840; selecting the data fields that will be displayed in the view 842; assigning access privileges to this view to other members or contacts 844, and reviewing and saving information views 846. The PIN relating to item 840 is not required in the preferred embodiment. The editing of an information view 838 allows a user to, among other things, choose profile information fields and assign or reassign access privileges to other members or contacts 848, on a field-by-field, person-by-person basis. The information-view-requests-sub-system 810 manages requests to access a profile information view including: accepting or denying information requested of the user by others 850; and accepting or denying information requested by the user of other members 852. The information exchange system 804 also allows the user to change the ZKEY 812 and the site password 814.

[0183] With reference to FIG. 26, the information exchange system screen 900 is shown with a choice of available information fields 908 displayed. By actuating a link 930 on this page, one of a plurality of types of information which can be entered is shown. The member may select among the plurality of information fields or types including: primary information 910, phone numbers 912, addresses 914, home information 816, work information 818, gift preferences 820, schools attended 822, cellular phone number 824, favorite web sites 826, hobbies 828, and the like. This information may be entered or edited for storage in RDBMS 506. This allows the user to select a specific field to view or modify. By activating a link 932, the user can provide access to this information field to others. Each of the information fields 908 provide access to field information that can be created, edited and stored by the user. Additionally, this screen allows the user to create/edit a custom information profile view 934, which can contain any of the information located within the profile information fields. This custom profile can be viewed by other members and non-members who are provided access.

[0184] With reference to FIG. 27, one example of entering information into the system is provided after choosing the selection 910 from FIG. 26. In order to enter/edit profile information 806 of FIG. 25, a primary information page will appear on browser 900. The user is prompted to enter a full name (e.g. first, middle, last, and nickname 950) and address information 952, including e-mail location information 954 (e.g., work, home or other e-mail), for updating of the RDBMS 506. The HTML page may be larger than the viewing area of the browser 900 because there are more fields in which text can be entered than those which could currently be displayed. The information can be saved 956 or canceled 958.

[0185] Moreover, an HTML page appears after selection of the “Phone Numbers” 912 information option in FIG. 26. The member is given the option to enter a plurality of different personal and business phone numbers. After the fields have been edited, a Save Icon may be actuated to store the input phone numbers into RDBMS 506.

[0186] Additionally, an HTML page appears after selection of the “Addresses” 914 information option in FIG. 26. In the screen of the browser 900, the user may enter address information for home, work, international travel and the like. The Slider bar of the screen may be lowered in order to enter more address information not shown on the screen, such as school, alternate, and travel addresses. A Save Icon may then be actuated in order to store the entered address information in RDBMS 506.

[0187] With reference to FIG. 26, other HTML pages for entry and editing of information may be displayed by selecting link 930 next to each field or type of information. With reference to FIG. 28, an HTML page is shown which is presented after selection of the “Info Requests” selection 910 of FIG. 26. The various profile information views are views which the member can set up for different contacts that the member allows selective access for the member's information. As explained below, the member may choose different fields for different profile information views which different groups of people may view. Members implement the different views as explained below. The info-requests-HTML page 970 of FIG. 28 alerts the member to various information views which other members have requested access to 972, or information views for other members which the current member has requested access to 974. As will be understood by one of ordinary skill in that, any of the pages of this invention described herein may be programmed in HTML, DHTML, or any other method for creating a page of information.

[0188] With reference to FIG. 29, a block diagram representing a detailed module overview of the contacts/address book module 558 shown in FIG. 21. The starting point 1402 initiates the contact list manager, which is an HTML page in the web site embodiment. From the contacts/address book page, the user may access a list view page 1404, a page for adding contacts 1406, a group manager page 1408, or create a meeting page 410.

[0189] In one aspect of the invention, the address book comprises a list view 1404 selection. Under list view 1404, a list of the member's contacts is provided 1404a. Additionally, contact information may be viewed by “Group” in one aspect of the invention 1404b, as contacts may be sorted into different contact groups. Also, contacts may be emailed 1404c. Finally, detailed records 1404d may be shown, including such things as personal notes 1404e and more information views 1404f. Also, the ability to remove a contact is provided 1404g.

[0190] By selecting “Add Contact” 1406 from the address book the user may add contact information. The system allows the user to search for members 1406a. If the new contact is a member of the system and assigned a member ID number or ZKEY, the member may enter the new contact's member ID number for a selection. If the member does not have the contact's member ID, the server application allows a search for the member by entering text into name fields in order to search by name, or by selecting a field for searching in a field, such as a Boolean field. After locating the member, the contact information may be viewed or added to 1406b.

[0191] Alternatively, if the contact is not a member of the system, the member may add a non-member contact 1406c. For example, an HTML page for adding a non-member contact will appear on a display screen 1406d. After entry is completed for the initial page, the member may actuate a button to proceed to enter further information regarding the non-member contact. In the preferred embodiment of the invention, the system creates an e-mail message to be sent to the non-member, which introduces the non-member contact to the system 1406e. The member is given the option of editing the message before it is sent. After sending the e-mail, the member has a temporary record added to the address book 1406f.

[0192] In one aspect of the invention, a group manager page 1408 appears after the member chooses the “GROUP MANAGER” selection on the menu. It will be understood that there are other ways of accessing the group manager page. In this page, the member may create 1408a, edit 1408b or delete groups 1408c for including contacts by actuating page buttons. A selection list appears listing contacts that the member has added to the contact list. A selection list of contacts already in the group is shown. In order to add a contact to the group, the member selects the contact from a selection list. Similarly, to remove a contact from the group, the member selects a contact from the selection list, and then selects a removal icon. After adding and removing contacts from the group, the member may direct the server application to store the group as edited to the RDBMS. Finally, a meeting for members or contacts can be created 1410.

[0193] With reference to FIG. 30, an HTML page 1000 for adding contact information is shown. The member arrives at this page after selecting “Add Contact” 1406 (FIG. 29). If the contact is a member of the system of the present invention with an ID number, the member may enter the contacts ID number in field 1102. If the member does not have the contact's ID, then the member presses button 1104. As seen in FIG. 31, server application 504 in FIG. 16 is capable of searching for the member by entering text into fields 1106 and 1108 in order to search by name, or by a selecting a field for searching in field 1110 as indicated by a field selection list 1112.

[0194] Alternatively, if the contact is not a member of the system, the member may select an HTML tag 1112 in FIG. 30 for adding a non-member contact. The system creates an e-mail message to be sent to the non-member contact which introduces the non-member contact to the system. The member is given the option of editing the message before the message is sent, and is also given the option for entering notes regarding the new contact. After the information is input, the system may be updated, and return the member to the list view HTML page. Additionally, an HTML page is displayed which appears after the user of the system chooses an existing member from the HTML of the list view. The user is given the option to add notes regarding the existing member.

[0195] With reference to FIG. 32, if actuation of either of the create 1408a or edit/view groups 1408b is chosen from FIG. 29, then a group-manager-edit-HTML-page is displayed on the screen of the browser 1700. A selection list 1702 appears listing contacts which the member has added to the contact list. A selection list of contacts already in the group is shown as indicated at 1704. In order to add a contact to the group 1712, the member selects the contact from selection list 1702, and then actuates an Add icon 1706. Similarly, to remove a contact from the group, the member selects a contact from selection list 1704, and then actuates a Remove icon 1708. After adding and removing contacts from the group, the member may actuate a Save icon 1710 to direct server application 104 to store the group as edited to RDBMS 506 or a cancel icon 1712 to not store the information.

[0196] With reference to FIG. 33, after selection of item 808 in FIG. 26, the currently available custom views are displayed in a scrolling list using methods known in the art. The user may select one of the current views 1800 and then edit 1802, view 1802, or delete 1804 the selected view. Users may also create new information views from this page 1806. The user can select fields that will be available in this particular profile information view. These fields include, among others, all fields or information within primary information, phone numbers, addresses, home information, work information, gift preferences, personal information, schools attended, hobbies, favorite web sites and other fields such as those described in conjunction with FIG. 25. Custom views are groups of profile information that the user creates. For example, after selection of item 1806, the user could create a customs view called “Business Card” consisting of the user's work address and pager numbers. This custom information view can then be shared with other members and non-members of the system, on a field-by-field, person-by-person basis. Through this aspect of the invention, the user can create as many custom information views as desired and grant access to one or more members and non-members.

[0197] With reference to FIG. 34, a block diagram describing a calendar system structure is shown. The calendar comprises several information view options including a day view, a week view, a month view, a group calendar view, and views of the calendars of other system members. The universal identification code can be used to access any of the calendar information views that a user decides to make public. Selective access can also be granted through an instant access code. In the case of other members, the other members may be selected using their universal identification codes or ZKEYS. Instant access codes are transmitted to named non-members by e-mail or other known communication methods. The system of the present invention may incorporate features from other calendar systems such as Microsoft Outlook™ and CorelCENTRAL™.

[0198] The calendar system 560 is comprised of a day view 2002 where users can see the schedule information for a given day; a week view 2004 where users can see schedule information for a given week; a month view 2006 where users can see schedule information for an entire month; and a group calendar view 2008 where combined schedule information for all of the members of a group are displayed. The user can also choose to share calendar information with other users 2010 on a field-by-field, person-by-person basis. Within the calendar day/week/month/group calendar view, users can create or edit a task 2012, create or edit an event 2014, or simply edit an existing event 2016. When creating or editing an event 2014 or editing an event 2016, the user may also invite members or non-members to the event 2018.

[0199] With reference to FIG. 35, a block diagram is shown describing the electronic mail system 562 of FIG. 21. The e-mail system is comprised of facilities for creating and editing 2100, spell checking 2102 and sending email 2104, an in-box for receiving 2106, reading 2108, forwarding 2110, copying or moving 2112, deleting 2114, replying to 2116, and otherwise managing incoming e-mail messages; a directory manager to create, manage, and delete e-mail directories and subfolders 2118; an address book 2120; and a facility to set a default personal signature 2122. Here, the universal identification code can be used to efficiently locate users in the address book. Thus, by selecting a user from the address book based on their universal identification code, the system will ensure that their latest or preferred e-mail address is used. The system of the present invention may incorporate features from systems such as those in AOL NetMail™ or Microsoft Outlook™.

[0200] With reference to FIG. 36, a block diagram of a virtually infinite storage system, which may be called a ZDRIVE 564, is described. This system allows a user to upload files to the storage system 2202; create, add, or delete a folder 2204; copy 2212, move 2214, delete 2216, or otherwise manage files or folders; share a file with another member 2218; download files from the system 2206; view files that have been shared by other members 2208; and rename files 2210. The universal identification code may be granted to other members to selectively allow these members to access, read, copy, modify or delete data or files stored on the virtually infinite storage system, 2200. Non-members may be sent an instant access code, which, by itself or in conjunction with the universal identification code, allows access to the stored data.

[0201] With reference to FIG. 37, a block diagram of a chat system 566 is described. The chat system is comprised of modules implementing a method for creating access lists to a plurality of chat sessions 2400; a method for posting messages to a chat group 2402; a method for moving among chat groups or Z-ROOMS 2404; a method to view the chat participants 2410; and housekeeping methods such as methods to clear the screen 2406 or record a session 2408. The universal identification code can be used to identify member chat participants and to add or remove members from restricted access chat groups. Furthermore, non-members may be invited to restricted access chat groups through an instant access code. By using the universal identification code in combination with the instant access code, non-member users can quickly locate relevant chat groups and can become participants.

[0202] With reference to FIG. 38, a block diagram is shown describing a search system for locating a member based on their universal identification code or ZKEY. First, a user requests to search for another member using the ZKEY (step 2500). Alternatively, a search can be performed based on profile information (step 2502). If selected, this search can be performed by the system on the other member's first or last name or by other profile information, such as the other member's home e-mail, work e-mail, or home phone, 2506. If the other member is found through either 2500 or 2502, the system display the detailed records of the member 2510. If not found, the system may perform another search, 2502. Additionally, the system provides for a search of the Internet 2506 to assist in locating members and non-members.

[0203] With reference to FIG. 39, a flow diagram showing a method for creating and designating access to an information view is shown. The user begins by accessing the information view creation module (step 4002). The user then selects a new view name (step 4004), and elects fields to included in the view (step 4006). The system then generates a view ID (step 4008), and stores the view ID in the RDBMS 506 (step 4010). In a preferred embodiment, the user is given the option to provide an instant access code or PIN which will allow both members and non-members instant access to the view being created, step 4012. If an instant access code is not created, the user is only given the option to select members of the system for granting access rights to the view, step 4014. After selection of the members, the members' identification codes, the associated user's member identification code, and a unique view ID are stored in the SDN_VIEW_SECURITY table RDBMS 506 in relational key fashion for providing an easy lookup facility for granting access to the newly created view. A message is then sent to those members who were added to the viewer list, letting them know that they now have access to the new view (step 4020). This is an option given to the user granted access. Additionally, for all selected members, the system offers to add the user to each member's contact list (step 4022).

[0204] If an instant access code is created by the user in step 4012, the system performs the processing according to the flow diagram shown in FIG. 43. With reference to FIG. 40, a flow diagram is shown illustrating a preferred embodiment of a method for providing an instant access code. The instant access code or PIN provides an alternative method for granting non-members of the system access to a view. As described above, the user may type in an instant access code during the view creation process, which is a code which is sent to the designated non-members to be typed in when prompted during access of the view.

[0205] The user is allowed to identify non-members to be granted instant access by selecting them from the user's contact list (step 4102). The user may then enter the instant access code (step 4104). The system stores the user identification code, instant access code and view ID in RDBMS 506. The data may also be stored in the SDN_VIEW_SECURITY table, or alternatively, be stored in a separate table for storing instant access codes. Next, the system transmits the access code to the selected non-members (step 4108). The system offers to have the user appear on the individual member's contact list if the user does not already appear (step 4110). After concluding this routine disclosed in FIG. 40, the system returns to step 4014 in FIG. 39.

[0206] With reference to FIG. 41, a flow diagram showing a method for displaying a member's view created by the method described in FIGS. 39-40 is shown. The user may initially view his/her contact list (step 4202). The user may select a member from the contact list who has created at least one view (step 4204). A list of views for the selected member is displayed (step 4206). The user may select a view from the list of the selected member's views (step 4208). The user then requests access to the view (step 4214). The system checks to see if the user has been granted access to the selected view (step 4210). If so, the information from the fields in the selected view is displayed on screen (step 4212). If the user has not been granted access, then the system performs step 4216 to determine whether the user desires to request access to the view. If so, access is requested (step 4218). If the user does not desire access, then the system will return to displaying the list of the selected member's views (step 4206).

[0207] With reference to FIG. 42, a flow diagram is shown illustrating a method for selecting and displaying a view using an instant access code, which is a view provided by a member as described with respect to FIG. 39-40. The process begins when the user, who may either be a member or a non-member of the system, receives a message stating that access to a member's view has been granted, along with the instant access code for accessing the view (step 4302). A decision branch (step 4304) determines whether the user is a member or a non-member. If the user is a non-member, then the user may be required to go through the new member sign-up process as described above with respect to FIGS. 22-23 (step 4306). Alternatively, non-member view selection lists may be provided by the system. As described with respect to FIG. 41, the user then chooses a view for display from the contact list (step 4308). The user is prompted for the instant access code to the view (step 4310). If the user does not have the instant access code, the user must obtain an instant access code (step 4314). The user is then allowed to enter the instant access code (step 4316). The system processes and compares the entered code to the designated instant access code for the view in RDBMS 506 (step 4318). The system checks for a match (step 4320). If the entered number does not match, processing returns to step 4308. Otherwise, the field information in the selected view is displayed (step 4322). For member users, after access is granted to a view by instant access code, the system records the user's user identification code, along with the member identification code and view ID for the view, so that the next time the user accesses the view the user would not be prompted again for the instant access code (step 4324).

[0208] With reference to FIG. 43, a flow diagram is illustrated showing a method for creating and designating access to files on the ZDRIVE as described with respect to FIG. 36. The user begins by accessing the information of the ZDRIVE module (step 4402). The user then selects a new file from the user's client computer to upload (step 4404). The user then uploads the file, using the file transfer protocol (FTP) or other standard network information transfer protocol (step 4406). The system then generates a file ID (step 4408), and stores the file ID in the RDBMS 506 (step 4410). The user is given the option to input an instant access code or PIN which will allow both members and non-members instant access to the uploaded file (step 4412). If an instant access code is not created, the user is only given the option to select members of the system for granting access rights to the file (step 4414). After selection of the members, the members' identification codes, the associated user's member identification code, and a unique file ID are stored in the SDN_VIEW_SECURITY table in RDBMS 506 in relational key fashion for providing an easy lookup facility for granting access to the newly uploaded file. The system offers the user to send a message to those members who were added to the access list, notifying them that they now have access to the newly uploaded file (step 4420). Additionally, the system offers to add the user to each of the selected member's contact lists for selection of views (step 4422). If an instant access code is created by the user in step 4412, the system performs the method shown in FIG. 44.

[0209] With reference to FIG. 44, a flow diagram is shown illustrating a preferred method for providing an instant access code to members. The instant access code or PIN provides an alternative method for granting members access to a file, while allowing non-members of the system to also have access to a file. The user may input an instant access code during the file upload process in similar fashion with respect to views as described above, which is a code that is sent to the designated members and non-members to be input when prompted during access of the file.

[0210] The user is allowed to identify members and non-members to be granted instant access by selecting them from the user's contact list (step 4502). Next, as described above, the user may enter the instant access code (step 4504). The system stores the user identification code, instant access code and file ID in RDBMS 506 in step 4506. This data may also be stored in the SDN_VIEW_SECURITY table, or alternatively, be stored in a separate table for storing instant access codes. Next, the system transmits the access code to the selected members and non-members (step 4508). For the members, the user will now appear on the individual member's contact list if the user does not already appear (step 4510). In other embodiments of the invention, note that a member may share files without providing access through an identification code or instant access code. The files may simply be available on the ZDRIVE.

[0211] With reference to FIG. 45, a flow diagram shows a method for providing access to a file uploaded by the method described in FIG. 43. The user may initially view their contact list (step 4602). The user may then select a member from the contact list who has uploaded at least one file (step 4604). A list of files uploaded by the selected member to which the user has been granted access is displayed (step 4406). The user may select a file from the list of the selected member's views (step 4608), and is provided the option to have the file presented or to download the file to the local client (step 4612).

[0212] With reference to FIG. 46, a flow diagram is shown illustrating a method for selecting and presenting or downloading a file using an instant access code using a file by a member as described with respect to FIG. 44. The process begins when the user, who may either be a member of the system or a non-member, receives a message stating that access to a member's file has been granted, along with the instant access code for accessing the file or, with respect to members, that access has been granted through a ZKEY (step 4702). A decision branch (step 4704) determines whether the user is a member or a non-member. If the user is a non-member, then the user may be required to go through the new member sign-up process (step 4706). Alternatively, non-member view selection lists may be provided by the system. The user then chooses a file through the available list (step 4708). If the user is a member and has been granted access through the user's universal identification code, then the downloaded file is displayed (step 4709). Otherwise, the user is prompted for the instant access code to the file if access has not already been granted through the universal identification code or ZKEY (step 4710). The user is then allowed to enter the instant access code (step 4712). The system searches for and compares the entered code to the designated instant access code for the file in RDBMS 506 (step 4714). The system checks for a match (step 4716). If the entered code does not match, processing returns to step 4708. Otherwise, the access is granted to the file for display or download (step 4718). For member user's, after access is granted to a file by the instant access code, the system records the user's user identification code, along with the file member's identification code and file ID for the file so that the next time the user accesses the file, the user would not be prompted again for the instant access code (step 4720).

[0213] With reference to FIG. 47, a flow diagram shows a preferred method for creating and designating access to an online chat event. The user begins by accessing the chat module (step 4802). The user then selects a new chat event name (step 4804) and selects a time and date for the chat event (step 4806). The system then generates a chat event ID (step 4808) and stores the chat ID in the RDBMS 506 (step 4810). The user is given the option to provide an instant access code or PIN which will allow both members and non-members instant access to the chat event being defined (step 4812). If an instant access code is not created, the user is only given the option to select members of the system for inviting to the chat event (step 4814). After selection of the members, the members' identification codes, the associated user's member identification code, and a unique chat ID are stored in the SDN_VIEW_SECURITY table RDBMS 506 in relational key fashion for providing an easy lookup facility for granting access to the scheduled chat event (step 4816). A message is then sent to those members who were added to the invite list, notifying them that they were invited to the chat event (step 4820). The system then offers to add the user to each of the selected member's contact list (step 4822).

[0214] If an instant access code is created by the user in step 4812, the system performs the method shown in FIG. 48. With reference to FIG. 48, a flow diagram is shown illustrating a preferred method for providing an instant access code to members. The instant access code or PIN provides an alternative method for inviting members to a chat event, while allowing non-members of the system to also be invited to the chat event. The user may input an instant access code during the chat event scheduling process, which is a code which is sent to the designated members and non-members to be typed in when prompted during access of the chat event room.

[0215] The user is allowed to identify members and non-members to be granted instant access by selecting them from the user's contact list (step 4902). The user may then input the instant access code (step 4904). The system stores the user identification code, instant access code and chat ID in RDBMS 506. This data may also be stored in the SDN_VIEW_SECURITY table, or alternatively, be stored in a separate table for storing instant access codes. Next, the system transmits the access code to the selected members and non-members (step 4908). For the members, the user will now appear on the individual member's contact list if the user does not already appear (step 4910).

[0216] With reference to FIG. 49, a flow diagram shows a preferred method for accessing a member's chat event created by the method described in FIG. 47-48. The user may initially view a current chat event list (step 5002). The user may select a chat event from the chat event list (step 5004). The system checks to see if the user has been granted access to the selected chat event (step 5010). If the user has not been granted access, then processing returns to step 5004 to re-display the list of the chat events. Otherwise, the user is entered into the chat event (step 5012).

[0217] With reference to FIG. 50, a flow diagram is shown illustrating a method for selecting and entering a chat event using an instant access code provided by a member according to the method described with respect to FIGS. 47-48. The process begins when the user, who may either be a member of the system or a non-member, receives a message stating that access to a member's chat event has been granted, along with the instant access code for entering the chat event (step 5102). A decision branch (step 5104) determines whether the user is a member or a non-member. If the user is a non-member, then the user may be required to go through the new member sign-up process as described above with respect to FIGS. 22-23 (step 5106). Alternatively, non-member view selection lists may be provided by the system. The user then chooses a chat event from a current chat event list (step 5108). The user is prompted for the instant access code to the view if they have not been given access through the universal identification code (step 5110). The user is then allowed to enter the instant access code (step 5112). The system processes and compares the entered code to the designated instant access code to the guest list for the chat event in RDBMS 506 (step 5114). The system checks for a match (step 5118). If the entered number or universal ID does not match, processing returns to step 5108. Otherwise, the user is granted entry to the selected chat event (step 5120). For member users, after access is granted to a chat event by instant access code or identification code, the system records the user's user identification code, along with the member identification code and chat ID for the chat event so that the next time the user accesses the chat event, they would not be prompted again for the instant access code (step 5122).

[0218] With reference to FIG. 51, a flow diagram is shown for selection of advertisement messages for display on screen during navigation of the system of the present invention. Advertisement messages may be selected from RDBMS 506 depending on things such as the date, time, geographic region and key words on the display screen or the profile information of the user. Beginning with step 5202, the system sets a system loop for navigation through each screen. The system reads the date and time, actual and calendar display (step 5204). The system checks for a trigger in RDBMS 506 according to date, time, geographic region, key words, profile information, and any other triggers which may appear in the display of each screen (step 5206). The system checks to see if an advertisement has been triggered (step 5208). If an advertisement is not triggered, a generic advertisement is displayed in ad region 702, for example as shown in FIG. 24 (step 5210). Otherwise, an advertisement indicated by the trigger as being set for display in an advertisement region 702 is displayed (step 5212).

[0219] The information exchange system may be used with unaffiliated, external systems such as external e-mail, online personal calendar and document management systems. The information exchange system provides facilities to unify these information sources, allowing a registered user to access, view and edit the registered user's stored information through a single system—the information exchange system. In a preferred embodiment, a subset of the information stored on unaffiliated, external systems is unified with the information stored by the information exchange system through information snarfing.

[0220] An example of information snarfing is provided in FIG. 52. An information exchange system 6000 is connected to a registered user 6002 through a network 6004 such as the Internet. The information exchange system 6000 includes a data storage system 6006 and an e-mail server application 6008 for providing the registered user 6002 with e-mail services, including an e-mail address and the ability to send and receive e-mail. The registered user 6002 may also have a second e-mail account through an unaffiliated, external e-mail server 6010. The e-mail server 6010 provides the registered user 6002 with an e-mail address, and the ability to send and receive e-mail messages through the e-mail server 6010. In the preferred embodiment, the e-mail server 6010 is a Post Office Protocol 3 server (“POP3 server”). As known in the art, a POP3 server is a standard e-mail server used on the Internet for storing and forwarding incoming e-mail messages; however, other e-mail servers may also be used. The registered user 6002 may access its second e-mail account by logging onto the e-mail server 6010 and downloading its stored messages to the registered user's network device.

[0221] Through the information exchange system 6000, the registered user 6002 may send and receive e-mail from both the e-mail server 6008 and the e-mail server 6010. In a preferred embodiment, the registered user 6002 first grants the information exchange system 6000 access to its e-mail information stored on the e-mail server 6010. Because the e-mail server 6010 is a POP3 server, the information exchange system 6000 may secure access to the registered user's e-mail if the user provides the location of the POP3 server (e.g., internet address) and the registered user's login information (e.g., username and password) for the POP3 server. However, it should be appreciated that the information required to access the registered user's external e-mail information will vary depending on the e-mail server being accessed.

[0222] To migrate the registered user's stored e-mail information from the e-mail server 6010 to the information exchange system 6000, the information exchange system 6000 includes a snarfing application 6012 that causes the information exchange system 6000 to connect to the e-mail server 6010 through its network address, and transmit the registered user's login information to the e-mail server 6010. The snarfing application 6012 next downloads the e-mail information to the information exchange system 6000 and stores the incoming messages in the registered user's inbox through the e-mail server 6008. The registered user 6002 may then access the e-mail information from both e-mail accounts through the e-mail server application 6008. In the preferred embodiment, the snarfing application 6012 periodically connects to the e-mail server 6010 when the registered user 6000 is logged into the information exchange server 6000 to download new e-mail information. It is further contemplated that the e-mail server application 6008 will include facilities allowing the registered user 6002 to alter the information in the “from field” of outgoing e-mail messages, thereby allowing the registered user 6002 to send e-mail messages from the information exchange server 6000 that indicate the e-mail server 6010 as the source of the message.

[0223] An alternate approach to migrating stored data to the information exchange system 6000 involves the snarfing application 6012 emulating the registered user 6002. For example, a registered user 6002 may use a web browser and the hypertext transport protocol (“HTTP”) to access stored information on an external site. The snarfing application 6012 of this embodiment is programmed to access the external storage site, navigate the user interface and download the stored information using HTTP. Any stored information accessible to a user through a web browser may be migrated in this manner, including personal calendar information and stored data files.

[0224] As discussed above, a registered user may provide access to selected data elements by creating views of the user's profile information and providing individuals access to the views. In addition to providing access to selected views of profile information, a registered user of the information exchange system may also “push” selected profile data to other applications and systems. A preferred embodiment of this feature will now be illustrated with reference to FIG. 53. An information exchange system 6100 includes a storage system 6102 storing user profile data and a recommendation engine application 6104. The information exchange system 6100 is connected to at least one registered user 6106 and a plurality of vendors 6108a-c through a network such as the Internet 6110. In operation the registered user 6106 stores profile data in the storage system 6102 and can control the access to the stored data elements on an element-by-element and person-by-person basis. Consequently, the vendors 6108a-c will not have access to the stored profile data unless and until the registered user 6106 provides them access.

[0225] The stored profile data may be generated through applications such as e-mail and personal calendar, may be entered by the registered user 6106 through data entry screens, and may be generated by the information exchange system 6100 (e.g., tracking the registered user's use of the network, including places visited, pages read, and items purchased online). This stored profile data is valuable to vendors the 6108a-c who may wish to direct advertisements or product offers to the people fitting the registered user's profile. These directed advertisements and offers could also benefit the registered user 6106 by providing the registered user 6106 with helpful information in the form of discounts and offers on products and services that the registered user 6106 is likely to use. In addition, the stored profile data may further include standard purchasing information that the registered user 6106 would manually enter in order to complete an online transaction, such as to purchase an item. In a preferred embodiment, this information is automatically provided to selected vendors to make online transaction more efficient to the registered user.

[0226] A preferred embodiment of the preference pushing information flow is illustrated in FIG. 54. The registered user 6106 has data profile information stored in data storage 6102. The registered user 6106 authorizes a subset 6120 of its user profile data to be pushed to one or more of the vendors 6108a-c. This subset 6120 is provided to the recommendation engine 6104. Preferably, because the stored profile data is encrypted, each data element is decrypted, using either the registered user's or a virtual registered user's public/private key pair, before being pushed to the recommendation application 6104. The vendors 6108a-c also provide the recommendation engine with data 6122a-c, such as advertisements, promotions and coupons, and a target audience profile for each advertisement, promotion and coupon. The recommendation engine 6104 compares the user profile information 6120 with the vendor data 6122a-c and, when appropriate, provides the registered user 6106 with the recommended vendor promotion 6122. The recommendation engine may include any software application known in the art that is adapted to recommend a targeted advertisement or promotion to a user having a particular user profile.

[0227] An alternative embodiment is illustrated in FIG. 55. The registered user 6106 authorizes a subset 6120 of its user profile data to be pushed to one or more of the vendors 6108a-b. This subset 6120 is provided to the recommendation engine 6104, which converts the profile data to an information request which is forwarded to selected vendors 6108a-b. The vendors 6108a-b will return requested information 6124a-b in response to the request. For example, if the registered user 6106 was searching for a home loan, the recommendation application 6104 may forward relevant home and financial information to various lenders who may return information on whether they will provide a home loan to the registered user, and on what terms. The recommendation engine 6104 then selects a subset of this returned information based on the user's preferences and provides a recommendation 6126 to the registered user 6106.

[0228] An example of preference pushing is illustrated in FIG. 56. A registered user stores user profile information in a personal calendar 6200. The personal calendar includes an interface portion for listing appointments and events on the current day 6202 and an interface portion for displaying a recommendations 6204 based on user profile information. As shown, the current day includes an entry indicating that it is user's wife's birthday. This generates an event with a recommendation application 6206 which recommends an appropriate gift for the user's wife, along with a recommended vendor for purchasing that gift. Preferably, the recommendation interface 6204 provides the registered user with the option of purchasing the goods through a single click of a screen control button 6208. Because the recommendation engine has access to user profile information such as name, address, telephone number and credit card number, this information may be pushed automatically to the vendor to complete the online order. Alternatively, the registered user may be provided with a form 6210 which is automatically filled in with the user profile information, from both the registered user and the person to whom the gift is purchased (gathered from the receiver's user profile data). The registered user may then alter any of the information before placing an order.

[0229] The information exchange system may be used with any network device (e.g., PDA, WAP phone, personal computer) and may further be used with a plurality of existing software applications, such as CorelCENTRAL™ or Lotus Smartsuite™. However, many network devices do not maintain a continuous connection to the Internet, and many applications do not make use of the Internet's capabilities. Consequently, these devices and applications will produce data that is not in synchronization with the data stored in the information exchange system. For example, if contact information is changed in an address book on a standalone PDA, the stored contact information will differ from the contact information stored on the information exchange system. Likewise, information updated in the information exchange system will not be reflected in the data stored on the standalone PDA.

[0230] To alleviate may of these problems, a preferred embodiment of the present invention includes intelligent synchronization software that executes on a client device. As illustrated in FIG. 57, an information exchange system 6300 includes a data storage system 6302 and a synchronization application 6304 for synchronizing the user profile data stored in the data storage system 6302 with user profile data stored on a network device 6306. The network device 6306 includes an intelligent synchronization application 6308 for controlling the data synchronization from the network device 6306. The network device 6308 is intermittently connected to the information exchange system 6300 through the network 6310. In operation, the intelligent synchronization application 6308 periodically initiates a data synchronization process with the information exchange system 6300 when network activity is detected by the application 6308 on the network device 6306. The intelligent synchronization software 6308 operates in the background and data is transferred between the information exchange server and the network device 6306 during periods of low traffic, making the data synchronization process imperceptible to the registered user.

[0231] Referring to FIG. 58, a preferred information flow for the data synchronization process is illustrated. First, the network device 6306 transmits at least one record stored on the network device 6306 to the information exchange system 6300. Next, based on the received records and the records stored on the information exchange system 6300, the information exchange system 6300 transmits a set of instructions to the network device 6306. The instructions include add a new record, delete a record and update a record. Finally, the network device 6306 transmits a set of mappings for any records that were added in the prior step. The mapping associates a record stored on the network device 6300 with a record stored on the information exchange system 6300.

[0232] FIG. 59 illustrates a preferred embodiment of the steps performed by the synchronization application 6304 to process the records received from the network device 6306. In step 6350, the next record is received from the network device, and a query is run in a mapping database for the received record in step 6352. The mapping database of the preferred embodiment is illustrated in FIG. 60 and includes unique pairs of record identification numbers assigned by the network device and record identification numbers assigned by the information management system. If the record is not located (step 6354) then it is treated as a new record that was added through the network device. If the record does not correspond to a registered user, then a pseudo user is created (step 6358), the new information is stored for the new pseudo user (step 6360) and a new mapping is created in the mapping database between the record and the pseudo user (step 6362). A pseudo user represents user profile information for someone who is not a registered user of the information exchange system. The right to access and edit the user profile information of a pseudo user belongs to the registered user for whom the pseudo user was created.

[0233] Referring back to step 6354, if the record is located in the mapping database, then a determination is made as to whether the record is located in the registered user's database (step 6363). If the record is not found, then instructions are sent to the network device to delete the record (step 6365). If the record is found then a determination is made as whether the operator of the network device has editing rights to the record (step 6364)—i.e., whether the record corresponds to the operator's user profile or a pseudo user created by the operator. If the operator has editing rights, then a determination is made as to whether the date of the record stored in the information exchange system is greater than the last synchronization date (step 6366). If the record has been updated since the last synchronization date, then no update will be performed for the data because the updated data stored on the information exchange system will be considered correct. Otherwise, the record stored on the information exchange system will be updated with the data received from the network device (step 6368). The process is repeated (step 6370) until no more records are received.

[0234] In the preferred embodiment, after the information management system processes the records received from the network device, the synchronization application 6304 performs the steps illustrated in FIG. 61. The synchronization application traverses each record used by the application that has not already been processed. The next record is retrieved (step 6400) and looked up in the mapping database (step 6402). If the record is not located in the mapping database (step 6404) then the record is new and should be added to the network device. In step 6406, a message is sent to the network device instructing the network device to add the record. The synchronization application next receives the mapping from the client (step 6408) and the new record is added to the mapping database (step 6410).

[0235] Referring back to step 6404, if the record is located in the mapping database, then it is determined whether the record is currently on the network device. If not currently on the network device, then the record is deleted from the information exchange system in step 6414. Because a mapping existed, it is assumed that the record existed at one time on both systems; however, because one record is missing, it must have been deleted by the user. If the record does exist on the network device, then if the record date is greater than the last synchronization date (step 6416) an instruction is sent to the device to update the record (step 6418). The process continues until there are no more records (step 6420).

[0236] A preferred embodiment of the steps performed by the network device in processing instructions from the information exchange server is illustrated in FIG. 62. In step 6450, the network device receives the next instruction from the information exchange server, the instruction may include “add,” “delete,” and “update” (step 6452). If an “add” instruction is received, then the network device adds the record that was sent with the instruction (step 6454) and sends a mapping of the newly created record to the record that was sent from the information exchange server to the information exchange server (step 6456). If an “update” instruction is received, then the record in the network device, corresponding to the record sent in the instruction is updated with the new data (step 6458). If a “delete” record is received, then the record in the network device is deleted (step 6460). This process continues until there are no more records (step 6462).

[0237] The intelligent synchronization of the preferred embodiment is operable with any device type, any record type, any transport protocol and any synchronization logic, including the synchronization logic described in FIGS. 58-62. This is accomplished through a synchronization engine as illustrated in FIG. 63, including a server portion 6500 and a client portion 6550. The server portion 6500 includes a server application 6502 which implements threads 6504 for processing synchronization requests from the client portion 6550, synchronization logic 6506 (e.g., the synchronization logic illustrated in FIGS. 58-62), a synchronization database 6508 and a database API to provide an interface between the synchronization database 6508 and the server application 6502. In the preferred embodiment, the server portion 6500 operates on a database server system, such as the information exchange system of the present invention. The synchronization logic 6506 is a plug-in module that can be seamlessly changed to implement different synchronization logic for different applications.

[0238] The client portion 6550 includes a client application 6552 which controls the synchronization of data between the server portion 6500 and the client portion 6550. A transformer plug-in 6554 is written for the specific client device, and functions to read the data records 6556 from the device and output the data in a format that may be manipulated by a packet plug-in 6558. The packet plug-in 6558 converts each record into a data structure that is specific to an application such as an address book or e-mail account operating on the network device. The packet plug-in 6558 outputs the data structures to a synchronization protocol plug-in 6560 which handles the transfer protocol of the data structures between the client portion 6550 and the server portion 6500.

[0239] The synchronization engine described above is extensible. It is not limited to a particular device, synchronization methodology, transport protocol or data type. By modifying any of the four plug-ins, the synchronization engine described above will operate with any client device, any type of data records, any transport protocol and any synchronization logic methodology.

[0240] Having thus described a preferred embodiment of the SYSTEM AND METHOD FOR SELECTIVE INFORMATION EXCHANGE, it should be apparent to those skilled in the art that certain advantages of the within system have been achieved. It should also be appreciated that various modifications, adaptations, and alternative embodiments thereof may be made within the scope and spirit of the present invention. For example, it should be apparent that the inventive concepts described above are applicable to any stored data, including data from personal calendars, contact databases, e-mail systems and document management systems. The scope of the invention is defined by the following claims.