MCTP Offload Engine for Low-Latency Message Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently processing large volumes of short, low-latency control messages with complex software requirements, such as header parsing, verification, and message fragmentation/reassembly, particularly in systems with numerous components and interfaces like PCIe, I2C, and I3C, leading to performance bottlenecks and latency issues.

Innovation Solution

Implementing a Management Component Transport Protocol (MCTP) Offload Engine (MOE) to handle resource-intensive tasks like message verification, length determination, mapping, reassembly, and fragmentation across various interfaces, using specialized hardware to accelerate these processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software-based message processing is used, then system flexibility and programmability are improved, but processing speed and latency performance deteriorate

Engineering Contradiction:

Improvesoftware flexibilityVSAvoidmessage processing speed

Core Design Contradiction:

Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent introduces an MCTP Offload Engine as an intermediary hardware component between the software layer and the communication interfaces. This offload engine handles time-critical message processing tasks (verification, fragmentation, reassembly) in hardware, while the software layer maintains flexibility for configuration and protocol management. The offload engine acts as a mediator that bridges the needs for both high performance and software flexibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the traditional software-based message processing mechanism with a hardware offload engine. Instead of using CPU instructions to parse, verify, and reassemble MCTP messages, the system uses dedicated hardware circuits that perform these operations autonomously. This substitution of the processing mechanism from software to hardware directly addresses the latency and performance issues while maintaining system flexibility through configurable hardware parameters.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If complex message processing operations are performed, then message validation and reliability are improved, but processing time and system latency increase

Engineering Contradiction:

Improvemessage validationVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements message validation operations (verification, length determination, mapping) in hardware within the MCTP Offload Engine. These operations that would traditionally consume CPU cycles are performed by dedicated hardware circuits that operate parallel to other message processing tasks, significantly reducing processing time while maintaining comprehensive validation capabilities.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The offload engine performs preliminary message processing actions autonomously before messages reach the software layer. By pre-verifying message integrity, determining lengths, and preparing message mappings in advance, the system reduces the processing burden on subsequent software handlers, thereby decreasing overall processing time while ensuring reliability.

Inventive Principle:

Principle #10Preliminary action

3Device complexity

If centralized message processing is used, then software control is simplified, but processing bottleneck and single point of failure risk increase

Engineering Contradiction:

Improvesoftware control complexityVSAvoidprocessing throughput

Core Design Contradiction:

Device complexityVSProductivity

Solution Approach 1:

The patent segments the message processing function into multiple independent components: the MCTP Offload Engine handles low-level message processing, while the software layer handles high-level protocol management. This segmentation distributes the processing workload and eliminates the bottleneck of centralized software processing, improving throughput while maintaining simplified control through clear interface definitions.

Inventive Principle:

Principle #1Segmentation

4Speed

If hardware offloading is implemented, then processing speed and latency performance are improved, but device complexity and hardware requirements increase

Engineering Contradiction:

Improvemessage processing speedVSAvoidhardware architecture

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The MCTP Offload Engine is designed with multi-functionality to handle various message processing tasks (verification, fragmentation, reassembly, mapping) within a single hardware component. This universal design reduces the need for multiple separate hardware modules, thereby limiting the increase in device complexity while achieving high processing speeds through hardware acceleration.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250370832A1Management component transport protocol

Publication Date: 2025.12.04 AXIADO CORP

AI summary

Described herein are systems and methods for processing a message comprising a management component transport protocol (MCTP). In some instances, the message comprising the MCTP may be processed by a MCTP Offload Engine (MOE).