Cross-device notification relay via server intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users often miss important notifications on one device while using another, leading to missed calls, messages, or interruptions due to the lack of cross-device notification management, especially when they are not physically near the device receiving the notification.

Innovation Solution

A method and system that detect events on a first device associated with a user account, determine event characteristics, and automatically broadcast relevant notifications to other devices associated with the user account for real-time management, allowing users to interact with and manage events from any connected device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If notifications are displayed only on the original device, then device complexity is reduced, but users may miss important notifications when not physically near the device

Engineering Contradiction:
Improvenotification delivery reliabilityVSAvoidcross-device notification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A server acts as an intermediary between devices to relay notifications. When a notification is generated on one device, the server receives it and forwards it to other associated devices, enabling cross-device notification delivery without requiring direct device-to-device communication infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The notification system is designed to work across multiple device types and platforms universally. The same notification can be delivered to smartphones, tablets, computers, and other devices associated with the user account, making the system multi-functional and device-agnostic

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of operation

If notifications are broadcast to multiple devices, then users can manage events from any device, but network traffic and system resources increase

Engineering Contradiction:
Improvecross-device event management capabilityVSAvoidnetwork traffic and processing resources
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

Different devices receive different types of notifications based on their characteristics and user preferences. The system evaluates device-specific factors such as device type, current usage state, and user preferences to determine which notifications should be delivered to which devices, optimizing resource usage by avoiding unnecessary notification broadcasts

Inventive Principle:
Principle #3Local quality

3Reliability

If all events are monitored and broadcast across devices, then no important events are missed, but information processing overhead increases

Engineering Contradiction:
Improveevent detection completenessVSAvoidevent monitoring and filtering system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Event filtering and categorization rules are pre-configured on the server before notifications are generated. The system applies these predetermined rules to determine which events warrant notification and which devices should receive them, eliminating the need for complex real-time decision-making and reducing processing overhead during notification delivery

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3162005B1Cross-device notifications
Publication Date: 2019.06.12 GOOGLE LLC
  • EP3162005B1 patent drawingFigure 1
  • EP3162005B1 patent drawingFigure 2~3A
  • EP3162005B1 patent drawingFigure 3B~3C

AI summary

Techniques for cross-device notifications are provided. An example method includes receiving a first indication of an event detected at a first device associated with a user account, determining one or more characteristics of the event based on the first indication of the event, detecting whether the determined characteristics match at least one selection criterion, automatically identifying a second device from one or more devices associated with the user account, and providing, if the determined characteristics match the at least one selection criterion, the first indication of the event to the second device associated with the user account, where the provided first indication of the event is displayed at the second device to allow management of the event at the first device from the second device.