Patent Application
20150215750
The present invention relates to wireless messaging devices such as two-way pagers, wireless telephones and personal digital assistants (PDA's) and, electronic media systems such as, electronic mail systems, electronic commerce systems and storage and retrieval systems. More specifically, the present invention relates to two-way wireless email devices and associated systems.
An object of the invention is to provide a messaging system for selectively performing an action on information, for remote retrieval of messages, for performing action on information at different times, for selective paging, for providing a user interface for message access and having integrated audio visual messaging.
Another object of the invention is to provide a method and system for wireless retrieval of an email attachment such as an audio or video file.
Another object of the invention is to provide a system for allowing a wireless device to retrieve a portion of or an entire email from one or a plurality of email systems.
It is yet another object of the invention to provide direct access to one specific or a plurality of specific email messages without having to retrieve or access other email messages.
Another object of the invention is to provide a messaging system that delivers messages or message notifications to a specific device, based on a variable such as: the “presence” of the user (i.e., whether the user has turned on his/her device), the location of the device, the device being accessed, the importance level of the message, the type of message, the time or date, the weather, a user action, or a user request.
It is still another object of the invention to provide automatic identification of a wireless mobile phone user or wireless email device and a mobile phone user's reply email message destination by utilizing a phone number or code.
It is yet another object of the invention to provide an improved method for memory management in a messaging device.
The accompanying drawings and above identified pending patent applications, which are incorporated herein, form a part of this specification together with this description and serve to explain the principles of the invention and to enable a person skilled in the pertinent art to make and use the invention.
For the purpose of illustration only, a wireless mobile telephone will be used as an exemplary wireless messaging device. However, it should be understood that other messaging devices, such as pagers, wireless PDA's and the like, are also contemplated.
A wireless mobile telephone, hereinafter mobile phone, is configured to receive text messages and message alerts. The mobile phone may be configured to receive Short Messaging Service (SMS) email messages or the mobile phone may have a Web Browser for accessing an Internet based email service. An email server receives an email message intended for a specific mobile telephone. An email message includes a message body and a message header. The message header usually includes various fields, such as a To field, a From field, and a Subject field. The message header also may include a Message Type field and other information common in email messages.
The email server assigns a message identifier (ID) to the message and, in one embodiment, forwards the entire message and the message ID to a mobile system for transmission to the targeted mobile phone. Alternatively, the email server may send to the mobile system just an alert, the From field, and/or the Subject field, but not the entire message. Depending on what was transmitted to the mobile system, the mobile phone user may read the entire message, read whom the message was from, read the message subject or read the message ID.
Whether the entire message or just part of the message header was transmitted to the mobile phone, the mobile phone user may choose to reply to the message. To reply to the message, the user may simply press a button to automatically transmit to the mobile system information that identifies the mobile phone user and the message to which the user is replying. The mobile phone user may be identified by the mobile phone's mobile identification number (MIN) or by data associated with the received message, such as the message ID described above. Similarly, the message to which the user is replying may be identified by the message ID. In one embodiment, the message ID is a reply code (i.e., a short string of letters and/or numbers, such as 1234). Alternatively, the message ID is a telephone number (or pseudo telephone number) that is associated with a message processing system. For example, the email server may assign a callback telephone number to a specific message. Upon receiving the message and callback number, the mobile phone user may simply activate the reply mode causing the callback number to be transmitted for identifying the mobile phone user and or the specific message being replied to.
Next, the email server 16 determines whether it should send to the mobile phone 10 the entire email message or just part of the message (for example, one or more fields of the message header) (step 206). This determination can be based on a user profile that is stored at the email server 16, or maybe specified by the user for one or a particular group of email messages. Thus, some users may create a profile that specifies that they want to receive the entire message, whereas other users can specify that they don't want to receive the entire message and can specify which portions of the message they do want to receive. If the entire message should be sent, then the entire message plus the callback number generated in step 204 is forwarded to the mobile system 14 (step 208). If the entire message should not be sent, then the email server 16 forwards, at the least, the callback number generated in step 204 to the mobile system 14 (step 210). The mobile system 14 comprises a message center, a call switching center, and transceiver circuitry necessary for transmitting information to the antenna 12 and the mobile phone 10. The mobile system 14 then transmits to the mobile phone 10 the information forwarded by the email server 16 (step 212).
Upon receiving at the mobile phone 10 the information forwarded by the email server 16, which at the least includes a callback number, the user may choose to send a reply message to the originator of the email message (step 214). The user can accomplish this by activating a reply command. Upon activating the reply command, the mobile phone automatically places a call to the callback number. Alternatively, instead of activating the reply command, the user may manually call the callback number by entering the callback number using a keypad on the mobile phone 10, or by speaking the callback number into the receiver of the mobile phone 10.
In one embodiment, all of the callback numbers generated by the email server are associated with message processor 18, thus upon placing the call to the callback number, the mobile system 14 routes the call to the message processor 18, which then answers the call. The message processor 18 may comprise a voice store and forward system for receiving voice and forwarding voice messages. Voice store and forward systems are readily available and are commonly configured to communicate with networked systems such as the email server 16. The email server 16 communicates with the message processor 18 for establishing a temporary mailbox associated with a specific callback number, which was assigned to a message.
When the message processor 18 receives a call directed to a specific callback number, the message processor 18 prompts the mobile phone user to dictate a reply message for the specific recipient identified by header information contained in the original message (step 216). The message processor 18 records the voice reply message, notifies the email server 16 of the voice message, and provides the email server with the callback telephone number that the user dialed (or that the mobile phone 10 automatically dialed in response to the user activating the reply command) (step 218).
The email server 16 uses the callback telephone number to retrieve the email message associated therewith (step 220). The email server 16 then transmits to the originator of the email message associated with the callback telephone number at least the voice message recorded by the message processor 18 (step 222). In one embodiment, only the voice message is transmitted, in other embodiments, the voice message plus the email message associated with the callback number are transmitted.
The message processor 18 may be replaced with another type of processor depending on the media type. For example, instead of utilizing a voice message processor, a video message processor may be utilized in a broadband system for sending video messages from a mobile phone.
Messages sent from the email server may be transported over the Internet 20 or a private network. The mobile system 14, email system 16 and message processor 18 may be directly connected or they may be connected via a network such as the Internet or the public switched telephone network.
As described above, a mobile phone user may reply to messages that were not transmitted in their entirety to the mobile phone 10. In one embodiment, a mobile phone user might receive only a name for identifying the message originator and/or a subject but not the body of the message. Such would be the case in a system that allows the mobile phone user to decide which messages should be transmitted. In the case where the user does not receive the entire message, the mobile phone user could reply to the originator of the message stating, “I will attend to your message when I return to the office.” Optionally, the mobile phone user could read the subject matter and then send a request message to the email server 16, which causes the email server to transmit the entire message or the remainder of the message. Lastly, a mobile phone 10 equipped with a web browser may connect to an Internet based mail system for reading messages. A reply code, callback number or message code may be embedded in the internet mail based message, thereby enabling a mobile phone user to reply to a specific message as described above.
A significant feature of the present invention described above is the ability to “directly access” a specific message from the mobile phone 10 for replying to or for performing an action thereon. Each message transmitted to or accessed from the mobile phone 10 has a message ID associated therewith. A mobile phone user (for example) may reply to a message, delete a message from the email server 16 without retrieving the entire message, forward a message and retrieve a message. The user may also mistakenly delete a message stored in the mobile phone 10 and then retrieve it again from the email server 16. Unlike prior art email and voice mail systems, the present invention provides for direct access of remotely stored messages for retrieval and for performing an action associated therewith, as is described in the above mentioned related U.S. patent application Ser. Nos. 08/934,143, 08/933,344, 08/934,132, and 08/934,337.
The invention of
Any email server 16 may send message alerts, header information, message codes, subject matter, or the body of a message to the mobile system 14 for transmission to the mobile phone 10. Alternatively, the email server 16 and or the message processor 18 (shown in
As previously stated, a mobile phone user may receive any part of the message or the entire message. While some mobile phone users may decide to have the system alert them and automatically deliver the entire message, other mobile phone users (power users) may wish to be alerted and automatically receive only the sender's name and the subject of the email message. The mobile phone user may then decide to retrieve the message, delete the message, forward the message or reply to the message. The present invention provides the mobile phone user direct access to and remote control of email messages regardless of where the email messages reside.
The mobile phone 10 can originate email messages by utilizing an address book or by direct entry of an address or an abbreviated address. The address book may be stored in the mobile phone 10, on the email server 16 or in the message processor 18. The mobile phone user may simply select a name from the mobile phone's 10 address book, activate a send message command and send a message to the message processor 18 for delivery to the email server 16 and finally to the addressed destination as previously described.
In another embodiment, the mobile phone user may enter the address manually or enter an abbreviated address associated with the actual address stored on the email server 16 and or the message processor 18. In another embodiment, the mobile phone user may utilize a mobile phone 10 that has Internet access capability such as the so-called “smart phones”. Upon accessing the Internet, the mobile phone user may access an Internet based email system such as Hot Mail, Yahoo Mail and the like. The Mobile phone user may then choose a message to read, reply to a message or select a name from an address book for originating a message. The user then selects a send command for sending a message (digital, analog, or other) to the Internet based email system or the email server 16. The selected address book entry may contain addressing information for identifying a particular email server or message processor. Upon the mobile phone user's selection of a message recipient, the mobile phone 10 connects to the identified email server 16, message processor 18, or another system for delivering the email message. An email message may also be routed to a particular system based on the type of email message For example, a voice message may be directed to a voice message processor and a text message may be directed to an email server. The mobile phone 10 may connect to the Internet for sending a message or a phone call may be placed to the message processor 18. Alternatively, a mobile phone user may indicate to an email server that he/she wishes to send a message, such as a voice message, to a particular destination. The email server then informs the message processor 18 that the specific mobile phone user wishes to send a message. The message processor then places a call (or connects) to the mobile phone 10 and prompts the mobile phone user to record a message as previously described.
The present invention provides for receiving an email message that has an attachment (i.e., an attached file). The mobile phone 10 does not need any special modifications to receive a text message and for example a voice attachment (i.e., the attached file contains a voice message). When a mobile phone 10 receives a text message having an attachment associated therewith, the mobile phone user may receive all or a portion of the text message, header information, an alert, and a message code which identifies the attachment. To hear the voice message attachment, delete the voice message, reply to the originator of the voice message, or forward the voice message to other people, the mobile phone user simply places a call to the message processor 18, enters the message code that identifies the attachment using a keypad (or if the message processor 18 has voice recognition capability, simply speaks the message code), and enters a code corresponding to an action or speaks a command, such as reply, delete, forward, save, etc. The message processor 18 performs the command.
That is, the message processor 18, upon receiving a call from a mobile phone user, may be configured to identify the mobile phone user utilizing the industry standard caller ID. After identifying the mobile phone user, the message processor prompts the mobile phone user to enter the message code associated with the received message for retrieving the corresponding voice attachment. The voice message file corresponding to the message code is then accessed by the message processor 18. The message processor 18 then plays the message to the mobile phone user over the telephone connection so that the mobile phone user can hear the attachment.
In this manner, unlike prior art voice mail systems, the present invention provides direct access to a specific message. The mobile phone user need not scroll through a large number of messages in order to locate a specific message.
Upon accessing a message file, the message processor 18 allows the user to erase the message, forward the message, or record a reply for the voice message originator. In another embodiment, the mobile telephone may be configured to automatically transmit a message code to a specific message processor as previously described. The main difference between a message code for retrieving a voice attachment and a reply code is that a message code for retrieving a message directs the message processor to play the message while a reply code directs the message processor 18 to record a reply message.
Voice attachments may be retrieved manually by entering a message code or automatically. The mobile phone user may place a call directly to a specific message processor 18 or the call may be automatically directed to a specific message processor that corresponds to a received system identification code or the call may be directed to a specific telephone number associated to the mailbox within the message processor 18 where a specific message resides.
The mobile phone user may additionally access a voice message by accessing a web based email system with a browser-enabled mobile phone 10. The web based email server may supply the message code and upon a mobile phone user activating a retrieve command, the mobile phone 18 places a call to a message processor 18. Alternatively, the web based email server may notify the message processor 18 and the message processor 18 then connects with (or calls) the mobile phone 10 and plays the message to the mobile phone user. The message processor 18 is adapted to play an analog voice file or a digital voice file. The voice message may be streamed to the mobile phone 10 for real time reproduction or the voice file may be transferred to the mobile phone 10 for storage in a memory device within the mobile phone 10. The message is not limited to an analog or digital voice message buy may include streaming video or other multimedia content.
It has been clearly shown that an email text message and an attachment may be received or retrieved by the mobile phone 10. Email messages may be sent to the mobile phone 10 from a number of devices such as for example, a computer with Internet access to a web based email system or from a computer utilizing an email program. The present invention additionally provides for sending email messages from a mobile phone 10 to another mobile phone 10 (i.e. mobile-to-mobile) or to itself (i.e. memo mode). A mobile originated voice message may be recorded and addressed by a mobile phone user to a targeted mobile phone 10. The difference between sending a message to a computer or to a mobile phone 10 is simply the address. The present invention makes it possible to communicate two-way email, including attachments between a computer and a mobile phone and between mobile phones. Mobile phone users need not scroll through messages to access a specific message. Messages may be directly accessed for performing an action thereto. A mobile phone user may simply select a destination address, activate a send message command and record a voice email for any targeted destination. A mobile phone user may activate a reply command and record a voice email that is automatically or manually addressed to a message originator. Messages may be automatically received, manually retrieved, replied to, forwarded, deleted, originated and reproduced by the mobile phone 10. The need for a mobile phone to have browser capability for accessing the Internet to communicate two-way email is eliminated.
As previously stated, the present invention may be configured to deliver entire text email messages to a mobile phone 10 or just a portion of the message, such as the name of the originator and/or the subject. Additionally, a message may be received from the email server 16 on demand by the mobile phone 10. A mobile phone user may automatically receive a name and subject information but may not wish to automatically receive the entire message. After the mobile user reviews the received names and associated subjects, the mobile phone user may decide to retrieve the remainder of the message or the entire message.
A message may be deleted from the mobile phone 10 but it may be again retrieved from the email server 10, if the message is still stored on the email server 10 as previously described. The ability to retrieve a specific message on demand allows for new and improved features for the mobile phone 10, a paging device or other types of wireless email and messaging devices.
One such feature of the present invention is an improved memory management arrangement and method for automatically deleting messages stored in a mobile phone or messaging device when the device's memory is full. For example, prior art paging devices have a limited amount of memory for storing messages. There are times when the memory is full of messages and new messages cannot be received and stored. Other paging devices automatically delete the oldest read message in order to make room in memory for a newly received message. These prior art devices and methods have a disadvantage because once a message is deleted or over written, it cannot be recovered. The present invention provides a system for deleting messages when memory is full but the deleted or over written messages may be again received and stored by the mobile telephone 10 as will be described hereinafter.
The mobile phone 10 may be configured so that an internal processor executes the following process: Receive and store messages in memory. When a message is received and memory is full, over write one or more message bodies, but retain the message header and the message ID associated with the message, to make room for the new message. Store the new message. When over writing message bodies, over write the oldest read message body first, when there are no read message bodies left, over write the oldest unread message body. When there are no more message bodies, over write the oldest read subject first. When there are no more read subjects, over write the oldest unread subject. The mobile phone 10 may be configured to delete the name and header information using the same priority as described above.
The above-described process causes the mobile phone 10 to over write only message bodies when there is not enough memory to store an additional message. The mobile phone user may continue to save and view information that identifies the message originator (the name) and information describing the message (the subject). If the mobile phone user desires to read an entire message body that was deleted or over written, a retrieve command may be activated by the mobile phone user for causing the mobile phone 10 to transmit the selected message ID to the email server 16. Upon receiving the retrieval request and message ID, the email server 16 sends the email message corresponding to the message ID to the requesting mobile phone 10. An over written or deleted message can now be recovered.
The present invention provides for sending and receiving messages based on one or more variables. The email server 16 and the message processor 18 may be configured with Instant Messenger software such as is provided by Microsoft, America On Line, AT&T and others. These programs provide notification when a computer-messaging device is on line or the operator is logged in (406). When the message processor 18 or email server 16 receives a message for the mobile phone 10, the message may be held until the mobile phone is on line. In other words, when the user is logged in or when the presence of the user is detected, the message is delivered. Conversely, when a message is sent to a mobile phone 10, the message may be held by the email server 16 or the message processor 18 until the presence of the mobile phone 10 or the mobile phone user is detected. Detection of the mobile phone 10 may for example be accomplished by interfacing a home location register (HLR) to the email server 16 and the message processor 18 (304). HLR equipment is readily available and used extensively by mobile phone companies to provide detection of a mobile phone in a particular service area in order to route calls. Detection of a mobile phone user may also be accomplished by detecting user-activated commands that are transmitted to the email server 16 or the message processor 18 (304). Detection of an operator, mobile phone user or active messaging device enables the present invention to perform actions responsive to the status of messaging devices or the presence of their respective user (404). The email server 16 may automatically route messages to a mobile phone 10 when the mobile phone user is utilizing the mobile phone 10 (412). Then, when the mobile phone user turns the mobile phone 10 off and logs in to an office computer, the email server routes messages to the office computer. The present invention may perform any number of actions or combination of actions based on a mobile phone user activated command or by automatically detecting the status of the mobile phone 10 and or the presence of the mobile phone user (310 and 410). Messages may even be redirected automatically to a mobile phone user's computer email service if the message cannot be delivered to the mobile phone 10 because the mobile phone 10 was out of range or turned off (312).
The email server 16 and the message processor 18 may automatically perform an action or sequence of actions based on the time of day, the date, the status of a mobile phone 10, the presence of a user, user activity, geographic location of the mobile phone 10 or any number of conditions which may be transmitted to the email server 16 or the message processor 18. Sensors may be added to the mobile phone 10 and data from the sensors may be automatically transmitted or manually sent by the mobile phone user. A temperature sensor, for example, may be included in the mobile phone 10 wherein temperature readings are automatically transmitted to the email server 16. Based on temperature, the location of the mobile phone 10 and the presence of the mobile phone user, the email server 16 or the message processor may for example send an email message to the mobile phone user that includes an advertisement stating, “The temperature is 98 degrees. Please drink Coke. 35 cent special one block away at the super store.” Alternatively, the mobile phone user may configure the present invention so that messages from particular people are delivered to the mobile phone 10 on week days between 9:00 am and 5:00 pm but otherwise routed to the mobile phone user's home computer and have copies of all message activity go to an office email system. Messages may also be filtered based on the location of the mobile phone 10 so that very important messages are routed to the mobile phone 10 when the mobile phone user is out of town with the mobile phone 10. A mobile phone user may also configure the system (302) to send a notification message to the mobile phone 10 when another mobile phone 10 user or a computer device user is detected by the email server 16 or the message processor 18 (306 and 406).
The present invention may be utilized in telephone systems, paging systems, email systems, and numerous communications systems.
This application is a continuation of U.S. patent application Ser. No. 12/973,722, filed Dec. 20, 2010 (pending), which is a division of U.S. application Ser. No. 11/598,202, filed Nov. 13, 2006 (now U.S. Pat. No. 8,107,601), which is a continuation of U.S. application Ser. No. 10/445,257, filed May 27, 2003 (status: Abandoned), which is a continuation of U.S. application Ser. No. 09/540,490, filed Mar. 31, 2000 (now U.S. Pat. No. 6,636,733), and which is a continuation-in-part of U.S. application Ser. No. 09/408,841, filed Sep. 30, 1999 (now U.S. Pat. No. 6,826,407), which claims the benefit of U.S. Provisional Application No. 60/155,055, filed Sep. 21, 1999 and U.S. Provisional Application No. 60/126,939, filed Mar. 29, 1999; U.S. patent application Ser. No. 09/540,490 is also a continuation-in-part of U.S. application Ser. No. 08/934,143, filed Sep. 19, 1997 (now U.S. Pat. No. 6,233,430), U.S. application Ser. No. 08/933,344, filed Sep. 19, 1997 (now U.S. Pat. No. 6,253,061), U.S. application Ser. No. 08/934,132, filed Sep. 19, 1997 (now U.S. Pat. No. 6,087,956), U.S. application Ser. No. 08/934,337, filed Sep. 19, 1997 (now U.S. Pat. No. 6,259,892), and U.S. application Ser. No. 08/989,874, filed Dec. 12, 1997 (now U.S. Pat. No. 6,097,941). All of the above mentioned applications (provisional and non-provisional) are incorporated in their entirety herein by this reference. Reference is made to the following co-pending and patented patent applications: (1) Ser. No. 13/985,226 (pending); (2) Ser. No. 13/763,970 (now U.S. Pat. No. 8,560,006); (3) Ser. No. 13/210,223 (now U.S. Pat. No. 8,498,387); (4) Ser. No. 09/513,998 (now U.S. Pat. No. 6,983,138); (5) Ser. No. 09/688,282 (now U.S. Pat. No. 7,039,428); (6) Ser. No. 09/860,954 (now U.S. Pat. No. 6,462,646); (7) Ser. No. 10/236,932 (now U.S. Pat. No. 6,696,921); (8) Ser. No. 09/688,321 (now U.S. Pat. No. 7,003,304); (9) Ser. No. 09/613,345 (now U.S. Pat. No. 6,459,360); (10) Ser. No. 11/049,869 (now U.S. Pat. No. 7,277,716); (11) Ser. No. 11/050,775 (now U.S. Pat. No. 7,155,241); (12) Ser. No. 11/082,913 (now U.S. Pat. No. 7,280,838); (13) Ser. No. 11/081,611 (now U.S. Pat. No. 7,376,432); (14) Ser. No. 11/082,872 (now U.S. Pat. No. 7,242,951); (15) Ser. No. 11/083,897 (now U.S. Pat. No. 7,403,787); (16) Ser. No. 11/635,781 (now U.S. Pat. No. 7,843,314); (17) Ser. No. 12/367,358 (now U.S. Pat. No. 8,134,450); (18) Ser. No. 12/580,189 (now U.S. Pat. No. 8,224,294); (19) Ser. No. 12/764,025 (now U.S. Pat. No. 7,835,757); (20) Ser. No. 13/109,389 (now U.S. Pat. No. 8,355,702); (21) Ser. No. 11/108,759 (now U.S. Pat. No. 7,146,157); (22) Ser. No. 11/399,513 (now U.S. Pat. No. 7,499,716); (23) Ser. No. 11/105,441 (now U.S. Pat. No. 7,627,305); (24) Ser. No. 12/625,357 (now U.S. Pat. No. 7,957,695); (25) Ser. No. 10/958,731 (now U.S. Pat. No. 8,099,046); (26) Ser. No. 12/167,971 (now U.S. Pat. No. 8,116,741); (27) Ser. No. 11/598,832 (now U.S. Pat. No. 8,116,743); (28) Ser. No. 12/267,436 (now U.S. Pat. No. 8,295,450); (29) Ser. No. 13/109,437 (now U.S. Pat. No. 8,374,585); (30) Ser. No. 14/225,727 (pending); and (31) Ser. No. 14/295,162 (pending).
| Number | Date | Country | |
|---|---|---|---|
| 60155055 | Sep 1999 | US | |
| 60126939 | Mar 1999 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11598202 | Nov 2006 | US |
| Child | 12973722 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12973722 | Dec 2010 | US |
| Child | 14681782 | US | |
| Parent | 10445257 | May 2003 | US |
| Child | 11598202 | US | |
| Parent | 09540490 | Mar 2000 | US |
| Child | 10445257 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09408841 | Sep 1999 | US |
| Child | 09540490 | US | |
| Parent | 08934143 | Sep 1997 | US |
| Child | 09540490 | US | |
| Parent | 08933344 | Sep 1997 | US |
| Child | 08934143 | US | |
| Parent | 08934132 | Sep 1997 | US |
| Child | 08933344 | US | |
| Parent | 08934337 | Sep 1997 | US |
| Child | 08934132 | US | |
| Parent | 08989874 | Dec 1997 | US |
| Child | 08934337 | US |
