Split-Architecture Message Processing System for Low Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Messaging systems face high operational overhead and complexity in managing high-volume data flows across decentralized networks, especially when messages need to be transformed from one internet protocol to another during processing and delivery.

Innovation Solution

A split-architecture message processing device that evaluates incoming messages to determine necessary processing levels and resource usage, allowing direct transmission of lightweight messages while directing resource-intensive messages to a workflow pipeline engine for deeper processing at a later stage, thereby optimizing resource management and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all messages are processed through deep scanning and transformation pipelines, then message security and protocol transformation reliability are improved, but system latency and resource consumption increase significantly

Engineering Contradiction:
Improvemessage securityVSAvoidsystem latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The message processing system is segmented into two distinct pathways: a fast path for messages requiring minimal processing (headers only) and a slow path for messages requiring deep scanning and transformation. This segmentation allows the system to apply different processing depths based on message characteristics, reducing overall latency while maintaining security for messages that require it.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary evaluation of incoming messages to determine their processing requirements before committing to a full processing pipeline. By assessing message type, size, and security requirements upfront, the system can route messages appropriately, avoiding unnecessary deep scanning for simple messages while ensuring thorough processing for complex or suspicious messages.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If a decentralized network architecture is used to handle high-volume data flows, then system scalability and fault tolerance are improved, but operational overhead and configuration complexity increase

Engineering Contradiction:
Improvedata flow handling capacityVSAvoidoperational overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The message processing device is designed with multi-functional capabilities that allow it to operate effectively in decentralized network environments. It can simultaneously perform message routing, protocol transformation, security scanning, and load balancing functions, reducing the need for separate specialized components and thereby reducing operational overhead while maintaining high data flow handling capacity.

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

3Adaptability or versatility

If protocol transformation is performed for all messages, then system adaptability to different messaging protocols is improved, but processing time and computational resources increase

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidmessage processing throughput
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system applies protocol transformation selectively based on the specific requirements of each message and its destination. Rather than transforming all messages uniformly, the system performs protocol conversion only where necessary, maintaining native protocol handling for messages that don't require transformation. This local quality approach preserves protocol compatibility while maximizing processing throughput.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9948585B2Split-architecture message processing system
Publication Date: 2018.04.17 APPRIVER CANADA ULC
  • US9948585B2 patent drawing
  • US9948585B2 patent drawing
  • US9948585B2 patent drawing

AI summary

A message processing device with a split-architecture is described that allows for flexible control over data flow while enabling optimal processing based on available system resources. In one particular example, messages are processed in two stages prior to transmission to a destination. A cursory evaluation of each message determines whether a deeper level of processing is to be performed using additional resources. Then, messages capable of transmission with no perceivable delay may be transmitted directly, whereas messages to be processed using greater resources are directed to a workflow pipeline engine for more expensive processing at a later stage. The result is a low latency system allowing for efficient resource management, whose architecture is scalable and readily extendible, for example, to increase resources available during periods of high data flow.