Difference between revisions of "Federate Simulation Bridge"
Jump to navigation
Jump to search
(Created page with "The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These ...") |
|||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These “bridges” have to be created where physical, logical or [[cyber dependency | cyber (inter)dependencies]] between infrastructures occur. Starting from a basic model of these dependencies, these bridges will be created at runtime to create a [[federated simulation]] between existing simulators dynamically. In order to provide this capability, the bridges have to contain several functions and have to be supported by additional components, including: | + | <!--Insert here introductory text regarding the term.--> |
| + | |||
| + | ==Definitions== | ||
| + | <!-- This section presents all available definitions of the above term.--> | ||
| + | |||
| + | === European Project Definitions === | ||
| + | ==== CIPRNet project ==== | ||
| + | {{quote-ciprnet|Federate simulation bridge is the coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. }}<br/> | ||
| + | |||
| + | ==== DIESIS project ==== | ||
| + | {{quote-diesis|The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These “bridges” have to be created where physical, logical or [[cyber dependency | cyber (inter)dependencies]] between infrastructures occur. Starting from a basic model of these dependencies, these bridges will be created at runtime to create a [[federated simulation]] between existing simulators dynamically. In order to provide this capability, the bridges have to contain several functions and have to be supported by additional components, including: | ||
* a Knowledge Base System (KBS) - shared among the [[federate]] subjects – able to gather, filter and maintain traces of any possible synergic actions driving a [[federated simulation]] | * a Knowledge Base System (KBS) - shared among the [[federate]] subjects – able to gather, filter and maintain traces of any possible synergic actions driving a [[federated simulation]] | ||
| − | * a basic [[model]] to containing a specific scenario (including initial situations, maps, etc) and a description of dependencies. A [[scenario]] can also include some kind of script to | + | * a basic [[model]] to containing a specific scenario (including initial situations, maps, etc) and a description of dependencies. A [[scenario]] can also include some kind of script to introduce faults and attacks into running [[simulation]]s |
| − | * a versatile timing mechanism to manage the synchronism inside the [[federated simulation]]. | + | * a versatile timing mechanism to manage the synchronism inside the [[federated simulation]].}} |
| + | <!--- | ||
| + | === Other International Definitions === | ||
| + | ==== United Nations’ Definition ==== | ||
| + | |||
| + | === National Definitions === | ||
| + | ==== Country Name==== | ||
| + | |||
| + | ===Standard Definition=== | ||
| + | --> | ||
| + | |||
| + | ===Standard Definition=== | ||
| + | <!--Insert the text of the definition. Each definition should be formatted as a heading level 4, followed by the text of the definition. --> | ||
| + | |||
| + | == Discussion Topic == | ||
| + | <!-- Discuss topics related to the term, such as closely-related terms, differences among definitions, how to use the definitions provided, open issues, etc. --> | ||
| + | |||
| + | ==See also== | ||
| + | * [[Simulation]] | ||
| + | * [[Federate]] | ||
| + | |||
| + | |||
| + | ==Notes== | ||
| + | <!-- The references will be automatically be listed below. In order to reference --> | ||
| + | <references /> | ||
| + | |||
| + | ==References== | ||
| + | <!-- Additional references can also be added below.--> | ||
| + | |||
| − | [[Category:DIESIS- | + | <!-- Add category, i.e. [[Category:Main]] --> |
| + | [[Category:CIPRNet-Glossary]][[Category:DIESIS-Glossary]][[Category:Simulation]] | ||
| + | {{#set:defined by=EU project}} | ||
Latest revision as of 14:04, 22 December 2016
Contents
Definitions
European Project Definitions
CIPRNet project
The CIPRNet project [1] uses the following definition:
Federate simulation bridge is the coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators.
DIESIS project
The DIESIS project [2] gives the following definition:
The coupling between the different CI simulators has to be “intelligent” in some way to provide a “bridge” between the different, very heterogeneous simulators. These “bridges” have to be created where physical, logical or cyber (inter)dependencies between infrastructures occur. Starting from a basic model of these dependencies, these bridges will be created at runtime to create a federated simulation between existing simulators dynamically. In order to provide this capability, the bridges have to contain several functions and have to be supported by additional components, including:
- a Knowledge Base System (KBS) - shared among the federate subjects – able to gather, filter and maintain traces of any possible synergic actions driving a federated simulation
- a basic model to containing a specific scenario (including initial situations, maps, etc) and a description of dependencies. A scenario can also include some kind of script to introduce faults and attacks into running simulations
- a versatile timing mechanism to manage the synchronism inside the federated simulation.
Standard Definition
Discussion Topic
See also
