Communication system for a tactical air defense system

Abstract

Communication system for a tactical air defense system (200), comprising: a communications base station (90) which can be connected to a command post (300) of the tactical air defense system (200) via a wired data network connection (E); one or more edge gateways (10) which are in bidirectional radio communication with the communication base station (90) and which are designed to exchange data with the communication base station (90) according to a common communication protocol; and one or more peripheral adapters (80) which can be connected to one or more edge gateways (10) via wired data network connections (E) and which are designed for the data connection of a peripheral element (500) to the tactical air defense system (200), characterized in that the one or more peripheral adapters (80) each have a core interface (53) and a peripheral interface (47) designed to transmit data exchanged between an edge gateway (10) and a peripheral element (500), to convert regarding a data format and a communication protocol, that the core interface (53) has an instantiated core interface driver (55) which is controlled by an interaction rule set (49) of the peripheral adapter (80) instantiated according to the system component type of the peripheral element (500), and a core interface state machine instantiated according to the system component type of the peripheral element (500), and that operating states of the peripheral element (500) are controllable from the command post (300) of the tactical air defense system (200) via the instantiated core interface state machine of the core interface (53).

Description

TECHNICAL AREA OF INVENTION

[0001] The invention relates to a communication system for a tactical air defense system (ADS), as well as communication methods for data exchange between components of a tactical air defense system. TECHNICAL BACKGROUND

[0002] Air defense systems (ADS) provide close-range and very close-range protection against aerial threats. ADS ensure stationary protection as well as highly mobile escort protection and immediate fire readiness as one of several elements of integrated air defense. ADS often use a unified system architecture for connecting sensors and effectors, which also ensures reliable detection and engagement of current threats from tactical ballistic missiles (TBMs) and air-breathing targets (ABTs), as well as small and very small targets.

[0003] A key component of a high-performance system architecture for an avalanche transceiver (AVS) is mobile optical long-range reconnaissance and observation systems (MOWABS; also known as "long-range reconnaissance and observation systems", LORROS), which use optical sensors such as CCD image sensors as day vision devices and forward-looking infrared (FLIR) cameras as night vision devices to enable the detection, classification, and identification of potential target objects of the AVS.

[0004] Another component of such a system architecture is effector systems for engaging airborne targets. These systems can include, for example, an effector unit such as an air defense missile with associated launchers for igniting the effector systems and / or loading units for loading a launcher canister with one or more effector units. Furthermore, radar systems for surveillance and target tracking, as well as support units such as reconnaissance systems, reloading vehicles, or logistics vehicles, can also be integrated into the system architecture.

[0005] Finally, a command or operational control center assumes tactical control of the effector system, the MOWABS, and, if applicable, other sensor systems. The command or operational control center directs the MOWABS, or other sensor systems, to a known aircraft and delivers online image and / or video data, radar target plots, radar HRR (high-range resolution), and / or radar JEM (jet engine modulation) measurements, etc., of the tracked aircraft to the command or operational control center in real time or near real time. Based on predefined criteria for target acquisition, target classification, target identification, risk assessment, and the rules of engagement, a manual authorization for target engagement in semi-automatic or manual combat mode can be granted, based on the optical data acquired by the MOWABS or other sensor systems.Manual blocking can occur in fully automatic combat mode.

[0006] German patent EP 2 955 475 B1 discloses a ground-based air defense system with such components, which are connected via a central integration module. German patent DE 10 2007 007 404 A1 discloses a method and a device for remotely triggering at least one projectile fired from a weapon. German patent US 4,641,801 A discloses a system for data exchange between individual components of an air defense system via a fire control computer.

[0007] The document IVERSEN, TF: Mobile and Networked Air Defence Systems. In: RTO Meeting Proceedings on Systems Concepts for Integrated Air Defense of Multinational Mobile Crisis Reaction Forces, Neuilly-sur-Seine Cedex (France), March 2001, pp. 17-1–17-8, describes a networked air defense system with central command posts, communication gateways, and network base stations. Publication US 2018 / 0198881 A1 discloses an interface device for connecting weapon systems to a tactical data link.

[0008] However, there is a need for improved communication systems within the framework of tactical air defense, which will simplify the maintenance and modification effort when integrating different components from various manufacturers and ensure that the system sovereignty for the operator is permanently maintained. SUMMARY OF THE INVENTION

[0009] One of the objectives of the invention is therefore to find solutions for communication between components of a tactical air defense system (ADS) that are compatible with the operation of components from different component manufacturers and that establish and permanently maintain the system sovereignty of the ADS user.

[0010] These and other tasks are solved by a communication system with the features of claim 1, a tactical air defense system (ADS) with the features of claim 9, and a method for communication between system components of a tactical air defense system (ADS) with the features of claim 11.

[0011] According to a first aspect of the invention, a communication system, particularly for use in a system architecture of a tactical air defense system as an element of integrated air defense, comprises a communication base station which can be connected to a command post of the tactical air defense system via a wired data network connection, one or more edge gateways which are in bidirectional radio communication with the communication base station and which are designed to exchange data with the communication base station according to a common communication protocol, and one or more peripheral adapters which can be connected to one or more edge gateways via wired data network connections and which are designed for the data connection of a system component or a peripheral element to the tactical air defense system.Each of the one or more peripheral adapters has a core interface and a peripheral interface designed to convert data exchanged between an edge gateway and a peripheral element into a specific data format and communication protocol. The core interface includes an instantiated core interface driver, controlled by an instantiated interaction rule set of the peripheral adapter, and a core interface state machine instantiated according to the system component type of the peripheral element. Operating states of the peripheral element can be controlled by the tactical air defense system's command post via the instantiated core interface state machine of the core interface.

[0012] According to a second aspect of the invention, a tactical air defense system comprises at least one command post, a communication system according to the first aspect of the invention, the communication base station of which is in a wired communication link with the at least one command post, and one or more air defense system components, each of which is in communicative communication link with one or more peripheral adapters and which are designed to exchange data with the at least one command post via the one or more peripheral adapters, the one or more edge gateways and the communication base station.

[0013] According to a third aspect of the invention, a method for communication between system components of an air defense system, in particular for supporting the detection, classification and identification of target objects in a command or operational control center of a tactical air defense system as an element of integrated air defense, comprises the steps of connecting a communication base station to a command post of the tactical air defense system via a wired data network connection, establishing a bidirectional radio communication link between one or more edge gateways and the communication base station, which enables radio-based data exchange according to a common communication protocol, and connecting one or more peripheral adapters to each of the one or more edge gateways via wired data network connections.wherein the one or more peripheral adapters each have a core interface and a peripheral interface designed to convert data exchanged between an edge gateway and a peripheral element with respect to a data format and a communication protocol, and wherein the core interface has an instantiated core interface data store, an instantiated core interface driver controlled by an instantiated interaction rule set of the peripheral adapter, and a core interface state machine instantiated according to an element type of the peripheral element,and the mediation of bidirectional data communication between peripheral elements of the tactical air defense system connected to the one or more peripheral adapters and the command post via the one or more edge gateways and the communication base station, and the control of operating states of the peripheral elements from the command post of the tactical air defense system via the instantiated core interface state machine of the core interface.

[0014] A key aspect of the invention is to differentiate between a core structure and optional peripherals in a tactical avalanche air support system (AAS), and to combine the command or operational command post with a powerful, centrally managed radio communication system for the core structure. This allows the AAS user to maintain control over the architecture and functionality of the core structure and to reconfigure it as needed.

[0015] A particular advantage of the solutions according to the invention is that a centralized, deterministic channel access method can be implemented at the communication level within the core structure. In this method, a fixed base station can efficiently prioritize data transmissions, guaranteeing minimum bandwidth, maximum latency, and maximum packet loss rates via quality of service (QoS). This efficient prioritization creates sufficient resilience of the communication system against potential saturation of the sensor systems and unacceptable delays in sending and receiving time- and content-critical information within the warehouse management system (WMS).

[0016] The command or operational command post can advantageously be equipped with a data rate control system that dynamically adjusts the data volumes to be transferred to the available data transfer capacities of each connected component. The communication system hardware required for data transfers remains transparent to the user of the air traffic control system (AVS) and guarantees full control over information regarding current data link states, such as channel quality, signal-to-noise ratios, modulation and coding schemes, and the like.

[0017] The invention eliminates the need for the mechanical and electrical integration of a radio communication system, including an antenna mast, electric or hydraulic drive, antennas, radio, and encryption devices, into a single peripheral element. This significantly simplifies the connection of additional sensors or other effectors, advantageously enabling the standardization of communication. Furthermore, messages can be prioritized within the core structure, and the message prioritization control remains encapsulated at the heart of the WMS. This simplifies the integration of peripheral elements from different manufacturers. Data volume control remains under the control of the core structure operator.

[0018] Furthermore, unlike in the state of the art, it is no longer necessary to use central integration modules, which makes adaptability to large warehouse management systems with a large number of peripheral elements difficult.

[0019] Advantageous designs and further developments result from the additional sub-claims as well as from the description with reference to the figures.

[0020] According to some embodiments of the communication system, the one or more peripheral adapters can be mobile devices that are in communicative data connection with a peripheral element. Alternatively, according to some further embodiments of the communication system according to the invention, the one or more peripheral adapters can be permanently integrated into a peripheral element.

[0021] According to some embodiments of the communication system, the wired data network connections between the one or more peripheral adapters and the one or more edge gateways can be secure against eavesdropping.

[0022] According to some embodiments of the communication system, the communication base station may further be configured to maintain a command post radio network between multiple command posts of the tactical air defense system.

[0023] Furthermore, according to some embodiments of the communication system, the peripheral interface may include a peripheral element driver and a data converter coupled to the peripheral element driver.

[0024] According to some embodiments of the communication system, the communication base station can implement a centralized, deterministic channel access method or a decentralized, stochastic channel access method to establish the bidirectional communicative radio link with the one or more edge gateways.

[0025] According to some embodiments of the communication system, the communication base station may also be designed to perform transport prioritization between the one or more edge gateways and the communication base station.

[0026] According to some embodiments of the method according to the invention, the step of establishing the bidirectional communicative radio link may include implementing a centralistic, deterministic channel access method for establishing the bidirectional communicative radio link between the communication base station and the one or more edge gateways.

[0027] According to some further embodiments of the method according to the invention, the one or more peripheral adapters can be mobile devices that are in communicative data connection with a system component. Alternatively, according to some further embodiments of the method according to the invention, the one or more peripheral adapters can be permanently integrated into a system component.

[0028] The above embodiments and further developments can be combined with one another as appropriate. Further possible embodiments, further developments, and implementations of the invention also include combinations of features of the invention described previously or subsequently with regard to the exemplary embodiments, even if not explicitly mentioned. In particular, the person skilled in the art will also add individual aspects as improvements or additions to the respective basic form of the present invention. BRIEF SUMMARY OF THE CHARACTERS

[0029] The present invention will be explained in more detail below with reference to the exemplary embodiments shown in the schematic figures. These figures show: Fig. 1 a schematic block diagram of the network environment in a tactical air defense system according to an embodiment of the invention; Fig. 2 a schematic block diagram of the system architecture of a communication system in a tactical air defense system according to a further embodiment of the invention; Fig. 3 an exemplary illustration of a network node according to a further embodiment of the invention, which can be used in a network environment of a tactical air defense system; Fig. 4 a schematic block diagram of a network interface of a network node according to a further embodiment of the invention; Fig. 5 a schematic block diagram of a network interface of a network node according to a further embodiment of the invention; Fig. 6 a schematic block diagram of an edge gateway for a network environment of a tactical air defense system according to a further embodiment of the invention; Fig. 7 a schematic block diagram of a communication base station for a network environment of a tactical air defense system according to an embodiment of the invention; Fig. 8 a schematic block diagram of a peripheral adapter for connecting a system component to a network environment of a tactical air defense system according to a further embodiment of the invention; and Fig. 9 a flowchart of a communication method for data exchange between components of a tactical air defense system according to a further embodiment of the invention.

[0030] The accompanying figures are intended to provide a further understanding of the embodiments of the invention. They illustrate embodiments and, in conjunction with the description, serve to explain the principles and concepts of the invention. Other embodiments and many of the aforementioned advantages become apparent with reference to the drawings. The elements of the drawings are not necessarily shown to scale. Directional terminology such as "above," "below," "left," "right," "over," "below," "horizontal," "vertical," "front," "back," and similar terms are used for explanatory purposes only and are not intended to limit the general public to specific embodiments as shown in the figures.

[0031] In the figures of the drawing, identical, functionally equivalent and similarly acting elements, features and components - unless otherwise stated - are each provided with the same reference symbols. DESCRIPTION OF EXAMPLES OF EXECUTION

[0032] Fig. Figure 1 shows an exemplary illustration of a network environment 100 in a tactical air defense system 200. The network environment 100 of the Fig. The system is structured in a star topology. For example, the central element 300, as the base network node, can typically perform the function of the command post G and temporarily assume the functions of a base station for communication with a large number of network nodes 500. The command post G can, in particular, be a command post or an operational command post.

[0033] If communication with command post G is disrupted, fails, or otherwise becomes unreliable, the star topology can be dynamically adjusted. This can involve a (in Fig. One redundant backup command post (not explicitly illustrated) is maintained, which can then take over the command post function. The remaining 500 network nodes can then be dynamically reconfigured and now communicate in a star topology with the redundant backup command post as the functional star center.

[0034] The in Fig. The components of network environment 100 shown in section 1 are only examples, and further components may be implemented in connection with network environment 100. For example, it may be possible that more or fewer than the seven shown in section 1 are used. Fig. The network nodes 500 shown in the diagram are present in the network environment 100. Furthermore, it should be clear that the network connections shown are between individual network nodes 500 or between network nodes 500 and the central element 300 in the diagram. Fig. 1 are only shown as examples, and that between network nodes 500 among themselves or between network nodes 500 and the central element 300, between which in Fig. 1. A network connection is shown, but a network connection does not necessarily have to exist permanently, and that between network nodes 500 among themselves or between network nodes 500 and the central element 300, between which in Fig. 1. If no network connection is shown, a network connection can be established temporarily or permanently.

[0035] Each of the 500 network nodes is equipped with network-enabled components or network interfaces, allowing each node to automatically establish contact with other nodes via a shared communication medium and to establish a network connection using suitable communication protocols. For example, the communication medium could be open space or the atmosphere, enabling a wireless network connection to be established, such as WLAN according to IEEE 802.11 or other wireless transmission methods in the radio frequency range, IrDA, or optical point-to-point radio links in the infrared or optical frequency range. The network connections established can be unidirectional or bidirectional.Furthermore, the network environment created by the network connections can be meshed, for example by creating redundant radio links to increase network capacity, network security and / or resilience to external disturbances.

[0036] In advantageous configurations, the network environment may not have a mesh structure in order to minimize the additional data volume caused by potentially multi-stage hopping. In some configurations, single-stage or two-stage hopping ("dual-hop relay") may be permitted, for example, for data links between command posts and effectors or support units. This allows, for instance, a sensor system to be positioned as close as possible to the expected target location or as far away from the command post as possible. This advantageously increases the range of the sensor system and its sensors.

[0037] Similarly, the failure of a communication link from the operational command post to one of the peripheral elements, such as an effector or a support unit, can be compensated for by one- or at most two-stage hopping if the corresponding network node 500 does not have an intact or reliable direct radio link to the central element 300, but can establish a radio link to a neighboring network node 500 whose direct radio link to the central element 300 is intact and reliable. For some network nodes 500, such as radar sensors, hopping may be prevented altogether due to the potentially high data volumes, in order to transmit the high data rates only via a direct radio link to the central element 300.

[0038] The network nodes 500 can be different participants in a tactical air defense communication network, such as radar stations R1 and R2 for target tracking or monitoring, launchers S1 and S2, sensors O (e.g., optronic sensors), aircraft A, or missiles F (e.g., drones, rockets, or the like). Furthermore, a mobile, quasi-stationary, or stationary command post G can be designated as the central element 300 of a network environment 100. The network nodes 500 can exchange various types of data with each other and with the central element 300, such as tactical data, Voice over IP traffic, video data, status reports, commands, GPS data, and the like. Data communication can preferably be packet-based, for example, using a time-division multiplexing (TDMA) transmission method.Such communication networks can, for example, benefit from the improved resilience to disturbances and the increased data rates of the network environment 100.

[0039] Fig. Figure 2 shows a schematic block diagram of the system architecture of a communication system in a tactical air defense system, such as the Tactical Air Defense System 200. Fig. 1. The system architecture comprises a core network K, which includes a command post 300, a communication base station 90, and one or more edge gateways 10. Each edge gateway 10 represents an addressable network node of the core network K, enabling the conversion of services and information from neighboring peripheral networks into services of the core network K. The edge gateways 10 implement all necessary functions to perform a complete conversion of the data and information received from the peripheral networks.The Edge Gateways can translate 10 formats and addresses from and to a core network protocol of the core network K, convert encodings, buffer data packets and send and receive them with time delays according to priority specifications, acknowledge received data packets, process acknowledgments of the receipt of sent data packets and control the data flow with regard to data rates, transmission speeds and / or receiving permissions.

[0040] The edge gateways 10 communicate with the communication base station 90, the central network element of the core network K. The communication base station 90 is assigned to the command post 300 and connected to it via a wired data network connection E, such as a wired Ethernet connection. Using the communication base station 90 and one of the respective edge gateways 10, the command post 300, acting as the master, can control and manage one of many peripheral elements (represented as network nodes 500 in peripheral networks). In advantageous configurations, no direct functional communication takes place between the peripheral elements. In some configurations, specific communication links can be established for a particular purpose, such as for dual tracking of target tracking radars.However, communication between the peripheral elements can take place via one of the Edge Gateways 10, the Communication Base Station 90 and the Command Post 300, which transmits the respective messages to another peripheral element.

[0041] The in Fig. 1 and Fig. The network environments shown in Figure 2 can serve to establish core cells of a communication system, each comprising a communication base station 90, one or more edge gateways 10 which are in bidirectional radio communication with the communication base station 90, and one or more peripheral adapters 80 which can be connected to one or more edge gateways 10 via wired data network connections E. The communication base station 90 is connected via a wired data network connection E to a command post 300 of the tactical air defense system 200, for example, a command post or an operational command post, for instance, for operational command and / or operational planning.

[0042] The Edge Gateways 10 provide the radio infrastructure for exchanging data between the Communication Base Station 90 and the Peripheral Adapters 80 according to a common communication protocol (Plug and Fight Protocol). The Peripheral Adapters 80 are each connected to one or more Edge Gateways 10 via wired data network connections E and can integrate a Peripheral Element 500 as a network node into the communication system of the Tactical Air Defense System 200.

[0043] It is possible that the peripheral adapters 80 are permanently integrated into a peripheral element 500 or are provided as mobile devices, i.e. as support units, which are in communicative data connection with an associated peripheral element 500.

[0044] To maintain communication control, the wired data network connections between the peripheral adapters 80 and the edge gateways 10, and between the communication base station 90 and the command post 300, are designed to be secure against eavesdropping. It may be possible that no encryption is used between the peripheral adapters 80 and the edge gateways 10, but that special cable shielding is provided or fiber optic cables are used for the wired data network connections.

[0045] Within such a secure core cell, technical elements of a communication system for an avalanche risk management system (AVMS) can be integrated, allowing the operator to maintain control, monitoring, and operational authority. At the periphery of the core cell, elements such as sensors (surveillance radars, target tracking radar systems, electro-optical sensors, etc.), effector systems (missile launchers, anti-aircraft guns, laser cannons for close-range and near-field defense, and high-frequency weapons), and support units (reconnaissance systems, reloading vehicles, logistics vehicles, etc.) can be arranged and interconnected via the communication system.

[0046] The peripheral components can then come from different manufacturers, each using proprietary, external interfaces. However, the peripheral components can still communicate with each other and with a command post located within the core cell via the core cell.

[0047] As in Fig. As indicated in section 2, the communication base station 90 can also maintain external radio links, such as a command post radio network Y2 between several command posts 300 of the tactical air defense system 200 in different core cells K or K2. Furthermore, the communication base station 90 can communicate via radio links Y1 with hierarchically superior systems Z, such as a command level.

[0048] The Air Defense System 200 primarily uses the widest possible bandwidth and long-range radio links for data exchange between the Command Post 300 and the Peripheral Elements 500. A potential disadvantage is that, in contrast to wired communication (e.g., via fiber optic cables), there can be higher susceptibility to interference, limited frequency spectrum availability, and path losses (free-space path loss, atmospheric path loss, polarization path loss, alignment path loss, obstacle path loss).

[0049] This can be at least partially compensated for by prioritizing messages between command post 300 and peripheral elements 500. Priority information is routed through code-transparent middleware in the core structure of the communication system and represented in the IP header of a transmitted message. Therefore, the middleware used does not require or utilize its own quality of service (QoS) parameters. Network interfaces can be provided in the communication base station 90 and / or in the edge gateways 10 to implement the appropriate middleware.

[0050] Fig. Figure 3 shows an exemplary illustration of the network interface architecture for a communication base station or an edge gateway, such as the communication base station 90 or one of the edge gateways 10 of the Fig. 2, for use in a network environment; 100 in a tactical air defense system; 200, as in Fig. 1 and Fig. Figure 2 is shown as an example. It should be clear that the communication base station or edge gateway can also be used in other network environments and that the respective network interface architecture of the Fig. 3. They can be adapted to the specific requirements of these network environments. For example, appropriate communication protocols can be implemented in the network interface architecture to enable the network node to communicate with other network nodes or exchange data in the respective network environments.

[0051] The exemplary network interface architecture comprises a communication controller 400, which processes the data to be transmitted from the communication base station 90 or the edge gateway 10 in packet-based form and processes received data packets to evaluate the information they contain. The IP data packets are exchanged with a network interface 600, which has a packet processing unit 7 that acts as an interface between the network layer (Layer 3) on the side of the communication controller 400 and the data link layer (Layer 2) on the side of the network interface 600. The data packets to be sent (IP) are converted into data frames (DF), and received data frames (DF) are output as IP data packets to the communication controller 400. In other words, the packet processing unit 7 is designed to convert datagrams at Layer 3 into datagrams at Layer 2 and vice versa.The data frames DF at the data link layer, for example MAC frames, are passed by the packet processing unit 7 to a media access controller 9 (MAC), which processes the data frames DF according to priority and passes the data to be sent to a physical data transmission device 8 of the network node 10 or 90, so that the data can be transmitted over a shared medium, for example a radio channel. The shared medium is subject to access competition, so the network interface 600 can implement collision monitoring measures and return corresponding collision monitoring results to the media access controller 9, for example in the form of signals confirming the complete or incomplete transmission of data over the radio channel (acknowledgment signals, so-called ACK signals).

[0052] The Fig. 4 and Fig. Figure 5 represents exemplary implementations of media access control devices 9 within a network interface, for example, the network interface 600 of the Fig. 2. The media access control units 9 of the Fig. 4 and Fig. 5 can each be implemented in network node 500 of a network environment of a tactical air defense system, for example in network environment 100 in a tactical air defense system 200, as in Fig. 1 and Fig. Figure 2 is shown as an example. Different implementations of the media access control devices 9 can be chosen for different network nodes 500, in particular with regard to the type, number and arbitration of data frame queues that can be formed in the media access control devices 9, as well as with regard to the respective assigned access competition parameters.

[0053] For example, different media access control units 9 can be designed according to various criteria or requirement profiles of the respective network node 500 in which they are to be deployed. Exemplary criteria include: assignment of the message types to be sent to differentiated service code points; assignment of the differentiated service code points to message priority levels; queue layout; assignment of priority levels to the queue types to be used; definition of the competition parameters for channel access; and assignment of the queue types to be used to the competition parameters for channel access. Each media access control unit 9 can be individually configured in this respect, depending on whether the media access control unit is located, for example, in the command post, in a radar, or in a launch device of the respective tactical air defense system.

[0054] The media control unit 9 of the Fig. 4 and Fig. In transmission order, component 5 first comprises a classifier 1, which receives data frames DF containing frame priority information in their headers from the packet processing unit 7 of a network interface 600. The data frames DF can be, for example, MAC frames, which the media control unit 9 processes at the data link layer, i.e., at layer 2 of the OSI model. The frame priority information can be encoded, for example, in IEEE 802.1Q-standardized VLAN octets of the MAC header of the data frames DF and is based on differentiated service code points (DSCPs) of the IP data packets IP contained as payload in the MAC frames. This conversion of the DSCPs into priority levels, which are encoded in the VLAN octets, can be performed, for example, by the packet processing unit 7.

[0055] In tactical communication systems of a live-fire (LV) system, time-critical tactical data should be transmitted with priority over other application data. For example, target tracks are categorized into different priority levels: messages via critical target tracks with the highest priority, which are allocated a fixed bandwidth of the waveform used and are transmitted with the highest accuracy and therefore a high data volume; messages via preferred target tracks with medium priority, whose bandwidth is allocated according to requirements and which are transmitted with medium accuracy and therefore a medium data volume; and messages via ordinary target tracks with low priority, whose bandwidth is allocated according to available capacity and which are transmitted only with coarse accuracy and therefore a low data volume.

[0056] Based on its threat assessment (target type, target behavior, protected object), the command post of the LV system can set and modify the message type of a target track. This ensures that critical target tracks always reach the recipient and that ordinary target tracks do not clog the channel. Packet processing unit 7 then uses the classification of the set message types as an encoding guideline for the priority levels encoded in the VLAN octets.

[0057] Downstream of the classifier 1, i.e., in the transmission stream, at least two frame queues 2 are provided in the media control unit 9. These queues are designed to temporarily store data frames DF, which are sorted into one of the at least two frame queues 2 by the classifier 1 based on the frame priority information. A timing control unit 3 ("scheduler") is connected downstream of the at least two frame queues 2. This scheduler extracts temporarily stored data frames DF from a sequence of frame queues 2, as defined by a predetermined arbitration logic. The extracted data frames DF are then output as a sequential output frame stream to a collision detection unit 4, according to their extraction order.The arbitration logic can be specified, for example, by a network configuration device 5, which can also configure the operation of the collision detection device 4. In some variants, different configuration devices can be provided for the timing control device 3 and the collision detection device 4, or the respective configuration can be permanently programmed into the circuits of the timing control device 3 and / or the collision detection device 4.

[0058] The timing control unit 3 knows the prioritization of the respective frame queues 2, so that, for example, a frame queue 2 with the highest priority level is always immediately included in the data frame retrieval sequence DF as soon as a data frame DF is pending at the queue output. Frame queues 2 with the lowest priority level can, for example, only be included in the data frame retrieval sequence DF if channel access is possible and simultaneously no other frame queue 2 has a data frame DF pending at its output.

[0059] The at least two frame queues 2 can be based on various queuing principles depending on the application, such as first-in, first-out (FIFO), priority queuing (PQ), fair queuing (FQ), weighted fair queuing (WFQ), round-robin arbitration, earliest deadline first (EDF), or rate monotonic scheduling (RMS). Each of these queuing principles creates a schedule according to which the retrieval order of data frames cached or buffered in the queue is planned. This allocates the limited resource of channel access time to the respective data frames according to the queue.The various queuing principles are based on the balancing of different resource utilization criteria such as data throughput, processing efficiency, resource allocation fairness, or adherence to deadlines.

[0060] The collision detection device 4 feeds the sequential output frame stream generated by the timing control device 3 according to the arbitration logic into a physical data transmission channel D, for example via the physical data transmission device 8 of the network interface 600. This physical data transmission device 8 can also provide feedback to the collision detection device 4 regarding the success or failure of sending individual data frames DF, enabling the collision detection device 4, for example, to initiate appropriate measures for controlling access competition on the transmission channel. For this purpose, the collision detection device 4 can, for example, feed the individual data frames DF of the sequential output frame stream into the physical data transmission channel according to predetermined access competition parameters.These access competition parameters can be created on the basis of access competition indicators, which are output by the timing control unit 3 to the collision detection unit 4 for the data frame DF that was last taken from one of the frame queues 2.

[0061] Different access competition indicators can be specified for different frame queues, such as the Arbitrated Interframe Space (AIFS) to be used, which is the minimum waiting time after a channel access to the transmission medium after which a new access should / may occur. Other access competition indicators can include a Transmission Opportunity (TXOP), which is the start and duration of a transmission interval that secures a transmission right, the length of a contention window (CW), or a maximum number of permissible channel access iterations after a failed channel access.

[0062] Depending on the access competition parameters and feedback from the physical data transmission device 8, the collision detection device 4 can be individually configured, depending on whether the media access control unit 9 is located, for example, in the communication base station 90, in the edge gateway 10 of a radar, or in the edge gateway 10 of a launch device of the respective tactical avalanche transceiver 200. Furthermore, the collision detection device 4 can output acknowledgment signals to the timing control unit 3 regarding the collision-free (or collision-prone) transmission of a data frame DF. The timing control unit 3 can, for example, only retrieve a new data frame DF from one of the frame queues 2 once a corresponding acknowledgment signal has been received for the preceding data frame DF.

[0063] In Fig. Figure 5 illustrates frame queues 2a, 2b, and 2c with different queuing principles. Frame queue 2a, for example, can be a pure FIFO queue, in which data frames DF are processed in chronological order, from oldest to newest. Frame queue 2c, for example, can be an Earliest Deadline First (EDF) queue, in which a termination device 6 reads the address indicators for the expiration of data frames DF and incorporates them into the arbitration logic as logic parameters. The termination device 6 can also be configured, for example, to remove data frames from frame queue 2c that have already expired.

[0064] The frame queues 2b are WFQ queues in which each of the frame queues 2b has a prioritization weight, and in which a joint access of the timing control device 3 adheres to a fixed retrieval sequence as soon as the group of frame queues 2b is in line in the hierarchically superior retrieval sequence.

[0065] It should be clear that the ones in the Fig. 4 and Fig. The arrangements of frame queues 2a, 2b, 2c shown in Figure 5 are only exemplary, and other groupings of frame queues 2 can be chosen in the same way with regard to number, type and arbitration parameters.

[0066] The media access control unit 9 is located at the data link layer (Layer 2, L2) and processes data frames DF, such as MAC frames, which are fed in from the network layer (Layer 3, L3). After processing the data frames DF by the media access control unit 9, they are passed to the physical transmission layer (Layer 1, L1), where the actual channel access takes place.

[0067] For transport prioritization, a packet selection can first be made deterministically in the media access control unit 9 according to the queuing principle. Subsequently, the edge gateway 10 or the communication base station 90 that is allowed to access the transport medium is selected competitively via a stochastic, decentralized access method. Media access control units 9 can be implemented as radio devices in an edge gateway 10 or the communication base station 90.

[0068] Fig. Figure 6 shows a schematic block diagram of an edge gateway 10. The edge gateway 10 initially comprises a container 16. The container 16 allows for the installation or attachment of components of the edge gateway 10 inside or on the outside. The container 16 can, for example, be a cuboid hollow structure made of steel or another suitable material. The interior of the container 16 can provide sufficient space for the various communication components, including a radio, as well as a workstation for managing the networks and domains and a workstation for operating the various components of the edge gateway 10.

[0069] Container 16 can be equipped with suitable locking mechanisms, for example, those that comply with DIN standard 18251 for externally mounted storage devices. Furthermore, Container 16 can accommodate several cable drums 13 in a special storage device, on which Ethernet cables for direct connection to the peripheral adapters 80 can be wound. Container 16 can also house personal equipment for operators and service personnel, grounding devices, and lightning protection devices in an external compartment. The interior of Container 16 can accommodate suitable fire protection equipment such as smoke detectors or fire extinguishers. Additionally, the interior of Container 16 can be protected against dew or condensation by desiccants.

[0070] The Edge Gateway 10 generally comprises a communication subsystem 50 arranged in the container 16, an interface device 70 arranged in the container 16, an antenna assembly 40 mounted externally or internally on the container 16, and a power supply unit 20. Furthermore, the Edge Gateway 10 may include an air conditioning unit 30 with a control panel 31 mounted externally on the container 16, designed to cool the container 16. In addition, the MOWABS 10 may have a navigation device 14 arranged externally on or inside the container 16.

[0071] The container 16 can be mounted on a motor vehicle or a motor vehicle trailer via an adapter device 17 mounted on the underside of the container 16.

[0072] The communication subsystem 50 can include a communication and routing computer 51, an IT security controller 52 with a time synchronization unit, and an administrator console. An unhardened version of the communication subsystem 50 can be selected, as it resides within container 16. The communication subsystem 50 provides a transparent, IP-based network in which domains of varying security levels are integrated. The communication and routing computer 51 can include application software for NAT routing, VoIP telecommunications, network management, status monitoring, and remote maintenance access. Furthermore, a switch with electrical and optical connections can be provided, enabling the connection of all domain components. The communication subsystem 50 can also include a key device, an analog telephone adapter, and a power distribution unit.

[0073] The Communication Subsystem 50 includes a radio capable of establishing point-to-point and point-to-multipoint connections, supporting OFDM for high-speed wireless data transmission, supporting military-relevant frequency bands, exhibiting low latency for bandwidth-intensive real-time applications, incorporating advanced interference suppression with automatic transmit power control and adaptive modulation, being operable with radio antennas (sector, directional, or rod antennas), featuring an antenna alignment unit, and boasting a lightweight and compact design for direct mast mounting. The radio implements the functions of a Media Access Control Unit 9 according to the Fig. 3, Fig. 4 to Fig. 5 o'clock.

[0074] The radio device of the communication subsystem 50 can, for example, be mounted on an antenna mast of the antenna assembly 40 together with a radio antenna 43 included in the antenna assembly 40. The radio antenna (sector or directional antenna) can be electrically aligned in azimuth and elevation by means of the antenna assembly control panel 41 of the antenna assembly 40. The antenna assembly 40 is communicatively connected to the communication subsystem 50 via a discrete data bus line.

[0075] The antenna assembly 40 can include an antenna radio unit 42, at least one radio antenna 43, and an antenna assembly control panel 41. Multiple sector antennas or directional radio antennas are preferably used when several command posts need to be supplied with image / video data in real time, for example, via a long-range radio network. Radio antennas 43 can be mounted together with the radio unit of the communication subsystem 50 on a tubular mast at least 10 meters high with an associated erection unit. The erection unit can raise or tilt the antenna mast into the operating position (perpendicular to the container) or into the transport position (horizontal to the container). In the operating position, the antenna mast can be leveled accordingly. A telescopic function of the antenna mast allows for continuous adjustment of the mast height.A mobile control panel inside container 16 can be used to operate the antenna mast, which can also display operating information for the antenna system 40. The antenna mast can be electrically powered, eliminating the need for hydraulics or pneumatics. The antenna radio 42 and the radio antenna 43 can be mounted at the top of the antenna mast system attached to the outside of container 16.

[0076] The power supply unit 20 has a power source 23 and is designed to supply the communication subsystem 50 and the antenna unit 40 with electrical energy. For this purpose, the power supply unit 20 can have a low-vibration fuel cell with an attached battery as a power source 23 to ensure an uninterruptible power supply (UPS), which feeds the electrical energy into a power grid P of the edge gateway 10. The other components of the edge gateway 10 can then be supplied with energy from this power grid.

[0077] The power supply unit 20 also includes a power supply management component 22 and a power supply unit control panel 21. The power supply management component 22 enables manual and automatic control of the power supply, the air conditioning via the air conditioning unit 30, the interface unit 70, the antenna mast, the communication subsystem 50, and the lighting of the container 16. Thus, the power supply management component 22 serves as a container control unit. The power supply management component 22 maintains an Ethernet connection to the communication and routing computer 51 of the communication subsystem 50 and to the interface unit 70 to enable remote maintenance, remote configuration, and data transfer. Data communication can preferably be packet-based, for example, using time-division multiplexing (TDMA) or code-division multiplexing (CDMA).The energy supply management component 22 can ensure that the interior of container 16 is sufficiently air-conditioned by the air conditioning system 30 before the installed electrical components are activated to provide operational environmental conditions.

[0078] Power supply via energy source 23 can preferably be provided by a low-vibration fuel cell, a distribution unit, and a battery. These components are connected to container 16 via a damping system to prevent the transmission of vibrations to container 16 and thus to the multispectral sensors. The fuel cell can be operated with methanol, is inaudible from a distance of approximately seven meters, produces barely detectable emissions, and requires minimal maintenance. Energy source 23 enables autonomous operation for at least 32 hours without operator intervention and can be supplied with external voltages as an alternative to its own power supply. Switching between the fuel cell's own voltage and an external power supply, and vice versa, is seamless.An automatic switchover occurs in the event of a voltage loss from the current source, or a manual switchover can be performed using the power supply unit's control panel 21. Furthermore, the power source 23 can supply auxiliary voltage externally via an auxiliary voltage connection 11 and has an emergency stop switch that can deactivate the power source 23 in an emergency when the switch is pressed. The emergency stop switch could, for example, be a red button.

[0079] The air conditioning unit 30, with its control panel 31, maintains the temperature and humidity inside the container within the permissible range for the operation of the electrical components. The air conditioning unit 30 also supplies fresh air to the interior of container 16 via a dust / NBC filter. The air conditioning unit 30 transfers heat from the interior of container 16 to the outside and is connected to container 16 by a damping system.

[0080] The interface unit 70 can have a local display 71 for an operator. In addition to enabling switching between local and remote operation of the components of the edge gateway 10, the interface unit 70 allows for the orderly deactivation of all components. Various operating parameters with timestamps, such as operating hours, sensor status, error codes, error images, malfunction log files, test results, videos, snapshots, configuration data, predictive data, and different versions of the operating software, can be stored in a removable memory (e.g., a flash SSD) of the interface unit 70, which can be read via USB or SATA.

[0081] The interface device 70 can also include a power distribution unit that can distribute the available power to the elements of the edge gateway 10. Furthermore, the interface device 70 can serve as a central data distribution point and can communicate with other components via a wired data network connection E. This wired data network connection E can, for example, be an Ethernet connection mediated between the respective nodes via a central data bus D within the edge gateway 10.

[0082] The interface device 70 can also have an interface 91 with multiple pins or connectors, via which one or more peripheral adapters 80 can be connected to the edge gateway 10. Local communication with the one or more peripheral adapters 80 can take place in a so-called "plug and fight" connection, i.e., unencrypted and in a standard format for each of the peripheral adapters 80 connected to the interface 91.

[0083] The interface unit 70 can store data, including data source and timestamp, for each connected peripheral adapter 80 over a period of 200 operating hours in an encrypted standard format and transfer the complete content to the communication base station 90 upon request. This data can include, for example, the status of the peripheral adapter 80, error images, error codes, test results (PBIT, CBIT, IBIT), fault localization data, estimates of remaining service life and maintenance / repair requirements (prognostic data), videos and snapshots, as well as configuration data.

[0084] The navigation device 14 can, for example, include an inertial measurement unit (IMU) that may comprise linear, inertial, sensor-fixed accelerometers and sensor-fixed angular velocity sensors. The navigation device 14 can also process satellite signals from a global positioning system such as GPS, Galileo, or GLONASS, including for time synchronization purposes. An antenna of the global positioning system can be integrated with the navigation device 14 into a top-loading frame, ensuring good visibility of the navigation satellites.

[0085] Fig. Figure 7 shows a schematic block diagram of a communication base station 90, which is used in a network environment of a tactical air defense system, such as the network environment 100 of the system described in relation to the Fig. 1 and Fig. 2 exemplary illustrated tactical air defense systems 200.

[0086] The main functions of the Communication Base Station 90 include, firstly, providing a functionally and topologically central base station for a communication system within a core or core cell K of a tactical air defense system 200, with a waveform that controls communication between a command post 300 and the associated network components in the periphery. Secondly, the Communication Base Station 90 serves to establish a command post radio network for communication with other command posts in other core cells K2 using a stochastic waveform. Furthermore, the Communication Base Station 90 is designed to ensure communication with higher command levels or other air defense systems via conventional tactical data links.

[0087] The interface device 70 of the communication base station 90 can be connected to a command post G or 300 via a command post interface 92.

[0088] Basically, the communication base station 90 of the Fig. 7 similar components or functional elements like the Edge Gateways 10 of the Fig. 6, which can be housed in or on a container 16. The base frame of the communication base station 90 can be mounted on an ISO container support frame of a ladder frame of a carrier truck. This container support frame can have ISO 20-foot twistlock latches, so that the container 16 is secured using 20-foot ISO corner fittings. The base frame can then accommodate the antenna mast of the antenna device 40 with attached communication components, a leveling system, and the IT components of the communication subsystem 50. Thus, the base frame with the antenna mast of the antenna device 40 can be transported like a standard container by both military trucks and civilian transport units such as trucks or railcars. The hydraulic leveling system of the communication base station 90 can be extended or retracted.The leveling system is installed on retractable supports attached to the base frame and can perform two functions: stabilizing and leveling the antenna mast using extended hydraulic supports, and lifting the antenna mast of the antenna system 40, including its base frame, from the carrier truck after releasing the twistlock fasteners. During transport, all components of the leveling system do not exceed the ISO 20-foot external dimensions. The necessary hydraulic power for this can be supplied by the carrier truck.

[0089] Using a control panel, the operator can control the extension and retraction of the hydraulic supports and, based on a level sensor and the angles measured at the antenna mast of the antenna device 40, adjust the vertical alignment (pitch, roll angle) of the antenna mast 43. Due to its height, the antenna mast of the antenna device 40 can be a hydraulically operated, telescopic lattice mast mounted on the base frame via a tilting system. This tilting system allows the antenna mast of the antenna device 40 to be moved from transport mode (horizontal position) to operating mode (vertical position) using hydraulic power.

[0090] The mast height can vary between 10 and 30 meters (measured from the ground to the highest mounted antenna), depending on the extension position, and the total weight is approximately 12 tons. Thanks to the leveling system, the antenna mast of the antenna system 40 can be detached from the carrier truck for extended shutdown periods.

[0091] Sensors can be mounted on the antenna mast to measure wind speed and tilt angle data, which are then displayed to the operator on the control panel. A floodlight system can also be attached to the antenna mast and is likewise controllable via the control panel.

[0092] The communication base station 90 can have at least two different radio communication systems: one as a base station for the communication system of the network environment 100 of the tactical air defense system 200 as a transparent, IP-based network with deterministic or decentralized, stochastic channel access (e.g., via IEEE 802.16e), and another as a network node as a participant in a (fully) meshed command post radio network as an ad-hoc network in which different command posts can communicate with each other. In the latter radio network, data transmission can be accomplished through concurrent, stochastic channel access (e.g., IEEE 802.11n), so that no dedicated base station is required.

[0093] Optionally, additional radio communication systems can be provided in the communication base station 90, which provide communication with higher command centers via tactical data links such as Link11 / 16 / 22 or ADatP-3.

[0094] The antenna unit 40 can – similar to the Edge Gateway 10 – Fig. 6 - comprising an antenna radio device 42, at least one radio antenna 43, and an antenna control panel 41. Several sector antennas or directional antennas, for example at least four, are preferably used when several command posts need to be supplied with image / video data in real time, for example via a long-range radio network, in order to increase the communication range. Each of the antennas can be rotated about the roll and pitch axis by an antenna directional unit to ensure optimal alignment with the respective communication partner. For the (fully) meshed command post radio network with network topology, rod antennas can preferably be mounted as omnidirectional radiators; however, sector antennas can also be used. For the tactical data links such as Link11 / 16 / 22 or ADatP-3, directional antennas can preferably be used.

[0095] The communication subsystem 50 can – similar to the Edge Gateway 10 – Fig. 6 - comprise a communication and routing computer 51, an IT security controller 52 with a time synchronization unit, and an administrator console. An unhardened version of the communication subsystem 50 can be selected, as it resides within container 16. The communication subsystem 50 provides a transparent, IP-based network in which domains of varying security levels are integrated. The communication and routing computer 51 can include application software for NAT routing, VoIP telecommunications, network management, status monitoring, and remote maintenance access. Furthermore, a switch with electrical and optical connections can be provided, enabling the connection of all domain components.In addition, the communication subsystem 50 can include a key device operating at the Ethernet level, a border protection gateway, an analog telephone adapter, and a voltage and power distribution unit.

[0096] The power supply unit 20 exhibits – similar to the Edge Gateway 10 – the Fig. 6 - a power source 23 and is designed to supply the communication subsystem 50 and the antenna system 40 with electrical energy. For this purpose, the power supply system 20 can have a low-vibration fuel cell with an attached battery as a power source 23 to ensure an uninterruptible power supply (UPS), which feeds the electrical energy into a power grid P of the edge gateway 10. The respective other components of the edge gateway 10 can be supplied with energy from the power grid.

[0097] The power supply unit 20 also includes a power supply management component 22 and a power supply unit control panel 21. The power supply management component 22 enables manual and automatic control of the power supply, the air conditioning via the air conditioning unit 30, the interface unit 70, the antenna mast, the communication subsystem 50, and the lighting of the container 16. Thus, the power supply management component 22 serves as a container control unit. The power supply management component 22 maintains an Ethernet connection to the communication and routing computer 51 of the communication subsystem 50 and to the interface unit 70 to enable remote maintenance, remote configuration, and data transfer. Data communication can preferably be packet-based, for example, using time-division multiplexing (TDMA) or code-division multiplexing (CDMA).The energy supply management component 22 can ensure that the interior of container 16 is sufficiently air-conditioned by the air conditioning system 30 before the installed electrical components are activated to provide operational environmental conditions.

[0098] Power supply via energy source 23 can preferably be provided by a low-vibration fuel cell, a distribution unit, and a battery. These components are connected to container 16 via a damping system to prevent the transmission of vibrations to container 16 and thus to the multispectral sensors. The fuel cell can be operated with methanol, is inaudible from a distance of approximately seven meters, produces barely detectable emissions, and requires minimal maintenance. Energy source 23 enables autonomous operation for at least 32 hours without operator intervention and can be supplied with external voltages as an alternative to its own power supply. Switching between the fuel cell's own voltage and an external power supply, and vice versa, is seamless.This involves an automatic switchover in the event of a voltage loss from the current source, or a manual switchover using the power supply unit control panel 21.

[0099] The communication base station 90 can optionally also include a sensor system 60, which can be mounted externally on the container 16. A sensor lifting device 66 is part of the sensor system 60 and carries a multispectral sensor device 63, which includes one or more infrared sensors, a VIS sensor, and a laser rangefinder, and which has a damping device that structurally absorbs the transmission of vibrations to the sensor. The sensor lifting device 66 is communicatively connected to the communication subsystem 50 via a wired data bus connection E. As in Fig. As shown in Figure 7, the sensor system 60 can be completely integrated into the container 16 of the communication base station 90.

[0100] In other variants (not explicitly shown), sensor systems 60 can additionally or alternatively be used as remote tripod devices outside the container 16. In this case, a cable connection of up to 100 meters can be established between the interface device 70 in the container 16 and the sensor system 60 to enable the sensors to operate with minimal fluctuation and vibration, for example, in strong winds or gusts, or to achieve more favorable camouflage of the sensor system 60 in the terrain. In the case of an externally mounted sensor system 60, a tripod is used instead of the sensor lifting device 66, which supports the sensor device 63.

[0101] The sensor lifting device 66 is a spindle mast system and is mounted on the rear of the container 16 on the outer wall next to the door. An operating panel 67 for this system is located inside the container 16. A built-in crank allows for manual emergency operation. The height is approximately 1.7 meters when retracted and a maximum of 8 meters when extended. The maximum top load of the sensor lifting device 66 is approximately 250 kg. A power and data distribution module 61, a connected sensor control unit 62, the sensor assembly 63, and a navigation antenna 64 are mounted as the top load in a frame of the sensor lifting device 66. This allows for flexible positioning of all sensor components beyond the container roof, thus providing cover and camouflage options for the container.

[0102] The Sensor System 60 comprises a multispectral target detection and tracking sensor designed as an open platform, a VIS camera (which can be color or black and white), at least one infrared camera, and an eye-safe laser rangefinder. The target detection and tracking sensor allows for remote control from the command post and installation on a tripod.

[0103] A stabilized pan-and-tilt unit 65, intended for mechanical 2-axis stabilization in the sensor unit 63, has, for example, a line-of-sight range of azimuth x 360° and elevation from -120° to 90°. The pan-and-tilt unit 65 is an open platform for supporting payloads and is easy to assemble and disassemble. The pan-and-tilt unit 65 can consist of two components: a 2-axis gimbal block with electromechanical azimuth / elevation drives, sensors, and brakes, and an electronic module with power supply, axis control, and communication interfaces.

[0104] The infrared cameras can operate in various infrared ranges, approximately 0.78 to 1.4 µm (NIR), 1.4 to 3 µm (SWIR), 3 to 8 µm (MWIR), or 8 to 15 µm (LWIR), and are specifically designed for long-range applications in day / night operation, even under adverse weather conditions. An infrared camera can be ruggedized for this purpose. The VIS camera can be specifically designed for long-range applications in daylight and / or twilight, with a spectral sensitivity of 400 to 760 nm. The VIS camera can utilize a CCD image processing chip and have a focal length of 50 to 1550 mm. The laser rangefinder is aligned with the line of sight of the VIS camera and can operate at a wavelength of, for example, 1.535 µm, such as an erbium fiber laser.

[0105] The sensor control unit 62 serves as the higher-level control system for at least one infrared camera, the VIS camera, and the laser rangefinder, and may include a video or infrared tracking function. Electronic image stabilization, operator-controlled image fusion of the infrared and VIS sensors, and, if necessary, further image manipulations can be performed within the sensor control unit 62. The power and data distribution module 61 can provide a data interface (e.g., Ethernet) to the interface device 70, enabling communication with it via a wired data network connection E. The power and data distribution module 61 also ensures the distribution of power from the power supply unit 20 to the sensors in the sensor system 60.

[0106] Fig. Figure 8 shows a schematic block diagram of a peripheral adapter 80 for connecting a peripheral element 500 to a network environment of a tactical air defense system. The peripheral adapter 80 can be used, for example, in the Fig. 1 and Fig. The network environment 100 of the tactical air defense system 200 is used as an example. The number of peripheral adapters 80 used can be variably adapted to the peripheral element 500 to be integrated.

[0107] The main functions of a peripheral adapter 80 of the Fig. 8 encompasses data and protocol conversion between a peripheral element 500 and the central communication protocol of the core structure K. For this purpose, the peripheral adapter 80 can include a terminal for data exchange, such as video or voice data, with the command post 300 or peripheral elements 500. The terminal can be used with a local laptop as an input / output device.

[0108] The peripheral adapter 80 functionally comprises two halves – the peripheral interface 47 and the core interface 53. The core interface 53 can be considered part of the core structure K of the LVS communication system. This allows the operator of the communication system to configure the core interface 53 at their own discretion.

[0109] The peripheral interface 47, on the other hand, can be considered part of the peripheral system. Both functional halves communicate with each other via an instantiated P&F data memory 54 (P&F = "Plug & Fight"). The manufacturers of the peripheral elements 500, to which the peripheral adapters 80 are connected, such as radars or effectors, are responsible for configuring the peripheral interface 47. For this purpose, the peripheral adapter 80 can have a development environment that is as open as possible, especially for software, enabling a manufacturer to program the functions of the peripheral interface 47 (peripheral element driver 44, peripheral element data memory 46, and data protocol converter 45) according to the requirements of the chosen instantiation of the connected peripheral element 500.This development environment can be designed in such a way that each manufacturer of a peripheral element 500 to be connected can fully develop the functions of the peripheral interface 47, i.e., integrate algorithms and processes, so that the instantiated P&F data store 54 of the core interface 53 can be correctly written to and read from. In the core interface 53, the development environment can be used in particular for instantiating the P&F data store 54, a P&F driver 55, and a P&F interaction rule set 49.

[0110] The functions programmed by the manufacturer of the connected peripheral element 500 therefore represent a connection between the raw data of the connected peripheral element 500, which is usually in a proprietary format, and the specified, standardized and instantiated format of the core interface 53 (data, drivers, rules).

[0111] The peripheral element driver 44 is responsible for obtaining the data required by the P&F driver 55 (e.g., status, report, error messages, sensor tracks, ammunition supply, etc.) instantiated in the core interface 53 from the peripheral element 500 and writing it to the peripheral element data memory 46. Furthermore, the peripheral element driver 44 is configured to feed data received from the core interface 53 via the peripheral element data memory 46 and translated by the data protocol converter 45 into the application domain of the peripheral element 500 into the peripheral element 500.

[0112] The peripheral element data store 46 stores data requested by the instantiated P&F driver 55 of the core interface 53. This data is in the form and with the information content as received by the peripheral element driver 44 from the peripheral element 500. It may be incomplete with respect to the information content required by the instantiated P&F driver 55. The peripheral element data store 46 also stores information that has been converted by the data protocol converter 45 into the format required by the peripheral element 500 and, if necessary, completed or reinterpreted. Data contents of the peripheral element data store 46 can be stored and backed up (data logging) on ​​a removable, persistent storage medium along with information about timestamps, source, and / or context.

[0113] The data protocol converter 45 is responsible for reading data from and writing data to the peripheral element data store 46, and, if necessary, completing the data so that its format and content meet the requirements of the instantiated P&F driver 55. This is done according to the rules of the instantiated P&F interaction rule set 49, from which the data protocol converter 45 can also read data and translate it into the application domain of the peripheral element 500. In this respect, the data protocol converter 45 represents a translation layer between the application domains of peripheral elements 500 and the core structure K of the LVS. The data protocol converter 45 can also, under certain circumstances, handle the translation between IPv4 and IPv6.

[0114] The core interface 53 is responsible for parsing messages from the edge gateways 10 and writing the resulting data content to the instantiated P&F data store 54. Furthermore, the core interface 53 reads data from the instantiated P&F data store 54, assembles the data into corresponding P&F messages, prioritizes them, and, if necessary, groups them into packets with the same priority.

[0115] Using the development environment associated with the peripheral adapter 80, the P&F data storage 54, P&F driver 55, a P&F state machine, and the P&F interaction rule set 49 are instantiated, depending on the type of connected peripheral element 500. These instantiations together form a P&F interface pattern, which can be preconfigured in the development environment for various system component types: radar sensor, electro-optical sensor (EOS), other sensor, missile effector, cannon effector, laser effector, multi-effector, reloading element, reconnaissance element, logistics element, other support element, operational command post, command post, and higher-level command post. This provides generic P&F interface patterns with which the command post 300 can communicate with the peripheral elements 500 after appropriate instantiation.The P&F interface patterns differ in the type and scope of data exchanged between the respective instance and the command post of the core structure K, as defined by the information and communication needs of the operational command post. Another distinguishing feature is the interaction mechanism (state automation, interaction rules) predefined between the respective instance and the command post.

[0116] A P&F state machine instantiated in the core interface can be instantiated according to the peripheral element type and enables the command post 300 to efficiently control the peripheral element 500. The command post 300 can typically control the following states of the peripheral element 500: Inactive, Local Ready, Local Test, Safety Delay, Remote Ready, Remote Test, Combat, Automatic Emergency Disable, and Training. Sub-states can be defined for some states, such as Ready and Combat. Furthermore, for each state, it is defined which P&F messages can be exchanged between the command post 300 and the peripheral element 500.

[0117] The instantiated P&F interaction rule set 49 can be instantiated according to the system component type and then provides the peripheral element driver 44, the data protocol converter 45 and the P&F driver 55 with procedural specifications regarding when to request, read and write which data, which communication patterns or access patterns should be used, which data should be completed, and which data should be converted in which form or structure.

[0118] The peripheral adapter 80 can also have a local display 81, via which the respective settings of the components of the peripheral adapter 80 can be made locally.

[0119] Fig. Figure 9 shows a method M for communication between system components of a tactical air defense system. Method M can be used, for example, in a tactical air defense system 200 of the Fig. 1 and Fig. 2 are used, which Edge Gateways 10 according to Fig. 6, Communication base stations 90 according to Fig. 7 and one or more peripheral adapters 80 according to Fig. 8.

[0120] The procedure M begins with step M1 of connecting a communication base station 90 to a command post 300 of the tactical air defense system 200 via a wired data network connection E. Then, in step M2, a bidirectional radio communication link is established between one or more edge gateways 10 and the communication base station 90. This radio link enables radio-based data exchange according to a common communication protocol, for example, by implementing a centralized, deterministic or a decentralized, stochastic channel access method.

[0121] In a third step M3 of the procedure M, one or more peripheral adapters 80 are connected via wired data network connections E to one or more edge gateways 10, so that in a fourth step M4 bidirectional data communication can be mediated between system components 500 of the tactical air defense system 200 connected to the one or more peripheral adapters 80 and the command post 300 via the one or more edge gateways 10 and the communication base station 90.

[0122] The peripheral adapters 80 can be permanently integrated into one of the system components 500. Alternatively, it is also possible to design one or more peripheral adapters 80 as mobile devices that are in communicative data connection with one system component 500 each and can be dynamically associated with a corresponding system component 500 as needed.

[0123] In the preceding detailed description, various features have been summarized in one or more examples to improve the clarity of the presentation. However, it should be clear that the above description is merely illustrative and in no way limiting. It serves to cover all alternatives, modifications, and equivalents of the various features and embodiments. Many other examples will be immediately and directly clear to the person skilled in the art based on their technical knowledge, given the above description.

[0124] The exemplary embodiments were selected and described to best illustrate the principles underlying the invention and its practical applications. This enables those skilled in the art to optimally modify and utilize the invention and its various exemplary embodiments with regard to the intended purpose. In the claims and the description, the terms "including" and "comprising" are used as neutral language terms for the corresponding terms "comprehensive." Furthermore, the use of the terms "a," "a," and "an" is not intended to fundamentally exclude multiple features and components described in this way.

Claims

[1] Communication system for a tactical air defense system (200), comprising: a communications base station (90) which can be connected to a command post (300) of the tactical air defense system (200) via a wired data network connection (E); one or more edge gateways (10) which are in bidirectional radio communication with the communication base station (90) and which are designed to exchange data with the communication base station (90) according to a common communication protocol; and one or more peripheral adapters (80) which can be connected to one or more edge gateways (10) via wired data network connections (E) and which are designed for the data connection of a peripheral element (500) to the tactical air defense system (200), characterized by, that the one or more peripheral adapters (80) each have a core interface (53) and a peripheral interface (47) designed to exchange data between an edge gateway (10) and a peripheral element (500), to convert regarding a data format and a communication protocol, that the core interface (53) has an instantiated core interface driver (55) which is controlled by an interaction rule set (49) of the peripheral adapter (80) instantiated according to the system component type of the peripheral element (500), and a core interface state machine instantiated according to the system component type of the peripheral element (500), and that operating states of the peripheral element (500) are controllable from the command post (300) of the tactical air defense system (200) via the instantiated core interface state machine of the core interface (53). [2] Communication system according to claim 1, wherein the one or more peripheral adapters (80) are permanently integrated into each peripheral element (500). [3] Communication system according to claim 1, wherein the one or more peripheral adapters (80) are mobile devices which are in communicative data connection with each peripheral element (500). [4] Communication system according to one of claims 1 to 3, wherein the wired data network connections (E) between the one or more peripheral adapters (80) and the one or more edge gateways (10) are protected against eavesdropping by cable shielding or the use of fiber optic cables. [5] Communication system according to one of claims 1 to 4, wherein the communication base station (90) is further configured to maintain a command post radio network between several command posts (300) of the tactical air defense system (200). [6] Communication system according to any one of claims 1 to 5, wherein the peripheral interface comprises a peripheral element driver (44) and a data converter (45) coupled to the peripheral element driver (44). [7] Communication system according to any one of claims 1 to 6, wherein the communication base station (90) implements a centralized, deterministic channel access method or a decentralized, stochastic channel access method for establishing the bidirectional communicative radio link with the one or more edge gateways (10). [8] Communication system according to any one of claims 1 to 7, wherein the communication base station (90) is further designed to perform transport prioritization between the one or more edge gateways (10) and the communication base station (90). [9] Tactical Air Defense System (200) with: at least one command post (300); a communication system according to any one of claims 1 to 8, the communication base station (90) of which is in a wired communication link with the at least one command post (300); and one or more air defense system components (500), each of which is in communicative communication with one or more peripheral adapters (80) and which are designed to, to exchange data with at least one command post (300) via one or more peripheral adapters (80), one or more edge gateways (10) and the communication base station (90). [10] Tactical air defense system (200) according to claim 9, wherein the communication base station (90) of the communication system is further designed to connect the at least one command post (300) to at least one other command post via a secure command post radio network. [11] Method (M) for communication between system components of a tactical air defense system (200), comprising the steps: Coupling (M1) of a communications base station (90) via a wired data network connection (E) to a command post (300) of the tactical air defense system (200); Establishing (M2) a bidirectional communicative radio link between one or more edge gateways (10) and the communication base station (90), which enables radio-based data exchange according to a common communication protocol; Connecting (M3) one or more peripheral adapters (80) via wired data network connections (E) to one or more of the one or several edge gateways (10), wherein the one or more peripheral adapters (80) each have a core interface (53) and a peripheral interface (47) designed to transmit data, which are exchanged between an edge gateway (10) and a peripheral element (500), to convert with respect to a data format and a communication protocol, wherein the core interface (53) is an instantiated core interface data store (54), an instantiated core interface driver (55) which is controlled by an instantiated interaction rule set (49) of the peripheral adapter (80), and a core interface state machine instantiated according to an element type of the peripheral element (500); and Facilitating (M4) bidirectional data communication between peripheral elements (500) of the tactical air defense system (200) connected to the one or more peripheral adapters (80) and the command post (300) via the one or more edge gateways (10) and the communication base station (90), and controlling operating states of the peripheral elements (500) from the command post (300) of the tactical air defense system (200) via the instantiated core interface state machine of the core interface (53). [12] Method (M) according to claim 11, wherein the step of establishing (M2) the bidirectional communicative radio link comprises implementing a centralized, deterministic channel access method or a decentralized, stochastic channel access method to establish the bidirectional communicative radio link between the communication base station (90) and the one or more edge gateways (10). [13] Method (M) according to one of claims 11 to 12, wherein the one or more peripheral adapters (80) are permanently integrated into each peripheral element (500). [14] Method (M) according to one of claims 11 to 12, wherein the one or more peripheral adapters (80) are mobile devices which are in communicative data connection with each peripheral element (500).

Images