Smart Message Queue Architecture for Multicore Processor Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic devices with multiple processors face challenges in efficiently communicating between processors due to the complexity of various communication protocols and hardware interfaces, leading to inefficiencies in data transfer and processing.
Innovation Solution
A unified and scalable multiprocessor communication framework is introduced, utilizing a Smart Message Queue (SMQ) and shared memory to abstract hardware details, enabling processors to communicate through a common interface while managing data transfer efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple processors use various communication protocols and hardware interfaces to communicate, then communication capability is achieved, but system complexity increases and data transfer efficiency decreases
Solution Approach 1:
The patent implements a universal communication framework where a single message queue interface can handle multiple communication protocols and processor types. The message queue system serves as a multi-functional intermediary that adapts to different protocols (shared memory, mailbox, interrupt controllers) without requiring separate communication paths for each protocol, thus reducing overall system complexity while maintaining productivity.
Solution Approach 2:
The message queue acts as an intermediary layer between processors and various communication protocols. Instead of processors directly interacting with complex protocol-specific interfaces, they communicate through the standardized message queue interface, which then handles protocol-specific details. This mediator approach simplifies the communication architecture and improves data transfer efficiency by providing a unified access point.
2Ease of operation
If processors communicate through direct hardware interfaces, then communication speed is achieved, but ease of operation decreases due to hardware detail complexity
Solution Approach 1:
The message queue system implements self-service mechanisms where the queue automatically manages message routing, protocol adaptation, and processor coordination without requiring manual intervention or complex configuration. The system self-adapts to different processor types and communication scenarios, making operation simple while maintaining efficient data transfer through optimized internal pathways.
Solution Approach 2:
The message queue performs preliminary actions by pre-configuring communication pathways and caching message templates. The system prepares communication buffers and routes in advance, so when actual data transfer occurs, it can proceed efficiently without real-time protocol negotiation overhead, thus reducing latency while maintaining operational simplicity.
3Adaptability or versatility
If a unified communication framework is implemented to simplify interfaces, then ease of operation improves, but device complexity increases
Solution Approach 1:
The unified communication framework is segmented into distinct functional modules: message queue management, protocol adaptation layer, buffer management, and processor interface handlers. Each segment handles specific aspects of communication independently, allowing the system to achieve high adaptability through modular design while keeping individual component complexity manageable. This segmentation enables versatile protocol support without creating an monolithic complex structure.
Data Source
AI summary
A device can provide a unified and scalable multiprocessor communication framework that enables communication between multiple processor cores in a multicore device. For example, the device may be configured to perform data payload management using a Smart Message Queue (SMQ) and/or shared memory. Additionally or alternatively, the communication framework may enable the processors to communicate with each other and/or peripherals of the device while abstracting details of various communication protocols, hardware interfaces, and/or the like. For example, the communication framework may provide a common interface for applications, enabling a first application associated with a processor to establish a connection to any processor and/or peripheral without knowing details of a communication protocol for each connection.