ISO 22902-1:2006

Road vehicles — Automotive multimedia interface — Part 1: General technical overview

ISO 22902-1:2006 is based on the AMI-C specifications and reference documents for the automotive industry. It is established to facilitate the development, promotion and standardization of automotive information and entertainment system interfaces to motor vehicle communication networks. The technical glossary is a compilation of terms and definitions used in AMI-C technical publications. The user guide describes the organization, classification and scope of the reference information for ISO documents. The architectural overview describes the structural, functional and applications views of the AMI-C architecture.

Véhicules routiers — Interface multimédia pour l'automobile — Partie 1: Vue d'ensemble technique générale

General Information

• Status: Withdrawn
• Publication Date: 23-Oct-2006
• Withdrawal Date: 23-Oct-2006
• ICS: 43.040.15 - Car informatics. On board computer systems
• Technical Committee: ISO/TC 22/SC 31 - Data communication
• Drafting Committee: ISO/TC 22/SC 31 - Data communication
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 02-Aug-2021
• Completion Date: 12-Feb-2026

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 22902-1
First edition
2006-11-01
Road vehicles — Automotive multimedia
interface —
Part 1:
General technical overview
Véhicules routiers — Interface multimédia pour l'automobile
Partie 1: Vue d'ensemble technique générale

Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2006
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 [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2006 – All rights reserved

Contents Page
Foreword. iv
1 Scope . 1
2 Normative references . 1
3 Terms and definitions. 2
3.1 Terms and definitions. 2
3.2 Abbreviations . 11
4 Introduction to the User Guide. 13
5 General architecture. 13
5.1 Architectural views. 13
5.2 Structural view . 13
5.3 Functional view. 19
5.4 Application view of the architecture. 24
6 System architecture configurations . 27
7 Relationship between uses cases and interface specifications. 27

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.
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 22902-1 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
ISO 22902 consists of the following parts, under the general title Road vehicles — Automotive multimedia
interface:
⎯ Part 1: General technical overview
⎯ Part 2: Use cases
⎯ Part 3: System requirements
⎯ Part 4: Network protocol requirements for vehicle interface access
⎯ Part 5: Common message set
⎯ Part 6: Vehicle interface requirements
⎯ Part 7: Physical specification

iv © ISO 2006 – All rights reserved

INTERNATIONAL STANDARD ISO 22902-1:2006(E)

Road vehicles — Automotive multimedia interface —
Part 1:
General technical overview
1 Scope
This multimedia and telematics standard is based on the AMI-C specifications and reference documents for
automotive industry.
It is established to facilitate the development, promotion and standardisation of automotive information and
entertainment system interfaces to motor vehicle communication networks.
Technical glossary is a compilation of terms and definitions used in AMI-C technical publications.
User guide describes the organisation and classification and scope of the reference information for ISO
specifications listed below.
Architectural overview describes the structural, functional, and applications views of the AMI-C architecture.
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 22902-2, Road vehicles — Automotive multimedia interface — Part 2: Use cases
ISO 22902-3, Road vehicles — Automotive multimedia interface — Part 3: System requirements
ISO 22902-4, Road vehicles — Automotive multimedia interface — Part 4: Network protocol requirements for
vehicle interface access
ISO 22902-5, Road vehicles — Automotive multimedia interface — Part 5: Common message set
ISO 22902-6, Road vehicles — Automotive multimedia interface — Part 6: Vehicle interface requirements
ISO 22902-7, Road vehicles — Automotive multimedia interface — Part 7: Physical specification
3 Terms and definitions
For the purposes of all parts of ISO 22902, the following terms and definitions apply.
3.1 Terms and definitions
3.1.1
1394 Automotive
the automotive version of IEEE 1394 network technology
3.1.2
AMI-C component
component that meets AMI-C specification(s)
3.1.3
AMI-C guideline
AMI-C statement of what should be done on a subject for which AMI-C adopts a standard or specification from
another organization
3.1.4
AMI-C recommendation
AMI-C guideline that AMI-C proposes to another organization for adoption
3.1.5
AMI-C requirement
requirement of one or more interfaces for one or more elements in the architecture; requirements do not
address performance and quality issues
3.1.6
AMI-C specification
automotive multimedia interface specification published for connecting or implementing information,
communication, entertainment systems to motor vehicles
3.1.7
Application
distinct executable software element that provides functionality or utility to a user
3.1.8
architecture
description of the key elements of a system, their functions, and the interrelationships among the elements
3.1.9
ASN.1 Reference
the AMI-C CMS has been developed in ASN.1. In this textual document the messages are presented in a
tabular format for readability. The CMS in ASN.1 is available as a download from the AMI-C web site,
although ASN.1 has a large number of type definitions, only the following definitions are used in
the AMI-C CMS
3.1.10
audio Gateway
[Bluetooth] device embedded with the Bluetooth transceiver that serves as the gateway (access) to the phone
audio for both input and output; typically, devices acting as audio gateways are cellular or mobile phones
these devices are implemented with the Hands-Free Profile
3.1.11
boolean
logical values TRUE and FALSE
2 © ISO 2006 – All rights reserved

3.1.12
bundle
[software] mechanism to organize the delivery of software to the platform/OSGi framework
3.1.13
common message set
CMS
sequence of network messages between two functional modules that enable the exchange of data
3.1.14
Car Communication Application Promotion
CCAP
Bluetooth Hands-Free phone application guideline for implementers to improve device interoperability and
enhance customer convenience by providing consistent user experience
3.1.15
choice
between types
3.1.16
common mode bulk current injection
CBCI
test method used to determine a component’s or subsystem’s immunity to electromagnetic fields, “common
mode” refers to the phase at which the signal is applied
3.1.17
commonality
the possession, along with one or more other systems, of a certain attribute or set of attributes: the
characteristic of being a shared feature or attribute
3.1.18
component
a device that is one of the individual parts of which a vehicle is made up; especially a part that can be
separated from or attached to a system
3.1.19
configure-ability
characteristic of a system that supports the rearrangement of features and attributes to support different
features and uses
3.1.20
consumer connector
connector intended for use in applications where the consumer regularly mates and un-mates the connector
for the purpose of installing and removing components or devices

Figure 1 — Consumer device connection — General configuration
3.1.21
consumer convenience port
CCP
connection point for portable consumer devices to connect to an AMI-C network
3.1.22
controllers
computer-based units performing a dedicated function or feature
NOTE They frequently use network devices to gather information to control a system.
3.1.23
custom access adaptor
interface device between an AMI-C interface connector and an embedded device to a customer access
connector
3.1.24
customer access connector
the connector accessible to a driver or passenger for the connection of an external or consumer device to an
AMI-C compliant network system
NOTE It provides access to the system signal set (power, network data, power mode, etc.).
3.1.25
device
low-level components with little or no programmable intelligence
NOTE They are generally driven by other components and customer commands.
3.1.26
differential Mode Bulk Current Injection
DBCI
test method used to determine a component’s or subsystem’s immunity to electromagnetic fields
NOTE Differential mode refers to the phase at which the signal is applied.
3.1.27
embedded
components or devices that are installed by the automaker
3.1.28
embedded component
component installed in a vehicle by the vehicle manufacturer or service technician using conventional wiring
and mounting technologies
3.1.29
embedded connector
separable interface that is an integral part of an embedded component or device
3.1.30
execution environment
(see software execution environment)
3.1.31
expandability
characteristic of a system that supports and/or facilitates the addition of new features and capabilities
4 © ISO 2006 – All rights reserved

3.1.32
functional module
FM
an abstraction within the AMI-C network architecture that is used to address a device
EXAMPLE Audio-related functions such as accessing vehicle audio resources, changing volume, etc., are grouped
in an audio functional module.
3.1.33
gateway
interface between two networks carrying different protocols
3.1.34
Hands-Free Car Kit
HFCK
[Bluetooth] car kit composed of two major components:
⎯ Hands-Free Unit (HFU): Device that the customer can use without need to manipulate by hands, the most
well-known is hand free phone;
⎯ User Interface (UI): Appropriate interface to facilitate complete phone operations from the hands-free unit.
3.1.35
Hands-Free Profile
HFP
[Bluetooth] specification defining the minimum set of functions required to use a mobile phone together with a
hands-free device in a car via a Bluetooth link
3.1.36
Hands-Free Unit
HFU
[Bluetooth] device embedded with the Bluetooth transceiver and implemented with the Bluetooth Hands-Free
Profile
NOTE The device serves as a remote unit to the audio gateway. It provides audio input, output and control functions
of the audio gateway over the Bluetooth link.
3.1.37
host
general-purpose computers having the capability to execute a variety of application software
NOTE Hosts easily allow a user to select and change software on demand.
3.1.38
implementation
physical realization of a specification or specifications
3.1.39
instance number
I-Num
a number statically or dynamically assigned to each functional module that shares the same function type
3.1.40
interchangeability
characteristic of a system that allows hardware and/or software components to be replaced by other
components with no perceptible change in system function or performance
3.1.41
integer
whole numbers (positive or negative), possibly named
3.1.42
interoperability
characteristic of providing an intended function in coordination with other components, the characteristic of
sharing information with other system functions or components to provide additional functionality
3.1.43
isochronous data
data that arrive at the destination at the same rate that they leave the source; the word “isochronous” means
“of equal time”; isochronous data are used for streaming video and audio data
3.1.44
L2CAP
(see Logical Link Control and Adaptation Protocol)
3.1.45
link key
[Bluetooth] authentication key used to establish a link between devices
3.1.46
listener
[software] Java object that responds to external events such as a change in the host operating state OR an
application with a well-defined interface that does something useful for another application of a user
3.1.47
local functional modules
functional modules that are within the same AMI-C component
3.1.48
logical address
address used to identify a functional module and is made up of the combination of F-Type and I-Num
3.1.49
Logical Link Control and Adaptation Protocol
L2CAP
protocol supporting higher level protocol multiplexing, packet segmentation and reassembly, and the
conveying of quality of service information
3.1.50
object body
has, Message Type (Msg Type), Message Class, Object Type and Operand
3.1.51
object type
an identification of object in a functional module
EXAMPLE In the case of body module, mirror, window, seat and so on.
3.1.52
octet string
byte strings
3.1.53
enumerated
enumeration of identifiers (state of a machine, for instance)
3.1.54
operand
data in a message
6 © ISO 2006 – All rights reserved

3.1.54.1
message type
there are six kinds of message type for application messages; INQUIRE, REPORT, SET, CONFIRM,
COMMAND, and WARNING
3.1.54.2
message class
the message class shows a class within which a message is comprised, the message class defines thirteen
types:
⎯ Management – Network device management, audio/video stream management, and service discovery.
⎯ Core – Information that are originally inherent in a vehicle (VIN, static configuration information, etc.).
⎯ Body Module – Control and status related with body module (window, seat, mirror, light, trip meter,
vehicle speed, etc.).
⎯ Powertrain – Status related with powertrain (Oil temperature, coolant temperature, gear, etc.).
⎯ Vehicle Diagnostics – Message for vehicle diagnostic (ISO 15031-5 emission related, ISO 14229-1 non
emission related).
⎯ Amplifier – Control related with amplifier and codec (volume, fade/balance, codec, etc.).
⎯ General Player – Common functions for disk and tape player.
⎯ Disk Media – Audio/video player for disk media (CD, MD, DVD, MP3, etc.).
⎯ Tape Media – Audio/video player for tape media (audio tape, VCR, etc.).
⎯ Tuner – Audio/video broadcast tuner (AM, FM, XM, TV, etc.).
⎯ General Phone – Basic phone functionality (dial, hang-up, phone book, etc.).
⎯ Advanced Phone – Advanced phone functionality (short message, multi party call, conference call, etc.).
⎯ Text Display – Command to display simple texts and input texts.
3.1.55
mode
the power level of a system, modes include ON, OFF, and SLEEP; a system is in a mode, a device or a
component is in a state
3.1.56
modularity
exhibiting separable functions embodied within discrete and removable hardware or software components or
modules
3.1.57
MSC
Modem Status Command
3.1.58
network adaptation layer
network layer that adapts the messages from the functional modules to those of the network specific layer and
resolves addressing issues (optional use of a registry)
3.1.59
network transport layer
network layer that puts network transactions in packets according to the network transport protocols of the
specific network
3.1.60
network transaction
sequence of network messages between two functional modules enabling the exchange of data
3.1.61
network transaction
CBCI
See common mode bulk current injection
3.1.62
NULL
Includes the single value NULL, used for delivery report or some alternatives of the CHOICE type (particularly
for the recursive types)
3.1.63
operability
the capability of being used or operated effectively to provide an intended result or function
3.1.64
pairing
[Bluetooth] the creation and exchange of a link key between two devices; the devices use the link key for
future authentication when exchanging information
3.1.65
PMODE line
signal wire used to control and sense wake-up and sleep states in an AMI-C system
3.1.66
PMODE signal
signal carried by the PMODE line or optionally a signal on the AMI-C network identifying the power mode of
the network
3.1.67
portability
characteristic of a component or a solution that allows it to be used effectively in multiple locations or
application venues
3.1.68
preference
default value preferred by a user, such as a radio preset value
3.1.69
preference service
service that returns the preferences for a given vehicle occupant
3.1.70
proof-of-concept implementation
implementation to validate requirements and/or specifications
3.1.71
radio frequency communication
[Bluetooth] the radio frequency oriented emulation of an RS232 serial communication over an L2CAP channel
8 © ISO 2006 – All rights reserved

3.1.72
reference implementation
fully functional implementation against which other implementations can be evaluated
3.1.73
registry
address-mapping table between the logical address of a functional module and the specific network address
of a component that contains this functional module
3.1.74
remote functional modules
functional modules that are in separate AMI-C components
3.1.75
requirement
statement of something that shall be followed for a particular purpose; an essential condition, it may not have
technical details for implementation
3.1.76
resource manager
a functional module that contains the ability to perform the following functions:
⎯ Provide dynamic I-Nums to the (FMs) that request them when a new component joins the network.
⎯ Deallocate the I-Nums of the FMs that belong to a component that unplugs from the network.
⎯ Allocate the multicast group ID when requested.
3.1.77
run level
the execution state of a multimedia system in a vehicle
3.1.78
run time environment
the total set of software running on a computing platform that supports the execution of applications/programs
on that platform
3.1.79
scooping
undesirable condition in which the female connector housing assembly makes contact with the male terminals
during the improper insertion of the female connector housing assembly into the male connector housing
assembly
3.1.80
security
the characteristic of being free of risk or danger
3.1.81
sequence
ordered structure of values of (generally) different types
3.1.82
sequence of
ordered structure of values of the same type
3.1.83
service
software that provides a useful function to another entity
3.1.84
Service Level Connection
SLC
[Bluetooth] the synchronized high-level connection that refers to the presence of a RFCOMM connection, and
assumes that the Hands-Free Unit has synchronized itself to the state of the AG using the specified Service
Level Connection initialization procedure
3.1.85
software execution environment
the set of Java classes that are present on the platform where Java program runs
3.1.86
specification
detailed, exact statement of required particulars, especially a statement prescribing the construction, operating
environment, functions, performance, or quality of a product
3.1.87
specific network
one of the networks either endorsed by AMI-C or determined to be a candidate for later endorsement by
AMI-C
3.1.88
start level
OSGi defined state that constrains the order in which services are started when the system boots
3.1.89
state
the power and activity level of an AMI-C device, these include ON, OFF, and SLEEP; contrast with mode,
system is in a mode and device is in a state
3.1.90
subscription
subscription is a service that allows a requestor to register for updates to a parameter without explicitly
requesting each update.
NOTE There are two types of Subscription services, Periodic and Notification. Periodic Subscription is one where the
basis for a message being sent is the expiration of a timer, and a Notification Subscription is one where the basis for the
transmission of the message is that the parameter contained in the message has changed.
3.1.91
Synchronous Connection Oriented
SCO
one of the two Bluetooth data link types; a synchronous (circuit-switched) connection is used for full duplex
audio communication between two devices
3.1.92
system transaction
data transaction performed by a component control module and characterized by its Sys bit field (in the AMI-C
header) set to ‘1’B; it is always broadcasted
3.1.93
testability
the ease of being tested for proper function(s) against some predefined criteria
3.1.94
upgradeability
characteristic of a system that allows the replacement of existing hardware and/or software components or
modules for improved or extended performance
10 © ISO 2006 – All rights reserved

3.1.95
vehicle interface
interface between the system and the vehicle manufacturer’s proprietary systems, information, and signals
3.1.96
vehicle services interface
proper subset of a vehicle interface that provides access to services commonly found on body and/or chassis
networks
3.2 Abbreviations
‘0101’B
binary string
(1.255)
1 to 255
(1 | 255)
1 or 255; “…”: new objects may dynamically be added
3.2.1
AG
see Audio Gateway
3.2.2
API
application programming interface
3.2.3
ASP
application service provider
3.2.4
CCAP
see Car Communication Application Promotion
3.2.5
CCP
see consumer convenience port
3.2.6
CISPR
Comité Internationale Spécial des Perturbations Radioelectrotechnique (IEC committee)
3.2.7
‘EF35’H
hexadecimal string
3.2.8
HFCK
see Hands-Free Car Kit
3.2.9
HFP
see Hands-Free Profiles
3.2.10
HFU
See Hands-Free Unit
3.2.11
HMI
human machine interface
3.2.12
MD
mini-disk
3.2.13
OCTET STRING [SIZE(8)]
eight-bytes string
3.2.14
OEM
original equipment manufacturer. In the automotive industry, OEM represents vehicle manufacturers
3.2.15
PAP
see Phone Access Profile
3.2.16
POF
Plastic Optic Fiber
3.2.17
PN
[Bluetooth] Parameter Negotiation
3.2.18
RFCOMM
Radio Frequency Communication
3.2.19
RPN
[Bluetooth] Remote Port Negotiation
3.2.20
SABM
[Bluetooth] Set Asynchronous Balanced Mode
3.2.21
SCO
see Synchronous Connection Oriented
3.2.22
UI
user interface
3.2.23
SLC
see Service Level Connection
3.2.24
VR
voice recognition
3.2.25
VSP
vehicle service provider
12 © ISO 2006 – All rights reserved

4 Introduction to the User Guide
To bring existing open technologies into automotive environment, the subject ISO specifications are provided:
ISO 22902-2, ISO 22902-3, ISO 22902-4, ISO 22902-5, ISO 22902-6.
The specifications can be used directly, and have adapted other available specifications by modifying them or
supplementing them with additional technical contributions to make the technologies compatible with the
vehicle environment. The adopted, adapted or created specifications include required technical elements that
were not available in the existing body of work.
The following connections and relationships among the ISO specifications are worth noting:
1) Vehicle interface, network and host are three architectural components of AMI-C architecture.
2) Among them, the vehicle interface (ISO 22902-6 Vehicle interface requirements) is a required
component.
3) AMI-C physical specification is applicable to all implementations of ISO 22902-4 Network protocol
boundary requirements and ISO 22902-6 Vehicle interface requirements.
4) ISO 22902-2 Use cases is an informational document used to help non-technical readers understand
the context of the specifications developed. The use cases examined are neither an exhaustive or
all-inclusive set, but rather a common set of examples for illustrative purposes.
ISO 22902-3 is a general technical reference, and is not a detailed requirements document. The purpose of
this information is to identify the general system characteristics implicit in the architecture provided by the
other specifications.
5 General architecture
The AMI-C architecture is the framework upon which the AMI-C system is formulated and configured. This
framework defines how the various components of an AMI-C system are interconnected, how the system
logically operates, and how the system meets the AMI-C system requirements.
5.1 Architectural views
An architectural view is a representation of the AMI-C system from the perspective of a related set of concerns.
The views used in this document are structural, functional and application views. Each of these architectural
views responds to different types of inquiries about the architectural description. The views and related inquiry
types are as follows:
⎯ Structural view addresses logical elements and how they inter-relate.
⎯ Functional view addresses what the system does and what the basic behavioral aspects are.
⎯ Application view addresses how the architecture enables applications and implementations to access
services.
5.2 Structural view
The logical elements of the architecture are:
⎯ Vehicle interface – An interface to other vehicle systems, information, and signals.
⎯ Network(s) – Standard network and message set to provide data interchange and control between
components.
⎯ Network protocols and services.
⎯ Network nodes: devices, controllers and gateways.
⎯ Host – Computer used to execute cross-platform, downloadable application code.
⎯ System services.
⎯ Applications.
An actual implementation of the architecture shall have a vehicle interface, and may have one or more
networks and/or one or more hosts.
5.2.1 Vehicle interface
The Vehicle Interface (VI) is the only required component of the architecture. The VI is the interface between
the manufacturer’s proprietary systems and the system. While the VI performs functions traditionally ascribed
to a gateway, it does so in a way that does not reveal any of the protocols, addressing mechanisms, physical
devices or functional partitioning of the manufacturer’s proprietary systems.
The VI creates for devices a standard interface to information and services from the manufacturer specific
portions of the vehicle. To other devices on the network, the VI appears as a black box. This approach
enables the VI to provide a measure of security to the proprietary side of the vehicle. Since the services of the
vehicle are exposed through the VI’s standard interface, devices never have direct communication with
manufacturer specific devices. The VI receives requests for information or services, translates them into
appropriate messages and/or protocols, and then forwards the requests to the proprietary network.
Additionally, the VI provides information regarding the required power status of the network. This includes the
control of specific hardware to control the power moding of networks and devices, if required by individual
networks. The VI functions are also made available to applications running on hosts through an appropriate
API.
Vehicle services provide devices and applications with three main mechanisms for retrieving information or
performing command functions:
⎯ Request/command: The request/command mechanism consists of a single command to a service
target, or request for information from a device on the proprietary side of the vehicle. The command
may b
...