PTP Message Conversion for Cross-Method Time Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Time synchronization fails between devices using different transmission delay measurement methods, such as End-to-End and Peer-to-Peer, due to differences in message formats, necessitating separate time distribution networks and high costs.
Innovation Solution
A conversion device that converts the transmission delay measurement method of an upper device to that of a lower device, utilizing Sync, Follow_Up, Delay_Req, Delay_Resp, Pdelay_Req, and Pdelay_Resp messages to synchronize clocks across devices with different methods, without modifying the devices themselves.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate time distribution networks are built for each transmission delay measurement method, then time synchronization reliability is improved, but device complexity and cost increase
Solution Approach 1:
A conversion device is introduced as an intermediary between the upper device and lower device. This conversion device receives PTP messages from the upper device using one measurement method, converts the message format and measurement method, and transmits to the lower device using a different measurement method. This mediator enables compatibility between different measurement methods without requiring separate networks, thus maintaining reliability while reducing complexity.
2Measurement precision
If separate time distribution networks are built for each transmission delay measurement method, then time synchronization accuracy is improved, but loss of substance increases
Solution Approach 1:
The conversion device provides multi-functionality by supporting conversion between multiple transmission delay measurement methods (End-to-End and Peer-to-Peer). A single conversion device can handle different message formats and measurement methods, making the network more universal and eliminating the need for separate dedicated networks for each method, thereby reducing equipment costs while maintaining synchronization accuracy.
3Adaptability or versatility
If devices use different transmission delay measurement methods, then adaptability is improved, but time synchronization reliability deteriorates
Solution Approach 1:
The conversion device acts as a translator between different measurement method profiles. It receives PTP messages with one measurement method profile, extracts the necessary timing information, converts it to the corresponding format of another measurement method, and transmits to the lower device. This intermediary function enables devices with different measurement method adaptabilities to synchronize reliably.
4Reliability
If message formats are modified to enable cross-method synchronization, then time synchronization reliability is improved, but device complexity increases
Solution Approach 1:
The conversion device centralizes the message format conversion logic in a dedicated intermediary component. Rather than requiring each endpoint device to handle multiple message formats and measurement methods, the conversion device alone performs the format translation, simplifying the overall system architecture while ensuring reliable synchronization through proper message format conversion.
Data Source
AI summary
A conversion device (100) includes a Sync message processing unit (11), a Follow_Up message processing unit (12), a Delay_Req message processing unit (13), a Delay_Resp message processing unit (14), a Pdelay_Req message processing unit (21), a Pdelay_Resp message processing unit (22), a Pdelay_Resp_Follow_Up message processing unit (23), an upper-side transmission delay calculation unit (40) that calculates a transmission delay time pt1 between a master device (200) and the conversion device (100), an internal processing time calculation unit (50) that calculates an internal processing time of the conversion device (100), and a CF processing unit (60) that stores a total value of pt1 and the internal processing time in a Follow_Up message.