Byzantine clock synchronization

Lamport, Leslie; Smith, Peter M. Melliar

doi:10.1145/12476.12477

Cited by 22 publications

(8 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…1(f). After that, all fault-free processors must delete the messages in the fourth level of the ms-tree [7], and then the remaining messages in the three level of ms-tree will not be influenced by the malicious faulty links anymore. After finish removing the influence caused by the malicious links, all fault-free processors can find out the reliable processors by examining the values stored in the second and third level of the ms-tree.…”

Section: The Details Of the Ngba Protocolmentioning

confidence: 99%

“…However, the previous works [1], [7], [8], [11], [14] only consider the agreement problem when there exists processors fault only, and the faulty transmission media are treated as faulty processors. As a result, the treatment ignores the fact that the processor connected with a faulty transmission medium, which was called innocent processor, is still in correct.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

New Approach to Improve the Generalized Byzantine Agreement Problem

Hsieh¹,

Mao-Lun²

2015

IJCTE

View full text Add to dashboard Cite

Abstract-To achieve reliability, it is very important to study the agreement and fault-tolerance topic in distributed systems. This kind of problem is known as a Byzantine Agreement (BA) problem. It requires a set of processors to agree on a common value, even if some processors and transmission media are faulty. Basically, the traditional BA protocols require (n-1)/3 + 2 rounds of message exchange to make each processor reach an agreement. In other words, those protocols are inefficient and unreasonable, due to the number of message results in a large protocol overhead. In this study, we propose a novel and efficient protocol to reduce the amount of messages. Our protocol can compare and replace the messages received from other processors to find out the reliable processors and replace the value sent by the un-reliable processors through four rounds of message exchange even when the total number of faulty components or the total number of processors in the system is large. Finally, the agreement can be reached by using the minimum number of messages in the distributed system, while tolerating the maximum number of faulty components.

show abstract

Section: The Details Of the Ngba Protocolmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

New Approach to Improve the Generalized Byzantine Agreement Problem

Hsieh¹,

Mao-Lun²

2015

IJCTE

View full text Add to dashboard Cite

show abstract

“…Synchrony of FTDF makes this check unnecessary. Clearly the execution platform must contain the implementation of a synchronization algorithm [21].…”

Section: Replica Determinismmentioning

confidence: 99%

Platform-Based Design for Embedded Systems

Sgroi¹,

Sangiovanni‐Vincentelli²,

Bernardinis³

et al. 2005

Embedded Systems Handbook

View full text Add to dashboard Cite

A platform is an abstraction layer that hides the details of several possible implementation refinements of the underlying layers. It is a library of elements characterized by models that represent their functionalities and offer an estimation of (physical) quantities that are of importance for the designer. The library contains interconnects and rules that define what are the legal composition of the elements. A legal composition of elements and interconnects is called a platform instance. Platform-based design is a meet-in-the-middle process, where successive refinements of specifications meet with abstractions of potential implementations that are captured in the models of the elements of the platform. It is this characteristic that makes platform-based design a novel design method.We argue for the importance of structuring precisely the platform layers and we discuss how to define formally the transitions from one platform to the next. In particular, we emphasize the interplay of top-down constraint propagation and bottomup performance estimation while illustrating the notion of articulation point in the design process. In this context, we study the key role played by the API platform together with the micro-architecture platform in embedded system design. Also, we report on three applications of platform-based design: at the system-level, we discuss network platforms for communication protocol design and fault-tolerant platforms for the design of safety-critical applications; at the implementation level, we present analog platforms for mixed-signal integrated circuit design.

show abstract

“…Synchrony of FTDF makes this check unnecessary. Clearly a synchronization algorithm must be implemented in the execution platform, see in example [17].…”

Section: Replica Determinismmentioning

confidence: 99%