Notification Routing via Wearable Charging State Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of wearable computing devices may miss notifications if the device is not actively being worn or is charging, as existing systems require manual interaction to manage notification delivery based on the device's state.

Innovation Solution

A method where a mobile computing device determines the charging state of a wearable device and automatically sends notifications when the wearable is disconnected from a power source, while not sending notifications when it is connected, thereby reducing user interaction and ensuring timely notification delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If notifications are always sent to the wearable device, then the user receives all notifications, but the user may miss notifications when the device is not being worn or is charging

Engineering Contradiction:
Improvenotification delivery reliabilityVSAvoidmanual interaction requirement
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary action by determining the charging state of the wearable device before sending notifications. The mobile computing device checks whether the wearable device is connected to a power source, and based on this pre-assessment, decides whether to send notifications. This prevents the problem of missed notifications by ensuring notifications are only sent when the device is in a state where it can receive and display them.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback by continuously monitoring the charging state of the wearable device and using this information to control notification delivery. The mobile computing device receives charging state information from the wearable device and adjusts notification sending behavior accordingly, creating a closed-loop control system that adapts to the device's current state.

Inventive Principle:
Principle #23Feedback

2Loss of time

If the system manually manages notification delivery based on device state, then notification timing can be controlled, but user interaction is required

Engineering Contradiction:
Improvenotification delivery timingVSAvoidmanual intervention level
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The system implements self-service by automatically determining the charging state and making notification delivery decisions without requiring user intervention. The mobile computing device autonomously monitors the wearable device's charging status and independently decides whether to send notifications, eliminating the need for manual user management while maintaining optimal notification timing.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary assessment of the charging state before notification delivery, allowing automatic timing control. By checking the charging state in advance and making delivery decisions based on this information, the system achieves proper notification timing automation without requiring real-time user input.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If notifications are sent when the wearable is charging, then notifications are delivered, but the user may not see them since the device is not being worn

Engineering Contradiction:
Improvenotification delivery efficiencyVSAvoidnotification visibility
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system applies inversion by reversing the conventional approach: instead of always sending notifications and hoping the user sees them, it sends notifications only when the device is NOT charging. This inverted logic ensures that notifications are sent during periods when the device is more likely to be worn and visible to the user, preventing information loss while maintaining delivery efficiency.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentEP2871575B1Redirecting notifications to a wearable computing device
Publication Date: 2020.05.06 GOOGLE LLC
  • EP2871575B1 patent drawingFigure 1
  • EP2871575B1 patent drawingFigure 2
  • EP2871575B1 patent drawingFigure 3

AI summary

A computing device can include one or more processors, and a charging module operable by the one or more processors to determine a charging state of a second computing device, responsive to determining that the charging state of the second computing devices indicates the second computing device is operatively coupled to a power source, output by the first computing device and for display, a notification, and responsive to determining that the charging state of the second computing device indicates the second computing device is disconnected from the power source, send, by the first computing device, to the second computing device, an indication of the notification.