Abstract:
A method and system are disclosed for authenticating on-line updates to listings maintained by a network-based directory service. An exemplary method for authenticating updates submitted on-line includes: (1) receiving an on-line update for a listing; (2) receiving origination information associated with a telephone call initiated by a user of a phone line corresponding to the listing; and (3) detecting a match between the origination information and at least a portion of the listing to authenticate the update. In one embodiment of the present invention, the origination information is a telephone number common to both the phone line from which the user is calling and the listing.

Description:
TECHNICAL FIEELD 
     This invention relates generally to a network-based directory service, and more particularly, to a method and system for collecting and authenticating on-line updates to listings maintained by the directory service. 
     BACKGROUND 
     It is known in the art to operate a network-based directory service--i.e., an on-line &#34;white pages&#34; which can be accessed via a client application, such as a world-wide-web (&#34;WWW&#34;) browser. Such directories contain approximately 100 million residential and business listings. These listings typically include name, address and telephone number information, together with business category information for non-residential listings. The operator of the directory service usually obtains the data for these listings from a data provider. 
     Users of the directory service are presently able to add, remove, and change (i.e., update) their listings on-line. To effect an on-line update, a user is required to provide the directory service, at the time of the update, with an e-mail address to which the service can thereafter send a message confirming the update. Once the user provides an e-mail address, the directory service will generate a new record for the listing in accordance with the update request. However, this method of update authentication is not entirely satisfactory, and indeed, is prone to fraud because e-mail addresses are (1) ephemeral, (2) not easily traced to an individual owner, and (3) not necessarily associated with the listing being updated. As such, fraudulent updates can easily be effected by users other than the owner of the listing. 
     Therefore, a method and system are needed to provide owners of directory listings with an opportunity to go on-line and update information corresponding to their listings in a manner that is efficient, error free, and resistant to fraud. 
     SUMMARY OF INVENTION 
     The above-identified problems are solved and a technical advance is achieved in the art by providing a method and system for authenticating on-line updates to listings in a network-based directory service. An exemplary method for authenticating on-line updates includes: (1) receiving an on-line update for a listing; (2) receiving origination information associated with a telephone call initiated by a user of a phone line corresponding to the listing; and (3) detecting a match between said origination information and at least a portion of the listing to authenticate the update. 
     In accordance with the present invention, the aforementioned problems associated with using an e-mail address to authenticate an update are eliminated; an individual with access to the phone line associated with the listing being updated is likely to be either the owner of the listing or some other individual authorized to confirm the update. 
     Other and further aspects of the present invention will become apparent during the course of the following description and by reference to the attached drawings. 
    
    
     BRIEF DESCRIPTION OF THE DRAWING 
     FIG. 1 is a block diagram illustrating one embodiment of the present invention. 
     FIG. 2 is a block diagram illustrating an alternate embodiment of the present invention. 
    
    
     DETAILED DESCRIPTION 
     Referring now to the drawings, wherein like reference numerals refer to like parts, FIG. 1 illustrates one embodiment of the present invention. In this embodiment, the network-based directory service update process comprises four phases: (1) update collection; (2) update confirmation; (3) update application; and (4) update maintenance. 
     Update Collection: 
     As shown in FIG. 1, a user of a personal computer 5 is provided access to the internet 10 via an internet service provider 15 and can thereby access a web page of a network-based directory service. The web page is maintained by a web server 20 and contains various forms created using a hypertext mark-up language. These forms provide the user with a means of interacting with the network-based directory service. In particular, the user can submit queries, select listings, and update information corresponding to the listings selected. A listing can include a wide variety of information including, but not limited to, names, addresses, telephone numbers, fax numbers, cellular phone numbers, e-mail addresses, business addresses, hours of operation, etc. 
     The web server 20 responds to a user&#39;s selection of a directory listing by obtaining the listing and the information associated therewith from directory server 25. It is to be understood that the user interface functionality of web server 20 could, alternatively, be provided by directory server 25, in which case a separate web server would not be required. The directory server 25, in turn, retrieves this information from database 30. The operation of database 30 and the provisioning thereof with the most up-to-date information for each directory listing will be described in detail below. 
     The web server 20 allows the user to both create a new listing and to either delete or revise a selected listing. The creation of a new listing, or the deletion or revision of information associated with a pre-existing listing is referred to hereinafter as &#34;an update&#34;. The web server 20 provides the user with an opportunity to verify that the update is correct (e.g., that the update does not contain any typographical errors). The web server 20 also audits the update for basic validity. For example, the web server 20 may verify that the correct number of digits for a telephone number has been entered by a user or, that the state and city information for the listing are consistent with the area code of the telephone number entered. 
     Once the user has verified that the update is correct, the web server 20 time stamps the update (i.e., the current time and date are added to the user-supplied information) and transmits it to database 35 where it is stored for a predetermined period of time pending confirmation by the user. The web server 20 requests the user to call a designated telephone number (either a toll-free number or a &#34;900&#34; number, as the update service may be either free or paid for by the user) from the phone line 55 associated with the listing being updated in order to confirm the update. 
     Update Confirmation: 
     When the user calls the designated number to confirm his update, the user is connected to voice response unit (VRU) 40, which, in turn, is coupled to a script database 45 and an update processor 50. The update processor 50 receives the telephone number corresponding to the line 55 from which the user is calling. The telephone number can be transmitted to the processor 55 in any number of ways including, but not limited to, via a calling line identification service provided by telephone service provider 60. Moreover, the telephone number transmitted to the processor 50 may be the automatic number identification (ANI) corresponding to the line 55 from which the user is calling, rather than the calling party number (CPN) corresponding to same. 
     The processor 50 then determines whether an update is pending for line 55 by comparing the telephone number corresponding to line 55 against the telephone numbers of all updates pending in database 35. The processor 50 provides the VRU 40 with the results of this comparison. 
     If it is determined that an update is not pending for line 55, the VRU 40 will play a pre-recorded announcement retrieved from database 45 to inform the user of such and will thereafter terminate the call. The Conversant™ Voice System, manufactured by AT&amp;T, is one unit which can be used to carry out the functions of VRU 40. Alternatively, if no updates are pending, the VRU 40 may refer the user to an attendant who can provide further assistance. For example, the attendant may be able to accept updates over the phone. 
     If an update is pending for line 55, the VRU 40 will play a pre-recorded announcement to inform the user of the update and to determine whether the user desires to confirm or cancel it. The VRU 40 will inform the user of the pending update by announcing the time-stamp for the update. Optionally, the VRU 40 may also announce the updated listing to the user. In cases where more than one update is pending for a given line 55, the use of the time-stamp alone or in combination with the announcement of the updated listing will (1) assist the user in determining which update is being confirmed or canceled and (2) prevent the user from inadvertently confirming a fraudulent update submitted by another user. 
     The user can then confirm or cancel the pending update by pressing the appropriate touch-tone button on the keypad of his telephone (e.g., &#34;1&#34; to confirm, &#34;2&#34; to cancel). Optionally, the user may also be required to enter a code number provided by the web server 20 (and stored with the update in database 35) when the update was submitted on-line by the user. This feature further prevents the user from inadvertently confirming an update submitted by an unauthorized individual; the user who submitted the update is the only person with the code number for the update. 
     In any event, the update processor 50 deletes canceled updates from database 35 and forwards confirmed updates to database 65. 
     Update Application: 
     As shown in FIG. 1, database 70 stores base directory data. This data is initially purchased from a data provider, such as Database America, and is thereafter merged with confirmed updates (database 65) and updates from sources other than the network-based directory service web-page (database 75), such as the U.S. Mail or live attendants, to generate revised directory data. The revised directory data is stored in database 85 and is made available to. the directory server 25, and thus, to users of the network-based directory service, via database 30. 
     The process 80 of merging the updates into the directory database 30 may be continuous (thus allowing immediate access to confirmed updates) or periodic (thereby allowing access to confirmed updates when the current merge cycle is complete). In either case, the directory data in database 30 becomes the base directory data in database 70 at the commencement of the merge process. 
     Update Maintenance: 
     Periodically (e.g., once each day), the update processor 50 will examine the updates pending in database 35 and will discard those that were not confirmed within some reasonable amount of time (e.g., 5 days) after being submitted. In addition, the update processor 50 may replace a pending update request with a new update request for the same listing, if the new request is submitted before the existing request is confirmed. 
     The many features and advantages of the present invention are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the invention which fall within the true spirit and scope of the present invention. 
     Furthermore, since numerous modifications and variations will readily occur to those skilled in the art, it is not desired that the present invention be limited to the exact construction and operation illustrated and described herein, and accordingly, all suitable modifications and equivalents which may be resorted to are intended to fall within the scope of the claims. For example, FIG. 1 illustrates one embodiment of the present invention wherein client access to the directory service is via a computer communications network such as the WWW. However, as shown in FIG. 2, access to the directory service may be via any network 12 including, but not limited to, the WWW. For example, network 12 may be a telephone network, in which case the client 6 would access the directory service by direct dialing server 18 using a modem. The web server 20 shown in FIG. 1 would therefore not be required in the embodiment of FIG. 2. Rather, server 18 alone, or in combination with a client application, would provide the necessary client interface functionality. The operation of the embodiment of FIG. 2 would otherwise be identical to the operation of the embodiment shown in FIG. 1.