WO2000038394A1

WO2000038394A1 - Web-page audio message system and method

Info

Publication number: WO2000038394A1
Application number: PCT/US1999/030750
Authority: WO
Inventors: Barry Septimus; Judah Libin; Bruce Fancher
Original assignee: Pagetalk, Inc.
Priority date: 1998-12-23
Filing date: 1999-12-23
Publication date: 2000-06-29
Also published as: AU2382000A

Abstract

A web-page audio message system includes a telephone server (6), a database server (8), a file server (8), a web server (10) and an audio server (10). A user desiring audio service registers with the system via the web server (10). The web server (10) retrieves user information and forwards that information to the database server (8) for storage. Alternatively, a user may obtain audio service through an affiliate web-page (9) or other service provider by requesting the audio message feature. The user may have one or more audio buttons and corresponding messages associated with one or more web-pages. Once a user is registered, the user may create or modify the audio message by accessing the telephone server (6) via a conventional telephone (2). The telephone server (6) prompts the caller for an access code, PIN, and button number, and verifies the entered information. A user message is recorded and the telephone server provides an audio file to the file server (8) for storage. When an end user visits a web-page and selects an audio button, a database query is transferred to the database server (8) to retrieve the corresponding audio file. The database server (8) tracks information relating to users, selection of audio buttons and the quantity of selections for marketing purposes. The retrieved audio file is transferred from the file server (8) to the audio server (10) for playback to the end-user.

Description

WEB-PAGE AUDIO MESSAGE SYSTEM AND METHOD

CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority from U.S. Provisional Patent Application Serial No. 60/113,461, entitled "Web-Page Audio Message System and Method", filed December 23, 1998. The disclosure of the above-referenced provisional patent application is incorporated herein by reference in its entirety. BACKGROUND OF THE INVENTION 1. Technical Field The present invention pertains to audio publishing tools. In particular, the present invention is directed toward a system facilitating creation and modification of audio information on an Internet web-page via a conventional telephone. 2. Discussion of Related Art The Internet is an established medium for disseminating tremendous amounts of information to a large number of people. One way the Internet is used as a medium for information dissemination is via audio which can be accessed on a web-page. Internet audio has been utilized only to a limited extent because the process of audio input and change on a web-page is cumbersome and time consuming. Further, a level of technical sophistication, usually beyond that of an ordinary person, and a significant amount of time are typically required to enter or change audio content on a web-page. The present invention pertains to a system and method that alleviate both of these obstacles. In particular, the system allows the content of an audio message to be placed on a web-page and modified using a conventional telephone in a minimum amount of time without requiring technical expertise. The system enables individual users to place and modify audio messages on their own web-pages, or permits affiliate web-page or other service providers to provide this feature in response to user requests. In addition, the system may further be utilized to provide audio for e-mail or other applications. Currently, placing audio content on a web-page requires digitization of the audio on a local computer, converting the audio into a compatible or web friendly format (e.g., a format that can be stored on a web server, such as Real Audio or any other one of several currently available formats), and transferring the resulting converted audio file to a web server (e.g., the server containing the web-page). Once the file resides on the web server, the web server is configured in a format that is capable of serving Real Audio files (e.g., one such format is Real Server). Finally, a hyperlink or icon is placed on the web-page to provide end-user access to the audio file audio content. This entire process is repeated in order to modify the audio content. OBJECTS AND SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to simplify both the initial entry of audio content onto a web-page, and the subsequent changing of the audio content on the web-page. It is another object of the present invention to permit entry and modification of a web- page audio message using a conventional telephone. A further object of the present invention is to permit a person without significant technical training to enter and change audio content on a web site. The aforesaid objects are achieved individually and in combination, and it is not intended that the present invention be construed as requiring two or more of the objects to be combined unless expressly required by the claims attached hereto. According to the present invention, a web-page audio message system includes a telephone server, a database server, a file server, a web server and an audio server. The servers may be implemented on and/or distributed among any quantity of computer systems. A user desiring audio service registers with the system via the web server. The web server retrieves user information and forwards that information to the database server for storage. The database server generates a user identification to uniquely identify the user to the system, while the web server provides computer code to enable the user to update his her web page to include an audio button. The user may have one or more audio buttons and corresponding messages associated with one or more web-pages. Alternatively, a user may obtain audio service through an affiliate web-page or other service provider by requesting the audio message feature. The affiliate provider retrieves user information and communicates directly with the system web server to register the user for audio service. The affiliate provider retrieves information from the web server and updates the user web-page to include an audio button for playback of an audio message. Once a user is registered, the user may create or modify the audio message by accessing the telephone server via a conventional telephone. The telephone server prompts the caller for an access code, PIN and button number, and verifies the entered information. A user message is recorded and the telephone server provides an audio file to the file server for storage. When an end-user visits a web-page and selects an audio button, a database query is transferred to the database server to retrieve the corresponding audio file. The database server tracks information relating to users, selection of audio buttons and the quantity of selections for marketing purposes. The retrieved audio file is transferred from the file server to the audio server for playback to the end-user. The above and still further objects, features and advantages of the present invention will become apparent upon consideration of the following detailed description of specific embodiments thereof, particularly when taken in conjunction with the accompanying drawings wherein like reference numerals in the various figures are utilized to designate like components. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagrammatic illustration of a network topology extending between a telephone and the Internet according to the present invention. Fig. 2 is a diagrammatic illustration of a portion of the network topology of Fig. 1 extending between a switched telephone network and the Internet. Fig. 3 A is a block diagram of a telephone application server illustrating the server internal software hierarchy according to the present invention. Fig. 3B is a procedural flow chart illustrating the manner in which user audio is managed by the telephone server according to the present invention. Fig. 3C is a block diagram of a database/file server illustrating the server internal software hierarchy according to the present invention. Fig. 3D is a block diagram of a web/audio server illustrating the server internal software hierarchy according to the present invention. Fig. 4A is a procedural flow chart illustrating the manner in which audio is placed on a web-page according to the present invention. Fig. 4B is exemplary HTML code facilitating audio access from a web-page. Fig. 4C is a procedural flowchart illustrating the manner in which audio residing on a web-page is accessed by end-users according to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A system for placing audio on a web-page according to the present invention is illustrated in Fig. 1. Specifically, an ordinary or conventional telephone instrument 2 communicates with a telephone server 6 through a switched telephone network 4. The telephone server includes software to perform various telephone server applications, such as answering calls, providing voice prompts and responding to touch tone responses as described below. In addition, the telephone server records audio information and stores the information in a telephony native format. A database/file server 8 is in communication with telephone server 6 and a web/audio server 10. Servers 6, 8, 10 may reside at the same or different remote sites, and may communicate via any desired communications medium. Database/file server 8 includes software to perform database and file server applications, and generally stores user information and organizes audio files containing the audio information received from telephone server 6. The web/audio server is connected to Internet 12 and includes software to perform web and audio server applications. This server typically handles user registration and playback of web-page audio messages to end-users 14. It is to be understood that the term "end-user" as used herein refers to an individual user and/or the computer or other processing system utilized by the user to perform the described functions (e.g., accessing a web site, clicking on an icon or button, etc.). The end-user computer system may be implemented by any computer system, such as a personal computer (e.g., IBM compatible, Macintosh, Linux, etc.), including the proper components (e.g., memory, processor, modem, network interface card, browser, streaming audio player (e.g., stand alone or plug-in Real Audio or Windows Media Player) and other software, etc.) and configuration for communicating over the particular communications medium. The system may provide audio service to individual users maintaining their own web- site, or to affiliate web-page or other service providers. The individual users register directly with web/audio server 10 in order to obtain access to system services as described below. Affiliate providers typically perform various services, such as creating and maintaining web sites for customers or interested users for various purposes. An exemplary affiliate may be a dating service having an Internet web site providing web-pages associated with individuals with each individual utilizing the system to place an audio message on his/her web-page. An interested user may request the affiliate to provide audio service, and subsequently enters registration information into an affiliate server 9 hosting the affiliate web site. The affiliate server communicates with web/audio server 10 to register the interested user with the system in a manner similar to that described above for an individual user. The system may further be utilized to provide audio messages for e-mail, e-commerce or any other applications. In addition, the system may provide audio service through any third party or affiliate service provider. A registered user places an audio message on a web-page by accessing telephone server 6 via telephone 2, dialing numbers on telephone 2 that serve as an access code, a personal identification number (PIN) and a button number (e.g., to associate the audio message with a particular web-page button), and communicating the audio message over the telephone to the telephone server as described below. The telephone server retrieves information from the user, records the message and forwards the information and audio message to database/file server 8 for storage. End-users 14 subsequently accessing the web- page through the Internet are able to listen to the recorded message by clicking on a web- page button that causes web/audio server 10 to retrieve the audio message from the database/file server and play the message back to the end-users. A further detailed view of the connection from switched telephone network 4 to Internet 12 with emphasis on the hardware and data transport mechanisms is illustrated in Fig. 2. Specifically, a connection 16 is provided from switched telephone network 4 to a Tl interface card 18 (e.g., Tl is a conventional type of communications line) that is in communication with telephone server 6. The interface card is typically implemented by a standard voice Tl card having standard protocol voice encoding (e.g., "bz8f) and a full twenty- four (24) channels. One example of a twenty- four (24) channel Tl card suitable for use in the present invention is the Tl card manufactured by the Linkon Corporation (e.g., commonly referred to as Teravox), whereby the card further serves as an extended SBUS (e.g., serial bus) attached to telephone server 6. The Tl card provides a connection to the switched telephone network and preferably includes eight Digital Signal Processors ("DSPs") that process and convert analog voice data into digital data. The digitizing is accomplished using a standard ulaw (e.g., a conventional type of file or data format) technique. Alternatively, the interface card may be of any quantity, and may be implemented by any suitable communications device capable of accommodating any quantity (e.g., at least one) of channels, having any quantity of DSPs, employing any conventional or other encoding techniques and being compatible with any type of communications line. Web/ Audio server 10 is connected to an OC12 Internet backbone 20 (e.g., a conventional communications device having high bandwidth capabilities) that is maintained by a co-location facility (OCF). The internal software hierarchy and relationship between components of the system servers is illustrated in Figs. 3A - 3D. Initially, the servers are each preferably implemented by a computer system manufactured by Sun Microsystems, such as a Sparc or other Unix system, however, any computer or other processing system capable of performing the described functions may be utilized. Referring to Fig. 3 A, an operating system (OS) 22, such as Sun Solaris, Windows, etc., provides the foundation and support for every layer of telephone server 6. A Transport Control Protocol/ Internet Protocol ("TCP/IP") 24 provides the transport layer (e.g., a layer that coordinates communications in accordance with a communications standard) for all the processes and applications within telephone server 6, while Open Database Connectivity (ODBC) 24 serves as an application programming interface for accessing a database residing on database/file server 8. The TCP/IP and ODBC functions may be implemented by any commercially available or custom software capable of enabling the telephone server to communicate over the Internet or other communications medium and access the database. Telephony board software module 26 is preferably implemented by commercially available software provided with the Tl interface card. This software enables the card to control the telephone line (e.g., answer incoming calls and release the line), provide voice prompts and interpret touch tone responses, and record audio messages in a format native to the telephony equipment (e.g., interface card 18). Software module 26 basically facilitates interaction with a caller and provides caller response information to an audio management software module 28. A Real Audio Encoder 30 converts the audio file into a Real Audio format as described below for playback of the message across the Internet, while Network File System (NFS) 32 facilitates file transfers between the servers. The Real Audio Encoder and NFS may be implemented by any commercially available or custom software. Audio management software module 28 creates and manages user audio and provides interfaces for communication between telephony (e.g., interface card 18), database and audio mass storage (e.g., database/file server). The software module is generally platform independent and modular, and may communicate with a variety of telephony equipment, databases and file storage systems. Software module 28 generally includes a plurality of instances of substantially the same program with each program instance monitoring a particular channel of interface card 18. It is to be understood that software module 28 may be utilized independent of the present invention system. Audio management software module 28 receives information from telephony board software module 26 and facilitates processing of caller requests as illustrated in Fig. 3B. Specifically, software module 28 presents a greeting message to a caller at step 80 in response to the telephony hardware (e.g., interface card 18) answering an incoming call. The message is typically pre-recorded and stored in telephony hardware memory. A connection is established to database/file server 8 to access user information, while the caller is prompted for an access code (e.g., preferably ten digits) at step 82. Software module 28 verifies the format of the access code (e.g., correct quantity of digits, no illegal prefixes, etc.) to reduce overhead at the network and database levels. The caller is prompted to re-enter the code when the entered format is unacceptable. If the caller does not provide a valid format after several opportunities, an error phrase is played and the call is disconnected. The corresponding program instance subsequently resumes listening for the next call. Once an acceptably formatted code is entered, a SQL database request is sent to the database/file server, via TCP/IP and ODBC 24 or a local shared memory, to verify the user access code (e.g., to retrieve user information based on the entered access code) at step 84. If the entered code is not valid, the caller is prompted to re-enter a code. When the caller has failed to enter a valid access code within several attempts as determined at step 86, the call is disconnected. Upon entry of a valid access code and retrieval of user information (e.g., unique user identification, PIN, etc.), software module 28 prompts the caller to enter a PIN (e.g., preferably four digits) at step 88. The entered PIN format is verified as described above, and compared to the PIN retrieved from database/file server 8 at step 92. If the entered PIN is not valid, the caller is prompted to re-enter a PIN. When the caller has failed to enter a valid PIN within several attempts as determined at step 94, the call is disconnected. After verifying the caller, software module 28 retrieves the total quantity of audio buttons associated with the caller (e.g., the total number of audio messages on caller web- pages) from database/file server 8 at step 96 via a SQL request. A user may have one or more messages associated with one or more web-pages, and the system generally does not limit the quantity of messages. The caller is further prompted to enter a particular button number that will be utilized to retrieve the message at step 98, and software module 28 verifies the entered button number against the retrieved information. If an invalid button number is entered, the caller is prompted to re-enter a button number with the call being terminated when the caller fails to provide a valid number within several attempts. Once a valid button number is entered, the caller is prompted to select a particular action at step 98. The options typically include: 1) play the recording for the button; 2) record audio for this button; 3) select another button; or 4) exit and disconnect. In response to selecting "play recording" as determined at step 100, software module 28 loads a telephony native audio file containing the audio message into the interface card memory and plays back the message at step 102. This file has a format native to the telephony system utilized (e.g., interface card 18), and is typically stored on and retrieved from database/file server 8. The database/file server generally stores the audio message in the telephony native format and a button destination format (e.g., Real Audio) enabling playback to an end-user. The dual storage enables immediate loading of an audio file into the telephony system without performing a conversion. After play back of the message, the caller is prompted to enter a button number and select an action at step 98 as described above. When the caller selects "record a message" as determined at step 104, software module 28 loads the received audio message into the interface card memory at step 106 and records the message in the telephony native format at step 108. The caller may re-record the message as many times as desired. The entered message is recorded without format conversion, thereby enabling virtually immediate recordings. After recording the message, the caller is prompted to enter a button number and select an action at step 98 as described above. If "another button" is selected by the caller as determined at step 110, software module 28 determines at step 112 whether or not the current button audio has changed. In response to a button audio change (e.g., as indicated by a byte count change within the telephony native file), software module 28 converts the audio content of the telephony native file to a button destination format (e.g., Real Audio) via Real Audio Encoder 30 and stores the converted file in database/file server 8. In addition, the new telephony native file is stored in database/file server 8 at step 116 as described above. In order to convert the telephony native file to the button destination file, the native file is first converted to a conversion audio file format (e.g., Unix file), and subsequently transformed to the button destination file. Upon completion of audio file storage, or if the button audio has not changed, the caller is prompted to enter a button number and select an action at step 98 as described above. In response to the caller selecting "exit" as determined at step 118, software module 28 determines whether or not the current button audio has changed at step 118, and, in response to a change, converts and stores the audio file in database/file server 8 at step 120 as described above. In addition, the new telephony native file is stored in the database/file server at step 122 as described above. Upon completion of the audio file storage, or if the button audio has not changed, the call is terminated and software module 28 monitors the channel for the next call. It is to be understood that software module 28 utilizes telephony board software module 26 (e.g., and hence interface card 18), Real Audio Encoder 30 and NFS 32 to perform the above-described functions (e.g., play voice prompts, receive entered user information, record messages, convert audio files, transfer files, etc.). The audio files on database/file server 8 are generally arranged in a manner for efficient management that is based on user information. In particular, when a caller enters an access code and PIN, the unique user identification associated with the caller is retrieved from the database/file server to provide software module 28 with the information to create or modify native, conversion and button destination audio files. These audio files are stored and managed within a directory/folder hierarchy determined by the user identification. By way of example, the last four digits of a user identification (e.g., preferably eight digits) are reversed in order and utilized to create or locate a path to the audio files for a caller. For example, if a user identification is ' 12345678', an audio file storage area path for that user would be 8/7/6/5/12345678. Since the total quantity of folders is generally limited to ten, the top level structure may be spread across several devices to improve performance and reliability. In addition, software module 28 may determine usage by individual number dialed. In particular, software module 28 may request the dialed number from a common DNIS (Dialed Number Identification System), and record the caller, line owner and time off-hook for each call. This permits allocation of bandwidth (e.g., telephony channels) on an as needed basis (e.g., without assigning specific channel ranges to individual line owners). Software module 28 may be implemented in any suitable computer language. Database/file server 8 (Fig. 3C) includes OS 22, TCP/IP and ODBC 24 and NFS 32 as described above. The database/file server further includes database 34, preferably implemented by an Informix database, to maintain (e.g., stores and updates) user information and generate user identifications as described below. Web/ Audio server 10 (Fig. 3D) similarly includes OS 22, TCP/IP and ODBC 24 and NFS 32 as described above. Further, the web/audio server includes commercially available Apache Web Server, PHP and Real Server software 36 to accommodate end-user audio and registration requests received from the Internet as described below. The web/audio server is preferably implemented by a pair of computer systems to provide redundancy for enhanced reliability (e.g., one system is available when the other becomes inoperative). The servers may include any communications device or any commercially available or custom software that enables the servers to perform the above-described functions. It is to be understood that these functions may be distributed among any quantity of computer systems in any fashion. The manner in which the present invention stores and retrieves audio messages for web sites is illustrated in Fig. 4A. Specifically, a user initially registers with web/audio server 10 (Fig. 1) or via affiliate server 9 at step 40 to obtain audio service. The user provides an e-mail address, an access code, and a personal identification number (PIN). The e-mail address enables the system to identify the user when the user logs in over the Internet. The access code, preferably ten digits, allows the system to identify the user over the telephone, while the PIN, preferably four digits, is utilized to verify the user. When the user registers on web/audio server 10, the registration is preferably accomplished via a PHP form with the information being sent to database/file server 8. A user may alternatively register via affiliate server 9 as described above with the user information being transferred from the affiliate server to web/audio server 10 to complete registration. Once the user information is obtained and transferred to database/file server 8, a user identification is generated and database 34 (Fig. 3C) is updated at step 42. The user identification is preferably an eight digit number that is used by the system to uniquely identify a user. The user identification is typically generated sequentially with each new registrant receiving the next available number. Upon an individual user completing the registration process with web/audio server 10, HTML code is sent via e-mail from the web/audio server to the individual user at step 44. The user incorporates the HTML code into his/her web site via an HTML editor (e.g., FrontPage, Web Express, Geocities or any other commercially available or other editor). The HTML code places one or more buttons on the web-page, each associated with a different audio message, and includes a query to database 34 to access the audio messages and other information corresponding to the buttons. For example, the date and time an audio message was created and/or modified may be retrieved from the database and displayed on the web- page. Exemplary HTML code generated by the system for a web site is illustrated in Fig. 4B, and includes standard HTML 3.0 code as outlined in the following publications: Berners-Lee and Connolly, "Hypertext Markup Language - 2.0", RFC 1866, MIT/W3C, November 3, 1995; Nebel and Masinter, "Form-based File Upload in HTML", RFC 1867, Xerox Corporation, November 7, 1995; and Berners-Lee et al, "Hypertext Transfer Protocol « HTTP/1.0", RFC 1945, MIT/LCS, May 17, 1996. Each of these publications is incorporated herein by reference in their entireties. Alternatively, when the user registers with an affiliate, the database/file server provides the generated user identification and button number to the affiliate, via web/audio server 10, to enable the affiliate to modify the user web page at step 44. The web-page may display the date and time an audio message was created and/or modified as described above. Thus, the incorporation of HTML code or updating of the web-page is transparent to the user when an affiliate is utilized. In order to create an audio message, a newly registered user accesses the system at step 46 by placing a call from a telephone over the switched telephone network to the telephone server. A telephone to computer software interface device or Tl card 18 (Fig. 2, e.g., the Teravox described above) interfaces the twenty-four (24) channels of the telephone server's Tl line to receive incoming telephone calls from the users. When a telephone call is received and the ring tone is detected, the telephone server, via Tl card 18, answers the call and provides a greeting message as described above. The caller is prompted for an access code and PIN, and subsequently enters his/her access code and PIN at step 48 as described above. The entered access code and PIN are retrieved by the telephone server, while user information is retrieved from the database/file server for verification at step 50 as described above. If the access code or PIN is invalid, the caller is prompted to re-enter a valid access code or PIN at step 48 as described above. In response to a valid access code and PIN at step 50, the caller enters the button number to be associated with the message at step 52 and upon selection of the proper action, is provided with a message prompting him her to record a message as described above. The user enters the audio message at step 54, while the message is processed in real time by the DSPs of Tl card 18 and associated software (e.g., telephony board software module 26, audio management software module 28, etc.) as described above. In particular, the entered audio message is digitized and formatted from a telephony native format into a Unix format for conversion to Real Audio (e.g., a conventional type of file or data format) at step 56, while the native and real audio files are transferred to database/file server 8 for storage as described above. Once an audio message has been recorded, the registered user may subsequently change the message by accessing the telephone server (e.g., step 46), entering the assigned access code and PIN (e.g., step 48), and entering a new or changed message (e.g., step 54), while the entered message is digitized and converted into Real Audio format (e.g., step 56) and transferred to the database/file server for storage in substantially the same manner described above. An end-user may retrieve the audio message as illustrated in Fig. 4C. Specifically, an end-user subsequently visiting a web-page clicks on an audio button at step 60. The web/audio server receives an audio request from a web server hosting the web-page and transfers information to the database/file server for processing. Basically, the web-page HTML code includes a database query containing the user identification and button number. The query is transferred to web/audio server 10 (Fig. 1) and forwarded to database/file server 8. The query provides information to uniquely identify the appropriate audio file corresponding to the selected button. The database/file server retrieves the corresponding audio file and transfers the audio file in Real Audio format to the web/audio server at step 62. The database/file server may further track usage statistics, the amount of times a button is selected, and which users are communicating or, in other words, the buttons users access, to determine communities or specified groups for marketing purposes. The web/audio server subsequently transfers the audio file to the end-user audio player for playback to the end-user at step 64. It will be appreciated that the embodiments described above and illustrated in the drawings represent only a few of the many ways of implementing a web-page audio message system and method. The servers may be implemented by any quantity (e.g., at least one) of any types of computer or other processing systems capable of supporting the above-described software and performing the above-described functions. The various server functions may be distributed among any quantity of computer systems in any fashion. The end-user systems may be implemented by any computer or other processing system (e.g., IBM-compatible or Macintosh PC, laptop, PDA, Linux, etc.) capable of executing a browser and/or performing communications functions. The web sites may reside on any of the servers or any other server or computer system interfacing the Internet or communications medium. The servers may reside in the same or different locations. The database may be implemented by any type of commercially available or other databases. The database/file server or any other server may track any type of information relating to a user or user transactions. The communications medium may be implemented by a local (LAN) or wide area (WAN) network, the Internet, direct connection (e.g., via modem) or any other commumcations path, while the communications devices (e.g., Tl card, modems or other devices in the end-user systems, etc.) may be implemented by any suitable devices (e.g., standalone or included within the telephone server or other device) enabling communication over the communications path. The Tl card may be implemented by any communications device having any quantity of channels and DSPs or other signal processing devices, and accommodating any type of line. The telephone may be implemented by any telephone or other device capable of communicating with the telephone server and providing audio information (e.g., modem in combination with a microphone, cellular telephone, etc.). The encoding/decoding and digitization may be implemented by any conventional or other techniques. The audio may be contained within and/or converted to any desired file types or formats (e.g., Real Audio, native telephony format, Unix, .au file, .wav file, etc.). The servers and end-user computer systems of the present invention may include any conventional or custom software or applications capable of controlling the computer systems to perform the above-described functions where the software may be implemented in any suitable computer languages. The software and/or algorithms within the present invention may be modified in any fashion while still achieving the general functions described above. It is to be understood that descriptions herein of software performing functions refers to computer systems or devices performing those functions under software control. The access code, PIN and user identification may have any quantity of alphanumeric or other characters to identify a user. Any types or quantities of codes or other information may be utilized to identify and/or verify a user (e.g., access code, PIN and user identification may be used individually or in any combination). The user identification may be generated by any of the servers in any fashion producing a unique identification. A user may have any quantity of buttons or audio messages on a web-page. The button may have any shape, size or appearance, and may be implemented by a link, button, icon or any other functional symbol. The buttons may be identified by any quantity of alphanumeric or other characters. It is to be understood that the present invention pertains to any computer or other processing system capable of receiving audio information from a user via a conventional telephone or other communications device, and readily providing access and playback of the audio information from a web-page. The present invention is not limited to the specific applications disclosed herein, but may be utilized to provide audio for any types of applications (e.g., e-mail, e-commerce, pagers, portable telephones, etc.). Further, any type of affiliate or third party provider may utilize the system to provide audio service to customers or interested users. From the foregoing description, it will be appreciated that the invention makes available a novel web-page audio message system and method wherein audio messages on a web-page may be created and modified via a conventional telephone. Having described preferred embodiments of a new and improved web-page audio message system and method, it is believed that other modifications, variations and changes will be suggested to these skilled in the art in view of the teachings set forth herein. It is therefore to be understood that all such variations, modifications and changes are believed to fall within the scope of the present invention as defined by the appended claims.

Claims

What is Claimed is:

1. An audio publishing system to provide audio information at a site within a communications network, wherein said audio information is manipulable by a user via access to said system by a telephone line, said system comprising: registration means for retrieving and storing user information to enable said system to identify said user; communications means for receiving and terminating calls on said telephone line and prompting for and interpreting a caller request; audio processing means for storing audio information received from said caller within an audio file and processing said audio file in response to said caller request; a database to store said user information and retrieval information relating to said audio file; a file system for storing said audio file received from said audio processing means based on said retrieval information; and network audio means for receiving an audio request from said network site and retrieving a corresponding audio file based on said retrieval information for transmission to said network site for playback.

2. The system of claim 1 wherein said database includes monitor means for collecting and storing information relating to system usage.

3. The system of claim 1 wherein said audio processing means includes: verification means for prompting said caller to enter verification information and comparing said entered information to said user information stored in said database to verify that said caller is registered with said system; record means for recording said audio information in the form of voice signals received from said caller within said audio file in response to a caller record request; playback means for retrieving said audio file and playing said audio file back to said caller in response to a caller playback request; storing means for storing said audio file within said file system in response to an audio file modification and a caller request to either process additional audio information or exit; and conversion means for converting said audio file to a format compatible for playback over said network and storing said formatted file within said file system in response to an audio file modification and a caller request to either process additional audio information or exit.

4. The system of claim 1 further including: affiliate registration means for retrieving information from said user and transmitting said retrieved information via said communications network to said registration means to register said user with said system.

5. The system of claim 1 wherein said audio information is associated with a plurality of audio messages and said audio processing means includes: association means for prompting said caller for a message identification and associating said audio information with said message corresponding to said message identification; message record means for storing said associated audio information for said identified message in a corresponding audio file in response to a caller record request; and audio playback means for retrieving and playing back said corresponding audio file in response to a caller playback request for said identified message.

6. The system of claim 1 wherein said network audio means includes audio file monitor means for retrieving modification information relating to a date and time of audio file modification from said database and transferring said modification information via said communications network to said network site for display.

7. A program product apparatus having a computer readable medium with computer program logic recorded thereon for facilitating user manipulation of audio information for a site on a communications network, said user manipulating said audio information via access by a telephone line, said program product apparatus comprising: communications means for receiving and terminating calls on said telephone line and prompting for and interpreting a caller request; verification means for prompting said caller to enter verification information and comparing said entered information to user information stored in a database to verify that said caller is a registered user; record means for recording said audio information in the form of voice signals received from said caller within an audio file in response to a caller record request; playback means for retrieving said audio file and playing said audio file back to said caller in response to a caller playback request; storing means for storing said audio file within a file system in response to an audio file modification and a caller request to either process additional audio information or exit; and conversion means for converting said audio file to a format compatible for playback over said network and storing said formatted file within said file system in response to an audio file modification and a caller request to either process additional audio information or exit.

8. The program product apparatus of claim 7 wherein: said audio information is associated with a plurality of audio messages; said verification means includes association means for prompting said caller for a message identification and associating said audio information with said message corresponding to said message identification; said record means includes message record means for storing said associated audio information for said identified message in a corresponding audio file in response to a caller record request for said identified message; and said playback means includes audio playback means for retrieving and playing back said corresponding audio file in response to a caller playback request for said identified message.

9. In an audio publishing system, a method to provide audio information at a site within a commumcations network, wherein said audio information is manipulable by a user via access to said system by a telephone line, said method comprising the steps of: (a) retrieving and storing user information to enable said system to identify said user; (b) receiving and terminating calls on said telephone line and prompting for and interpreting a caller request; (c) storing audio infoimation received from said caller within an audio file and processing said audio file in response to said caller request; (d) storing said user information and retrieval information relating to said audio file within a database; (e) storing said audio file within a file system based on said retrieval information; and (f) receiving an audio request from said network site and retrieving a corresponding audio file based on said retrieval information for transmission to said network site for playback.

10. The method of claim 9 wherein step (d) further includes: (d.1) collecting and storing information relating to system usage.

11. The method of claim 9 wherein step (c) further includes: (c.l) prompting said caller to enter verification information and comparing said entered information to said user information stored in said database to verify that said caller is registered with said system; (c.2) recording said audio information in the form of voice signals received from said caller within said audio file in response to a caller record request; (c.3) retrieving said audio file and playing said audio file back to said caller in response to a caller playback request; (c.4) storing said audio file within said file system in response to an audio file modification and a caller request to either process additional audio information or exit; and (c.5) converting said audio file to a format compatible for playback over said network and storing said formatted file within said file system in response to an audio file modification and a caller request to either process additional audio information or exit.

12. The method of claim 9 wherein step (a) further includes: (a.l) retrieving information from said user at a network site and transmitting said retrieved information via said communications network to said system to register said user with said system.

13. The method of claim 9 wherein said audio information is associated with a plurality of audio messages and step (c) further includes: (c.l) prompting said caller for a message identification and associating said audio information with said message corresponding to said message identification; (c.2) storing said associated audio information for said identified message in a corresponding audio file in response to a caller record request for said identified message; and (c.3) retrieving and playing back said corresponding audio file in response to a caller playback request for said identified message.

14. The method of claim 9 wherein step (f) further includes: (f.l) retrieving modification information relating to a date and time of audio file modification from said database and transferring said modification information via said communications network to said network site for display.

15. A method of facilitating user manipulation of audio information for a site on a communications network, said user manipulating said audio information via access by a telephone line, said method comprising the steps of: (a) receiving and terminating calls on said telephone line and prompting for and interpreting a caller request; (b) prompting said caller to enter verification information and comparing said entered information to user information stored in a database to verify that said caller is a registered user; (c) recording said audio information in the form of voice signals received from said caller within an audio file in response to a caller record request; (d) retrieving said audio file and playing said audio file back to said caller in response to a caller playback request; (e) storing said audio file within a file system in response to an audio file modification and a caller request to either process additional audio information or exit; and (f) converting said audio file to a format compatible for playback over said network and storing said formatted file within said file system in response to an audio file modification and a caller request to either process additional audio information or exit.

16. The method of claim 15 wherein said audio information is associated with a plurality of audio messages, and step (b) further includes: (b.l) prompting said caller for a message identification and associating said audio information with said message corresponding to said message identification; step (c) further includes: (c.l) storing said associated audio information for said identified message in a corresponding audio file in response to a caller record request for said identified message; and step (d) further includes: (d.l) retrieving and playing back said corresponding audio file in response to a caller playback request for said identified message.