EP3007152B1 - Système et procédé permettant de déterminer des moments OOOI d'un aéronef - Google Patents
Système et procédé permettant de déterminer des moments OOOI d'un aéronef Download PDFInfo
- Publication number
- EP3007152B1 EP3007152B1 EP14187838.9A EP14187838A EP3007152B1 EP 3007152 B1 EP3007152 B1 EP 3007152B1 EP 14187838 A EP14187838 A EP 14187838A EP 3007152 B1 EP3007152 B1 EP 3007152B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- aircraft
- coordinates
- data
- altitude
- close
- 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 75
- 238000012545 processing Methods 0.000 claims description 24
- 230000003247 decreasing effect Effects 0.000 claims 4
- 238000012795 verification Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010006 flight Effects 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000033001 locomotion Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 229920006395 saturated elastomer Polymers 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0004—Transmission of traffic-related information to or from an aircraft
- G08G5/0013—Transmission of traffic-related information to or from an aircraft with a ground station
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0017—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information
- G08G5/0026—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information located on the ground
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0073—Surveillance aids
- G08G5/0082—Surveillance aids for monitoring traffic from a ground station
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/06—Traffic control systems for aircraft, e.g. air-traffic control [ATC] for control when on the ground
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0047—Navigation or guidance aids for a single aircraft
- G08G5/0065—Navigation or guidance aids for a single aircraft for taking-off
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/06—Traffic control systems for aircraft, e.g. air-traffic control [ATC] for control when on the ground
- G08G5/065—Navigation or guidance aids, e.g. for taxiing or rolling
Definitions
- the invention relates to a system to determine the times of an aircraft to touch the runway, to park at a parking position, to leave a parking position and to take off from the runway.
- Transponders are usually used to identify aircrafts in air traffic control radar and are usually used to avoid collisions between aircrafts.
- the Secondary Surveillance Radar (SSR) depends on an embedded transponder which replies to interrogations of the secondary radar.
- the interrogation mode of a transponder is the format of a sequence of pulses, referred to as a code used to determine detailed information from the aircraft. There are different types of interrogation modes: Modes 1 to 5 are reserved for military use whereas Modes A, B, C, D and S are dedicated to civilian use.
- Modes A and C are developed for airframe identification and altitude reporting and this is still widely used in air traffic control and management of air space.
- ATCRBS Air Traffic Control Radar Beacon System
- FRUIT False Replies Uncorrelated In Time
- Mode S technology was developed in the seventies and was widely deployed in the eighties. The advantages of Mode S technology over Mode A and C is that it is addressable, more accurate and reliable and that it can operate with greater capacity.
- a transponder which receives a valid Mode S discrete interrogation replies 128 ⁇ s after reception. The reply is transmitted on 1090 MHz carrier with 56 bit or 112 bit Pulse Positioning Modulation (PPM).
- PPM Pulse Positioning Modulation
- Mode-S uses a monopulse SSR, as in Modes A and C, but it has an increased accuracy.
- Each Mode S interrogation includes an International Civil Aeronautics Organization (ICAO) 24-bit aircraft address, which corresponds to the registration number of the aircraft as a 24-bit parity check for validation. In basic Mode S surveillance, the information is limited to altitude reporting, basic airframe information and aircraft identification.
- IICAO International Civil Aeronautics Organization
- ADS-B Automatic Dependent Surveillance-Broadcast
- GNSS Global Navigation Satellite Systems
- 1090ES Extended Squitter
- This modification allows to send 112 bits messages which include the position of the aircraft calculated by the GNSS system and eventually to receive them.
- SSR Global Navigation Satellite Systems
- the mode (A, C or S) of the reply is then decoded and the information is demodulated within each mode. Since most of commercial aircrafts are already equipped with transponders, the 1090ES is a very cheap solution for these aircrafts.
- ASDE-X uses data which come different types of radars, sensors and transponders. The merging of all these data allows the ASDE-X to determine the position of aircraft and to identify aircraft and vehicles on the airport surfaces, as well as determine aircraft approaching the airport.
- One of the reasons is to evaluate performance of an air carrier, required by Eurocontrol, the FAA etc.
- the data used to evaluate the performance include "OOOI" data which corresponds to the operations of an aircraft: O ut of the stand, O ff the ground, O n the ground, and I nto the stand.
- This data along with airline schedules allow for the calculation of route times, stand arrival time delay, stand delay, taxi times etc. for every flight.
- Another reason is to improve ground operations such as baggage handling, refuelling of air carriers. Late arriving flights may also imply a new stand assignment which drastically complicates the organization of ground operations.
- Planning and staffing of airlines are however planned according to scheduled times and it is therefore important to have realistic Scheduled Times of Departure (STD) and Scheduled Times of Arrival (STA). Realistic STD and STA are also important for passengers in order to meet their expectations.
- STD Scheduled Times of Departure
- OOOI times are significant because these times are used as the basis of predictions and in calculation of delays. For these and other reasons it is important that OOOI data have sufficient completeness and accuracy.
- ACARS Aircraft Communications Addressing and Reporting System
- ACARS Aircraft Communications Addressing and Reporting System
- the main function of ACARS is related to the detection of the major flight phases of an aircraft, the OOOI operations.
- OOOI operations are automatically detected using sensors.
- 'Wheels "out" of the stand' corresponds to the time an aircraft pushes back from the stand and is measured when the parking brake is released, with the associated change in brake pressure. It corresponds to the Actual Time of Departure (ATD).
- ATTD Actual Time of Departure
- 'Wheels "off" the runway' corresponds to the time an aircraft takes-off.
- DGS Docking Guidance System
- transponder data allows a simple method to accurately determine the in-time of an aircraft. No additional hardware is necessary for the implementation of the proposed method.
- the transponder data from the aircraft further includes flight data including data indicating if the flight is an arrival flight or a departure flight
- the method of determining the in-time further comprises the step of verifying if said flight is an arrival flight, and determining the actual processing time as the in-time of the aircraft if the flight is also an arrival flight.
- the transponder data is a Mode S message.
- a Mode S message comprises the registration number of the aircraft and preferably its position from the GNSS system.
- the combination of the mode-S message data and a database allows an accurate computation of the OOOI times of the aircraft.
- the method further comprises the step of comparing said parsed transponder data with data available in a flight data database, and adding data from the flight data database to said parsed transponder data to create more complete flight data.
- the method further comprises the step of verifying if the aircraft is on a runway, and determining the actual processing time as the in-time of the aircraft if the aircraft is also not on the runway.
- the method further comprises determining an on-time of an aircraft prior to determining said in-time thereof.
- said parking coordinates are stand coordinates or parking spot coordinates.
- This method allows the determination of the on-time of an aircraft without the need of new special hardware. Only data available in a database and the transponder data are necessary for determining the on-time.
- the method further comprises the step of verifying if a previous on-time is available for said aircraft and determining an actual processing time as the on-time of the aircraft if there is also no on-time available for said aircraft.
- the on-time is only valid if no previous on-time has been previously calculated.
- This method allows the determination of the out-time of an aircraft without the need of new special hardware. Only data available in a database and the transponder data are necessary for determining the out-time.
- This method allows the determination of the off-time of an aircraft without the need of new special hardware. Only data available in a database and the transponder data are necessary for determining the off-time.
- the on-time, the in-time, the out-time and the off-time described above are used to determine the OOOI time of an aircraft as defined in claim 14.
- the method allows a simple and accurate way of determining OOOI times of an aircraft. Also, there is no need to provide new hardware in the aircraft for this accurate computation. This is performed using the already existing hardware on board of the aircraft.
- a system for determining said on-, in-, out- and off-times of an aircraft at an airport is defined in claim 15.
- OOOI time calculation refers to Out of the stand, Off the ground, On the ground and Into the stand.
- the stand is the parking position. It is for example the stand or a parking spot allocated to the aircraft. Therefore, in this description, we refer to this position as the stand position.
- Runway Thresholds are markings across the runway which define the beginning and the end of the space intended for landing and take-off.
- the Mode S transponder messages include the coordinates of the plane calculated by a Global Navigation Satellite System such as the GPS.
- the aircraft are equipped with ADS-B and the Mode S messages include the coordinates of the aircraft.
- the AODB Airport Operation DataBase
- the AODB is a resilient, comprehensive central repository for operational data management activities. It delivers the efficiency of centralized operational database of an airport along with guaranteed, consistent and robust operational performance.
- the AODB stores, distributes and manages all real-time flight data, in addition to all aeronautical and non-aeronautical service data, and it quickly transforms this data into accurate financial figures.
- the AODB is a multi-tiered application. Interaction between the user interface and service layers, which is designed by utilizing Service Oriented Architecture (SOA), is event-based.
- SOA Service Oriented Architecture
- the AODB user interface is designed as a RIA, (Rich Internet Application) it takes advantage of cross browser and platform compatibility in addition to taking advantage of the web deployment model's traditional benefits.
- the AODB is configurable depending on the operation and size of the airport.
- the AODB is equally well suited for small, medium-sized or large airports. According to the needs of the customer, it can be downsized or dedicated "cost effective" solutions can be tailored.
- the AODB further includes an interface capable of receiving Mode S messages and interpreting them.
- the definition of "in-time” used in this application is the time that the aircraft arrives in its parking position.
- the parking position can be a stand position or a parking spot allocated to the aircraft. It should be understood that throughout the application, where stand or parking spot is used, the one can be replaced by the other.
- out-time used in this application is the time that the aircraft leaves its parking position.
- off-time used in this application is the time that the aircraft is no longer in contact with the runway.
- on-time used in this application is the time that the aircraft is touching the runway.
- Figure 1 illustrates a flow chart of a system that is used to determine OOOI times based on transponder Mode S messages. The method is executed for every Mode S message received.
- the transponder of an aircraft sends a Mode S message every few seconds.
- the time interval between two consecutive Mode S messages of an aircraft is lower than 5 seconds.
- the transponder of the aircraft replies to signals from a Secondary Surveillance Radar 100 by transmitting the Mode S message 102.
- This Mode S message includes the aircraft identification number, the pressure altitude, the GPS position and the speed of the aircraft.
- the signal corresponding to the Mode S message is sent to an SBS receiver (antenna) 104 which decodes the transponder signal from the aircraft, demodulates it and converts the analog signal to a digital message 106.
- the SBS receiver then sends this digital message to an application, part of a control system, responsible of reading, parsing and processing the digital data 108. In this control system, another application is responsible for listening to specific ports which receive the converted digital messages.
- the messages are received byte by byte and the application is able to distinguish each message and its corresponding source.
- the digital signal corresponding to the analog Mode S message is analysed.
- the corresponding data is inserted into a predefined flight data structure which comprises the following data fields:
- This flight data structure is updated and completed during the process, some fields can be empty.
- this flight data structure is subsequently compared to the data already available in the AODB 114 from different integrated sources.
- the system can use different search criteria as the flight date and time, the airline and the flight ID, the registration number of the aircraft, the call-sign, etc.
- the new flight data is, in step 113, added to the database 114. Additional flight data can be added to the AODB 114 from other sources of information such as AFTN, airline-ground handling systems, slot.
- step 115 The flight data structure is checked and updated if necessary depending on the Mode S transponder message data. The most important data being the identification number because it allows identification of the aircraft.
- Step 130 consists in checking whether the aircraft is already on the runway. This step is performed with a comparison of its coordinates, available in the flight data structure, to the runway coordinates. If the aircraft is not on the runway (arrow 131), the next step 132 consists in determining if the aircraft is in the stand position and if its speed has recently changed. A negative reply 133 leads to perform the "Log message” step 134, which consists in saving an appropriate message, to be used later on. In case of a positive reply 135, the method verifies at step 136 if the flight is an arrival flight. If it is (arrow 137), the system performs the "in" time determination method 200.
- the system performs the "out” time determination method 300.
- the sequence of operations used to determine these "in” and “out” times are described in more detail later in this description.
- step 130 checks if the current flight is an arrival flight. In case of a positive reply 143, the system performs the "on" time determination method 400. In case of a negative reply 144, the system performs the "off" time determination method 500. The sequence of operations used to determine these "on” and “off” times are described in more detail later in this description.
- Figure 2 illustrates the method to determine the "in" time 200.
- the method includes the following steps and starts after step 136 of Figure 1 .
- All the data of the aircraft are available in the flight data structure.
- Step 220 consists in getting aircraft coordinates and checking whether the speed is close to zero. Theoretically, the speed should be zero. However, sometimes transponders may send incorrect speed values. These incorrect values are found by comparing the speed values of the previous and the next messages.
- Each airport has its own regulation regarding the speed limit for which a plane is assumed to be in its parking position. Usually, this speed limit value is around 3 knots.
- the system logs the available data in step 225 for further use. If the speed is close to zero, the method compares the aircraft coordinates to the stand coordinates in step 230. If the coordinates do not lie in a range corresponding to the stand coordinates, the method stops and performs logs the data in step 235 for further use. While the coordinates lie in the range of the stand coordinates, the next step consists in checking whether a previous "in” time has been saved in step 240. While no previous "in” time is available, the current time corresponds to an actual "in” time and the "in” time is set to the current time. The stand coordinates which correspond to the current GPS coordinates of the aircraft saved in the flight data structure are also set as "stand" coordinates.
- step 245 the "in” time and the "stand” coordinates are set.
- the method verifies if there is a previous "out” time with step 250. While there is no previous “out” time, the method sets the “out” time to the current time with step 255. If a previous "out” time has been saved, the method verifies if the speed of the aircraft was higher than zero in the previous data with the verification step 260. If it is not the case, the plane is about to leave and the "out” time can be updated with step 265. However, if the aircraft was moving in the previous data, it implies that the plane has just arrived in the gate and a new "in” time can be saved. The coordinates of the stand position are also stored from the available GPS data saved in the flight data structure. The "in” time and the stand coordinates are saved in step 270.
- Figure 3 illustrates the flow chart corresponding to the processing of the "out" time. Pilots may turn the transponders off. However, they should be turned on before leaving the stand. Once a transponder is turned on, it starts sending messages.
- the method actually compares the coordinates of the aircraft with the stand coordinates and checks the speed. If the speed is different from zero and/or the coordinates are different from those of the allocated stand, it means that the aircraft is about to leave the stand.
- the method includes the following steps and starts after the arrival flight verification 136 step of Figure 1 . In this case, the flight is a departure flight.
- the aircraft coordinates are available and the speed is available from the transponder Mode S message..
- the first step consists in checking whether the speed of the aircraft is close to zero with step 320.
- step 325 the data is logged in step 325 for further use. If it is moving slowly, the method verifies whether the aircraft coordinates lie in the range corresponding to the allocated stand. If they do not, the next step is to log the data 335 for further use. If they do, the method checks if the speed in the previous data is higher than zero in step 340. If it is not, the method performs the step of updating the "out" time in step 345. If the plane was previously moving, the method performs the step of adding a new "in” time as well as a new stand coordinate in step 350.
- Figure 4 illustrates the sequence of events used to determine the "on” time 400.
- the aircraft coordinates are compared with coordinates corresponding to the runway thresholds coordinates. If the aircraft coordinates (longitude and latitude) lie in this zone and if the altitude corresponds to that of the runway, the current time is stored as an actual "on” time candidate. For validation, the method continues to verify whether or not the next messages support this "on" time candidate. When the below conditions are met, then the time becomes a real "on" time:
- the current flight can be either a training flight, that pilots may train to approach the runway, or it could be any technical problem which has lead the pilot to cancel landing.
- the data is stored as "on" approach time for further reporting in AODB.
- the method includes the following steps and starts after the arrival flight verification step 142.
- the first condition concerns the altitude of the aircraft and the method verifies if the altitude of the aircraft is close to the altitude of the runway in step 420. If it is not, the method stops by storing the flight data structure in memory and performs the step of logging the data in step 425. If the altitude of the aircraft is close to that of the runway, the method continues with step 430 where the coordinates of the aircraft are compared to the runway thresholds coordinates. While the coordinates of the aircraft do not lie in a range corresponding to the runway thresholds coordinates, the method stops and the flight data structure is logged in step 435.
- Step 445 also comprises the setting of the thresholds ("Set “on” time & threshold”). If the actual "on” time is not valid, the method needs to verify whether the speed of the aircraft is increasing with the condition 450. If it is not, the method stops and logs the data in step 455. If the speed of the aircraft is increasing, it means that the plane has taken off again and the method stops with the status "Set Touch and Go” 460.
- Figure 5 illustrates the sequence of operations for determining the "off" time 500.
- step 520 the coordinates of the aircraft are compared with the runway thresholds coordinates. If the aircraft coordinates (longitude and latitude) lie in the corresponding range of the runway coordinates, it means that the aircraft is ready for take-off and the system continues to monitor the movements of the aircraft until it passes the take-off zone on the runway and the altitude of the aircraft becomes higher than the altitude of the runway. Once the above condition is met, the time is saved as actual take-off time.
- the method includes the following steps and starts after the arrival flight verification 142 step.
- the flight is a departure flight and the first verification step of the method concerns the comparison of the coordinates of the aircraft with respect to the runway thresholds coordinates (step 520). If the position of the aircraft is not in the zone of the runway thresholds coordinates, the method stops with logging the data in step 525. Otherwise, the method continues with an altitude check in step 530: is the altitude of the aircraft increasing with respect to previous data? A negative reply leads the method to stop and to log data in step 535. However, a positive reply means that the aircraft is taking off. Subsequently, step 540 verifies whether there is a previous "off" time set. With a negative reply, the method can save the actual time as the "off" time in step 545. With a positive reply, the method stops and logs the data in step 550.
- step 600 is dedicated to collect the four times acquired in steps 200, 300, 400, 500.
- Step 700 accurately calculates the OOOI time of an aircraft from the "in”, “out”, “on” and “off” times.
Landscapes
- Engineering & Computer Science (AREA)
- Aviation & Aerospace Engineering (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Traffic Control Systems (AREA)
- Radar Systems Or Details Thereof (AREA)
Claims (15)
- Procédé de détermination d'un temps d'arrivée en stationnement d'un aéronef, comprenant les étapes consistant à :a) recevoir des données de transpondeur provenant dudit aéronef, lesdites données de transpondeur incluant au moins des données de coordonnées, des données d'altitude et des données de vitesse dudit aéronef ;b) analyser lesdits données de transpondeur ;c) vérifier si des données de vitesse sont proches de zéro ;d) vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles dans une base de données ;e) vérifier si lesdites données de vitesse dudit aéronef diminuent ; etf) déterminer un temps de traitement réel en tant que dit temps d'arrivée en stationnement de l'aéronef si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, lesdites données de vitesse sont à zéro et une vitesse précédente est supérieure à zéro.
- Procédé selon la revendication 1, dans lequel lesdites données de transpondeur provenant dudit aéronef incluent en outre des données de vol incluant des données indiquant si le vol est un vol d'arrivée ou un vol de départ, ledit procédé comprenant en outre l'étape consistant à vérifier si ledit vol est un vol d'arrivée, et à déterminer ledit temps de traitement réel en tant que dit temps d'arrivée en stationnement de l'aéronef si ledit vol est également un vol d'arrivée.
- Procédé selon la revendication 1 ou 2, dans lequel lesdites données de transpondeur sont un message Mode S.
- Procédé selon l'une quelconque des revendications précédentes, comprenant en outre l'étape de comparaison desdites données de transpondeur analysées à des données disponibles dans une base de données de données de vol, et d'ajout de données depuis ladite base de données de vol auxdites données de transpondeur analysées pour créer des données de vol plus complètes.
- Procédé selon l'une quelconque des revendications précédentes, dans lequel ledit procédé comprend en outre l'étape consistant à vérifier si ledit aéronef est sur une piste de décollage, et à déterminer ledit temps de traitement réel en tant que dit temps d'arrivée en stationnement dudit aéronef si ledit aéronef n'est également pas sur la piste de décollage.
- Procédé selon l'une quelconque des revendications précédentes, comprenant en outre, avant l'étape c), les étapes consistant à :vérifier si ladite altitude d'aéronef est proche de l'altitude d'aéroport disponible dans ladite base de données ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles dans ladite base de données ; etdéterminer un temps de traitement réel en tant que dit temps de touchée dudit aéronef si ladite altitude d'aéronef est proche de ladite altitude d'aéroport et lesdites coordonnées d'aéronef sont proches desdites données de piste de décollage.
- Procédé selon la revendication 6, comprenant en outre l'étape consistant à vérifier si un temps de touchée précédent est disponible pour ledit aéronef et déterminer ledit temps de traitement réel en tant que dit temps de touchée de l'aéronef s'il n'y a également aucun temps de touchée disponible pour ledit aéronef.
- Système configuré pour déterminer un temps d'arrivée en stationnement d'un aéronef, comprenant :un récepteur configuré pour recevoir des données de transpondeur provenant dudit aéronef, lesdites données de transpondeur incluant au moins des données de coordonnées, des données d'altitude et des données de vitesse dudit aéronef ;une base de données configurée pour stocker au moins des données d'altitude d'aéroport, des données de coordonnées de piste de décollage et des données de coordonnées de stationnement ;un processeur configuré pour analyser lesdites données de transpondeur, vérifier si des données de vitesse sont proches de zéro, vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles depuis ladite base de données, vérifier si lesdites données de vitesse dudit aéronef diminuent, et générer, en tant que dit temps d'arrivée en stationnement, un temps de traitement réel si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, lesdites données de vitesse sont à zéro, et une vitesse précédente est supérieure à zéro ; etune mémoire configurée pour stocker ledit temps d'arrivée en stationnement dudit aéronef.
- Système selon la revendication 8, dans lequel ledit processeur est en outre configuré pour vérifier si ladite altitude d'aéronef est proche de l'altitude d'aéroport disponible à partir de ladite base de données, vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles à partir de ladite base de données, et générer, en tant que dit temps d'entrée en contact avec la piste d'atterrissage, un temps de traitement réel si ladite altitude d'aéronef est proche de ladite altitude d'aéroport et si lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage ; et
ladite mémoire est en outre configurée pour stocker ledit temps d'entrée en contact avec la piste d'atterrissage dudit aéronef. - Procédé de détermination d'un temps de sortie de stationnement d'un aéronef au niveau d'un aéroport, comprenant les étapes consistant à :i) recevoir des données de transpondeur provenant dudit aéronef, lesdites données de transpondeur incluant au moins des données de coordonnées et des données de vitesse dudit aéronef ;ii) analyser lesdites données de transpondeur ;iii) vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles dans une base de données ;iv) vérifier si lesdites données de vitesse dudit aéronef augmentent ; etv) déterminer un temps de traitement réel en tant que dit temps de sortie de stationnement dudit aéronef au niveau dudit aéroport si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, la vitesse augmente et une vitesse précédente est de zéro.
- Procédé selon la revendication 10, comprenant en outre, après l'étape v), les étapes consistant à :vérifier si ladite altitude d'aéronef est proche d'une altitude d'aéroport disponible à partir de ladite base de données ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles à partir de ladite base de données ;vérifier si une altitude d'aéronef précédente est plus basse qu'une altitude d'aéronef actuelle ; etdéterminer un temps de traitement réel en tant que dit temps de fin de contact avec la piste d'atterrissage dudit aéronef si ladite altitude d'aéronef est proche de ladite altitude d'aéroport, lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage, et si ladite altitude d'aéronef précédente est plus basse que ladite altitude d'aéronef actuelle.
- Système configuré pour déterminer un temps de sortie de stationnement d'un aéronef au niveau d'un aéroport, comprenant :un récepteur configuré pour recevoir des données de transpondeur provenant d'un aéronef, lesdites données de transpondeur incluant au moins des données de coordonnées et des données de vitesse dudit aéronef ;une base de données configurée pour stocker au moins des données d'altitude d'aéroport, des données de coordonnées de piste de décollage et des données de coordonnées de stationnement ;un processeur configuré pour analyser lesdites données de transpondeur, vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles à partir de ladite base de données, vérifier si lesdites données de vitesse dudit aéronef augmentent, et générer, en tant que dit temps de sortie de stationnement, un temps de traitement réel si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, la vitesse augmente et une vitesse précédente est à zéro ; etune mémoire configurée pour stocker ledit temps de sortie de stationnement dudit aéronef au niveau dudit aéroport.
- Système selon la revendication 12, dans lequel ledit processeur est en outre configuré pour vérifier si ladite altitude d'aéronef est proche d'une altitude d'aéroport disponible à partir de ladite base de données, vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles à partir de ladite base de données, vérifier si une altitude d'aéronef précédente est plus basse qu'une altitude d'aéronef actuelle et générer, en tant que dit temps de fin de contact avec la piste d'atterrissage, un temps de traitement réel si ladite altitude d'aéronef est proche de ladite altitude d'aéroport, lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage et ladite altitude d'aéronef précédente est plus basse que ladite altitude d'aéronef actuelle ; et
ladite mémoire est en outre configurée pour stocker ledit temps de fin de contact avec la piste d'atterrissage dudit aéronef au niveau dudit aéroport. - Procédé de détermination de temps d'arrivée en stationnement, temps de sortie de stationnement, temps d'entrée en contact avec la piste d'atterrissage et temps de fin de contact avec la piste d'atterrissage, OOOI, d'un aéronef au niveau d'un aéroport, le procédé comprenant les étapes consistant à :recevoir des données de transpondeur provenant dudit aéronef, lesdites données de transpondeur incluant au moins des données de coordonnées, des données d'altitude et des données de vitesse dudit aéronef ;analyser lesdites données de transpondeur ;vérifier si ladite altitude d'aéronef est proche de l'altitude d'aéroport disponible dans une base de données ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles à partir de ladite base de données ;déterminer un temps de traitement réel en tant que dit temps d'entrée en contact avec la piste d'atterrissage dudit aéronef si ladite altitude d'aéronef est proche de ladite altitude d'aéroport et lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage ;vérifier si des données de vitesse sont proches de zéro ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles à partir de ladite base de données ;vérifier si lesdites données de vitesse dudit aéronef diminuent ;déterminer un temps de traitement réel en tant que dit temps d'arrivée en stationnement de l'aéronef si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, lesdites données de vitesse sont à zéro et une vitesse précédente est supérieure à zéro ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles à partir de ladite base de données ;vérifier si lesdites données de vitesse dudit aéronef augmentent ;déterminer un temps de traitement réel en tant que dit temps de sortie de stationnement dudit aéronef si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, la vitesse augmente et une vitesse précédente est de zéro ;vérifier si ladite altitude d'aéronef est proche d'une altitude d'aéroport disponible à partir de ladite base de données ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles à partir de ladite base de données ;vérifier si une altitude d'aéronef précédente est plus basse qu'une altitude d'aéronef actuelle ; etdéterminer un temps de traitement réel en tant que dit temps de fin de contact avec la piste d'atterrissage dudit aéronef si ladite altitude d'aéronef est proche de ladite altitude d'aéronef, lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage, et si ladite altitude d'aéronef précédente est plus basse que ladite altitude d'aéronef actuelle.
- Système configuré pour déterminer des temps d'arrivée en stationnement, temps de sortie de stationnement, temps d'entrée en contact avec la piste d'atterrissage et temps de fin de contact avec la piste d'atterrissage, OOOI, d'un aéronef au niveau d'un aéroport, comprenant :un récepteur configuré pour recevoir des données de transpondeur provenant dudit aéronef, lesdites données de transpondeur incluant au moins des données de coordonnées, des données d'altitude et des données de vitesse dudit aéronef ;une base de données configurée pour stocker au moins des données d'altitude d'aéroport, des données de coordonnées de piste de décollage et des données de coordonnées de stationnement ;un processeur configuré pour :analyser lesdites données de transpondeur ;vérifier si ladite altitude d'aéronef est proche de l'altitude d'aéroport disponible à partir de ladite base de données ;vérifier si lesdites données d'aéronef sont proches de coordonnées de piste de décollage disponibles à partie de ladite base de données ;déterminer un temps de traitement réel en tant que dit temps d'entrée en contact avec la piste d'atterrissage dudit aéronef si ladite altitude d'aéronef est proche de ladite altitude d'aéroport et lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage ;vérifier si des données de vitesse sont proches de zéro ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles à partir de ladite base de données ;vérifier si lesdites données de vitesse dudit aéronef diminuent ;déterminer un temps de traitement réel en tant que dit temps d'arrivée en stationnement de l'aéronef si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, lesdites données de vitesse sont à zéro, et une vitesse précédente est supérieure à zéro ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de stationnement disponibles à partir de ladite base de données ;vérifier si lesdites données de vitesse dudit aéronef augmentent ;déterminer un temps de traitement réel en tant que dit temps de sortie de stationnement dudit aéronef si lesdites coordonnées d'aéronef sont proches desdites coordonnées de stationnement, la vitesse augmente, et une vitesse précédente est à zéro ;vérifier si ladite altitude d'aéronef est proche d'une altitude d'aéroport disponible à partir de ladite base de données ;vérifier si lesdites coordonnées d'aéronef sont proches de coordonnées de piste de décollage disponibles à partir de ladite base de données ;vérifier si une altitude d'aéronef précédente est plus basse qu'une altitude d'aéronef actuelle ; etdéterminer un temps de traitement réel en tant que dit temps de fin de contact avec la piste d'atterrissage dudit aéronef si ladite altitude d'aéronef est proche de ladite altitude d'aéroport, lesdites coordonnées d'aéronef sont proches desdites coordonnées de piste de décollage, et si ladite altitude d'aéronef précédente est plus basse que ladite altitude d'aéronef actuelle ; etune mémoire configurée pour stocker lesdits temps d'entrée en contact avec la piste d'atterrissage, temps d'arrivée en stationnement, temps de sortie de stationnement, et temps de fin de contact avec la piste d'atterrissage dudit aéronef au niveau dudit aéroport.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14187838.9A EP3007152B1 (fr) | 2014-10-06 | 2014-10-06 | Système et procédé permettant de déterminer des moments OOOI d'un aéronef |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14187838.9A EP3007152B1 (fr) | 2014-10-06 | 2014-10-06 | Système et procédé permettant de déterminer des moments OOOI d'un aéronef |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3007152A1 EP3007152A1 (fr) | 2016-04-13 |
EP3007152B1 true EP3007152B1 (fr) | 2019-04-24 |
Family
ID=51726348
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP14187838.9A Active EP3007152B1 (fr) | 2014-10-06 | 2014-10-06 | Système et procédé permettant de déterminer des moments OOOI d'un aéronef |
Country Status (1)
Country | Link |
---|---|
EP (1) | EP3007152B1 (fr) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR3091521B1 (fr) | 2019-01-08 | 2021-05-07 | Airbus | Procédé et système de génération de données opérationnelles relatives à des déplacements d’aéronef dans une infrastructure aéroportuaire |
US20230391471A1 (en) * | 2022-06-03 | 2023-12-07 | The Boeing Company | Aircraft touch-and-go detection |
-
2014
- 2014-10-06 EP EP14187838.9A patent/EP3007152B1/fr active Active
Non-Patent Citations (1)
Title |
---|
JERRY D WELCH ET AL: "A01-37185 USING SURFACE SURVEILLANCE TO HELP REDUCE TAXI DELAYS*", 9 September 2001 (2001-09-09), XP055391743, Retrieved from the Internet <URL:https://pdfs.semanticscholar.org/ca45/bb77258a13a0f02d00775e51d2dfcbed6884.pdf> [retrieved on 20170718] * |
Also Published As
Publication number | Publication date |
---|---|
EP3007152A1 (fr) | 2016-04-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3336580B1 (fr) | Procédé et station de base ads-b destinés à valider des informations de position contenues dans un message de squitter étendu en mode s (ads-b) à partir d'un aéronef | |
US9842506B2 (en) | Systems and methods for conflict detection using dynamic thresholds | |
EP3159869B1 (fr) | Système de gestion des données de manoeuvre d'un aéronef | |
US6809679B2 (en) | Surveillance system and method for aircraft approach and landing | |
US11727818B1 (en) | Aircraft surface state event track system and method | |
CN101793961B (zh) | 具有减少等待时间的多传感器跟踪处理方法 | |
US20180107227A1 (en) | Revised speed advisory for an aircraft during flight based on holding time | |
US11869373B1 (en) | Autonomous and automatic, predictive aircraft surface state event track system and corresponding methods | |
López-Lago et al. | Present and future of air navigation: PBN operations and supporting technologies | |
EP3007152B1 (fr) | Système et procédé permettant de déterminer des moments OOOI d'un aéronef | |
CN110709913B (zh) | 机场处的控制系统 | |
Chung et al. | A 1090 extended squitter automatic dependent surveillance-Broadcast (ADS-B) reception model for air-traffic-management simulations | |
Ali | A safety assessment framework for automatic dependent surveillance broadcast (ads-b) and its potential impact on aviation safety | |
JP4597992B2 (ja) | 航空機の離着陸時刻の測定方法並びにその方法を用いた航空機の離着陸管理方法 | |
Young | UAS ground-based detect and avoid capability | |
Eftekari | Preliminary Assessment of Surveillance Alternatives for Upper Class E Traffic Management (ETM) | |
EP3489709B1 (fr) | Procédé et système d'attribution d'adresses mode s dynamique | |
Bojda | Air traffic surveillance method using an existing network of DME navigation system | |
Wood | Multilateration system development history and performance at Dallas/Ft. Worth Airport | |
Castaldo et al. | Improved Location/ldentification of Aircraft/Ground Vehicles on Airport Movement Areas: Results of FAA Trials | |
Young et al. | Establishing baseline requirements for a UAS ground-based sense and avoid system | |
Mavrakis et al. | [Poster] Improving light aviation safety through traffic sharing and OpenSky ADS-B feed | |
Kazhan et al. | Peculiarities of Pre-processing of ADS-B Data for Aircraft Noise Modeling and Measurement During Specific Stages of LTO Cycle | |
CN115331487A (zh) | 引导车的航班识别以及智能引导系统 | |
Castaldo et al. | Positive identification of aircraft on surface movement areas: results of FAA trials |
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 |
|
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 |
|
17P | Request for examination filed |
Effective date: 20161005 |
|
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 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G08G 5/06 20060101ALN20181017BHEP Ipc: G08G 5/00 20060101AFI20181017BHEP |
|
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: 20181205 |
|
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 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1125048 Country of ref document: AT Kind code of ref document: T Effective date: 20190515 Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602014045232 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20190424 |
|
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: 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: 20190424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20190424 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: 20190424 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: 20190824 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: 20190424 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: 20190424 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: 20190724 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: 20190424 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: 20190424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20190725 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: 20190424 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: 20190724 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: 20190424 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: 20190424 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1125048 Country of ref document: AT Kind code of ref document: T Effective date: 20190424 |
|
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: 20190824 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602014045232 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20190424 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: 20190424 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: 20190424 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: 20190424 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: 20190424 Ref country code: AT 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: 20190424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT 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: 20190424 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: 20190424 |
|
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: 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: 20190424 |
|
26N | No opposition filed |
Effective date: 20200127 |
|
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: 20190424 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: 20190424 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
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: 20191006 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191031 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191031 |
|
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: 20191006 |
|
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: 20190424 |
|
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: 20141006 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: 20190424 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20210922 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: BE Payment date: 20210922 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20211027 Year of fee payment: 8 |
|
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: 20190424 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602014045232 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20221031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20221031 Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230503 |
|
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: 20221031 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231001 Year of fee payment: 10 |