In-Application Message Delivery via Redundant Push and Data Paths

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The delivery of push notifications for in-application messages is unreliable in certain geographical regions due to physical infrastructure or government regulations, leading to delayed or failed message delivery, which disrupts customer engagement services' ability to orchestrate timely message delivery to users.

Innovation Solution

Implementing redundant message delivery paths through both push notification services and data networks to ensure that in-application messages are presented to users, even if push notifications are delayed or fail, by using a server to check for recent message delivery requests and sending redundant message data to the software application if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If push notification services are used to deliver in-application messages, then message delivery can be achieved through a simple mechanism, but delivery reliability deteriorates in certain geographical regions due to infrastructure or regulatory issues

Engineering Contradiction:
Improvemessage delivery mechanismVSAvoidpush notification delivery
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system performs preliminary actions by sending push notifications in advance and simultaneously preparing alternative delivery paths. The server checks for recent message delivery requests before sending alternative messages, ensuring that redundant delivery mechanisms are already in place before delivery failure occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system sets up compensatory measures in advance by implementing a dual delivery path architecture. When push notification delivery is unreliable in certain regions, the system has pre-configured alternative data network paths ready to compensate for potential failures, cushioning against delivery disruptions.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If redundant message delivery paths are implemented through both push notification services and data networks, then message delivery reliability is improved, but system complexity increases

Engineering Contradiction:
Improvemessage deliveryVSAvoiddelivery system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server acts as an intermediary that manages the complexity of dual delivery paths. It receives message delivery requests, checks for recent delivery attempts, coordinates between push notification services and data networks, and prevents duplicate message presentations. This intermediary approach centralizes control and simplifies the overall system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where the server checks for recent message delivery requests before sending alternative messages. This feedback loop ensures that redundant messages are only sent when necessary, and the software application receives instructions to prevent duplicate message presentations, thereby managing system complexity through intelligent coordination.

Inventive Principle:
Principle #23Feedback

3Speed

If push notifications are sent to deliver in-application messages, then timely message delivery can be achieved, but delivery fails or is delayed in regions with unreliable push notification infrastructure

Engineering Contradiction:
Improvemessage delivery speedVSAvoidpush notification delivery
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system dynamically changes delivery parameters by switching between push notification services and data networks based on delivery reliability. When push notification delivery is unreliable in certain regions, the system alters the delivery parameter to use alternative data network paths, maintaining message delivery speed and reliability by adapting to regional conditions.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10693987B1Systems and methods for ensuring presentation of in-application messages
Publication Date: 2020.06.23 BRAZE INC
  • US10693987B1 patent drawing
  • US10693987B1 patent drawing
  • US10693987B1 patent drawing

AI summary

Systems and methods for causing an in-application message to be presented to a user of a software application can send message data to the software application via a push notification and via a redundant communication sent over a data network. If the push notification is delivered to the software application first, information in the push notification is used to present the in-application message to the user and the later arriving redundant communication over the data network is ignored. Similarly, if the redundant communication via the data network arrives first, information in that communication is used to present the in-application message to the user, and the later arriving push notification is ignored.