DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0043] FIG. 1 is a functional diagram of one preferred embodiment of the present invention. Message broadcast system 10 , comprises a message data input stage 20 and message data output stage 30 . Included in a preferred embodiment is at least one 12 , and preferably a plurality of message data 12 , 14 , 16 , a central controller 18 and at least one 22 , and preferably a plurality of database systems 22 , 24 , 26 . Central controller 18 receives message data 12 , via a communications interface, and automatically communicates with and controls database 22 to remove and/or disperse information from database 22 that matches information contained in the message data 12 . Preferably, system 10 provides an automated central controller 18 to automatically communicate with and control a plurality of databases 22 , 24 , 26 upon being supplied with message data 12 from a user. Each of these functional components of the present embodiment will be more fully described below.

[0044] It should be understood at the outset that message broadcast system 10 , in its broadest sense, operates both as an information removal system and an information dispersal system. Operating as an information removal system 10 , message data 12 can be personal identification data (e.g., name, address, email address, phone number, etc.) that is supplied by a user to the central controller 18 and central controller communicates with and controls selected database systems 22 to remove personal identification data therefrom. Included in message data 12 is a request to have the personal identification data removed from systems 22 that supply bulk mailers, bulk emailers and telemarketers with this information. Thus, preferably, database systems 22 are marketing warehouse systems used by bulk mailers, bulk emailers and telemarketers. Database systems 22 are selected by the central controller 18 based on the content of the message data, i.e., a request to have an email address, postal address or phone number, or all of the above, removed from the marketing warehouse systems 22 .

[0045] Operating as an information dispersal system 10 , message data 12 can be information request data that is supplied by a user to the central controller 18 and central controller communicates with and controls selected database systems 22 to disperse information related to the information request data from the database systems 22 back to the user. While not wishing to be bound by example, information request data (message data) 12 can be a request for information related to a professional organization (e.g., medical, legal, engineering, etc.), trade organization (e.g., electricians, plumbers, technicians, etc.), civic activities (e.g., voting preference, government actions/bills, etc.), community activities (e.g., conventions, events, etc.), commercial activities (e.g., business transactions, etc.) or any other particularized request for information. Accordingly, database systems 22 are database systems that contain such information and are selected by the central controller 18 to forward the information to the user in response to the information request. Thus, for example, a physician can upload a request for information (message data 12 ) on the latest drug for a disease and/or the latest report on a disease and/or latest research on a disease into the central controller 18 to have the central controller 18 automatically communicate with and control a plurality of preselected database systems 22 to forward information in response to the request.

[0046] Unless otherwise stated herein, message data 12 shall be understood to comprise information request data and/or personal identification data. Accordingly, database systems 22 shall be understood to be related to the given message data 12 .

[0047] Referring to FIG. 2 , message input stage 20 of FIG. 1 is depicted. Message data 12 is generated by a message data generator 32 . Message data generator 32 can be a personal computer, email terminal, or the like, or any other means of generating a text message containing personal information. In a preferred embodiment, message data generator 32 is a personal computer used by a customer or user 28 at a remote location. Although not shown, message data generator 32 also includes processor, memory, input devices, monitor, and anything else associated with a personal computer. Message data generator 32 also includes a communication interface 34 to communicate with the central controller 18 . In a preferred embodiment, communication interface 34 is a network server interface which permits the user to access the network (e.g., world wide web) and includes email transmissions network communication protocol. Communication interface could also be a direct dial-up interface via a modem (not shown). Of course, if communication interface 34 is an network server interface, message data generator 32 also includes (not shown) an appropriate web browsing and/or email messaging tool, as are known in the art (e.g. Netscape™, Internet Explorer™, etc.). As mentioned above, a customer or user 28 supplies message data, via message data generator 32 . Message data 12 is input into central controller 18 , via communication interface 34 , as will be described below.

[0048] Central controller 18 preferably includes a local database 46 , an external database controller 44 and at least one communication interface 36 and 70 to communicate with message data generator 32 and external database systems 22 , respectively. It is important to note at the outset that, although not shown in the figures, central controller 18 and message data generator 32 can communicate directly, via a direct modem link over communication interface 34 and 36 . Preferably, the communication takes place virtually over an external network server, for example, America On-Line™ or ISP (internet service provider), each of which can be controlled by central controller 18 . Of course, to communicate over the network, communication interface 34 and 36 must be appropriately configured for internet protocol, e.g., TCP/IP internet protocol. Thus, for example, communication interface 36 comprises a TCP/IP network interface to communicate with a network server. Message data 12 originating from at least one, but preferably a plurality of remote message data generators 32 , is uploaded into central controller 18 and stored in local database 46 . In the preferred embodiment, message data 12 is uploaded to central controller 18 via, as described above, an network server system. In addition, network server, controlled by central controller 18 , can provide a user interface to simplify and facilitate message data 12 input from a user 28 (described below).

[0049] Upon receiving message data 12 , central controller stores the message data 12 in local database 46 .

[0050] Referring to FIG. 3 , the message data output stage 30 of FIG. 1 is depicted. Message data output stage 30 is primarily directed to communication with and control of database 22 by central controller 18 . Database 22 typically comprises a database processor 52 , a communication interface 48 and a database containing message data 54 . Of course, database 22 also comprises associated hardware and software (not shown) associated with database 22 . Preferably, database 22 is one of a plurality of remote databases that can be communicated with and controlled by central controller 18 . Also, preferably database 22 is a preselected database who's identity is stored by central controller 18 on the local database 46 . Upon receiving and storing message data 12 (described above), central controller 18 initiates communication with database 22 , via communication interface 70 and 48 .

[0051] External database controller 44 is a device that is adapted to communicate with and control the external database systems 22 . At its most basic level, external database controller is coupled to a local database 46 and a communication interface 70 . In operation, message data 12 is uploaded into central controller 18 and stored on local database 46 . Upon receiving the message data 12 , local database 46 is appropriately configured to initiate communication with external database controller 44 . Likewise, external database controller initiates communication with the external database systems 22 , via communications interface 70 and 48 . External database controller 44 contains appropriate hardware and/or software to control database 22 . External database controller 22 reads message data 12 contained in local database 46 and, via communication interface 36 , initiates control signals to search database 54 for matching data contained in message data 12 . Although not shown, it is understood by those skilled in the art that local database 46 contains data related to each external database 22 . This data preferably includes communications protocol, control data, handshaking protocol, and other information used by external database controller 44 to communicate with and control each of the preselected database. Of course, to contain such data, local database must be appropriately programmed by an administrator of central controller 18 , as is understood by those skilled in the art.

[0052] As described above, communication between central controller 18 and database 22 can be initiated over a direct point-to-point link (e.g., via modem) and/or by a virtual connection over a network server. Of course, communication interface 36 and 48 must be appropriately configured to communicate in such a fashion. Central controller 18 is adapted to communicate over both mediums, depending on the particular requirements of database 22 .

[0053] FIG. 5 is a flow chart 200 illustrating the operational flow of the above-described information dispersal system of the embodiments shown in FIGS. 1 - 3 . Reference shall be made to above-described components without corresponding numbering. The system 100 begins by a user creating a text message containing information request data 102 . The user uploads the message to the central controller 104 , and the central controller stores this message on the local database 108 . Upon receiving the message data 12 , central controller determines the content of the message data to determine appropriate database systems to communicate with based on the particular information requested 106 . Upon receiving and storing the message, central controller initiates communication with an external (remote) database n 110 . Central controller queries database n, via control signals initiated by central controller, for information matching the information request 118 . Central controller, and more specifically, external database controller determines if a match is found between the user-supplied information request and data contained in the external database 112 . If a match is not found, external database controller initiates communication to another preselected database n+1. If a match is found, central controller controls the external database, based on control signals initiated by the external database controller, to disperse information in that database matching the information request 114 . Preferably, the information is dispersed directly back to the user, either in hard copy format or in electronic format that can be accessed directly on the message data generator. Alternatively, the information can be dispersed to central controller and stored there until retrieved by the user. Central controller then initiates communication to another preselected database n+1, and the above process repeats. Central controller generates a report to user indicating which databases have dispersed information found 116 .

[0054] FIG. 4 is a flow chart 100 illustrating the operational flow of the above-described personal identification information removal system of the embodiments shown in FIGS. 1 - 3 . Reference shall be made to above-described components without corresponding numbering. The system 200 begins by a user creating a text message containing personal ID data 202 . The user uploads the message to the central controller 204 , and the central controller stores this message on the local database 208 . Upon receiving the message data 12 , central controller determines the content of the message data to determine appropriate database systems to communicate with based on the particular personal identification to be removed 206 . Upon receiving and storing the message, central controller initiates communication with an external (remote) database n 208 . Central controller queries database n, via control signals initiated by central controller, for matching message data 210 . Central controller, and more specifically, external database controller determines if a match is found between the user-supplied message data and data contained in the external database 212 . If a match is not found, external database controller initiates communication to another preselected database n+1. If a match is found, central controller controls the external database, based on control signals initiated by the external database controller, to remove information in that database matching the personal identification data 214 . Central controller then initiates communication to another preselected database n+1, and the above process repeats. Central controller generates a report to user indicating which databases had data removed 216 .

[0055] In another embodiment, and again referring to FIGS. 1 - 3 , the message broadcast system 10 comprises a central controller, a plurality of remote, external databases 22 , 24 , 26 , and a plurality of message data 12 , 14 , 16 generated by a plurality of users 28 . In this embodiment, message data 12 includes preference data or request data indicating the users' preference of having the personal information contained in the message data removed from the database 22 . User 28 generates message data 12 and uploads message data 12 into central controller 18 , as in the previous embodiment. Central controller 18 initiates communication with database 22 and uploads message data into database 22 . As in the previous embodiment, the process repeats for the next preselected database. However, central controller does not control the database systems, rather an administrator (not shown) of database system 22 removes personal identification data contained in message data from database 22 , in accordance with the request or preference indicated in message data 22 .

[0056] Referring to FIG. 6 , another embodiment of the message data input stage 20 ′ of the present invention is depicted. Its elements operate essentially the same as the message data input stage 20 of the previous embodiment. Additionally, however, message data input stage 20 ′ provides a PIN server 64 , operable over a telephone network 56 via a standard telephone 56 . At its most basic level, PIN server generates a unique PIN access code to each user. The user includes the unique access code when accessing central controller 18 ′ to upload message data 12 ′. Thus, central controller 18 ′ acts as a subscription service system and is available only to users who have valid PIN access code. Each of these functional components will be described below.

[0057] PIN server 64 is a remote server typically operated by long distance service providers (e.g., AT&T, Sprint, MCI, etc.) or by local exchange carriers (e.g., NYNEX, etc.) and is generally a random number generator adapted to communicate with both user 28 ′ and central controller 18 ′. PIN server 64 essentially has two functional components associated with it: PIN server access from a user 28 ′ and PIN server access, update and administration from the central controller 18 ′. In operation, user 28 ′ accesses PIN server 64 by dialing a particular access number (e.g., 900#) over a standard telephone 56 . PIN server 64 queries user 28 ′ by preferably using an interactive voice response (IVR) system. Typically, user 28 ′ is requested by PIN server 64 to supply personal information to ensure security, PIN server 64 then issues a unique PIN access code number to that user. In addition, PIN server is configured, via the local exchange carrier, to issue a debit to the user's monthly phone record and to issue a corresponding credit report to the central controller 18 ′. In this regard, PIN server 64 can be adapted to provide various levels of services based on the user's preference (i.e., a user can be provided with more services by increasing the debit). The various levels of services offered can be administered and controlled by central controller 18 ′.

[0058] Using the PIN access code issued by PIN server 64 , user 28 ′ inputs message data and PIN number 12 ′ using the message data generator 32 ′, as in the previous embodiment. User 28 ′ uploads message data and PIN 12 ′, via communication interface 34 ′ and 36 ′, into central controller. Of course, as in the previous embodiment, communication interface 34 ′ and 36 ′ can be a direct communication or a virtual connection over a network server (internet). Message data and PIN 12 ′ is stored on local database 46 ′.

[0059] The central controller 18 ′ of this embodiment also includes a telephone network interface 58 adapted to communicate with and control PIN server 64 aver a standard telephone network 62 . Central controller 18 ′ routinely accesses PIN server 64 to get pertinent information regarding the status of PIN server, for example, PIN access codes issued, customer (or user 28 ′) account information, customer personal identification data, etc. This status information is stored on local database 46 ′ and is used by central to compare against the information contained in message data 12 ′ to ensure that the person sending the message data 12 ′ is the individual who is granted access to the central controller 18 ′. Central controller 18 ′ also controls PIN server 64 to facilitate updates and other control functions associated with PIN server 64 . For example, central controller 18 ′ is appropriately configured to control PIN server 64 to set operational parameters (e.g., user-level access, communication protocol, etc.) and to control various security parameters with the PIN server, as is known in the art. To facilitate communication and control of PIN server, central controller 18 ′ also has an administration system (not shown) appropriately configured to administer and control both the central controller 18 ′ and the PIN server 64 .

[0060] As mentioned above, in this embodiment local database 46 ′ stores both message data and PIN 12 ′ and customer account information. To ensure security, local database checks the information in the message data and PIN access code 12 ′ supplied by user 28 ′ against the customer account information supplied by PIN server 64 . If a correct match is found, central controller initiates communication with external database system 22 , via communications interface 70 ′, in accordance with the previous embodiments.

[0061] FIG. 7 is a flow chart 300 illustrating the operational flow of the information request system of the above-described embodiment of FIGS. 3 and 6 . Reference will be made to above-described components without corresponding numbering. Customer dials the appropriate access number over a telephone network to access the PIN server 302 . After supplying PIN server with customers' identification information, PIN server grants customer a unique PIN access code 304 . PIN server also generates a debit bill for service directly to customers phone bill, typically generated by a local exchange carrier 304 . With knowledge of the PIN granted by PIN server, customer creates a text message containing information request data and PIN access code 308 . Customer initiates communication with central controller and uploads text message to central controller 310 . At periodic intervals, central controller communicates with the PIN server to retrieve valid PIN access codes issued by PIN server for comparison 314 . Central controller updates the PIN server with current data of valid PIN access codes to ensure that no code is used more than once for a given transaction 316 . Central controller compares text message against information supplied by PIN server to validate the PIN account based on personal identification data contained in the text message 312 . If the comparison is not valid 318 , indicating either that customer has supplied the wrong PIN number or the personal identification associated with the PIN number does not match, central controller generates a message (e.g., email) to customer indicating current status 320 . If a match is found 318 , central controller stores message data (i.e., personal identification data) in the local database 322 . In a similar fashion of the previous embodiment of FIG. 4 , upon receiving and storing the message, central controller initiates communication with an external (remote) database n 324 . Central controller queries database n, via control signals initiated by central controller, for information matching the information request 326 . Central controller, and more specifically, external database controller determines if a match is found between the user-supplied information request and data contained in the external database 328 . If a match is not found, external database controller initiates communication to another preselected database n+1. If a match is found, central controller controls the external database, based on control signals initiated by the external database controller, to disperse information in that database matching the information request 330 . Central controller then initiates communication to another preselected database n+1, and the above process repeats. Central controller generates a report to user indicating which databases have dispersed information 332 .

[0062] FIG. 8 is a flow chart 400 illustrating the operational flow of the information removal system of the above-described embodiment of FIGS. 3 and 6 . Reference will be made to above-described components without corresponding numbering. Customer dials the appropriate access number over a telephone network to access the PIN server 402 . After supplying PIN server with customers' identification information, PIN server grants customer a unique PIN access code 404 . PIN server also generates a debit bill for service directly to customers phone bill, typically generated by a local exchange carrier 404 . With knowledge of the PIN granted by PIN server, customer creates a text message containing personal identification data and PIN access code 408 . Customer initiates communication with central controller and uploads text message to central controller 410 . At periodic intervals, central controller communicates with the PIN server to retrieve valid PIN access codes issued by PIN server for comparison 414 . Central controller updates the PIN server with current data of valid PIN access codes to ensure that no code is used more than once for a given transaction 416 . Central controller compares text message against information supplied by PIN server to validate the PIN account based on personal identification data contained in the text message 412 . If the comparison is not valid 418 , indicating either that customer has supplied the wrong PIN number or the personal identification associated with the PIN number does not match, central controller generates a message (e.g., email) to customer indicating current status 420 . If a match is found 418 , central controller stores message data (i.e., personal identification data) in the local database 422 . In a similar fashion of the previous embodiment of FIG. 5 , upon receiving and storing the message, central controller initiates communication with an external (remote) database n 424 . Central controller queries database n, via control signals initiated by central controller, for information matching the personal identification data 426 . Central controller, and more specifically, external database controller determines if a match is found between the user-supplied information request and data contained in the external database 428 . If a match is not found, external database controller initiates communication to another preselected database n+1. If a match is found, central controller controls the external database, based on control signals initiated by the external database controller, to remove information in that database matching the personal identification data 430 . Central controller then initiates communication to another preselected database n+1, and the above process repeats. Central controller generates a report to user indicating which databases had data removed 432 .

[0063] Referring to FIG. 9 , another embodiment of the message data input stage 20 ″ of the present invention is depicted. Its elements operate essentially the same as the message data input stage 20 and 20 ′ of the previous embodiments. Additionally, however, message data input stage 20 ′ provides a network server 66 and an administration system 68 , as will be described below. It is to be understood that, although not shown in FIG. 9 , central controller 18 ″ incorporates all of the essential elements as in the previous embodiments, i.e., external database controller 44 , 44 ′. At its most basic level, this embodiment provides a system to permit user 28 ″ to contact network server 66 , access PIN server 64 ′ through the network server 66 , and upload message data and PIN access code 12 ″ to central controller 18 ″ directly from the network server 66 . Thus, unlike the previous embodiment, customer 28 ″ need not make a separate telephone call to the PIN server 64 ′, rather, customer 28 ″ can receive a PIN access code and upload message data all on the network server 66 , as explained below.

[0064] In this embodiment, customer 28 ″, via massage data generator 32 ″, communicates with network server 66 to facilitate creation and uploading of message data and PIN access code 12 ″. Network server 66 can be a remotely hosted internet site, web page, or the like, that is controlled and maintained by central controller 18 ″. Of course, communication interface 34 ″ is appropriately configured to allow message data generator to communicate with network server 66 . For example, if network server 66 is a remotely hosted web page, communication interface 34 ″ is appropriately configured to interactively communicate with the web page, e.g., via TCP/IP and/or FTP (file transfer protocol).

[0065] Network server 66 is appropriately configured to provide customer 28 ″ with the following functions: interactive text communication (e.g., email), access to PIN server to obtain a PIN account and direct uploading of message data and PIN access code 12 ″ to central controller 18 ″. In addition, network server 66 communicates with PIN server 64 ′ to dynamically update PIN server 64 ′ directly from the network server 66 . For example, customer 28 ″ in this embodiment can change or alter PIN access code data and accompanying message data. Also, the customer 28 ″ can access PIN server 64 ′ to obtain PIN access code, create message data (including PIN access code) and upload this information directly to central controller 18 ″ all in one step. Of course PIN server 64 ′ can be appropriately configured to generate a debit report directly to the user's 28 ″ telephone bill. Or, PIN server 64 ′ can be appropriately configured to accept debit financial transaction directly on the network server 66 (e.g., customer 28 ″ supplies the network server 66 with a credit card account number). PIN server also 64 ′ generates a credit report to central controller and credits an account that is set up on PIN server 64 ′ having the central controller 18 ′ as the beneficiary of the funds received.

[0066] Similarly, central controller 18 ″ connects to network server 66 via appropriately configured communication interface 36 ″. However, central controller 18 ″ is the controller of network server 66 , and thus, unlike user 28 ″, is granted full access and control over network server 66 and PIN server 64 ′. To facilitate control and maintenance of network server 66 , PIN server 64 ′ and central controller 18 ″, an administration system 68 is provided. Administration system 68 provides an administrator (not shown) access to local database 46 ″ for local programming and administrative functions. Also, administrative system 68 connects to network server to program and administer network server 66 and provide customer 28 ″ parameters, PIN server access and programming and general localized control over network server, as is known in the art. Only central controller 18 ″, via administration system 68 , has the ability to change parameters of the network server 66 and PIN server 64 ′, thus, central controller has global control over network server 66 and PIN server 64 ′ to set parameters for customer-level access.

[0067] Once the message data has been received by central controller 18 ″, central controller 18 ″ initiates communication to external database 22 , to upload and/or control external database system 22 in accordance with the previous embodiments of the message data output stage 30 of the present invention as depicted in FIG. 3 .

[0068] FIG. 10 depicts another embodiment of the message broadcast system 10 ′ of the present invention and includes communication between central controller 18 ″, message data generator 32 ″ and database systems 22 ′ entirely over a network server 66 . Message data input stage 20 ″ of FIG. 9 (described above) is incorporated into FIG. 10 . In this embodiment, communication interface 48 ′ of database system 22 ′ is adapted to communicate with the network server, as described above with reference to communication interface 34 ″ and 36 ″. Accordingly, communication interface 36 ″ of central controller 18 ″ is appropriately configured to permit communication and control of database systems 22 directly over the network server. Moreover, in this embodiment, and with particular reference to the information dispersal system of the present invention, database system 22 ′ can be appropriately controlled by the central controller 18 ″ to forward information directly to the message data generator over the network server 66 , without having to pass through the central controller 18 ″.

[0069] FIG. 11 is a flow chart 600 illustrating the operational flow of the information dispersal system of the above-described embodiment of FIG. 10 . Reference will be made to above-described components without corresponding numbering. Customer contacts network server to access the pin server 602 . Through interactive communication over the network server, customer is granted a unique PIN access code 604 . PIN server also generates a debit bill for service directly to customer's phone bill or by a financial transaction over the network server 604 . Customer creates a text message, either locally on the message data generator or virtually on the network server, that includes the PIN access code granted by PIN server and information request data 606 . Customer initiates communication with central controller and uploads text message to central controller 608 . Because network server is in communication with central controller, preferably, network server automatically forwards the text message to central controller. Thus, customer preferably need not make a separate communication with central controller, rather network server provides a direct on-line connection to central controller via, e.g., a web page server. Upon receiving the text message, central controller compares text message to information supplied by PIN server to validate the PIN account based on personal identification data contained in the text message 610 (i.e., using PIN server access and updating 612 and 614 , respectively). If the comparison is not valid 616 , indicating either that customer has supplied the wrong PIN number or the personal identification associated with the PIN number does not match, central controller generates a message (e.g., email) to customer indicating current status. If a match is found, central controller stores message data in the local database 620 . Upon receiving and storing the message, central controller initiates communication with an external (remote) database n 622 over the network server. Central controller queries database n, using control signals supplied by central controller over the network server, for information matching the information request data 624 . Central controller, and more specifically, external database controller determines if a match is found between message data and data contained in the external database 626 . If a match is not found, external database controller initiates communication to another preselected database n+1. If a match is found, central controller controls the external database (over the network server), based on control signals initiated by the external database controller, to disperse information in that database matching the information request data 628 . Moreover, central controller controls the database to disperse the appropriate information directly over the network server to the message data generator (and, ultimately, to the customer). External database controller then initiates communication to another preselected database n+1, and the above process repeats. After all of the preselected external databases are contacted by central controller, central controller generates a report to user indicating which databases dispersed information 630 .

[0070] FIG. 12 is a flow chart 700 illustrating the operational flow of the information removal system of the above-described embodiment of FIG. 10 . Reference will be made to above-described components without corresponding numbering. Customer contacts network server to access the pin server 702 . Through interactive communication over the network server, customer is granted a unique PIN access code 704 . PIN server also generates a debit bill for service directly to customer's phone bill or by a financial transaction over the network server 704 . Customer creates a text message, either locally on the message data generator or virtually on the network server, that includes the PIN access code granted by PIN server and personal identification data 706 . Customer initiates communication with central controller and uploads text message to central controller 708 . As described above, network server is in communication with central controller and network server automatically forwards the text message to central controller. Thus, customer preferably need not make a separate communication with central controller, rather network server provides a direct on-line connection to central controller via, e.g., a web page server. Upon receiving the text message, central controller compares text message to information supplied by PIN server to validate the PIN account based on personal identification data contained in the text message 710 (i.e., using PIN server access and updating 612 and 614 , respectively). If the comparison is not valid 716 , indicating either that customer has supplied the wrong PIN number or the personal identification associated with the PIN number does not match, central controller generates a message (e.g., email) to customer indicating current status. If a match is found, central controller stores message data in the local database 720 . Upon receiving and storing the message, central controller initiates communication with an external (remote) database n 722 over the network server. Central controller queries database n, using control signals supplied by central controller over the network server, for information matching the personal identification data 724 . Central controller, and more specifically, external database controller determines if a match is found between message data and data contained in the external database 726 . If a match is not found, external database controller initiates communication to another preselected database n+1. If a match is found, central controller controls the external database (over the network server), based on control signals initiated by the external database controller, to remove information in that database matching the personal identification data 728 . External database controller then initiates communication to another preselected database n+1, and the above process repeats. After all of the preselected external databases are contacted by central controller, central controller generates a report to customer indicating which databases had personal identification data removed 730 .

[0071] In any of the above-described embodiments, central controller 18 , 18 ′ and 18 ″ is adapted to contain optimal searching parameters of database systems 22 for information removal and/or dispersal. Optimal searching is based on the specific content of message data 12 , 12 ′, 12 ″ and also the specific database system 22 , 22 ′ to be controlled by central controller. Thus, central controller 18 , 18 ′ and 18 ″ is adapted to interpret message data 12 , 12 ′, 12 ″ to recognize the specific data contained therein. Interpretation of message data 12 , 12 ′, 12 ″ can be based on specific text search strings initiated by central controller so that central controller can make an optimal decision for information searching and/or removal. Also, central controller 18 , 18 ′ and 18 ″ is adapted to optimally control database systems 22 , 22 ′ based on the message data and also based on the particular database system to be controlled. In addition, central controller is adapted to contain optimal searching parameters of a plurality of database systems 22 , 22 ′ and further to implement such parameters in an automatic fashion.

[0072] As mentioned above, the information dispersal system of the present invention is intended to facilitate refined searching and dispersal of information from a plurality of preselected, specialized database systems 22 , 22 ′. While not wishing to be bound by example, the present invention can provide specialized, efficient information dispersal for medical professionals, legal professionals, trade professionals, localized civic events, voting preferences and voting histories of senators, congressmen at both national and local levels, specific commercial activities, and any other specialized transaction where a user requires specific information on a specific topic. Central controller is therefore adapted to contain control information for a plurality of preselected database systems related to the specialized information requested. To that end, central control is adapted to interpret the incoming message to optimally find the correct information desired. Thus, for example, central controller can provide a user interface that restricts the users' information input, thereby inherently refining the search parameters. This can be accomplished, for example, by providing a web-page interface that requires the user to “pigeon-hole” an information request by requiring progressive refinements. Alternatively, central controller can be adapted to read the message data in directly and scan the text for specific text strings or words that indicate the information request. Either way, central controller initiates communication and control of the database systems based on the message data content.

[0073] Moreover, central controller, via administration system, is continually updated with new database systems that can be controlled by central controller and that fit into a specific category of user information requests.

[0074] Thus, it is evident that there has been provided a message broadcast system and method for operating same that fully satisfy both the aims and objectives hereinbefore set forth. It will be appreciated that although specific embodiments and methods of use have been presented, many modifications, alternatives and equivalents are possible.

[0075] There are certain direct marketing database systems that cannot communicate with the central controller 18 , 18 ′ or 18 ″. In addition, certain database systems require a written (i.e., hardcopy) removal request before removing personal identification data therefrom. In either instance, central controller 18 , 18 ′ and 18 ″ can be appropriately modified to communicate with certain ones of the preselected database systems that are adapted to generate a hardcopy message and supply these certain database systems with the appropriate location information indicating where to forward the hardcopy message.

[0076] Local database 46 , 46 ′, 46 ″ has been described above as containing information generated from user 28 , 28 ′, 28 ″, and database system 22 , but local database 46 , 46 ′, 46 ″ can also be appropriately configured to contain control data related to PIN server 64 , 64 ′ and network server 66 . Of course, local database 46 , 46 ′, 46 ″ can be separate databases, each separately containing the above-described parameters, or local database 46 , 46 ′, 46 ″ can be one unified database appropriately programmed to contain these parameters in the appropriate format. Optimal search parameters based on the particular message data received and the particular database to be controlled can also be stored on the local database 46 , 46 ′, 46 ″ and preferably operate in conjunction with the external database controller 44 , 44 ′ to permit optimal control of the external database systems from the central controller.

[0077] Also, the foregoing detailed description described storing the message data on local database 46 , 46 ′, 46 ″ before other action is taken (i.e., communication with database systems 22 and 22 ′); however, it is to be understood that storing, as defined herein, is only an operational parameter of maintaining the message data locally (i.e., local to the central controller). Thus, storing the message data need not be an additional process that requires additional hardware, but can merely be performed locally in ROM or RAM when the message data is uploaded by the message data generator.

[0078] External database controller 44 , 44 ′ is appropriately programmed to facilitate communication with and control of external database systems 22 . To this end, administration system can be appropriately configured so as to have global control external database controller 44 , 44 ′. Processor 38 , 38 ′ is configured to generally control local database and external database controller, and can be a standard off-the-shelf process (e.g., Pentium, RISC) or a customized processor (e.g., PLD), as is known by those skilled in the art. Of course, processor 38 , 38 ′ has associated ROM/RAM system 42 , 42 ′ for local information processing. Also, central controller and administration system 68 can be separate components or all part of one unified system.

[0079] Although the foregoing detailed description has proceeded without reference to specific hardware and/or software for implementing the system, it will be understood by those skilled in the art that central controller 18 , 18 ′ and 18 ″ of the present invention can be implemented with various hardware, software, or any combination thereof, without departing from the scope of the present invention. Preferably central controller 18 , 18 ′ and 18 ″ is implemented with a high-speed computer system and control software that has general applicability to many control scenarios for controlling the database systems heretofore described. Thus, for example, to facilitate high-speed transmission, central controller 18 , 18 ′ and 18 ″ can be adapted to communicate over the network using a T1 and/or T3 communication system. Moreover, central controller 18 , 18 ′ and 18 ″ can be adapted to permit real-time user interactivity, thus permitting a user to complete the entire transaction (e.g., information removal and/or information dispersal) at one time.

[0080] In addition, network server 66 can be a preprogrammed internet web page having a user interface that supplies an email messaging system and a direct link to central controller 18 , 18 ′, 18 ″. Thus, instead of user creating a text message locally using message data generator, user can create the text message directly on the network server. To this end, network server can be appropriately configured to provide a “fill-in-the-blanks” text message interface for the user. PIN server 64 ′ is programmed by administration system 68 to communicate with network server and further to provide administrative control over PIN server 64 ′, via network server 66 . Thus, central controller 18 ″ has global control over parameters offered by PIN server 64 .

[0081] Although the foregoing detailed description has been described with reference to a variety of particular utilities of the present invention, the present invention is of broad scope intended to cover centralized transactions where an information dispersal system has advantages over the art. For example, the present invention can be utilized as a centralized commercial transaction system whereby users (or customers) can engage in a variety of commercial transactions using the aforementioned information dispersal system of the present invention. Some examples include travel information, greeting card services, news and news related information, etc. In addition, the information dispersal system of the present invention can be adapted to permit a variety of other transactions. For example, the present invention can be utilized as a means of posting a single resume from a job applicant to all appropriate job banks in any geographically remote database systems, as requested by the applicant. Therefore, the present invention is intended to permit message broadcasting (information removal and/or information dispersal) from a centralized controller to access to a variety of geographically remote database systems, depending on the particular request from the user. Of course, to facilitate the above-mentioned transactions, central controller must be appropriately programmed to connect with the particular databases systems, as described herein. The present invention is intended to cover all such applications of the information dispersal system described herein, as set forth in the appending claims.

[0082] Accordingly, the present invention is intended to cover all such alternatives, modifications, and equivalents as may be included within the spirit and broad scope of the invention as defined only by the hereafter appended claims.