Cross-Device Notification Hold Logic for Consistent Alerts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional notification systems across multiple devices require constant information synchronization, leading to bandwidth and power-intensive operations, and can result in conflicting notifications due to asynchronous health information updates.

Innovation Solution

Each device generates its own notifications based on local health information, using hold, send, or dismiss instructions to synchronize notifications across devices, minimizing network traffic and power consumption, and ensuring consistent notification display.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If constant information synchronization is implemented across multiple devices, then notification consistency is improved, but bandwidth consumption and power usage increase

Engineering Contradiction:
Improvenotification consistencyVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Each device independently generates its own notifications based on local health information, eliminating the need for constant synchronization requests. The device serves itself by locally processing health data and determining when notifications should be displayed, thus reducing network traffic and power consumption while maintaining notification consistency across devices.

Inventive Principle:
Principle #25Self-service

2Reliability

If constant information synchronization is implemented across multiple devices, then notification consistency is improved, but network traffic increases

Engineering Contradiction:
Improvenotification consistencyVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Each device independently generates its own notifications based on local health information, eliminating the need for constant synchronization requests. The device serves itself by locally processing health data and determining when notifications should be displayed, thus reducing network traffic and power consumption while maintaining notification consistency across devices.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If asynchronous health information updates are allowed, then device independence is improved, but conflicting notifications occur

Engineering Contradiction:
Improvedevice independenceVSAvoidnotification consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements a feedback mechanism where devices monitor for hold instructions from other devices. When a device receives health information that would trigger a notification, it checks whether another device has already processed the same health information and sent a hold instruction. This feedback loop allows devices to maintain independence in processing health information while preventing conflicting notifications through coordinated action based on inter-device communication.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12475981B2Multidevice notification synchronization
Publication Date: 2025.11.18 APPLE INC
  • US12475981B2 patent drawing
  • US12475981B2 patent drawing
  • US12475981B2 patent drawing

AI summary

A second computing device can receive a hold instruction from a first computing device. The hold instruction can instruct the second computing device to hold a second notification until the second computing device receives first health information. The first computing device can be configured to transmit the hold instruction based on rescheduling a first notification on the first computing device to be displayed at a first time based at least in part on the first health information. The second notification can have been previously scheduled to be displayed at a second time. The second notification can correspond to the first notification. The second computing device can hold the second notification. The second computing device can receive the first health information. The second computing device can reschedule the second notification to be displayed at a third time based at least in part on the first health information.