EP2988278A1 - Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication - Google Patents

Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication Download PDF

Info

Publication number
EP2988278A1
EP2988278A1 EP14181862.5A EP14181862A EP2988278A1 EP 2988278 A1 EP2988278 A1 EP 2988278A1 EP 14181862 A EP14181862 A EP 14181862A EP 2988278 A1 EP2988278 A1 EP 2988278A1
Authority
EP
European Patent Office
Prior art keywords
data
vehicle
configuration
control unit
communication device
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.)
Pending
Application number
EP14181862.5A
Other languages
German (de)
English (en)
Inventor
Pete Houlden
Nicholas Baker
Daniel Bishop
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.)
Continental Automotive Technologies GmbH
Original Assignee
Continental Automotive GmbH
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 Continental Automotive GmbH filed Critical Continental Automotive GmbH
Priority to EP14181862.5A priority Critical patent/EP2988278A1/fr
Publication of EP2988278A1 publication Critical patent/EP2988278A1/fr
Pending legal-status Critical Current

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/0808—Diagnosing 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
    • G07C2205/00—Indexing scheme relating to group G07C5/00
    • G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool

Definitions

  • the invention relates to a method for operating a device for requesting diagnostic data of a vehicle and a communication device.
  • the invention further relates to a diagnostic system for operating a device for requesting diagnostic data of a vehicle and a communication device.
  • the invention further relates to a configuration system for operating a device for requesting diagnostic data of a vehicle, a communication device and a communication server.
  • Today devices for requesting diagnostic data of a vehicle often communicate via a standardized connection with the vehicle, as, for example, defined by ISO15031. However, via such a standardized connection only little data can be requested, as, for example, emission related data.
  • the object of the invention is to provide a method and a system for operating versatilely a device for requesting diagnostic data of a vehicle and a communication device.
  • the invention is distinguished according to a first aspect by a method for operating a device for requesting diagnostic data of a vehicle and a communication device.
  • Identification data is requested from the vehicle by the device.
  • the identification data is sent to a communication device.
  • configuration data for a vehicle or manufacture specific communication is requested from a configuration server depending on the identification data by the communication device.
  • the configuration data is sent to the device.
  • the configuration data is stored in the device for requesting diagnostic data of the vehicle by use of the configuration data for the vehicle or manufacture specific communication.
  • identification data which is requested from the vehicle is not sufficient, additional data for identification can be requested from a web server and/or from the communication device, wherein this additional request may be manually initiated.
  • configuration data not only a standardized connection with the vehicle, as, for example, defined by ISO15031, is possible, but also a non-standardized vehicle or manufacture specific communication.
  • diagnostic data can be requested, as for example, information about a variable service and/or information about a given sensor of the vehicle.
  • the identification data comprises a vehicle identification number and the configuration data is requested from the configuration server depending on the vehicle identification number.
  • the configuration data for the vehicle or manufacture specific communication is requested from the configuration server depending on a vehicle identification number by requesting control unit detection data from the configuration server depending on the vehicle identification number by the communication device. Further, in response to receiving the control unit detection data by the communication device the control unit detection data is sent to the device. In response to receiving the control unit detection data by the device at least one control unit of the vehicle is identified by use of the control unit detection data and an information about the at least one control unit is sent to the communication device. In response to receiving the information about the at least one control unit by the communication device the configuration data for the vehicle or manufacture specific communication is requested depending on the information about the at least one control unit.
  • control unit detection data By use of the control unit detection data it can be very exactly determined which diagnostic data can be requested from the vehicle.
  • the diagnostic data of the vehicle in response to receiving a request for requesting diagnostic data by the device is requested by the device by use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data.
  • the diagnostic data is sent by the device by use of a given universal protocol to the communication device, wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
  • the vehicle or manufacture specific communication is often not very efficient.
  • a much more efficient communication between the device and the communication device is possible, especially for a wireless communication.
  • 200 bytes can be necessary to send given requested diagnostic data, wherein only about 40 bytes are necessary by use of the given universal protocol.
  • a start of a cranking phase of the vehicle is determined by the device.
  • a transient minimum voltage in the cranking phase is determined by the device.
  • the determined transient minimum voltage is compared by the device with a given limit minimum voltage which is given by the configuration data.
  • the device can be used for a determination of the battery status.
  • the device is, for example, directly connected with a battery supply voltage pin of the vehicle.
  • an initial voltage of a sustained cranking period of the cranking phase is determined by the device.
  • An end voltage of the sustained cranking period of the cranking phase is determined by the device. The determined initial voltage and the determined end voltage are compared by the device with a given limit initial voltage and a given limit end voltage which are given by the configuration data.
  • the invention is distinguished by a diagnostic system, wherein the diagnostic system comprises the device and the communication device being configured to execute the method according to the first aspect or an advantageous embodiment of the method according to the first aspect.
  • the invention is distinguished by a Configuration system, wherein the Configuration system comprises the device, the communication device and the configuration server comprising the configuration data for vehicle or manufacture specific communication, being configured to execute the method according to the first aspect or an advantageous embodiment of the method according to the first aspect.
  • Figure 1 shows a network.
  • the network comprises a diagnostic system 1.
  • the diagnostic system 1 comprises a device 3 for requesting diagnostic data of a vehicle 10 and a communication device 5.
  • the device 3 is, for example, built in a dongle.
  • the communication device 5 is, for example, built in a smartphone, laptop, PC and/or telematics device.
  • the device 3 can, for example, be plugged into an on-board diagnostic, OBD, plug of the vehicle 10 to communicate with control units of the vehicle 10.
  • OBD on-board diagnostic
  • the device 3 is further configured to communicate with the communication device 5, for example via a wireless communication as, for example, Bluetooth.
  • the communication device 5 is configured to communicate with the device 3, for example, via a wireless communication as, for example, Bluetooth.
  • the communication device 5 is configured to communicate with a configuration server 30 and/or with a customer server 40, for example, via internet 20.
  • the configuration server 30 is configured to communicate with the communication device 5, for example, via internet 20.
  • the configuration server 30 is further configured to communicate with a diagnostic database 35.
  • Figure 2 shows a diagram of a measured battery voltage, which can be measured by the device 3.
  • the device 3 is configured to determine a start of a cranking phase of the vehicle 10.
  • the device 3 is, for example, further configured to determine a transient minimum voltage V1 in the cranking phase.
  • the device 3 is, for example, further configured to compare the determined transient minimum voltage V1 with a given limit minimum voltage which is given by a configuration data, which will be later described.
  • Dependent on the comparison a battery status to predict pending failure or insufficient capacity to start the vehicle 10 can be determined, for example, by the device 3 and/or the communication device 5.
  • the device 3 is configured to determine an initial voltage V2 of a sustained cranking period of the cranking phase.
  • the device 3 is, for example, further configured to determine an end voltage V3 of the sustained cranking period of the cranking phase.
  • the device 3 is, for example, further configured to compare the determined initial voltage V2 and the determined end voltage V3 with a given limit initial voltage and a given limit end voltage which are given by the configuration data. Dependent on the comparisons a battery status to predict pending failure or insufficient capacity to start the vehicle 10 can be determined, for example, by the device 3 and/or the communication device 5.
  • Figure 3 shows a first flowchart of a first program for operating the diagnostic system 1 for receiving the configuration data.
  • the configuration data can, for example, be used for a vehicle or manufacture specific communication of the device 3 with the vehicle 10.
  • the configuration data can, for example, additionally be used for the above explained determination of the battery status.
  • the first program can be executed distributed on the device 3, the communication device 5 and the configuration server 30.
  • a step S1 the program is started and, for example, variables are initialized.
  • identification data is requested from the device 3 by the communication device 5.
  • the identification data comprises for example a vehicle identification number.
  • a step S5 the identification data is requested from the vehicle 10 by the device 3.
  • a step S7 the identification data is checked by the device 3. If the identification data is not correct the program is continued in a step S9. If the identification data is correct the program is continued in a step S11.
  • step S9 the identification data is requested from the vehicle 10 by use of a user input.
  • step S11 the identification data is sent from the communication device 5 to the configuration server 30.
  • step S13 the identification data is decoded by the configuration server 30.
  • control unit detection data package is created by the configuration server 30 depending on the identification data by use of the diagnostic database 35 and the control unit detection data package is sent to the communication device 5.
  • the control unit detection data package can comprise control unit detection data for one control unit or for more than one control unit.
  • the control unit detection data package is, for example, encrypted, for example, by use of AES256.
  • control unit detection data is send to the device 3 for identifying at least one control unit of the vehicle 10 by use of the control unit detection data.
  • step S19 in response to receiving the control unit detection data by the device 3 at least one control unit of the vehicle 10 by use of the control unit detection data is identified and an information about the at least one control unit is sent to the communication device 5.
  • control unit detection data package comprises further control unit detection data. If the control unit detection data package comprises further control unit detection data the program is continued in the step S19 and further control unit detection data is sent to the device 3, if not the program is continued in a step S23.
  • step S23 it is checked by the communication device 5 if at least one control unit was identified. If at least one control unit was identified the information about the at least one control unit is sent to the configuration server 30 and the program is continued in a step S27, if no control unit was identified the program is continued in a step S25.
  • step S25 the program is stopped and can, for example, be restarted in the step S1.
  • step S27 configuration data for a vehicle or manufacture specific communication is requested by the communication device 5 from the configuration server 30 depending on the information about the at least one control unit, for example, by use of a web server.
  • the web server for example, comprises a token-system for security.
  • a step S29 the configuration data is built by the configuration server 30, in particular by the web server and the configuration data is sent to the communication device 5.
  • step S31 in response to receiving the configuration data by the communication device 5, the configuration data is sent to the device 3.
  • a step S33 the configuration data is stored and/or loaded into the device 3 for requesting diagnostic data of the vehicle 10 by use of the configuration data for the vehicle or manufacture specific communication.
  • step S35 the program is stopped and can, for example, be restarted in the step S1.
  • Figure 4 shows a second flowchart of a second program for determining a list of diagnostic data which can be requested from the vehicle 10.
  • the second program is, for example, started at vehicle logon.
  • the second program can be executed distributed on the device 3, the communication device 5 and the configuration server 30.
  • a step S40 the program is started, for example, after the first program was stopped and, for example, variables are initialized.
  • step S41 a security authentication is done by the communication device 5.
  • step S43 a security authentication is done by the device 3.
  • a request is sent from the communication device 5 to the device 3 for getting a list of supported diagnostic data which also can be called supported live readings.
  • a vehicle or manufacture specific communication is started by the device 3 with control units for which the configuration data was stored.
  • a standardized communication with other and/or the same control units is started by the device 3.
  • a list of all supported live readings is built by the device 3, for example, by interrogating all control units and attempting all live data commands which are given to the device 3 by a diagnostic package.
  • the list is, for example, separated in a part for diagnostic data which can be requested by a vehicle or manufacture specific communication and diagnostic data which can be requested by a standardized communication, as, for example, defined by ISO15031.
  • the diagnostic data which can be requested by a standardized communication can also be called Level 1 diagnostics.
  • the diagnostic data which can be requested by a vehicle or manufacture specific communication can also be called Level 2 diagnostics.
  • a step S49 the list is sent to the communication device 5.
  • a step S51 the list is, for example, displayed and or logged by the communication device 5 and the program is stopped.
  • An example list is shown in the table 1.
  • Table 1 list of all supported live readings Live reading Level 2 supported Level 1 supported Engine Speed YES control unit 1 YES Vehicle Speed YES control unit 1 YES Coolant Temp YES control unit 1 YES Intake Air Temperature YES control unit 1 YES Mass Air Flow NO NO NO Absolute Throttle Position NO NO NO Odometer YES control unit 3 N/A Brake Pedal YES control unit 2 N/A Fuel Level NO NO Distance till service YES control unit 3 N/A
  • FIG. 5 shows a simplified flowchart of the second program.
  • a step S60 the request is sent from the communication device 5 to the device 3 for getting the list of supported live readings.
  • a step S61 the list of all supported live readings is built by the device 3, for example, by interrogating all control units and attempting all live data commands which are given to the device 3 by a diagnostic package.
  • a step S63 the list is sent to the communication device 5.
  • a step S65 the list is stored in the communication device 5 and the program is stopped.
  • Figure 6 shows a flowchart of a third program to get diagnostic data.
  • a step S100 the program is started and, for example, variables are initialized.
  • a request for requesting diagnostic data is sent by the communication device 5 to the device 3.
  • a step S103 the list of all supported live readings is provided by the device 3 which was built for example in the step S61 and/or S47.
  • a step S105 it is checked by the device 3 if the requested diagnostic data is supported by use of the list. If the requested diagnostic data is not supported the program is continued in a step S160. If the requested diagnostic data is supported the program is continued in a step S107.
  • a step S107 it is checked by the device 3 if the configuration data is needed or if the requested diagnostic data can be requested by use of a given standardized protocol. If the configuration data is needed the program is continued in a step S120. If the configuration data is not needed the program is continued in a step S109.
  • a step S109 the diagnostic data is requested by the device 3 from the vehicle 10 by use of a given standardized protocol.
  • a step S111 the request for diagnostic data is received by the vehicle 10.
  • a step S113 the diagnostic data is sent back to the device 3 from the vehicle 10.
  • a step S115 the diagnostic data is received by the device 3 and the diagnostic data is decoded and the program is continued in a step S150.
  • step S120 the required configuration data is loaded for a vehicle or manufacture specific communication, in particular, for the use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data.
  • a wakeup/start command is sent by the device 3 to the control unit from which the diagnostic data is requested.
  • a wakeup sequence is started in the control unit.
  • a step S127 the wakeup sequence is finished in the control unit.
  • a diagnostic data request for the requested diagnostic data is loaded by the device 3 by use of the configuration data.
  • a step S131 the diagnostic data request is sent by the device 3 to the control unit.
  • step S133 the control unit receives the diagnostic data request.
  • step S135 the requested diagnostic data is sent by the control unit to the device 3.
  • a request is sent by the device 3 for stopping the communication with the control unit to the control unit.
  • a step S139 the communication is stopped by the control unit.
  • a stop acknowledgment is sent by the control unit to the device 3 and the program is continued in the step S150.
  • step S150 the diagnostic data is stored by the device 3.
  • a step S160 it is checked by the device 3 if further diagnostic data is requested. If further diagnostic data is requested the program is continued in the step S103. If no further diagnostic data is requested the program is continued in a step S161.
  • the diagnostic data is sent by the device 3 to the communication device 5, in particular by use of a given universal protocol, wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
  • a step S163 the diagnostic data is displayed by the communication device 5 and/or stored in the communication device 5.
  • a step S170 it is checked by the device 3 if the diagnostic data is to be requested again, for example, in a given interval. If the diagnostic data is to be requested again, the program is continued in the step S103. If the diagnostic data is not to be requested again, the program is continued in a step S173.
  • step S173 the program is stopped and can, for example, be restarted in the step S1.
  • the configuration data not only a standardized connection with the vehicle 10, as, for example, defined by ISO15031, is possible, but also a non-standardized vehicle or manufacture specific communication.
  • many different diagnostic data can be requested, as, for example, information about a variable service and/or information about a given sensor of the vehicle 10. Further, the battery status can be determined.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Small-Scale Networks (AREA)
EP14181862.5A 2014-08-21 2014-08-21 Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication Pending EP2988278A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP14181862.5A EP2988278A1 (fr) 2014-08-21 2014-08-21 Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP14181862.5A EP2988278A1 (fr) 2014-08-21 2014-08-21 Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication

Publications (1)

Publication Number Publication Date
EP2988278A1 true EP2988278A1 (fr) 2016-02-24

Family

ID=51454543

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14181862.5A Pending EP2988278A1 (fr) 2014-08-21 2014-08-21 Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication

Country Status (1)

Country Link
EP (1) EP2988278A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3567554A1 (fr) * 2018-05-10 2019-11-13 Mahle International GmbH Appareils, systèmes et procédés de capture d'informations de diagnostic de véhicule automobile à distance, de surveillance et de commande

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040227523A1 (en) * 2003-05-13 2004-11-18 Hamid Namaky Cellular phone configured with off-board device capabilities and starter/charger and battery testing capabilities
US20090276115A1 (en) * 2005-06-30 2009-11-05 Chen Ieon C Handheld Automotive Diagnostic Tool with VIN Decoder and Communication System
US20130317694A1 (en) * 2012-05-23 2013-11-28 Snap-On Incorporated Methods and Systems for Providing Vehicle Repair Information
US20140195099A1 (en) * 2013-01-04 2014-07-10 Innova Electronics, Inc. Smart phone app-based vin decoding and symptomatic diagnostic system and method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040227523A1 (en) * 2003-05-13 2004-11-18 Hamid Namaky Cellular phone configured with off-board device capabilities and starter/charger and battery testing capabilities
US20090276115A1 (en) * 2005-06-30 2009-11-05 Chen Ieon C Handheld Automotive Diagnostic Tool with VIN Decoder and Communication System
US20130317694A1 (en) * 2012-05-23 2013-11-28 Snap-On Incorporated Methods and Systems for Providing Vehicle Repair Information
US20140195099A1 (en) * 2013-01-04 2014-07-10 Innova Electronics, Inc. Smart phone app-based vin decoding and symptomatic diagnostic system and method

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3567554A1 (fr) * 2018-05-10 2019-11-13 Mahle International GmbH Appareils, systèmes et procédés de capture d'informations de diagnostic de véhicule automobile à distance, de surveillance et de commande
CN110471393A (zh) * 2018-05-10 2019-11-19 马勒国际有限公司 用于远程捕捉汽车诊断信息、监控和控制的设备、系统和方法
JP2019209964A (ja) * 2018-05-10 2019-12-12 マーレ インターナショナル ゲゼルシャフト ミット ベシュレンクテルハフツングＭＡＨＬＥ Ｉｎｔｅｒｎａｔｉｏｎａｌ ＧｍｂＨ 自動車の診断情報の遠隔取得、監視及び制御のための装置、システム及び方法
US11024102B2 (en) 2018-05-10 2021-06-01 Mahle International Gmbh Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling
US20210264698A1 (en) * 2018-05-10 2021-08-26 Mahle International Gmbh Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling
CN110471393B (zh) * 2018-05-10 2024-02-06 马勒国际有限公司 用于远程捕捉汽车诊断信息、监控和控制的设备、系统和方法

Similar Documents

Publication Publication Date Title
US10776098B2 (en) Centralized management of mobile-assisted motor vehicle software upgrading and vehicle data analytics
CN107547327B (zh) 保护车辆的方法和系统
US20180081671A1 (en) Program rewriting device and program rewriting method
US10120030B2 (en) Trace data recording system, trace data recording server, trace data recording method, and information storage medium
CN110471393B (zh) 用于远程捕捉汽车诊断信息、监控和控制的设备、系统和方法
US10567550B2 (en) Method for operating a server
US9767624B2 (en) Method and system for retrieving vehicular parameters from a vehicle data bus
US20150094929A1 (en) Vehicle diagnostic and prognostic systems and methods
US20160325592A1 (en) Method for configuring a tyre pressure sensor
US9324194B2 (en) Method and system for database compilation on a remote electronic device
JP2010064654A (ja) 車両の修理交換情報管理システム、及び車両の異常原因情報管理システム
KR20140113776A (ko) 데이터 처리 방법 및 그 전자 장치
US20170225526A1 (en) Method for configuring a tyre pressure sensor
US20120310474A1 (en) Data recorder
KR20160045191A (ko) 차량의 소프트웨어 업데이트 장치 및 방법
US20150330318A1 (en) Method and Apparatus for Scheduling Vehicle Startup
CN111835799A (zh) 车辆日志自动获取系统及方法
US8380975B2 (en) Safety data writes
JP2019133649A (ja) ネットワーク制御システムにおける自動改ざん検出
EP2988278A1 (fr) Procédé, système de diagnostic et système de configuration de fonctionnement d'un dispositif pour demander des données de diagnostic de véhicule et dispositif de communication
US10261733B2 (en) Image forming apparatus, information processing apparatus, and non-transitory computer readable medium for transmitting a program to an in-room device
KR20200059580A (ko) 사물인터넷 기반의 차량단말장치를 이용한 차량관리시스템
US20190188104A1 (en) Method and apparatus for monitoring memory and for displaying use in electronic control device
JP2014215120A (ja) 電子制御装置
KR101553538B1 (ko) Obd를 이용한 차량 내부의 무선 단말기 제어 시스템 및 그 제어 방법

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

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

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CONTINENTAL AUTOMOTIVE GMBH

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH

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

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTG Intention to grant announced

Effective date: 20240618

INTC Intention to grant announced (deleted)
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: 20240802

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

Free format text: CASE NUMBER: APP_48656/2024

Effective date: 20240826

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