Cross-Channel Pull Notifications for Missed Critical Alerts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customers may miss critical messages, such as real-time fraud prevention alerts, due to intentionally or unintentionally disabling push notifications on their mobile devices.

Innovation Solution

Implementing a system that uses pull notifications, where messages are stored with a message identifier and marked for retrieval during the next customer login, enabling display through mobile applications or browsers, even when push notifications are disabled.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If push notifications are used to deliver messages to customers, then message delivery speed is improved, but message reliability deteriorates when customers disable push notifications

Engineering Contradiction:
Improvemessage delivery speedVSAvoidmessage delivery reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

Instead of pushing notifications to customers (active approach), the system inverts the approach by having customers pull/retrieve messages through their mobile applications or web browsers. The backend stores messages with unique identifiers and makes them accessible when customers log in, ensuring messages are delivered regardless of notification settings.

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

Solution Approach 2:

The system introduces an intermediary mechanism - a message retrieval system with unique message identifiers that bridges the gap between message sending and customer receipt. Messages are stored in a backend database and customers can retrieve them through their authenticated sessions, acting as an intermediary that ensures delivery without relying on push notification permissions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If pull notifications are implemented to ensure message delivery, then message reliability is improved, but system complexity increases

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The message retrieval system serves multiple functions: it stores messages, manages message identifiers, handles customer authentication, and provides message access across different platforms (mobile apps and web browsers). This multi-functional approach consolidates what could be separate complex systems into a unified message management infrastructure.

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

Solution Approach 2:

The system uses message identifiers as simplified copies or references to the actual messages. Instead of transferring entire message contents through complex notification channels, the system stores lightweight identifier data that customers retrieve and use to access full messages, reducing data transmission complexity while ensuring reliable delivery.

Inventive Principle:
Principle #26Copying

3Reliability

If messages are stored with message identifiers for retrieval, then message security is improved, but message access time increases

Engineering Contradiction:
Improvemessage securityVSAvoidmessage access time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-generating and storing unique message identifiers along with message data in the backend database before customers need to access them. Messages are prepared and tagged with identifiers in advance, so when customers log in and request messages, the system can quickly retrieve pre-prepared message data using the stored identifiers without performing complex processing at access time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4693135A1Systems and methods for pull notifications and interacting on both web and mobile channels
Publication Date: 2026.02.11 JPMORGAN CHASE BANK NA
  • EP4693135A1 patent drawingFigure 1
  • EP4693135A1 patent drawingFigure 2
  • EP4693135A1 patent drawingFigure 3A

AI summary

A method may include: receiving, by a backend computer program and from a service provider system, a message for customer; storing, by the backend computer program, the message with a message identifier for the message; marking, by the backend computer program, a customer electronic device associated with the customer to receive the message on a next customer login on the customer electronic device; receiving, by the backend computer program and from a mobile application or a browser executed by the customer electronic device, a login from the customer; authenticating, by the backend computer program, the customer; confirming, by the backend computer program, that the customer electronic device is marked; and providing, by the backend computer program, the message identifier to the mobile application or the browser; wherein the mobile application or the browser may be configured to retrieve the message using the message identifier and to display the message.