Notification Policy Engine for Multi-Channel User Engagement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current social networking systems lack an efficient framework for delivering personalized notifications across multiple channels to users based on their interactions and relationships, often resulting in missed opportunities for engagement and customer reactivation.

Innovation Solution

A notification providing architecture that includes a policy engine to execute notification policies, sending reminders and promotional offers through various channels like SMS, MMS, email, and VOIP, based on triggering events and user-specific policies, allowing for interrelated notification policies across different software applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a notification system sends notifications through multiple channels to enhance user engagement, then user engagement and customer reactivation rates improve, but system complexity and coordination difficulty increase

Engineering Contradiction:
Improveuser engagementVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The notification system is segmented into independent modular components including notification generators for different channels (SMS, email, push notifications), a central routing engine, and policy management modules. Each generator handles a specific channel type independently, allowing the system to scale and maintain complexity without increasing overall system difficulty.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A central routing engine acts as an intermediary between notification generators and delivery mechanisms. This mediator coordinates all notification channels, manages routing logic, and handles channel selection based on user preferences and notification priority, thereby reducing the coordination burden across multiple channels.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If notification policies are customized for individual users and applications, then notification relevance and timeliness improve, but policy management complexity increases

Engineering Contradiction:
Improvenotification relevanceVSAvoidpolicy management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The policy management module implements universal policy templates that can be applied across multiple applications and user types. These templates define common notification patterns, timing rules, and channel preferences that can be customized through simple parameters rather than creating entirely new policies for each case, thereby reducing management complexity while maintaining relevance.

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

Solution Approach 2:

The system pre-configures notification policies based on user profiles, application types, and historical interaction data before notifications are needed. This preliminary action establishes default routing rules, preferred channels, and timing parameters in advance, allowing the system to quickly retrieve and apply appropriate policies without complex real-time decision-making.

Inventive Principle:
Principle #10Preliminary action

3Speed

If notifications are sent immediately upon triggering events, then response timeliness improves, but notification timing precision and user experience deteriorate due to potential overload

Engineering Contradiction:
Improveresponse timelinessVSAvoidnotification timing precision
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The routing engine implements periodic batching and scheduling mechanisms that group notifications by priority, user activity patterns, and channel capacity. Instead of immediate one-by-one delivery, notifications are scheduled in optimized batches that maintain timely response while preventing user overload and respecting preferred viewing times.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The notification timing system dynamically adjusts delivery schedules based on real-time user behavior data, channel availability, and notification priority. The routing engine can postpone, accelerate, or cancel notifications based on changing conditions, optimizing the balance between timeliness and user experience without rigid immediate delivery rules.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10432468B2Notification policies
Publication Date: 2019.10.01 META PLATFORMS INC
  • US10432468B2 patent drawing
  • US10432468B2 patent drawing
  • US10432468B2 patent drawing

AI summary

In one embodiment, a method includes receiving an indication of an occurrence of a triggering event for one or more notifications relevant to one or more users. The notifications are sent to one or more of the users through one or more of a number of notifications channels, and each notification channel is associated with one or more software applications. The method also includes accessing a number of notification policies associated with the software applications. Each of the software applications has at least one associated notification policy. At least one of the notification policies associated with a first one of the software applications is interrelated with at least one other notification policy associated with a second one of the software applications. The method also includes sending one or more notifications to one or more users through one or more of the number of notification channels.