Connection-Based Notification Classification for Faster Alert Recognition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing messaging applications lack efficient methods to convey relevant information to users based on user connections, often requiring users to see message content to determine the type of notification, which is inefficient and time-consuming.

Innovation Solution

A classification-based notification system that designates notification types to user connections based on user profiles, communication history, and explicit user inputs, using auditory, visual, and haptic elements to alert users quickly about message types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If traditional notification systems are used, then users can receive message notifications, but users must view message content to identify notification types, which is time-consuming and inefficient

Engineering Contradiction:
Improvetime to identify notification typeVSAvoidease of identifying notification type
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The notification system segments user connections into different classifications (e.g., family, friends, colleagues, strangers) and assigns distinct alert attributes to each classification. This allows users to identify notification types based on the sender's classification rather than viewing message content, reducing time and effort required.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses different alert attributes (visual, auditory, haptic) that can be distinguished by their characteristics to indicate different notification types. For example, different sound tones, vibration patterns, or visual icons can signal whether a notification is from a family member, friend, or colleague, enabling quick identification without opening the message.

Inventive Principle:
Principle #32Color changes

2Loss of information

If notification systems provide detailed message content, then users have complete information, but users cannot quickly identify notification types without viewing content

Engineering Contradiction:
Improveinformation about notification typeVSAvoidtime to access notification type information
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary classification of user connections and pre-assigns alert attributes to different connection types before messages are received. This preliminary organization allows the notification system to immediately present differentiated alerts when messages arrive, providing notification type information before the user needs to read the actual message content.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the system classifies users based on communication history, then notification personalization improves, but system complexity increases

Engineering Contradiction:
Improvenotification personalizationVSAvoidclassification system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system automatically performs user classification based on communication history and interaction patterns without requiring manual input from the user. The classification algorithm operates autonomously in the background, analyzing message metadata and user behavior to assign connection types, thereby achieving personalization while minimizing user burden and system complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260003473A1User classification based notification
Publication Date: 2026.01.01 SNAP INC
  • US20260003473A1 patent drawing
  • US20260003473A1 patent drawing
  • US20260003473A1 patent drawing

AI summary

A classification based notification system is disclosed which performs operations that include: accessing user profile data associated with a user account associated with a client device, the user profile data including a list of user connections; designating a notification type to a portion of the list of user connections, the notification type corresponding to an alert attribute; receiving a notification from a user connection from among the portion of the list of user connections at the client device; and presenting an alert based on the alert attribute that corresponds with the notification type associated with the portion of the list of user connections at the client device.