ISO/TR 13185-1:2012
(Main)Intelligent transport systems — Vehicle interface for provisioning and support of ITS services — Part 1: General information and use case definition
Intelligent transport systems — Vehicle interface for provisioning and support of ITS services — Part 1: General information and use case definition
ISO/TR 13185-1:2012 specifies the communications architecture and generic protocol to provide and maintain ITS services to travellers (including drivers, passengers and pedestrians), using nomadic and portable devices.
Systèmes intelligents de transport — Interface véhicule pour la fourniture et le support de services ITS — Partie 1: Informations générales et définition des cas d'utilisation
General Information
Standards Content (Sample)
TECHNICAL ISO/TR
REPORT 13185-1
First edition
2012-05-15
Intelligent transport systems — Vehicle
interface for provisioning and support of
ITS services —
Part 1:
General information and use case definition
Systèmes intelligents de transport — Interface véhicule pour la
fourniture et le support de services ITS —
Partie 1: Informations générales et définition des cas d’utilisation
Reference number
©
ISO 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO’s
member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2012 – All rights reserved
Contents Page
Foreword .iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 3
4 Conventions . 3
5 General information . 3
5.1 Document overview and structure . 3
5.2 Purpose of this Technical Report . 4
5.3 ITS communication architecture components . 4
6 Vehicle interface standardization . 6
6.1 Overview of relevant standards . 6
6.2 Standardized vehicle interface . 7
6.3 Vehicle interface diagnostic data configuration .10
7 Single solution standardized access method .10
7.1 Functionality consolidation of vehicle interfaces into V-ITS-SG .10
7.2 Single solution vehicle interface for ITS applications .13
7.3 Vehicle Station and V-ITS-SG conceptual aspects and guidelines .13
8 V-ITS-SG configuration .14
8.1 Overview of vehicle, Vehicle Stations, network and ITS services .14
8.2 CALM reference architecture-compliant configurations .15
8.3 Examples of benefits .17
9 Use case overview and principles .18
9.1 Basic principles for use case definition .18
9.2 Use case clusters .19
10 Use case definition .22
10.1 UC 1 Requesting V-ITS-SG and vehicle identification related information cluster .22
10.2 UC 2 Requesting vehicle and ECU data values cluster .24
10.3 UC 3 Requesting and clearing DTCs and related data cluster .26
10.4 UC 4 Unsolicitated V-ITS-SG messages cluster .28
10.5 UC 5 Realtime data transmission cluster .31
10.6 UC 6 Controlling/adjusting various equipment of the vehicle cluster .33
10.7 UC 7 Writing short and long term data to V-ITS-SG cluster .34
10.8 UC 8 V-ITS-SG accessibility restrictions and firewall protection cluster .36
10.9 UC 9 V-ITS-SG special features cluster .37
10.10 UC 10 Vehicle diagnostics cluster .38
10.11 UC 11 Electric vehicle system status cluster .39
10.12 UC 12 V-ITS-SG maintenance cluster .40
Bibliography .43
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International
Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In exceptional circumstances, when a technical committee has collected data of a different kind from that
which is normally published as an International Standard (“state of the art”, for example), it may decide by a
simple majority vote of its participating members to publish a Technical Report. A Technical Report is entirely
informative in nature and does not have to be reviewed until the data it provides are considered to be no longer
valid or useful.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TR 13185-1 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
ISO 13185 consists of the following parts, under the general title Intelligent transport systems — Vehicle
interface for provisioning and support of ITS services:
— Part 1: General information and use case definition [Technical Report]
1)
— Part 2: Protocol requirements and specification for vehicle ITS station gateway (V-ITS-SG) interface
2)
— Part 3: Configuration process requirements and specification for vehicle ITS station gateway (V-ITS-SG)
The following document is under development:
— Part 4: Protocol conformance test cases for vehicle ITS station gateway (V-ITS-SG) interface
1) To be published.
2) To be published.
iv © ISO 2012 – All rights reserved
Introduction
This part of ISO 13185 specifies the requirements for a common software interface to a vehicle gateway
to easily exchange vehicle information data among nomadic and/or mobile device, vehicle gateway and the
vehicle’s ECUs.
Applications supporting ITS service provision and multimedia use via nomadic and mobile device need a
common access method to vehicle data through an in-vehicle interface as well as the harmonization of existing
standards to support a single vehicle data access solution.
This document defines a vehicle data transfer protocol between vehicle gateway also called V-ITS-SG and the
nomadic and/or mobile device (ND).
This part of ISO 13185 may be used by vehicle manufacturers for future vehicle design to support the design
of ITS/Telematics and as a retrofit equipment for aftersales vehicles.
Applications supporting ITS service provision and multimedia use via ND may be implemented using vehicle
information, driver advisory, warning systems and entertainment systems. The following standards are subject
to analysis in regard to their applicability to supporting ITS service provision and multimedia use via nomadic
and mobile device.
— ISO 15031 defines emissions-related diagnostic data supported by vehicles in all countries requiring
OBD compliance.
— ISO 27145 WWH-OBD defines diagnostic data (emissions-related systems, future safety related systems,
etc.) to be supported by vehicles in all countries implementing the GTR (Global Technical Regulation) into
their local legislation.
— ISO 22900-2 defines the Modular Vehicle Communication Interface (MVCI) D-PDU API to separate the
protocol data unit (PDU) from the vehicle specific protocols.
— ISO 22901 defines the Open Diagnostic data eXchange (ODX) format which is a standard for describing
diagnostic related ECU data. This International Standard is becoming the vehicle manufacturer’s choice to
document vehicle system diagnostic data and protocol information.
— ISO 22902 is a multimedia and telematics standard based on the AMI-C specification and reference
documents for automotive industry. The important logical element of the architecture is a vehicle interface.
— ISO 22837 defines the reference architecture for probe vehicle systems and a basic data framework
for probe data.
— ISO/TS 29284 defines the standardization of information, communication and control systems in the
field of urban and rural surface transportation, including intermodal and multimodal aspects thereof,
traveller information, traffic management, public transport, commercial transport, emergency services
and commercial services in the ITS field.
— SAE J2534 defines a standardized system for programming of ECUs in a vehicle.
— SAE J2735 defines the support of interoperability among DSRC applications through the use of standardized
message sets, data frames and data elements.
This part of ISO 13185 supports ITS applications which are based on ND in vehicles to operate on a common
software interface to a V-ITS-SG integrated within the CALM architecture and easily exchange vehicle
information data among ND, V-ITS-SG and ECUs.
TECHNICAL REPORT ISO/TR 13185-1:2012(E)
Intelligent transport systems — Vehicle interface for
provisioning and support of ITS services —
Part 1:
General information and use case definition
1 Scope
This part of ISO 13185 specifies the communications architecture and generic protocol to provide and maintain
ITS services to travellers (including drivers, passengers and pedestrians), using nomadic and portable devices for:
— The mobile device as a mobile router,
— Augmentation of the capabilities of a nomadic device using information from in-vehicle systems,
— Nomadic device acting as a key to personalise the vehicle configuration,
— Using capabilities of a nomadic or mobile device to augment functionality within the vehicle,
— The use of portable nomadic devices within commercial vehicles and public transport,
— Optimising the use of the capabilities in nomadic and mobile devices in the provision of ITS services,
— Harmonization of existing standards to support a single solution access method,
— Applications supporting ITS service provision and multimedia use a common access method to retrieve
vehicle data through a vehicle communication interface.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced document
(including any amendments) applies.
ISO/IEC 10731:1994, Information technology — Open Systems Interconnection — Basic Reference Model —
Conventions for the definition of OSI services
ISO 15031 (all parts), Road vehicles — Communication between vehicle and external equipment for emissions-
related diagnostics
3)
ISO/IEC 15118-1 , Road vehicles — Vehicle to grid communication interface — Part 1: General information
and use-case definition
ISO 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture
ISO 22837, Vehicle probe data for wide area communications
ISO 22900-2, Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic protocol
data unit application programming interface (D-PDU API)
ISO 22901 (all parts), Road vehicles — Open diagnostic data exchange (ODX)
ISO 22902-5, Road vehicles — Automotive multimedia interface — Part 5: Common message set
3) To be published.
ISO 22902-6, Road vehicles — Automotive multimedia interface — Part 6: Vehicle interface requirements
4)
ISO/TS 29284, Intelligent transport systems — Event-based probe vehicle data
ISO 27145 (all parts), Road vehicles — Implementation of WWH-OBD communication requirements
ETSI EN 302 665, Intelligent Transport System (ITS) — Communications Architecture
SAE J2735, Dedicated Short Range Communications (DSRC) — Message Set Dictionary
SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 15031-2 and the following apply.
Bluetooth
BT
communication protocol for exchanging data over short distances
Communications Access for Land Mobiles
CALM
specification of a common architecture, network protocols and communications interface definitions to enable
continuous or quasi-continuous communications between vehicles and the infrastructure, or between vehicles,
using wireless telecommunications media that are available in any particular location, and have the ability to
migrate to a different available media where required
eco lamp
lamp that is implemented on the dashboard or nomadic device to guide the driver to drive the vehicle in the
most economical way
EXAMPLE A green lamp/symbol will indicate high fuel efficiency driving or travelling at a constant speed while a red
lamp/symbol will indicate low fuel efficiency, i.e. strong acceleration, sudden braking.
event log file
data record with multiple event data stored with time stamp
nomadic device
ND
device that provides communications connectivity via equipment such as cellular telephones, mobile wireless
broadband (WIMAX, HC-SDMA, etc.), WiFi, etc. and includes short range links, such as Bluetooth, Zigbee, etc.
to connect nomadic devices to the motor vehicle communications system network
Vehicle-Intelligent Transport Systems-Station Gateway
V-ITS-SG
interface device in the vehicle that acts as the vehicle’s mobile gateway between the vehicle’s ECU(s) and the
external nomadic device
V-ITS-SG long term memory
storage of all data in internal memory which are required to be available after key On/Off cycles
V-ITS-SG short term memory
storage of all data in internal memory which shall only be available during this key On/Off cycle
4) To be published.
2 © ISO 2012 – All rights reserved
Vehicle State Of Capabilities Log File
VSOCLogFile
data record with multiple data snapshots including a pre-selected data set providing a vehicle capabilities
status of the vehicle’s electronic system(s)
3.2 Abbreviated terms
BT Bluetooth
CALM Communications Access for Land Mobiles
DLL Dynamic Link Library
DSRC Dedicated Short Range Communications
DTC Diagnostic Trouble Code
ECU Electronic Control Unit
GUI Graphical User Interface
ITS-S Intelligent Transport System-Station
LL Logical Link
N2V Nomadic and mobile devices to Vehicle
ND nomadic device
OBE On-Board Equipment
PDU protocol data unit
RMI Repair and Maintenance Information
RSE Road Side Equipment
V2N Vehicle to Nomadic and mobile devices
VIN Vehicle Identification Number
V-ITS-SG Vehicle-Intelligent Transport System-Station Gateway
VSOC Vehicle State Of Capabilities
4 Conventions
This part of ISO 13185 is based on the conventions discussed in the OSI Service Conventions (ISO/IEC
10731:1994) as they apply to communication services. The vehicle data transfer protocol is applicable to OSI
layers 4, 5, 6 and 7.
5 General information
5.1 Document overview and structure
The ISO 13185 series provides an implementer with all documents and references required to support the
implementation of the requirements related to standardized access to automotive Repair and Maintenance
Information (RMI) in accordance with the requirements set forth in the EC mandate M/421.
— Part 1: This Technical Report provides an overview of the document set and structure along with the use
case definitions and a common set of resources (definitions, references) for use by all subsequent parts.
— Part 2: This part of ISO 13185 specifies all technical requirements related to the protocol to be used
between the V-ITS-SG and the ND to retrieve data from the vehicle’s electronic systems connected to the
V-ITS-SG. The requirements will reflect the deriving needs from the use cases as specified in Part 1.
— Part 3: This part of ISO 13185 specifies the requirements related to the configuration of the V-ITS-SG. The
configuration data derive from an ISO 22901-1 ODX data source converted to a V-ITS-SG specific format
which is V-ITS-SG system supplier specific.
— Part 4: This part of ISO 13185 specifies conformance test cases for self-certification purposes of a provider
of the ND and V-ITS-SG system. The conformance test cases will follow the use-case definition of Part 1
as well as the requirements stated in Part 2. The purpose of this part of ISO 13185 is to provide information
to the ND and V-ITS-SG system provider to build and test the ND and V-ITS-SG system against the
conformance test cases. This final step in the development process of the ND and V-ITS-SG system is an
enabler for all providers to ensure that their ND and/or V-ITS-SG system meets a high degree of functional
requirements expected by the end user.
Vehicle interface for provisioning and support of ITS services
Part 2 Part 3
Part 4
Protocol requirements and Configuration process
Part 1
Protocol conformance test
specification for vehicle ITS requirements and specifica-
General information and use
cases for vehicle ITS station
station gateway (V-ITS-SG) tion for vehicle ITS station
case definition
gateway (V-ITS-SG) interface
interface gateway (V-ITS-SG) interface
Figure 1 — Document structure
5.2 Purpose of this Technical Report
The main purpose of this Technical Report is to:
a) Identify the requirements of bidirectional vehicle data transfer,
b) Identify the usability of the existing International Standards for nomadic and mobile devices and existing
vehicle communication network access standards,
c) Identify additional work required to develop the common software interface to a vehicle gateway integrated
within the CALM architecture by the amendment of the existing interface to D-PDU API in the provision
and support of ITS services via nomadic and mobile devices.
5.3 ITS communication architecture components
The ITS communication architecture is a communication system designed for ITS and made of four physically
separated subsystem components:
— the vehicle subsystem component: Vehicle ITS Station (Vehicle ITS-S),
— the nomadic and mobile subsystem component: Personal ITS Station (Personal ITS-S),
— the roadside subsystem component: Roadside ITS Station (Roadside ITS-S),
— the central subsystem component: Central ITS Station (Central ITS-S).
Figure 2 illustrates the connection between the Personal and Vehicle ITS Station. The V-ITS-S consists of:
— the V-ITS-S Router supporting the CALM architecture, and
— the V-ITS-S Host and Gateway to the in-vehicle networks.
4 © ISO 2012 – All rights reserved
Personal ITS-Station
ND
...
Bluetooth enabled
Nomadic Device
Vehicle ITS-Station
TCP/IP
Central ITS-Station
Vehicle Vehicle Vehicle
ITS-S ITS-S ITS-S
Gateway Host Router Communication
Network
Central System
VM VM VM
...
ECU 1 ECU 2 ECU n
Roadside ITS-Station
Vehicle Architecture
(Host/Router)
Key
1 Vehicle ITS Station: Vehicle subsystem component connected to vehicle domain architecture designed by vehicle
manufacturer via the V-ITS-SG
2 Personal ITS Station: Nomadic and mobile subsystem component
3 Roadside ITS Station: Roadside subsystem component
4 Central ITS Station: Central subsystem component
Figure 3 — ITS communication architecture
NOTE The V-ITS-SG is not a part of the Vehicle ITS Station.
The scope of this Technical Report is V2N (or N2V). V2N is the abbreviation used to cover all types of
communication between vehicle and nomadic and mobile devices.
There are many existing International Standards for the communication between Vehicle ITS Station and
Personal ITS Station for bidirectional vehicle data transfer.
There is a need to identify the usability of the existing International Standards for nomadic devices and existing
vehicle communication network access standards.
6 Vehicle interface standardization
6.1 Overview of relevant standards
Various standards exist which are applicable to either the vehicle network or ITS infrastructure. The following
is a summary of applicable standards:
— ISO 15031 (all parts) defines emissions-related diagnostic data supported by vehicles in all countries
requiring legislative OBD compliance. This International Standard defines a diagnostic connector and
facilities which should be provided by an external test tool. ISO 15031 (all parts) also specifies the diagnostic
6 © ISO 2012 – All rights reserved
messages and DTCs (Diagnostic Trouble Codes) which are reported by the vehicle to the external test tool.
It specifies additional details of the diagnostic message format and communication for the ISO 9141-2,
ISO 14230-4 and SAE J1850 protocols. ISO 15031-5 supersedes those protocol standards.
— ISO 27145 (all parts) defines diagnostic data (emission-related systems, future safety related systems) to
be supported by vehicles in all countries implementing the GTR (Global Technical Regulation) into their
local legislation. The ISO 27145 series includes the definitions for a common data dictionary, provides
data definitions for emissions-related legislated diagnostics (reference to SAE J1930-DA, SAE J1979-
DA, SAE J2012-DA) and common message dictionary, provides the message implementation details
from ISO 14229-1 and ISO 14229-2, Unified Diagnostic Services (UDS) to support the required legislated
WWH-OBD. It also defines the details necessary to implement the communication between the vehicle’s
WWH-OBD systems and external test equipment including the definition/reference of physical layers, data
link layers, network layer, transport layer and session layer.
— ISO 22837 defines the reference architecture for probe vehicle systems and a basic data framework for
probe data. The basic data framework provides an initial set of probe data elements which are commonly
used in typical probe data enabled application domains, such as traffic, weather, and safety. The basic
data framework provides example probe messages, which define how probe data elements are combined
to convey information to a probe processing centre.
— ISO 22900-2 defines the Modular Vehicle Communication Interface (MVCI) D-PDU API to separate the
protocol data unit (PDU) from the vehicle specific protocols. This part of ISO 22900 is becoming the
diagnostic tool supplier’s choice to separate diagnostic data conversion and application test logic from the
vehicle communication.
— ISO 22901 (all parts) defines the Open Diagnostic data eXchange (ODX) format, which is a standard for
describing diagnostic related ECU data. This series of International Standards is becoming the vehicle
manufacturer’s choice to document vehicle system diagnostic data and protocol information.
— ISO 22902-5 and ISO 22902-6 define a multimedia and telematics standard based on the AMI-C
specification and reference documents for the automotive industry. The important logical element of the
architecture is a vehicle interface. The vehicle interface is defined as a component that provides access
to vehicle services from an AMI-compliant network. It may act as a gateway to the in-vehicle manufacturer
defined network or it may implement some or all of the vehicle services directly.
— ISO/TS 29284 defines the probe data format that is sent from vehicles depending on particular events.
The proposed Technical Specification defines events for, e.g. fog, snowfall, and accidents.
— SAE J2534 defines a standardized system for programming that includes a standard personal computer
(PC), standard interface to a software device driver, and an interface that connects between the PC and a
programmable ECU in a vehicle.
— SAE J2735 defines the interoperability among DSRC applications through the use of standardized message
sets, data frames and data elements. This International Standard provides the messages sets, data frames
and data elements to produce interoperable DSRC applications between Road Side Equipment (RSE) and
On-Board Equipment (OBE).
6.2 Standardized vehicle interface
6.2.1 Vehicle interface for ITS applications
Each International Standard (ISO 22837, ISO/TS 29284 and SAE J2735) defines messages sets, data frames
and data elements to produce interoperable ITS applications between Vehicle Station and Roadside Station.
Figure 4 illustrates that these International Standards do not include the access method to ‘1’ and ‘2’ from the
vehicle manufacturer’s in-vehicle network (vehicle domain architecture).
IMPORTANT — The vehicle interface does not include a standardized access method to data elements
from the in-vehicle network.
...
1 3
VM
Roadside Station
ECU 1 Message Dispatcher
4 5
Vehicle
Vehicle Vehicle
VM ITS-Station Communication
ITS-S ITS-S
ECU 2 Gateway Network
Host Router
Interface
Vehicle ITS-Station
(Host/Router)
VM
ECU n
Vehicle
Architecture
Key
1 Access method to data elements Vehicle Speed, Vehicle Acceleration from ECU 1
2 Access method to data element Brake Status from ECU n
3 Vehicle interface with non-standardized access methods to data elements of vehicle network
4 Standardized message including data elements Vehicle Speed, Vehicle Acceleration, Brake Status
5 Standardized message including data elements Vehicle Speed, Vehicle Acceleration, Brake Status
6 Short length packet message
Figure 4 — ISO 22837, ISO/TS 29284 and SAE J2735 based vehicle interface for ITS applications
6.2.2 Vehicle interface for multimedia and telematics
The ISO 22902 series provides network protocol requirements for vehicle interface access and a Common
Message Set (CMS). The network protocol requirements are focused on supporting access to vehicle services.
This series of International Standards does not include an access method to ‘1’, ‘2’ and ‘3’ from the vehicle
manufacturer’s in-vehicle network (vehicle domain architecture).
Figure 5 depicts the vehicle interface for multimedia and telematics.
Vehicle ITS-Station Gateway Interface Vehicle ITS-Station
Vehicle Mobile Host
Personal ITS-Station
Door Lock Telematics
data elements application
Vehicle
3 ND
ITS-S
Vehicle Speed Navigation
Router
...
data elements application
Diagnostic Diagnostic
data elements application
VM VM VM AMI-C AMI-C AMI-C
... ...
ECU 1 ECU 2 ECU n ECU 1 ECU 2 ECU n
Diagnostic Tool
Vehicle Architecture IEEE 1394 Automotive, Bluetooth
Key
1 Vehicle Speed data elements from ECU 1
2 Door Lock data elements from ECU 2
3 Diagnostic data elements from ECU n
Figure 5 — Vehicle interface for multimedia and telematics
8 © ISO 2012 – All rights reserved
IMPORTANT — The vehicle interface does not include a standardized access method to data elements
from the in-vehicle network.
6.2.3 Vehicle interface for diagnostics
ISO 15031 (all parts), ISO 27145 (all parts), and ISO 22901(all parts) do not include any definition of a vehicle
interface to support a standardized access method to the vehicle manufacturer’s in-vehicle network.
ISO 22900-2 and SAE J2534 define a standardized access method to the vehicle manufacturer’s in-vehicle network.
TM
SAE J2534 requires a Windows 32 bit DLL while ISO 22900-2 is independent.
Figure 6 illustrates ISO 22900-2 Modular VCI – D_PDU API used as the vehicle interface supporting
standardized access methods (PDU) to vehicle manufacturer’s in-vehicle network through Logical Link 1 (LL1)
between ECU 1 and the Modular VCI D-PDU API or Logical Link 2 (LL 2) between ECU 2 through the Vehicle
Gateway (optional) and the Modular VCI D-PDU API.
Vehicle ITS-Station
Vehicle Vehicle
ITS-S ITS-S
Vehicle Interface (MVCI)
Host Router
ISO 22900-2 MVCI D-PDU API
MVCI Protocol Module
Communication
ISO 22900-1 MVCI Hardware
Network
requirements
Personal ITS-Station
1 LL1 2 LL2
ND
...
Vehicle
Gateway
Diagnostic
application
VM VM VM
...
ECU 1 ECU 2 ECU n
Vehicle Architecture
Diagnostic Tool
Key
1 LL1 between MVCI D-PDU API and ECU 1
2 LL2 between MVCI D-PDU API and ECU 2 (only if Vehicle Gateway installed)
3 Optional Vehicle Gateway
4 TCP/IP on, e.g. IEEE 802.3 Ethernet
Figure 6 — Vehicle interface for diagnostics
IMPORTANT — The vehicle interface includes a standardized access method to data elements from
the in-vehicle network.
6.3 Vehicle interface diagnostic data configuration
ISO 22901 (all parts) defines the Open Diagnostic data eXchange (ODX) format.
One of the use cases defined in ISO 22901-1 is to optimize the ODX data describing the ECU diagnostic data stream
(diagnostic data elements) into a runtime format to setup the ISO 22900 Modular VCI. The ODX configuration file
enables the Modular VCI to communicate to the vehicle’s electronic systems and to interpret the message PDUs
being exchanged between the Modular VCI-compliant diagnostic system and the vehicle’s ECUs.
In the Modular VCI reference architecture, the tool supplier specific D-Server Kernel interprets the non-
standardized ODX optimized runtime format.
IMPORTANT — The D-Server Kernel is a very complex and powerful software and requires medium to
high end PC resources to operate properly and therefore does not fit the resource category of a V-ITS-SG.
Figure 7 depicts the ODX configuration of vehicle interface.
ODX Modular Vehicle
Tool Supplier
Format Communication
Specific ODX
Converter Interface
Runtime Data
1 5
Vehicle
ITS-S
ISO 22901-1 ODX
Gateway
ECU
description
VM VM VM
in ODX format .
ECU 1 ECU 2 ECU n
Vehicle Architecture
Key
1 ODX-ECU diagnostic data stream description (ISO 22901-1)
2 Software program to convert the ODX format into a target system optimized runtime format
3 Modular VCI tool supplier specific ODX optimized runtime format
4 Modular Vehicle Communication Interface (ISO 22900-2)
5 Represents the in-vehicle electronic system architecture designed by the vehicle manufacturer (VM)
Figure 7 — ODX configuration of vehicle interface
7 Single solution standardized access method
7.1 Functionality consolidation of vehicle interfaces into V-ITS-SG
Clauses 6.1 to 6.3 provide a brief overview of the content and basic principles of each International Standard.
All of the International Standards, except for ISO 22900-2, do not specify a standardized access method to data
elements from the in-vehicle network. This leads to vehicle interface supplier product specific implementations
which cannot be shared across the automotive and ITS industry.
10 © ISO 2012 – All rights reserved
This Technical Report specifies the functionality consolidation of the various vehicle interfaces into a “single
solution” concept for a “V-ITS-SG” which shall be connected to the CALM-compliant Vehicle Station (which
consists of a Vehicle Mobile Host and a Vehicle Mobile Router).
The V-ITS-SG requires a runtime optimized ODX configuration data file which meets the available resources
specified by the V-ITS-SG tool supplier.
The process and requirements on the use of ODX to support V-ITS-SG are specified in ISO 13185-3.
Figure 8 depicts the functionality consolidation of vehicle interfaces into V-ITS-SG.
functionality
ISO 22837, ISO/TS 29284 and SAE J2735
based vehicle interface
Vehicle ITS-S Gateway Interface
ISO 13185
VM VM VM
...
ECU 1 ECU 2 ECU n
Vehicle Architecture
Vehicle Interface for multimedia and
telematics
Vehicle ITS-S Gateway Interface
Door Lock Vehicle ITS-Station
Vehicle
data elements
ITS-S Gateway
(V-ITS-SG) TCP/IP
Vehicle Speed
Diagnostic
data elements data elements
Vehicle Vehicle
ITS-S ITS-S
Host Router
VM VM VM
...
ECU 1 ECU 2 ECU n
Vehicle Architecture
Converter
AMI-C AMI-C AMI-C
...
ECU 1 ECU 2 ECU n
IEEE 1394 Automotive, Bluetooth
Tool Supplier
Specific ODX
Runtime Data
Vehicle Interface for diagnostics
Vehicle Interface (MVCI)
ODX
ISO 22900-2 MVCI D-PDU API
Format
Converter
MVCI Protocol Module
ISO 22900-1 MVCI Hardware
requirements
ISO 22901-1 ODX
Vehicle ECU
Gateway
description
in ODX format
VM VM VM
...
ECU 1 ECU 2 ECU n
ODX configuration of
Vehicle Architecture
Vehicle ITS-S Gateway
Key
1 ISO 22837, ISO/TS 29284 and SAE J2735 based vehicle interface
2 Vehicle Interface for multimedia and telematics
3 Vehicle Interface for diagnostics
4 ODX configuration of V-ITS-SG
5 Vehicle ITS Station Gateway (V-ITS-SG)
6 vehicle data transfer protocol
7 Vehicle ITS Station: Vehicle ITS Station Host and Vehicle ITS Station Router
Figure 8 — Functionality consolidation of vehicle interfaces into V-ITS-SG
IMPORTANT — The single solution standardized access method specifies a vehicle data transfer
protocol which shall be implemented in any vehicle interface product from any supplier. It takes over
the role of the vehicle interface, hereinafter “V-ITS-SG”, of the existing standards and connects to the
CALM reference architecture-compliant Vehicle Station.
12 © ISO 2012 – All rights reserved
functionality
Vehicle
Protocol
functionality
7.2 Single solution vehicle interface for ITS applications
The concept specified in this Technical Report is backward compatible to the existing standards but specifies a
“single solution” for standardized access method to data elements from the in-vehicle network. The standardized
access method is specified in ISO 13185-2.
The V-ITS-SG technical requirements are specified in ISO 13185-2.
Figure 9 illustrates the V-ITS-SG as the “connector” between the “Road Vehicle technology” and the “ITS technology”.
ISO
Road Vehicle technology ITS technology
Personal ITS-Station
Vehicle Architecture ND
...
VM VM VM
...
ECM BCM ABS
7 1
Bluetooth enabled
Nomadic Device
Vehicle
TCP/IP
ITS-S
Central ITS-Station
Gateway
Vehicle Vehicle Vehicle
VM VM VM
Communication
ECU 1 ECU 2 . ECU n ITS-S ITS-S ITS-S
Network
Gateway Host Router
Central System
AMI
Vehicle ITS-Station
Vehicle Interface
Roadside ITS-Station
AMI AMI AMI
ECU 1 ECU 2 . ECU n
AMI Architecture
Converter
(Host/Router)
Key
1 Vehicle ITS Station: Vehicle ITS Station Host and Vehicle ITS Station Router
2 Personal ITS Station
3 Roadside ITS Station
4 Central ITS Station
5 Vehicle Architecture with optional VM gateway
6 Automotive Multimedia Interface Architecture
7 Firewall implemented in V-ITS-SG
8 Vehicle Protocol Converter to standardized vehicle data transfer protocol
Figure 9 — Single solution V-ITS-SG for ITS applications
IMPORTANT — The standardized access method and formatting of data elements from the in-vehicle
network takes place in the V-ITS-SG.
7.3 Vehicle Station and V-ITS-SG conceptual aspects and guidelines
Figure 10 illustrates six different areas of competence in the technology chain.
a) Road vehicle technology: this competence is occupied by the vehicle manufacturers and their electronic
system suppliers.
b) Vehicle interface technology: this competence is occupied by the diagnostic tool suppliers.
c) ITS Host Applications and Mobile Routing technology (Vehicle ITS Station): this competence is occupied
by the IT application and communication companies.
d) Short and Wide Range Communication technology: this competence is occupied by the IT
communication companies.
e) ITS Host Applications and Mobile Routing technology (Roadside ITS Station): this competence is occupied
by the IT application and communication companies.
Vehicle
Protocol
f) ITS Back Office technology: this competence is occupied by the ITS service provider companies.
The vehicle interface technology connects the road vehicle technology with the ITS technology.
IMPORTANT — The V-ITS-SG provides vehicle manufacturer/V-ITS-SG supplier controlled access to
vehicle data and functions. The ND software applications have a similar functionality compared to an
Internet browser.
ITS Host Application & Mobile ITS Host Application & Mobile
Road Vehicle Vehicle Interface Short & Wide Range ITS Back Office
Routing technology Routing technology
technology technology Communication technology technology
(Vehicle ITS-Station) (Roadside Station)
IAM Off-Board Configuration Roadside ITS-Station
Vehicle
ITS-S ND
Gateway
...
(Mobile Host/Router)
Vehicle ITS-Station
(Host/Router)
Central ITS-Station
Personal ITS-Station
ND Communication
Network
...
Bluetooth enabled
Nomadic Device
Central System
VM On-Board Configuration
TCP/IP
Vehicle
ITS-S Vehicle Vehicle
VM VM VM
ECU 1 ECU 2 . ECU n Gateway ITS-S ITS-S
Host Router
Vehicle ITS-Station
Vehicle Architecture
Figure 10 — Road vehicle to ITS technology chain
8 V-ITS-SG configuration
8.1 Overview of vehicle, Vehicle Stations, network and ITS services
This Technical Report specifies use cases and requirements to be supported by the vehicle interface (Vehicle
ITS Station Gateway) for provisioning and support of ITS services.
Figure 11 illustrates two configurations for a “Vehicle-ITS- Station” connected to a “V-ITS-SG”:
— The Independent Aftermarket (IAM) “Off-Board” configuration consists of a V-ITS-SG and a Vehicle Station
(Bluetooth connected CALM-compliant ND), which connects to the communication network to ITS services.
— The vehicle manufacturer (VM) “On-Board” configuration consists of a V-ITS-SG and a CALM-compliant
Vehicle ITS Station (Vehicle ITS Station Host and Vehicle ITS Station Router), which connects to the
communication network to ITS services.
14 © ISO 2012 – All rights reserved
VM VM VM
...
ECM BCM ABS
5 7
IAM Off-Board Configuration Roadside ITS-Station ITS Service Provider
#1 . #n
(Host/Router)
Vehicle
Vehicle
ND
ITS-S ITS-S
Gateway
Gateway
...
Vehicle ITS-Station
VM VM VM
...
Communication
ECU 1 ECU 2 ECU n
Network
Vehicle Architecture
VM On-Board Configuration
AMI Architecture
TCP/IP Central ITS-System VM RMI and Diagnostic
Services #1 . #n
Vehicle
AMI Vehicle
ITS-S
Vehicle Vehicle
Interface
Gateway Mobile Mobile
Host Router
Vehicle ITS-Station
Central System
AMI AMI AMI
... 4 6
ECU 1 ECU 2 ECU n
Key
1 represents the in-vehicle electronic system architecture designed by the VM
2 represents the Automotive Multimedia Interface (AMI) designed for aftermarket add-on components/systems
3 IAM “Off-Board” configuration
4 VM “On-Board” configuration
5 Roadside ITS Station
6 Central ITS Station System
7 ITS service provider back-office system
8 VM Repair and Maintenance Information (RMI) and diagnostic back-office system
Figure 11 — Configuration for a Vehicle ITS Station connected to a V-ITS-SG
8.2 CALM reference architecture-compliant configurations
8.2.1 CALM-compliant Vehicle ITS Stations
Figure 12 illustrates two different types of supported Vehicle ITS Stations:
a) the concept recommended to be applied by a consumer if the vehicle does not have any communication
network capabilities to utilize ITS services. In such case, it is recommended that the vehicle be equipped
with an IAM Off-Board configuration, which consists of a “V-ITS-SG and a CALM architecture-compliant
ND (Vehicle ITS Station)” (see arrow from box 3 to box 1).
b) the concept recommended to be applied by a VM if the vehicle is equipped with a V-ITS-SG and an “On-
Board CALM architecture-compliant Vehicle ITS Station” (see arrow from box 3 to box 2).
Security
IAM Off-Board Configuration
Vehicle
ITS-S ND
IAM
Gateway
...
installation
Vehicle ITS-Station
CALM reference architecture
Applications
Facilities
Communication
Network
Networking and
Transport
Access
Technologies
e.g. e.g. e.g.
BlueTooth GPS 2G/3G/.
VM
TCP/IP
installation Vehicle
ITS-S
Vehicle Vehicle
Gateway
ITS-S ITS-S
Host Router
Vehicle ITS-Station
VM On-Board Configuration
Key
1 IAM “Off-Board” configuration
2 VM “On-Board” configuration
3 CALM reference architecture
4 IAM “Off-Board” after sales installation of configuration referenced by 1
5 VM “On-Board”
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...