This document is applicable to road vehicles, where the electronic vehicle interface is used to perform a test method that is part of a periodic technical inspection (ePTI).<\/p>\n
This document describes use cases and specifies technical requirements in order to support the ePTI-relevant vehicle safety system(s) checks during the periodic technical inspection via the electronic interface. This document references the ISO 14229 series<\/span><\/span>, the unified diagnostic services implemented on diagnostic communication over controller area network (DoCAN) and the Internet protocol (DoIP) along with the required provision of data definitions.<\/p>\n The technical requirements of diagnostic services and data definitions of emissions-related systems are specified in other International Standards, for example, ISO 15031<\/span><\/span> and ISO 27145<\/span><\/span>. Other environmental systems’ ePTI use cases and technical requirements can be considered in the future.<\/p>\n This document defines:<\/p>\n all requirements describing the vehicle-communication functionality via the diagnostic link connector related to ePTI, for example:<\/p>\n discovery of the ePTI data link;<\/p>\n<\/li>\n discovery of the ePTI-relevant systems;<\/p>\n<\/li>\n query of ePTI-relevant systems\u2019 information, including software identification, software integrity, current and\/or stored values;<\/p>\n<\/li>\n query of ePTI-relevant systems\u2019 error information;<\/p>\n<\/li>\n activation of ePTI-relevant systems\u2019 actuators or routines;<\/p>\n<\/li>\n<\/ol>\n<\/li>\n the use cases about the individual vehicle communication functionality, for example, query identification information, command functional test method.<\/p>\n<\/li>\n<\/ul>\n This document does not directly specify any type of test method or pass\/fail criteria of the ePTI-relevant system during a PTI, but provides data, which may support PTI test methods.<\/p>\n The document specifies:<\/p>\n terminology;<\/p>\n<\/li>\n communication establishment between the ePTI external test equipment and the vehicle’s ePTI-relevant systems;<\/p>\n<\/li>\n usage of a credentials-based authentication and authorisation mechanism between the ePTI external test equipment and the vehicle;<\/p>\n<\/li>\n protection against tampering of the defined ePTI methods;<\/p>\n<\/li>\n definition of ePTI-relevant use cases:<\/p>\n ePTI external test equipment discovers available data identifier as specified in ISO 20730-3<\/span><\/span> ;<\/p>\n<\/li>\n ePTI external test equipment queries the ePTI-relevant system\u2019s information, including software numbers, software integrity information, current and\/or stored values, self-test completion status, system status, and error information (e.g. DTC and\/or DID information);<\/p>\n<\/li>\n ePTI external test equipment activates the ePTI-relevant system\u2019s actuators or routines;<\/p>\n<\/li>\n<\/ul>\n<\/li>\n definition of ePTI-relevant technical requirements;<\/p>\n<\/li>\n ePTI external test equipment minimum requirements.<\/p>\n<\/li>\n<\/ul>\n This document excludes:<\/p>\n process definitions for performing the PTI check;<\/p>\n<\/li>\n process and data definitions for off-board data provision;<\/p>\n<\/li>\n standardised data exchange formats;<\/p>\n<\/li>\n validation and verification of vehicle safety systems according to vehicle manufacturer specifications.<\/p>\n<\/li>\n<\/ul>\n Road vehicles. Vehicle interface for electronic Periodic Technical Inspection (ePTI) – Application and communication requirements<\/b><\/p>\n\n
\n
\n
\n
\n
PDF Catalog<\/h4>\n
\n
\n PDF Pages<\/th>\n PDF Title<\/th>\n<\/tr>\n \n 2<\/td>\n undefined <\/td>\n<\/tr>\n \n 8<\/td>\n Foreword <\/td>\n<\/tr>\n \n 9<\/td>\n Introduction <\/td>\n<\/tr>\n \n 11<\/td>\n 1 Scope <\/td>\n<\/tr>\n \n 12<\/td>\n 2 Normative references <\/td>\n<\/tr>\n \n 13<\/td>\n 3 Terms and definitions <\/td>\n<\/tr>\n \n 15<\/td>\n 4 Symbols and abbreviated terms
5 How to read this document
5.1 Layout of the document <\/td>\n<\/tr>\n\n 16<\/td>\n 5.2 Use case structure explanation
5.3 Requirements statement structure <\/td>\n<\/tr>\n\n 17<\/td>\n 5.4 ePTI application example <\/td>\n<\/tr>\n \n 18<\/td>\n 6 ePTI inspection modules and use cases overview and principles
6.1 Basic principles <\/td>\n<\/tr>\n\n 19<\/td>\n 6.2 ePTI inspection modules
7 IM-1 \u2013 Discover ePTI data link and ePTI-relevant system(s)
7.1 UC 1.1 \u2013 Discover ePTI data link <\/td>\n<\/tr>\n\n 20<\/td>\n 7.2 UC 1.2 \u2013 Discover ePTI-relevant system(s)
8 IM-2 \u2013 Authentication, authorisation
8.1 UC 2.1 \u2013 ePTI external test equipment authentication <\/td>\n<\/tr>\n\n 21<\/td>\n 8.2 UC 2.2 \u2013 Vehicle ECU authentication
9 IM-3 \u2013 Query available ePTI identifier(s)
9.1 UC 3.1 \u2013 Query supported data identifier(s) <\/td>\n<\/tr>\n\n 22<\/td>\n 9.2 UC 3.2 \u2013 Query supported routine identifier(s)
9.3 UC 3.3 \u2013 Query supported input\/output control identifier(s) <\/td>\n<\/tr>\n\n 23<\/td>\n 10 IM-4 \u2013 Query ePTI system information
10.1 UC 4.1 \u2013 Query vehicle identification number
10.2 UC 4.2 \u2013 Query vehicle odometer value
10.3 UC 4.3 \u2013 Query system’s software number <\/td>\n<\/tr>\n\n 24<\/td>\n 10.4 UC 4.4 \u2013 Identify installed system’s software integrity information
10.5 UC 4.5 \u2013 Query information from system <\/td>\n<\/tr>\n\n 25<\/td>\n 11 IM-5 \u2013 Query system’s self-test completion and error information
11.1 UC 5.1 \u2013 Query system’s self-test completion status
11.2 UC 5.2 \u2013 Query system status and error information <\/td>\n<\/tr>\n\n 26<\/td>\n 12 IM-6 \u2013 Activate system’s routines, input\/output control(s)
12.1 UC 6.1 \u2013 Activate system’s routine(s)
12.2 UC 6.2 \u2013 Activate system’s input\/output control(s) <\/td>\n<\/tr>\n\n 27<\/td>\n 13 Overview of vehicle system requirements
13.1 ePTI external test equipment and vehicle message exchange sequence
13.2 Technical requirements and use case coverage <\/td>\n<\/tr>\n\n 28<\/td>\n 14 Application (APP)
14.1 Setup vehicle’s DoCAN data link framework <\/td>\n<\/tr>\n\n 30<\/td>\n 14.2 Setup vehicle’s DoIP data link framework <\/td>\n<\/tr>\n \n 32<\/td>\n 14.3 Choice of DoCAN and DoIP data link in the vehicle
15 Application layer (AL)
15.1 Applicable ISO 14229-1 UDS functionality <\/td>\n<\/tr>\n\n 33<\/td>\n 15.2 Authentication
15.2.1 Requirements definition \u2014 ePTI external test equipment authentication <\/td>\n<\/tr>\n\n 34<\/td>\n 15.2.2 Requirements definition \u2014 ECU authentication
15.3 ReadDataByIdentifier \u2014 Report ePTI-relevant system(s)
15.3.1 Requirements definition \u2014 Report ePTI-relevant system(s)
15.3.2 Message sequence implementation requirements \u2014 Report ePTI-relevant system(s) <\/td>\n<\/tr>\n\n 35<\/td>\n 15.3.3 Example of the message sequence \u2014 Report ePTI-relevant system(s) <\/td>\n<\/tr>\n \n 36<\/td>\n 15.4 ReadDataByIdentifier \u2014 Report ECU supported data identifier(s)
15.4.1 Requirements definition \u2014 Report ECU supported data identifier(s) <\/td>\n<\/tr>\n\n 37<\/td>\n 15.4.2 Message sequence implementation requirements \u2014 Report ECU supported data identifier(s)
15.4.3 Example of the message sequence \u2014 Report ECU supported data identifier(s) <\/td>\n<\/tr>\n\n 38<\/td>\n 15.5 ReadDataByIdentifier \u2014 Report ECU supported routine identifier(s)
15.5.1 Requirements definition \u2014 Report ECU supported routine identifier(s)
15.5.2 Message sequence implementation requirements \u2014 Report ECU supported routine identifier(s) <\/td>\n<\/tr>\n\n 39<\/td>\n 15.5.3 Example of the message sequence \u2014 Report ECU supported routine identifier(s)
15.6 ReadDataByIdentifier \u2014 Report ECU supported input\/output control identifier(s)
15.6.1 Requirements definition \u2014 Report ECU supported input\/output control identifier(s) <\/td>\n<\/tr>\n\n 40<\/td>\n 15.6.2 Message sequence implementation requirements \u2014 Report ECU supported input\/output control identifier(s)
15.6.3 Example of the message sequence \u2014 Report ECU supported input\/output control identifier(s)
15.7 ReadDataByIdentifier \u2014 Report VIN from ECU
15.7.1 Requirements definition \u2014 Report VIN from ECU <\/td>\n<\/tr>\n\n 41<\/td>\n 15.7.2 Message sequence implementation requirements \u2014 Report VIN from ECU
15.7.3 Example of the message sequence \u2014 Report VIN from ECU <\/td>\n<\/tr>\n\n 42<\/td>\n 15.8 ReadDataByIdentifier \u2014 Report vehicle odometer value
15.8.1 Requirements definition \u2014 Report vehicle odometer value
15.8.2 Message sequence implementation requirements \u2014 Report vehicle odometer value <\/td>\n<\/tr>\n\n 43<\/td>\n 15.8.3 Example of the message sequence \u2014 Report vehicle odometer value
15.9 ReadDataByIdentifier \u2014 Report vehicle’s system software number(s)
15.9.1 Requirements definition \u2014 Report vehicle’s system software number(s) <\/td>\n<\/tr>\n\n 44<\/td>\n 15.9.2 Message sequence implementation requirements \u2014 Report vehicle’s system software number(s)
15.10 ReadDataByIdentifier \u2014 Report information from system
15.10.1 Requirements definition \u2014 Report information from system <\/td>\n<\/tr>\n\n 45<\/td>\n 15.10.2 Message sequence implementation requirements \u2014 Report information from system
15.10.3 Example of the message sequence \u2014 Report information from system
15.11 ReadDataByIdentifier \u2014 Report vehicle’s ePTI system self-test completion and system status
15.11.1 Requirements definition \u2014 Report vehicle’s ePTI system self-test completion and system status <\/td>\n<\/tr>\n\n 46<\/td>\n 15.11.2 Message sequence implementation requirements \u2014 Report vehicle’s ePTI system self-test completion and system status <\/td>\n<\/tr>\n \n 47<\/td>\n 15.11.3 Example of the message sequence \u2014 Report vehicle’s ePTI system self-test completion and system status
15.12 RoutineControl \u2014 Activate system’s routines
15.12.1 Requirements definition \u2014 Activate system’s routines <\/td>\n<\/tr>\n\n 49<\/td>\n 15.12.2 Message sequence implementation requirements \u2014 Activate system’s routines
15.12.3 Example of the message sequence \u2014 Activate system’s routines exterior lights
15.13 InputOutputControlByIdentifier \u2014 Activate system’s input\/output controls
15.13.1 Requirements definition \u2014 Activate system’s input\/output controls <\/td>\n<\/tr>\n\n 51<\/td>\n 15.13.2 Message sequence implementation requirements \u2014 Activate system’s input\/output controls
15.13.3 Example of the message sequence \u2014 Activate system’s input\/output controls
16 Session layer (SL) <\/td>\n<\/tr>\n\n 52<\/td>\n Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" \n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n BSI<\/b><\/a><\/td>\n 2021<\/td>\n 54<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":375838,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-375831","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/375831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/375838"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=375831"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=375831"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=375831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}