Animated audio messaging

[0001] The invention relates to telecommunications and more particularly to messaging using audio messages and animated video images.

[0002] Telecommunications are increasing rapidly both in amount and variety. Fairly recent technological advances in telecommunications include cellular phones and other mobile phones, and e-mail. It has been estimated that e-mail already outnumbers traditional mail by over 10 to 1, and this ratio is expected to increase. E-mail can be transmitted through hard-wired computers, but also through wire digital assistants (PDAs). Mobile communication devices can also enable “instant messaging” between parties. With people more and more mobile, they communicate more and more using mobile communication devices instead of, e.g., hardwired phones.

[0003] With mobile communications increasing, people want more functionality from their mobile communication devices. Despite this, people also want to have mobile communications devices that are smaller because they do not want to carry bulky, heavy devices, and because people are tending to carry more such devices, e.g., pagers, mobile phones, PDAs, and wireless e-mail devices. They also want their devices to be faster, because time is often at a premium, and cheaper. More functionality, however, is often in direct conflict with smaller, lighter, faster, cheaper devices because more, and more complicated, functions require more memory and processing power. This translates into bigger, more expensive, devices.

[0004] The invention provides techniques to enable persons to provide animated audio messages to desired recipients. Animated audio messages may be, e.g., audio messages accompanied by an image that moves in concert with the audio message. Playing the animated audio message to the recipient simulates, e.g., the sender of the message, speaking the message. Alternatively, images other than the sender may be used. The image may be a standard image stored in an animation message system (AMS), or may be uploaded/downloaded to the AMS, e.g., by the animated message sender. An audio message may be stored in a voice-mail system before or after selection of the image(s) to accompany the audio message.

[0005] In general, in an aspect, the invention provides a method for providing an animated audio message. The method includes wirelessly receiving indicia of an audio message and an image, and animating the image in association with the audio message to produce an animated audio message.

[0006] Implementations of the invention may include one or more of the following features. The image can be stored and identified by the indication of the image. The animated audio message can be stored and information for retrieving the animated audio message can be sent toward an intended recipient of the animated audio message. The animated audio message can be stored corresponding to a web address. The web address can be of a web page supported by an animation message system. The information for retrieving the animated audio message can be supplied in a format that is indicated by a wireless communication. This format can be, e.g., e-mail or mobile-terminated short message service format. The audio message can be stored in and received from a voice-mail system. The indicia of the audio message and the image can be received in one wireless communication, or multiple wireless communications. Indicia of the audio message can be text that is converted to the audio message, or information identifying an audio message.

[0007] In general, in another aspect, the invention provides a method for providing an animated audio message as selected in a wireless communication. The method includes receiving indicia of an animated audio message and a recipient. The animated audio message includes an image that changes corresponding to audio of the message. At least some of the indicia of the animated audio message is received through a wireless communication. Information is sent toward the recipient for the recipient to be able to view and listen to the message.

[0008] Implementations of the invention may include one or more of the following features. The information sent toward the recipient may be a URL of a web site. The audio of the message may be received from a voice-mail system. The image may be one of multiple stored images that is selected according to the received indicia.

[0009] In general, in another aspect, the invention provides a computer program product including computer-executable instructions. The instructions are set up for causing a computer to wirelessly receive an audio-message indication, to wirelessly receive an image indication, to associate the image with the audio message, and to animate the image according to the audio message to produce an animated audio message.

[0010] Implementations of the invention may include one or more of the following features. Information for retrieving the animated audio message may be sent toward an intended recipient of the animated audio message. The animated audio message may be stored in association with a web page or other packet-switched-network site. The information for retrieving the animated audio message may include an address of the web page or other site. The information can be formatted in a format indicated wirelessly, and the format may be, e.g., e-mail or mobile-terminated short message service format.

[0011] In general, in another aspect, the invention provides a system for providing animated audio messages. The system includes a wireless interface that can receive wireless communications that provide or identify an audio message and provide or identify an image. An animator is coupled to the wireless interface and can animate the image in accordance with the audio message to form an animated audio message. An animation interface is coupled to the animator and can transfer the animated audio message from the animator toward a desired destination.

[0012] Implementations of the invention may include one or more of the following features. The animation interface can transfer the animated audio message toward the desired destination in a wireless communication. Audio and image engines can convert the audio message and image to appropriate formats. Storage devices can store the audio message and the image. A streaming server can transfer the animated audio message as a streaming file. A web server can provide access to the animated audio message via a web page. Interfaces can provide an address of the web page in a mobile-terminated short message service or e-mail format.

[0013] Various aspects of the invention may provide one or more of the following advantages. Mobile-communication device users can produce and send animated audio messages. Mobile-communication device users can produce and send personalized animated audio messages, such as electronic greeting cards. Mobile-communication device users can view and listen to animated audio messages. Animated audio messages can be produced, sent, and played using devices, including mobile communication devices, without requiring specialized equipment in the device for playing the messages.

[0014] These and other advantages of the invention, along with the invention itself, will be more fully understood after a review of the following figures, detailed description, and claims.

[0019] Referring to FIG. 1, a communication system 10 includes a mobile communication device (MCD), here a portable phone 12, a personal digital assistant (PDA) 14, a computer 16, and a hard-wired telephone 18, connected through a mobile circuit/data network 20, the global packet-switched network known as the Internet 22, a public-switched telephone network (PSTN) 24, and a router/WAP gateway 26, respectively as shown, to an animation message system (AMS) 28, a short message center (SMC) 30, and a voice-mail system 32. The networks 20, 22, 24 and the router/gateway 26 provide for bi-directional communication between the phones 12, 18, the PDA 14, and the computer 16, and the AMS 28, the SMC 30, and the voice-mail system 32. The Internet 22 and the PSTN 24 are well-known networks, and the mobile circuits/data network 20 provides an interface between hard-wired and wireless communications, e.g., a cellular network.

[0020] The telephones 12, 18 are configured to communicate bi-directionally with the voice-mail system 32. For example, the mobile phone 12 can com network 20, that communicates with the voice-mail system 32. Thus, through the network 20, the mobile phone 12 can, e.g., transmit voice or other audio messages for storage in the voice-mail system 32. Likewise, the hard-wired telephone 18 can transmit voice or other audio messages through the PSTN 24 for storage in the voice-mail system 32. The phones 12, 18 can also receive audible messages from the voice-mail system 32 to allow/promote interaction with the system 32, e.g., by receiving and responding to directions from the voice-mail system 32.

[0021] The mobile phone 12 is also configured to communicate with the AMS 28. The phone 12 communicates with the AMS 28 through the mobile circuits/data network 20 and the router/WAP gateway 26. The phone 12 is configured to communicate with the AMS 28 such that a user of the phone 12 can log in to a website of the AMS 28 and provide information to select an image that is stored in the AMS 28, and to associate that image with an audio message stored in the voice-mail system 32. Communications between the router/WAP gateway 26 and the AMS 28, for communications involving the phone 12, are processed in accordance with the wireless application protocol (WAP). The phone 12 is also configured to receive communications from the AMS 28 in order to facilitate selection of the image and association of a desired audio message.

[0022] The devices 12, 14, 16 are configured to receive communications from the AMS 28 and/or the SMC 30 in mobile terminated short-message service (MT-SMS) format or e-mail format, as appropriate. The phone 12 can receive MT-SMS messages from the SMC 30 via the network 20. Each of the devices 12, 14, 16 are configured to receive digital data as e-mail-formatted messages from the AMS 28.

[0023] Each of the devices 12, 14, 16 are further configured to access a web page stored in the AMS 28. The devices 12 and 14 are configured to communicate with the AMS 28 through the router/WAP gateway 26 and the network 20 to access a web page of the AMS 28 and to download information, e.g., an animated audio message, from the web page of the AMS 28. An animated audio message can be, e.g., an electronic, or virtual, greeting card. The computer 16 is configured to communicate, e.g., in Hyper Text Transfer Protocol (HTTP) or Simple Mail Transfer Protocol (SMTP) as appropriate to access a desired web page stored in the AMS 28 and to download data from that web page. The devices 12, 14, 16 are further configured to play animated audio messages (e.g., by audibly broadcasting an audio portion of the message and by visually displaying an image portion of the message).

[0024] The voice-mail system 32 is a standard voice-mail system modified to provide audio messages to the AMS 28. The voice-mail system 32 provides standard voice-mail features for receiving and storing audio messages from the phones 12, 18 via the networks 20, 24. Additionally, the voice-mail system 32 is configured to provide audio messages to the AMS 28 when instructed to do so. For example, the voice-mail system 32 is configured to receive an audio message for storage from the phones 12, 18, and to provide an option for a user of the phone 12 or 18 to provide an indication that the audio message (e.g., voice-mail) is to be associated with an image by the AMS 28. For example, the voice-mail system 32 may prompt a user that has provided an audio message for storage to press a certain button on a keypad of the phone 12 or 18 to indicate that the audio message is to be associated with an image. The user may further be prompted to enter other information to help identify the audio message so that the audio message can be associated with a desired image. The voice-mail system 32 is configured to provide audio messages, either in real-time or stored audio messages, to the AMS 28, and to otherwise communicate with the AMS 28 using Voice Profile for Internet Mail (VPIM) or Audio Message Interchange Service digital (AMISD) formats as appropriate. The voice-mail system 32 can send the recorded message along with other identifying information, such as information regarding the sender and/or the recipient, to the AMS 28.

[0025] The SMC 30 is a known system for providing Short Message Service (SMS) messages to wireless devices via a wireless network, to receive such messages from wireless devices through a wireless network, and to communicate with other devices, here the AMS 28, as appropriate. The SMC 30 can communicate bi-directionally with the AMS 28 using a Short Message Peer-to-Peer (SMPP) protocol. The SMC 30 can receive data in the SMPP protocol from the AMS 28, and in response thereto provide Mobile-Terminated-SMS (MT-SMS) messages through the network 20 to wireless devices such as the mobile phone 12 or the PDA 14. Also, the SMC 30 is configured to receive SMS messages via the network 20 from the phone 12 and the PDA 14, and to provide appropriate data in the SMPP protocol to the AMS 28. For example, the SMC 30 can provide indicia of a Universal Resource Locator (URL), corresponding to a web page of the AMS 28, to the devices 12, 14, to receive URL indications from the devices 12, 14, and to provide corresponding indicia to the AMS 28 to access a web page corresponding to an indicated URL. The AMS 28 is a server configured to process audio messages from the voice-mail system 32 with video images stored in the AMS 28 into animated audio messages.

[0026] Referring to FIG. 2, the AMS 28 includes a processor 34 coupled for bi-directional communication with a memory 36. The processor 34 is configured to execute instructions stored in the memory 36 to perform various operations in accordance with the descriptions of functions provided above and below. The memory 36 is configured to store instructions that are executable by the processor 34. For example, the memory 36 can be Random Access Memory (RAM), Read-Only Memory (ROM), or hard or floppy discs, or combinations of any of these, and/or any other types of memory for storing such instructions. The stored instructions form software code that is executable by the processor 34 to carry out the functions described above and below.

[0027] Referring to FIG. 3, with further reference to FIG. 1, a software architecture 38 of the AMS 28 includes a streaming server 40, a web server 42, a subscriber database 44, an audio repository 46, an animation image repository 48, an animated message constructor 50, a text-to-speech engine 52, an audio format engine 54, an animation engine 56, a graphical user interface 58 with CGI scripts or servlets, a voice-mail interface 60, an MT-SMS interface 62, and an e-mail interface 64. The software architecture 38 is configured such that the AMS 28 can receive audio messages and video images, convert them to appropriate formats if needed, animate the audio message using the image, and provide the animated audio message to a desired recipient.

[0028] The Graphical User Interface (GUI) 58 includes Common Gateway Interface (CGI) scripts or servlets and is the interface that allows a user to select an animation image and an audio message. The CGI scripts or servlets are used to handle user inputs, e.g., from the web server 42. The GUI 58 can communicate with the web server 42 to receive indications from a user to perform various functions. For example, the user can provide indications to select a delivery type, to enter recipient information for an animated message, to select an audio message, to select an image, and/or to provide text to be converted to speech by the text-to-speech engine 52. Indicia from the user to select an audio message and/or an image can be, e.g., an address of a storage area of the message or image. The GUI 58 is further configured to send URLs of web pages to the MT-SMS interface 62 or to the e-mail interface 64 based upon a delivery type selected by the user. Also, the GUI 58 is configured to receive data from the animated message constructor 50 indicative of a storage location of an animated audio message.

[0029] The voice-mail interface 60 is configured to provide an interface between the voice-mail system 32 and the AMS 28, specifically the audio fo voice-mail interface 60 is configured to receive indicia from the GUI 58 as to which audio message stored in the voice-mail system 32 to use with an image to provide an animated audio message. The voice-mail system 60 is configured to communicate with the voice-mail system 32 in VPIM or AMISD protocols, or any other protocol that is defined on top of Transmission Control Protocol/Internet Protocol (TCP/IP). The interface 60 is further configured to transfer messages received from the voice-mail system 32 to the audio format engine 54.

[0030] The MT-SMS interface 62 is configured to process communications between the GUI 58 and the SMC 30. The MT-SMS interface 62 is configured to receive indicia from the GUI 58 of a URL of a web page containing an animated audio message. The interface 62 is further configured to process the URL indicia into a message in the SMPP protocol and transfer the SMPP protocol message to the SMC 30 for further transfer to an intended recipient.

[0031] The e-mail interface 64 is configured to transfer URL indicia from the GUI 58 to the internet 22. The e-mail interface 64 is configured to operate with an external e-mail server using Simple Mail Transfer Protocol (SMTP) protocol. The e-mail interface 64 receives indicia of the URL of a web page containing an animated audio message and produces an SMTP formatted e-mail message that the interface 64 sends to the Internet 22 for further transfer to an intended recipient.

[0032] The text-to-speech engine 52 is configured to convert text messages received from the GUI 58 to speech. The engine 52 is configured to receive text messages as input from the GUI 58 and convert the received text into digital audio format. The engine 52 is further configured to send the digital audio format data to the audio format engine 54. Preferably, the text-to-speech engine 52 is based on an IBM® text-to-speech engine or an MS text-to-speech engine.

[0033] The audio format engine 54 is configured to process audio messages for storage and to update the subscriber database 44. The audio format engine 54 is configured to receive audio messages in the form of digital audio files from the text-to-speech engine 52 and from the voice-mail interface 60. If the received file is not in a desired format such as MPEG4, then the engine 54 converts the audio file into a desired format, such as MPEG4. The audio format engine 54 can store the audio file, in the desired format, in the audio repository 46. Also, the audio format engine 54 can communicate with the subscriber database 44 to update a corresponding user record in the subscriber database 44. The user record is updated with user information for the voicemail message, the format of the message, and the location and file name of the message.

[0034] The animation engine 56 is configured to ensure proper format of image or picture files for storage in the animation image repository 48. The animation engine 56 receives images or picture files from the GUI 58. The engine 56 is configured to convert the received images or pictures, if necessary, into an animation format and store the files in a desired animation format in the animation image repository 48. Standard images may be stored in the animation image repository or non-standard images may be uploaded from a user through the GUI 58. The animation image 56 may be, e.g., a JAVA-based animation engine. For example, suitable animation software can be obtained from http://www.redted.com.

[0035] The subscriber database 44, the audio repository 46, and the animation image repository 48 are configured to store information and to provide information to the animated message constructor 50. The database 44 may be the Oracle 8i Enterprise Edition made by Oracle Corporation of Redwood City, Calif. The subscriber database 44 stores subscriber data, e.g., a user's log in/password and other records, and can be updated with information from the audio format engine 54. The database 44 can provide data, such as data identifying a subscriber, to the animated message constructor 50. The audio repository 46 and the animation image repository 48 respectively store the audio message file and animation image, and can provide the respective data to the animated message constructor 50.

[0036] The subscriber database 44 stores subscriber data records. These data records contain information relating to users, including user preference and access information, and data regarding system use by the user. For example, a subscriber data record may be:

[0037]

	sub_record {
	char	userid[32];
	char	password[32];
	char	user_phone_number
	int	message_cnt;
	int	total_message_cnt;
	long	last_login_time;
	int	prefer_delivery_type
	}

where userid, password, and user_phone_number are self-explanatory, message_cnt is the number of new messages, total_message_cnt is the accumulated number of messages for the user, last_login_time is self-explanatory, and prefer_delivery_type is the user's preferred notification type, MT-SMS or e-mail.

[0038] The animated message constructor 50 is configured to animate the image by processing information from the database 44, the audio repository 46, and the animation image repository 48 into a suitable streaming-media-type file. The constructor 50 receives subscriber information from the subscriber database 44 regarding the locations of the image and the audio message. The constructor 50 combines the audio message from the audio repository 46 and the animated image from the animation image repository 48. The constructor 50 animates the image in accordance with the audio message, to attempt to synchronize the image and the audio message, using appropriate software. For example, suitable animation software can be obtained from http://www.redted.com. The constructor 50 combines the audio message and animated image into an animated audio message and constructs a streaming-media-type file, of the animated audio message, for the streaming server 40 and stores this file on a disc or other memory. To do this, the constructor 50 uses the subscriber data record and message header. The constructor 50 can alternatively construct the animated audio message in real time for a recipient, with or without storing the animated audio message.

[0039] Animated audio messages include message headers produced by the constructor 50. For example, a message header may be:

[0040]

	message_header {
	char	sender[32];
	char	recipient[32];
	long	msgid;
	int	delivery_type;
	int	delivery_option;
	varchar	audio_location[256];
	varchar	image_location[256];
	varchar	streamfile_location[256];
	;

where sender, recipient, and msgid fields are self-explanatory, delivery_type and delivery_option indicate whether notification of the animated audio message will be via email or SMS, and audio_location, image_location, and streamfile_location indicate memory addresses storing the audio message, the image, and the streaming file of the animated audio message, respectively.

[0041] The web server 42 communicates with the subscriber database 44 and the streaming server 40 and is the host for an AMS IP interface to recipients such as wireless devices or a computer. The web server 42 hosts a website that allows a user of, e.g., the wireless device or computer, to select an animation image and an audio message. The web server 42 further allows the user to select the delivery type of the animated audio message and to enter recipient information for the animated audio message. By communicating with the subscriber database 44, the web server 42 can store and retrieve subscriber information into and from the subscriber database 44. The web server 42 further hosts web pages associated with the animated audio messages that can be selected by accessing appropriate URLs to retrieve the desired animated audio message for downloading the message to a recipient's device and playing the message. The web server 42 can provide indicia of how to obtain the animated audio message. The web server 42 is configured to communicate with users in HTTP/WAP protocol data packets. Preferably, the web server 42 is an Apache web server such as the Apache 1.3.19 web server made by Apache Software Foundation of Forest Hill, Md.

[0042] The streaming server 40 is configured to communicate with the web server 42 and the animated message constructor 50 and to provide streaming animated audio message files to recipients. The streaming server 40 receives streaming file requests, redirected from the web server 42, and in response gets an appropriate streaming media file from the animated message constructor 50. Animated audio messages retrieved from the animated message constructor 50 are provided in Microsoft Metadirectory Services/Real-Time Streaming Protocol (MMS/RTSP protocol) to appropriate recipients via the Internet 22 or the mobile circuits/data network 20.

[0043] In operation many processes may be followed to provide, select, and play back animated audio messages. For example, multiple processes may optionally be used if the sender is a mobile handset and the receiver is a mobile handset or PC. Multiple processes may also be employed if the sender is a mobile handset or wireless PDA or personal computer and the receiver is a mobile handset or PC. Still further options exist if the sender is a wireless PDA or personal computer and the receiver is a mobile handset or personal computer.

[0044] FIG. 4 shows a process 70 of providing an animated audio message to a mobile handset or personal computer receiver 90 using a mobile handset sender 89. Referring to FIG. 4, with further reference to FIGS. 1 and 3, a mobile handset user can provide and/or select, as appropriate, an audio message and an image, and have the audio message and the image combined into an animated audio message, and a recipient can download and play the message.

[0045] At stage 72, the user of the sending device 89 records an audio message and designates it to be associated with an image. The user logs into the voice-mail system 32, and records the user's message in typical fashion. The user designates the message as a message to be associated with an image. For example, the user may press one or more buttons on a keypad, as prompted by the voice-mail system 32, to designate the audio message as being associated, or to be associated, with an image. Here the sending device is the mobile handset 12.

[0046] At stage 74, the voice-mail system 32 forwards a recorded message to the AMS 28. The AMS 28 receives the recorded message in the voice-mail interface 60, and stores the message in the audio repository 46, with the audio format engine 54 converting the audio message to an appropriate format if necessary.

[0047] At stage 76, the user selects the audio message and the image to be associated with the audio message to form the animated audio message. The user logs into the AMS web page or website hosted by the web server 42. The user selects the audio message using the website based upon, e.g., the desired recipient's telephone number. The user may also select the audio message based on, e.g., the sender's mailbox number, the recipient's mailbox number, or an identification number that is associated with the audio message. For example, the user can make the selection by entering the appropriate information before or after recording the audio message using the voice-mail system 32. The user also selects the desired animation image. The user can select the image by uploading an image or images, that may be animation or non-animation images. For non-animation images, the animation engine 56 will convert the image into an animation image format before storing the image in the animation image repository 48. The user may also select an animation image that is stored in the repository 48 from a list of images, e.g., that are associated with the sender 89. The user may have an account that has an associated list of available animation images from which the user may select a desired image. For example, the user may be presented with small icons associated with the images in the user's account list, and the user can, e.g., click on one of the icons to select the image.

[0048] At stage 78, the user selects the notification delivery-type. Possible notification delivery types are e-mail or MT-SMS. The user can select e-mail if the recipient is, e.g., a PC or other e-mail-accessible device. The user may wish to use the MT-SMS format if the receiving device 90 is, e.g., a handset similar to the mobile handset 12. The notification delivery-type selection is made by the user via the web server 42 and the GUI 58, with the GUI 58 communicating with the MT-SMS interface 62 or the e-mail interface 64 as appropriate.

[0049] At stage 80, the AMS 28 produces a web page from which the animated audio message can be accessed. The animated message constructor 50 animates the image in accordance with the audio message and provides a streaming-media-type file to the streaming server 40. The produced web page contains both the selected animation image and the selected audio message as they are accessible via the streaming server 40.

[0050] At stage 82 the AMS 28 sends the URL of the web page produced by the AMS 28 to the SMC 30. The URL of the web page is sent to the SMC 30 from the GUI 58 via the MT-SMS interface 62 in SMPP format.

[0051] At stage 84, the SMC 30 sends the URL received in stage 82 to the recipient 90, that may be, e.g., another mobile handset similar to the handset 12, or the computer 16. SMC 30 operates in known fashion to transfer the URL as MT-SMS to the recipient 90.

[0052] At stage 86, the AMS 28 transfers the URL to the recipient 90 if the sender chose e-mail as the notification delivery type. In this case, th URL of the web page associated with the animated audio message to the recipient 90 via the e-mail interface 64.

[0053] At stage 88, the recipient 90 accesses the web page hosted by the web server 42 containing the animated audio message in the AMS 28. The recipient accesses the appropriate web page using the URL provided via e-mail or MT-SMS. With the appropriate web page accessed, the recipient 90 downloads the animated audio message and plays the animated audio message on the receiving device 90.

[0054] FIG. 5, with reference to FIGS. 1 and 3, shows another process 100 for sending an animated audio message using a mobile handset to a mobile handset or computer. Many stages of the process 100 are similar to the stages in the process 70 shown in FIG. 4.

[0055] At stage 102, the user of the handset 12 accesses the website maintained in the AMS 28. The user selects a desired animation image through the web server 42, the GUI 58, the animation engine 56, and the animation image repository 48. The user further selects the delivery type as either e-mail or MT-SMS, using the web server 42, the GUI 58, and, as appropriate, the MT-SMS interface 62 or the e-mail interface 64. The user further enters the telephone number or address, or other appropriate identifying information, of the recipient device 90 through the web server 42 and the GUI 58. This information can be used by the AMS 28 to associate the selected animation image with an audio message.

[0056] At stage 104, the user of the device 12 logs into the voice-mail system 32 to deposit an audio message. The user logs into the voice-mail system 32 and records an audio message in known fashion. The user further designates or otherwise provides information to allow the AMS 28 to associate the recorded audio message with an animation image.

[0057] Stages 106, 108, 110, 112, 114, and 116, are similar to stages 74, 80, 82, 84, 86, and 88, respectively, of process 70. These stages help produce and transfer a desired animated audio message to the user of the recipient device 90.

[0058] FIG. 6, with reference to FIGS. 1 and 3, shows a process 120 for transferring an animated audio message using a mobile handset or wireless PDA as the sending device 89 to a mobile handset or computer as the recipient device 90. In the process 120, an audio message is produced via a text message.

[0059] At stage 122, the user of the sending device 89 provides information to the AMS 28 to provide or select the audio message and animation image. The user logs into the web page hosted by the web server 42 and selects an animation image by providing information through the web server 42 to the GUI 58 that conveys the selection to the animation image repository 48. The user further provides a text message to the AMS 28. The user further provides information to select the delivery type as MT-SMS or e-mail. Also, the user submits information regarding recipient and/or recipient device 90.

[0060] At stages 124 and 126, the animated audio message is produced. The text message received from the sending device 89 is conveyed through the web server 42 to the GUI 58. The GUI 58 provides the text message to the text-to-speech engine 52, that converts the message to audio format, at stage 124, and provides the audio-format message to the audio format engine 54 for recording in the audio repository 46. At stage 126, the animated message constructor 50 constructs the animated audio message using the audio message produced from the text message, and the image selected by the user. The web server 42 produces a web page containing the animated audio message.

[0061] In stages 128, 130, 132, the recipient device 90 is notified of the web page containing the animated audio message. These stages are similar to stages 82, 84, 86 of FIG. 4.

[0062] At stage 134, the user of the recipient device 90 accesses the AMS 28 and retrieves the animated audio message. This stage is similar to stage 88 of FIG. 4.

[0063] FIG. 7 shows another process 140 for conveying an animated audio message from a mobile handset or PDA or computer as the sending device 89 to a mobile handset or computer as the recipient device 90. In the process 140, the user of the sending device 89 selects a pre-recorded audio message versus logging into the voice-mail system 32 (FIG. 1) to record an audio message.

[0064] At stage 142, the sending device user provides information to select an audio message and an animation image, as well as delivery type and recipient information. This stage is similar to stage 122 of FIG. 6. In stage 142, however, the user selects a pre-recorded audio file such as a message, music, or sound track by providing appropriate information to the AMS 28. Using the information provided at stage 142, at stage 144 the AMS 28 produces a web page containing the animated audio message.

[0065] At stages 146, 148, 150, 152, that are similar to stages 128, 130, 132, 134 of FIG. 6, the URL of the web page produced at stage 144 is provided to the user of the recipient device 90, and the recipient uses the recipient device 90 to retrieve the animated audio message. The user of the recipient device 90 retrieves the animated audio message by accessing and downloading the message from the web page of the AMS 28.

[0066] FIG. 8 shows a process 160 of transferring an animated audio message to a recipient device 90 using a sending device 89 that may be a wireless PDA or computer, and includes recording an audio message in the voice-mail system 32 using a wireline telephone. In the process 160, at stage 162, the user uses a wireline telephone to log into the voice-mail system 32 and deposit an audio message. Stages 164, 166, 168, 170, 172, 174, and 176, are similar to stages 106, 102, 108, 110, 112, 114, and 116, of FIG. 5 for providing additional information to the AMS 28 to produce a website containing an animated audio message, for providing an appropriate URL to the user of the device 90, and for retrieving and downloading the animated audio message and playing this message at the device 90.

[0067] The specific processes 70, 100, 120, 140, and 160 shown in FIGS. 4–8 are exemplary and not limiting. Stages can be added, removed, and/or rearranged without departing from the scope and spirit of the invention or the appended claims.

[0068] Other embodiments are within the scope and spirit of the appended claims. For example, due to the nature of software, functions described above can be implemented using software, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.