US20100106786A1 - Methods and systems for automatically presenting users with option to call sender responsive to email message - Google Patents
Methods and systems for automatically presenting users with option to call sender responsive to email message Download PDFInfo
- Publication number
- US20100106786A1 US20100106786A1 US12/592,262 US59226209A US2010106786A1 US 20100106786 A1 US20100106786 A1 US 20100106786A1 US 59226209 A US59226209 A US 59226209A US 2010106786 A1 US2010106786 A1 US 2010106786A1
- Authority
- US
- United States
- Prior art keywords
- user
- message
- messages
- reformatted
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/06—Message adaptation to terminal or network requirements
- H04L51/066—Format adaptation, e.g. format conversion or compression
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/212—Monitoring or handling of messages using filtering or selective blocking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
- H04M3/42263—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location where the same subscriber uses different terminals, i.e. nomadism
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
Definitions
- the CD Appendix which is incorporated herein by this reference, contains the source code for an embodiment of the invention, features of which are described below in connection with the drawings.
- the file that includes the source code is named “CD appendix OG001.C1C1C2.txt,” was created Apr. 19, 2007, and is 4,430 KB.
- the copyright owner of the material in the CD Appendix has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office files and records, but otherwise reserves all copyright rights.
- a communications server in accordance with the invention simplifies this process by automatically collecting all of the messages from two or more email sources and presenting the collection to the user.
- an embodiment of the invention includes a mail agent that can be added to a protected client to instruct the client to periodically push messages to the mail system.
- the mail system is therefore not limited to mail collection from sources on the same network, and can therefore provide the user with a complete listing of the user's mail from a single location.
- one embodiment of the invention dispatches messages to an appropriate receiving device based on the user's needs, as specified by the user.
- a communications server in accordance with one embodiment can be configured to dispatch important messages to a wireless device, such as a mobile phone or pager.
- Forwarded messages are automatically reformatted for the receiving device, while a copy of the original message is retained.
- the retained copy can be viewed later if the user is interested in message content that is incompatible with the wireless device.
- the user can also use the wireless device to forward the original message to another receiving device. In the case of forwarding, the saved original message and not the reformatted message is sent to the forwarding address.
- messages are reformatted to include a phone number of the message sender.
- the reformatted message when conveyed to the user's mobile phone, can then present the user with an option to return the message by calling the sender.
- the reformatted message can include more than one phone number.
- the sender's phone numbers are prioritized for presentation to the user. For example, the sender's work number might have a higher priority than the sender's work number during working hours.
- messages are reformatted to include a link to contact information for the message sender.
- the reformatted message when conveyed to the user's mobile phone, can then present the user with an option to review the contact information prior to responding to the message.
- the contact information can include e.g. the sender's nickname, address, phone numbers, and general notes that might be of interest to the recipient.
- Some conventional email services collect messages from various mail sources, allowing users to receive both messages directed to a user's work address and messages directed to a user's home address, for example. When the user then responds to these messages, a single email address identifies the source of the reply. Assume, for example, that a user is assigned that user address “user@home” for a personal email account and “user@work” for a work-related email account. Further assume that the user's email systems collects mail directed to both the work and home accounts, allowing the user to respond to personal and work-related messages from home.
- the user responding from home to a collection of work-related email messages will typically respond to each message as “user@home.” Subsequent replies from the user's response message will then be directed to the user's home address, even if the original message was directed to the user's work account.
- This failure to maintain the user's separate identities can be problematic, as the user will not be able to effectively categorize messages if the user's work and home identities are not preserved.
- An embodiment of the invention addresses this problem, allowing a user to easily maintain separate user identities.
- FIG. 1 depicts a system 100 in accordance with an embodiment of the present invention.
- FIG. 2 depicts system 100 FIG. 1 , showing client 145 and communications server 105 in more detail, while eliminating other features for simplicity.
- FIG. 3 depicts a “screen shot” of a form 300 that allows the user to specify an email source account and choose a corresponding color.
- FIG. 4 is a flowchart 400 depicting the manner in which communications server 105 maintains user identities when the user responds to email messages directed to different ones of the user's identities.
- FIG. 5 is a flowchart 500 depicting the message polling method employed by mail poller 152 of FIG. 2 .
- FIG. 6 is a screen shot depicting an HTML form 600 that a user fills in to establish a new mail filter rule.
- FIG. 7 is a block diagram of dispatcher 154 of FIGS. 1 and 2 .
- FIG. 8 depicts an HTML form 800 that the user has filled out so that dispatcher 154 forwards all urgent messages from co-workers if those messages are received on a Sunday.
- FIG. 9 depicts an HTML form 900 that the user fills out to register a wireless receiving device, such as a pager or mobile phone, so that dispatcher 154 can forward messages to the device.
- a wireless receiving device such as a pager or mobile phone
- FIG. 10 is a flowchart 1000 depicting an operation of dispatcher 154 in the event the user has specified a dispatch rule as depicted in FIG. 8 .
- FIG. 1 depicts a system 100 in accordance with an embodiment of the present invention.
- System 100 includes a number of entities that communicate with one another over a large network, such as the Internet.
- dotted lines terminating in arrows represent communications that can take place over the Internet.
- System 100 includes a communications server 105 , an intranet 110 , a pair of mail servers 115 and 120 , a laptop computer 125 hardwired to the Internet via a local line 130 and a modem 132 , and a cell transceiver 135 adapted to communicate with a wireless device 140 , such as a cell phone that communicates via the conventional Wireless Application Protocol (WAP).
- WAP Wireless Application Protocol
- intranet 110 is a network designed for information processing within an organization.
- Intranet 110 typically employs applications that allow users to communicate with others within intranet 110 and, via the Internet, with others outside of intranet 110 .
- Such applications typically include Web browsers and email programs.
- Intranet 110 includes a local server 143 , a number of clients 145 - 147 , and a firewall 149 .
- Clients 145 - 147 communicate with one another within intranet 110 without their messages traversing firewall 149 .
- Firewall 149 is a conventional security system intended to protect an organization's network against external threats available over the Internet. Among other things, firewall 149 prevents clients 145 - 147 from communicating directly with communications server 105 and other entities on the Internet.
- Communications server 105 includes a mail interface 150 , a mail poller 152 , and a dispatcher 154 .
- Mail poller 152 polls various email sources, such as servers 115 and 120 , to consolidate messages from different information sources that are all assigned to the same user. Messages may be simple, plain text messages, or may include attachments. In one embodiment messages are MIME encoded.
- the examples presented in connection with FIGS. 1-3 assume that single user “USER” maintains three email accounts.
- the first, “user@work,” resides on local server 143 and may be accessed by the user via client 145 .
- the second, “user@home,” is a personal account stored on server 115 that the user distributes to family and friends for personal correspondence.
- the third, “user@play,” is another email account stored on server 120 that the user maintains to communicate with other users that may share a hobby, for example.
- These examples are illustrative; network users often have numerous email accounts for any number of reasons.
- Messages for use in one embodiment of the invention are encoded using the well-known Simple Mail Transfer Protocol (SMTP).
- Servers 115 and 120 typically communicate messages using the POP3 post-office protocol, but may also use the more recent Internet Message Access Protocol (IMAP). Both POP3 and IMAP employ SMTP to communicate between client and server.
- SMTP Simple Mail Transfer Protocol
- IMAP Internet Message Access Protocol
- mail interface 150 is adapted to periodically receive messages pushed through firewall 149 to communications server 105 , for example from client 145 .
- client 145 is adapted to include a software application that periodically pushes messages from client 145 to mail interface 150 .
- the application is often necessary, as mail interface 150 cannot poll client 145 through firewall 149 . Consequently, the user would not have access to mail stored on client 145 unless the user had access to the client on intranet 110 . This is a problem, for example, when the user is away from the office and attempting to retrieve his or her messages using laptop 125 , for example.
- the portion of the attached source code that includes the client-side plug-in enabling the email push is: “src/skywalker/accessors/desktop/desktopagent.” (pp. 294-393).
- the portion of the attached source code that includes the corresponding server-side code is: “src/skywalker/accessors/desktop/server” (pp. 289-293).
- the user configures mail interface 150 to collect all messages associated with the three user mail accounts by receiving pushed messages from client 145 and by polling for messages on servers 115 and 120 .
- Communications server 105 can then be accessed by the user using any number of message-receiving devices, such as client 145 , laptop 125 , or wireless device 140 . The user can thus retrieve all of his or her messages from any device that provides Internet access.
- communications server 105 dispatches messages to an appropriate receiving device based on the user's needs, as specified by the user to communications server 105 .
- communications server 105 can be configured so that dispatcher 154 dispatches messages flagged as urgent to wireless device 140 via cell receiver 135 .
- Messages flagged as “urgent” need not include the term “urgent,” but include some portion of the message that identifies the message as having a higher priority than other messages. Other dispatch criteria are discussed below in connection with FIG. 8 .
- FIG. 2 depicts system 100 FIG. 1 , showing client 145 and communications server 105 in more detail, while eliminating other features for simplicity.
- client 145 includes a mail program 200 and a mail agent 205 .
- communications server 105 polls multiple information sources to consolidate user messages directed to different addresses assigned to a user.
- Mail polling is not new; however, Internet servers are believed to be unable to consolidate all types of user messages because firewalls such as firewall 149 of the Internet 110 preclude servers from polling messages from intranet clients such as client 145 .
- Mail agent 205 periodically pushes messages collected by agent 205 to mail poller 152 of communications server 105 .
- the program modules specific to poller 152 are preceded by “package skywalker.apps.email.”
- Mail poller 152 includes a polling engine 210 and a filter or filters 215 .
- Polling engine 210 periodically downloads the user messages from servers 115 and 120 and conveys the messages to filter 215 .
- Filter 215 applies blocking and filtering rules to the polled messages from polling engine 215 and to any messages obtained from agent 205 .
- Messages that make it through filter 215 are conveyed to mail application 217 , and are possibly dispatched to an appropriate user device using a dispatcher 220 .
- Mail application 217 presents the received new messages to the user using a user interface 222 .
- User interface 222 presents the messages to the user, segregating the messages based on source. For example, messages from “user@home” may be associated with a different color than messages from “user@work” or “user@play.”
- FIG. 3 depicts a “screen shot” of a form 300 that allows the user to specify an email source account and choose a corresponding color.
- Mail application 217 identified as “MailFrontHandler” in the attached source code, handles interfacing with the user over various devices.
- Mail application 217 in conjunction with user interface 222 , allows the user to interact with communications server 105 to send and retrieve mail and to configure the collection of user-specific variables that control message filtering, dispatching, and blocking.
- Mail application 217 supports HyperText Markup Language (HTML) to communicate forms and documents.
- Mail application 217 also supports Wireless Markup Language (WML) and Handheld Device Markup Language (HTML) to format content for Web-enabled mobile phones.
- HTML HyperText Markup Language
- WML Wireless Markup Language
- a user accesses communications server 105 over a conventional connection, such as an Internet connection 224 .
- a user-management and authentication module 226 communicates with the user, verifying the user's personal identity and allowing the user to configure his or her mail settings. Configuration information is stored in a profile server 230 within communications server 105 .
- user management and authentication module 226 also facilitates communication with the user via wireless devices, such as cellular phones.
- the portions of the attached source code that deal with user management and authentication module 226 are prefaced with “MainServLet” for HTML and prefaced with “ephone” for wireless devices.
- Conventional email services collect messages from various sources, allowing users to receive messages directed to a work address and messages directed to a home address, for example. When the user then responds to these messages, a single email address identifies the source of the reply. For example, a user responding from home to a collection of work-related email messages will respond to each message as “user@home.” Subsequent replies from the original message sources will then be directed to the user's home address.
- a collection of messages includes one from the user's employer directed to “user@work” and another from a family member directed to “user@home,” then the user will respond to both messages either as “user@work” or “user@home,” depending upon whether the user responded from home or from work.
- This can be problematic, as the user will not be able to effectively filter messages based on identity if the user's identities are not preserved, regardless of the account from which the user responds to messages.
- FIG. 4 is a flowchart 400 depicting the manner in which communications server 105 maintains user identities when the user responds to email messages directed to different ones of the user's identities.
- Communications server 105 organizes incoming messages by their respective destination addresses. Thus, messages directed to user@home would be stored in directory locations associated with the user's “home” identity, while messages directed to user@work would be stored in directory locations associated with the user's “work” identity.
- Communications server 105 then replies to messages using the destination address associated with the respective identity.
- mail application 217 can save the “to” field from incoming messages and use this information to identify the author of message replies. This method is not preferred, however, as the “to” field can sometimes incorrectly identify a message recipient.
- Communications server 105 stores each of messages No. 1 and No. 2, depicting each in a manner that identifies the source address to the user.
- message #1 is green to indicate that message #1 was directed to the user's home address
- message #2 is red to indicate that message #2 was directed to the user's play address.
- the chosen colors are arbitrary, and other colors and distinctions can be used to distinguish messages.
- the user's reply identifies the sender as having the email address to which the original message was directed.
- the reply to “Alyssa@play” (to mail server 120 ) is identified as being from “user@play” and the reply to “Nicole@yahoo” (to a yahoo mail server 405 ) is identified as being from “user@home,” even though both replies are from the same server 105 .
- Server 105 need not be associated with any of the depicted mail servers 115 , 120 , or 405 , but may have an entirely different path name. Alternatively, servers 115 and 120 may be “native” servers that are part of server 105 .
- Reply icon 410 is a conventional “button” linked to a selected one of the first and second messages. Many other methods of initiating message replies will be obvious to those of skill in the art.
- a message can be reformatted to present the recipient an option to reply to the message by calling the sender, which option is identified here as a second reply icon 412 .
- database 230 FIG. 2
- Each address book maintains a list of contacts for the user and includes various fields for each contact, including contact names, email addresses, phone numbers, notes, etc.
- a portion of the attached source code that deals with contact fields begins on Page 9 of 1078 with the line entitled “CREATE TABLE CONTACTS (NICKNAME VARCHAR(40) NOT NULL.”
- Reformatted messages can present the recipient user with an option to return the message by calling the sender.
- Portions of the attached source code that support this aspect of the invention begin on Page 400 of 1078 with the line “// Get Phone Number to dial—Priorities are: 1) Cellular, 2) Work, 3) Home,” and on Page 439 of 1078 with the line “// look up contact phone message based on From field of email message.” Further, the call to the function that inserts the sender's phone number into the message is entitled “fromcontact.getPhoneBack( ),” and is detailed beginning at page 696 of 1078 in the source code.
- the reformatted message can include more than one phone number.
- the sender's phone numbers are prioritized for presentation to the user. This aspect is also discussed in the attached source code at pages 400 and 439.
- messages are reformatted to include a link to contact information specific to the message sender.
- the reformatted message when conveyed to the user's mobile phone, can then present the user with an option to review the contact information prior to responding to the message.
- the contact information can include e.g. notes about the sender that might be of interest to the recipient.
- Contact-specific information in accordance with one embodiment is listed in the attached source code at Page 393 of 1078 beginning at line “package skywalker.apps.contacts.frontend.”
- message are also reformatted to support the following user options: “Reply”: reply to the message with a message to the sender; “Reply All”: reply to the message with a message to the sender and all message recipients; “Forward”: forward the message to a recipient of the user's choosing; “Add Contact”: add the sender's contact information to the user's address book; “Delete”: delete the message.
- selecting “Reply” may present the user alternative reply options, allowing the message recipient to reply via email or by selecting from among a list of phone numbers.
- FIG. 5 is a flowchart 500 depicting the message polling method employed by mail poller 152 of FIG. 2 .
- Poller 152 retrieves, parses, and filters mail messages received from disparate sources.
- Poller 152 acquires the requisite user-specific information to perform these functions from database 230 , the contents of which the user can manipulate via mail application 217 .
- the first event is the beginning of what is known as the “polling interval.”
- external email sources are polled every 15 minutes and native mail sources every two minutes, regardless of whether the user is currently logged onto communications server 105 .
- the user may also initiate polling either by logging on to server 105 or by selecting a “get messages” button on a message-view screen.
- poller 152 when first triggered, poller 152 takes the user's information from database 230 , logs onto the first server listed (step 505 ), and obtains the first message on the server (step 505 ).
- Each message has a unique identifier (UID).
- Poller 152 reads the message (step 507 ) and determines whether the UID is already listed in database 230 (step 509 ). If not, the message is a new one, and is therefore added to the list of messages in database 230 (step 511 ). Also in step 511 , the message is marked to indicate that the message exists locally and on a remote server. As discussed below, this marking scheme enables poller 152 to synchronize the contents of the local and remote mail servers.
- step 515 the entire contents of the message, including any attachments, are cached (step 515 ) in database 230 .
- Caching renders the message content available to the user as soon as the message appears in the user's “in-box.”
- filter 215 determines whether the message meets the requirements of a blocked message (step 517 ). If so, then the message is unmarked (step 519 ), causing the message to be deleted at a later step. If, on the other hand, the message is not blocked in step 517 , then filter 215 determines whether the message should be dispatched to another device, such as another mail account, a mobile phone, or pager. If so, then dispatcher 220 dispatches the message to the appropriate device (step 521 ).
- another device such as another mail account, a mobile phone, or pager.
- FARE Filtering And Routing Engine
- the poller does a procedure call on a FARE module called “fareworker.java,” passing the messages as arguments.
- the FARE module then employs user-specific filter variables (e.g., from database 230 of FIG. 2 ) to filter and dispatch the messages.
- poller 152 then sends the UID and the message header to the local message database in database 230 (step 523 ) and looks for more messages (step 525 ). Additional messages are treated in the same manner as the first message. If there are no more messages, then the process moves to step 527 , during which unmarked messages are deleted. Unmarked messages include those that were blocked in step 517 .
- poller 152 Having read all the messages from the first remote server, poller 152 checks database 230 to determine whether there are more email sources to be polled (step 529 ). If so, then poller 152 reads the next source (step 531 ) and returns to step 507 .
- step 509 the UID will already have been listed so the process will move to step 513 , during which the message is marked. If the user is in session (step 533 ), then the entire contents of the message, including any attachments, will be cached to allow the user immediate access to the content (steps 535 and 537 ). Since the message had been dealt with previously, there is no need to determine whether the message should be blocked or filtered. Consequently, the process moves to step 525 .
- step 527 in which all of the unmarked messages are deleted. These messages will include those that were blocked in step 517 and those that were not marked in steps 511 and 513 .
- the unmarked messages will be either blocked messages or those that have been deleted at the source, and that should consequently be deleted in the local server. The entire process will then be repeated for each message source listed in database 220 .
- poller 152 goes dormant until the next time polling is initiated. If the user is in session, then the message headers are displayed in step 541 . The entire messages may also be displayed when prompted by the user (step 531 ). If the user is not in session, then nothing happens (step 545 ) until the user logs on or periodic polling is initiated.
- the entire message polled from the remote server (for example, remote server 115 ) is not cached in either step 515 or step 537 , but rather is stored within database 230 .
- messages that are deleted from the remote server are not marked for deletion on the local server in step 511 and 513 , and consequently are not deleted in step 527 .
- Communications server 105 saves the UIDs of messages deleted at communications server 105 . The next time communications server 105 polls for messages, those messages identified with a deleted UID are not displayed to user. Communications server 105 retains the UIDs of messages deleted from database 230 until those messages are also deleted at the source (e.g., deleted from remote server 115 ).
- FIG. 6 is a screen shot depicting an HTML form 600 that a user fills in to establish a new mail filter rule.
- Form 600 appears when the user clicks on an “Add Blocking Filter” button.
- the user may block mail messages based on the sender, the subject, the mail source, the priority level, and/or the time at which the message was sent.
- the “Filter Title” field in form 600 is purely for user interface, and is not part of the filtering algorithm.
- Polling engine 210 will generally have already sorted the messages by source (e.g., user@home vs. user@work), so the specified mail servers control polling engine 210 , and do not control filter 215 . This distinction is transparent to the user.
- Mail poller 152 blocks any message that matches any criterion of filter 215 .
- the criteria in anyone filter are applied as a group using top-to-bottom inheritance. For example, the definition shown in FIG. 6 would block all low-priority messages sent during any weekday.
- mail poller 152 When mail poller 152 encounters a match, mail poller 152 blocks the message without further tests. Mail poller 152 then stores the message UID of the blocked message in the user database for future reference. For a message retrieved from a remote mail server, where a copy still exists, the message header and body are flushed permanently from local memory. If a blocked message is retrieved from native mail (in which case no backup copy would otherwise exist), the message is placed into the user's deleted mail folder.
- mail poller 152 stores both its UID and its header in database 220 . In addition, if this particular call is taking place while the user is in session, the message body and attachments are cached for the duration of the session.
- Filter 215 in mail poller 152 looks for stream patterns in the “from” and “subject” fields. Streams are case-insensitive.
- the filter string need not be identical to the corresponding portion of the message, but the corresponding portion of the message must include the string. For example, if a message's “from” field reads:
- Filter 215 matches priorities using the “X-priority” field associated with conventional email messages.
- the values for high, medium, and low priority are specified as 1, 0, and ⁇ 1, respectively.
- FIG. 7 is a block diagram of dispatcher 154 of FIGS. 1 and 2 .
- Dispatcher 154 includes a dispatching filter 700 , a message renderer 705 , and a message hound 710 .
- Dispatching filter 700 allows the user to specify one or more forwarding addresses for messages that meet particular filtering requirements.
- FIG. 8 depicts an HTML form 800 that the user has filled out so that dispatcher 154 forwards all urgent messages from co-workers if those messages are received on a Sunday. Before such dispatching can be accomplished, the user must enter a description of the device to which the messages are to be forwarded.
- FIG. 9 depicts an HTML form 900 that the user fills out to register a wireless receiving device, such as a pager or mobile phone, so that dispatcher 154 can forward messages to the device.
- Form 900 allows the user to include the contents of the subject field, the identities of other users to whom the message was directed, and a limited number of characters from within the message body. This aspect of form 900 is sometimes important for pagers, because some pager companies charge based on the amount of information conveyed to device.
- the wireless device is a mobile phone
- message renderer 705 is instructed to include: 1) the subject, 2) the identities of other users receiving the message, and 3) up to 700 characters within the body of the message.
- Message renderer 705 allows users to set different dispatch parameters for different devices. For example, message renderer 705 may be configured to send less information to a pager than to a cellular phone, and to forward the entire contents of the message, including any attachments, if the message is forwarded to a personal computer or laptop. Renderer 705 also reformats messages as necessary to forward some or the entire message content to selected target receiving devices. In a typical example, a user may configure renderer 705 to forward only the subject and sender of important messages to the user's mobile phone.
- message renderer 705 can reformat messages to include the phone number of the message sender.
- the reformatted message when conveyed to the user's mobile phone, can then present the user with an option to return the message via a phone call.
- database 230 includes more than one phone number for the sender
- the reformatted message can include more than one phone number.
- message renderer 705 prioritizes the sender's phone numbers for presentation to the user.
- Message renderer 705 can also reformat the message to include additional information about the contact, such as notes about the sender that might be of interest to the message recipient.
- the final element of dispatcher 154 is message hound 710 .
- Message hound 710 can be configured by the user to establish a hierarchy of devices to which selected messages might be forwarded. For example, the user can configure message hound 710 to forward all urgent messages to a mobile phone and, in the event that the mobile phone is turned off or otherwise out of service, then to send the same or a smaller version of the message to the user's pager.
- Message hound 710 can also be configured to include another email address, such as that of the user's secretary, in the hierarchy.
- FIG. 10 is a flowchart 1000 depicting an operation of dispatcher 154 in the event the user has specified a dispatch rule as depicted in FIG. 8 .
- the method for dispatcher 154 is “forwardMessage” in the file “FareWorker” in the source code of the attached CD Appendix.
- step 1005 the user has filled out and submitted form 800 , and consequently conveyed the information of form 800 to database 230 ( FIG. 2 ).
- Dispatcher 154 using the information stored in database 230 , subjects subsequently received unblocked messages (step 1010 , from step 517 of flowchart 500 of FIG. 5 ) to the rules defined using form 800 (decision 1015 ). If the message meets the rules, then a version of the received message should be sent to the user's mobile phone. Regardless of whether the message meets the rules, the message's UID and header are added to the user's database (step 1020 ). Step 1020 is the same step identified at step 523 in FIG. 5 .
- dispatcher 154 If the message is to be forwarded to the user's mobile phone, dispatcher 154 first attempts to contact the specified phone (step 1025 ). This attempt is made using the Short Messaging Service (SMS) protocol, a conventional protocol adapted for sending short messages to pagers and phones. Using SMS, dispatcher 154 can send a short alphanumeric message to the user's mobile phone.
- SMS Short Messaging Service
- one embodiment of the invention reformats the message for receipt by a pager (step 1035 ) and then sends the reformatted message to the user's pager (step 1045 ).
- This embodiment is beneficial, as pagers generally provide a more robust means of communication than do mobile phones.
- the message is reformatted as necessary for transmission to the user's cellular phone (step 1040 ), in which case the reformatted message may include a reply number for the sender of the received message. Finally, the reformatted message is sent to the user's cellular phone (step 1050 ).
- the entire message is preserved in the user's database regardless of whether all or a portion of the message is conveyed to one of the user's wireless devices.
- the user can therefore access the complete message later from e.g. a personal computer.
- mail application 217 FIG. 2
- the recipient of the forwarded message is therefore not limited by the capabilities of the forwarding device. For example, a user away from his or her office may forward an urgent message containing an attachment to a nearby computer for viewing or printing.
- the code that supports this type of forwarding is identified at pages 446-469 of the attached source code as “PhoneComposeMessageHandler.”
- Message hound 710 can be set to dispatch messages to the next listed device upon receipt of a failure-to-deliver message, or can be set to dispatch the message if the intended recipient does not respond within a given time period.
- SMTP and WAP can be implemented to let the sender know whether the intended recipient received a message.
- One embodiment uses this information to report success or failure to the sender. For example, mail application 217 might report that the user's mobile phone was out of service and the user's pager has been alerted.
- the foregoing specification and figures are high-level descriptions of some embodiments of the invention.
- the attached annotated source code details a specific embodiment.
- the code executes on a Solaris Sparc workstation on a UNIX platform.
- the messages, user preferences, email sources, and UIDs are stored on a database server, in one embodiment a Microsoft SQL server running on a Windows NT server machine.
Abstract
A mail server collects messages from a number of user accounts and presents them to the user from a single location. Forwarded messages are automatically reformatted for the receiving device, while a copy of the original message is retained. Messages may be reformatted to include the phone number of the message sender. The reformatted message can then present the user with an option to return the message via a phone call. The reformatted message can include more than one phone number, in which case the sender's phone numbers can be prioritized for presentation to the user. The reformatted message can also present the user with an option to review notes or other contact-specific information prior to responding to the message.
Description
- The CD Appendix, which is incorporated herein by this reference, contains the source code for an embodiment of the invention, features of which are described below in connection with the drawings. The file that includes the source code is named “CD appendix OG001.C1C1C2.txt,” was created Apr. 19, 2007, and is 4,430 KB. The copyright owner of the material in the CD Appendix has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office files and records, but otherwise reserves all copyright rights.
- Many computer users maintain a number of different email accounts. For example, many users have separate accounts for home and work. Unfortunately, maintaining more than one account can be cumbersome, often requiring the user to check his or her mail at more than one location. A communications server in accordance with the invention simplifies this process by automatically collecting all of the messages from two or more email sources and presenting the collection to the user.
- Some conventional mail systems collect mail from various sources. However, such systems do not work in many cases in which one of the email sources is a client connected to the mail system via a protective firewall. In such cases, the firewall will not allow the mail collection systems to pull mail from the protected client. To address this problem, an embodiment of the invention includes a mail agent that can be added to a protected client to instruct the client to periodically push messages to the mail system. The mail system is therefore not limited to mail collection from sources on the same network, and can therefore provide the user with a complete listing of the user's mail from a single location.
- In addition to providing the user access to a number of mail sources, one embodiment of the invention dispatches messages to an appropriate receiving device based on the user's needs, as specified by the user. For example, a communications server in accordance with one embodiment can be configured to dispatch important messages to a wireless device, such as a mobile phone or pager.
- Forwarded messages are automatically reformatted for the receiving device, while a copy of the original message is retained. The retained copy can be viewed later if the user is interested in message content that is incompatible with the wireless device. The user can also use the wireless device to forward the original message to another receiving device. In the case of forwarding, the saved original message and not the reformatted message is sent to the forwarding address.
- In one embodiment messages are reformatted to include a phone number of the message sender. The reformatted message, when conveyed to the user's mobile phone, can then present the user with an option to return the message by calling the sender. The reformatted message can include more than one phone number. In some embodiments the sender's phone numbers are prioritized for presentation to the user. For example, the sender's work number might have a higher priority than the sender's work number during working hours.
- In another embodiment messages are reformatted to include a link to contact information for the message sender. The reformatted message, when conveyed to the user's mobile phone, can then present the user with an option to review the contact information prior to responding to the message. The contact information can include e.g. the sender's nickname, address, phone numbers, and general notes that might be of interest to the recipient.
- Some conventional email services collect messages from various mail sources, allowing users to receive both messages directed to a user's work address and messages directed to a user's home address, for example. When the user then responds to these messages, a single email address identifies the source of the reply. Assume, for example, that a user is assigned that user address “user@home” for a personal email account and “user@work” for a work-related email account. Further assume that the user's email systems collects mail directed to both the work and home accounts, allowing the user to respond to personal and work-related messages from home. The user responding from home to a collection of work-related email messages will typically respond to each message as “user@home.” Subsequent replies from the user's response message will then be directed to the user's home address, even if the original message was directed to the user's work account. This failure to maintain the user's separate identities can be problematic, as the user will not be able to effectively categorize messages if the user's work and home identities are not preserved. An embodiment of the invention addresses this problem, allowing a user to easily maintain separate user identities.
- In one embodiment that forwards messages to wireless devices, if the user's mobile phone is unavailable, then the original message is reformatted and forwarded to the user's pager. This embodiment is beneficial, particularly for urgent messages, as pagers generally provide a more robust means of communication than do mobile phones.
- This summary does not limit the claims, which are defined instead by the claims.
-
FIG. 1 depicts asystem 100 in accordance with an embodiment of the present invention. -
FIG. 2 depictssystem 100FIG. 1 , showingclient 145 andcommunications server 105 in more detail, while eliminating other features for simplicity. -
FIG. 3 depicts a “screen shot” of aform 300 that allows the user to specify an email source account and choose a corresponding color. -
FIG. 4 is aflowchart 400 depicting the manner in whichcommunications server 105 maintains user identities when the user responds to email messages directed to different ones of the user's identities. -
FIG. 5 is aflowchart 500 depicting the message polling method employed bymail poller 152 ofFIG. 2 . -
FIG. 6 is a screen shot depicting an HTMLform 600 that a user fills in to establish a new mail filter rule. -
FIG. 7 is a block diagram ofdispatcher 154 ofFIGS. 1 and 2 . -
FIG. 8 depicts an HTMLform 800 that the user has filled out so thatdispatcher 154 forwards all urgent messages from co-workers if those messages are received on a Sunday. -
FIG. 9 depicts an HTMLform 900 that the user fills out to register a wireless receiving device, such as a pager or mobile phone, so thatdispatcher 154 can forward messages to the device. -
FIG. 10 is aflowchart 1000 depicting an operation ofdispatcher 154 in the event the user has specified a dispatch rule as depicted inFIG. 8 . -
FIG. 1 depicts asystem 100 in accordance with an embodiment of the present invention.System 100 includes a number of entities that communicate with one another over a large network, such as the Internet. InFIG. 1 , dotted lines terminating in arrows represent communications that can take place over the Internet.System 100 includes acommunications server 105, anintranet 110, a pair ofmail servers laptop computer 125 hardwired to the Internet via alocal line 130 and amodem 132, and acell transceiver 135 adapted to communicate with awireless device 140, such as a cell phone that communicates via the conventional Wireless Application Protocol (WAP). - As is conventional,
intranet 110 is a network designed for information processing within an organization.Intranet 110 typically employs applications that allow users to communicate with others withinintranet 110 and, via the Internet, with others outside ofintranet 110. Such applications typically include Web browsers and email programs.Intranet 110 includes alocal server 143, a number of clients 145-147, and afirewall 149. Clients 145-147 communicate with one another withinintranet 110 without theirmessages traversing firewall 149. Firewall 149 is a conventional security system intended to protect an organization's network against external threats available over the Internet. Among other things,firewall 149 prevents clients 145-147 from communicating directly withcommunications server 105 and other entities on the Internet. -
Communications server 105 includes amail interface 150, amail poller 152, and adispatcher 154.Mail poller 152 polls various email sources, such asservers - The examples presented in connection with
FIGS. 1-3 assume that single user “USER” maintains three email accounts. The first, “user@work,” resides onlocal server 143 and may be accessed by the user viaclient 145. The second, “user@home,” is a personal account stored onserver 115 that the user distributes to family and friends for personal correspondence. Finally, the third, “user@play,” is another email account stored onserver 120 that the user maintains to communicate with other users that may share a hobby, for example. These examples are illustrative; network users often have numerous email accounts for any number of reasons. - Messages for use in one embodiment of the invention are encoded using the well-known Simple Mail Transfer Protocol (SMTP).
Servers - In addition to collecting messages from the various email sources via
poller 152,mail interface 150 is adapted to periodically receive messages pushed throughfirewall 149 tocommunications server 105, for example fromclient 145. In one embodiment,client 145 is adapted to include a software application that periodically pushes messages fromclient 145 to mailinterface 150. The application is often necessary, asmail interface 150 cannot pollclient 145 throughfirewall 149. Consequently, the user would not have access to mail stored onclient 145 unless the user had access to the client onintranet 110. This is a problem, for example, when the user is away from the office and attempting to retrieve his or hermessages using laptop 125, for example. The portion of the attached source code that includes the client-side plug-in enabling the email push is: “src/skywalker/accessors/desktop/desktopagent.” (pp. 294-393). The portion of the attached source code that includes the corresponding server-side code is: “src/skywalker/accessors/desktop/server” (pp. 289-293). - The user configures
mail interface 150 to collect all messages associated with the three user mail accounts by receiving pushed messages fromclient 145 and by polling for messages onservers Communications server 105 can then be accessed by the user using any number of message-receiving devices, such asclient 145,laptop 125, orwireless device 140. The user can thus retrieve all of his or her messages from any device that provides Internet access. - In addition to providing the user access to a number of mail sources,
communications server 105 dispatches messages to an appropriate receiving device based on the user's needs, as specified by the user tocommunications server 105. For example,communications server 105 can be configured so thatdispatcher 154 dispatches messages flagged as urgent towireless device 140 viacell receiver 135. Messages flagged as “urgent” need not include the term “urgent,” but include some portion of the message that identifies the message as having a higher priority than other messages. Other dispatch criteria are discussed below in connection withFIG. 8 . -
FIG. 2 depictssystem 100FIG. 1 , showingclient 145 andcommunications server 105 in more detail, while eliminating other features for simplicity. As shown,client 145 includes amail program 200 and amail agent 205. As noted above,communications server 105 polls multiple information sources to consolidate user messages directed to different addresses assigned to a user. Mail polling is not new; however, Internet servers are believed to be unable to consolidate all types of user messages because firewalls such asfirewall 149 of theInternet 110 preclude servers from polling messages from intranet clients such asclient 145. Applicants therefore extendedconventional mail program 200 to include amail agent 205.Mail agent 205 periodically pushes messages collected byagent 205 to mailpoller 152 ofcommunications server 105. The program modules specific to poller 152 are preceded by “package skywalker.apps.email.” -
Mail poller 152 includes apolling engine 210 and a filter or filters 215.Polling engine 210 periodically downloads the user messages fromservers Filter 215 applies blocking and filtering rules to the polled messages frompolling engine 215 and to any messages obtained fromagent 205. Messages that make it throughfilter 215 are conveyed to mailapplication 217, and are possibly dispatched to an appropriate user device using a dispatcher 220.Mail application 217 presents the received new messages to the user using a user interface 222. - User interface 222 presents the messages to the user, segregating the messages based on source. For example, messages from “user@home” may be associated with a different color than messages from “user@work” or “user@play.”
FIG. 3 depicts a “screen shot” of aform 300 that allows the user to specify an email source account and choose a corresponding color.Mail application 217, identified as “MailFrontHandler” in the attached source code, handles interfacing with the user over various devices.Mail application 217, in conjunction with user interface 222, allows the user to interact withcommunications server 105 to send and retrieve mail and to configure the collection of user-specific variables that control message filtering, dispatching, and blocking.Mail application 217 supports HyperText Markup Language (HTML) to communicate forms and documents.Mail application 217 also supports Wireless Markup Language (WML) and Handheld Device Markup Language (HTML) to format content for Web-enabled mobile phones. - A user accesses
communications server 105 over a conventional connection, such as anInternet connection 224. A user-management andauthentication module 226 communicates with the user, verifying the user's personal identity and allowing the user to configure his or her mail settings. Configuration information is stored in aprofile server 230 withincommunications server 105. Although not shown inFIG. 2 , user management andauthentication module 226 also facilitates communication with the user via wireless devices, such as cellular phones. The portions of the attached source code that deal with user management andauthentication module 226 are prefaced with “MainServLet” for HTML and prefaced with “ephone” for wireless devices. - Conventional email services collect messages from various sources, allowing users to receive messages directed to a work address and messages directed to a home address, for example. When the user then responds to these messages, a single email address identifies the source of the reply. For example, a user responding from home to a collection of work-related email messages will respond to each message as “user@home.” Subsequent replies from the original message sources will then be directed to the user's home address.
- For example, if a collection of messages includes one from the user's employer directed to “user@work” and another from a family member directed to “user@home,” then the user will respond to both messages either as “user@work” or “user@home,” depending upon whether the user responded from home or from work. This can be problematic, as the user will not be able to effectively filter messages based on identity if the user's identities are not preserved, regardless of the account from which the user responds to messages. Thus, if the user's employer sends a message to “user@work,” then user will want to respond as “user@work,” and if a family member sends a message to “user@home,” then the user will want to respond as “user@home.” Some mail systems allow the user to manually change the “from” address of messages; unfortunately, manually switching between address is cumbersome and invites errors. An embodiment of the invention addresses this problem, allowing a user to easily maintain separate identities.
-
FIG. 4 is aflowchart 400 depicting the manner in whichcommunications server 105 maintains user identities when the user responds to email messages directed to different ones of the user's identities.Communications server 105 organizes incoming messages by their respective destination addresses. Thus, messages directed to user@home would be stored in directory locations associated with the user's “home” identity, while messages directed to user@work would be stored in directory locations associated with the user's “work” identity.Communications server 105 then replies to messages using the destination address associated with the respective identity. Alternatively,mail application 217 can save the “to” field from incoming messages and use this information to identify the author of message replies. This method is not preferred, however, as the “to” field can sometimes incorrectly identify a message recipient. - Referring again to the example of
FIG. 4 , assume that “Nicole@yahoo” sent a message No. 1 to “user@home,” and that “Alyssa@play” sent a message No. 2 to “user@play.”Communications server 105 stores each of messages No. 1 and No. 2, depicting each in a manner that identifies the source address to the user. In the example,message # 1 is green to indicate thatmessage # 1 was directed to the user's home address, andmessage # 2 is red to indicate thatmessage # 2 was directed to the user's play address. The chosen colors are arbitrary, and other colors and distinctions can be used to distinguish messages. - Should the user initiate a response to either message (by selecting a
reply icon 410, for example), the user's reply identifies the sender as having the email address to which the original message was directed. In the example ofFIG. 4 , the reply to “Alyssa@play” (to mail server 120) is identified as being from “user@play” and the reply to “Nicole@yahoo” (to a yahoo mail server 405) is identified as being from “user@home,” even though both replies are from thesame server 105.Server 105 need not be associated with any of the depictedmail servers servers server 105.Reply icon 410 is a conventional “button” linked to a selected one of the first and second messages. Many other methods of initiating message replies will be obvious to those of skill in the art. - A message can be reformatted to present the recipient an option to reply to the message by calling the sender, which option is identified here as a
second reply icon 412. In some embodiments, database 230 (FIG. 2 ) includes an address book for each user. Each address book maintains a list of contacts for the user and includes various fields for each contact, including contact names, email addresses, phone numbers, notes, etc. A portion of the attached source code that deals with contact fields begins on Page 9 of 1078 with the line entitled “CREATE TABLE CONTACTS (NICKNAME VARCHAR(40) NOT NULL.” - Reformatted messages can present the recipient user with an option to return the message by calling the sender. Portions of the attached source code that support this aspect of the invention begin on
Page 400 of 1078 with the line “// Get Phone Number to dial—Priorities are: 1) Cellular, 2) Work, 3) Home,” and on Page 439 of 1078 with the line “// look up contact phone message based on From field of email message.” Further, the call to the function that inserts the sender's phone number into the message is entitled “fromcontact.getPhoneBack( ),” and is detailed beginning at page 696 of 1078 in the source code. - The reformatted message can include more than one phone number. In some embodiments the sender's phone numbers are prioritized for presentation to the user. This aspect is also discussed in the attached source code at
pages 400 and 439. - In another embodiment messages are reformatted to include a link to contact information specific to the message sender. The reformatted message, when conveyed to the user's mobile phone, can then present the user with an option to review the contact information prior to responding to the message. The contact information can include e.g. notes about the sender that might be of interest to the recipient. Contact-specific information in accordance with one embodiment is listed in the attached source code at Page 393 of 1078 beginning at line “package skywalker.apps.contacts.frontend.”
- In addition to providing an option to reply to a message via a phone call, message are also reformatted to support the following user options: “Reply”: reply to the message with a message to the sender; “Reply All”: reply to the message with a message to the sender and all message recipients; “Forward”: forward the message to a recipient of the user's choosing; “Add Contact”: add the sender's contact information to the user's address book; “Delete”: delete the message. These features are supported e.g. on page 1072 in the attached source code beginning at the line entitled “<option onpick=“#replymenu”>Reply</option>.” In some embodiments selecting “Reply” may present the user alternative reply options, allowing the message recipient to reply via email or by selecting from among a list of phone numbers.
-
FIG. 5 is aflowchart 500 depicting the message polling method employed bymail poller 152 ofFIG. 2 .Poller 152 retrieves, parses, and filters mail messages received from disparate sources.Poller 152 acquires the requisite user-specific information to perform these functions fromdatabase 230, the contents of which the user can manipulate viamail application 217. - Three events trigger mail polling. The first event is the beginning of what is known as the “polling interval.” In one embodiment, external email sources are polled every 15 minutes and native mail sources every two minutes, regardless of whether the user is currently logged onto
communications server 105. The user may also initiate polling either by logging on toserver 105 or by selecting a “get messages” button on a message-view screen. - Regardless of the way in which polling is initiated, when first triggered,
poller 152 takes the user's information fromdatabase 230, logs onto the first server listed (step 505), and obtains the first message on the server (step 505). - Each message has a unique identifier (UID).
Poller 152 reads the message (step 507) and determines whether the UID is already listed in database 230 (step 509). If not, the message is a new one, and is therefore added to the list of messages in database 230 (step 511). Also instep 511, the message is marked to indicate that the message exists locally and on a remote server. As discussed below, this marking scheme enables poller 152 to synchronize the contents of the local and remote mail servers. - If the user is currently logged onto
communications server 105, a circumstance termed “in session,” the entire contents of the message, including any attachments, are cached (step 515) indatabase 230. Caching renders the message content available to the user as soon as the message appears in the user's “in-box.” Next,filter 215 determines whether the message meets the requirements of a blocked message (step 517). If so, then the message is unmarked (step 519), causing the message to be deleted at a later step. If, on the other hand, the message is not blocked instep 517, then filter 215 determines whether the message should be dispatched to another device, such as another mail account, a mobile phone, or pager. If so, then dispatcher 220 dispatches the message to the appropriate device (step 521). - In the attached source code, message dispatching, filtering, and blocking are collectively performed by a Filtering And Routing Engine (FARE). In that embodiment, after obtaining messages the poller does a procedure call on a FARE module called “fareworker.java,” passing the messages as arguments. The FARE module then employs user-specific filter variables (e.g., from
database 230 ofFIG. 2 ) to filter and dispatch the messages. - Returning to
flowchart 500, whether the message is dispatched or not,poller 152 then sends the UID and the message header to the local message database in database 230 (step 523) and looks for more messages (step 525). Additional messages are treated in the same manner as the first message. If there are no more messages, then the process moves to step 527, during which unmarked messages are deleted. Unmarked messages include those that were blocked instep 517. - Having read all the messages from the first remote server,
poller 152checks database 230 to determine whether there are more email sources to be polled (step 529). If so, then poller 152 reads the next source (step 531) and returns to step 507. - The first example assumed that the message had not yet been read by
poller 152. Periodic polling often results inpoller 152 reading messages multiple times. Previously read messages are dealt with in a different way.Steps step 509, however, the UID will already have been listed so the process will move to step 513, during which the message is marked. If the user is in session (step 533), then the entire contents of the message, including any attachments, will be cached to allow the user immediate access to the content (steps 535 and 537). Since the message had been dealt with previously, there is no need to determine whether the message should be blocked or filtered. Consequently, the process moves to step 525. - The foregoing processes for new and old messages will continue until all of the messages on a given server have been processed. Once there are no more messages in the server, the process moves to step 527, in which all of the unmarked messages are deleted. These messages will include those that were blocked in
step 517 and those that were not marked insteps - Once the message sources have been processed,
poller 152 goes dormant until the next time polling is initiated. If the user is in session, then the message headers are displayed in step 541. The entire messages may also be displayed when prompted by the user (step 531). If the user is not in session, then nothing happens (step 545) until the user logs on or periodic polling is initiated. - In accordance with another embodiment, the entire message polled from the remote server (for example, remote server 115) is not cached in either step 515 or step 537, but rather is stored within
database 230. In addition, messages that are deleted from the remote server are not marked for deletion on the local server instep step 527.Communications server 105 saves the UIDs of messages deleted atcommunications server 105. The nexttime communications server 105 polls for messages, those messages identified with a deleted UID are not displayed to user.Communications server 105 retains the UIDs of messages deleted fromdatabase 230 until those messages are also deleted at the source (e.g., deleted from remote server 115). -
FIG. 6 is a screen shot depicting anHTML form 600 that a user fills in to establish a new mail filter rule.Form 600 appears when the user clicks on an “Add Blocking Filter” button. As is apparent from the screen shot, the user may block mail messages based on the sender, the subject, the mail source, the priority level, and/or the time at which the message was sent. - The “Filter Title” field in
form 600 is purely for user interface, and is not part of the filtering algorithm.Polling engine 210 will generally have already sorted the messages by source (e.g., user@home vs. user@work), so the specified mail serverscontrol polling engine 210, and do not controlfilter 215. This distinction is transparent to the user. -
Mail poller 152 blocks any message that matches any criterion offilter 215. The criteria in anyone filter are applied as a group using top-to-bottom inheritance. For example, the definition shown inFIG. 6 would block all low-priority messages sent during any weekday. - When
mail poller 152 encounters a match,mail poller 152 blocks the message without further tests.Mail poller 152 then stores the message UID of the blocked message in the user database for future reference. For a message retrieved from a remote mail server, where a copy still exists, the message header and body are flushed permanently from local memory. If a blocked message is retrieved from native mail (in which case no backup copy would otherwise exist), the message is placed into the user's deleted mail folder. - If the message passes all the blocking filters,
mail poller 152 stores both its UID and its header in database 220. In addition, if this particular call is taking place while the user is in session, the message body and attachments are cached for the duration of the session. -
Filter 215 inmail poller 152 looks for stream patterns in the “from” and “subject” fields. Streams are case-insensitive. The filter string need not be identical to the corresponding portion of the message, but the corresponding portion of the message must include the string. For example, if a message's “from” field reads: - “John Q. Doe”<jdoe1277@aol.com>, then “Doe”, “@aol.com”, and “e12” yield a match. Conversely, “John Doe” and “America Online” will not yield a match. It is important to note that is possible to block an entire domain by specifying something like “aol” in the “sender” yield.
- Filter 215 matches priorities using the “X-priority” field associated with conventional email messages. In database 220, the values for high, medium, and low priority are specified as 1, 0, and −1, respectively.
-
FIG. 7 is a block diagram ofdispatcher 154 ofFIGS. 1 and 2 .Dispatcher 154 includes a dispatchingfilter 700, amessage renderer 705, and amessage hound 710. -
Dispatching filter 700 allows the user to specify one or more forwarding addresses for messages that meet particular filtering requirements.FIG. 8 depicts anHTML form 800 that the user has filled out so thatdispatcher 154 forwards all urgent messages from co-workers if those messages are received on a Sunday. Before such dispatching can be accomplished, the user must enter a description of the device to which the messages are to be forwarded.FIG. 9 depicts anHTML form 900 that the user fills out to register a wireless receiving device, such as a pager or mobile phone, so thatdispatcher 154 can forward messages to the device. -
Form 900 allows the user to include the contents of the subject field, the identities of other users to whom the message was directed, and a limited number of characters from within the message body. This aspect ofform 900 is sometimes important for pagers, because some pager companies charge based on the amount of information conveyed to device. In the example ofFIG. 9 , the wireless device is a mobile phone, andmessage renderer 705 is instructed to include: 1) the subject, 2) the identities of other users receiving the message, and 3) up to 700 characters within the body of the message. -
Message renderer 705 allows users to set different dispatch parameters for different devices. For example,message renderer 705 may be configured to send less information to a pager than to a cellular phone, and to forward the entire contents of the message, including any attachments, if the message is forwarded to a personal computer or laptop.Renderer 705 also reformats messages as necessary to forward some or the entire message content to selected target receiving devices. In a typical example, a user may configurerenderer 705 to forward only the subject and sender of important messages to the user's mobile phone. - In one
embodiment message renderer 705 can reformat messages to include the phone number of the message sender. The reformatted message, when conveyed to the user's mobile phone, can then present the user with an option to return the message via a phone call. Wheredatabase 230 includes more than one phone number for the sender, the reformatted message can include more than one phone number. In someembodiments message renderer 705 prioritizes the sender's phone numbers for presentation to the user.Message renderer 705 can also reformat the message to include additional information about the contact, such as notes about the sender that might be of interest to the message recipient. These and other reply options are noted above. - The final element of
dispatcher 154 ismessage hound 710.Message hound 710 can be configured by the user to establish a hierarchy of devices to which selected messages might be forwarded. For example, the user can configuremessage hound 710 to forward all urgent messages to a mobile phone and, in the event that the mobile phone is turned off or otherwise out of service, then to send the same or a smaller version of the message to the user's pager.Message hound 710 can also be configured to include another email address, such as that of the user's secretary, in the hierarchy. -
FIG. 10 is aflowchart 1000 depicting an operation ofdispatcher 154 in the event the user has specified a dispatch rule as depicted inFIG. 8 . In the attached source code, the method fordispatcher 154 is “forwardMessage” in the file “FareWorker” in the source code of the attached CD Appendix. - At
step 1005, the user has filled out and submittedform 800, and consequently conveyed the information ofform 800 to database 230 (FIG. 2 ).Dispatcher 154, using the information stored indatabase 230, subjects subsequently received unblocked messages (step 1010, fromstep 517 offlowchart 500 ofFIG. 5 ) to the rules defined using form 800 (decision 1015). If the message meets the rules, then a version of the received message should be sent to the user's mobile phone. Regardless of whether the message meets the rules, the message's UID and header are added to the user's database (step 1020).Step 1020 is the same step identified atstep 523 inFIG. 5 . - If the message is to be forwarded to the user's mobile phone,
dispatcher 154 first attempts to contact the specified phone (step 1025). This attempt is made using the Short Messaging Service (SMS) protocol, a conventional protocol adapted for sending short messages to pagers and phones. Using SMS,dispatcher 154 can send a short alphanumeric message to the user's mobile phone. - Per
decision 1030, if the user's phone is unavailable (for example, where the phone is turned off or out of the service area), one embodiment of the invention reformats the message for receipt by a pager (step 1035) and then sends the reformatted message to the user's pager (step 1045). This embodiment is beneficial, as pagers generally provide a more robust means of communication than do mobile phones. - Returning to
decision 1030, if the mobile phone is available, the message is reformatted as necessary for transmission to the user's cellular phone (step 1040), in which case the reformatted message may include a reply number for the sender of the received message. Finally, the reformatted message is sent to the user's cellular phone (step 1050). - The entire message is preserved in the user's database regardless of whether all or a portion of the message is conveyed to one of the user's wireless devices. The user can therefore access the complete message later from e.g. a personal computer. Additionally, mail application 217 (
FIG. 2 ) responds to instructions from a mobile phone to forward a reformatted message by forwarding the original message stored indatabase 230. The recipient of the forwarded message is therefore not limited by the capabilities of the forwarding device. For example, a user away from his or her office may forward an urgent message containing an attachment to a nearby computer for viewing or printing. The code that supports this type of forwarding is identified at pages 446-469 of the attached source code as “PhoneComposeMessageHandler.” -
Message hound 710 can be set to dispatch messages to the next listed device upon receipt of a failure-to-deliver message, or can be set to dispatch the message if the intended recipient does not respond within a given time period. SMTP and WAP can be implemented to let the sender know whether the intended recipient received a message. One embodiment uses this information to report success or failure to the sender. For example,mail application 217 might report that the user's mobile phone was out of service and the user's pager has been alerted. - The foregoing specification and figures are high-level descriptions of some embodiments of the invention. The attached annotated source code details a specific embodiment. The code executes on a Solaris Sparc workstation on a UNIX platform. The messages, user preferences, email sources, and UIDs are stored on a database server, in one embodiment a Microsoft SQL server running on a Windows NT server machine.
- While the present invention has been described in connection with specific embodiments, variations of these embodiments will be obvious to those of ordinary skill in the art. For example, polling can be extended from mail sources to other info, such as local weather, sports, or stock quotes. Each embodiment extends to both methods as well as to structures and devices that carry out the methods. Therefore, the spirit and scope of the appended claims should not be limited to the foregoing description.
Claims (1)
1. A method comprising:
a. associating a phone number with an identity of a first user;
b. receiving a text message from the first user directed to a second user, the text message including the identity of the first user; and
c. responsive to the text message, automatically presenting the second user with an option to call the first user at the phone number.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/592,262 US20100106786A1 (en) | 2000-08-17 | 2009-11-20 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
US13/374,413 US8463862B2 (en) | 2000-08-17 | 2011-12-28 | Methods and systems for dispatching messages to mobile devices |
US13/986,823 US9479638B2 (en) | 2000-08-17 | 2013-06-07 | Methods and systems for dispatching messages to mobile devices |
US15/331,984 US20170142054A1 (en) | 2000-08-17 | 2016-10-24 | Methods and systems for dispatching messages to mobile devices |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/641,551 US6779022B1 (en) | 2000-08-17 | 2000-08-17 | Server that obtains information from multiple sources, filters using client identities, and dispatches to both hardwired and wireless clients |
US10/921,733 US7062538B2 (en) | 2000-08-17 | 2004-08-17 | Server that obtains information from multiple sources, filters using client indentities, and dispatches to both hardwired and wireless clients |
US45164606A | 2006-06-12 | 2006-06-12 | |
US11/724,918 US7546351B1 (en) | 2000-08-17 | 2007-03-15 | Methods and systems for filtering, sorting, and dispatching messages to wired and wireless devices |
US11/796,591 US7627642B1 (en) | 2000-08-17 | 2007-04-26 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
US12/592,262 US20100106786A1 (en) | 2000-08-17 | 2009-11-20 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/796,591 Continuation US7627642B1 (en) | 2000-08-17 | 2007-04-26 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/374,413 Continuation US8463862B2 (en) | 2000-08-17 | 2011-12-28 | Methods and systems for dispatching messages to mobile devices |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100106786A1 true US20100106786A1 (en) | 2010-04-29 |
Family
ID=40688802
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/724,918 Expired - Fee Related US7546351B1 (en) | 2000-08-17 | 2007-03-15 | Methods and systems for filtering, sorting, and dispatching messages to wired and wireless devices |
US11/796,591 Expired - Fee Related US7627642B1 (en) | 2000-08-17 | 2007-04-26 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
US12/592,262 Abandoned US20100106786A1 (en) | 2000-08-17 | 2009-11-20 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
US13/374,413 Expired - Fee Related US8463862B2 (en) | 2000-08-17 | 2011-12-28 | Methods and systems for dispatching messages to mobile devices |
US13/986,823 Expired - Fee Related US9479638B2 (en) | 2000-08-17 | 2013-06-07 | Methods and systems for dispatching messages to mobile devices |
US15/331,984 Abandoned US20170142054A1 (en) | 2000-08-17 | 2016-10-24 | Methods and systems for dispatching messages to mobile devices |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/724,918 Expired - Fee Related US7546351B1 (en) | 2000-08-17 | 2007-03-15 | Methods and systems for filtering, sorting, and dispatching messages to wired and wireless devices |
US11/796,591 Expired - Fee Related US7627642B1 (en) | 2000-08-17 | 2007-04-26 | Methods and systems for automatically presenting users with option to call sender responsive to email message |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/374,413 Expired - Fee Related US8463862B2 (en) | 2000-08-17 | 2011-12-28 | Methods and systems for dispatching messages to mobile devices |
US13/986,823 Expired - Fee Related US9479638B2 (en) | 2000-08-17 | 2013-06-07 | Methods and systems for dispatching messages to mobile devices |
US15/331,984 Abandoned US20170142054A1 (en) | 2000-08-17 | 2016-10-24 | Methods and systems for dispatching messages to mobile devices |
Country Status (1)
Country | Link |
---|---|
US (6) | US7546351B1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050223074A1 (en) * | 2004-03-31 | 2005-10-06 | Morris Robert P | System and method for providing user selectable electronic message action choices and processing |
US20100281224A1 (en) * | 2009-05-01 | 2010-11-04 | International Buisness Machines Corporation | Prefetching content from incoming messages |
WO2012027305A3 (en) * | 2010-08-23 | 2012-04-19 | Daly Kevin C | A private mobile messaging and data communications apparatus and method of managing organizational messaging |
FR2978573A1 (en) * | 2011-07-27 | 2013-02-01 | Poste | METHOD OF MATCHING DATA AND USE IN IDENTITY VERIFICATION OF A RECIPIENT OF A MAIL |
US20160234729A1 (en) * | 2007-05-30 | 2016-08-11 | Apple Inc. | Method and Apparatus for Security Configuration and Verification of Wireless Devices in a Fixed/Mobile Convergence Environment |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7546351B1 (en) | 2000-08-17 | 2009-06-09 | Mxgo | Methods and systems for filtering, sorting, and dispatching messages to wired and wireless devices |
US7698433B2 (en) | 2001-03-20 | 2010-04-13 | Verizon Business Global Llc | User aliases in communication system |
US7730143B1 (en) * | 2004-12-01 | 2010-06-01 | Aol Inc. | Prohibiting mobile forwarding |
US8103509B2 (en) * | 2006-12-05 | 2012-01-24 | Mobile Voice Control, LLC | Wireless server based text to speech email |
EP1981230B1 (en) * | 2007-04-13 | 2011-08-31 | TeamOn Systems Inc. | Direct access electronic mail (email) distribution and synchronization system with external SMTP server support |
US20110060996A1 (en) * | 2009-09-10 | 2011-03-10 | Alberth Jr William P | Method and System for Reducing Notifications to a Mobile Device in Accordance with User Preferences |
KR101664430B1 (en) * | 2009-11-13 | 2016-10-10 | 삼성전자주식회사 | Method and apparatus for providing remote UI service |
US20110217954A1 (en) * | 2010-03-03 | 2011-09-08 | Htc Corporation | Method, system, and mobile device for managing messages and computer-readable medium using the method |
US8503629B2 (en) | 2010-03-26 | 2013-08-06 | Google Inc. | Computing device with remote contact lists |
JP4879361B1 (en) * | 2011-04-28 | 2012-02-22 | 楽天株式会社 | E-mail system, e-mail system control method, relay device, program, and information storage medium |
US20130282844A1 (en) * | 2012-04-23 | 2013-10-24 | Contact Solutions LLC | Apparatus and methods for multi-mode asynchronous communication |
US9373093B2 (en) * | 2013-11-07 | 2016-06-21 | Sap Se | Gateway service manager for business object applications |
DE102014003520A1 (en) * | 2014-03-16 | 2015-09-17 | Tobias Rückert | Method and system for processing an electronic message |
US20180331984A1 (en) * | 2017-05-10 | 2018-11-15 | Rachel McCall | Encrypted Pixilated Color(s) Communication Message Translator |
US11528242B2 (en) * | 2020-10-23 | 2022-12-13 | Abnormal Security Corporation | Discovering graymail through real-time analysis of incoming email |
Citations (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5577202A (en) * | 1992-08-24 | 1996-11-19 | Trw Inc. | Message handling system for automated gateway between first and second handling systems wherein first envelope is added to a second envelope respectively without changing text |
US5717742A (en) * | 1993-06-22 | 1998-02-10 | Vmx, Inc. | Electronic mail system having integrated voice messages |
US5844969A (en) * | 1997-01-23 | 1998-12-01 | At&T Corp. | Communication system, method and device for remotely re-transmitting received electronic mail directed to a destination terminal to a new destination terminal |
US5956521A (en) * | 1995-06-26 | 1999-09-21 | Wang; Kevin Kuan-Pin | System for universal electronic mail delivery where messaging devices are notified using a particular dialing, ringing, and hanging-up pattern |
US6052709A (en) * | 1997-12-23 | 2000-04-18 | Bright Light Technologies, Inc. | Apparatus and method for controlling delivery of unsolicited electronic mail |
US6087959A (en) * | 1998-05-26 | 2000-07-11 | Diablo Research Company, Llc | Optically coupled gas meter |
US6097941A (en) * | 1997-12-12 | 2000-08-01 | Helferich; Richard J. | User interface for voice message access |
US6138146A (en) * | 1997-09-29 | 2000-10-24 | Ericsson Inc. | Electronic mail forwarding system and method |
US6169911B1 (en) * | 1997-09-26 | 2001-01-02 | Sun Microsystems, Inc. | Graphical user interface for a portable telephone |
US6199102B1 (en) * | 1997-08-26 | 2001-03-06 | Christopher Alan Cobb | Method and system for filtering electronic messages |
US6233430B1 (en) * | 1997-09-19 | 2001-05-15 | Richard J. Helferich | Paging transceivers and methods for selectively retrieving messages |
US6253061B1 (en) * | 1997-09-19 | 2001-06-26 | Richard J. Helferich | Systems and methods for delivering information to a transmitting and receiving device |
US6259892B1 (en) * | 1997-09-19 | 2001-07-10 | Richard J. Helferich | Pager transceiver and methods for performing action on information at desired times |
US6298128B1 (en) * | 1999-03-11 | 2001-10-02 | Thomson Licensing S.A. | Unified directory for caller ID and electronic mail addresses |
US6311231B1 (en) * | 1995-09-25 | 2001-10-30 | Thomas Howard Bateman | Method and system for coordinating data and voice communications via customer contract channel changing system using voice over IP |
US6321267B1 (en) * | 1999-11-23 | 2001-11-20 | Escom Corporation | Method and apparatus for filtering junk email |
US20020016818A1 (en) * | 2000-05-11 | 2002-02-07 | Shekhar Kirani | System and methodology for optimizing delivery of email attachments for disparate devices |
US20020023143A1 (en) * | 2000-04-11 | 2002-02-21 | Stephenson Mark M. | System and method for projecting content beyond firewalls |
US6351523B1 (en) * | 1999-03-22 | 2002-02-26 | Sharp Laboratories Of America, Inc. | Method and apparatus for management of EMail originated by thin client devices |
US20020024947A1 (en) * | 2000-11-03 | 2002-02-28 | Omer Luzzatti | Communications availability |
US20020026500A1 (en) * | 2000-06-12 | 2002-02-28 | Kanefsky Steven T. | Method and apparatus for sharing wireless content |
US20020078198A1 (en) * | 2000-02-25 | 2002-06-20 | Buchbinder John E. | Personal server technology with firewall detection and penetration |
US6438583B1 (en) * | 1999-06-23 | 2002-08-20 | Re-Route Corporation | System and method for re-routing of e-mail messages |
US20030026393A1 (en) * | 2000-02-29 | 2003-02-06 | Julia Skladman | Method and system for interfacing systems unified messaging with legacy systems located behind corporate firewalls |
US6563912B1 (en) * | 1999-03-02 | 2003-05-13 | Toshiba America Information Systems, Inc. | System and method for providing integrated messaging |
US20030104827A1 (en) * | 2001-11-30 | 2003-06-05 | Brian Moran | Rerouting/reformating wireless messages for cross connectivity between service providers |
US6606647B2 (en) * | 1999-01-11 | 2003-08-12 | Infospace, Inc. | Server and method for routing messages to achieve unified communications |
US6636733B1 (en) * | 1997-09-19 | 2003-10-21 | Thompson Trust | Wireless messaging method |
US6654787B1 (en) * | 1998-12-31 | 2003-11-25 | Brightmail, Incorporated | Method and apparatus for filtering e-mail |
US6708217B1 (en) * | 2000-01-05 | 2004-03-16 | International Business Machines Corporation | Method and system for receiving and demultiplexing multi-modal document content |
US6725269B1 (en) * | 1999-12-02 | 2004-04-20 | International Business Machines Corporation | System and method for maintaining multiple identities and reputations for internet interactions |
US6741980B1 (en) * | 1999-03-23 | 2004-05-25 | Microstrategy Inc. | System and method for automatic, real-time delivery of personalized informational and transactional data to users via content delivery device |
US6779022B1 (en) * | 2000-08-17 | 2004-08-17 | Jens Horstmann | Server that obtains information from multiple sources, filters using client identities, and dispatches to both hardwired and wireless clients |
US20040205198A1 (en) * | 2000-06-30 | 2004-10-14 | Zellner Samuel N. | Anonymous location service for wireless networks |
US6826407B1 (en) * | 1999-03-29 | 2004-11-30 | Richard J. Helferich | System and method for integrating audio and visual messaging |
US20050064850A1 (en) * | 2000-09-29 | 2005-03-24 | Postini, Inc | E-mail filtering services and e-mail service enrollment techniques |
US20050089052A1 (en) * | 2000-01-31 | 2005-04-28 | 3E Technologies International, Inc. | Broadband communications access device |
US6961751B1 (en) * | 2000-05-31 | 2005-11-01 | International Business Machines Corporation | Method, apparatus, and article of manufacture for providing enhanced bookmarking features for a heterogeneous environment |
US7003327B1 (en) * | 1999-07-23 | 2006-02-21 | Openwave Systems Inc. | Heuristically assisted user interface for a wireless communication device |
US7003546B1 (en) * | 1998-10-13 | 2006-02-21 | Chris Cheah | Method and system for controlled distribution of contact information over a network |
US7130298B1 (en) * | 2000-07-20 | 2006-10-31 | Verizon Corporate Services Group Inc. | Systems and methods implementing internet screen dialing for circuit switched telephones |
US20060245425A1 (en) * | 2005-04-28 | 2006-11-02 | Mathis James E | Method of access to a channelized network from a packet data network |
US7225409B1 (en) * | 1998-08-26 | 2007-05-29 | Microsoft Corporation | Graphical user interface for a screen telephone |
US7231423B1 (en) * | 2001-05-23 | 2007-06-12 | Jens Horstmann | Interactive wireless device communication system for meetings and conferences |
US20070233806A1 (en) * | 2006-03-29 | 2007-10-04 | Mehrzad Asadi | Method and system for conducting an internet search using a mobile radio terminal |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5825865A (en) | 1991-10-04 | 1998-10-20 | Motorola, Inc. | Temporary message routing and destination selection |
JP3168756B2 (en) | 1993-02-24 | 2001-05-21 | ミノルタ株式会社 | Email management method of email system |
US5493692A (en) | 1993-12-03 | 1996-02-20 | Xerox Corporation | Selective delivery of electronic messages in a multiple computer system based on context and environment of a user |
US5604788A (en) | 1995-03-16 | 1997-02-18 | Motorola, Inc. | Wireless messaging system with electronic mail replication |
US6101531A (en) | 1995-12-19 | 2000-08-08 | Motorola, Inc. | System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless client |
US5781901A (en) | 1995-12-21 | 1998-07-14 | Intel Corporation | Transmitting electronic mail attachment over a network using a e-mail page |
US5903723A (en) | 1995-12-21 | 1999-05-11 | Intel Corporation | Method and apparatus for transmitting electronic mail attachments with attachment references |
US5937161A (en) | 1996-04-12 | 1999-08-10 | Usa.Net, Inc. | Electronic message forwarding system |
US5790790A (en) | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
US5995597A (en) | 1997-01-21 | 1999-11-30 | Woltz; Robert Thomas | E-mail processing system and method |
US5961590A (en) | 1997-04-11 | 1999-10-05 | Roampage, Inc. | System and method for synchronizing electronic mail between a client site and a central site |
US6073165A (en) | 1997-07-29 | 2000-06-06 | Jfax Communications, Inc. | Filtering computer network messages directed to a user's e-mail box based on user defined filters, and forwarding a filtered message to the user's receiver |
US6087956A (en) | 1997-09-19 | 2000-07-11 | Helferich; Richard J. | Paging transceivers and methods for selectively erasing information |
US6272545B1 (en) | 1997-10-24 | 2001-08-07 | Microsoft Corporation | System and method for interaction between one or more desktop computers and one or more mobile devices |
US6115754A (en) | 1997-12-29 | 2000-09-05 | Nortel Networks Limited | System and method for appending location information to a communication sent from a mobile terminal operating in a wireless communication system to an internet server |
US6195533B1 (en) | 1998-05-27 | 2001-02-27 | Glenayre Electronics, Inc. | Method for storing an application's transaction data in a wireless messaging system |
US6219694B1 (en) | 1998-05-29 | 2001-04-17 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device having a shared electronic address |
US6438585B2 (en) | 1998-05-29 | 2002-08-20 | Research In Motion Limited | System and method for redirecting message attachments between a host system and a mobile data communication device |
WO1999065256A2 (en) | 1998-06-10 | 1999-12-16 | Logica, Inc. | System and method for delivering e-mail notification to mobile phones |
GB2338862B (en) | 1998-06-25 | 2003-08-06 | Virtualplus Ltd | A unified messaging system |
US6275850B1 (en) | 1998-07-24 | 2001-08-14 | Siemens Information And Communication Networks, Inc. | Method and system for management of message attachments |
US6389455B1 (en) | 1998-09-22 | 2002-05-14 | Richard C. Fuisz | Method and apparatus for bouncing electronic messages |
GB2342196A (en) | 1998-09-30 | 2000-04-05 | Xerox Corp | System for generating context-sensitive hierarchically-ordered document service menus |
US6442589B1 (en) | 1999-01-14 | 2002-08-27 | Fujitsu Limited | Method and system for sorting and forwarding electronic messages and other data |
US6965918B1 (en) | 1999-04-30 | 2005-11-15 | International Business Machines Corporation | System and method for integrated management of electronic messages |
US6393107B1 (en) * | 1999-05-25 | 2002-05-21 | Lucent Technologies Inc. | Method and apparatus for creating and sending structured voicemail messages |
US20020112007A1 (en) | 1999-11-03 | 2002-08-15 | Christopher (Noah) Wood | Personal message management system |
US7430554B1 (en) * | 2000-04-07 | 2008-09-30 | Heisinger Jr Charles Gilbert | Method and system for telephonically selecting, addressing, and distributing messages |
US7546351B1 (en) | 2000-08-17 | 2009-06-09 | Mxgo | Methods and systems for filtering, sorting, and dispatching messages to wired and wireless devices |
GB0508847D0 (en) | 2005-04-29 | 2005-06-08 | Nokia Corp | A network |
-
2007
- 2007-03-15 US US11/724,918 patent/US7546351B1/en not_active Expired - Fee Related
- 2007-04-26 US US11/796,591 patent/US7627642B1/en not_active Expired - Fee Related
-
2009
- 2009-11-20 US US12/592,262 patent/US20100106786A1/en not_active Abandoned
-
2011
- 2011-12-28 US US13/374,413 patent/US8463862B2/en not_active Expired - Fee Related
-
2013
- 2013-06-07 US US13/986,823 patent/US9479638B2/en not_active Expired - Fee Related
-
2016
- 2016-10-24 US US15/331,984 patent/US20170142054A1/en not_active Abandoned
Patent Citations (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5577202A (en) * | 1992-08-24 | 1996-11-19 | Trw Inc. | Message handling system for automated gateway between first and second handling systems wherein first envelope is added to a second envelope respectively without changing text |
US5717742A (en) * | 1993-06-22 | 1998-02-10 | Vmx, Inc. | Electronic mail system having integrated voice messages |
US5956521A (en) * | 1995-06-26 | 1999-09-21 | Wang; Kevin Kuan-Pin | System for universal electronic mail delivery where messaging devices are notified using a particular dialing, ringing, and hanging-up pattern |
US6311231B1 (en) * | 1995-09-25 | 2001-10-30 | Thomas Howard Bateman | Method and system for coordinating data and voice communications via customer contract channel changing system using voice over IP |
US5844969A (en) * | 1997-01-23 | 1998-12-01 | At&T Corp. | Communication system, method and device for remotely re-transmitting received electronic mail directed to a destination terminal to a new destination terminal |
US6199102B1 (en) * | 1997-08-26 | 2001-03-06 | Christopher Alan Cobb | Method and system for filtering electronic messages |
US6233430B1 (en) * | 1997-09-19 | 2001-05-15 | Richard J. Helferich | Paging transceivers and methods for selectively retrieving messages |
US6636733B1 (en) * | 1997-09-19 | 2003-10-21 | Thompson Trust | Wireless messaging method |
US6259892B1 (en) * | 1997-09-19 | 2001-07-10 | Richard J. Helferich | Pager transceiver and methods for performing action on information at desired times |
US6253061B1 (en) * | 1997-09-19 | 2001-06-26 | Richard J. Helferich | Systems and methods for delivering information to a transmitting and receiving device |
US6169911B1 (en) * | 1997-09-26 | 2001-01-02 | Sun Microsystems, Inc. | Graphical user interface for a portable telephone |
US6138146A (en) * | 1997-09-29 | 2000-10-24 | Ericsson Inc. | Electronic mail forwarding system and method |
US6097941A (en) * | 1997-12-12 | 2000-08-01 | Helferich; Richard J. | User interface for voice message access |
US6052709A (en) * | 1997-12-23 | 2000-04-18 | Bright Light Technologies, Inc. | Apparatus and method for controlling delivery of unsolicited electronic mail |
US6087959A (en) * | 1998-05-26 | 2000-07-11 | Diablo Research Company, Llc | Optically coupled gas meter |
US7225409B1 (en) * | 1998-08-26 | 2007-05-29 | Microsoft Corporation | Graphical user interface for a screen telephone |
US7003546B1 (en) * | 1998-10-13 | 2006-02-21 | Chris Cheah | Method and system for controlled distribution of contact information over a network |
US6654787B1 (en) * | 1998-12-31 | 2003-11-25 | Brightmail, Incorporated | Method and apparatus for filtering e-mail |
US6606647B2 (en) * | 1999-01-11 | 2003-08-12 | Infospace, Inc. | Server and method for routing messages to achieve unified communications |
US6563912B1 (en) * | 1999-03-02 | 2003-05-13 | Toshiba America Information Systems, Inc. | System and method for providing integrated messaging |
US6298128B1 (en) * | 1999-03-11 | 2001-10-02 | Thomson Licensing S.A. | Unified directory for caller ID and electronic mail addresses |
US6351523B1 (en) * | 1999-03-22 | 2002-02-26 | Sharp Laboratories Of America, Inc. | Method and apparatus for management of EMail originated by thin client devices |
US6741980B1 (en) * | 1999-03-23 | 2004-05-25 | Microstrategy Inc. | System and method for automatic, real-time delivery of personalized informational and transactional data to users via content delivery device |
US6826407B1 (en) * | 1999-03-29 | 2004-11-30 | Richard J. Helferich | System and method for integrating audio and visual messaging |
US6438583B1 (en) * | 1999-06-23 | 2002-08-20 | Re-Route Corporation | System and method for re-routing of e-mail messages |
US7003327B1 (en) * | 1999-07-23 | 2006-02-21 | Openwave Systems Inc. | Heuristically assisted user interface for a wireless communication device |
US6321267B1 (en) * | 1999-11-23 | 2001-11-20 | Escom Corporation | Method and apparatus for filtering junk email |
US6725269B1 (en) * | 1999-12-02 | 2004-04-20 | International Business Machines Corporation | System and method for maintaining multiple identities and reputations for internet interactions |
US6708217B1 (en) * | 2000-01-05 | 2004-03-16 | International Business Machines Corporation | Method and system for receiving and demultiplexing multi-modal document content |
US20050089052A1 (en) * | 2000-01-31 | 2005-04-28 | 3E Technologies International, Inc. | Broadband communications access device |
US20020078198A1 (en) * | 2000-02-25 | 2002-06-20 | Buchbinder John E. | Personal server technology with firewall detection and penetration |
US20030026393A1 (en) * | 2000-02-29 | 2003-02-06 | Julia Skladman | Method and system for interfacing systems unified messaging with legacy systems located behind corporate firewalls |
US20020023143A1 (en) * | 2000-04-11 | 2002-02-21 | Stephenson Mark M. | System and method for projecting content beyond firewalls |
US20020016818A1 (en) * | 2000-05-11 | 2002-02-07 | Shekhar Kirani | System and methodology for optimizing delivery of email attachments for disparate devices |
US6961751B1 (en) * | 2000-05-31 | 2005-11-01 | International Business Machines Corporation | Method, apparatus, and article of manufacture for providing enhanced bookmarking features for a heterogeneous environment |
US20020026500A1 (en) * | 2000-06-12 | 2002-02-28 | Kanefsky Steven T. | Method and apparatus for sharing wireless content |
US20040205198A1 (en) * | 2000-06-30 | 2004-10-14 | Zellner Samuel N. | Anonymous location service for wireless networks |
US7130298B1 (en) * | 2000-07-20 | 2006-10-31 | Verizon Corporate Services Group Inc. | Systems and methods implementing internet screen dialing for circuit switched telephones |
US7062538B2 (en) * | 2000-08-17 | 2006-06-13 | Jens Horstmann | Server that obtains information from multiple sources, filters using client indentities, and dispatches to both hardwired and wireless clients |
US6779022B1 (en) * | 2000-08-17 | 2004-08-17 | Jens Horstmann | Server that obtains information from multiple sources, filters using client identities, and dispatches to both hardwired and wireless clients |
US20050004992A1 (en) * | 2000-08-17 | 2005-01-06 | Horstmann Jens U. | Server that obtains information from multiple sources, filters using client identities, and dispatches to both hardwired and wireless clients |
US20050064850A1 (en) * | 2000-09-29 | 2005-03-24 | Postini, Inc | E-mail filtering services and e-mail service enrollment techniques |
US20060155808A1 (en) * | 2000-09-29 | 2006-07-13 | Postini, Inc. | E-mail filtering services using Internet protocol routing information |
US20020024947A1 (en) * | 2000-11-03 | 2002-02-28 | Omer Luzzatti | Communications availability |
US7231423B1 (en) * | 2001-05-23 | 2007-06-12 | Jens Horstmann | Interactive wireless device communication system for meetings and conferences |
US20030104827A1 (en) * | 2001-11-30 | 2003-06-05 | Brian Moran | Rerouting/reformating wireless messages for cross connectivity between service providers |
US20060245425A1 (en) * | 2005-04-28 | 2006-11-02 | Mathis James E | Method of access to a channelized network from a packet data network |
US20070233806A1 (en) * | 2006-03-29 | 2007-10-04 | Mehrzad Asadi | Method and system for conducting an internet search using a mobile radio terminal |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050223074A1 (en) * | 2004-03-31 | 2005-10-06 | Morris Robert P | System and method for providing user selectable electronic message action choices and processing |
US9867044B2 (en) * | 2007-05-30 | 2018-01-09 | Apple Inc. | Method and apparatus for security configuration and verification of wireless devices in a fixed/mobile convergence environment |
US20160234729A1 (en) * | 2007-05-30 | 2016-08-11 | Apple Inc. | Method and Apparatus for Security Configuration and Verification of Wireless Devices in a Fixed/Mobile Convergence Environment |
US20100281224A1 (en) * | 2009-05-01 | 2010-11-04 | International Buisness Machines Corporation | Prefetching content from incoming messages |
US20130086197A1 (en) * | 2009-05-01 | 2013-04-04 | International Business Machines Corporation | Managing cache at a computer |
US10264094B2 (en) * | 2009-05-01 | 2019-04-16 | International Business Machines Corporation | Processing incoming messages |
US9454506B2 (en) * | 2009-05-01 | 2016-09-27 | International Business Machines Corporation | Managing cache at a computer |
US20160360003A1 (en) * | 2009-05-01 | 2016-12-08 | International Business Machines Corporation | Processing incoming messages |
WO2012027305A3 (en) * | 2010-08-23 | 2012-04-19 | Daly Kevin C | A private mobile messaging and data communications apparatus and method of managing organizational messaging |
US8812607B2 (en) | 2010-08-23 | 2014-08-19 | Maxxess Systems, Inc. | Private mobile messaging and data communications apparatus and method of managing organizational messaging |
US9705841B2 (en) | 2010-08-23 | 2017-07-11 | Maxxess Systems, Inc. | Private mobile messaging and data communications apparatus and method of managing organizational messaging |
FR2978573A1 (en) * | 2011-07-27 | 2013-02-01 | Poste | METHOD OF MATCHING DATA AND USE IN IDENTITY VERIFICATION OF A RECIPIENT OF A MAIL |
US9081811B2 (en) | 2011-07-27 | 2015-07-14 | La Poste | Method of matching data and use in the verification of identity of a recipient of a mail |
Also Published As
Publication number | Publication date |
---|---|
US9479638B2 (en) | 2016-10-25 |
US20140287731A1 (en) | 2014-09-25 |
US7546351B1 (en) | 2009-06-09 |
US8463862B2 (en) | 2013-06-11 |
US20170142054A1 (en) | 2017-05-18 |
US7627642B1 (en) | 2009-12-01 |
US20120100840A1 (en) | 2012-04-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9479638B2 (en) | Methods and systems for dispatching messages to mobile devices | |
US7062538B2 (en) | Server that obtains information from multiple sources, filters using client indentities, and dispatches to both hardwired and wireless clients | |
US7076241B1 (en) | System and method for selectively transmitting electronic messages | |
US9462046B2 (en) | Degrees of separation for handling communications | |
US7181495B2 (en) | Method and system for filtering notification of e-mail messages | |
US8583744B2 (en) | System and method for pushing information from a host system to a mobile data communication device | |
AU2001296473B2 (en) | Value-added electronic messaging services and transparent implementation thereof using intermediate server | |
US8606854B2 (en) | System and method for opportunistic image sharing | |
US11888805B2 (en) | Method and apparatus for storing email messages | |
US20020120748A1 (en) | Method and apparatus for selective delivery and forwarding of electronic mail | |
US20030208547A1 (en) | Direct internet mail access through links in wireless instant messaging systems | |
US7030730B1 (en) | System and method for formatting an electronic message | |
US20060086798A1 (en) | Deferred email message system and service | |
WO2007031963A2 (en) | Platform for intelligent message management | |
KR101124843B1 (en) | Message Relay System and Method of Thereof | |
US20040184613A1 (en) | Method of safely sending e-mails over LAN | |
KR20040082485A (en) | Method and apparatus for performing the process such as re-transmittance of the saved spam mail and modification of the spam rule, and computer readable medium on which program for executing the method is recorded | |
AU2007203464A1 (en) | Method and system for Mobile Messaging | |
KR20020024293A (en) | Multiple mail delivery method under the downmail system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MXGO TECHNOLOGIES, INC.,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HORSTMANN, JENS U.;REEL/FRAME:023600/0774 Effective date: 20060605 |
|
AS | Assignment |
Owner name: MXGO TECHNOLOGIES, INC.,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TANG, VINCENT L., MR.;REEL/FRAME:024125/0407 Effective date: 20010831 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |