Mobile Terminal Notification Mode Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile terminal notification systems lack a flexible and prioritized method to manage multiple notification modes for incoming push messages, often resulting in inconsistent user experience due to overlapping or conflicting notification settings across different applications.

Innovation Solution

A notification method that determines and prioritizes between multiple notification modes based on a first configuration set by the user and a second configuration set by the application, allowing for conditional control of notification devices such as ringtone, vibration, silent, or notification-off modes, and incorporates time-based settings to adjust notification modes dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple notification modes are allowed for different applications, then notification versatility is improved, but notification management complexity increases

Engineering Contradiction:
Improvenotification versatilityVSAvoidnotification management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The notification system is segmented into two distinct configuration layers: device-level notification settings and application-level notification settings. Each layer manages specific aspects of notification behavior, allowing versatile notification modes while simplifying management through clear separation of concerns. The device-level configuration handles global notification preferences, while application-level configuration handles app-specific overrides.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different notification configurations are applied locally to different applications based on their specific needs. Each application can have its own notification mode settings (ringtone, vibration, silent, etc.) that are independently configured and applied, allowing tailored notification behavior for each app while maintaining overall system organization.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If application-specific notification settings are allowed, then notification customization is improved, but configuration conflict increases

Engineering Contradiction:
Improvenotification customizationVSAvoidconfiguration consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary determination of configuration priority before applying notification settings. When an application receives a push notification, the system first checks whether the application has its own notification mode settings configured. This preliminary check prevents conflicts by establishing a clear resolution order: application-level settings take precedence when configured, otherwise device-level settings are used.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The notification management system acts as an intermediary layer between the application and the notification devices. It receives notification requests from applications, determines the appropriate configuration to use based on the priority determination logic, and then directs the notification output. This intermediary resolves conflicts by systematically selecting the appropriate configuration level.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If priority-based configuration selection is implemented, then notification consistency is improved, but processing overhead increases

Engineering Contradiction:
Improvenotification consistencyVSAvoidnotification processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs only the necessary priority determination steps required for consistent notification delivery. Rather than evaluating all possible configuration combinations, it implements a streamlined priority check: first check if application-level settings exist, if yes use them, if no use device-level settings. This partial action approach achieves consistency without excessive processing overhead.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11038831B2Notification method of mobile terminal using a plurality of notification modes and mobile terminal using the method
Publication Date: 2021.06.15 KAKAO CORP
  • US11038831B2 patent drawing
  • US11038831B2 patent drawing
  • US11038831B2 patent drawing

AI summary

Disclosed is a notification method of a mobile terminal using a plurality of notification modes. A mobile terminal according to one aspect of the present invention determines a first configuration type relating to the notification mode of the mobile terminal in response to the receipt of a new push message. The mobile terminal determines a second configuration type relating to the notification mode of a push message application based on the first configuration type. The mobile terminal notifies the arrival of a new push message according to the second configuration type. That is, embodiments may provide a technology that uses at least two configurations relating to the notification mode of the mobile terminal so as to notify the user about receipt of a new message.