Dynamic Notification Pushing for Mobile Terminals

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile phone notification systems lack diversity in notification methods, requiring users to manually search for information as notifications are not contextually updated based on event changes, leading to complex operations and difficulty in obtaining relevant information.

Innovation Solution

A method for pushing notifications on a terminal device that determines multiple conditions (time, place, user behavior, environment) for a to-be-notified event, displaying different notification pages with association information, allowing timely and varied notification content based on event development stages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional notification methods are used, then the notification system is simple, but the notification effectiveness and user experience are poor

Engineering Contradiction:
Improvenotification effectivenessVSAvoidnotification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The notification system dynamically adapts its behavior based on event development stages. The notification apparatus transitions between different notification modes (initial notification, updated notification, service entry notification) according to the progress of the event, making the system dynamic rather than static. This resolves the contradiction by implementing conditional logic that activates complex behaviors only when needed, maintaining simplicity for basic cases while providing enhanced effectiveness when events require it.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes notification parameters (content, timing, display location, interaction options) based on the event stage and user behavior. For example, the notification content is updated to reflect current event status, the notification is displayed at different locations (top of screen, lock screen, notification bar) depending on the stage, and interaction options vary based on user actions. This parameter adaptation resolves the contradiction by making the notification system flexible and context-aware without requiring complete system redesign.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If users manually search for notification information, then the notification content is simple, but the operations are complex and information is difficult to obtain

Engineering Contradiction:
Improveinformation access easeVSAvoidnotification information completeness
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The notification system proactively provides updated information about event status, service progress, and required user actions directly within the notification itself. Instead of requiring users to manually search through applications or SMS messages, the system pre-fetches and displays relevant information (flight status, hotel check-in time, taxi arrival status) in the notification, making information immediately accessible without complex operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The notification system implements a feedback mechanism where it monitors event progress and user interactions, then updates the notification content accordingly. When events progress or user actions are detected, the system sends updated notifications with new information, creating a closed-loop feedback system. This resolves the contradiction by ensuring information completeness is maintained through continuous updates rather than requiring manual user searching.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If single-stage notifications are used, then the notification system is simple, but the notification cannot adapt to event development stages

Engineering Contradiction:
Improvenotification adaptabilityVSAvoidnotification logic complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The notification process is segmented into distinct stages: initial notification stage, updated notification stage, and service entry notification stage. Each stage has specific triggers, display locations, and interaction options. This segmentation allows the system to adapt to different event development stages without requiring complex monolithic logic, as each stage can be independently configured and managed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The notification system dynamically transitions between different notification modes based on event progress and user behavior. The system monitors event status changes and user actions, then automatically switches between notification types (initial alert, updated status, service entry prompt). This dynamic behavior provides adaptability to different event stages while maintaining manageable complexity through event-driven state transitions rather than complex conditional programming.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11909906B2Method and apparatus for pushing notification, mobile terminal, and graphical user interface
Publication Date: 2024.02.20 HONOR DEVICE CO LTD
  • US11909906B2 patent drawing
  • US11909906B2 patent drawing
  • US11909906B2 patent drawing

AI summary

According to a method for pushing a notification provided in some embodiments of the present disclosure, a to-be-notified event is obtained; a first notification condition and a second notification condition are determined; a first notification page is displayed on the display when the first notification condition is met, to display, to a user, first association information when the first notification condition is met, for example, event status information, to-be-executed behavior information, and operation association information; and a second notification page is displayed on the display when the second notification condition is met after the first notification page is displayed, to display, to the user, second association information when the second notification condition is met. A plurality of notification pages are pushed for a to-be-notified event, and each notification page is pushed when a notification condition is met as the event develops.