Dynamic Two-Wire Interface Frame Structure for Bandwidth Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional two-wire interfaces, such as the MDIO interface, have a fixed frame structure that is inefficient for devices with smaller memory capabilities and often waste bandwidth due to the need for extensive address bits and separate operations for read/write operations, leading to suboptimal communication efficiency.
Innovation Solution
A guaranteed header two-wire interface that dynamically adjusts its frame structure based on the operation code, allowing for extended address fields, reliability fields, and optional CRC and acknowledgement fields to be included or excluded depending on the communication needs, thereby optimizing bandwidth and reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fixed frame structure with extensive address bits is used in conventional two-wire interfaces, then device identification and addressing capability are ensured, but bandwidth is wasted and communication efficiency deteriorates when communicating with devices having smaller memory capabilities
Solution Approach 1:
The frame structure is made dynamic by allowing the address field length to be variable rather than fixed. The interface can adjust the number of address bits transmitted based on the specific device being addressed and the operation type, thereby adapting the frame structure to match the actual communication needs and avoid wasting bandwidth on unnecessary address bits.
Solution Approach 2:
The patent changes the parameter of address field length from a fixed value to a variable value that can be adjusted based on device capabilities and operation requirements. This parameter change allows the system to optimize bandwidth utilization by transmitting only the necessary number of address bits for each specific communication scenario.
2Reliability
If separate operations are used for read and write operations in conventional two-wire interfaces, then operation specificity is ensured, but the number of operation codes increases and bandwidth utilization deteriorates
Solution Approach 1:
The patent merges the read and write operation codes into a single unified operation code structure. Instead of requiring separate operation codes for read and write operations, the system uses a combined operation code that specifies both the operation type and the direction (read/write) within a more compact encoding scheme, thereby reducing the total number of operation codes and improving bandwidth utilization.
3Reliability
If a guaranteed header structure with extensive header fields is used, then data integrity and operation identification are ensured, but header overhead increases and effective data transfer ratio deteriorates
Solution Approach 1:
The patent extracts and removes unnecessary header fields from the frame structure based on the specific operation being performed. Instead of including all possible header fields in every frame, the system selectively includes only the header fields that are necessary for the current operation, thereby reducing header overhead and improving the ratio of effective data transfer to total transmission.
4Adaptability or versatility
If extensive address fields are included in every frame, then addressing capability for large memory devices is ensured, but bandwidth is wasted when communicating with devices having smaller memory capabilities
Solution Approach 1:
The address field length is made dynamic and adaptive to the specific device being addressed. The system determines the appropriate address field length based on the device's memory capabilities and adjusts the frame structure accordingly, thereby avoiding the transmission of excessive address bits when communicating with devices that have smaller memory spaces and reducing bandwidth waste.
Data Source
AI summary
A guaranteed two-wire interface in which upon determining that an operation is to be performed on a slave component, a master component transmits at least a portion of a corresponding frame to the slave component over the data wire. The master component repeats this detection and transmission each time it determines that an operation is to be performed on a slave component, whether the same component or a different slave component as the slave component previously communicated with. The frame structure itself may change depending on the operation to be performed. For example, one frame might include an extended address data field that includes extended address information that goes beyond a basic address field included in another frame. One frame may include reliability fields (such as cyclic redundancy checking field, an acknowledgement field, and/or an error field), whereas another frame having a different operation may not.