Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Mobile-Side Configurable Pseudo-Email and Phone-Call Receiving Filter for Alerting Users Intelligently Based on Different Personal Preferences and Email Priority Levels

IP.com Disclosure Number: IPCOM000130466D
Publication Date: 2005-Oct-31
Document File: 3 page(s) / 42K

Publishing Venue

The IP.com Prior Art Database

Abstract

Email priority categorization differ from person to person, for example, one scenario may be: A . higher priority emails from my superior (CEO, manager, etc.) and high priority messages sent by any other sender B. low priority message that the user sets (i.e., CNN news, association group messages, old project email group) C. regular emails (i.e., all other company mail, messages from customers / vendors, new messages) Consider the following characteristics: 1). All different emails received will cause a mobile device to instantly alert the user the same way, any time, 365 days a year, 24 hours a day, regardless of their different importance levels. Some mobile users may be alerted hundreds of times a day. This may be a distraction from their daily jobs. Furthermore, users may not be able to afford to set the device in "Silent Profile" mode. 2). Instant alerting of high priority or regular emails may be necessary and is often appreciated. Instant alerting of low priority message is not needed. Users may want to check these at their own free time. 3). In certain instances, only higher priority messages are required (e.g., sleep time, during 1-day-long meeting or expensive training). 4) The concept of "always instant alerting" is good for some users, but may not be good for other users (i.e., people bombarded with too many emails a day) One proposed solution is to use "pseudo-filtering". Psuedo-filtering is used for user-alerting control. It enables a mobile device to systematically receive more-important and/or higher-priority messages, yet may not alert the user immediately. The user can read, process the message or act on it at his/her convenience. This pseudo-filter is different from that "solid filter" that is implemented on email servers or data redirection servers. Messages or senders hitting the solid filter that are on a blacklist (i.e., spam filter) may not be received by a mobile device. The proposed solution consists of the following: 1. Adding a new application feature to let users do a pseudo filtering mobile device. For example, enabling users an editable UI like this: Highest (Always) Alerting: (List A) [Boss] boss@company.com [Manager] manager@company.com [value customer at T-Mobile] importantguy@t-mobile.com Regular (Conditional) Alerting: (List B.1) [Company Domain] @company.com [Customer Domain] @tmobile.com Silent Time: (List B.1) weekends public holidays my vacation days deep night sleep time Aug 30,2004 - ABC Training (all day event) Sep 28, 2004 - Quaterly Project Meeting (all day event) Lowest (Never) Alerting: (List C) *@yahoo.com *@ieee.org *@creaders.net 2. List A has the highest alerting level for the emails that will ALWAYS alert the user when received. List B.1 has regular alerting level for emails that will CONDITIONALLY alert the user when received in the time other than those in List B.2; and won't alert the user when received in the time of List B.2. List C has the lowest alerting level for emails that will NEVER alert the user when received. 3. "Email address item" in List A, B.1, C can be input/edited from a qwerty keypad or imported from an existing Address Book entry. 4. "Silent Time item" in List B.2 can be input/edited from a qwerty keypad or imported from an existing calendar entry. Once the time has become the past, it will be deleted automatically from the list. 5. Any email address of a received email not in the above list is treated as a "Default address item" which belongs to List B.1. 6. The "Alerting" style (loud, vibrating, silent, tone, personalized tones, etc.) is subject to the setting of the "Profile" configuration to maintain compatibility. 7. The above ideas 1-6 can be reused for the alerting control of incoming phone calls. A possible editable UI is as follows: Highest (Always) Alerting: (List A) 456-883-7465 (boss' Tel #) 847-666-6000 (value/big customer Tel#) 416-789-5555 (a special private Tel#) 862-122-4892 (parents Tel#) 219-889-0104 (home) Regular (Conditional) Alerting: (List B.1) (all other numbers, default) Silent Time: (List B.2) 11:30 pm - 6:30 am Daily deep night sleep time Aug 30,2004 - UMTS Training (all day event) Sep 28, 2004 - Quarterly Project Meeting (all day event) Aug 6, 2004, Friday, 7:00 pm - 11:00 pm (not this moment) Lowest (Never) Alerting: (List C) 419-123-4567 (unwanted ex-girl friend) 419-444-4444 (unwanted harassing calls at midnight) 8. With above solution, users will have all the wanted convenience and control to maintain personal preference & comply with personalizable requirements.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 43% of the total text.

PSEUDO RX ALERTING FILTER ON

MOBILE

TERMINAL SIDE

Mobile-Side Configurable Pseudo-Email and Phone-Call Receiving Filter for Alerting Users Intelligently Based on Different Personal Preferences and Email Priority Levels

Disclosed Anonymously

Email priority categorization differ from person to person, for example, one scenario may be:

        A . higher priority emails from my superior (CEO, manager, etc.) and high priority messages sent by any other sender

        B.  low priority message that the user sets (i.e., CNN news, association group messages, old      

project email group)

        C.  regular emails (i.e., all other company mail, messages from customers / vendors, new messages)

Consider the following characteristics:

1). All different emails received will cause a mobile device to instantly alert the user the same way, any time, 365 days a year, 24 hours a day, regardless of their different importance levels. Some mobile users may be alerted hundreds of times a day. This may be a distraction from their daily jobs. Furthermore, users may not be able to afford to set the device in "Silent Profile" mode.

2). Instant alerting of high priority or regular emails may be necessary and is often appreciated. Instant alerting of low priority message is not needed. Users may want to check these at their own free time.

3). In certain instances, only higher priority messages are required (e.g., sleep time, during 1-day-long meeting or expensive training).

 

4) The concept of "always instant alerting" is good for some users, but may not be good for other users (i.e., people bombarded with too many emails a day)

One proposed solution is to use "pseudo-filtering". Psuedo-filtering is used for user-alerting control. It enables a mobile device to systematically receive more-important and/or higher-priority messages, yet may not alert the user immediately. The user can read, process the message or act on it at his/her convenience.

This pseudo-filter is different from that "solid filter" that is implemented on email servers or data redirection servers. Messages or senders hitting the solid filter that are on a blacklist (i.e., spam filter) may not be received by a mobile device.

The proposed solution consists of the following:

1. Adding a new application feature to let users do a pseudo filtering mobile device. For example, enabling users an editable UI like this:

     Highest (Always) Alerting: (List A)

                                   [Boss] boss@company.com

                                   [Manager] manager@company.com

                                   [value customer at T-Mobile] importantguy@t-mobile.com

 

    Regular (Conditional) Alerting: (List B.1)

                                                     

                          ...