Mobile Notification Exception Profiles for Event-Driven Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile devices lack the ability to provide unique notifications based on specific attributes or characteristics of device events, such as sender identity, email characteristics, time, and calendar events, leading to intrusive notifications in various environments.
Innovation Solution
A system and method that allows users to create and manage exception profiles on mobile devices, enabling customized notifications for specific contacts, email characteristics, time, and calendar events without requiring filter rules on the mail server side, using a user interface to associate attributes with custom notifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If standard notification profiles are used for all device events, then device complexity is reduced and ease of operation is improved, but the ability to provide unique notifications based on event attributes is lost
Solution Approach 1:
The notification system is segmented into multiple independent profiles, each associated with specific event attributes (sender identity, email characteristics, time, calendar events). Users can create and manage multiple notification profiles with different settings, and the system automatically selects the appropriate profile based on the event attributes, providing customization without requiring complex manual configuration for each event type.
Solution Approach 2:
Different notification profiles are applied to different event attributes or characteristics. Each profile has localized settings tailored to specific situations (e.g., silent notifications for meeting room events, standard notifications for regular events), allowing customization at the local level while maintaining overall system simplicity.
2Adaptability or versatility
If multiple notification profiles are created for different event attributes, then notification adaptability is improved, but device complexity increases
Solution Approach 1:
Users pre-configure multiple notification profiles with different settings before actual use. Each profile is associated with specific event attributes in advance (e.g., assigning a silent profile to meeting-related events). When an event occurs, the system automatically matches the event attributes to the pre-configured profiles and applies the appropriate notification settings, eliminating the need for real-time profile selection and simplifying user interaction.
Solution Approach 2:
The notification system automatically selects and applies the appropriate profile based on event attributes without requiring user intervention. The system self-manages the complexity of profile selection and switching, allowing users to benefit from customized notifications while maintaining ease of operation.
3Object-affected harmful factors
If profile-based notification control is implemented, then notification intrusiveness is reduced in certain environments, but the ability to provide unique notifications for specific event characteristics is limited
Solution Approach 1:
Different notification profiles are created with localized settings for specific event attributes. For example, a silent profile is applied to events occurring in meeting rooms or from specific contacts, while other events receive standard notifications. This allows the system to reduce intrusiveness where needed while maintaining uniqueness and customization for different event characteristics.
Solution Approach 2:
The notification system changes parameters such as sound volume, vibration pattern, and display behavior based on event attributes. By dynamically adjusting these parameters according to the specific characteristics of each event (sender identity, time, calendar context), the system reduces intrusiveness in appropriate situations while providing unique notifications for different event types.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A mobile electronic device has a notification mechanism for notifying a user of device events in accordance with an active notification profile defining notification options and one or more exception notification profiles defining notification options based on specified attributes of a device event. A mechanism is provided for identifying one or more attributes in an incoming device event and for overriding the active notification profile with one of the exception notification profiles that has attributes corresponding to the identified attributes. The user is thus notified in accordance with notification options specified in the exception profile of the device.