Adaptive Messaging Modality Selection for Workflow Engines

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Project management systems using multiple data systems face challenges with project timelines and error handling due to the need for efficient communication between workflow engines and independent systems, particularly in managing synchronous and asynchronous message modalities.

Innovation Solution

A communication system with a decision/response module that determines communication history parameters to select between synchronous and asynchronous message modalities, including a retry handler for error handling and fault message management, to ensure reliable message delivery and update endpoint profiles for improved communication metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous message modality is used for communication between workflow engine and independent systems, then real-time response and reliability are improved, but system complexity and communication overhead increase

Engineering Contradiction:

Improvemessage delivery reliabilityVSAvoidcommunication system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system dynamically selects between synchronous and asynchronous message modalities based on communication history parameters and system state. The decision/response module evaluates whether to use synchronous or asynchronous messaging for each message, allowing the system to adapt its communication approach to balance reliability requirements against system complexity and performance considerations.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If asynchronous message modality is used for communication between workflow engine and independent systems, then system scalability and flexibility are improved, but message delivery reliability and real-time response deteriorate

Engineering Contradiction:

Improvecommunication flexibilityVSAvoidmessage delivery reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system uses communication history parameters to inform future messaging decisions. By analyzing past communication outcomes, success rates, and system performance data, the decision/response module can determine whether asynchronous messaging has been reliable for particular destination systems, thereby making more informed choices about when to use asynchronous versus synchronous modalities.

Inventive Principle:

Principle #23Feedback

3Reliability

If retry mechanism is implemented for error handling, then message delivery reliability is improved, but system complexity and processing time increase

Engineering Contradiction:

Improvemessage delivery reliabilityVSAvoidmessage processing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The retry handler implements selective retry logic based on message type, destination system, and communication history. Rather than uniformly retrying all failed messages, the system applies retry attempts only when appropriate based on the specific context and historical success rates, thereby reducing unnecessary processing time while maintaining reliability for messages that benefit from retry attempts.

Inventive Principle:

Principle #16Partial or excessive action

4Productivity

If communication history tracking is implemented to select message modalities, then communication efficiency is improved, but data storage requirements and system complexity increase

Engineering Contradiction:

Improvecommunication efficiencyVSAvoiddata storage requirements

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The system extracts and tracks only the essential communication history parameters needed for modality selection, rather than storing complete communication logs. By identifying and monitoring specific key parameters such as message delivery success rates, response times, and error patterns, the system achieves improved communication efficiency while minimizing data storage requirements.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11956071B2Systems and methods for synchronous and asynchronous messaging

Publication Date: 2024.04.09 VERIZON PATENT & LICENSING INC

AI summary

An example method includes receiving a message from a sending service and addressed to a destination service. The message is sent to the destination service using a synchronous message modality responsive to a communication history parameter for the destination service indicating a synchronous message type. The message is sent to the destination service using an asynchronous message modality responsive to the communication history parameter indicating an asynchronous message type. A reply is received from the destination service and the reply is sent to the sending service. The synchronous message modality comprises waiting for a reply to be received from the destination service for a predetermined time interval. The asynchronous message modality comprises storing identification data associated with the message in a correlation data store, receiving the reply from the destination service, and determining whether the reply is associated with the message based on the identification data.