MCU Tunneling API Messages to Data-Path Chip
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Transceivers face memory shortages and increased latency due to the need to store and process extensive Application Programming Interfaces (APIs) on Microcontroller Units (MCUs), which are exacerbated by the complexity of functions and the requirement for converting commands into API calls for data-path chips.
Innovation Solution
Compiling a first portion of the API on a host device and a second portion on the MCU, allowing the MCU to tunnel messages associated with the host device's API to the data-path chip without performing operations, thereby offloading API-related tasks and reducing processing loads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the MCU stores and processes extensive APIs locally, then the transceiver can control data-path chip functions, but the MCU experiences memory shortages and increased latency
Solution Approach 1:
The patent extracts the API storage and processing function from the MCU and relocates it to the host device. The host device now stores the complete API and generates control messages, while the MCU only receives and forwards these messages to the data-path chip. This extraction resolves the memory shortage problem by removing the burden of storing extensive APIs from the resource-constrained MCU.
Solution Approach 2:
The patent introduces a message tunneling mechanism where the host device acts as an intermediary. The host device compiles API calls into standardized control messages that are sent through the MCU to the data-path chip. This intermediary approach allows the MCU to maintain control functionality without needing to store or interpret complex APIs locally, thus reducing memory requirements and processing latency.
2Ease of operation
If the MCU converts commands into API calls for the data-path chip, then the data-path chip can be controlled, but the processing load and latency on the MCU increase
Solution Approach 1:
The patent applies preliminary action by having the host device pre-compile API calls into standardized control messages before sending them to the MCU. The conversion from high-level API calls to low-level control commands is performed in advance on the host device, which has sufficient processing resources. The MCU then simply forwards these pre-processed messages to the data-path chip, eliminating the need for real-time conversion and thus reducing processing latency.
3Adaptability or versatility
If the MCU processes extensive API data, then comprehensive control functions are available, but power dissipation increases
Solution Approach 1:
The patent extracts the computationally intensive API processing workload from the MCU and relocates it to the host device. The host device performs all API interpretation and command generation, while the MCU only handles message forwarding. This extraction significantly reduces the MCU's processing load and associated power consumption, while the host device's superior processing capabilities ensure comprehensive control function coverage is maintained.
Data Source
AI summary
A system may comprise a host device that stores a first application programming interface (API) and a transceiver. The transceiver may comprise a microcontroller unit (MCU) that stores a second API. The second API may be a subset of the first API. The first API and the second API may control different functions of a data-path chip of the transceiver. The MCU may be configured to provide controls and data from the first API through the MCU without operating on the controls and the data and without using the second API.