EP2405233B1 - Procédé de commande d'une munition aérienne - Google Patents

Procédé de commande d'une munition aérienne Download PDF

Info

Publication number
EP2405233B1
EP2405233B1 EP11005432.7A EP11005432A EP2405233B1 EP 2405233 B1 EP2405233 B1 EP 2405233B1 EP 11005432 A EP11005432 A EP 11005432A EP 2405233 B1 EP2405233 B1 EP 2405233B1
Authority
EP
European Patent Office
Prior art keywords
mission
data
control means
component
missile
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.)
Revoked
Application number
EP11005432.7A
Other languages
German (de)
English (en)
Other versions
EP2405233A2 (fr
EP2405233A3 (fr
Inventor
Thomas Dr. Kuhn
Wilhelm Hinding
Andreas Beutel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Diehl Defence GmbH and Co KG
Original Assignee
Diehl BGT Defence GmbH and Co KG
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=44763678&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP2405233(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Diehl BGT Defence GmbH and Co KG filed Critical Diehl BGT Defence GmbH and Co KG
Publication of EP2405233A2 publication Critical patent/EP2405233A2/fr
Publication of EP2405233A3 publication Critical patent/EP2405233A3/fr
Application granted granted Critical
Publication of EP2405233B1 publication Critical patent/EP2405233B1/fr
Revoked legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F42—AMMUNITION; BLASTING
    • F42B—EXPLOSIVE CHARGES, e.g. FOR BLASTING, FIREWORKS, AMMUNITION
    • F42B15/00—Self-propelled projectiles or missiles, e.g. rockets; Guided missiles
    • F42B15/01—Arrangements thereon for guidance or control
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F41—WEAPONS
    • F41G—WEAPON SIGHTS; AIMING
    • F41G7/00—Direction control systems for self-propelled missiles
    • F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
    • F41G7/22—Homing guidance systems
    • F41G7/2253—Passive homing systems, i.e. comprising a receiver and do not requiring an active illumination of the target
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F41—WEAPONS
    • F41G—WEAPON SIGHTS; AIMING
    • F41G7/00—Direction control systems for self-propelled missiles
    • F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
    • F41G7/22—Homing guidance systems
    • F41G7/226—Semi-active homing systems, i.e. comprising a receiver and involving auxiliary illuminating means, e.g. using auxiliary guiding missiles
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F41—WEAPONS
    • F41G—WEAPON SIGHTS; AIMING
    • F41G7/00—Direction control systems for self-propelled missiles
    • F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
    • F41G7/22—Homing guidance systems
    • F41G7/2273—Homing guidance systems characterised by the type of waves
    • F41G7/2293—Homing guidance systems characterised by the type of waves using electromagnetic waves other than radio waves

Definitions

  • the invention relates to a method for controlling a combat missile comprising a data memory, a control means and a mission component, wherein the control means controls the mission component during a flight of the combat missile.
  • a combat missile and method of controlling such a combat missile are off US Pat. No. 7,506,587 B1 known.
  • a missile introduced into a rocket launcher is recognized by the fire control system and classified, for example, on the basis of a type designation.
  • the detection can be done by a codified interface, such as a plug shape or the like, so that the fire control system can correctly recognize the type of missile introduced into the missile launcher.
  • the control means controls the flight of the Missiles according to the data received from the fire control system, which may include an aircraft trajectory, an ignition timing and other data.
  • the data memory contains identification data for a plurality of different mission components and the control means reads type data from the mission component, identifies the type of mission component based on the recognition data and the type data, and controls steps depending on the type Mission component.
  • the invention is based on the consideration that the execution of a mission with a new mission component in a conventional combat missile, e.g. The transfer of a new active use, was previously associated with a considerable effort, because properties of the mission component in the fire control system had to be re-integrated and above all qualified. Therefore, before inserting a new mission component into the known combat missile, the computer systems of the fire control system must be supplied with the type data of the new mission component and this process had to be qualified to verify that the algorithms for calculating control data stored in the fire control system Missile with the new type data work properly and in any battle situation. With a large number of different mission components such integration and qualification in different fire control systems is associated with a very high expenditure. This limits flexibility, e.g. rocket artillery with regard to alternative warhead variants.
  • control data for controlling the mission component of the fire control system in the control means of the combat missile can be moved.
  • control data may be data for controlling the missile on its trajectory, data for triggering an action, data for controlling a launch angle, and the like.
  • An integration and qualification of the type data of the mission component does not have to take place in the fire control system, but can take place at the level of the combat missiles are relocated.
  • the tasks of the fire control system can be simplified to the transmission of mission data to the missile, so that the fire control system does not need to process the specific type data of the mission component.
  • the fire control system of a modular artillery rocket system for example, only needs to know one single type of ammunition, namely the generic type of the missile, for example the modular artillery rocket. This can, for example, spend different payloads in different active applications, wherein the control means of the missile is programmed and the data memory of the missile contains such data that a calculation of the control action adapted to the active use by the control means is possible.
  • the data store contains detection data about a plurality of different mission components.
  • Detection data is such data by which the control means can identify the type of mission component, for example by comparing type data of the mission component with the recognition data.
  • the identification data can be identical to the type data, so that for identification, for example, the type designation is compared with a list of type designations.
  • the type data may be any type of information identifying the type of mission component. In a particularly simple way, type data can be acquired by the control means if they are stored in a data component of the mission component and are read out by the control means or handed over to the control means.
  • type data may also be hardware information, such as an interface property, e.g. a plug shape.
  • the type of the mission component is identified by the control means and the control means is based on control data in the data memory, which are associated with the corresponding identification data of the mission component, and / or control data in the data component of the mission component capable of the Steurstoff or data storage generically applied algorithms, for example for steering, regulation and / or mission control, to parameterize the mission component used in the missile appropriately. Accordingly, the control steps are calculated by means of the control data depending on the type of the mission component and executed by the control means during the mission of the missile.
  • control means it is also expedient for the control means to calculate the control steps as a function of the composition of different mission components, the mission components being known from the outset Can be mission components or also the control means initially unknown, so they must be identified only on the basis of the type data.
  • control means For identification, it suffices if the control means identifies one of several types of the mission component. Thus, for example, a completely new mission component can be used, which is not yet known to the control means. Nevertheless, by associating with a type group, communication between the control means and the mission component can be established and the control means can obtain data from the mission component for further communication or for calculating the control steps.
  • the combat missile is expediently a missile with an active use for destroying a target, in particular a combat missile, for example a ground-based missile, ie a ground-to-surface missile or a ground-to-air missile, or a sea or airborne missile.
  • a combat missile for example a ground-based missile, ie a ground-to-surface missile or a ground-to-air missile, or a sea or airborne missile.
  • the control steps may be mission control steps, such as steps to directionally control the flight of the missile and / or steps to control operation of a mission component, e.g. for deploying a work item, there may be steps for communicating with other units, e.g. for the purpose of determining control data, calculating steps for obtaining control data, and others.
  • the control means or the data memory contains generically applied algorithms for the control steps and the control means parameterizes these algorithms with control data or directly with the type data.
  • the combat missile contains at least one mission component from the group of rocket engine, active charge, seeker, fuselage and wing structure.
  • the combat missile may thus contain one or more such mission components which it recognizes and controls as indicated.
  • Each mission component expediently contains a data medium which contains the type data and possibly further data, such as operational data or operational data.
  • the data means may be a pure data storage means, such as a ROM, or a control means with a processor.
  • the identification data stored in the data memory can be subdivided into component groups, eg the component group of the rocket motors, the component group of the active charges, the component group of the seekers and the component group of the fuselage and wing structures.
  • Each component group can contain one or more mission components of the same group.
  • the control means can check whether there is a mission component for each component group and has been detected and the corresponding software component of the control means has been parameterized, for example on the basis of the type data, so that each mission component is ready for operation.
  • a further advantageous embodiment of the invention provides that the control means controls the missile on a trajectory and thereby controls the combat component, e.g. triggers the active intervention.
  • control means selects data from the type data of the mission component and transmits them to a control unit outside the missile.
  • the transmitted data may be taken from the data memory or be generated therefrom by the control means or be read out of the mission component or its data means.
  • a fire control center can be informed of which mission component or mission components are deployed in the missile so that the external control unit, such as a fire control center, can issue mission commands tailored to the mission component.
  • control means also parameterizes an algorithm of the external control unit on the basis of the data.
  • the external control unit can thus easily determine mission data, without having to be able to parameterize the respective algorithm according to the - possibly unknown - mission components.
  • the data is conveniently such data that the external control unit processes to create mission commands.
  • possible modes of operation e.g. Detonation modes of an active intervention, advantageous, which has received the control means expediently from the data means of the mission component and forwards to the external control unit.
  • control means receives from an external control unit mission data, in particular those which the external control unit has calculated in dependence on the parameterized by the control means algorithm.
  • Mission data can Target coordinates, a launch time, boundary conditions for a trajectory and the like.
  • control means receive mission data, e.g. Target coordinates or general target data to be transmitted, in particular from a Feuerleitrechner, and the control means calculated from the mission data flight data of the missile.
  • the flight data may be data characterizing the flight of the missile, such as a trajectory design, an approach direction to the target, a deployment trigger point, and the like.
  • the fire control computer which has traditionally been managed with these tasks, can be relieved of load so that it no longer needs to be so familiar with type data of the mission component.
  • control means can make a determination as to whether a flight is to the given destination, taking into account the type of mission component, e.g. of the rocket engine, is allowable.
  • the allowability can be given if the achievement of the goal as such is possible.
  • the allowability can also be characterized by the achievement or exceeding of a given value in terms of meeting a goal.
  • the success value may be a hit probability, a goal achievement below a predetermined approach angle, or before the expiration of a predetermined time.
  • a fire control center can be further de-respon- sible for the mission so that further integration of type data in the fire control computer can be dispensed with.
  • Use of the type data for identifying the mission component is sufficient so that control data and target data can be used to calculate the mission data using the type data.
  • control means determines an aircraft trajectory to a predetermined destination in dependence on the type data of the mission component.
  • the flight trajectory can be selected or calculated and is determined taking into account the type of active use. Destination coordinates as the endpoint of the flight trajectory may have been received by the control means from an external control unit.
  • the missile is in a launcher and the control means determines an angular position of the launcher in dependence on properties of the mission component and notifies the angular position of an external control unit.
  • the external control unit may be that of the launcher or a control unit of a fire control system.
  • the angular position can be a specific spatial direction, ie a specific direction of a spatial vector, or an angular range, for example around a spatial direction.
  • the angular position may be one-dimensional, e.g. as elevation angle, or two-dimensional.
  • the external control unit can check the suitability of the angular position, for example as a function of further missiles in the launcher and angular positions which they require.
  • the control unit of the missiles notified angular positions differ over a predetermined threshold.
  • the control unit may notify the control means of the missiles in the launcher of the discrepancy, for example by answering the reported angle as inappropriate.
  • the control unit determines from the different angular positions of the plurality of missiles in the launcher a firing position of the launcher and transmits them to the control means of the missile.
  • the firing position can be a compromise between different angular positions, for example an averaging of the different angular positions.
  • the control means of the missile can now determine whether the missile can reach a predetermined target in a predetermined manner depending on the firing position and the type of mission component.
  • the predetermined manner may be achievement or achievement under given conditions.
  • the firing position can be positively acknowledged by the control means, so that the launcher is ready for a launch of the missile.
  • the combat missile may include a plurality of mission components initially unknown to the control means. It is therefore advantageous if the control means reads out type data of a plurality of mission components combined in the combat missile from the data memory, identifies their types on the basis of the recognition data and the type data and carries out control steps in dependence on the composition of the mission components.
  • the control means is provided with or has access to control software, which is expediently divided into several software components.
  • control software which is expediently divided into several software components.
  • each mission component there may be a separate software component, which in particular is assigned to only one mission component group, and e.g. can be tailored by parameterization to a mission component of the group.
  • a universal applicability of the control software can thus be achieved if at least one software component is created so that it can be used for several different mission components, e.g. several mission components of a component group, such as different seekers or various so-called airframes, ie fuselage and wing structures.
  • the software component is parameterized as a function of the type data, so that the control means can now control the mission component with the parameterized software component.
  • the software component may include a navigation component and / or a mission flow control and / or an image processing component and / or a flight controller.
  • the invention is also directed to a missile having a fuselage containing a data store, a mission component, and a control means that is prepared to control the mission component during a flight of the combat missile.
  • control means is signal connected to the data memory containing detection data on a plurality of different mission components, and the control means is prepared to read type data from the mission component, identify the type of the mission component and control steps depending on the type of the mission component perform.
  • the preparation of the control means can be realized by appropriate control software of the control means, the sequence - for example, in conjunction with suitable input signals, such as sensor signals or read signals of type data - causes such a control.
  • the control means expediently comprises electronic elements which comprise a processor and a data memory which are necessary or useful for running the control software.
  • control means is prepared for controlling one, several or all of the method steps described above.
  • the control means is expediently prepared to control the missile on a trajectory and to trigger the active intervention.
  • the invention is directed to a system of multiple combat missiles as described, each containing different mission components.
  • the control means of all combat missiles be equipped with the same hardware and software components.
  • the same mission component groups associated software components of the control means before a parameterization are identical.
  • all control means are initially equipped with a software component for the seeker, all of these software components being identical.
  • the initially identical software components can now be adapted to the different seekers, so that they subsequently act differently, according to the search heads assigned to them.
  • the control means comprises, besides those software components which are adapted to mission components, e.g. through parameterization, other key hardware components that remain the same in every combat missile. These may be an inertial system used to determine the location and location of the combat missile in space, a GPS system for receiving position data, a power supply for conditioning all electrical voltages required in the combat missile from an internal or external voltage source and data interfaces for transmission of Data to recipients outside the combat missile.
  • the new combat missile controller can contain only the same software components as the controllers of the other combat missiles equipped. By parameterizing the software component that is assigned to the new mission component, the software component can be made ready for operation.
  • each combat missile has the same mounting frame, which carries the control means.
  • a uniform control means can thus be easily installed. If each combat missile has the same cabling from an interface to the control means to several mission components, in particular with the same hardware interfaces as plugs, a mounting of the combat missiles can be facilitated.
  • Fig. 1 shows a combat missile 2, which is designed as a ground-to-ground defense missile, on a trajectory 4, which is guided by a starting device 6 to a destination point 8 through a landscape 10.
  • the launcher 6 is a truck with a mobile launcher into which a modular rocket insert with a plurality of combat missiles 2 is inserted.
  • the target point 8 is that location in the room at which the combat missile 2 is expected to hit its target 12, which is in the shown embodiment is an armored vehicle to be fought by the combat missile 2.
  • the combat missile 2 can just as well be any missile that is to fly from a starting point to a predicted meeting point 8 with a destination.
  • a fire command, the target coordinates of the meeting point 8 and further mission data are given by a fire control system 14 to the launcher 6 or the combat missile 2, which in Fig. 1 is schematically indicated by a house.
  • Fig. 2 shows the combat missile 2 in an enlarged and schematic representation.
  • the combat missile 2 comprises in its indicated hull a rocket motor 16, an action insert 18 with a data means 20, a control means 22 which is connected to a data memory 24, a seeker 26 and a hood 28, the transparent dome 30 during the approach to the Target 12 protects.
  • the control means 22 and the data memory 24 are installed in a mounting frame in the fuselage.
  • the control means 22 can control the flight of the combat missile 2.
  • the rocket motor 16, the seeker head 26 and the control system 32 also contain a corresponding data means 20.
  • the components rocket motor 16, seeker head 26, active insert 18 and the control system 32 are generally referred to as mission components.
  • Each of the data means 20 contains type data of the mission component to which it is assigned or included.
  • the type data may include a type designation and operational data of the corresponding mission component.
  • the combat missile 2 is modular. It comprises a plurality of component groups, in this embodiment four, each having a plurality of mission components, wherein from each component group at least one mission component is installed in the combat missile.
  • a family of missiles can be created in which each combat missile of the family contains a base and mission components, the base being the same in all combat missiles of the family, and the mission components being assorted differently.
  • the base consists of the control means, which may be a management computer with control software, and which may have an inertial measuring unit, a GPS receiver, a power supply, a data link and electrical or logical interface to a starting device.
  • the remaining components of the combat missiles can be assigned to the individual mission components.
  • Combat missiles of this family can be used by different platforms against ground, sea or air targets, can be used over different ranges, can contain different warheads, thus active inserts, and dispose of different steering strategies and target approaches.
  • the "B” group of rocket motors includes a solid fuel engine, a jelly engine, and a multi-stage engine, these three types of engines again being in different sizes in the family, but omitted from illustration.
  • the group “C” Wirkladept are included. Shown are a small shaped active body, eg against vehicles, a large shaped active body, eg for the penetration of buildings, a non-lethal body, eg with sensors, and a large active body with several small penetrators.
  • the group of seekers is labeled "D" and includes an IR seeker head with cooled image processing for detecting and tracking air targets, a multi-color IR seeker head with cooled image processing for detecting ground targets Seeker head with a semi-active laser and a dummy seeker, which is actually only a nose of the nose and is used when no seeker head is needed, for example, in very well-grounded ground targets, if a pure coordinate approach provides sufficient security.
  • a variety of different combat missiles can be produced modular. While the simplest variant of a combat missile uses a single-stage solid state propulsion engine of conventional design, a steerable jet engine is used to combat long-range targets or combat modes with target overflight, target identification, and subsequent assault. Likewise, a simple variant of the Zielsuchsensorik exist in a semi-active laser seeker head, while it should also give more sophisticated variants with image-processing seekers in different spectral ranges for air and ground targets. For reasons of clarity, individual representations of different combat missiles can be dispensed with, since the variety of variants of the missile family already comprises the components Fig. 3 becomes visible.
  • the illustrated component spectrum is just one embodiment.
  • the range of different mission components is even greater when considering modern warheads with programmable effects. If necessary, not all theoretically possible combinations are tactically meaningful. Nevertheless, it should be generally assumed that all mission components of the various groups can be combined.
  • FIG Fig. 4 An embodiment of a base is shown in FIG Fig. 4 shown. It forms the control means 22 for all combat missiles 2 of the family. It contains a plurality of hardware components 36-44, which of course can also be equipped with own software, and a software module 46 with several software components 48.
  • the hardware components 36-44 are a GPS receiver 36, an inertial measurement unit 38 for location and position determination in space , a processor unit 40 with one or more processors for data processing, a bidirectional data link 42 and a power supply 44.
  • the control means 22 is equipped with interfaces 49: an interface 49 to the GPS antenna, one to the uplink antenna and an interface for communication with external units outside the combat missile 2, eg with the fire control 14th
  • the software components 48 are programmed so that each software component 48 has a basic version, e.g. can be adapted by parameterization to all members of a component group. In this way, the control means can be configured for all possible or useful component combinations.
  • all functions are stored for all members of the component group and can each be activated by a call.
  • there is a flight controller for each missile group A which is adapted to the payload to be transported.
  • the missile family expediently has a uniform transport and starburst container which forms the interface to the starting device.
  • step 52 the rocket insert with, for example, 4 x 4 containers, in each of which a combat missile 2 is stored, loaded into the launcher of the launcher 6.
  • the type of combat missile 2 so that it is a combat missile 2 of the modular family system, can be reported to the fire control system 14, for example, when connecting the rocket insert to the launcher, as known by the type of missile deployment and the type of combat missile 2 is.
  • the detection of the missile deployment and thus the nature of the combat missile 2 can be done by specified hardware, for example by the nature of a data connector for data transmission, from the nature of the starting device 6 can already detect the type of missile deployment.
  • the combat missiles are supplied with electrical voltage in step 54.
  • the control means 22 of the combat missile 2 automatically moves up in step 56 and in step 58, via the data bus 51, retrieves the type data of the mission components 50 from their data means, e.g. Type designations.
  • the control means 22 compares the type data in step 60 with the recognition data stored in the data memory 24 and identifies the mission component, e.g. For example, a plurality of designations of different mission components 50 are stored in the data memory 24 so that the control means 22 recognizes the types of the mission components 50 on the basis of the designation read or received by the data means 20.
  • control means can now parameterize the corresponding software components (step 62) so that they are prepared for the control of the special existing mission components 50.
  • control means 22 logs on to the fire control system 14 with the name of the active insert 18 (step 64).
  • the type of combat missile 2 and the exact name of the active element 18 are thus known to the fire control system 14.
  • all the mission components 50 are known to the control means 22 after the identification 60, so that the composition of the mission components 50 in the combat missile 2 can be forwarded to the fire control system 14.
  • an alignment of the mission components 50 actually used in the missile deployment such as active missions 18, seekers, engines, etc. of the multiple combat missiles 2 with the data of the launching device 6 for Missile deployment in step 66.
  • the launching device 6, or its control unit can be informed, which mission components 50 are present in the combat missiles 2 of the rocket insert.
  • control means 22 it can also be checked whether the software in the control means 22 has a planned degree of actuality. If this is not the case, an update 68 of the software can take place, for example, by the control unit of the starting device 6 or by the fire control system 14.
  • step 70 the control means 22 parameterizes an algorithm of an external control unit of the fire control system 14 using data from the mission components 50, such as the action insert 18, so that the control unit can generate mission commands to perform the mission.
  • step 72 the target coordinates of the target point 8 are transmitted from the fire control system 14 to the control means 22 of the combat missile 2 and, if appropriate, a target weather report and further data or mission commands.
  • the control means 22 calculates in step 74 an angular position of the launcher, which is advantageous for the launching of the combat missile 2 in the direction of the target point 8.
  • the angular position is a two-dimensional vector of an azimuth angle and an elevation angle.
  • the angular position depends on the type of mission of the combat missile 2 and this in turn depends on the type of active use, so that when calculating the angular position of the type of active use is taken into account.
  • the uncertainties may be indicated in an uncertainty or uncertainty around the nominal trajectory within which the combat missile 2 will fly with a given probability.
  • the probability of mission success also includes determining whether the mission with the launching angle is even allowable, that is, feasible at all or under given conditions. Feasibility depends on the type of active power 18, such as its weight, and on terminal conditions required by the active power, such as approach direction to the target 12 and / or minimum terminal speed, and the like. These data are taken into account in the calculation of the probability of mission success.
  • the mission parameters are communicated to the fire control system 14 by the control means 22 and this determines the Go or NoGo for the combat missile 2. For example, the fire control system 14 checks whether the trajectory meets all overflight conditions and whether each point within the uncertainty hose can be flown without collision, e.g. when flying over a ridge.
  • the launcher 6 or its launcher drives the launch direction in step 80. Subsequently, a start of the combat missile 2 from the launcher 6 in step 82 and a control of the flight of the combat missile 2 in step 84 to a release of the active use 18th
  • the control of the combat missile 2 by the control means 22 is, of course, adapted to the mission components 50 present in the combat missile, so that the control steps are carried out in dependence on the composition of the mission components 50.
  • the composition of the mission components 50 e.g. an aircraft trajectory depending on the existing engine, the wing structure, the type of active use, the weight of the combat missile, including the size of the active use, and other sizes more.
  • a completely new mission component 50 can in principle also be integrated into a combat missile which was still unknown when the software module 46 was created. It is only to pay attention to the compatibility with the software modules 46 and in particular the corresponding software component 48.
  • the corresponding software component can also be adapted to the previously unknown mission component 50 so that it can control the operation of the mission component 50 , If a compatible design of the new mission component 50 is not possible, only the corresponding, ie associated software component can be renewed and integrated into the software module 46, so that this process is also associated with relatively little effort.

Claims (14)

  1. Procédé de commande d'un missile de combat (2), lequel contient une mémoire de données (24), un moyen de commande (22) et un composant de mission (50), selon lequel le moyen de commande (22) commande le composant de mission (50) pendant un vol du missile de combat (2),
    la mémoire de données (24) contenant des données de reconnaissance à propos d'une pluralité de composants de mission (50) différents et le moyen de commande (22) chargeant des données de type depuis le composant de mission (50), identifiant le type du composant de mission (50) à l'aide des données de reconnaissance et des données de type et exécutant des étapes de commande en fonction du type du composant de mission (50).
  2. Procédé selon la revendication 1, caractérisé en ce que le missile de combat (2) contient au moins un composant de mission (50) du groupe moteur-fusée (B), charge effective (C), tête chercheuse (D), structure de fuselage et d'ailes (A).
  3. Procédé selon la revendication 1 ou 2, caractérisé en ce que le moyen de commande (22) sélectionne des données à l'aide des données de type du composant de mission (50) et communique celles-ci à une unité de commande externe en dehors du missile de combat (2) et paramètre un algorithme de l'unité de commande externe à l'aide des données.
  4. Procédé selon l'une des revendications précédentes, caractérisé en ce que des données de mission sont communiquées au moyen de commande (22) et le moyen de commande (22) calcule des données de vol du missile de combat (2) à partir des données de mission.
  5. Procédé selon la revendication 4, caractérisé en ce que les données de vol contiennent une trajectoire de vol vers une cible (12) prédéfinie.
  6. Procédé selon l'une des revendications précédentes, caractérisé en ce que le moyen de commande (22) charge depuis la mémoire de données (24) des données de type de plusieurs composants de mission (50) regroupés dans le missile de combat (2), identifie leurs types à l'aide des données de reconnaissance et des données de type et exécute des étapes de commande en fonction de la composition des composants de mission (50).
  7. Procédé selon l'une des revendications précédentes, caractérisé en ce que le moyen de commande (22) contient pour chaque composant de mission un composant logiciel (48), paramètre celui-ci conformément aux données de type et commande le composant de mission (50) avec le composant logiciel (48) paramétré.
  8. Procédé selon la revendication 7, caractérisé en ce que le moyen de commande (22) contient au moins un composant logiciel (48) du groupe composant de navigation, commande de déroulement de mission, composant de traitement d'image, régulateur de vol.
  9. Missile de combat (2) comprenant un fuselage, lequel contient une mémoire de données (24), un composant de mission (50) et un moyen de commande (22), lequel est préparé pour commander le composant de mission (50) pendant un vol,
    le moyen de commande (22) étant connecté de manière signalétique avec la mémoire de données (24), caractérisé en ce que la mémoire de données contient des données de reconnaissance à propos d'une pluralité de composants de mission (50) différents et le moyen de commande (22) est préparé pour charger des données de type depuis le composant de mission (50), pour identifier le type du composant de mission (50) et pour exécuter des étapes de commande en fonction du type du composant de mission (50).
  10. Missile de combat selon la revendication 9, caractérisé par une pluralité de composants de mission (50) qui sont reliés avec le moyen de commande (22) par le biais d'un bus de données (51).
  11. Système constitué de plusieurs missiles de combat (2) selon la revendication 9 ou 10, lesquels contiennent respectivement des composants de mission (50) différents, caractérisé en ce que les moyens de commande (22) de tous les missiles de combat (2) sont équipés du même matériel et des mêmes composants logiciels (48).
  12. Système selon la revendication 11, caractérisé par un missile de combat supplémentaire (2) comprenant un nouveau composant de mission (50) qui n'est présent dans aucun des autres missiles de combat (2), son moyen de commande (22) étant équipé exclusivement des mêmes composants logiciels (48) que les moyens de commande (22) des autres missiles de combat (2) et un composant logiciel (48) associé au nouveau composant de mission (50) étant rendu opérationnel par un paramétrage du moyen de commande (22).
  13. Système selon la revendication 11 ou 12, caractérisé en ce que chaque missile de combat (2) dispose du même cadre de montage qui porte le moyen de commande.
  14. Système selon l'une des revendications 11 à 13, caractérisé en ce que chaque missile de combat (2) dispose du même câblage du moyen de commande (22) à plusieurs composants de mission (50) par le biais d'une interface.
EP11005432.7A 2010-07-08 2011-07-02 Procédé de commande d'une munition aérienne Revoked EP2405233B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102010026428 2010-07-08
DE102010052202A DE102010052202A1 (de) 2010-07-08 2010-11-24 Verfahren zum Steuern eines Gefechtsflugkörpers

Publications (3)

Publication Number Publication Date
EP2405233A2 EP2405233A2 (fr) 2012-01-11
EP2405233A3 EP2405233A3 (fr) 2014-06-25
EP2405233B1 true EP2405233B1 (fr) 2015-02-11

Family

ID=44763678

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11005432.7A Revoked EP2405233B1 (fr) 2010-07-08 2011-07-02 Procédé de commande d'une munition aérienne

Country Status (3)

Country Link
EP (1) EP2405233B1 (fr)
DE (1) DE102010052202A1 (fr)
IL (1) IL213934A (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102015012970A1 (de) 2015-10-07 2017-04-13 Mbda Deutschland Gmbh Funktionsorientierter und rekonfigurierbarer Flugkörper
CN112824820A (zh) * 2019-11-21 2021-05-21 北京恒星箭翔科技有限公司 一种40毫米火箭筒用反低小慢目标防空导弹系统及拦截方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102015013349B4 (de) * 2015-10-15 2023-05-17 Mbda Deutschland Gmbh Verfahren zum Betreiben eines Waffensystems
DE102017105565A1 (de) * 2017-03-15 2018-09-20 Rheinmetall Waffe Munition Gmbh Munitions- und Logistikkonzept für insbesondere Artilleriegeschosse

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2272047B (en) * 1989-12-14 1994-07-27 British Aerospace Stand-off weapons
US7905182B2 (en) * 2005-06-02 2011-03-15 Raytheon Company Multi-mode modular projectile
US7506587B1 (en) * 2007-02-20 2009-03-24 The United States Of Americas As Represented By The Secretary Of The Navy Modular projectile system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102015012970A1 (de) 2015-10-07 2017-04-13 Mbda Deutschland Gmbh Funktionsorientierter und rekonfigurierbarer Flugkörper
CN112824820A (zh) * 2019-11-21 2021-05-21 北京恒星箭翔科技有限公司 一种40毫米火箭筒用反低小慢目标防空导弹系统及拦截方法

Also Published As

Publication number Publication date
IL213934A0 (en) 2011-12-01
IL213934A (en) 2014-12-31
EP2405233A2 (fr) 2012-01-11
DE102010052202A1 (de) 2012-01-12
EP2405233A3 (fr) 2014-06-25

Similar Documents

Publication Publication Date Title
DE19740888C2 (de) Verfahren zum autonomen Lenken eines drallstabilisierten Artilleriegeschosses und autonom gelenktes Artilleriegeschoß zur Durchführung des Verfahrens
DE2904749A1 (de) Flugkoerper nach art einer drohne
EP1090263B1 (fr) Procede pour combattre a distance des cibles proches du sol et/ou sur le sol
EP2405233B1 (fr) Procédé de commande d'une munition aérienne
EP2482026B1 (fr) Procédé de défense contre l'attaque d'un missile
EP2594891B1 (fr) Procédé destiné à repousser une fusée balistique se rapprochant en volant et système d'interception
DE102015015938A1 (de) Autonome, unbemannte Fluggeräte zur Begleitung, Eskortierung und Absicherung von Lutffahrzeugen wie Starr- und Drehflügler
EP1674818B1 (fr) Missile
EP3931087A1 (fr) Drone et procédé de lutte contre des cibles
DE4029898C2 (fr)
DE3013405A1 (de) Verfahren zum vermeiden des nachrichtens von abschussgeraeten fuer ballistische flugkoerper
DE2522927C2 (de) System zur taeuschung, ablenkung und vernichtung von lenkwaffen
DE102014005300A1 (de) Waffenträger zur Anbringung von zumindest einem unbemannten Flugkörper an einem Trägerluftfahrzeug, Waffensystem und Luftfahrzeug
DE102011089584B4 (de) Waffensystem, insbesondere Verfahren zur effektiven Bekämpfung von Schiffszielen
EP1612504B1 (fr) Tête militaire pour munition d'artillerie
EP0384965A2 (fr) Sous-projectile avec ailettes stabilisatrices
EP3376154B1 (fr) Procédé de protection d'un missile de croisière
EP2080981B1 (fr) Missile sans équipage
DE102019109360A1 (de) Inventionssystem zur Abwehr von RAM-Zielen und/oder UAVs sowie Verfahren zur Abwehr von RAM-Zielen und/oder UAVs
EP0187900B1 (fr) Avion non équipé pour la lutte contre cibles terrestres
DE60121139T2 (de) Vorrichtung zum schutz einer zone gegen feindliche bedrohung
DE102013006812B4 (de) Lenkflugkörper sowie Wirksystem, umfassend den Lenkflugkörper
DE102017002262B4 (de) Verfahren zum Verteidigen eines U-Boots gegen einen Angriff durch einen unter Wasser befindlichen Sprengkörper
DE3303888A1 (de) Anordung zur zielerfassung und identitizierung fuer gepanzerte kampffahrzeuge
DE102004040253A1 (de) Modulares Aufklärungs- und/oder Kampfsystem für Wasserfahrzeuge, insbesondere für Unterwasserfahrzeuge

Legal Events

Date Code Title Description
AK Designated contracting states

Kind code of ref document: A2

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

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

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

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

RIC1 Information provided on ipc code assigned before grant

Ipc: F42B 15/01 20060101AFI20140521BHEP

17P Request for examination filed

Effective date: 20140527

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

INTG Intention to grant announced

Effective date: 20141008

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

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: AT

Ref legal event code: REF

Ref document number: 710064

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150315

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502011005840

Country of ref document: DE

Effective date: 20150326

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20150211

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 5

REG Reference to a national code

Ref country code: NO

Ref legal event code: T2

Effective date: 20150211

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20150211

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: 20150211

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: 20150211

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: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20150211

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: 20150611

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: 20150211

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: 20150512

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: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20150211

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: 20150211

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: 20150211

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: 20150211

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: 20150211

REG Reference to a national code

Ref country code: DE

Ref legal event code: R026

Ref document number: 502011005840

Country of ref document: DE

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

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: 20150211

26 Opposition filed

Opponent name: MBDA DEUTSCHLAND GMBH

Effective date: 20151111

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

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: 20150211

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: 20150211

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150702

R26 Opposition filed (corrected)

Opponent name: MBDA DEUTSCHLAND GMBH

Effective date: 20151111

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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: 20150731

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150731

PLAF Information modified related to communication of a notice of opposition and request to file observations + time limit

Free format text: ORIGINAL CODE: EPIDOSCOBS2

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150702

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 502011005840

Country of ref document: DE

Owner name: DIEHL DEFENCE GMBH & CO. KG, DE

Free format text: FORMER OWNER: DIEHL BGT DEFENCE GMBH & CO. KG, 88662 UEBERLINGEN, DE

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: 20150211

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: DIEHL DEFENCE GMBH & CO. KG

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: 20110702

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: 20150211

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: 20150211

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: 20150211

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

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: 20150731

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 710064

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160702

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160702

APBM Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNO

APBP Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2O

APAH Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNO

APBQ Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3O

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20150211

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: 20150211

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20150211

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20200630

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200723

Year of fee payment: 10

Ref country code: GB

Payment date: 20200727

Year of fee payment: 10

Ref country code: NO

Payment date: 20200723

Year of fee payment: 10

Ref country code: DE

Payment date: 20200916

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20200724

Year of fee payment: 10

Ref country code: SE

Payment date: 20200727

Year of fee payment: 10

REG Reference to a national code

Ref country code: DE

Ref legal event code: R064

Ref document number: 502011005840

Country of ref document: DE

Ref country code: DE

Ref legal event code: R103

Ref document number: 502011005840

Country of ref document: DE

APBU Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9O

RDAF Communication despatched that patent is revoked

Free format text: ORIGINAL CODE: EPIDOSNREV1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: PATENT REVOKED

RDAG Patent revoked

Free format text: ORIGINAL CODE: 0009271

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: PATENT REVOKED

REG Reference to a national code

Ref country code: FI

Ref legal event code: MGE

27W Patent revoked

Effective date: 20210708

GBPR Gb: patent revoked under art. 102 of the ep convention designating the uk as contracting state

Effective date: 20210708

REG Reference to a national code

Ref country code: AT

Ref legal event code: MA03

Ref document number: 710064

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210708

REG Reference to a national code

Ref country code: SE

Ref legal event code: ECNC

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 NON-PAYMENT OF DUE FEES

Effective date: 20210702