Logging for Telematic Systems Protokollierung Für Telematiksysteme Journalisation Pour Systèmes Télématiques
Total Page:16
File Type:pdf, Size:1020Kb
(19) TZZ Z¥_T (11) EP 2 680 534 B1 (12) EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention (51) Int Cl.: of the grant of the patent: H04L 29/08 (2006.01) G07C 5/00 (2006.01) 27.12.2017 Bulletin 2017/52 G07C 5/08 (2006.01) (21) Application number: 12004834.3 (22) Date of filing: 28.06.2012 (54) LOGGING FOR TELEMATIC SYSTEMS PROTOKOLLIERUNG FÜR TELEMATIKSYSTEME JOURNALISATION POUR SYSTÈMES TÉLÉMATIQUES (84) Designated Contracting States: • Detlef Borchers: "Mit WLAN im Verbund auf der AL AT BE BG CH CY CZ DE DK EE ES FI FR GB Autobahn",heise online, 7 May 2010 (2010-05-07), GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO XP55041617, Retrieved from the Internet: PL PT RO RS SE SI SK SM TR URL:http://www.heise.de/newsticker/meldung /Mit-WLAN-im-Verbund-auf-der-Autobahn-9954 (43) Date of publication of application: 43.html?view=print [retrieved on 2012-10-19] 01.01.2014 Bulletin 2014/01 • John Quinn: "setting up syslog for distributed application logging", , 9 July 2007 (2007-07-09), (73) Proprietor: Harman Becker Automotive Systems XP55041628, New York, USA Retrieved from the GmbH Internet: 76307 Karlsbad (DE) URL:http://www.johnandcailin.com/blog/john /setting-syslog-distributed-application-lo gging (72) Inventors: [retrieved on 2012-10-19] • Guenkova-Luy, Teodora • "Syslog", Wikipedia, 5 May 2012 (2012-05-05), 89081 Ulm-Grimmelfingen (DE) XP55041614, San Francisco, CA, USA Retrieved • Goeckelmann, Ralph from the Internet: 89160 Dornstadt (DE) URL:http://en.wikipedia.org/w/index.php?ti • Clauss, Martin tle=Syslog&oldid=490814502 [retrieved on 88444 Ummendorf (DE) 2012-10-19] • Klimke, Andreas • JUNGHOON LEE ET AL: "A Telematics Service 89081 Ulm-Söflingen (DE) System Based on the Linux Cluster", 27 May 2007 •Abt,Oliver (2007-05-27), COMPUTATIONAL SCIENCE Â 89134 Blaustein (DE) ICCS 2007; [LECTURE NOTES IN COMPUTER • Seibold, Felix SCIENCE;;LNCS], SPRINGER BERLIN 89081 Ulm-Jungingen (DE) HEIDELBERG, BERLIN, HEIDELBERG, PAGE(S) 660 - 667, XP019094555, ISBN: 978-3-540-72589-3 (74) Representative: Grünecker Patent- und * Section 1 Section 3 * * figure 1 * Rechtsanwälte • GERHARDS ADISCON GMBH R: "The Syslog PartG mbB Protocol; rfc5424.txt", THE SYSLOG Leopoldstraße 4 PROTOCOL; RFC5424.TXT, INTERNET 80802 München (DE) ENGINEERING TASK FORCE, IETF; STANDARD, INTERNET SOCIETY (ISOC) 4, RUE DES (56) References cited: FALAISES CH- 1205 GENEVA, SWITZERLAND, 1 US-A1- 2009 150 023 US-A1- 2012 053 778 March 2009 (2009-03-01), XP015065515, [retrieved on 2009-03-10] Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). EP 2 680 534 B1 Printed by Jouve, 75001 PARIS (FR) (Cont. next page) EP 2 680 534 B1 • EDWARD CHUAH ET AL: "Diagnosing the root-causes of failures from cluster log files", HIGH PERFORMANCE COMPUTING (HIPC), 2010 INTERNATIONAL CONFERENCE ON, IEEE, 19 December 2010 (2010-12-19), pages 1-10, XP031914499, DOI: 10.1109/HIPC.2010.5713159 ISBN: 978-1-4244-8518-5 2 EP 2 680 534 B1 Description Field of Invention 5 [0001] The present invention relates to a method and an apparatus for logging and diagnostics for telematic systems combining features from real-time tracing methodology with persistent error storage and diagnosis, wherein the system being logged and analyzed may be composed of an arbitrary number of sub-components that exhibit significant inter- dependency. 10 Background of the Invention [0002] Since its introduction in 1978 by Simon Nora and Alain Minc, telematics, i.e., the integration of telecommuni- cations and informatics, has become very popular, especially in the context of automotive telematics, i.e., for application in vehicles. Typical applications of automotive telematic systems include automotive navigation systems using Global 15 Positioning System technology, emergency warning systems for vehicles, both in vehicle-to-vehicle and in vehicle-to- infrastructure settings, emergency calling systems in the case of accident or break-down of the vehicle, integrated hands- free cell phones, wireless safety communications, automatic driving assistance systems, mobile data, radio, and tele- vision, and vehicle tracking, e.g., as part of fleet management systems, but are not limited to these. Telematic systems may comprise electronic, electromechanical, and electromagnetic devices. Intelligent vehicle technologies are utilized 20 for safety and commercial communications between vehicles or between a vehicle and an external sensor or an external server. [0003] One of the latest additions to the world of automotive telematics is the provision of on-board logging and on- board diagnostics systems for vehicles interacting with telematic components of the vehicle. Current vehicle systems employ an ’on-board diagnostics system’ in order to detect problems with components of the vehicle early on. The 25 detected problems are reported to the driver. In addition, they are generally recorded for later analysis by a specialist using diagnostic trouble codes (DTCs). This typically allows the service provider to more rapidly identify the cause of a problem once a vehicle has been returned for inspection. Typically, a scan tool is used to read the diagnostics information memory. To this end, the scan tool is generally physically connected to the on-board diagnostics system. [0004] Tracking of a system state of a complex product, like an automotive telematic system, combined with the ability 30 of detecting problematic behavior as early on as possible is key in preventing serious vehicle accidents as well as ensuring a (near) problem-free product life cycle. Particularly, malfunctions of safety relevant telematics components, as for instance for the automatic dispatching of an emergency call in the case of an accident or break-down of the vehicle or for the exchange of information concerning hazardous road conditions between vehicles and/or back-end servers, need to be detected as early as possible or ideally be anticipated by constant monitoring of the involved telematics 35 components and/or (software) application components. With increasing complexity of nowadays telematics systems and ongoing integration of electronic components, logging, diagnosing, and correction of malfunctions of the involved (software) application components have gained relative importance compared to hardware diagnostics alone, which so far were at the heart of on-board diagnostics standardization efforts in the automotive industry. [0005] System processes and activities are usually carried out by or in interaction with (software) application compo- 40 nents in the automotive environment and are typically composed of a large number of sub-tasks executed by sub- components that interact with each other. In many cases, the combined behavior of the sub-systems must be taken into account in order to correctly identify the root cause of an error in the case of a malfunction of a system. Furthermore, processes often exhibit volatile behavior in case of errors, i.e., system problems may recover by themselves due to a change of the external conditions. Specific examples for such systems are the online and connectivity systems which 45 may fail under conditions of no network coverage but recover as soon as network coverage is reached. [0006] An automated diagnostics tool needs to be able to take these characteristics into account in order to avoid inconclusive results. In a volatile system, it is desirable to not only extract the relevant errors that have occurred, but also, to provide information on the overall system reliability and performance (for instance, the number of successfully completed use cases vs. failed ones). Since many errors in complex systems involving application components and 50 telematic components are not safety relevant and may additionally be volatile, it is desirable to decouple servicing of the telematic system from the standard vehicle inspection cycle. Particularly, a servicing of the telematic system driven by demand, ideally prior to customer complaints, is in the interest of both customers and service providers. [0007] Further, the increasing complexity and interconnectivity of telematic systems in current vehicles lead to an ever larger quantity of possible errors, root causes, and error messages, thus rapidly exceeding the capabilities of on-board 55 diagnostics systems and trained diagnosticians, who, in many cases, have to diagnose occurred problems ’by hand’ by running diagnostics tests as part of a vehicle service. Standardized error codes or diagnostic trouble codes can help but often hamper technological progress in a highly competitive environment. Considering the rather long product life cycle of vehicles, as opposed for instance to smart phones, and the limited capabilities for system upgrades of deployed 3 EP 2 680 534 B1 telematic systems, a genuinely extensible logging and diagnostics system as opposed to current, more rigid solutions is also desirable. Document US 2009/150023 A1 (GRAU THOMAS P [US] ET AL) (2009-06-11) discloses a method and a system for providing vehicle data to a third party, e.g. car dealerships, repair shops, governmental agencies (e.g. for certification), call centers etc., using recipient group-specific reports. Vehicle data are collected