EP3789970B1 - Verfahren für eine fahrzeugbezogene identitätsvalidierung - Google Patents

Verfahren für eine fahrzeugbezogene identitätsvalidierung Download PDF

Info

Publication number
EP3789970B1
EP3789970B1 EP19195619.2A EP19195619A EP3789970B1 EP 3789970 B1 EP3789970 B1 EP 3789970B1 EP 19195619 A EP19195619 A EP 19195619A EP 3789970 B1 EP3789970 B1 EP 3789970B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
signal
data
presumed
designated
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
Application number
EP19195619.2A
Other languages
English (en)
French (fr)
Other versions
EP3789970A1 (de
Inventor
John Newman
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.)
Audi AG
Original Assignee
Audi AG
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
Application filed by Audi AG filed Critical Audi AG
Priority to EP19195619.2A priority Critical patent/EP3789970B1/de
Publication of EP3789970A1 publication Critical patent/EP3789970A1/de
Application granted granted Critical
Publication of EP3789970B1 publication Critical patent/EP3789970B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit

Definitions

  • the invention is concerned with a method for a vehicle related identity validation.
  • Document US 2002/0072963 A1 discloses a system for collecting and/or disseminating information in relation to traffic. With this system, information about individual persons and/or vehicles can be collected and checked on reliability in such a way that yet sufficient protection can be offered against illegitimate tracing of individual persons and/or vehicles. Hereby, an odometer reading can be verified with help of reliable information supplied from the outside world via a transmitter.
  • Document US 2011/0187513 A1 discloses a method for remotely controlling equipment of a vehicle such as an engine start electronic control unit of the vehicle or a window opening/closing electronic control unit.
  • the corresponding remote-control request is selected by a user of the vehicle and transmitted to the vehicle via a control center or server.
  • Document US 2014/0334684 A1 discloses a system and a method to identify a vehicle and to determine a characterizing feature of the vehicle.
  • the system can therefore comprise a license plate reader and a camera.
  • Document US 2018/0082500 A1 discloses a vehicle accident reporting system and a method that include a request sent to a mobile device, wherein the request asks an owner or operator of the mobile device to photograph a license plate of another vehicle or to record a video of the accident.
  • the inventive method is based on the understanding that in some cases the value of gaining unauthorized access to a vehicle and/or its vehicle data is high. Therefore, there is a considerable interest in cracking an encryption that is used to prevent unauthorized access to the vehicle and/or its vehicle data. Under such circumstances, it may be desirable to have an additional and redundant validation mechanism to be able to perform a reliable identity validation of vehicle related data.
  • Such an additional redundant validation mechanism can be achieved by making use of a signal transmitted to the vehicle, modifying the transmitted signal in a vehicle or vehicle part specific manner to create a vehicle related signal that could be measured by an off-vehicle device, transmitting a signal externally comprising a request for measuring the vehicle related signal to the off-vehicle device, and then measuring the externally observable vehicle related signal by the off-vehicle device.
  • the inventive method for vehicle related identity validation comprises receiving a vehicle related identity validation request signal associated with a designated vehicle.
  • receives the validation request signal that one party, e.g., a user of a vehicle selling platform, is interested in performing an identity validation in connection with a specific vehicle.
  • This specific vehicle is referred to as the designated vehicle.
  • the received vehicle related identity validation request signal contains data characterizing the designated vehicle whose identity shall be validated with the help of the inventive method.
  • the request signal can furthermore specify a particular vehicle part of the designated vehicle, e.g., a specific battery that is comprised by the designated vehicle.
  • a vehicle identification number could be used to identify the vehicle itself and/or the vehicle that is supposed to contain the vehicle part in question. If, however, it is expected that, for example, a specific battery as vehicle part is comprised by a specific vehicle, this information could be comprised by the identity validation request signal. In general, it should be first decided which vehicle related identity is supposed to be validated and afterwards a respective identity validations request signal should be generated and provided. However, details on the identity of the designated vehicle relating to the object of the vehicle related identity validation request should be comprised by the vehicle related identity validation request signal.
  • the vehicle related identity validation request signal is received by an off-vehicle server unit.
  • the off-vehicle server unit is, for example, designed as a computer such as a network host.
  • the off-vehicle server unit that received the vehicle identity validation request signal then transmits a specific control signal to the vehicle that is presumed to be the designated vehicle.
  • the specific control signal contains control data for at least one vehicle component of the designated vehicle.
  • the at least one vehicle component is for example a headlight of the vehicle that can be dimmed or brightened up according to lightning control specifications given by the control data.
  • the specific control signal contains, additionally to the control data, identification data.
  • the identification data are customized for the designated vehicle and/or a vehicle component whose identity validation is requested according to the received vehicle identity validation request signal.
  • the identification data comprise for example a digital code that can only be decrypted by a component of the designated vehicle and/or the vehicle component whose identity validation is requested according to the received vehicle identity validation request signal.
  • the server unit creates and then transmits a specific signal, i.e., the specific control signal to a vehicle that comprises data with which it is possible to modify for example the intensity of the vehicle headlights.
  • This modification is supposed to be only temporary, meaning that no permanent modification of the respective vehicle component of the designated vehicle is intended based on the control data, such as permanent dimming of the vehicle headlights.
  • the specific control signal can, for example, be transmitted via a wireless communication connection between the server unit and the presumed vehicle.
  • the wireless communication connection can be established via a wireless local network such as a wireless local area network (WLAN), or via a mobile data network based on mobile radio standard Long Term Evolution (LTE) or Fifth Generation (5G).
  • WLAN wireless local area network
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • the vehicle to which the specific control signal is transmitted is referred to as the presumed vehicle because in order to validate the vehicle identity it is in the beginning only assumed that a certain vehicle is the designated vehicle.
  • the presumed vehicle is thus the vehicle that is allegedly the designated vehicle.
  • the vehicle to which the specific control signal is transmitted is hence referred to as the presumed vehicle.
  • the presumed vehicle receives the specific control signal. Therefore, the presumed vehicle comprises a communication unit that is capable of receiving the specific control signal from the server unit. Subsequently, it is verified if the identification data of the received specific control signal match with stored identification data stored in the presumed vehicle.
  • This verification step can be performed by a control unit of the presumed vehicle.
  • the control unit is connected with a data storage unit of the presumed vehicle in which the identification data known to the vehicle are stored. But the specific control signal that is received by the presumed vehicle is at first convoluted. This means that the specific control signal is converted into a format in which it is a combined signal comprising the control data as well as the identification data, wherein the identification data is unique to the designated vehicle.
  • the data unique to the designated vehicle i.e., the identification data
  • the identification data can only be decrypted if corresponding stored identification data is available to the control unit.
  • the intensity of the headlights of the presumed vehicle is dimmed by a specific percentage for a specific time interval.
  • the headlights of the designated vehicle could each be dimmed by 20 percent for a duration of three seconds. If however the transmitted identification data and the stored identification data are no match, the control unit cannot access the control data contained by the specific control signal and therefore the at least one vehicle component, e.g., the headlights of the vehicle are not operated according to the control signal.
  • An off-vehicle sensor device can now detect a sensor signal characterizing the operation of the at least one vehicle component of the presumed vehicle according to the control data.
  • the off-vehicle sensor device can be designed as a traffic camera. This means that the sensor signal could be given as a video feed of a road on which the presumed vehicles is driving. In case the at least one vehicle component of the presumed vehicle is operated according to the control signal, this operation should be verifiable by evaluating the detected sensor signal.
  • the next step of the method therefore comprises evaluating the detected sensor signal to validate if the at least one vehicle component has been operated according to the transmitted control data.
  • the evaluation step it is determined whether the headlights of the presumed vehicle were dimmed according to the control data or if no change in brightness of the headlights of the vehicle can be recognized according to the evaluated sensor signal.
  • the evaluation step is typically performed by the off-vehicle server unit. This means that the detected sensor signal is after its detection transmitted from the off-vehicle sensor device to the off-vehicle server unit.
  • the server unit confirms the requested vehicle related identity validation. If the requested vehicle related identity validation is confirmed, it is achieved that the presumed vehicle is identified as the designated vehicle. Confirming the requested vehicle related identity validation can be done by storing confirmation data in the server unit that can serve as a certificate for the vehicle related identity associated with the presumed vehicle.
  • the certificate can be advantageous to have for the vehicle selling platform that first sent out the request signal to the server unit in order to gain prove for a potential customers that a certain vehicle is actually the designated vehicle, wherein details regarding equipment and condition of the designated vehicle are known previous to the request signal. Now the known details are furthermore known to be connected to the presumed vehicle since the identity validation was successful for the presumed vehicle.
  • the server unit can connect to the off-vehicle sensor device and request transmission of the video feed of a particular traffic camera. It can afterwards evaluate the measured intensity of the vehicle headlights over time and match the thereby calculated light intensity value to the expected light intensity value according to the control signal.
  • the designated vehicle is expected to implement the control data by operating the vehicle headlights.
  • the identification data transmitted within the specific control signal would not match with the stored identification data stored in the vehicle resulting in a lack of proof for operating the at least one vehicle component according to the control signal.
  • the advantage of the described method is that it can reliably allow for the validation of vehicles, vehicle parts and/or vehicle data. By doing so one can build confidence into a service provided by the vehicle selling platform or another respective platform, wherein the service confirms the vehicle related identity validation. By detecting the operation of the at least one vehicle component with an off-vehicle sensor device a manipulation of the validation result from within the vehicle can be ruled out. This increases trustworthiness and reliability of the described method and especially of the results of the described validation process.
  • the control data comprise at least one activation data element.
  • the activation data element characterizes a specific time and a specific location at which the at least one vehicle component of the presumed vehicle is operated. It is therefore possible to predefine a point in time in the future as well as a particular place where operating the at least one vehicle component according to the control signal takes place. This allows, for example, choosing a location in a predefined surrounding area of a specific off-vehicle sensor device, for example the traffic camera located at a specific location alongside a particular road. Under consideration of details on a current driving route of the vehicle, it is hence possible to estimate an approximate arrival time within the surveillance area of the specific traffic camera meaning that it is known at which specific time the vehicle reaches the specific location.
  • the specific control signal comprises the information on time and location at which the presumed vehicle is supposed to be in the surveillance area of the specific traffic camera. At that time and location the operation of the at least one vehicle component of the designated vehicle is performed. If the right vehicle received the specific control signal and was able to access the control data, the expected operation actually happens at the expected point in time and location and can be detected by the specific off-vehicle sensor device.
  • the specific time and specific location is preferably determined based on a current vehicle location, the known driving route of the vehicle and the availability of off-vehicle sensor devices, such as one or multiple public traffic camera with an available video feed.
  • the invention also comprises embodiments that provide features which afford additional technical advantages.
  • the vehicle related identity validation request signal requests identity validation of a vehicle, a vehicle part and/or vehicle data.
  • the vehicle part whose identity validation is requested can be for example a particular battery or another exchangeable vehicle part that is integrated in the vehicle.
  • the vehicle data could be a current odometer reading value, i.e., a mileage in kilometers or miles of a specific vehicle.
  • the identification data of the specific control signal fit the stored identification data associated with the vehicle, the vehicle part and/or the vehicle data.
  • the specific control signal is created in a way that the identification data that is added to the specific control signal contains the specific identification data that is correlated to the stored identification data that is related to the vehicle related object or data comprised within the validation request signal.
  • a potential buyer of a vehicle is interested in making sure that the vehicle that is expected to be the offered vehicle shown at a vehicle selling platform comprises a specific battery, that is for example relatively new and therefore in good condition.
  • the potential buyer then sends a corresponding vehicle related identity validation request signal to the server unit.
  • the sent vehicle identity validation request signal comprises the information, that the identity that is supposed to be validated refers to a specific battery comprised by a specific vehicle.
  • the specific control signal that is then created contains identification data for the specific vehicle itself but also for the specific battery that is presumably integrated into the specific vehicle. Therefore the operation according to the control data takes place if both the battery related identification data match corresponding stored identification data as well as the identification data associated with the designated vehicle itself matches stored identification data associated with the vehicle itself in the presumed vehicle.
  • the identification data of the specific control signal can contain multiple identification data elements each associated with either the designated vehicle itself, a particular vehicle part, specific vehicle data, and/or vehicle data elements. This allows for a nuanced and accurate identity validation of the vehicle related object or data which are of interest due to the received vehicle related validation request signal. This makes the described method particularly effective and furthermore guarantees a reliable result of the method as it is guaranteed that all requested identities are actually validated.
  • An additional embodiment comprises that if the requested vehicle related identity validation is confirmed the location where the operation of the at least one vehicle component was detected is stored in an off-vehicle memory device. Every time the requested vehicle related identity validation is confirmed meaning every time it is detected, that the presumed vehicle was operated according to the transmitted control data of the specific control signal this event is saved as a respective specific data element. In addition to the simple information that the vehicle related identity validation was successful it is therefore furthermore stored where the respective identity validation event took place.
  • the stored data thus allows for tracking a driving route of the designated vehicle if the described method to validate a vehicle related identity is preformed multiple times, preferably continuously, for example every ten minutes or once an hour when the vehicle is in action.
  • the multiple performed identity validations can beneficially support the accuracy of the confirmation of the vehicle, the vehicle part and/or the vehicle data.
  • a total length of a driving distance of the designated vehicle is estimated. By doing so, an approximated odometer reading is calculated for the designated vehicle. It is thus possible to track a distance the designated vehicle has travelled by determining the sum of all distances between the individual locations where the operation of the at least one vehicle component was detected. This is possible due to the fact that all these different locations are stored in the off-vehicle memory device. Additionally it is possible to also store driving routes prepared by a navigation system of the designated vehicle in the off-vehicle memory device if those driving route details are transmitted to the off-vehicle memory device.
  • the reason for the approximation of the odometer reading value of the designated vehicle is that this value is often manipulated with, e.g., by resetting a vehicle electric control unit that record the odometer reading value.
  • the advantage of the described method to estimate the odometer reading value is that the designated vehicle has been proven physically localized at each specific stored location so that the driven distance of the vehicle can be estimated reliably. Since data provided by the off-vehicle sensor device is available for the public, it is easily possible to verify a given odometer reading of a vehicle if the individual locations where the operation of the at least one vehicle component of this vehicle was detected is stored in the off-vehicle memory device.
  • the estimation of the total lengths of the driving distance of the designated vehicle is typically not performed in the designated vehicle itself due to fear of manipulation of data but by the off-vehicle server unit. This reduces the risk of tempering with individual steps of the method but also guarantees a reliable estimated odometer reading value, e.g., to convince a potential buyer or seller of the vehicle of the validity its odometer reading value.
  • the received vehicle related identity validation request signal associated with the designated vehicle is sent by a server unit of a vehicle selling platform and/or a manufacturer of the designated vehicle.
  • the vehicle related validation request signal is particularly sent by this server unit as a reaction to a validation request made by a potential buyer and/or a potential seller of the designated vehicle.
  • the validation request can be made for example via activating a predefined request option of an application on a mobile communication device or a website that is respectively accessed by the potential buyer and/or the potential seller.
  • a potential buyer it can be interesting to have proof that, for example, a particular battery is actually built into a vehicle that the designated potential buyer would like to purchase.
  • the potential seller it is advantageous to have a confirmation of the identity of the vehicle, the vehicle part of the vehicle or the vehicle data he provides to show a potential customer. With help of this proof, the potential customer would trust information about the designated vehicle stated on the vehicle selling platform.
  • the manufacturer of the designated vehicle it can be beneficial to be informed if any manipulations were performed on a vehicle that was produced by the manufacturers, e.g., in order to estimate the vehicle's reselling value on a used-vehicle market.
  • an automatically generated validation request could be transmitted to the server unit or be created by the server unit.
  • a particular automatically generated validation request could be generated after a predetermined time interval and/or for a randomly chosen designated vehicle in order to get an estimation of the general dimension of attempts to manipulate vehicle identity, vehicle part identity and/or vehicle data identity.
  • the specific control signal is transmitted and/or the detected sensor signal is respectively evaluated by an off-vehicle server unit.
  • the specific control signal is created and transmitted to the presumed vehicle by a device that is definitively not positioned within the designated vehicle itself so that the transmittance of the specific control signal is independent from the presumed as well as the designated vehicle.
  • This part of the method is thus independent of potential manipulations of the control unit of the presumed and/or designated vehicle.
  • the verification step during which the detected sensor signals are validated and correlated with the control data of the specific control signal is performed by the off-vehicle server unit. This guarantees a high probability that if the requested vehicle related identity validation is confirmed this result is highly trustworthy and cannot be manipulated by performing manipulation steps on the vehicle, vehicle parts and/or vehicle data.
  • Another embodiments comprises that one or multiple vehicle components of the presumed vehicle are operated in such a way that the operation is physically detectable by the off-vehicle sensor device.
  • any vehicle component or combination of vehicle components could be operated that is designed to be altered so as to be physically detected by a sensors device as off-vehicle sensor device that responds to, for example, an electromagnetic signal, sound, i.e., an acoustic signal, a physical movement of the respective vehicle component or components, and/or a mass of the respective vehicle component or components. Therefore, multiple vehicle components could be operated, particularly an interior or exterior light of the vehicle that sends out an electromagnetic signal. In case a sound is detected by the off-vehicle sensor device, a horn of the vehicle could be operated as vehicle component.
  • the vehicle could be operated according to a specific driving routine so that the resulting physical movement could be detectable.
  • the vehicle could be operated according to the specific driving routine so that the vehicle is at a specific point in time positioned on a specific road segment with an integrated mass sensor as off-vehicle sensor device that then detects the presence of the vehicle.
  • a respective physically detectable operation is performed by the at least one vehicle component according to the control data of the specific control signal. This makes the vehicle related identity validation versatile applicable.
  • another embodiment comprises that as vehicle component of the presumed vehicle at least one of following vehicle components is operated: at least one headlight, at least one rear light, at least one sidelight, at least one vehicle interior light, a light detection and ranging (LIDAR) device, a horn, a communication device with a predefined limited communication range, i.e., a transmitter, a drive system, a brake system, and/or a steering system.
  • the control signal can therefore for example include an operation rule for the vehicle headlights, the vehicle sidelights and/or the rear lights comprising a rapid dimming or rapid brightening of these lights, respectively.
  • a rapid changing of the corresponding headlights, sidelights and/or rear lights e.g., a blinking of the corresponding light for three times in a predefined time interval.
  • changing the intensity of the corresponding lights, particularly the vehicle interior lights, by a predefined percentage for a predefined time duration can be intended as operation.
  • another transmission device can be used for such intensity changes like for example the LIDAR device or the communication device that transmits, for example, a predefined radio signal to a nearby cell tower.
  • sound can be used as an operation, such as the sound of the horn of the vehicle.
  • a particular motion pattern of the vehicle can be introduced by for example changing the speed of a vehicle causing the car to stutter or to temporarily drop speed at a predefined speed dropping rate.
  • Another movement of the vehicle that could be used as specific operation of a vehicle component involves steering the vehicle according to a predefined trajectory routine performed by operating the steering system according to respective control data.
  • the off-vehicle sensor device detects an electromagnetic signal, an acoustic signal, a force signal, an acceleration signal, a deceleration signal and/or a mass signal as sensor signal.
  • electromagnetic signal a signal of a specific wavelength range can be detected, which is for example the wavelength range of ultraviolet light, visible light, infrared light and/or a radio wave. If, for example, at least one light of the vehicle, and/or the LIDAR device are operated, this can be detected as an electromagnetic signal by a respective off-vehicle sensor device.
  • the drive system, the brake system, and/or the steering system are operated, this can be detected as a force signal, an acceleration signal, a deceleration signal and/or a mass signal by a respective off-vehicle sensor device.
  • the sensor device could be a mass sensor positioned in a road segment on which the vehicle can be positioned.
  • the ideal sensor device or even multiple sensor devices can be chosen to detect the operation of the presumed vehicle by detecting at least one of the mentioned signal types as sensor signal. This leads to a particularly diverse applicability of the validation method described.
  • the off-vehicle sensor device at least one of following devices is operated: a camera device, a light detection device, a communication device with a predefined limited communication range, i.e., a receiver, a motion sensor device, and/or an acoustic sensor device. If for example the at least one headlight, the at least one rear light, the LIDAR device, the drive system, the brake system, and/or the steering system are operated, this can be detected by using the camera device, i.e., a traffic camera, as off-vehicle sensor device. If a light detection device is used it is also possible to use for example an infrared or LIDAR device signal to detect the operation of the designated vehicle.
  • a camera device i.e., a traffic camera
  • the communication signal can be detected by a corresponding communication device that has also a limited communication range but is positioned outside of the vehicle as the off-vehicle sensor device.
  • Communication can be done via a wireless technology for short distance data exchange, such as a Bluetooth communication.
  • the motion sensor device is for example included into a road. This sensor is then also designed to detect operations of the drive system, the brake system and/or the steering system of the vehicle that result in a specific driving pattern of the designated vehicle.
  • an acoustic sensor device is used as an off-vehicle device, the horn of the presumed vehicle should be operated or another sound making device of the presumed vehicle, e.g., a multimedia system of the designated vehicle.
  • the ideal sensor device or even multiple sensor devices can be chosen to detect the operation of the presumed vehicle. This also leads to a diverse applicability of the validation method described.
  • the application also discloses a non-claimed vehicle with a control unit and at least one vehicle component that can be operated according to control data of a specific control signal.
  • the vehicle is designed to conduct corresponding steps related to the vehicle of a method as described above.
  • the invention also comprises embodiments of the vehicle that comprise features that correspond to features as they have already been described in connection with the embodiments of the inventive method. For this reason, the corresponding features of the embodiments of the vehicle are not described here again.
  • the vehicle is preferably designed as a motor vehicle, in particular as a passenger vehicle or a truck, or as a bus or a motorcycle.
  • the invention also discloses a system comprising a vehicle as described above, an off-vehicle sensor device as well as an off-vehicle server unit.
  • the off-vehicle server unit is, for example, designed as a computer such as a network host.
  • the system is designed to conduct a method as it was described above.
  • the invention also comprises embodiments of the inventive system that comprise features that correspond to features as they have already been described in connection with the embodiments of the inventive method. For this reason, the corresponding features of the embodiments of the inventive system are not described here again.
  • the invention also provides a processing unit for a server unit and/or a vehicle control unit comprising at least one processor and a data memory coupled to the at least one processor, wherein the processing unit is designed to perform corresponding steps for the server unit and/or the vehicle control unit of an embodiment of the inventive method.
  • the at least one processor may each be based on one of a microprocessor and a microcontroller and an ASIC (application specific integrated circuit).
  • the data memory may comprise computer readable instructions that -when executed by the at least one processor- cause the at least one processor to perform the embodiment of the inventive method.
  • the processing unit may comprise one or more microprocessors and/or one or more microcontrollers. Further, the processing unit may comprise program code that is designed to perform the described method when executed by the processing unit. The program code may be stored in a data storage of the processing unit.
  • the invention also comprises the combinations of the features of the different embodiments.
  • FIG. 1 shows a schematic illustration of a method for vehicle related identity validation.
  • the only Fig. shows different steps S1 to S11 that are performed to validate the identity of a vehicle related item.
  • This method starts once a person 10, who can be a potential buyer and/or a potential seller of a vehicle, makes a validation request 12.
  • the person 10 could, alternatively or additionally, be a vehicle rental company operator, a vehicle fleet operator and/or a vehicle manufacturer.
  • the vehicle manufacturer as person 10 could make a validation request 12 because it intends to offer a warranty certificate for one of the vehicles produced by the vehicle manufacturer.
  • the validation request 12 states that the person 10 is interested in the performance of a vehicle related identity validation.
  • the validation request 12 can be made via a respective application installed on a mobile communication device of the person 10 and/or by using a corresponding application on a website.
  • Providing the validation request 12 and transmitting it to a vehicle selling platform 14 is considered as a pre-step S0.
  • the validation request 12 can be sent to a manufacturer of a vehicle of interest.
  • the vehicle selling platform 14 then sends a vehicle related identity validation request signal 16 that is associated with the designated vehicle to a server unit 18. This is done within step S1.
  • the server unit 18 that is preferably not situated within a vehicle receives the vehicle related identity validation request signal 16 that is based on the validation request 12 made by the person 10 in advance.
  • the server unit 18 then creates a specific control signal 20 for the designated vehicle.
  • the specific control signal 20 comprises control data 22 for at least one vehicle component of the designated vehicle and identification data 24 for the designated vehicle and/or the vehicle component whose identity validation is requested according to the received vehicle related identity validation request signal 16.
  • the server unit 18 transmits the specific control signal 20 in step S2 to the vehicle that is presumed to be the designated vehicle. This vehicle is allegedly the designated vehicle and in the following referred to as the presumed vehicle 26.
  • Presumed vehicle 26 comprises a control unit 28 and a memory device in which stored identification data 30 is stored.
  • the presumed vehicle 26, in particular its control unit 28 receives the specific control signal 20.
  • the control unit 28 verifies if the identification data 24 of the received specific control signal 20 match the stored identification data 30 stored in the presumed vehicle 26.
  • the data transmission that takes place in the vehicle is indicated by dotted lines in the only Fig. Due to verifying if the identification data 24 matches the stored identification data 30 either one of the resulting situations A and B is possible. If the received identification data 24 matches the stored identification data 30, as it is the case in situation A, in a step S5 the at least one vehicle component of the presumed vehicle 26 is operated according to the control data 22.
  • the control unit 28 of the presumed vehicle 26 is unlocked so that a wanted operation of the presumed vehicle 26 can be performed by the control unit 28, wherein this operation is performed according to the control data 22.
  • the operation could be a temporarily dimming of the headlights 32 of the presumed vehicle 26.
  • the headlights 32 could be dimmed by a factor of 10 percent of the usual intensity for in total 3 seconds or for three times of a duration of 1 second each within 10 seconds.
  • the control data 22 comprise at least one activation data element which characterizes a specific time and a specific location at which the at least one vehicle component of the presumed vehicle 26 is operated.
  • the dimming of the headlights 32 of the presumed vehicle 26 therefore takes place at a specific location and presumably also at a specific point in time in the future.
  • an off-vehicle sensor device 34 that is a camera along a road the presumed vehicle 26 is currently driving on, detects a sensor signal 36.
  • the detected sensor signal 36 characterizes the operation of the at least one vehicle component of the presumed vehicle 26 according to the control data 22.
  • the camera as sensor device 34 takes a short video feed of the presumed vehicle 26 while driving on the road while the headlights 32 are dimmed three times for 1 second each within 10 seconds according to the control data 22.
  • a light detection device a communication device with a predefined limited communication range, a motion sensor device and/or an acoustic sensor device could be used for detecting the operation of the at least one component of the presumed vehicle 26.
  • the at least one vehicle component could be at least one rear light, a light detection ranging (LIDAR) device, a horn, a communication device with a predefined limited communication range, a drive system, a brake system and/or a steering system.
  • LIDAR light detection ranging
  • the received identification data 24 does not match the stored identification data 30 stored in the presumed vehicle 26 in situation B.
  • step S7 the sensor signal 36 is transmitted to the server unit 18, particularly to an analysis subunit 38 of the sever unit 18.
  • the next steps S8 to S12 all take place in the server unit 18 and this is indicated by using dashed lines within the only Fig.
  • step S8 the detected and transmitted sensor signal 36 is evaluated. This is done to validate if the at least one vehicle component was operated according to transmitted control data 22. This results again in two possible situations, i.e., in situation A or situation B. In case the headlights 32 were not operated in situation B due to the mismatch of the received control data 24 and the stored control data 30, there is no operation according to the control data 24 that can be observed according to the sensor signal 36 in step S8. This results in a failed identity validation. This means that the presumed vehicle 26 does not seem to be the designated vehicle the person 10 is interested in.
  • step S8 has a positive result. If this is the case, meaning that if the at least one vehicle component was operated according to the control data 22, it is in step S9 confirmed that the requested vehicle related identity validation was successful. If, for example, the person 10 was only interested in finding out if the presumed vehicle 26 is really the designated vehicle of which details on for example total lengths of a driven distance of the vehicle are known, the identity of the presumed vehicle 26 as the designated vehicle is now verified.
  • step S9 some sort of digital certificate 40 is created for the presumed vehicle 26 that states, that the presumed vehicle 26 is the designated vehicle, that a certain vehicle part of the presumed vehicle 26 is actually located within the designated vehicle or that vehicle data received from the presumed vehicle 26 or are stored within the presumed vehicle 26 are valid.
  • the vehicle related identity validation request signal 16 can request identity validation of a vehicle itself, a vehicle part, e.g., a battery, and/or vehicle data.
  • the identification data 24 of the specific control signal 20 fit the stored identification data 30 associated with the vehicle, the vehicle part and/or the vehicle data. Meaning that the specific control signal 20 is designed in a way, that depending on the actual validation request signal 16 the identification data 24 is included into the specific control signal 20 that is necessary to make sure that corresponding stored identification data 30 is stored in the vehicle, wherein the stored identification data 30 can be related to a specific vehicle component, vehicle data and/or the vehicle.
  • step S9 the location, where the operation of the at least one vehicle component has been detected, is stored in an off-vehicle memory device, meaning here the server unit 18.
  • step S10 Once several locations are stored in the off-vehicle memory device for the designated vehicle, it is possible to calculate an estimation of a total lengths of driven distance of the designated vehicle. Thereby an approximated odometer reading value 44 is calculated in step S11.
  • the approximate odometer reading value 44 is thus generated based on multiple sensor signals 36 from different locations described by the stored location data 42 that are combined to calculate the estimation of the total distance the presumed vehicle 26, that has been validated as the designated vehicle, has driven so far. This information referring to the odometer reading value 44 can be included into the certificate 40 in a step S12.
  • transmitting the specific control signal 20, detecting the sensor signal 36, and evaluating the sensor signal 36 is all performed by the off-vehicle server unit 18.
  • a vehicle that is designed to perform the described method comprises the control unit 28 and the at least one vehicle component that can be operated according to the control data 22. In this case these are the headlights of the presumed vehicle 26.
  • the vehicle is designed to conduct the corresponding steps related to the vehicle as described above, meaning steps S3, S4 and S5.
  • the described invention describes a validation of a vehicle related identity through multi-factor authentication of convoluted events.
  • the convoluted events here refer to the combination of the control data 22 with the identification data 24 in the convoluted and therefore combined specific control signal 20.
  • this was exemplarily described in the context of approximating an odometer reading value 44.
  • the described method could be applied to approximate other vehicle data to provide, for example, confidence in one of various vehicle parts and/or vehicle data elements of the vehicle. This could, for example, be achieved by integrating other transmitted control signals over time when performing multi-factor authentication of convoluted events.
  • the verifying procedure performed to check if the identification data 24 and the stored identification data 30 match can, for example, be based on the principle of a transaction authentication number (TAN) method that is typically used for online banking services.
  • TAN transaction authentication number

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)

Claims (10)

  1. Verfahren für eine fahrzeugbezogene Identitätsvalidierung, wobei das Verfahren umfasst:
    - Empfangen eines fahrzeugbezogenen Identitätsvalidierungs-Anforderungssignals (16), das mit einem benannten Fahrzeug verknüpft ist (S1), durch eine fahrzeugexterne Servereinheit (18);
    - Übertragen eines bestimmten Steuersignals (20) an ein Fahrzeug, bei dem es sich vermutlich um das benannte Fahrzeug handelt, wobei die Servereinheit (18) das bestimmte Steuersignal (20) erzeugt und dann überträgt, und das bestimmte Steuersignal (20) Steuerdaten (22) für mindestens eine Fahrzeugkomponente des benannten Fahrzeugs und Identifikationsdaten (24) für das benannte Fahrzeug und/oder eine Fahrzeugkomponente, dessen bzw. deren Identitätsvalidierung dem empfangenen fahrzeugbezogenen Identitätsvalidierungs-Anforderungssignal (16) gemäß angefordert wird, enthält, wobei die Steuerdaten (22) mindestens ein Aktivierungsdatenelement umfassen, das eine bestimmte Zeit und einen bestimmten Ort (42) kennzeichnet, zu der bzw. an dem die mindestens eine Fahrzeugkomponente des vermuteten Fahrzeugs (26) betätigt wird, wobei unter Berücksichtigung von Einzelheiten bezüglich einer aktuellen Fahrtroute des Fahrzeugs eine ungefähre Ankunftszeit in einem Überwachungsbereich einer fahrzeugexternen Sensorvorrichtung (34) geschätzt wird und die bestimmte Zeit und der bestimmte Ort (42) auf Basis eines aktuellen Fahrzeugstandorts, der bekannten Fahrtroute des Fahrzeugs und einer Verfügbarkeit von fahrzeugexternen Sensorvorrichtungen (34) bestimmt wird (S2);
    - Empfangen des bestimmten Steuersignals (20) durch das vermutete Fahrzeug (26) (S3);
    - Überprüfen, ob die Identifikationsdaten (24) aus dem empfangenen bestimmten Steuersignal (20) mit gespeicherten Identifikationsdaten (30), die in dem vermuteten Fahrzeug (26) gespeichert sind, übereinstimmen (S4);
    - nur dann, wenn die empfangenen Identifikationsdaten (24) mit den gespeicherten Identifikationsdaten (30) übereinstimmen, Betätigen der mindestens einen Fahrzeugkomponente des vermuteten Fahrzeugs (26) dem Steuersignal gemäß zu der bestimmten Zeit und an dem bestimmten Ort (S5);
    - Erkennen eines Sensorsignals (36), das die den Steuerdaten (22) gemäße Betätigung der mindestens einen Fahrzeugkomponente des vermuteten Fahrzeugs (26) kennzeichnet, durch die fahrzeugexterne Sensorvorrichtung (34) (S6);
    - Auswerten des erkannten Sensorsignals (36), um zu validieren, ob die mindestens eine Fahrzeugkomponente den übertragenen Steuerdaten (22) gemäß betätigt wurde (S8);
    - wenn die mindestens eine Fahrzeugkomponente den Steuerdaten (22) gemäß betätigt wurde, Bestätigen der angeforderten fahrzeugbezogenen Identitätsvalidierung (S9).
  2. Verfahren nach Anspruch 1, wobei das fahrzeugbezogene Identitätsvalidierungs-Anforderungssignal (16) die Validierung der Identität eines Fahrzeugs, eines Fahrzeugteils und/oder von Fahrzeugdaten anfordert und je nach fahrzeugbezogenem Identitätsvalidierungs-Anforderungssignal (16) die Identifikationsdaten (24) des bestimmten Steuersignals (20) zu den vorbestimmten Identifikationsdaten (30), die mit dem Fahrzeug, dem Fahrzeugteil und/oder den Fahrzeugdaten verknüpft sind, passen.
  3. Verfahren nach einem der vorstehenden Ansprüche, wobei, wenn die angeforderte fahrzeugbezogene Identitätsvalidierung bestätigt wird, der Ort (42), an dem die Betätigung der mindestens einen Fahrzeugkomponente erkannt wurde, in einer fahrzeugexternen Speichervorrichtung gespeichert wird (S10).
  4. Verfahren nach dem vorstehenden Anspruch, wobei, wenn in der fahrzeugexternen Speichervorrichtung mehrere Orte (42) für das benannte Fahrzeug gespeichert sind, eine Gesamtlänge einer Fahrstrecke des benannten Fahrzeugs geschätzt wird, sodass ein ungefährer Kilometerzählerstand (44) berechnet wird (S11).
  5. Verfahren nach einem der vorstehenden Ansprüche, wobei das empfangene fahrzeugbezogene Identitätsvalidierungs-Anforderungssignal (16), das mit dem benannten Fahrzeug verknüpft ist, von einer Servereinheit (18) einer Fahrzeugverkaufsplattform (14) und/oder einem Hersteller des benannten Fahrzeugs gesendet wird, insbesondere in Reaktion auf eine Validierungsanforderung (12), die von einem potentiellen Käufer und/oder einem potentiellen Verkäufer gestellt wird (S0).
  6. Verfahren nach einem der vorstehenden Ansprüche, wobei das erkannte Sensorsignal (36) jeweils von der fahrzeugexternen Servereinheit (18) ausgewertet wird.
  7. Verfahren nach einem der vorstehenden Ansprüche, wobei die mindestens eine Fahrzeugkomponente oder mehrere der Fahrzeugkomponenten des vermuteten Fahrzeugs (26) derart betätigt werden, dass die Betätigung durch die fahrzeugexterne Sensorvorrichtung (34) physikalisch erkannt werden kann.
  8. Verfahren nach einem der vorstehenden Ansprüche, wobei als Fahrzeugkomponente des vermuteten Fahrzeugs (26) mindestens eine der folgenden Komponenten betätigt wird:
    - mindestens ein Scheinwerfer (32);
    - mindestens ein Seitenlicht;
    - mindestens ein Rücklicht;
    - mindestens ein Fahrzeug-Innenraumlicht;
    - eine Lichterkennungs- und Abstandsermittlungsvorrichtung;
    - eine Hupe;
    - eine Kommunikationsvorrichtung mit einer vordefinierten begrenzten Kommunikationsreichweite;
    - ein Antriebssystem;
    - ein Bremssystem; und/oder
    - ein Lenksystem.
  9. Verfahren nach einem der vorstehenden Ansprüche, wobei die fahrzeugexterne Sensorvorrichtung (34) ein elektromagnetisches Signal, ein akustisches Signal, ein Kraftsignal, ein Beschleunigungssignal, ein Verzögerungssignal und/oder ein Massensignal als Sensorsignal (36) erkennt.
  10. Verfahren nach einem der vorstehenden Ansprüche, wobei als fahrzeugexterne Sensorvorrichtung (34) mindestens eine der folgenden Vorrichtungen betätigt wird:
    - eine Kameravorrichtung (34);
    - eine Lichterkennungsvorrichtung;
    - eine Kommunikationsvorrichtung mit einer vordefinierten begrenzten Kommunikationsreichweite;
    - eine Akustiksensorvorrichtung; und/oder
    - eine Bewegungssensorvorrichtung.
EP19195619.2A 2019-09-05 2019-09-05 Verfahren für eine fahrzeugbezogene identitätsvalidierung Active EP3789970B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19195619.2A EP3789970B1 (de) 2019-09-05 2019-09-05 Verfahren für eine fahrzeugbezogene identitätsvalidierung

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP19195619.2A EP3789970B1 (de) 2019-09-05 2019-09-05 Verfahren für eine fahrzeugbezogene identitätsvalidierung

Publications (2)

Publication Number Publication Date
EP3789970A1 EP3789970A1 (de) 2021-03-10
EP3789970B1 true EP3789970B1 (de) 2023-01-18

Family

ID=67875251

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19195619.2A Active EP3789970B1 (de) 2019-09-05 2019-09-05 Verfahren für eine fahrzeugbezogene identitätsvalidierung

Country Status (1)

Country Link
EP (1) EP3789970B1 (de)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152230A1 (zh) * 2023-01-18 2024-07-25 苏州易信安工业技术有限公司 一种点检数据验证方法、装置及系统
CN116307949B (zh) * 2023-05-24 2023-08-22 江西五十铃汽车有限公司 车辆ota组件产线验证方法、设备、介质和程序产品

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NL1011501C2 (nl) 1999-03-09 2000-09-12 Wiebren De Jonge Het Traffic Information & Pricing (TIP) systeem.
JP4507884B2 (ja) * 2005-01-11 2010-07-21 トヨタ自動車株式会社 遠隔制御システム及び遠隔制御装置を備える車両
BR112015003676A2 (pt) * 2012-08-20 2017-07-04 Strimling Jonathan sistema, sistema para previsão de uma identidade de um veículo detectado por múltiplos sensores e método para monitoramento de veículo
US9922471B2 (en) * 2016-05-17 2018-03-20 International Business Machines Corporation Vehicle accident reporting system
WO2019043444A1 (en) * 2017-09-04 2019-03-07 Ebrahimian Ziba SYSTEM AND METHOD FOR MONITORING VEHICLE HISTORY

Also Published As

Publication number Publication date
EP3789970A1 (de) 2021-03-10

Similar Documents

Publication Publication Date Title
US11694481B2 (en) Rental/car-share vehicle access and management system and method
CN111295862B (zh) 用于密码地保证车辆身份的系统和方法
US11782692B2 (en) Transport component acceptance
EP3789970B1 (de) Verfahren für eine fahrzeugbezogene identitätsvalidierung
JP2019524562A (ja) 車両の安全を保証するシステム及び方法
US20220398149A1 (en) Minimizing transport fuzzing reactions
WO2024049612A1 (en) Internal certificate authority for electronic control unit
JP2024505138A (ja) 輸送機関に対する外部機能のプロビジョニング
CN113678182A (zh) 用于交通信号验证的系统和密码硬化方法
US20230274629A1 (en) Keyless entry message validation
US20230410538A1 (en) Vehicle-related projectile minimization
CN114297222A (zh) 车辆不正当行为管理方法、设备、存储介质及装置
CN115708142A (zh) 验证车对外界的用于控制交通流的交互信息的方法和装置
CN111832774B (zh) 网约车的轨迹追踪方法、云平台和网约车obu
WO2024020234A1 (en) Providing recorded data related to an event
US11252154B2 (en) Apparatus and server for sharing position information of vehicle
CN118488905A (zh) 稳健的空中重新编程
EP3789968A1 (de) Verfahren zur validierung von fahrzeugdaten eines bestimmten fahrzeugs
US20220335123A1 (en) Transport component tamper detection
CN115699818A (zh) 用于评估由车辆传输的信息的正确性的方法和系统
CN112802213A (zh) 一种不停车电子收费中车载控制器的激活方法及激活系统
EP3789971A1 (de) Validierung von daten, die von einem bordeigenen diagnosesystem bereitgestellt werden
EP3789969B1 (de) Verfahren und system zur validierung einer identität einer bestimmten funktionalen vorrichtung
KR102369668B1 (ko) 차량 번호에 기반을 둔 결제 처리 시스템 및 그 제어방법
CN112689243B (zh) 一种车辆定位方法、装置、车辆和可读介质

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200716

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20220811

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

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

Ref legal event code: R096

Ref document number: 602019024493

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1545114

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230215

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20230118

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1545114

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230118

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

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230530

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

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230118

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602019024493

Country of ref document: DE

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

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

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

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

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

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

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

26N No opposition filed

Effective date: 20231019

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

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

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230930

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

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

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

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

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

Effective date: 20230905

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

Ref country code: CH

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

Effective date: 20230930

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

Ref country code: CH

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

Effective date: 20230930

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

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

Ref country code: DE

Payment date: 20240930

Year of fee payment: 6

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

Ref country code: GB

Payment date: 20240922

Year of fee payment: 6

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

Ref country code: FR

Payment date: 20240924

Year of fee payment: 6