Challenges deploying PTPv2 in a global financial company

Estrela, P.V.; Bonebakker, Lodewijk

doi:10.1109/ispcs.2012.6336634

Cited by 20 publications

(11 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The underlying unicast routing is a crucial part of distributing multicast traffic over multi-hop networks, without which forwarding can fail due to RPF checks [12]. Another common problem, highlighted by Estrela and Bonebakker [13], are slave implementations defaulting to low multicast TTL values, which when set lower than the number of network hops, result in a loss of multicast transmission.…”

Section: B Network Issuesmentioning

confidence: 99%

“…The fact that different modes that do not interoperate, are allowed within the same PTP profile (default), proves that PTP profiles alone (Standard subclause 19.3) are not useful in the enterprise -they merely provide default settings. The PTP Enterprise Profile, initially proposed by Estrela and Bonebakker [13], does not embed information in PTP messages to be interpreted by slaves, and thus remains only a recommendation. The recent PTP Enterprise PTP Profile draft [14] looks promising for two reasons: addition of a TLV to the Announce message, which denotes supported transmission modes, but also the definition of the Hybrid mode.…”

Section: ) Inconsistent Functionality -Ptp Profiles Too Generalmentioning

confidence: 99%

“…Dedicated GM products rarely support ACLs -this can be moved to switches or routers, but features such as Delay Request rate limiting should find their way into GM products. Many GMs will accept incoming Delay Requests at higher rates than configured, allowing to overload the GM [13] if not controlled elsewhere.…”

Section: ) Lack Of True Enterprise-grade Gm Hardwarementioning

confidence: 99%

“…Author believes that the use of a single multicast group by PTP version 2 is not a major disadvantage, but support for custom groups would make it easier to group GMs. It is a common engineering practice to separate multicast traffic (one group) into PIM-SM domains with different RPs (mentioned in [13]). This is possible using carefully planned routing policies and features such as multicast borders.…”

Section: Design Considerations and Recommendations For Ptp As A mentioning

confidence: 99%

“…A notable product line supporting multiple satellite constellations, are products from Elproma 2 . To ensure spoofing protection on the slave side, the slave would need to track more than two GMs [13] -not supported by standard.…”

Section: ) Timing Reference (Gps) Securitymentioning

confidence: 99%

See 4 more Smart Citations

Deploying PTP as an Enterprise Service: Issues, challenges and design considerations

Owczarek¹

2013

2013 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control and Communication (ISPCS) Proceed

View full text Add to dashboard Cite

This paper presents an industry experience and research-based analysis of issues that the deployment of PTP as a service is facing in the finance industry, based on real life examples from a global stock exchange operator. It aims to summarise over three years of author's experience with deploying PTP, highlighting the most common problems encountered: standard specific, implementation specific and nontechnical. The paper attempts to define some best practices for achieving high resiliency and service quality levels combined with ease of operation, also touching on design considerations for scalable timing networks. Finally, it makes recommendations for the industry, standard, for vendors and service providers, and presents some novel design concepts for timing networks, contributing to the relatively small public knowledge base.

show abstract

Section: B Network Issuesmentioning

confidence: 99%

Section: ) Inconsistent Functionality -Ptp Profiles Too Generalmentioning

confidence: 99%

Section: ) Lack Of True Enterprise-grade Gm Hardwarementioning

confidence: 99%

Section: Design Considerations and Recommendations For Ptp As A mentioning

confidence: 99%

Section: ) Timing Reference (Gps) Securitymentioning

confidence: 99%

See 3 more Smart Citations

Deploying PTP as an Enterprise Service: Issues, challenges and design considerations

Owczarek¹

2013

2013 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control and Communication (ISPCS) Proceed

View full text Add to dashboard Cite

show abstract

Synchronization performance evaluation of reference clock connection methods for IEEE 1588 master clocks

Kovácsházy

2015

Proceedings of the 2015 16th International Carpathian Control Conference (ICCC)

View full text Add to dashboard Cite

Clock and/or frequency synchronization is a common requirement in modern distributed measurement and control systems, such as Internet of Things (loT). The required precision is application dependent; however, the possibility of sub1 microsecond precision provided by low-cost advanced IEEE 1588 implementations sets the industry standard today. The performance and price of IEEE 1588 implementations are primarily defined by the master clocks and their actual installation and configuration. The paper investigate how master clock architectures, i.e., how the master clock is connected to the reference clock, influence price and performance; and in addition, it also details how the architecture effects installation and configuration requirements. The primary factors of investigation are ambient temperature and delay compensation required due to signal transmission time. The paper also introduces the architecture and performance of a Linux based open source/hardware prototype master clock developed by the author.

show abstract

Performance analysis of a clock state estimator for PROFINET IO IRT synchronization

Fontanelli

Macii

Rinaldi

et al. 2013

2013 IEEE International Instrumentation and Measurement Technology Conference (I2MTC)

View full text Add to dashboard Cite

Clock synchronization is essential to support timebased medium access scheduling and distributed control over industrial networks relying on Real-Time Ethernet (RTE). PROFINET IO is one of the most widely used field-buses in large automation plants. The PROFINET IO Isochronous Real Time (IRT) implementation includes a Precision Transparent Clock Protocol (PTCP) for network-level synchronization. A similar scheme is also used in the second version of the Precision Time Protocol (PTP), standardized as IEEE 1588-2008. Unfortunately, synchronization uncertainty typically grows in the case of long chains of cascaded clocks. In this paper, the accuracy of a clock state estimator based on a Kalman filter is analyzed in the context of PROFINET IO IRT networks. The proposed estimator can be used to compensate the time offsets of every node with respect to the reference master, thus improving synchronization accuracy in the case of long linear topologies beyond the limits of other existing solutions. The presented results are obtained from multiparametric simulations based on the features of real hardware devices.

show abstract

Challenges deploying PTPv2 in a global financial company

Cited by 20 publications

References 8 publications

Deploying PTP as an Enterprise Service: Issues, challenges and design considerations

Deploying PTP as an Enterprise Service: Issues, challenges and design considerations

Synchronization performance evaluation of reference clock connection methods for IEEE 1588 master clocks

Performance analysis of a clock state estimator for PROFINET IO IRT synchronization

Contact Info

Product

Resources

About