Cross-Account Notification Tagging and Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users cannot execute application programs or receive event notifications across different accounts on the same electronic device, limiting convenience and responsiveness to notifications.

Innovation Solution

A cross-account notification method and electronic device architecture that allows tagging of application programs, setting notification preferences, and transmitting notifications between accounts, enabling notifications to be received and managed across multiple accounts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application programs are isolated by account for security and management, then account security and data privacy are improved, but cross-account notification capability deteriorates

Engineering Contradiction:
Improveaccount securityVSAvoidcross-account notification capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system segments notification management by creating account-specific notification settings while maintaining a separate notification transmission mechanism. Each account has its own notification preferences and tagged applications, but the notification service acts as an intermediary that can selectively transmit notifications across account boundaries based on user-defined rules.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The notification service acts as an intermediary component that receives notifications from applications in one account and can transmit them to other accounts. This mediator layer enables cross-account communication without compromising the security isolation of individual accounts, as the transmission is controlled through predefined notification settings.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If notifications are transmitted across accounts, then user responsiveness to notifications is improved, but system complexity increases

Engineering Contradiction:
Improvenotification response timeVSAvoidnotification management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system performs preliminary configuration by allowing users to pre-define notification settings, including which applications are tagged for cross-account notification and which accounts should receive them. This advance configuration eliminates the need for real-time decision-making about notification routing, reducing system complexity while enabling rapid notification delivery.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If multiple accounts are supported on the same device, then user convenience is improved, but application execution capability deteriorates

Engineering Contradiction:
Improvemulti-account supportVSAvoidapplication execution capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The notification service provides a universal function that operates across multiple accounts and applications. By tagging applications rather than restricting them to single accounts, the system enables a single notification infrastructure to serve multiple accounts and their respective applications, allowing notifications to be transmitted across account boundaries without requiring separate notification systems for each account.

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

Data Source

PatentUS9877170B2Cross-account notification method and electronic device using the same
Publication Date: 2018.01.23 ASUSTEK COMPUTER INC
  • US9877170B2 patent drawing
  • US9877170B2 patent drawing
  • US9877170B2 patent drawing

AI summary

A cross-account notification method and an electronic device using the same are provided. The method includes: tagging multiple application programs of multiple accounts of the electronic device; receiving a first notification of the tagged first application program of the first account; determining whether the first notification needs to be transmitted to a second account according to a notification setting; transmitting the first notification to the second account according to the notification setting.