SoC Time Domain Synchronization via Intermediary Trigger Events
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems on chip face difficulties in synchronizing different time domains, such as Precision Time Measurement (PTM) protocols used by PCIe interfaces and Precision Time Protocol (PTP) protocols used by Ethernet interfaces, which are not directly compatible, requiring a method to synchronize these disparate time domains without modifying existing communication interfaces.
Innovation Solution
A method that uses a third time domain as an intermediary to detect periodic trigger events and acquire current timestamp values from multiple time domains, comparing differential durations to synchronize the second time domain with the first time domain, utilizing existing timestamp information without altering the first or second time domain's structure or operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If different communication protocols (PTM for PCIe, PTP for Ethernet) are used to share time information, then each protocol can provide precise time synchronization within its own domain, but the time domains become incompatible and cannot be directly synchronized with each other
Solution Approach 1:
The patent introduces a third time domain as an intermediary between the first time domain (PTM/PCIe) and the second time domain (PTP/Ethernet). This intermediary time domain enables comparison and synchronization of timestamp values from different protocols without requiring direct compatibility between them. The third time domain acts as a mediator that can receive and compare timestamp information from both PTM and PTP protocols, allowing synchronization while maintaining protocol independence.
2Adaptability or versatility
If communication interfaces are modified to enable direct synchronization between different time domains, then synchronization compatibility improves, but compatibility with third-party devices and existing standards is compromised
Solution Approach 1:
By introducing the third time domain as an intermediary, the patent enables synchronization between different time domains without modifying the existing communication interfaces. The intermediary handles the protocol conversion and timestamp comparison, allowing the original PTM and PTP interfaces to remain unchanged and maintain their compatibility with third-party devices while still achieving cross-protocol synchronization.
3Measurement precision
If timestamp values from different time domains are directly compared, then synchronization can be achieved, but the different coding formats and precision levels of various protocols make direct comparison difficult
Solution Approach 1:
The patent employs parameter changes by introducing a third time domain with specific timing characteristics that can accommodate and compare timestamp values from different protocols. The intermediary time domain enables conversion and comparison of timestamp parameters (such as frequency, resolution, and format) without requiring complex direct translation between incompatible formats. This approach simplifies the comparison process while maintaining precision.
Data Source
AI summary
A method for synchronizing a first time domain with a second time domain of a system on chip includes a detection of at least one periodic trigger event generated in the first time domain, the second time domain or in a third time domain; acquisitions, made at the instants of the at least one trigger event, of the current timestamp values representative of the instantaneous states of the time domain(s) other than the trigger time domain; a comparison, made in the third time domain, between differential durations between current timestamp values which are respectively acquired successively; and a synchronization of the second time domain with the first time domain, on the basis of the comparison.