Configurable car infotainment services (CCIS) - Part 4: Protocol

IEC TR 63246-4:2022 describes the CCIS protocol, which includes the protocol messages, parameters and procedures performed by protocol entities. This part is informative; its intent is to provide information that can be considered in order to implement the CCIS protocol.

General Information

Publication Date
Current Stage
PPUB - Publication issued
Start Date
Completion Date
Ref Project

Buy Standard

Technical report
IEC TR 63246-4:2022 - Configurable car infotainment services (CCIS) - Part 4: Protocol Released:12/14/2022
English language
27 pages
sale 15% off
sale 15% off

Standards Content (Sample)

IEC TR 63246-4

Edition 1.0 2022-12

Configurable car infotainment services (CCIS) –
Part 4: Protocol
IEC TR 63246-4:2022-12(en)

---------------------- Page: 1 ----------------------
Copyright © 2022 IEC, Geneva, Switzerland

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 IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé
CH-1211 Geneva 20

About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - IEC Products & Services Portal -
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always
committee, …). It also gives information on projects, replaced have access to up to date content tailored to your needs.
and withdrawn publications.

Electropedia -
IEC Just Published -
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 300 terminological entries in English
details all new publications released. Available online and
and French, with equivalent terms in 19 additional languages.
once a month by email.
Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Customer Service Centre -

If you wish to give us your feedback on this publication or
need further assistance, please contact the Customer Service

---------------------- Page: 2 ----------------------
IEC TR 63246-4


Edition 1.0 2022-12



Configurable car infotainment services (CCIS) –

Part 4: Protocol




ICS 33.160.99; 43.040.15 ISBN 978-2-8322-6225-2

  Warning! Make sure that you obtained this publication from an authorized distributor.

® Registered trademark of the International Electrotechnical Commission

---------------------- Page: 3 ----------------------
– 2 – IEC TR 63246-4:2022 © IEC 2022
1 Scope . 8
2 Normative references . 8
3 Terms and definitions . 8
4 General . 8
5 Message . 9
5.1 Message format . 9
5.1.1 General . 9
5.1.2 Version . 10
5.1.3 Message type . 10
5.1.4 Payload length . 10
5.1.5 Sequence number. 10
5.1.6 Cookie . 10
5.1.7 Payload . 10
5.2 Message type . 10
5.2.1 Format . 10
5.2.2 Service . 10
5.2.3 Class . 11
5.2.4 Operation . 11
5.2.5 Types of CCIS messages . 12
6 Parameters . 13
6.1 General . 13
6.2 Broadcasting – Broadcasting_Master_Information . 13
6.3 Authority and Certification . 13
6.3.1 General . 13
6.3.2 Certification_Information_Request . 13
6.3.3 Certification_Information_Response . 13
6.3.4 Authority_Check_Request . 14
6.3.5 Authority_Check_Response . 14
6.3.6 Authority_Check_Confirmation . 14
6.4 Client registration. 14
6.4.1 General . 14
6.4.2 Client_Registration_Request . 14
6.4.3 Client_Registration_Response . 14
6.5 Device registration . 15
6.5.1 General . 15
6.5.2 Device_Identity_Notification. 15
6.5.3 Device_Discovery_Notification . 15
6.5.4 Device_Registration_Authentication . 15
6.5.5 Device_Registration_Request . 15
6.5.6 Device_Registration_Response . 16
6.5.7 Device_Registration_Confirmation . 16
6.6 Device monitoring . 16
6.6.1 General . 16
6.6.2 Device_Status_Report . 16

---------------------- Page: 4 ----------------------
IEC TR 63246-4:2022 © IEC 2022 – 3 –
6.6.3 Device_Status_Request . 17
6.6.4 Device_Status_Response . 17
6.6.5 Device_Status_Query . 17
6.7 Device control . 17
6.7.1 General . 17
6.7.2 Device_Occupation_Request . 17
6.7.3 Device_Occupation_Response . 18
6.7.4 Device_Control_Request . 18
6.7.5 Device_Control_Transmission . 18
6.7.6 Device_Control_Confirmation . 18
6.7.7 Device_Control_Response . 18
6.8 Content delivery . 18
6.8.1 General . 18
6.8.2 Contents_Delivery_Request. 19
6.8.3 Contents_Delivery_Notification . 19
6.8.4 Contents_Delivery_Confirmation . 20
6.8.5 Contents_Delivery_Response . 20
7 Procedures . 20
7.1 General . 20
7.2 CCIS user . 20
7.3 CCIS device . 21
7.4 CCIS master . 22
7.4.1 Initialization . 22
7.4.2 Client registration and certification . 22
7.4.3 Device registration . 23
7.4.4 Device monitoring . 24
7.4.5 Device control. 25
7.4.6 Content delivery . 25
Bibliography . 27

Figure 1 – Protocol stack for CCIS . 9
Figure 2 – Message format of CCIS protocol . 9
Figure 3 – Format of message type field . 10
Figure 4 – State transitions of CCIS users . 21
Figure 5 – State transitions of CCIS device . 22
Figure 6 – State transition of CCIS master in initialization process . 22
Figure 7 – States transitions of CCIS master in client registration and certification . 23
Figure 8 – State transitions of CCIS master in device registration . 23
Figure 9 – State transitions of CCIS master in device monitoring . 24
Figure 10 – State transitions of CCIS master in device control . 25
Figure 11 – State transitions of CCIS master in content delivery . 26

Table 1 – Services indicated by message type . 11
Table 2 – Classes indicated by message type . 11
Table 3 – Operations indicated by message type . 12
Table 4 – Messages used for CCIS protocol . 12

---------------------- Page: 5 ----------------------
– 4 – IEC TR 63246-4:2022 © IEC 2022
Table 5 – Messages and parameters for authority and certification . 13
Table 6 – Messages and parameters for client registration . 14
Table 7 – Messages and parameters for device registration . 15
Table 8 – Messages and parameters for device monitoring . 16
Table 9 – Messages and parameters for device control . 17
Table 10 – Messages and parameters for content delivery . 19

---------------------- Page: 6 ----------------------
IEC TR 63246-4:2022 © IEC 2022 – 5 –


Part 4: Protocol

1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC Publication(s)"). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent
rights. IEC shall not be held responsible for identifying any or all such patent rights.
IEC TR 63246 has been prepared by the technical area 17: Multimedia systems and equipment
for vehicles, of IEC technical committee 100: Audio, video and multimedia systems and
equipment. It is a Technical Report.
The text of this Technical Report is based on the following documents:
Draft Report on voting
100/3638/DTR 100/3823/RVDTR

Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this Technical Report is English.
A list of all parts in the IEC 63246 series, published under the general title Configurable car
infotainment services (CCIS), can be found on the IEC website.

---------------------- Page: 7 ----------------------
– 6 – IEC TR 63246-4:2022 © IEC 2022
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at The main document types developed by IEC are
described in greater detail at
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.

---------------------- Page: 8 ----------------------
IEC TR 63246-4:2022 © IEC 2022 – 7 –
The market for car infotainment services (also known as "in-vehicle infotainment systems") has
been growing rapidly, as reflected by the growth of the associated industries. It is expected that
a variety of car infotainment (or multimedia) devices and services will be developed in the future.
Such devices include navigation, cameras, speakers, headrest displays, air-conditioners,
thermometers, heated seats, and lights. It is also expected that some devices will be developed
to provide 4-dimensional experiences for users.
Car infotainment systems typically include A/V features (such as standard radio and CD players),
and two-way communications tools, as well as hands-free phone connections, vehicle voice
commands, and other types of interactive audios or videos. Car infotainment systems have
evolved to allow passengers to watch movies and other visual media (for example, DVD players
installed on the rear seats). Another distinctive feature of future car infotainment systems is
mobile device connectivity. Newer vehicles provide a wide range of systems that allow devices
(e.g. smartphones and laptops) to be connected to a variety of services embedded in the vehicle.
From this observation, there is a crucial need for standardization to provide car infotainment
users with more enhanced services so as to easily manage and control infotainment devices as
well as content within a car.
The purpose of the IEC 63246 series is to specify the general considerations, requirements,
framework, and protocols to provide car users with the functionality of managing and controlling
device and content resources within a car.
The IEC 63246 series consists of the following parts:
– Part 1: General;
– Part 2: Requirements;
– Part 3: Framework; and
– Part 4: Protocol.
IEC 63246-1 describes the general considerations of CCIS, which includes the CCIS system
model and the types of CCIS users with the associated service flows.
IEC 63246-2 describes the requirements for CCIS, which include the CCIS functional entities,
the communication model, and the functional requirements.
IEC 63246-3 describes the CCIS framework, which includes the information flows between
functional entities and the CCIS operations, such as registration, device monitoring and control,
and data transfer.
IEC 63246-4 describes the CCIS protocol, which includes the protocol messages and
parameters, protocol procedures, implementation guidelines, etc.

---------------------- Page: 9 ----------------------
– 8 – IEC TR 63246-4:2022 © IEC 2022

Part 4: Protocol

1 Scope
This part of IEC 63246 describes the CCIS protocol, which includes the protocol messages,
parameters and procedures performed by protocol entities. This part is informative; its intent is
to provide information that can be considered in order to implement the CCIS protocol.
2 Normative references
The following document is referred to in the text in such a way that some or all of their content
constitutes requirements 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.
IEC 63246-1, Configurable Car Infotainment Services (CCIS) – Part 1: General
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 63246-1 apply.
ISO and IEC maintain terminology databases for use in standardization at the following
• IEC Electropedia: available at
• ISO Online browsing platform: available at
4 General
The CCIS services are provided in collaboration with the protocol entities: CCIS users, CCIS
master, and CCIS devices. CCIS master manages and controls the CCIS services by interaction
with CCIS users and devices. CCIS devices can support multimedia contents for CCIS services.
To provide CCIS services, a set of CCIS functional operations are performed by the protocol
entities, which include registration, authentication, device control, device monitoring, profile
management, and content delivery. These functional operation flows are described in
IEC 63246-3. This document describes the protocol for CCIS services (represented as the CCIS
protocol), which are based on the other parts of CCIS (IEC 63246-1, IEC 63246-2 and
IEC 63246-3).
Figure 1 describes a reference protocol stack for CCIS among the protocol entities. The CCIS
protocol is an application-layer protocol that can be used to provide the CCIS services. The
well-known Transmission Control Protocol (TCP) and Internet Protocol (IP) can be used as the
underlying protocol for delivery of CCIS messages in the networks. Any other transport protocol
can be used for delivery of CCIS messages, instead of TCP/IP. For example, a low-power CCIS
device can use its own dedicated protocol for message delivery, or it can deliver the CCIS
message by using the lower-layer protocol, without using the TCP/IP protocols. As for the lower-
layer protocols, any kinds of Medium Access Control (MAC) and Physical layer protocol (PHY)
can be used, which can typically include the IEEE 802.11 Wireless Local Area Network (WLAN)
and the IEEE 802.15 Wireless Personal Area Network (WPAN) technologies.

---------------------- Page: 10 ----------------------
IEC TR 63246-4:2022 © IEC 2022 – 9 –

Figure 1 – Protocol stack for CCIS
This Technical Report describes information that can be referred to for implementation of the
CCIS protocol. The CCIS protocol or its implementation can depend on the choice of the CCIS
service providers.
This Technical Report specifies the CCIS protocol that is an application-layer protocol used to
provide CCIS services between the CCIS user and the CCIS master, or between the CCIS
master and CCIS devices. For this purpose, the messages for the CCIS protocol are described
in Clause 5, which includes the message format, the types of messages, and the parameters
associated with the messages. Based on the messages, the protocol procedures are described
in Clause 6, which includes the protocol operations that will be performed by each protocol
entity: user, master, and device. The overall operational flows for CCIS operations are
described in IEC 63246-3.
5 Message
5.1 Message format
5.1.1 General
Each CCIS protocol message consists of the 12-byte header and the data payload of variable
length, as shown in Figure 2. The 12-byte header consists of the following fields: version (4
bits), message type (12 bits), payload length (16 bits), sequence number (32 bits), and cookie
(32 bits).

Figure 2 – Message format of CCIS protocol

---------------------- Page: 11 ----------------------
– 10 – IEC TR 63246-4:2022 © IEC 2022
5.1.2 Version
A 4-bit unsigned integer is used to indicate the version number of this CCIS protocol. The
current version of this specification shall be set to 1 (0x01). Other values are reserved for future
5.1.3 Message type
A 12-bit unsigned integer is used to indicate the type of this message, which is described in 5.2.
5.1.4 Payload length
A 16-bit unsigned integer is used to indicate the length (in byte) of the payload contained in this
message, except the 12-byte header.
5.1.5 Sequence number
A 32-bit unsigned integer is used to indicate the sequence number of this message. This field
can be used to detect the message loss or duplication during message transmission. This field
initially begins with 1 and increases by 1, whenever a new message is generated. When the
sequence number reaches 2 − 1, its subsequent sequence value will be 0.
5.1.6 Cookie
A 32-bit unsigned integer is used to indicate a cookie. This cookie information is used to
determine whether a pair of messages corresponds to the same transaction flow (request-
response). For example, a request message and its corresponding response message must
have the same cookie value. A cookie value (other than 0) is randomly generated by the
requester of the concerned messages.
The cookie value 0 represents that no response is needed for the requesting message. For
example, the periodically or repeatedly messages can have the cookie value of 0.
5.1.7 Payload
This variable-length field is used to represent the data payload information, which depends on
the message type.
5.2 Message type
5.2.1 Format
The message type is determined by combination the three 4-bit subfields: service, class, and
operation. Figure 3 shows the format of message type.

Figure 3 – Format of message type field
5.2.2 Service
The service field, a 4-bit unsigned integer, is used to represent the associated service
operations: broadcasting (0), authentication and certification (1), client registration (2), device
registration (3), device control (4), device monitoring (5), or content delivery (6).

---------------------- Page: 12 ----------------------
IEC TR 63246-4:2022 © IEC 2022 – 11 –
Table 1 shows the service value currently defined in this specification. The remaining values
ranging from 7 to 15 are reserved for future use.
Table 1 – Services indicated by message type
Services Value
Broadcasting 0
Authentication and certification 1
Client registration 2
Device registration 3
Device monitoring 4
Device control 5
Content delivery 6
Reserved 7 to 15

5.2.3 Class
Table 2 shows the classes indicated by message type. In CCIS, the message types are
classified into the five classes: request (0), notification (1), success response (2), client error
response (4), and server error response (5). 'Request' indicates that the peer node should take
an action as the response. 'Notification' indicates that this is just for information. 'Success
response' indicates that the request is successfully processed. 'Client error response' and
'server error response' indicate that the request has not been processed successfully by the

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.