Mobile Messaging Notification Pipeline with Reply Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile messaging technologies face challenges in delivering messages across various mobile carriers and markets, particularly in enabling user interactions such as responding to messages while ensuring privacy and security.

Innovation Solution

A pipeline system that handles notification messages by correlating them with replies, using declarative APIs to access carrier data, format messages for delivery, and perform actions based on coded responses, supporting locale-specific and agnostic codes to facilitate user interactions across different markets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a pipeline system is implemented to handle notification messages and correlate replies across diverse mobile carriers, then adaptability and versatility improve, but device complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a pipeline system with multiple intermediary components including a message receiver that accepts messages from senders, a message formatter that adapts messages for different mobile carriers, a message sender that delivers formatted messages, a notification receiver that receives notifications from mobile devices, a notification correlator that links notifications to original messages, and a notification sender that delivers notifications to users. These intermediaries handle the complexity of carrier-specific protocols and message formatting, allowing the system to adapt to diverse mobile carriers without requiring the sender or recipient to understand carrier-specific details.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent divides the message delivery system into distinct functional segments: message reception, message formatting, message sending, notification reception, notification correlation, and notification sending. Each component performs a specific function and can be independently configured for different mobile carriers. This segmentation allows the system to handle diverse carrier requirements by configuring individual segments rather than redesigning the entire system.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If state data is maintained to correlate replies with notification messages, then user interaction capability improves, but loss of information increases

Engineering Contradiction:
Improveuser interactionVSAvoidinformation loss
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where the notification correlator receives notifications from mobile devices and correlates them with original messages using maintained state data. The state data includes message identifiers, reply formats, and carrier-specific information that enable the system to track which reply corresponds to which original message. This feedback loop ensures that user interactions are properly associated with the correct messages while preserving all necessary information through structured state management.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8934925B2Mobile messaging message notifications processing
Publication Date: 2015.01.13 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8934925B2 patent drawing
  • US8934925B2 patent drawing
  • US8934925B2 patent drawing

AI summary

Described is a pipeline for handling notification messages sent to a mobile messaging message (e.g., SMS or SMTP) recipient, and handling a reply to that notification message, including correlating the notification message with the reply. An engine receives a notification message, and for a notification message to which a reply is possible, maintains state data for use in correlating a received reply with the notification message. The state data includes metadata that indicates that text or code data is expected in any reply. For a reply providing code data, the engine calls a selected URL corresponding to the code. To facilitate message delivery, the engine may format the notification message, including shortening a URL of the message, and/or splitting a longer notification message into shorter notification messages.