eLibrary >
ISO 13185-4:2020 Intelligent transport systems - Vehicle interface for provisioning and support of ITS Services - Part 4: Unified vehicle interface protocol (UVIP) conformance test specification >
ISO 13185-4:2020 Intelligent transport systems - Vehicle interface for provisioning and support of ITS Services - Part 4: Unified vehicle interface protocol (UVIP) conformance test specification, 2020
- Foreword
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms, definitions and abbreviated terms
- 3.1 Terms and definitions
- 3.2 Abbreviated terms
- 4 Conventions
- 5 Conformance test plan (CTP) basic principles and clustering
- 5.1 Basic principles for CTC definition
- 5.2 CTC structure
- 5.2.1 CTC – General structure
- 5.2.2 Result criteria
- 5.3 CTC system setup
- 5.4 CTC clustering
- 5.4.1 General
- 5.4.2 Main CTC clusters
- 6 CT cluster 1 – Requesting V-ITS-SG and vehicle identification related information
- 6.1 CTC_UC 1.1 – Browsing available V-ITS-SGs
- 6.1.1 Overview
- 6.1.2 Test purpose
- 6.1.3 Configuration
- 6.1.4 Preamble (setup state)
- 6.1.5 Test execution
- 6.1.6 Postamble (setup state)
- 6.2 CTC_UC 1.2 – Browsing supported ECUs
- 6.2.1 Overview
- 6.2.2 Test purpose
- 6.2.3 Configuration
- 6.2.4 Preamble (setup state)
- 6.2.5 Test execution
- 6.2.6 Postamble (setup state)
- 6.3 CTC_UC 1.3 – Browsing supported data Ids
- 6.3.1 Overview
- 6.3.2 Test purpose
- 6.3.3 Configuration
- 6.3.4 Preamble (setup state)
- 6.3.5 Test execution
- 6.3.6 Postamble (setup state)
- 7 CT cluster 2 – Requesting vehicle and ECU data values
- 7.1 CTC_UC 2.1 – Requesting data ID values for single usage
- 7.1.1 Overview
- 7.1.2 Test purpose
- 7.1.3 Configuration
- 7.1.4 Preamble (setup state)
- 7.1.5 Test execution
- 7.1.6 Postamble (setup state)
- 7.2 CTC_UC 2.2 – Requesting data ID values for repeated usage
- 7.2.1 Overview
- 7.2.2 Test purpose
- 7.2.3 Configuration
- 7.2.4 Preamble (setup state)
- 7.2.5 Test execution
- 7.2.6 Postamble (setup state)
- 7.3 CTC_UC 2.3 – Requesting data ID text and data type information
- 7.3.1 Overview
- 7.4 CTC_UC 2.4 – Requesting data type definitions
- 7.4.1 Overview
- 7.5 CTC_UC 2.5 – Requesting all available text and data type information
- 7.5.1 Overview
- 8 CT cluster 3 – Requesting and clearing DTCs and related data
- 8.1 CTC_UC 3.1 – Requesting DTCs
- 8.1.1 Overview
- 8.1.2 Test purpose
- 8.1.3 Configuration
- 8.1.4 Preamble (setup state)
- 8.1.5 Test execution
- 8.1.6 Postamble (setup state)
- 8.2 CTC_UC 3.2 – Requesting additional DTC data
- 8.2.1 Overview
- 8.2.2 Test purpose
- 8.2.3 Configuration
- 8.2.4 Preamble (setup state)
- 8.2.5 Test execution
- 8.2.6 Postamble (setup state)
- 8.3 CTC_UC 3.3 – Clearing DTCs
- 8.3.1 Overview
- 8.3.2 Test purpose
- 8.3.3 Configuration
- 8.3.4 Preamble (setup state)
- 8.3.5 Test execution
- 8.3.6 Postamble (setup state)
- 8.4 CTC_UC 3.4 – SendOnChange – Provide DTC and status
- 8.4.1 Overview
- 9 CT cluster 4 – Unsolicited V-ITS-SG messages
- 9.1 CTC_UC 4.1 – SendOnEvent — Emergency situation
- 9.1.1 Overview
- 9.2 CTC_UC 4.2 – SendOnEvent — Critical driving situation
- 9.2.1 Overview
- 9.3 CTC_UC 4.3 – SendOnEvent — Safety situation
- 9.3.1 Overview
- 9.4 CTC_UC 4.4 – SendOnEvent — Warning situation
- 9.4.1 Overview
- 9.5 CTC_UC 4.5 – SendOnEvent — Data ID value matches threshold
- 9.5.1 Overview
- 10 CT cluster 5 – Real-time data transmission
- 10.1 CTC_UC 5.1 – Real-time data ID value measurement
- 10.1.1 Overview
- 10.2 CTC_UC 5.2 – Real-time DTC reporting
- 10.2.1 Overview
- 11 CT cluster 6 – Controlling /adjusting various equipment of the vehicle
- 11.1 CTC_UC 6.1 – Learn settings of customer profile
- 11.1.1 Overview
- 11.1.2 Test purpose
- 11.1.3 Configuration
- 11.1.4 Preamble (setup state)
- 11.1.5 Test execution
- 11.1.6 Postamble (setup state)
- 11.2 CTC_UC 6.2 – Control convenience system
- 11.2.1 Overview
- 11.2.2 Test purpose
- 11.2.3 Configuration
- 11.2.4 Preamble (setup state)
- 11.2.5 Test execution
- 11.2.6 Postamble (setup state)
- 11.3 CTC_UC 6.3 – Control charging for EV
- 11.3.1 Overview
- 11.3.2 Test purpose
- 11.3.3 Configuration
- 11.3.4 Preamble (setup state)
- 11.3.5 Test execution
- 11.3.6 Postamble (setup state)
- 12 CT cluster 7 – Writing short- and long-term data to V-ITS-SG
- 12.1 CTC_UC 7.1 – Write data to V-ITS-SG’s memory
- 12.1.1 Overview
- 12.1.2 Test purpose
- 12.1.3 Configuration
- 12.1.4 Preamble (setup state)
- 12.1.5 Test execution
- 12.1.6 Postamble (setup state)
- 12.2 CTC_UC 7.2 – Write vehicle profile to V-ITS-SG’s memory
- 12.2.1 Overview
- 12.3 CTC_UC 7.3 – Enable/disable functional system related data IDs
- 12.3.1 Overview
- 12.4 CTC_UC 7.4 – Write data ID thresholds to V-ITS-SG’s memory
- 12.4.1 Overview
- 13 CT cluster 8 – V-ITS-SG accessibility restrictions and firewall protection cluster
- 13.1 CTC_UC 8.1 – Secure access to V-ITS-SG
- 13.1.1 Overview
- 13.1.2 Test purpose
- 13.1.3 Configuration
- 13.1.4 Preamble (setup state)
- 13.1.5 Test execution
- 13.1.6 Postamble (setup state)
- 13.2 CTC_UC 8.2 – Request V-ITS-SG firewall status
- 13.2.1 Overview
- 13.3 CTC_UC 8.3 – Configuration of V-ITS-SG firewall
- 13.3.1 Overview
- 13.3.2 Test purpose
- 13.3.3 Configuration
- 13.3.4 Preamble (setup state)
- 13.3.5 Test execution
- 13.3.6 Postamble (setup state)
- 14 CT cluster 9 – V-ITS-SG special features
- 14.1 CTC_UC 9.1 – General data exchange
- 14.1.1 Overview
- 14.2 CTC_UC 9.2 – V-ITS-SG activation mode
- 14.2.1 Overview
- 14.3 CTC_UC 9.3 – Upload EventLogFile from V-ITS-SG
- 14.3.1 Overview
- 14.3.2 Test purpose
- 14.3.3 Configuration
- 14.3.4 Preamble (setup state)
- 14.3.5 Test execution
- 14.3.6 Postamble (setup state)
- 15 CT cluster 10 – Vehicle diagnostics
- 15.1 CTC_UC 10.1 – Perform functional group OBD
- 15.1.1 Overview
- 15.1.2 Test purpose
- 15.1.3 Configuration
- 15.1.4 Preamble (setup state)
- 15.1.5 Test execution
- 15.1.6 Postamble (setup state)
- 15.2 CTC_UC 10.2 – Perform enhanced OBD
- 15.2.1 Overview
- 15.2.2 Test purpose
- 15.2.3 Configuration
- 15.2.4 Preamble (setup state)
- 15.2.5 Test execution
- 15.2.6 Postamble (setup state)
- 15.3 CTC_UC 10.3 – Upload VSOCLogFile from V-ITS-SG
- 15.3.1 Overview
- 15.3.2 Test purpose
- 15.3.3 Configuration
- 15.3.4 Preamble (setup state)
- 15.3.5 Test execution
- 15.3.6 Postamble (setup state)
- 16 CT cluster 11 – Electric vehicle system status
- 16.1 CTC_UC 11.1 – Monitor battery charge status
- 16.1.1 Overview
- 16.1.2 Test purpose
- 16.1.3 Configuration
- 16.1.4 Preamble (setup state)
- 16.1.5 Test execution
- 16.1.6 Postamble (setup state)
- 16.2 CTC_UC 11.2 – Monitor connection between charging station and EV
- 16.2.1 Overview
- 16.2.2 Test purpose
- 16.2.3 Configuration
- 16.2.4 Preamble (setup state)
- 16.2.5 Test execution
- 16.2.6 Postamble (setup state)
- 16.3 CTC_UC 11.3 – Battery charge start/stop notification
- 16.3.1 Overview
- 17 CT cluster 12 – V-ITS-SG maintenance
- 17.1 CTC_UC 12.1 – Update core software of V-ITS-SG
- 17.1.1 Overview
- 17.1.2 Test purpose
- 17.1.3 Configuration
- 17.1.4 Preamble (setup state)
- 17.1.5 Test execution
- 17.1.6 Postamble (setup state)
- 17.2 CTC_UC 12.2 – Perform a Reset in V-ITS-SG
- 17.2.1 Overview
- 17.2.2 Test purpose
- 17.2.3 Configuration
- 17.2.4 Preamble (setup state)
- 17.2.5 Test execution
- 17.2.6 Postamble (setup state)
- 17.3 CTC_UC 12.3 – Perform a reset in V-ITS-SG
- 17.3.1 Overview
- 17.3.2 Test purpose
- 17.3.3 Configuration
- 17.3.4 Preamble (setup state)
- 17.3.5 Test execution
- 17.3.6 Postamble (setup state)
- 17.4 CTC_UC 12.4 – Upload V-ITS-SG configuration file
- 17.4.1 Overview
- 17.4.2 Test purpose
- 17.4.3 Configuration
- 17.4.4 Preamble (setup state)
- 17.4.5 Test execution
- 17.4.6 Postamble (setup state)
- 17.5 CTC_UC 12.5 – Download V-ITS-SG configuration file
- 17.5.1 Overview
- 17.5.2 Test purpose
- 17.5.3 Configuration
- 17.5.4 Preamble (setup state)
- 17.5.5 Test execution
- 17.5.6 Postamble (setup state)
- Bibliography [Go to Page]