EP3499175B1 - Procédé de commande d'un système de défense contre les véhicules aériens sans pilote - Google Patents
Procédé de commande d'un système de défense contre les véhicules aériens sans pilote Download PDFInfo
- Publication number
- EP3499175B1 EP3499175B1 EP18212567.4A EP18212567A EP3499175B1 EP 3499175 B1 EP3499175 B1 EP 3499175B1 EP 18212567 A EP18212567 A EP 18212567A EP 3499175 B1 EP3499175 B1 EP 3499175B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- peripheral
- data
- drone
- effector
- connector
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 19
- 230000002093 peripheral effect Effects 0.000 claims description 205
- 239000012636 effector Substances 0.000 claims description 65
- 230000004927 fusion Effects 0.000 claims description 13
- 238000004891 communication Methods 0.000 claims description 12
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000007123 defense Effects 0.000 description 46
- 238000007726 management method Methods 0.000 description 9
- 238000011156 evaluation Methods 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 8
- 238000004321 preservation Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000001419 dependent effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 241001271959 Anablepidae Species 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000005670 electromagnetic radiation Effects 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000005855 radiation Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41H—ARMOUR; ARMOURED TURRETS; ARMOURED OR ARMED VEHICLES; MEANS OF ATTACK OR DEFENCE, e.g. CAMOUFLAGE, IN GENERAL
- F41H11/00—Defence installations; Defence devices
- F41H11/02—Anti-aircraft or anti-guided missile or anti-torpedo defence installations or systems
Definitions
- the invention relates to a method for controlling a drone defense system.
- Remote-controlled small aircraft are becoming more and more powerful, both in terms of their payload and in terms of their control and flight capabilities.
- model building drones can easily be remote-controlled over long distances without the pilot standing on the ground having to keep an eye on them.
- a method for controlling a drone defense system and a drone defense system according to the preambles of claims 1 and 11 is from US Pat JP 2014 052 138 A known. Also the US 2017/0261999 A1 deals with a system for fighting drones.
- the invention is based on the consideration that a drone defense system can be controlled in a particularly flexible manner if the control system has a modular structure.
- Individual peripheral devices with the associated peripheral connector can easily be exchanged, which means that the properties of the drone defense system in can be easily adapted to a new task without a central management system having to be replaced or reprogrammed as a whole.
- a drone can be understood to mean an unmanned aircraft such as a remote-controlled aircraft, in particular up to a total weight of twenty kilograms, for example from the hobby area of model aircraft building. It can be a so-called Small Unmaned Aircraft (SUA) or a Micro Air Vehicle (MAV).
- a drone can be a rotary wing aircraft, in particular with a plurality of rotors, for example a quadrocopter or a hexacopter. However, a fixed wing aircraft is also possible.
- the group of peripheral devices expediently comprises a sensor, in particular for recognizing a drone feature, such as a flight noise, an optical signature or the like.
- An effector is also useful as a peripheral device, i.e. a device for intercepting and / or destroying a drone.
- the effector can be an interceptor missile, an explosive device, a laser or the like and can have the task of bringing a flying drone to the ground in some way.
- a control station is also useful as a peripheral device, via which an operator can control the drone defense system.
- the control station is expediently designed in such a way that the effector can be actuated from it, for example the interceptor missile is ignited or a defense laser is switched on.
- the main components of the drone defense system are the central command system and the peripheral devices.
- the central management system is divided into several peripheral connectors, each of which controls its peripheral device.
- the peripheral connectors are expediently independently functioning modules that each control their peripheral device separately from one another.
- the peripheral connectors with their peripheral devices expediently form a star-shaped structure around the central message core, which has at least as many arms as there are peripheral connectors, and the arms each extend from the message core via their peripheral connector to their peripheral device and, in particular, are only connected to each other in the message core.
- the peripheral connectors are expediently only in terms of data technology connected to each other via the message core. All data that are exchanged between the peripheral connectors for system control are therefore entered in the message core.
- Each peripheral connector can have its own input to the message core and an output to its peripheral device. Input and output are only connected to each other for data purposes through the peripheral connector.
- a peripheral device can consist of several units.
- a peripheral device has one or more sensors.
- several sensors can form a peripheral device.
- the group of peripheral devices comprises a primary sensor and a secondary sensor.
- the two sensors each form a peripheral device, which expediently work independently of one another.
- Both peripheral devices are each connected to the message core via a peripheral connector.
- the peripheral connector of the primary sensor controls only this and the peripheral connector of the secondary sensor controls only the secondary sensor.
- the peripheral connector of the secondary sensor advantageously controls it on the basis of data from the primary sensor.
- the primary sensor is expediently a sensor that is prepared for the initial detection of a drone. It can have an all-round sensor, i.e. a sensor that is 360 ° sensitive.
- the sensor can be an acoustic sensor. If the sensor detects an event, i.e. an event that could be a drone, the data associated with the event can be transmitted to the message core as generic data. This is done by the peripheral connector assigned to the primary sensor, which either extracts an event from the data of the primary sensor or - if the primary sensor has already extracted an event - converts the event data into a generic form.
- the primary sensor expediently sends target information about the event to the peripheral connector, which can pass it on to the message core in a generically adapted form.
- the target information can be two-dimensional information, that is to say a direction, for example in the form of two angles, or three-dimensional information with an additional distance component.
- the peripheral connector of the primary sensor is advantageously designed in such a way that it filters out generic information from the information from the primary sensor and discards the rest.
- the generic information is placed in the message core and is available to all other peripheral links, for example.
- Generic information from the primary sensor can be information about an event that has also been converted into generic form by the peripheral connector.
- the secondary sensor is expediently a sensor that is oriented towards a target on the basis of the directional information from the primary sensor.
- the secondary sensor is expediently sensitive to electromagnetic radiation, in particular in the optical range, infrared range or radar range.
- the group of peripheral devices includes a software module for data fusion of several sensors, also called a data fusion unit.
- a peripheral connector in the group of peripheral connectors that only controls this software module.
- This data fusion unit is advantageously prepared to determine a movement track of a drone from data from several sensors.
- the multiple sensors expediently include one or more primary sensors and one or more secondary sensors.
- the trajectory of the drone's movement is expediently determined from a change in the data from the multiple sensors over time.
- the movement track or data for this are expediently transmitted from the data fusion unit to its peripheral connector. After a suitable conversion into generic data, this can feed the data into the message core.
- the secondary sensor and / or the primary sensor can be prepared to classify the target.
- a classification of the target can be assigning the target to one of several different classes of different missiles or drones.
- a classification of the missile expediently includes a distinction between missiles to be attacked and missiles not to be attacked. The detection of unmanned small missiles is particularly useful. If the primary sensor has not already classified the target, so this can be done by the secondary sensor, which outputs a target type, for example.
- the target type is one of several possible target types that can classify different aircraft and also a fault type, i.e. a device that is not a device to be defended against.
- the activity of a lawnmower was wrongly classified as an event by the primary sensor, this can for example be classified as an error type by the primary sensor, i.e. as a device that cannot be defended against.
- the target type is set by the associated peripheral link as generic data in the message core.
- the group of peripheral devices includes a software module for classifying a detected drone, also called a classification unit.
- This software module expediently transmits its classification data to its peripheral connector.
- the group of peripheral devices expediently includes an effector that can be designed as an interceptor missile.
- the peripheral connector of the interceptor missile controls the interceptor missile based on data from the message core and possibly its own data, in particular exclusively based on the message core data and possibly its own data. For example, this data contains a movement track of the drone, so that the peripheral connector lets the interceptor missile fly towards the drone based on this data, so that the interceptor missile ends the drone's onward flight, for example by destroying the drone or capturing the drone with fibers.
- the execution and programming of the peripheral connector can be tailored to the interceptor missile so that different interceptor missiles can be used by the associated peripheral connector.
- the peripheral connector of the drone defense system is also replaced and the drone defense system is functional again without other peripheral connectors or peripheral devices having to be changed as a result.
- the group of peripheral devices expediently comprises a software module for assessing the situation, expediently an object to be protected.
- This software module also called a position evaluation unit, can be a Output degree of threat. Additionally or alternatively, it can contain information about what type of missile it is and what kind of damage it can cause. It is also useful to know where the destination is likely to fly and which environment is at risk. It also makes sense if this or another software component determines and outputs which effector can be used to defend against the drone, i.e. which effector has a sufficient degree of success for defending the drone at the current moment or probably in a future. All of this data can be fed into the message core.
- the control station expediently comprises an output means, for example a screen, for the visual output of situation evaluation data to an operator.
- This can now control a future action of the drone defense system by an input in an input device.
- the operator can visually assess the position shown on the output device on the basis of the information displayed.
- the operator can now use an input to give a defense command, on the basis of which an effector is activated, for example an interceptor missile is launched.
- the operator is expediently provided with information that helps him to form an opinion. For example, an image of the flying drone can be displayed and, in particular, a map with a trajectory so that the operator can see where the drone is flying to. Data for assessing the situation or a threat scenario can also be displayed.
- an effector release module is provided as a further peripheral device.
- the effector release module is expediently connected in terms of data technology indirectly via a peripheral connector only assigned to it or directly with the message core.
- the effector release module can be present in addition to a control station and enables a four-eyes check of a defense order.
- the module can consist of a button or a lever that has to be actuated by another operator for additional unlocking of the effector (s). It is advantageous if, in order to trigger an effector, both unlocking information must be present in the message core, that is to say that of the effector unlocking module and that of a control center.
- the peripheral connector of the effector is expediently designed so that it has a Arming of the effector, for example a launch of the interceptor missile, is only initiated when both arming information is available.
- the structure of the central management system and the message core can be kept simple if data is transmitted from one peripheral device to another peripheral device exclusively via the assigned peripheral connector and the message core.
- the modular structure of the central management system and thus the exchange of a peripheral device and / or a peripheral connector is very easy as a result.
- the message core can at least essentially be limited to a line system without essential data processing components having to be present between the peripheral connectors.
- peripheral connectors A simple message transfer between peripheral connectors can be achieved if they exchange with each other in the message core via broadcast.
- Each peripheral connector recognizes information that is intended for it independently.
- the communication in the message core exclusively with generic data facilitates the exchange of devices considerably. For this it is useful if the peripheral connectors translate information from their peripheral device into a data format that is understandable for all peripheral connectors.
- the data format expediently also contains the data protocol.
- the group of peripheral devices contains at least one effector and one worker assigned to the effector who determines the effector's ability to act from location data from the message core. Data on the ability to act are fed into the message core via the peripheral connector assigned to the effector. In this way, for example, an operator in a control room knows whether defense against an approaching drone is currently possible or still or no longer possible.
- the invention also relates to a drone defense system according to the features of claim 11 with a group of peripheral devices and a central guidance system.
- the control system according to the invention comprises several peripheral connectors and a message core via which the peripheral connectors are networked with one another, each peripheral device being connected to the message core exclusively via a peripheral connector assigned to it and the Peripheral connectors jointly form a central management system for the peripheral devices and are each prepared to control their peripheral device.
- the group of peripheral devices advantageously contains at least one sensor, an effector, preferably designed as an interceptor missile, and a control station.
- the message core is expediently designed in the form of a data line system.
- FIG 1 shows an object 2 to be protected, which in the exemplary embodiment shown is a football stadium.
- a drone 4 flying towards the object 2 to be protected is repelled by a drone defense system 6, which is located partly in a building 8 and partly outside the building 8.
- the drone defense system 6 is equipped with a plurality of effectors 10, which in this exemplary embodiment are interceptor missiles, as in FIG FIG 1 is shown schematically.
- effectors are also possible, for example lasers or other high-energy transmitters, the directed energy of which disturbs the optics, the receiver or another sensor system of the drone 4 to such an extent that a remotely controlled and directed onward flight is impossible.
- the drone defense system 6 is equipped with a number of sensors 12, 14 which are positioned on and / or in the vicinity of the object 2 to be protected.
- the drone defense system 6 also has a control station 16 in the building 8, from which an operator controls actions of the drone defense system 6.
- the effectors 10, the sensors 12, 14 and the control station 16 form a group of peripheral devices of the drone defense system 6, which are controlled by a central guidance system of the drone defense system 6.
- the peripheral devices can be selected differently, with those in the Figures 1 and 2
- the peripheral devices described are selected only by way of example to illustrate particularly suitable combinations.
- the central guidance system of the drone defense system 6 is shown below using the illustration FIG 2 described.
- FIG 2 shows a schematic representation of a drone defense system 6, as it is in the embodiment from FIG 1 would be usable. It comprises several sensors 12, 14, which are shown in FIG 2 are only shown by way of example. The same applies to the effectors 10, whereby these do not have to be of identical construction, but can be specialized in different drone defense scenarios, as in FIG FIG 2 is indicated.
- an effector unlocking module 18 which can be a safety unit, a master arm safety switch or the like.
- the effectors 10, the sensors 12, 14, the control station 16 and the effector release module 18 belong to a group of peripheral devices that are controlled by a central management system 30.
- the group of peripheral devices also includes a software module 20 for data fusion, a software module 22 for classification and a software module 24 for position evaluation - also called data fusion unit 20, classification unit 22 and position evaluation unit 24.
- the group of peripheral devices also contains a success estimator 26 and an evidence preservation unit 28.
- a peripheral connector 10a-28a is provided for each of the peripheral devices 10-28.
- the peripheral connectors 10a-28a form the central management system 30, which additionally has a central message core 32.
- the central message core 32 is a zone within the central management system 30 into which all information is entered that is exchanged between the peripheral devices 10-28 and / or the associated peripheral connectors 10a-28a.
- the central message core 32 comprises only a data line system, for example a data bus.
- the area between the peripheral connectors 10a-28a is free of control units of the peripheral devices 10-28, a device for pure message broadcast control not being understood as a control unit.
- central data processing units in the message core 32, for example to subdivide the message core into two or more zones which are separated from one another by appropriate translators or the like.
- the structure of the drone defense system 6 is such that the peripheral devices 10-28 are connected in a star shape to the central message core 32, each via only one peripheral device 10-28 or one type of peripheral device associated peripheral connector 10a-28a. There is no data connection between the peripheral devices 10-28 without one or more interconnected peripheral connectors 10a-28a. Information from one peripheral device 10-28 to another must in this respect always run through the message core 32, the associated peripheral connector 10a-28a being interposed between peripheral device 10-28 and message core 32. The peripheral connectors 10a-28a also communicate with one another exclusively via the message core 32. Since messages are distributed from one peripheral connector 10a-28a to another via a broadcast, the information can be received by all peripheral connectors 10a-28a.
- Each peripheral connector 10a-28a exclusively controls its peripheral device 10-28, whereby a peripheral device 10-28 in this context can also be understood to be a group of identical peripheral devices, as indicated, for example, by the sensors 12, 14.
- a peripheral device 10-28 in this context can also be understood to be a group of identical peripheral devices, as indicated, for example, by the sensors 12, 14.
- several peripheral devices 12, 14 can be connected together with their associated peripheral connector 12a, 14a.
- the peripheral connectors 10a-28a are used to control your peripheral device 10-28. To do this, they receive messages from their peripheral device 10-28 and send control information to their peripheral device 10-28.
- the information received from the peripheral device 10-28 is examined by the associated peripheral connector 10a-28a for generic data, that is to say such data that another peripheral device 10-28 needs to perform a function of the drone defense system 6.
- the corresponding information from the peripheral device 10-28 is converted into a generic data format by the peripheral connector 10a-28a and imported into the message core 32.
- the peripheral connector 10a-28a, the peripheral device 10-28 of which requires this information to perform a function of the drone defense system 6, receives this information and converts it, if necessary, into a data format that the associated peripheral device 10-28 can process.
- the peripheral connector 10a-28a may add further information that contributes to the control of the corresponding peripheral device 10-28.
- the peripheral connectors 10a-28a thus have the functions of a data filter, a translator from a peripheral data format into a generic data format and back, and a control unit for controlling their peripheral device 10-28.
- peripheral device 10-28 If a peripheral device 10-28 is to be exchanged and replaced by another, the associated peripheral connector 10a-28a may also have to be removed and replaced by another.
- the other peripheral connectors 10a-28a can continue to be operated unchanged, since the replaced peripheral connector 10a-28a, like its predecessor, only feeds generic data into the central message core 32, which is received and processed by another peripheral connector 10a-28a. This makes it possible to exchange peripheral devices 10-28 and thus modify the drone defense system 6, for example to different threat scenarios, different drones 4 or different objects 2 to be protected, very easily and inexpensively.
- peripheral devices 10-14 distributed.
- the other peripheral devices 16-28 are accommodated, for example, in the building 8 in which the control station 16 is also arranged.
- the central guidance system 30 with the peripheral connectors 10a-28a is also in the building. If a drone approaches the object 2 to be protected, it sends out acoustic and electromagnetic signals which are received by one or more of the sensors 12, 14.
- the sensors 12 are, for example, primary sensors that are equipped with an all-round sensor system, which means that they monitor the surrounding area through 360 °.
- the primary sensors 12 are, for example, acoustic sensors, the evaluation unit of which is capable of filtering or recognizing the flight noises of a drone 4 from other noises and thereby recognizing an event, i.e. an approaching drone 4, as such. If an event is recognized, the recognizing sensor 12 sends data assigned to the event to its peripheral connector 12a. In this respect, the latter receives data about the event from one or more primary sensors 12. The sensor 12 may already be in a position to extract directional data from the event. Otherwise, this task is assigned to the peripheral connector 12a, which determines the direction data for the event from event data from several sensors 12 that recognize the event. In any case, the direction data are entered into the message core 32.
- This primary information is important for at least one secondary sensor 14, which uses the directional information to align itself with the target or the approaching drone 4 and detect it, for example optically and / or by radar radiation.
- the secondary sensor or sensors 14 uses the directional information to align itself with the target or the approaching drone 4 and detect it, for example optically and / or by radar radiation.
- three-dimensional information about the event is now available, namely the direction and the distance of the drone 4.
- high-resolution optical images are available on which the drone 4 is depicted.
- These secondary data are transmitted to the associated peripheral connector 14a, which extracts the generic information from the data and places it in the message core 32.
- the primary information and / or the secondary information in the message core 32 are important for the classification unit 22 and the data fusion unit 20.
- the classification unit 22 uses the data, for example the high-resolution images and / or the three-dimensional directional information, to classify the event.
- the classification is binary and is limited to "threat” or "non-threat”.
- the classification expediently also includes a type of drone, for example a type of construction or, ideally, even a make.
- the data fusion unit 20 generates a track or a track of the target 4 from the optical data and / or the radar data. In this way, a flight direction and flight speed can be determined. In addition, the unit 20 generates a probable future track by means of a predication.
- the data from a plurality of optical sensors 12, 14 and / or radar sensors 14 are usually used for such data fusions and merged by the software component. For this purpose, it is useful if several secondary sensors 14 and possibly also several primary sensors 12 are present in order to be able to detect the target 4 well.
- the flown track of the target 4 is in turn processed by the classification unit 22, since the type of the target 4 can be inferred from the altitude, airspeed and / or flight agility. In this way, the classification based on the optical data can be facilitated, or a preselection can be made.
- the associated peripheral connectors 20a, 22a ensure both a back and forth translation of the data from and to the message core 32 as well as a filtering of the generic data from the whole existing peripheral data and the addition of generic data with further data that the associated peripheral device 20, 22 may need for further processing of the data.
- the data necessary or useful for your peripheral device 10-28 are filtered out of the pool of data present in total in the message core 32 by the respective peripheral link 10a-28a and possibly translated and supplemented and output to the respective peripheral device 10-28.
- the situation assessment unit 24 forms a situation assessment from the data on the event present in the message core 32.
- the classification from the classification unit 22 and the trace of the drone 4 from the data fusion unit 20 that will presumably be flown in the future are used.
- the location and type of the object to be protected 2 is also used.
- the location assessment is again entered into the message core 32 via the peripheral connector 24a and is available there to the control center 16 or its peripheral connector 16a for forwarding to the control center 16.
- On a screen 34 of the control station 16 the situation assessment is output to an operator.
- the operator sees, for example, the location of the object 2 to be protected in a geographical map, for example a city map, and the past and future trace of the approaching drone 4.
- the classification and a potential threat are expediently output to the operator.
- the situation assessment can also include a possibility of defense by the effectors 10.
- the defense option contains the information as to whether one of the effectors 10 is able to intercept the drone 4 and, if so, expediently where and in what way. For example, an encounter point between an effector 10 and the approaching drone is displayed to the operator on the screen 34 when the effector 10 starts immediately. From this, for example optical information, the operator can see how long he has time left for a decision to start a drone defense action.
- an effector 10 is able to repel the approaching drone 4 depends, among other things, on the type of effector 10. For example, a laser cannot shine around the corner if the drone is flying behind a building or other object. For example, an interceptor missile is not fast enough to be able to reach the drone 4 in good time, or the drone 4 is still too far away and thus outside the flight range of the interceptor missile.
- the effectors 10 are connected to so-called workers 38, which are arranged, for example, for signaling purposes between the effector 10 and the associated peripheral connector 10a. From information on the trajectory of target 4 and / or the situation assessment, the workers 38 determine the current and, in particular, future possibilities of action for their effector 10.
- the component status i.e. whether the sensors 12, 14 are active, whether the effectors 10 are secured or unlocked, which sensors 12, 14 and effectors 10 are present, whether the effector unlocking module 18 is used to unlock the Effector 10 is ready and the like.
- a corresponding command can be entered into the control station 16 by the operator via the input unit 36, for example a keyboard. If this is the case, the operator enters the corresponding fire command in the control room 16 and this is fed into the message core 32 as generic information.
- the four-eyes principle is of particular importance in missile defense technology, so that the effector release module 18 can be present. This can consist of a simple button or a lever that has to be actuated by another operator for additional unlocking of the effector (s) 10. To trigger an effector 10, both unlocking information must be present in the message core 32.
- the decision as to whether the unlocking message is passed on to an effector 10 can be made by the associated peripheral connector 10a, which is programmed, for example, so that the corresponding unlocking information is only output to the worker 38 or the associated effector 10 if the double unlocking command is present.
- an associated peripheral connector can be dispensed with, since the signal from the effector unlocking module 18 can be very simple and the message core 32 can already be entered as generic information.
- a monodirectional data transmission from the effector unlocking module 18 to the message core 32 is also sufficient, since the module 18 does not need any information from the message core 32 in order to perform its task. If the drone 4 is defended against, another component is advantageous, namely the success estimator 26.
- These can be determined, for example, from image data that are present as generic data in the message core 32 and can be processed by the success estimator 26.
- the success estimator 26 extracts the most meaningful images for recognizing the defensive success from the images of the sensors 12, 14 and transfers them as success images to the message core 32 so that they are displayed on the control station 16 or its screen 34 and viewed by the operator can. In this way, the operator can understand the effect of the effector 10 or the success or failure of the defense.
- the component of the evidence preservation unit 28, whose task is, for example, the data storage of essential messages from the message core 32, such as the success images from the success estimator 26, is also useful of the target 4 and the like are stored by the evidence preservation unit 28. In this way, a threat situation and a defense scenario can be secured for subsequent evaluations or a justification.
- the evidence preservation unit 28 permanently stores all of the data from the message core 32 that are relevant for the preservation of evidence.
Landscapes
- Engineering & Computer Science (AREA)
- Aviation & Aerospace Engineering (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- General Engineering & Computer Science (AREA)
- Aiming, Guidance, Guns With A Light Source, Armor, Camouflage, And Targets (AREA)
Claims (11)
- Procédé de commande d'un système de défense contre les drones (6), dans lequel un groupe d'appareils périphériques (10-28) comprenant un effecteur (10), comprenant en particulier un capteur (12, 14) et un poste de commande (16), est commandé par plusieurs connecteurs périphériques (10a-28a), dont chacun commande précisément un appareil périphérique (10-28), associé uniquement au connecteur périphérique (10a-28a) respectif, et qui forment ensemble un système de commande central (30) du système de défense contre les drones (6) et échangent entre eux des données pour commander les appareils périphériques (10-28) par l'intermédiaire d'un noyau de messages (32),
caractérisé en ce qu'un opérateur (38) associé à l'effecteur (10) détermine une capacité d'action de l'effecteur (10) à partir de données de position provenant du noyau de messages (32) et introduit des données concernant la capacité d'action dans le noyau de messages (32) par l'intermédiaire du connecteur périphérique (10a) associé à l'effecteur (10). - Procédé selon la revendication 1,
caractérisé en ce que le groupe d'appareils périphériques (10-28) comprend un capteur primaire (12) et un capteur secondaire (14), et le connecteur périphérique (14a) du capteur secondaire (14) commande ce dernier sur la base de données provenant du capteur primaire (12). - Procédé selon la revendication 1 ou 2,
caractérisé en ce que le groupe d'appareils périphériques (10-28) comprend une unité de classification (22) destinée à classer un drone (4) détecté, laquelle transmet ses données de classification à son connecteur périphérique (22a). - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que le groupe d'appareils périphériques (10-28) comprend une unité de fusion de données (20) pour la fusion de données provenant de plusieurs capteurs (12, 14), laquelle détermine un tracé de déplacement d'un drone (4) à partir de données provenant de plusieurs capteurs (12, 14) et le transmet à son connecteur périphérique (20a). - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que l'effecteur (10) est conçu comme un corps d'interception et le connecteur périphérique (10a) du corps d'interception commande ce dernier exclusivement sur la base des données du noyau de messages (32), de sorte que le corps d'interception vole ainsi vers un drone (4) et met fin à la poursuite du vol de ce dernier. - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que le groupe d'appareils périphériques (10-28) comprend une unité d'évaluation de position (24) pour l'évaluation de la position d'un objet (2) à protéger, dont les données de position déterminées sur la base d'un drone (4) détecté sont transmises à un poste de commande (16) par l'intermédiaire de son connecteur périphérique (24a). - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce qu'il est prévu un module de désarmement d'effecteur (18) en tant qu'appareil périphérique supplémentaire, lequel est relié par voie de transmission de données indirectement par l'intermédiaire d'un connecteur périphérique (18a) qui lui est uniquement affecté ou directement au noyau de messages (32). - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que des données sont transmises d'un appareil périphérique (10-28) à un autre appareil périphérique (10-28) exclusivement par l'intermédiaire des connecteurs périphériques associés (10a-28a) et du noyau de messages (32). - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que les connecteurs périphériques (10a-28a) échangent des informations entre eux par diffusion dans le noyau de messages (32). - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que les connecteurs périphériques (10a-28a) convertissent des informations de leur appareil périphérique (10-28) en un format de données compréhensible par tous les connecteurs périphériques (10a-28a). - Système de défense contre les drones (6) comprenant un groupe d'appareils périphériques (10-28) comprenant un effecteur (10), comprenant en particulier un capteur (12, 14) et un poste de commande (16), et un système de guidage central (30) comprenant plusieurs connecteurs périphériques (10a-28a) et un noyau de messages (32), par l'intermédiaire duquel les connecteurs périphériques (10a-28a) sont mis en réseau les uns avec les autres, dans lequel chaque appareil périphérique (10-28) est relié au noyau de messages (32) exclusivement par l'intermédiaire d'un connecteur périphérique (10a-28a) qui lui est associé, et les connecteurs périphériques (10a-28a) forment ensemble le système de gestion central (30) des appareils périphériques (10-28) et sont respectivement conçus pour commander leur appareil périphérique (10-28),
caractérisé par un opérateur (38) associé à l'effecteur (10) et configuré pour déterminer une capacité d'action de l'effecteur (10) à partir de données de position provenant du noyau de messages (32) et pour introduire des données concernant la capacité d'action dans le noyau de messages (32) par l'intermédiaire du connecteur périphérique (10a) associé à l'effecteur (10).
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102017011592.3A DE102017011592A1 (de) | 2017-12-14 | 2017-12-14 | Verfahren zum Steuern eines Drohnenabwehrsystems |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3499175A1 EP3499175A1 (fr) | 2019-06-19 |
EP3499175B1 true EP3499175B1 (fr) | 2021-09-01 |
Family
ID=64665552
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18212567.4A Active EP3499175B1 (fr) | 2017-12-14 | 2018-12-14 | Procédé de commande d'un système de défense contre les véhicules aériens sans pilote |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3499175B1 (fr) |
DE (1) | DE102017011592A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2809997C1 (ru) * | 2023-03-07 | 2023-12-21 | Акционерное общество "Научно-технический центр радиоэлектронной борьбы" | Система обнаружения и противодействия беспилотным воздушным судам |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102020200124B3 (de) * | 2020-01-08 | 2021-04-29 | Zf Friedrichshafen Ag | Sicherer Betrieb eines Fahrzeugs |
DE102020003043A1 (de) | 2020-05-20 | 2021-11-25 | SDT Industrial Technology UG (haftungsbeschränkt) | Das Luftraum-Schutz-System gegen die Flugobjekte |
CN114500687B (zh) * | 2022-01-26 | 2023-12-12 | 北京环境特性研究所 | 反无人机系统的设计方法、装置、计算设备及存储介质 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7974814B2 (en) * | 2007-06-15 | 2011-07-05 | Raytheon Company | Multiple sensor fusion engine |
US8368584B2 (en) * | 2009-06-10 | 2013-02-05 | The University Of North Dakota | Airspace risk mitigation system |
US9389681B2 (en) * | 2011-12-19 | 2016-07-12 | Microsoft Technology Licensing, Llc | Sensor fusion interface for multiple sensor input |
JP2014052138A (ja) * | 2012-09-07 | 2014-03-20 | Toshiba Corp | 防空システム |
US9715009B1 (en) * | 2014-12-19 | 2017-07-25 | Xidrone Systems, Inc. | Deterent for unmanned aerial systems |
DE102015011058A1 (de) * | 2015-08-27 | 2017-03-02 | Rheinmetall Waffe Munition Gmbh | System zur Abwehr von Bedrohungen |
WO2017040254A1 (fr) * | 2015-08-28 | 2017-03-09 | Laufer Wind Group Llc | Atténuation des menaces sur les petits aéronefs sans équipage |
US20170261604A1 (en) * | 2016-03-11 | 2017-09-14 | Raytheon Bbn Technologies Corp. | Intercept drone tasked to location of lidar tracked drone |
-
2017
- 2017-12-14 DE DE102017011592.3A patent/DE102017011592A1/de not_active Withdrawn
-
2018
- 2018-12-14 EP EP18212567.4A patent/EP3499175B1/fr active Active
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2809997C1 (ru) * | 2023-03-07 | 2023-12-21 | Акционерное общество "Научно-технический центр радиоэлектронной борьбы" | Система обнаружения и противодействия беспилотным воздушным судам |
Also Published As
Publication number | Publication date |
---|---|
EP3499175A1 (fr) | 2019-06-19 |
DE102017011592A1 (de) | 2019-06-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE60305041T2 (de) | Luftfahrtsystem und bodenstation zur führung eines flugzeugs abseits des kurses und alarmübertragung | |
EP3499175B1 (fr) | Procédé de commande d'un système de défense contre les véhicules aériens sans pilote | |
EP3485472B1 (fr) | Système et procédé de détermination vérifiée d'un état d'incendie ainsi que véhicule et unité centrale associés | |
EP2955475B1 (fr) | Procédé de fonctionnement d'un système de défense aérienne basé à terre | |
EP1505556B1 (fr) | Procédé et appareil de reconnaissance des obstacles de vol | |
EP3129971B1 (fr) | Procédé de surveillance d'espace aérien | |
DE102015003323A1 (de) | Einrichtung zum Einfangen eines fliegenden unbemannten Luftfahrzeugs | |
EP3198217A1 (fr) | Dispositif de défense permettant de combattre un aéronef sans pilote, dispositif de protection permettant de combattre un aéronef sans pilote et procédé permettant de faire fonctionner un dispositif de protection | |
EP2820371B1 (fr) | Véhicule militaire et système ti intégré pour un véhicule militaire | |
EP3139125B1 (fr) | Installation de defense par drone contre les drones etrangers | |
EP3819659A1 (fr) | Module de communication pour composants de systèmes de défense aérienne tactique | |
DE102008018880A1 (de) | Überwachungsverfahren und -vorrichtung für Windkraftanlagen, Gebäude mit transparenten Bereichen, Start- und Landebahnen und/oder Flugkorridore von Flughäfen | |
EP3648081A1 (fr) | Procédé de fonctionnement d'un aéronef au moins temporairement sans pilote ainsi qu'un tel aéronef | |
DE102019114354A1 (de) | Verfahren und System zur Vermeidung von Kollisionen zwischen Fluggeräten und anderen fliegenden Objekten | |
EP2511894A1 (fr) | Procédé de surveillance d'un espace aérien autour d'un aéronef | |
DE102021002195B3 (de) | Kommunikationssystem fuer ein system zur bodengebundenen luftverteidigung | |
DE102018202901A1 (de) | Verfahren und Vorrichtung zur Abwehr einer detektierbaren Drohne | |
DE102021110647A1 (de) | Verfahren, Abfangdrohne und Abfangsystem zur Abwehr einer unerwünschten Fremddrohne | |
DE19716025B4 (de) | Plattform mit abschießbaren, zielverfolgenden Flugkörpern, insbesondere Kampfflugzeug | |
DE102021115140B4 (de) | Verfahren zum Steuern einer Flugbewegung eines Fluggeräts zum Landen oder zum Abwerfen einer Ladung sowie Fluggerät | |
DE102020106703B4 (de) | Objekterkennungseinheit mit Sensoreingaben in verschiedenen Spektralbereichen | |
EP3376152A1 (fr) | Système de traitement d'informations et procédé de traitement d'informations | |
EP2526367A1 (fr) | Missile et procédé pour détecter une cible | |
EP3670342B1 (fr) | Aéronef sans pilote doté d'un système de commande de vol | |
EP3933539B1 (fr) | Train de véhicules pouvant être conduit de manière autonome |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20191219 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20210401 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 1426658 Country of ref document: AT Kind code of ref document: T Effective date: 20210915 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 502018006818 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20210901 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211201 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211202 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220101 Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220103 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 502018006818 Country of ref document: DE |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
26N | No opposition filed |
Effective date: 20220602 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20211231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211214 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211214 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211231 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20181214 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231220 Year of fee payment: 6 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20231228 Year of fee payment: 6 Ref country code: FR Payment date: 20231222 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240214 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210901 |