Messaging Manager for Asynchronous Multi-APS Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional web chat systems require synchronous sessions for message exchange, limiting their ability to manage multiple simultaneous conversations across different autonomous processing systems and platforms, and they do not efficiently handle asynchronous communication without persistent connections.

Innovation Solution

A messaging system that manages multiple simultaneous conversations using both synchronous and asynchronous communication methods, employing a messaging manager to select and route messages to appropriate autonomous processing systems based on metadata, allowing for stateless operation and efficient handling of messages across various platforms without persistent connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous sessions are used for message exchange, then message delivery reliability is improved, but system complexity and connection management burden increase

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidconnection management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments connection management by introducing a messaging manager that handles connection persistence independently from autonomous processing systems. This separates the persistent connection requirement from the message processing logic, allowing APS instances to operate statelessly while the messaging manager maintains conversation state and manages persistent connections to messaging platforms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The messaging manager acts as an intermediary between messaging platforms and autonomous processing systems. It manages persistent connections to platforms like Facebook Messenger and Twitter, while APS instances process messages without maintaining persistent connections, thus resolving the contradiction between reliability and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If persistent connections are maintained for all conversations, then message exchange reliability is improved, but resource consumption and system scalability worsen

Engineering Contradiction:
Improvemessage exchange reliabilityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies persistent connections locally only where needed - specifically at the messaging manager level for maintaining conversations across platforms. Individual APS instances operate without persistent connections, consuming minimal resources while still enabling reliable message exchange through the messaging manager's connection management.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The messaging manager provides universal connection management services to multiple APS instances simultaneously. A single persistent connection infrastructure supports many conversations and multiple platforms, reducing overall resource consumption compared to each APS maintaining its own persistent connections.

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

3Adaptability or versatility

If multiple autonomous processing systems handle different message types, then system versatility and adaptability are improved, but routing complexity and coordination overhead increase

Engineering Contradiction:
Improvemessage handling versatilityVSAvoidrouting complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system uses metadata feedback mechanisms where messages include metadata indicating their type and intended recipient APS. The messaging manager uses this metadata to automatically route messages to the appropriate APS instance, reducing routing complexity through rule-based decisions rather than complex coordination protocols.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Each APS instance is self-described through its capabilities and metadata requirements. The messaging manager automatically matches incoming messages with appropriate APS instances based on message metadata and APS capabilities, enabling versatile message handling without complex manual routing configuration.

Inventive Principle:
Principle #25Self-service

4Productivity

If stateless operation is implemented across APS instances, then system scalability and ease of deployment are improved, but conversation state management complexity increases

Engineering Contradiction:
Improvesystem scalabilityVSAvoidstate management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system merges state management functionality into the messaging manager, combining persistent connection management, conversation state tracking, and message routing in a single centralized component. This allows APS instances to remain stateless and scalable while the messaging manager handles the complexity of maintaining conversation state across multiple instances and platforms.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11516154B2Systems for managing messaging conversations
Publication Date: 2022.11.29 APPLE INC
  • US11516154B2 patent drawing
  • US11516154B2 patent drawing
  • US11516154B2 patent drawing

AI summary

A system for managing messaging conversations that can be simultaneous and can be maintained across various different autonomous processing systems is described. In one embodiment, the system (operated by or on behalf of a first organization) can include a messaging manager and a first autonomous processing system (first APS) and a second APS. The system can receive a first message and a second message, both directed to the first organization, and the messaging manager can select the first APS to respond to the first message and route the first message to the first APS which can transmit a response to the first message. The messaging manager can select the second APS to respond to the second message and route the second message to the second APS. The messages can be managed asynchronously without a persistent connection during the one or more conversations.