INTERFACE AND METHOD FOR COMMUNICATION BETWEEN A SIMULATION APPLICATION AND A PERIPHERAL SIMULATOR

Description

State of the art

[0001] The invention relates to communication between a simulation application and a peripheral simulator.

[0002] US 2011 / 202553 A1 discloses a method for handling spatially referenced multisensory data. The method includes identifying a voxel database. Data elements are stored using the voxels. Some of the data elements comprise a variety of different sensory attributes. These different sensory attributes include visual attributes and at least one attribute selected from a group consisting of a spectral signature attribute, an olfactory attribute, an auditory attribute, a gustatory attribute, a somatic attribute, and a material composition attribute.

[0003] US 4 484 266 A discloses an "ESI peripheral simulator" which is arranged to transmit signals between a simulation computer and a tactical computer, where the abbreviation "ESI" stands for "Externally Specified Index".

[0004] EP 1 359 558 A2 discloses a flight simulator. The black box used in a simulator platform is simulated by separating the software and software-executing components of the simulated black box from the interface hardware components that form the signal interface between the simulated black box and the simulator platform.

[0005] US 4 207 687 A also reveals a flight simulator.

[0006] Operational training systems are training tools that enable users of real-world systems, such as ships, to learn and practice the mastery of complex technologies. The need for testing and training is increasing due to growing technological complexity. Due to increasing networking, it is desirable to enable as many participants as possible to take part in an exercise. Ideally, operational training systems should be available that can be used regardless of system availability. For this purpose, a simulation network can be established for a training environment, comprising simulators of real-world systems and real-world systems themselves.

[0007] Communication within the simulation network takes place via a communication network and requires connections to national and international partners. This involves the use of a simulation application and communication protocols that must meet specific requirements regarding application security and communication technology.

[0008] The individual components of the simulation network must be approved for simulation application and communication. The certification effort for this is very high. Disclosure of the invention

[0009] Thanks to the interface, the system, and the procedure based on independent requirements, simulators from different systems are easily interchangeable. This makes it possible to conduct a wide variety of training exercises.

[0010] The interface can communicate with peripheral simulators via communication protocols approved for a simulation network. These communication protocols are used, for example, for signal transmission or addressing. In this example, packet-switched signals can be sent using the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The use of an encryption protocol may also be possible. The simulation function determines a signal specific to the peripheral simulator from a signal specific to the class, and vice versa. For example, the simulation function determines one or more quantities from the class-specific signal and one or more quantities from the peripheral simulator-specific signal, and vice versa. The class-specific signal comprises the quantities required for the simulation application to simulate a device of that class.The signal specific to the peripheral simulator includes the parameters required to control the peripheral simulator. This allows the simulation application and communication protocols to be certified for a class of peripheral simulators within a system. Integrating another peripheral simulator from a system within a known class is thus simplified.

[0011] The functional element includes at least one instruction for reformatting a signal specific to the peripheral simulator into a signal specific to the class. This makes it particularly easy to implement different signals.

[0012] The functional element can be configured to receive the signal specific to the peripheral simulator from the peripheral simulator and to send the class-specific signal with a label for the peripheral simulator. Alternatively, the functional element can be configured to receive the class-specific signal with a label for a peripheral simulator and to send the signal specific to the peripheral simulator to the peripheral simulator defined by that label. These are ways of assigning the class-specific signal to the peripheral simulator.

[0013] The first interface can be configured to communicate with the simulation application in a primary data format, while the second interface can be configured to communicate with the peripheral simulator in a secondary data format, specifically one that differs from the first. The data formats for signal transmission can be independent of the data format used to transmit the simulation parameters.

[0014] The functional element can include at least one instruction for receiving the signal specific to the peripheral simulator in the second data format and for sending the signal specific to the class in the first data format. This provides a way to determine, on the one hand, the quantities to be processed by the simulation function within the functional element from signals for transport, and on the other hand, to generate signals for transport from quantities processed by the simulation function.

[0015] The simulation function can be configured to determine a simulation parameter specific to the peripheral simulator depending on a simulation parameter specific to the class, or to determine a simulation parameter specific to the class depending on a simulation parameter specific to the peripheral simulator. These simulation parameters can be actual or target values ​​of a simulated real-world technical device that the peripheral simulator replicates.

[0016] The class characterizes a system type, in particular a radar system, a weapon system, an electro-optical sensor, an electromagnetic sensor, or a defense system. The peripheral simulator models a subsystem of the system type, in particular a stationary radar or a rotating radar. The interface has a multitude of functional elements specific to different classes and system types, each comprising a multitude of implementations of simulation functions specific to different peripheral simulators.

[0017] A system for controlling a peripheral simulator from a class of simulators comprises a kernel and this interface. The kernel includes the simulation application.

[0018] The simulation application is configured to receive a signal specific to the class of peripheral simulator, which includes a first simulation parameter specific to that class, to determine a second simulation parameter specific to that class, and to control the peripheral simulator with a signal specific to that class, which includes the second simulation parameter specific to that class. The simulation application is thus ready for operation within that class. Re-enabling is not required when adding a peripheral simulator to the simulation network or when modifying a peripheral simulator within the simulation network.

[0019] The first simulation parameter can characterize the actual and / or target value for the simulation application. The second simulation parameter can characterize an actual and / or target value for the peripheral simulator.

[0020] The system can include a peripheral simulator, wherein the peripheral simulator is configured to receive a simulation parameter specific to the peripheral simulator, in particular an actual and / or target value for the peripheral simulator, in a signal specific to the peripheral simulator, and to control an actuator of the peripheral simulator depending on the simulation parameter specific to the peripheral simulator. The peripheral simulator can comprise software and hardware. The actuator can be controlled to execute an action of the peripheral simulator or to output a signal perceptible to a user of the peripheral simulator, in particular visually, haptically, or audibly.

[0021] It may be provided that the functional element receives the signal specific to the peripheral simulator from the peripheral simulator and sends the signal specific to the class with a label of the peripheral simulator.

[0022] It may be provided that the functional element receives the class-specific signal with a label of the peripheral simulator and sends the peripheral simulator-specific signal to the peripheral simulator defined by the label.

[0023] It may be provided that the first interface communicates at least temporarily with the simulation application in a first data format, while the second interface communicates at least temporarily with the peripheral simulator in a second data format different from the first.

[0024] It may be provided that the functional element executes at least one instruction to receive the signal specific to the peripheral simulator in the second data format and to send the signal specific to the class in the first data format.

[0025] It may be provided that the functional element executes at least one instruction to receive the signal specific to the class in the first data format and to send the signal specific to the peripheral simulator in the second data format.

[0026] It may be provided that the simulation function determines a simulation parameter specific to the peripheral simulator depending on a simulation parameter specific to the class, or determines a simulation parameter specific to the class depending on a simulation parameter specific to the peripheral simulator.

[0027] It may be provided that the simulation function determines a simulation parameter specific to the peripheral simulator depending on a simulation parameter specific to the class, or determines a simulation parameter specific to the class depending on a simulation parameter specific to the peripheral simulator.

[0028] Further advantageous embodiments will become apparent from the following description and the drawing. The drawing shows: Fig. 1 a schematic view of a system, Fig. 2 steps in a procedure for operating the system.

[0029] In Figure 1 A system 100 for controlling a peripheral simulator 102 is shown schematically.

[0030] The system 100 comprises a peripheral simulator 102 from a class of simulators, a kernel 104, and an interface 106. In the example, the system comprises a variety of peripheral simulators 102 from different classes.

[0031] The class characterizes a type of system. The system type can be a radar system, a weapon system, an electro-optical sensor, an electromagnetic sensor, or a defense system.

[0032] In this example, the peripheral simulator 102 models a subsystem of the system type. The peripheral simulator 102 can, for example, model a fixed radar or a rotating radar. In this example, the fixed radar and the rotating radar are assigned to the class "Radar System". Models of operations centers for different ship types can be created by combining different classes.

[0033] Kernel 104 includes a simulation application. In this example, the simulation application comprises several parts, which are located in Figure 1 are designated with the reference numbers 104-1, ..., 104-n.

[0034] The simulation application is configured to receive a signal 108 specific to the class of peripheral simulator 102, which includes a first simulation parameter specific to the class. In the example, the simulation application is configured to process a first simulation parameter specific to the class radar system, regardless of whether the peripheral simulator is a stationary radar or a rotating radar.

[0035] The first simulation parameter can characterize an actual and / or target value for the simulation application 104-1, ..., 104-n. In the example, an actual or target value is used that characterizes an operating parameter of a radar system.

[0036] The simulation application can be configured to receive a variety of initial simulation parameters from various peripheral simulators 102.

[0037] The simulation application is configured to determine a second simulation parameter specific to the class. In the example, the simulation application is configured to process a second simulation parameter specific to the class "Radar System", regardless of whether the peripheral simulator is a stationary or a rotating radar.

[0038] The second simulation parameter characterizes an actual and / or target value for the peripheral simulator 102. In the example, an actual or target value is used that characterizes an operating parameter of a radar system.

[0039] The simulation application can be configured to determine a variety of second simulation parameters for other peripheral simulators, depending on the first simulation parameter. The simulation application can be configured to determine the second simulation parameter depending on the variety of first simulation parameters.

[0040] The simulation application is configured to control the peripheral simulator with a class-specific signal 108, which includes the class-specific second simulation parameter.

[0041] The peripheral simulator 102 can be configured to receive a simulation parameter specific to the peripheral simulator 102, in particular an actual and / or target value for the peripheral simulator 102, in a signal 110 specific to the peripheral simulator 102, and to control an actuator 112 of the peripheral simulator 102 depending on the simulation parameter specific to the peripheral simulator 102.

[0042] The peripheral simulator 102 can be configured to control the actuator 112 to perform an action of the peripheral simulator 102 or to output a signal that is perceptible to a user of the peripheral simulator 102, in particular visually, haptically or acoustically.

[0043] The interface 106 for communication between the simulation application and a communication line 114, e.g. a point-to-point connection, is described below.

[0044] The interface 106 comprises a first interface 116 for the simulation application and a second interface 118 for at least one peripheral simulator 102. Data transmission between the simulation application and the first interface 116 and data transmission between the at least one peripheral simulator 102 and the second interface 118 is carried out, for example, via a communication device 120.

[0045] In this example, the communication device 120 is configured for communication with an infrastructure 124 and for communication with a large number of peripheral simulators 102 that can be connected via respective communication lines 114. The communication device 120 can also be configured specifically for a particular class of peripheral simulators 102 or specifically for a particular peripheral simulator 102.

[0046] Between the first interface 116 and the second interface 118, a functional element 122 specific to a particular class is arranged.

[0047] The functional element 122 specific to this class includes an implementation of a simulation function specific to the peripheral simulator 102.

[0048] In this example, kernel 104 comprises infrastructure 124. Infrastructure 124 is configured to send and receive class-specific signals 108. A communication network 126 connects the parts of the simulation application 104-1, ..., 104-n to each other and to infrastructure 124.

[0049] In this example, the peripheral simulator 102 comprises a computing unit 128, which is configured to communicate with the interface 106 using signals 110 specific to the peripheral simulator 102. The computing unit 128 is configured to perform functions specific to the peripheral simulator 102, such as controlling the actuator 112.

[0050] In the example, the peripheral simulators 102 are combined into a network 130, in which a simulation can be performed with the simulation application.

[0051] The functional element 122 and the simulation function are described below for a peripheral simulator 102 from a specific class. The functional element and the simulation function for other peripheral simulators 102 from the same class can be configured in the same way. For peripheral simulators 102 from a different class, a functional element 122 and a simulation function configured for that class are provided.

[0052] The simulation function is designed in one aspect to determine the simulation parameter specific to the peripheral simulator 102 depending on the second simulation parameter specific to the class.

[0053] In the example, the simulation function is designed to process the second simulation parameter specific to the class radar system, depending on whether the peripheral simulator is a stationary radar or a rotating radar.

[0054] The simulation function is designed in one aspect to determine the first simulation parameter specific to the class, depending on a simulation parameter specific to the peripheral simulator.

[0055] In the example, the simulation function is designed to process the first simulation parameter specific to the class radar system, depending on whether the peripheral simulator is a stationary radar or a rotating radar.

[0056] This allows the kernel to be certified for a system type, i.e., a class. A new subsystem of an already certified system type can then be added via interface 106 without altering the result of the kernel certification. Interface 106 certification can be achieved by certifying the functional element for the class that includes the simulation function.

[0057] In one aspect, the interface 106 has a multitude of functional elements 122 specific to different classes for different system types, each comprising a multitude of implementations of simulation functions specific to different peripheral simulators 102.

[0058] The functional element 122 can include at least one instruction for reformatting the signal 110 specific to the peripheral simulator 102 into a signal 108 specific to the class.

[0059] The functional element 122 can include at least one instruction for reformatting the class-specific signal 108 into a peripheral simulator-specific signal 110.

[0060] In one aspect, the functional element 122 is designed to receive the signal 110 specific to the peripheral simulator 102 from the peripheral simulator 102 and to send the class-specific signal 108 with a designation of the peripheral simulator 102.

[0061] The functional element 122 can be configured to receive the class-specific signal 108 with a designation of a peripheral simulator 102 and to send the peripheral simulator 102-specific signal 110 to the peripheral simulator 102 defined by the designation.

[0062] The designation can refer to the peripheral simulator 102 in a single training environment and can be used in a variety of different training environments.

[0063] The first interface 116 is designed in one aspect to communicate with the simulation application in a first data format.

[0064] The second interface 118 is designed in one aspect to communicate with the peripheral simulator 102 in a second data format, different from the first data format.

[0065] Communication can take place in an interface-compliant manner with existing and certified transitions between communication systems of different networked elements.

[0066] The functional element 122 can include at least one instruction for receiving the signal 110 specific to the peripheral simulator 102 in the second data format and for sending the signal 108 specific to the class in the first data format.

[0067] The functional element 122 can include at least one instruction for receiving the class-specific signal 108 in the first data format and for sending the peripheral simulator 102-specific signal 110 in the second data format.

[0068] A procedure for operating the system is described below with reference to Figure 2 described.

[0069] In the process, interface 106 communicates at least temporarily via the first interface 116 to the simulation application and via the second interface 118 to the communication device 120 for the communication line 114.

[0070] The communication device 120 communicates at least temporarily with the peripheral simulator 102 from the class of simulators, which can be connected via the communication line 114.

[0071] The functional element 122, which is specific to the class and is arranged between the first interface 116 and the second interface 118, performs the implementation of the simulation function specific to the peripheral simulator, at least temporarily.

[0072] In step 202, a simulation parameter specific to the peripheral simulator 102 is determined.

[0073] In step 204, the simulation parameter specific to the peripheral simulator 102 is sent from the peripheral simulator 102 to the functional element 122 in a signal 110 specific to the peripheral simulator 102.

[0074] The peripheral simulator 102 can send the signal 110 specific to the peripheral simulator 102.

[0075] In step 206, the functional element 122, in particular the simulation function, determines a simulation parameter specific to the class of peripheral simulator 102, depending on the simulation parameter specific to peripheral simulator 102.

[0076] The simulation function can determine a simulation parameter specific to the peripheral simulator 102 depending on a simulation parameter specific to the class.

[0077] The functional element 122 can execute at least one instruction to receive the signal 110 specific to the peripheral simulator 102 in the second data format and to send the signal 108 specific to the class in the first data format.

[0078] In step 208, the simulation parameter specific to the class of peripheral simulator 102 is sent from the functional element 122 to the kernel 104 in a signal 108 specific to the class of peripheral simulator 102.

[0079] The class-specific signal 108 can be sent with a designation of the peripheral simulator 102.

[0080] In step 210, a simulation step is executed on kernel 104 depending on the simulation parameter specific to the class of peripheral simulator 102. In the example, a simulation parameter specific to the class of peripheral simulator 102 is determined for controlling the peripheral simulator 102.

[0081] In step 212, the simulation parameter specific to the class of peripheral simulator 102 for controlling the peripheral simulator 102 is sent from the kernel 104 to the functional element 122 in a signal 108 specific to the class of peripheral simulator 102.

[0082] The functional element 122 can receive the class-specific signal 108 with the designation of the peripheral simulator 102.

[0083] In step 214, a simulation parameter specific to the peripheral simulator 102 is determined by the functional element 122, in particular with the simulation function, depending on the simulation parameter specific to the class of the peripheral simulator 102.

[0084] A simulation parameter specific to the class can be determined depending on a simulation parameter specific to the peripheral simulator.

[0085] In step 216, the simulation parameter specific to the peripheral simulator 102 is sent from the functional element 122 to the peripheral simulator 102 in a signal 110 specific to the peripheral simulator 102.

[0086] The signal 110, specific to the peripheral simulator 102, can be sent to the peripheral simulator 102 as defined by the designation.

[0087] In step 218, the peripheral simulator 102 is controlled depending on the simulation parameter specific to the peripheral simulator 102.

[0088] In one aspect, it can be provided that the simulation application receives signals from the peripheral simulator 102 without controlling it. The procedure can then be executed without steps 212 to 218.

[0089] In one aspect, it may be provided that the simulation application controls the peripheral simulator 102 without receiving signals from it. The procedure can then be executed without steps 202 to 208.

[0090] The procedure can provide that the simulation application in the simulation step processes a large number of signals from a large number of peripheral simulators 102 and controls a large number of peripheral simulators 102 with signals.

[0091] In this example, the first interface 116 communicates at least temporarily with the simulation application in the first data format.

[0092] In this example, the second interface 118 communicates at least temporarily with the peripheral simulator 102 in the second data format, which differs from the first data format.

[0093] The functional element 122 can execute at least one instruction to receive the class-specific signal 108 in the first data format and to send the peripheral simulator 102-specific signal 110 in the second data format.

[0094] The peripheral simulator 102 can comprise one or more processors and one or more memories configured to work together to execute steps in the procedure that take place in the peripheral simulator 102. The interface 106 can comprise one or more processors and one or more memories configured to work together to execute steps in the procedure that take place in the interface 106. The kernel 104 can comprise one or more processors and one or more memories configured to work together to execute steps in the procedure that take place in the kernel 104.

Claims

1. Interface (106) for communication between a simulation application (104-1, ..., 104-n) and a peripheral simulator (102) from a class of simulators (102), wherein the interface (106) has a first interface (116) to the simulation application (104-1, ..., 104-n) and a second interface (118) to the peripheral simulator (102), wherein a class-specific functional element (122) is arranged between the first interface (116) and the second interface (118), which functional element comprises an implementation of a simulation function specific to the peripheral simulator (102), wherein the functional element (122) comprises at least one instruction for reformatting a signal (110) specific to the peripheral simulator (102) into a class-specific signal (108) and / or wherein the functional element (122) comprises at least one instruction for reformatting a class-specific signal (108) into a signal (110) specific to the peripheral simulator, wherein the class characterizes a system type and the peripheral simulator (102) models a subsystem of the system type, wherein the interface (106) has a plurality of different class-specific functional elements (122) for different system types, which functional elements each comprise a plurality of implementations of simulation functions specific to different peripheral simulators (102).

2. Interface (106) according to claim 1, characterized in that the functional element (122) is configured to receive the signal (110) specific to the peripheral simulator (102) from the peripheral simulator (102) and to send the class-specific signal (108) together with a designation of the peripheral simulator (102).

3. Interface (106) according to either of claims 1 or 2, characterized in that the functional element (122) is configured to receive the class-specific signal (108) together with a designation of a peripheral simulator (102) and to send the signal (110) specific to the peripheral simulator (102) to the peripheral simulator (102) defined by the designation.

4. Interface (106) according to any of claims 1 to 3, characterized in that the first interface (116) is configured to communicate with the simulation application (104-1, ..., 104-n) in a first data format, the second interface (118) being configured to communicate with the peripheral simulator (102) in a second data format, in particular which is different from the first data format.

5. Interface (106) according to claim 4, characterized in that the functional element (122) comprises at least one instruction for receiving the signal (110) specific to the peripheral simulator (102) in the second data format and for sending the class-specific signal (108) in the first data format.

6. Interface (106) according to either of claims 4 or 5, characterized in that the functional element (122) comprises at least one instruction for receiving the class-specific signal (108) in the first data format and for sending the signal (110) specific to the peripheral simulator (102) in the second data format.

7. Interface (106) according to any of the preceding claims, characterized in that the simulation function is designed to determine a simulation parameter specific to the peripheral simulator depending on a class-specific simulation parameter, or to determine a class-specific simulation parameter depending on a simulation parameter specific to the peripheral simulator.

8. Interface (106) according to any of the preceding claims, characterized in that the class characterizes a radar system and the peripheral simulator (102) models a fixed radar or a rotating radar, or the class characterizing a weapon system and the peripheral simulator (102) modeling a subsystem of the weapon system class, or the class characterizing an electro-optical sensor and the peripheral simulator (102) modeling a subsystem of the electro-optical sensor class, or the class characterizing an electromagnetic sensor and the peripheral simulator (102) modeling a subsystem of the electromagnetic sensor class, or the class characterizing a defense system and the peripheral simulator (102) modeling a subsystem of the defense system class.

9. System (100) for controlling a peripheral simulator (102) from a class of simulators, characterized in that the system (100) comprises a kernel (104) and the interface (106) according to any of claims 1 to 7, the kernel (104) comprising the simulation application (104-1, ..., 104-n), and the simulation application (104-1, ..., 104-n) being configured to receive a signal (108) specific to the class of the peripheral simulator (102) and comprising a first class-specific simulation parameter, to determine a second class-specific simulation parameter, and to control the peripheral simulator using a class-specific signal (108) which comprises the second class-specific simulation parameter.

10. System (100) according to claim 9, characterized in that the first simulation parameter characterizes an actual value and / or target value for the simulation application (104-1, ..., 104-n) and / or the second simulation parameter characterizes an actual value and / or target value for the peripheral simulator (102).

11. System (100) according to claim 9 or claim 10, characterized in that the system (100) comprises the peripheral simulator (102), the peripheral simulator (102) being configured to receive a simulation parameter specific to the peripheral simulator (102), in particular an actual value and / or target value for the peripheral simulator (102), in a signal (110) specific to the peripheral simulator (102), and to control an actuator (112) of the peripheral simulator (102) depending on the simulation parameter specific to the peripheral simulator (102).

12. System (100) according to claim 11, characterized in that the actuator (112) is controlled to perform an action of the peripheral simulator (102) or to produce an output that is perceptible to a user of the peripheral simulator (102), in particular visually, haptically or acoustically.

13. Method for operating an interface (106) for communication between a simulation application (104-1, ..., 104-n) and a peripheral simulator (102) from a class of simulators, wherein the interface (106) communicates (208, 214), at least at times, with the simulation application (104-1, ..., 104-n) via a first interface (116) and communicates (204, 216), at least at times, with the peripheral simulator (102) via a second interface (118), wherein a class-specific functional element (122) arranged between the first interface (116) and the second interface (118) performs (206, 214), at least at times, an implementation of a simulation function specific to the peripheral simulator, wherein the functional element (122) performs (206) at least one instruction for reformatting a signal (110) specific to the peripheral simulator (102) into a class-specific signal (108) and / or wherein the functional element (122) performs at least one instruction for reformatting a class-specific signal (108) into a signal (110) specific to the peripheral simulator (102), wherein the class characterizes a system type and the peripheral simulator (102) models a subsystem of the system type, wherein the interface (106) has a plurality of different class-specific functional elements (122) for different system types, which functional elements each comprise a plurality of implementations of specific simulation functions for different peripheral simulators (102).

14. Method according to claim 13, characterized in that the functional element (122) receives (204) the signal (110) specific to the peripheral simulator (102) from the peripheral simulator (102) and sends (208) the class-specific signal (108) together with a designation of the peripheral simulator (102).

15. Method according to claim 13 or claim 14, characterized in that the functional element (122) receives (212) the class-specific signal (108) together with a designation of the peripheral simulator (102) and sends (216) the signal (110) specific to the peripheral simulator (102) to the peripheral simulator (102) defined by the designation.

16. Method according to claims 13 to 15, characterized in that the first interface (116) communicates (208, 212), at least at times, with the simulation application (104-1, ..., 104-n) in a first data format, the second interface (118) communicating (204, 216), at least at times, with the peripheral simulator (102) in a second data format which is different from the first data format.

17. Method according to claim 16, characterized in that the functional element (122) performs (206) at least one instruction for receiving the signal (110) specific to the peripheral simulator (102) in the second data format and for sending the class-specific signal (108) in the first data format.

18. Method according to claim 16 or claim 17, characterized in that the functional element (122) performs (214) at least one instruction for receiving the class-specific signal (108) in the first data format and for sending the signal (110) specific to the peripheral simulator (102) in the second data format.

19. Method according to any of claims 12 to 17, characterized in that the simulation function determines (206) a simulation parameter specific to the peripheral simulator (102) depending on a class-specific simulation parameter, or determines (214) a class-specific simulation parameter depending on a simulation parameter specific to the peripheral simulator.

20. Method according to any of claims 13 to 19, characterized in that the class characterizes a radar system and the peripheral simulator (102) models a fixed radar or a rotating radar, or the class characterizing a weapon system and the peripheral simulator (102) modeling a subsystem of the weapon system class, or the class characterizing an electro-optical sensor and the peripheral simulator (102) modeling a subsystem of the electro-optical sensor class, or the class characterizing an electromagnetic sensor and the peripheral simulator (102) modeling a subsystem of the electromagnetic sensor class, or the class characterizing a defense system and the peripheral simulator (102) modeling a subsystem of the defense system class.