Format Decoder Annotation Extraction for Message Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing message handling techniques face challenges with high latency and memory resource requirements in generic software solutions, while targeted hardware solutions are inflexible and can only process specific protocols and applications.

Innovation Solution

The use of annotations to extract parameters from messages, allowing for dynamic configuration of format decoders and application logic to support various message types without changing hardware, enabling efficient processing of messages with minimal latency and flexible protocol support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If generic software solutions are used for message processing, then flexibility is improved, but latency and memory resource requirements worsen

Engineering Contradiction:
ImproveflexibilityVSAvoidlatency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The message processing system is segmented into distinct functional units: a format decoder that extracts parameters from incoming messages, a register file that stores extracted parameters, and message handlers that execute application logic. This segmentation allows each component to be optimized independently, with the format decoder operating in hardware to minimize latency while maintaining software-like flexibility through configurable parameter extraction rules.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A register file serves as an intermediary between the format decoder and message handlers. The format decoder extracts parameters from messages and stores them in the register file, which then provides these parameters to message handlers for processing. This intermediary structure enables efficient data flow and reduces latency by eliminating the need for software to manually extract and pass parameters between components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If targeted hardware solutions are used for message processing, then throughput and latency are improved, but adaptability worsens

Engineering Contradiction:
ImprovethroughputVSAvoidadaptability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The format decoder is designed as a universal hardware component that can process multiple message formats and protocols. Instead of creating dedicated hardware for each protocol, the system uses a single configurable format decoder that can be programmed to extract parameters from various message types. This universal approach maintains high throughput and low latency while providing adaptability to different protocols and applications.

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

Solution Approach 2:

The system achieves adaptability by changing parameters rather than hardware structure. The format decoder can be configured with different parameter extraction rules, field positions, and data formats through software programming. This allows the same hardware to efficiently process different message types by simply changing the extraction parameters, maintaining high performance while providing flexibility.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If generic software solutions are used for message processing, then flexibility is improved, but memory resource requirements worsen

Engineering Contradiction:
ImproveflexibilityVSAvoidmemory resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system extracts only the necessary parameters from incoming messages and stores them in a compact register file, rather than storing entire messages in software buffers. The format decoder identifies and extracts only the relevant data fields needed for processing, significantly reducing memory requirements. This extraction approach maintains flexibility in handling different message types while minimizing memory resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The register file uses small, fast, and inexpensive storage elements to hold extracted parameters temporarily during processing. Rather than allocating large software memory buffers for each message, the system uses small register-sized storage that is quickly written and read, then overwritten for the next message. This approach provides the necessary flexibility while using minimal memory resources.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS9781062B2Using annotations to extract parameters from messages
Publication Date: 2017.10.03 ORACLE INT CORP
  • US9781062B2 patent drawing
  • US9781062B2 patent drawing
  • US9781062B2 patent drawing

AI summary

The disclosed embodiments relate techniques for using annotations to extract parameters from messages. During operation, a computing device receives a message from a network interface. After determining a message type for the message, a format decoder in the computing device uses the message type to determine an annotation that is associated with the message type. The message and the annotation are then output to one or more functional units of the computing device, with the annotation output aligned with the message on a per-message-byte basis.