eLibrary >
BS ISO 20730-1:2021 Road vehicles. Vehicle interface for electronic Periodic Technical Inspection (ePTI) - Application and communication requirements >
Expand All
TOC Search:
BS ISO 20730-1:2021 Road vehicles. Vehicle interface for electronic Periodic Technical Inspection (ePTI) - Application and communication requirements, 2021
- undefined
- Foreword
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms and definitions
- 4 Symbols and abbreviated terms
- 5 How to read this document
- 5.1 Layout of the document
- 5.2 Use case structure explanation
- 5.3 Requirements statement structure
- 5.4 ePTI application example
- 6 ePTI inspection modules and use cases overview and principles
- 6.1 Basic principles
- 6.2 ePTI inspection modules
- 7 IM-1 – Discover ePTI data link and ePTI-relevant system(s)
- 7.1 UC 1.1 – Discover ePTI data link
- 7.2 UC 1.2 – Discover ePTI-relevant system(s)
- 8 IM-2 – Authentication, authorisation
- 8.1 UC 2.1 – ePTI external test equipment authentication
- 8.2 UC 2.2 – Vehicle ECU authentication
- 9 IM-3 – Query available ePTI identifier(s)
- 9.1 UC 3.1 – Query supported data identifier(s)
- 9.2 UC 3.2 – Query supported routine identifier(s)
- 9.3 UC 3.3 – Query supported input/output control identifier(s)
- 10 IM-4 – Query ePTI system information
- 10.1 UC 4.1 – Query vehicle identification number
- 10.2 UC 4.2 – Query vehicle odometer value
- 10.3 UC 4.3 – Query system's software number
- 10.4 UC 4.4 – Identify installed system's software integrity information
- 10.5 UC 4.5 – Query information from system
- 11 IM-5 – Query system's self-test completion and error information
- 11.1 UC 5.1 – Query system's self-test completion status
- 11.2 UC 5.2 – Query system status and error information
- 12 IM-6 – Activate system's routines, input/output control(s)
- 12.1 UC 6.1 – Activate system's routine(s)
- 12.2 UC 6.2 – Activate system's input/output control(s)
- 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
- 14 Application (APP)
- 14.1 Setup vehicle's DoCAN data link framework
- 14.2 Setup vehicle's DoIP data link framework
- 14.3 Choice of DoCAN and DoIP data link in the vehicle
- 15 Application layer (AL)
- 15.1 Applicable ISO 14229-1 UDS functionality
- 15.2 Authentication
- 15.2.1 Requirements definition — ePTI external test equipment authentication
- 15.2.2 Requirements definition — ECU authentication
- 15.3 ReadDataByIdentifier — Report ePTI-relevant system(s)
- 15.3.1 Requirements definition — Report ePTI-relevant system(s)
- 15.3.2 Message sequence implementation requirements — Report ePTI-relevant system(s)
- 15.3.3 Example of the message sequence — Report ePTI-relevant system(s)
- 15.4 ReadDataByIdentifier — Report ECU supported data identifier(s)
- 15.4.1 Requirements definition — Report ECU supported data identifier(s)
- 15.4.2 Message sequence implementation requirements — Report ECU supported data identifier(s)
- 15.4.3 Example of the message sequence — Report ECU supported data identifier(s)
- 15.5 ReadDataByIdentifier — Report ECU supported routine identifier(s)
- 15.5.1 Requirements definition — Report ECU supported routine identifier(s)
- 15.5.2 Message sequence implementation requirements — Report ECU supported routine identifier(s)
- 15.5.3 Example of the message sequence — Report ECU supported routine identifier(s)
- 15.6 ReadDataByIdentifier — Report ECU supported input/output control identifier(s)
- 15.6.1 Requirements definition — Report ECU supported input/output control identifier(s)
- 15.6.2 Message sequence implementation requirements — Report ECU supported input/output control identifier(s)
- 15.6.3 Example of the message sequence — Report ECU supported input/output control identifier(s)
- 15.7 ReadDataByIdentifier — Report VIN from ECU
- 15.7.1 Requirements definition — Report VIN from ECU
- 15.7.2 Message sequence implementation requirements — Report VIN from ECU
- 15.7.3 Example of the message sequence — Report VIN from ECU
- 15.8 ReadDataByIdentifier — Report vehicle odometer value
- 15.8.1 Requirements definition — Report vehicle odometer value
- 15.8.2 Message sequence implementation requirements — Report vehicle odometer value
- 15.8.3 Example of the message sequence — Report vehicle odometer value
- 15.9 ReadDataByIdentifier — Report vehicle's system software number(s)
- 15.9.1 Requirements definition — Report vehicle's system software number(s)
- 15.9.2 Message sequence implementation requirements — Report vehicle's system software number(s)
- 15.10 ReadDataByIdentifier — Report information from system
- 15.10.1 Requirements definition — Report information from system
- 15.10.2 Message sequence implementation requirements — Report information from system
- 15.10.3 Example of the message sequence — Report information from system
- 15.11 ReadDataByIdentifier — Report vehicle's ePTI system self-test completion and system status
- 15.11.1 Requirements definition — Report vehicle's ePTI system self-test completion and system status
- 15.11.2 Message sequence implementation requirements — Report vehicle's ePTI system self-test completion and system status
- 15.11.3 Example of the message sequence — Report vehicle's ePTI system self-test completion and system status
- 15.12 RoutineControl — Activate system's routines
- 15.12.1 Requirements definition — Activate system's routines
- 15.12.2 Message sequence implementation requirements — Activate system's routines
- 15.12.3 Example of the message sequence — Activate system's routines exterior lights
- 15.13 InputOutputControlByIdentifier — Activate system's input/output controls
- 15.13.1 Requirements definition — Activate system's input/output controls
- 15.13.2 Message sequence implementation requirements — Activate system's input/output controls
- 15.13.3 Example of the message sequence — Activate system's input/output controls
- 16 Session layer (SL)
- Bibliography [Go to Page]