Proxy Slave LIN Messaging Across Backbone Network Partitions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Local Interconnect Network (LIN) messaging between partitions separated by a backbone communication network often violates the predefined LIN response time due to added latency in sending requests and responses through high-speed networks.
Innovation Solution
Implementing a proxy slave and proxy master architecture that anticipatorily stores data from one LIN partition and forwards it to the originating master within the LIN response time, using a basic read schedule table (BRST) or event triggered schedule table (ETST) to manage read and write requests, thereby reducing latency and preventing response time violations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If LIN messaging is performed between partitions separated by a backbone communication network, then data can be accessed across different LIN partitions, but the LIN response time is violated due to added latency
Solution Approach 1:
The proxy slave anticipatorily receives and stores data from the slave in the second LIN partition before the originating master needs it. This preliminary action ensures that when the read request arrives, the data is already available locally, eliminating the need to wait for backbone network transmission and thus meeting the LIN response time requirement.
Solution Approach 2:
The proxy slave acts as an intermediary between the originating master in the first LIN partition and the slave in the second LIN partition. It receives data from the remote slave, stores it locally, and provides it to the originating master as if it were locally available, thereby mediating the cross-partition communication to maintain LIN response time constraints.
2Reliability
If data is sent through the high-speed backbone network in real-time, then data freshness is maintained, but the response time exceeds LIN specifications
Solution Approach 1:
The system performs preliminary data retrieval and storage actions before they are actually needed. The proxy slave anticipatorily receives data from the slave in the second partition and stores it in its data structure, so that when the originating master requests the data, it is immediately available without requiring real-time backbone network transmission.
Solution Approach 2:
The proxy slave creates a local copy of the data from the slave in the second LIN partition. Instead of repeatedly transmitting the original data through the backbone network, the proxy slave maintains a copy in its data structure, which can be served to multiple originating masters locally, eliminating repeated network latency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A proxy slave in a first LIN partition receives data from a proxy master in the second LIN partition which in turn receives the data from a slave in the second LIN partition. The proxy slave stores the data in a data structure and receives a read request from an originating master in the first LIN partition after the data is stored. The read request comprises a LIN message identifier subscribed to by the slave in the second LIN partition. The proxy slave accesses the data stored in the data structure based on the LIN message identifier in the read request; and sends a LIN response to the originating master with the stored data from the slave in the second LIN partition.