Condition-Sensitive Message Validation in Distributed Workflows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In electronic file workflows, condition-sensitive messages often face delays and validation challenges, leading to increased computing resource costs and operational expenses due to duplicative validation processes and the inability to change messages at the endpoint, especially when messages arrive late or on 'dumb' devices with unidirectional communication capabilities.

Innovation Solution

Implementing a validator that creates clones or key passes with varying content based on anticipated arrival times, allowing only valid messages to reach the endpoint, with a gatekeeper determining validity and discarding invalid ones, thus simplifying validation and reducing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a second validation process is included at the endpoint to verify message validity, then message validity is ensured, but operation costs and computing resource costs increase

Engineering Contradiction:
Improvemessage validityVSAvoidvalidation process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by performing validation at the message production service before the message enters the workflow. The validation service validates messages based on attributes and conditions, and only valid messages are published to the workflow. This eliminates the need for a second validation process at the endpoint, reducing operational complexity while ensuring message validity throughout the workflow.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If messages are validated early in the workflow, then validation occurs as soon as possible, but messages may arrive late at the endpoint and be discarded

Engineering Contradiction:
Improvevalidation speedVSAvoidmessage timeliness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The validation service performs preliminary validation at the message production service, checking message attributes and conditions before publication. This early validation ensures that only valid messages enter the workflow, preventing wasted resources on invalid messages while maintaining timeliness through efficient validation logic that accounts for delivery conditions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by monitoring message delivery status and timing. The validation service can adjust validation criteria based on observed delivery patterns and conditions, optimizing the balance between early validation efficiency and message timeliness assurance.

Inventive Principle:
Principle #23Feedback

3Reliability

If validation is performed at the endpoint, then message conditions are verified, but computational cost increases due to service calls and business logic access

Engineering Contradiction:
Improvecondition verificationVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The validation service performs all necessary condition verification and attribute validation at the message production service before the message enters the workflow. This preliminary validation eliminates the need for expensive endpoint validation that would require service calls and business logic access, significantly reducing computational cost while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If duplicate validation processes are implemented, then message validity is ensured, but operation costs increase

Engineering Contradiction:
Improvemessage validityVSAvoidoperation cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The validation service performs comprehensive validation at the message production service, including checks on message attributes, conditions, and delivery requirements. This single preliminary validation eliminates the need for duplicate validation processes at the endpoint, ensuring message validity while reducing operational costs by avoiding redundant validation operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10248507B1Validation of condition-sensitive messages in distributed asynchronous workflows
Publication Date: 2019.04.02 AMAZON TECH INC
  • US10248507B1 patent drawing
  • US10248507B1 patent drawing
  • US10248507B1 patent drawing

AI summary

Technologies are disclosed for validation of condition-sensitive messages (or other electronic files) in distributed asynchronous message workflows. An asynchronous message processing system includes a message producer configured to generate an original message that includes at least one attribute related to a time of arrival of the original message at a message publishing service. A validation service is also included that initially validates a current time and generates alternatives for the original message. The alternatives for the original message are based upon a plurality of potential times of arrival. A gatekeeper service selects one of (i) the original message or (ii) one of the alternatives for the original message based upon a time of arrival. The selected message or alternative for the original message is provided to the message publishing service to publish the selected one of the original message or the selected alternative for the original message to an entity.