IECON 2018 - 44th Annual Conference of the IEEE Industrial Electronics Society 2018
DOI: 10.1109/iecon.2018.8592737
|View full text |Cite
|
Sign up to set email alerts
|

Replication Strategies for Distributed IEC 61499 Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 5 publications
0
3
0
Order By: Relevance
“…The interaction scenarios depend on the system distribution and the replication performed by the application designer, that is, on the components that send events and/or data ➁ (one-to-many), the receivers ➄ (many-to-one) or both ➃ (many-to-many) are replicated components or not, as you can see in Fig. 4 and explained in [12] and [13].…”
Section: Overview Of Iec 61499 Replicationsmentioning
confidence: 99%
“…The interaction scenarios depend on the system distribution and the replication performed by the application designer, that is, on the components that send events and/or data ➁ (one-to-many), the receivers ➄ (many-to-one) or both ➃ (many-to-many) are replicated components or not, as you can see in Fig. 4 and explained in [12] and [13].…”
Section: Overview Of Iec 61499 Replicationsmentioning
confidence: 99%
“…Component replication can be performed using multiple replicas, however, the most common is the use of two (f + 1) or three replicas (2 * f + 1), to tolerate f failures. Therefore, replication based on these assumptions places us in the presence of several communication/interaction scenarios in which the exchange of messages can be defined according to the following four approaches [22]: 1-to-1 (communication from a nonreplicated FB to another nonreplicated or communication inside of the replica, base of the IEC 61499 communication); 1-to-many (communication from a nonreplicated FB to a group of replicated FB. An atomic multicast protocol [9] must be used to ensure that all the replicas received the same set of information (data/events) in the same order.…”
Section: Proposed Iec 61499 Implementationmentioning
confidence: 99%
“…Therefore, the concept of timed messages [10] must be implemented to define the correct order of the execution of the received data. Thus, according to the mapping of the replication scenarios presented in [22], the application clocks must be synchronized. Data to be disseminated are associated with the availability times, defined by the execution times of the FBs to which the events/data are linked, that is, immediately after their execution.…”
Section: Consolidation and Voting Replicate Inputsmentioning
confidence: 99%