Road vehicles -- Media Oriented Systems Transport (MOST)

This document specifies the conformance test plan (CTP) for the application layer for MOST, a synchronous time-division-multiplexing network, as specified in ISO 21806-2. This document specifies conformance test cases (CTCs) in the following categories: — device model; — data and basic data types; — registry management; — connection management; — error management; — diagnosis. Interoperability testing is not in the scope of this document.

Véhicules routiers -- Système de transport axé sur les médias

General Information

Status
Published
Publication Date
20-Oct-2020
Current Stage
5060 - Close of voting Proof returned by Secretariat
Start Date
16-Sep-2020
Completion Date
15-Sep-2020
Ref Project

Buy Standard

Standard
ISO 21806-3:2020 - Road vehicles -- Media Oriented Systems Transport (MOST)
English language
96 pages
sale 15% off
Preview
sale 15% off
Preview
Draft
ISO/FDIS 21806-3:Version 24-apr-2020 - Road vehicles -- Media Oriented Systems Transport (MOST)
English language
96 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO
STANDARD 21806-3
First edition
2020-10
Road vehicles — Media Oriented
Systems Transport (MOST) —
Part 3:
Application layer conformance test
plan
Véhicules routiers — Système de transport axé sur les médias —
Partie 3: Plan d'essais de conformité de la couche d’application
Reference number
ISO 21806-3:2020(E)
ISO 2020
---------------------- Page: 1 ----------------------
ISO 21806-3:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2020

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 21806-3:2020(E)
Contents Page

Foreword ..........................................................................................................................................................................................................................................v

Introduction ................................................................................................................................................................................................................................vi

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 1

4 Symbols and abbreviated terms ........................................................................................................................................................... 2

4.1 Symbols ......................................................................................................................................................................................................... 2

4.2 Abbreviated terms ............................................................................................................................................................................... 2

5 Conventions ............................................................................................................................................................................................................... 2

6 CTP overview ............................................................................................................................................................................................................ 2

6.1 Test set-up ................................................................................................................................................................................................... 2

6.2 Conformance test plan organisation .................................................................................................................................... 4

7 CTP general information .............................................................................................................................................................................. 4

7.1 CTC remarks .............................................................................................................................................................................................. 4

7.1.1 Timer naming ..................................................................................................................................................................... 4

7.1.2 Deadlock prevention .................................................................................................................................................... 4

7.1.3 Un-initialised logical node address .................................................................................................................. 5

7.1.4 Addresses of MOST nodes in the LT ................................................................................................................ 5

7.1.5 Device manufacturer information list ........................................................................................................... 5

7.1.6 States of the node that contains the IUT ..................................................................................................... 8

7.1.7 Procedures .........................................................................................................................................................................10

7.1.8 Violation of prerequisites of the CTC ..........................................................................................................11

7.2 CTC items ..................................................................................................................................................................................................11

7.2.1 FBlock EnhancedTestability ................................................................................................................................11

7.2.2 Multi-node devices ......................................................................................................................................................11

7.2.3 Node kinds excluded from conformance testing ...............................................................................11

8 CTC specification ...............................................................................................................................................................................................11

8.1 Static FBlock behaviour ................................................................................................................................................................11

8.1.1 CTC_2.1.0-1 – Generic FBlock property test ..........................................................................................11

8.1.2 CTC_2.1.0-2 – Generic FBlock method test .............................................................................................14

8.2 Power management .........................................................................................................................................................................16

8.2.1 Power management – PowerMaster ............................................................................................................16

8.2.2 Power management – PowerSlave ................................................................................................................20

8.3 Error management ...........................................................................................................................................................................24

8.3.1 CTC_2.4.1-2 – Restart continue test ..............................................................................................................24

8.3.2 CTC_2.4.1-9 – Reaction on network change event test ................................................................27

8.4 Central registry ....................................................................................................................................................................................29

8.4.1 Central registry handling (NetworkMaster) .........................................................................................29

8.4.2 Central registry handling test (NetworkSlave) ...................................................................................47

8.4.3 CTC_2.6.4-10 – InstID wildcard test .............................................................................................................54

8.5 CTC_2.7-1 – Node addressing test .......................................................................................................................................56

8.6 Notification matrix test .................................................................................................................................................................58

8.6.1 CTC_2.8.3-1a – Notification matrix storage test (NetworkMaster) ...................................58

8.6.2 CTC_2.8.3-1b – Notification matrix storage test (NetworkSlave) .......................................61

8.6.3 CTC_2.8.3-2 – NotificationCheck test ..........................................................................................................62

8.6.4 CTC_2.8.3-7 – Notification matrix double entry test ......................................................................64

8.6.5 CTC_2.8.3-10 – Notification error test ........................................................................................................66

8.7 CTC_3.0-1 – TEST_GSI_GSO_Identification ...................................................................................................................69

8.8 Obligatory tests for sink and source MOST devices .............................................................................................71

8.8.1 General...................................................................................................................................................................................71

8.8.2 Sink MOST devices ......................................................................................................................................................71

© ISO 2020 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 21806-3:2020(E)

8.8.3 Source MOST devices ................................................................................................................................................79

Annex A (normative) Measurement uncertainty for individual CTCs.............................................................................94

Bibliography .............................................................................................................................................................................................................................96

iv © ISO 2020 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 21806-3:2020(E)
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.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

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. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/

iso/ foreword .html.

This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,

Data communication.
A list of all parts in the ISO 21806 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO 2020 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 21806-3:2020(E)
Introduction

The Media Oriented Systems Transport (MOST) communication technology was initially developed at

the end of the 1990s in order to support complex audio applications in cars. The MOST Cooperation was

founded in 1998 with the goal to develop and enable the technology for the automotive industry. Today,

MOST enables the transport of high quality of service (QoS) audio and video together with packet data

and real-time control to support modern automotive multimedia and similar applications. MOST is a

function-oriented communication technology to network a variety of multimedia devices comprising

one or more MOST nodes.
Figure 1 shows a MOST network example.
Figure 1 — MOST network example
The MOST communication technology provides:
— synchronous and isochronous streaming,
— small overhead for administrative communication control,
— a functional and hierarchical system model,
— API standardization through a function block (FBlock) framework,
— free partitioning of functionality to real devices,
— service discovery and notification, and
[2]

— flexibly scalable automotive-ready Ethernet communication according to ISO/IEC/IEEE 8802-3 .

MOST is a synchronous time-division-multiplexing (TDM) network that transports different data types

on separate channels at low latency. MOST supports different bit rates and physical layers. The network

clock is provided with a continuous data signal.

1) MOST is the registered trademark of Microchip Technology Inc. This information is given for the convenience

of users of this document and does not constitute an endorsement by ISO.
vi © ISO 2020 – All rights reserved
---------------------- Page: 6 ----------------------
ISO 21806-3:2020(E)

Within the synchronous base data signal, the content of multiple streaming connections and control

data is transported. For streaming data connections, bandwidth is reserved to avoid interruptions,

collisions, or delays in the transport of the data stream.

MOST specifies mechanisms for sending anisochronous, packet-based data in addition to control data

and streaming data. The transmission of packet-based data is separated from the transmission of

control data and streaming data. None of them interfere with each other.

A MOST network consists of devices that are connected to one common control channel and packet

channel.

In summary, MOST is a network that has mechanisms to transport the various signals and data streams

that occur in multimedia and infotainment systems.

The ISO standards maintenance portal (https:// standards .iso .org/ iso/ ) provides references to MOST

specifications implemented in today's road vehicles because easy access via hyperlinks to these

specifications is necessary. It references documents that are normative or informative for the MOST

versions 4V0, 3V1, 3V0, and 2V5.

The ISO 21806 series has been established in order to specify requirements and recommendations

for implementing the MOST communication technology into multimedia devices and to provide

conformance test plans for implementing related test tools and test procedures.

To achieve this, the ISO 21806 series is based on the open systems interconnection (OSI) basic reference

[1] [3]

model in accordance with ISO/IEC 7498-1 and ISO/IEC 10731 , which structures communication

systems into seven layers as shown in Figure 2. Stream transmission applications use a direct stream

data interface (transparent) to the data link layer.
© ISO 2020 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO 21806-3:2020(E)
Figure 2 — The ISO 21806 series reference according to the OSI model

The International Organization for Standardization (ISO) draws attention to the fact that it is claimed

that compliance with this document may involve the use of a patent.

ISO takes no position concerning the evidence, validity and scope of this patent right.

The holder of this patent right has assured ISO that he/she is willing to negotiate licences under

reasonable and non-discriminatory terms and conditions with applicants throughout the world. In

this respect, the statement of the holder of this patent right is registered with ISO. Information may be

obtained from the patent database available at www .iso .org/ patents.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights other than those in the patent database. ISO shall not be held responsible for identifying

any or all such patent rights.
viii © ISO 2020 – All rights reserved
---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO 21806-3:2020(E)
Road vehicles — Media Oriented Systems Transport
(MOST) —
Part 3:
Application layer conformance test plan
1 Scope

This document specifies the conformance test plan (CTP) for the application layer for MOST, a

synchronous time-division-multiplexing network, as specified in ISO 21806-2.

This document specifies conformance test cases (CTCs) in the following categories:

— device model;
— data and basic data types;
— registry management;
— connection management;
— error management;
— diagnosis.
Interoperability testing is not in the scope of this document.
2 Normative references

The following documents are 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.

ISO/IEC 9646-1:1994, Information technology — Open Systems Interconnection — Conformance testing

methodology and framework — Part 1: General concepts

ISO 21806-1:2020, Road vehicles — Media Oriented Systems Transport (MOST) — Part 1: General

information and definitions

ISO 21806-2:2020, Road vehicles — Media Oriented Systems Transport (MOST) — Part 2: Application layer

ISO 21806-4:2020, Road vehicles — Media Oriented Systems Transport (MOST) — Part 4: Transport layer

and network layer
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 21806-1, ISO 21806-2,

ISO 21806-4, ISO/IEC 9646-1, and the following apply.

ISO and IEC maintain terminological databases for use in standardisation at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
© ISO 2020 – All rights reserved 1
---------------------- Page: 9 ----------------------
ISO 21806-3:2020(E)
3.1
REPEAT
pseudo code command for an iteration
3.2
REPEAT END
pseudo code command for ending an iteration
4 Symbols and abbreviated terms
4.1 Symbols
--- empty cell/undefined
4.2 Abbreviated terms
CTC conformance test case
CTP conformance test plan
CR central registry
DR decentral registry
IUT implementation under test
LT lower tester
MPI maximum position information
MSC Message Sequence Chart
NCE network change event
OSI Open Systems Interconnection
UT upper tester
5 Conventions
[3]

This document is based on OSI service conventions as specified in ISO/IEC 10731 and ISO/IEC 9646-1

for conformance test system set-up.
6 CTP overview
6.1 Test set-up

All CTCs are based on the same test set-up with an upper tester (UT) and a lower tester (LT). The LT

contains the lower tester pre-IUT (LT pre-IUT) and the lower tester post-IUT (LT post-IUT).

Figure 3 specifies the test set-up.
2 © ISO 2020 – All rights reserved
---------------------- Page: 10 ----------------------
ISO 21806-3:2020(E)
Figure 3 — Test set-up

The LT pre-IUT and the LT post-IUT implement the application layer services and the lower layer

services of a MOST node in accordance with the ISO 21806 series. They also contain a listen-only

node in front of the MOST node to log the whole communication. The MOST node is able to operate as

TimingMaster or TimingSlave; alternatively, it can be physically disconnected from the MOST network.

If it is disconnected, the associated LT pre-IUT or LT post-IUT serves as listen-only node.

Every CTC specifies the roles of the LT pre-IUT and the LT post-IUT.

During testing of the MOST device that implements the IUT, avoid over-temperature by following the

manufacturer recommendations regarding cooling.

The power supply of the MOST device that contains the IUT is adjustable and the power consumption

can be monitored by the UT. This is necessary to determine whether a node has entered s_

NetInterface_Sleep.

A MOST device contains one or more nodes, which are connected to an external MOST physical interface.

One of the nodes contains the implementation under test (IUT). All tests and timings, specified by the

CTP, are related to the external MOST physical interface.

Figure 4 shows a MOST device with one node and a MOST device with three internal nodes.

© ISO 2020 – All rights reserved 3
---------------------- Page: 11 ----------------------
ISO 21806-3:2020(E)
1 external MOST physical interface
2 internal MOST physical interface
Figure 4 — MOST device with one node and MOST device with three nodes
6.2 Conformance test plan organisation

CTCs are independent of one another. Each CTC checks the behaviour of the IUT for requirements stated

in ISO 21806-2. Within CTCs, which require variations of individual parameters, each specified value of

the parameter is iterated.
The measurement uncertainty for each CTC shall be in accordance with Annex A.
7 CTP general information
7.1 CTC remarks
7.1.1 Timer naming

For conformance testing of the IUT, the UT and LT need minimum and maximum timers. The names of

the timers used by this document are based on ISO 21806-2 and ISO 21806-4. To obtain the timer name,

for minimum and maximum, “ ” and “ ” are appended, respectively. Table 1 shows a timer naming

_min _max
definition example for t .
Config
Table 1 — Timer naming example
Name Minimum Typical value Maximum Unit Purpose
value name name value name
t t t t ms Time before ev_Init_Error_
Config Config_min Config Config_max
Shutdown or delay for RBD result.
7.1.2 Deadlock prevention
This document specifies the timeouts t , t , and t to prevent deadlock
DeadLockShort DeadLockMid DeadLockLong
situations during conformance testing. These are the default values:
— t : 1 s;
DeadLockShort
— t : 20 s;
DeadLockMid
— t : 5 min.
DeadLockLong
These timeouts are only relevant for conformance testing and may be extended.
4 © ISO 2020 – All rights reserved
---------------------- Page: 12 ----------------------
ISO 21806-3:2020(E)
7.1.3 Un-initialised logical node address

The variable uninitialised_node_address is defined as the address of an un-initialised node, which is

specified in ISO 21806-2.
7.1.4 Addresses of MOST nodes in the LT

The address of a MOST node in the LT is the default logical node address corresponding to the node

position.

If this address is in conflict with the address of a node that contains the IUT (e.g. if a supplier uses

static addresses in the dynamic address range), the affected MOST node in the LT shall use a valid free

address.
7.1.5 Device manufacturer information list

This list contains all information that is provided by the device manufacturer for conformance testing.

It also includes remarks and references to corresponding CTCs.

Table 2 shows the device manufacturer information list, which does not include information stored in

FBlock EnhancedTestability.
© ISO 2020 – All rights reserved 5
---------------------- Page: 13 ----------------------
ISO 21806-3:2020(E)
Table 2 — Device manufacturer information list
Category Item/property Description Reference
to CTC

MOST network IUT in the TimingMaster Determines whether the IUT is part of the All CTCs

configuration TimingMaster.
IUT in the NetworkMaster Determines whether the IUT is part of the All CTCs
NetworkMaster.
IUT in the PowerMaster Determines whether the IUT is part of the All CTCs
PowerMaster.
IUT in the connection --- CTC_3.1-3,
manager CTC_3.1-4,
CTC_3.1-5,
CTC_3.1-6,
CTC_3.2-3,
CTC_3.2-4,
CTC_3.2-5,
CTC_3.2-6,
CTC_3.2-7,
CTC_3.2-8,
CTC_3.2-9,
CTC_3.2-14

Multi-node device If the IUT is part of a MOST device that contains more All CTCs

than one node, the following information is provided:
— number of nodes in the MOST device;
— topology of the MOST device (position
of PowerMaster and TimingMaster/
NetworkMaster);
— position of the node that contains the IUT.
IUT sample frequency If the IUT is not part of the TimingMaster, the LT All CTCs
provides the correct network frame rate (44,1 kHz or
48,0 kHz).
Required value of boundary Value of the boundary descriptor. All CTCs
descriptor (if the
Unless otherwise stated, all CTCs are performed with
TimingMaster is in the LT)
this value of the boundary descriptor.
mi The maximum number of permitted conflicting node CTC_2.6.2-3a
MaxInvalidReg
address registrations by a NetworkSlave.
mi When an invalid InstID registration occurs, the CTC_2.6.2-6
MaxSetNewInstID
NetworkMaster sends a request to the NetworkSlave
for setting a new InstID.
t Time before ev_Init_Error_Shutdown or delay for CTC_2.1.1-6b
Config_max
RBD result.
t Limit for the NetworkMaster to set the central CTC_2.6.2-4a,
ConfigurationAnnounce
registry state. CTC_2.6.2-5
t Time the NetworkMaster waits for all NetworkSlaves CTC_2.6.2-1,
WaitForAnswer_min
to respond. CTC_2.6.2-3b,
WaitForAnswer_max
CTC_2.6.2-5
6 © ISO 2020 – All rights reserved
---------------------- Page: 14 ----------------------
ISO 21806-3:2020(E)
Table 2 (continued)
Category Item/property Description Reference
to CTC

Power Node that contains the IUT Determines whether the node that contains the IUT CTC_2.3.2-3

management supports supports s_NetInterface_Sleep:
s_NetInterface_Sleep
— yes: the MOST device that contains the IUT
reduces its power consumption below threshold
before timeout expires;
— no: the reduction of power consumption is not
detectable.
s_NetInterface_Sleep: Threshold of current for s_NetInterface_Sleep See 7.1.6.
detection
NetInterfaceSleep_Threshold
s_NetInterface_Sleep: t CTC_2.3.2-3,
PwrSwitchOffDelay_min
CTC_2.6.4-1
t Specific timeout for s_NetInterface_Sleep; after
PwrSwitchOffDelay_min
the end of network activity, the node that contains
PwrSwitchOffDelay_max
the IUT does not enter s_NetInterface_Sleep
(reduced power consumption) before t
PwrSwitchOffDelay_
expires.
min
PwrSwitchOffDelay_max
MOST device specific timeout for s_NetInterface_
Sleep; after the end of network activity, the node
that contains the IUT enters s_NetInterface_
Sleep (reduced power consumption) before
t expires.
PwrSwitchOffDelay_max

Wake-up preconditions Preconditions for the node that contains the IUT for See 7.1.6.

wake-up.
Supplemented by information whether the node that
contains the IUT needs additional conditions during
operation (e.g. ignition ON) to stay in
s_NetInterface_Normal_Operation.
Node that contains the IUT is --- CTC_2.4.1-2
capable of waking via network
startup (i.e. switching on its
MOST output)

Delay between connection to Potentially, the UT (see Figure 3) waits for a short All CTCs

power (of the MOST device period of time between connecting the MOST device
that contains the IUT) and that contains the IUT to power and switching on the
the ability of the node that MOST output to wake up the node that contains the
contains the IUT to detect IUT. Otherwise, the node that contains the IUT does
wake-up events not detect a wake-up event.
s_NetInterface_Normal_
This delay covers: See 7.1.6.
Operation:
— NetworkMaster: period of time the node that
CTC_2.6.2-3b
Delay until all FBlocks of contains the IUT needs to add own FBlocks to
the node that contains its central registry after Configuration.
Status(OK);
the IUT are available
after Configuration.
Status(OK) — NetworkSlave: delay between
ev_Init_Ready and availability of application.
(equivalent to t )
WaitForApplication
t Specific limit for the NetworkMaster to start an CTC_2.4.1-9,
WaitBeforeScan
FBlock scan. CTC_2.6.2-5,
CTC_2.6.4-8
© ISO 2020 – All rights reserved 7
---------------------- Page: 15 ----------------------
ISO 21806-3:2020(E)
Table 2 (continued)
Category Item/property Description Reference
to CTC

Addressing Node that contains the IUT If the node that contains the IUT uses a static logical See 7.1.6.

uses static node address in node address that is in the specified dynamic address

CTC_2.6.4-4
dynamic address range range, the address is provided.
Free address Logical node address that may be used by a MOST CTC_2.6.4-3
node in the L
...

DRAFT INTERNATIONAL STANDARD
ISO/DIS 21806-3
ISO/TC 22/SC 31 Secretariat: DIN
Voting begins on: Voting terminates on:
2019-10-10 2020-01-02
Road vehicles — Media oriented systems transport (MOST)
framework —
Part 3:
Application layer conformance test plan
Véhicules routiers — Environnement du système axé sur les médias —
Partie 3: Plan d'essais de conformance de la couche d’application
ICS: 43.040.15
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
This document is circulated as received from the committee secretariat.
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 21806-3:2019(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. ISO 2019
---------------------- Page: 1 ----------------------
ISO/DIS 21806-3:2019(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2019

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 21806-3:2019(E)
Contents Page

Foreword ........................................................................................................................................................................... v

Introduction ..................................................................................................................................................................... v

1 Scope ....................................................................................................................................................................1

2 Normative references ....................................................................................................................................1

3 Terms and definitions ....................................................................................................................................2

4 Symbols and abbreviated terms .................................................................................................................2

5 Conformance .....................................................................................................................................................2

6 CTP overview .....................................................................................................................................................3

6.1 Test set-up ............................................................................................................................................................ 3

6.2 Conformance test plan organisation .......................................................................................................... 4

7 MOST CTP general information ..................................................................................................................5

7.1 CT remarks ........................................................................................................................................................... 5

7.1.1 Timer naming example .................................................................................................. 5

7.1.2 Deadlock prevention ...................................................................................................... 5

7.1.3 Un-initialised logical node address ................................................................................ 5

7.1.4 Addresses of MOST nodes in the LT .............................................................................. 5

7.1.5 Device manufacturer information list ............................................................................ 5

7.1.6 Further definitions – States of the node that contains the IUT ................................... 10

7.1.7 Further definitions – Procedures ................................................................................. 12

7.1.8 Violation of prerequisites of the CTC ........................................................................... 13

7.2 CT items .............................................................................................................................................................. 13

7.2.1 FBlock EnhancedTestability ......................................................................................... 13

7.2.2 Multi-node devices ...................................................................................................... 13

7.2.3 Node kinds excluded from conformance testing ......................................................... 13

8 CT specification ............................................................................................................................................. 14

8.1 Static FBlock behaviour ................................................................................................................................ 14

8.1.1 CTC_2.1.0-1 – Generic FBlock property test ................................................................ 14

8.1.2 CTC_2.1.0-2 – Generic FBlock method test ................................................................. 16

8.2 Power management ....................................................................................................................................... 20

8.2.1 Power management – PowerMaster ........................................................................... 20

8.2.2 Power management – PowerSlave .............................................................................. 24

8.3 Error management ......................................................................................................................................... 28

8.3.1 CTC_2.4.1-2 – Restart continue test ............................................................................ 28

8.3.2 CTC_2.4.1-9 – Reaction on network change event test ............................................... 30

8.4 Central registry ................................................................................................................................................ 32

8.4.1 Central registry handling (NetworkMaster) ................................................................. 32

8.4.2 Central registry handling test (NetworkSlave) ............................................................. 52

8.4.3 CTC_2.6.4-10 – InstID wildcard test ............................................................................. 59

8.5 CTC_2.7-1 – Node addressing test ............................................................................................................ 61

8.6 Notification matrix test................................................................................................................................. 63

8.6.1 CTC_2.8.3-1a – Notification matrix storage test (NetworkMaster) ............................. 63

8.6.2 CTC_2.8.3-1b – Notification matrix storage test (NetworkSlave)................................ 65

© ISO 2019 – All rights reserved
iii
---------------------- Page: 3 ----------------------
ISO/DIS 21806-3:2019(E)

8.6.3 CTC_2.8.3-2 – NotificationCheck test ......................................................................... 67

8.6.4 CTC_2.8.3-7 – Notification matrix double entry test .................................................. 69

8.6.5 CTC_2.8.3-10 – Notification error test ........................................................................ 71

8.7 CTC_3.0-1 – TEST_GSI_GSO_Identification ............................................................................................ 74

8.8 Obligatory tests for sink and source MOST devices ......................................................................... 76

8.8.1 Sink MOST devices ...................................................................................................... 76

8.8.2 Source MOST devices .................................................................................................. 86

Annex A (normative) Measurement uncertainty for individual conformance tests ....................... 104

Bibliography ............................................................................................................................................................... 106

© ISO 2019 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 21806-3:2019(E)
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.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

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. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www.iso.org/patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see

www.iso.org/iso/foreword.html.

This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,

Data communication.
A list of all parts in the ISO 21806 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www.iso.org/members.html.
© ISO 2019 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/DIS 21806-3:2019(E)
Introduction

The Media Oriented Systems Transport (MOST) communication technology was initially developed at

the end of the 1990s in order to support complex audio applications in cars. The MOST Cooperation was

founded in 1998 with the goal to develop and enable the technology for the automotive industry. Today,

MOST enables the transport of high Quality of Service (QoS) audio and video together with packet data

and real-time control to support modern automotive multimedia and similar applications. MOST is a

function-oriented communication technology to network a variety of multimedia devices comprising

one or more MOST nodes.
Figure 1 shows a MOST network example.
Figure 1 — MOST network example
The MOST communication technology provides
⎯ synchronous and isochronous streaming,
⎯ small overhead for administrative communication control,
⎯ a functional and hierarchical system model,
⎯ API standardization through a function block (FBlock) framework,
⎯ free partitioning of functionality to real devices,
⎯ service discovery and notification, and
© ISO 2019 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/DIS 21806-3:2019(E)

⎯ flexibly scalable automotive-ready Ethernet communication according to ISO/IEC/IEEE 8802-3.

MOST is a synchronous time-division-multiplexing (TDM) network that transports different data types

on separate channels at low latency. MOST supports different bit rates and physical layers. The network

clock is provided with a continuous data signal.

Within the synchronous base data signal, the content of multiple streaming connections and control

data is transported. For streaming data connections, bandwidth is reserved to avoid interruptions,

collisions, or delays in the transport of the data stream.

MOST specifies mechanisms for sending anisochronous, packet-based data in addition to control data

and streaming data. The transmission of packet-based data is separated from the transmission of

control data and streaming data. None of them interfere with each other.

A MOST network consists of devices that are connected to one common control channel and packet

channel.

In summary, MOST is a network that has mechanisms to transport the various signals and data streams

that occur in multimedia and infotainment systems.

The ISO Standards Maintenance Portal (http://standards.iso.org/iso/) provides references to MOST

specifications implemented in today's road vehicles because easy access via hyperlinks to these

specifications is necessary. It references documents that are normative or informative for the MOST

versions 4V0, 3V1, 3V0, and 2V5.

MOST® is the Registered Trademark of Microchip Technology Inc. This information is given for the

convenience of users of this document and does not constitute an endorsement by ISO.

The ISO 21806 series has been established in order to specify requirements and recommendations for

implementing the MOST communication technology into multimedia devices and to provide

conformance test plans for implementing related test tools and test procedures.

To achieve this, the ISO 21806 series is based on the Open Systems Interconnection (OSI) Basic

Reference Model in accordance with ISO/IEC 7498-1 [1] and ISO/IEC 10731 [2], which structures

communication systems into seven layers as shown in Figure 2.
© ISO 2019 – All rights reserved
vii
---------------------- Page: 7 ----------------------
ISO/DIS 21806-3:2019(E)
Key

1 Stream transmission application uses a direct stream data interface (transparent) to the data link layer

Figure 2 — ISO 21806 documents reference according to the OSI model
© ISO 2019 – All rights reserved
viii
---------------------- Page: 8 ----------------------
DRAFT INTERNATIONAL STANDARD ISO/DIS 21806-3:2019(E)
Road vehicles — Media oriented systems transport (MOST)
framework —
Part 3:
Application layer conformance test plan
1 Scope

This document specifies the conformance test plan (CTP), which covers the MOST device conformance

tests for the application layer and includes the conformance tests (CTs) of the
⎯ device model,
⎯ data and basic data types,
⎯ registry management,
⎯ connection management,
⎯ error management, and
⎯ diagnosis.
Interoperability testing is not in the scope of this document.
2 Normative references

The following documents are 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.

ISO/IEC 9646-1, Information technology — Open Systems Interconnection — Conformance testing

methodology and framework — Part 1: General concepts

ISO 21806-1, Road vehicles – Media Oriented Systems Transport (MOST) – Part 1: General information

and definitions

ISO 21806-2, Road vehicles – Media Oriented Systems Transport (MOST) – Part 2: Application layer

ISO 21806-4, Road vehicles – Media Oriented Systems Transport (MOST) – Part 4: Transport layer and

network layer

ISO 21806-6, Road vehicles – Media Oriented Systems Transport (MOST) – Part 6: Data link layer

© ISO 2019 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/DIS 21806-3:2019(E)
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 21806-1, ISO 21806-2,

ISO 21806-4, ISO/IEC 9646-1, and the following apply.

ISO and IEC maintain terminological databases for use in standardisation at the following addresses:

⎯ IEC Electropedia: available at http://www.electropedia.org/;
⎯ ISO Online browsing platform: available at http://www.iso.org/obp.
4 Symbols and abbreviated terms

For the purposes of this document, the abbreviated terms given in ISO 21806-1, ISO 21806-2,

ISO 21806-4, and the following apply.
CT conformance test
CTC conformance test case
CTP conformance test plan
CR central registry
DR decentral registry
IUT implementation under test
LT lower tester
MSC Message Sequence Chart
NCE network change event
OSI Open Systems Interconnection
UT upper tester
5 Conformance

This document is based on the conventions discussed in the OSI service conventions as specified in

ISO/IEC 10731.
© ISO 2019 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/DIS 21806-3:2019(E)
6 CTP overview
6.1 Test set-up

All CTCs use the same test set-up with two testers, an upper tester (UT) and a lower tester (LT), which

contains the lower tester pre-IUT (LT pre-IUT) and the lower tester post-IUT (LT post-IUT).

Figure 3 shows the test set-up.
Figure 3 — Test set-up

The LT pre-IUT and the LT post-IUT each include the network service and the lower layers of a MOST

node. They also contain a listen-only node in front of the MOST node to log the whole communication.

The MOST node is able to operate as TimingMaster or TimingSlave; alternatively, it can be physically

disconnected from the MOST network. If it is disconnected, the associated LT pre-IUT or LT post-IUT

serves as listen-only node.

Every CTC contains a description of the experimental set-up that specifies the roles of the LT pre-IUT

and the LT post-IUT.

NOTE During testing, avoid over-temperature situations of the MOST device that contains the IUT by

following the manufacturer recommendations regarding cooling.
© ISO 2019 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/DIS 21806-3:2019(E)

The power supply of the MOST device that contains the IUT is adjustable and the power consumption

can be monitored by the UT. This is necessary to determine whether a node has entered

s_NetInterface_Sleep.

A MOST device contains one or more nodes, which are connected to an external MOST physical

interface. One of the nodes contains the implementation under test (IUT). All tests and timings, specified

by the CTP, are always related to the external MOST physical interface.

Figure 4 shows a MOST device with one node and a MOST device with three internal nodes.

Key
1 External MOST physical interface
2 Internal MOST physical interface
Figure 4 — MOST device with one node and MOST device with three nodes
6.2 Conformance test plan organisation

The CTCs are independent of one another. Each CTC checks the behaviour of the IUT for a particular

purpose of ISO 21806-2.

CTCs, which require variations of individual parameters, shall be repeated for each value of the

parameter.
© ISO 2019 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/DIS 21806-3:2019(E)
7 MOST CTP general information
7.1 CT remarks
7.1.1 Timer naming example

For conformance testing of the IUT, the UT and LT need minimum and maximum timers. The names of

the timers used by this document are based on ISO 21806-2 and ISO 21806-4. To obtain the timer name,

for minimum and maximum, “_min” and “_max” are appended, respectively. Table 1 shows a timer

naming definition example for t .
Config
Table 1 — Timer naming example
Name Min value Typ value Max value Unit Purpose
t t t t ms Time before ev_Init_Error_Shutdown or delay
Config Config_min Config Config_max
for RBD result.
7.1.2 Deadlock prevention

To prevent a deadlock during testing, three timeouts are defined by this document:

⎯ t = 1 s;
DeadLockShort
⎯ t = 20 s;
DeadLockMid
⎯ t = 5 min.
DeadLockLong
These timeouts are only relevant for conformance testing.

If extended timeouts of the deadlock timer are necessary, the CTC shall indicate this.

7.1.3 Un-initialised logical node address

This document uses the variable uninitialised_node_address to identify the address of an un-

initialised node, which is specified in ISO 21806-2.
7.1.4 Addresses of MOST nodes in the LT

By default, the address of a MOST node in the LT is the default logical node address corresponding to

the node position.

If the address is in conflict with the address of a node that contains the IUT (e.g., if a supplier uses static

addresses in the dynamic address range), the affected MOST node in the LT shall use a valid free

address.
7.1.5 Device manufacturer information list

This list contains all information that is provided by the device manufacturer for conformance testing. It

also includes remarks and references to corresponding CTCs.
© ISO 2019 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/DIS 21806-3:2019(E)

Table 2 specifies the device manufacturer information list, which does not include information stored in

FBlock EnhancedTestability.
Table 2 — Device manufacturer information list
Item/property Description Reference
to CTC

MOST network IUT in the TimingMaster Specify whether the IUT is part of the All CTCs

configuration TimingMaster.
IUT in the NetworkMaster Specify whether the IUT is part of the All CTCs
NetworkMaster.
IUT in the PowerMaster Specify whether the IUT is part of the All CTCs
PowerMaster.
IUT in the connection manager --- CTC_3.1-3,
CTC_3.1-4,
CTC_3.1-5,
CTC_3.1-6,
CTC_3.2-3,
CTC_3.2-4,
CTC_3.2-5,
CTC_3.2-6,
CTC_3.2-7,
CTC_3.2-8,
CTC_3.2-9,
CTC_3.2-14
Multi-node device If the IUT is part of a MOST device that All CTCs
contains more than one node, the following
information should be provided:
— number of nodes in the MOST device;
— topology of the MOST device (position of
PowerMaster and
TimingMaster/NetworkMaster);
— position of the node that contains the IUT.
IUT sample frequency If the IUT is not part of the TimingMaster, the All CTCs
LT shall provide the correct network frame
rate (44,1 kHz or 48,0 kHz).
Required value of boundary Value of the boundary descriptor. All CTCs
descriptor
Unless otherwise stated, all CTCs are
(if the TimingMaster is in the
performed with this value of the boundary
LT)
descriptor.
mi The maximum number of permitted CTC_2.6.2-3a
MaxInvalidReg
conflicting node address registrations by a
NetworkSlave.
miMaxSetNewInstID When an invalid InstID registration occurs, CTC_2.6.2-6
the NetworkMaster sends a request to the
NetworkSlave for seting a new InstID.
© ISO 2019 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/DIS 21806-3:2019(E)
Item/property Description Reference
to CTC
tConfig_max Time before ev_Init_Error_Shutdown or delay CTC_2.1.1-6b
for RBD result.
t Limit for the NetworkMaster to set the central CTC_2.6.2-4a,
ConfigurationAnnounce
registry state. CTC_2.6.2-5
t Time the NetworkMaster waits for all CTC_2.6.2-1,
WaitForAnswer_min
NetworkSlaves to respond. CTC_2.6.2-3b,
WaitForAnswer_max
CTC_2.6.2-5

Power Node that contains the IUT The manufacturer shall provide whether the CTC_2.3.2-3

management supports node that contains the IUT supports
s_NetInterface_Sleep s_NetInterface_Sleep:
— yes: the MOST device that contains the
IUT reduces its power consumption below
threshold before timeout expires;
— no: the reduction of power consumption is
not detectable.
s_NetInterface_Sleep:
Threshold of current for see 7.1.6
NetInterfaceSleep_Threshold s_NetInterface_Sleep detection
s_NetInterface_Sleep: tPwrSwitchOffDelay_min CTC_2.3.2-3,
CTC_2.6.4-1
Specific timeout for s_NetInterface_Sleep;
PwrSwitchOffDelay_min
after the end of network activity, the node
tPwrSwitchOffDelay_max
that contains the IUT does not enter
s_NetInterface_Sleep (reduced power
consumption) before tPwrSwitchOffDelay_min
expires.
PwrSwitchOffDelay_max
MOST device specific timeout for
s_NetInterface_Sleep; after the end of
network activity, the node that contains the
IUT enters s_NetInterface_Sleep (reduced
power consumption) before
t expires.
PwrSwitchOffDelay_max
Preconditions for the node that contains the
Wake-up preconditions see 7.1.6
IUT for wake-up.
Supplemented by information whether the
node that contains the IUT needs additional
conditions during operation (e.g. ignition ON)
to stay in s_NetInterface_Normal_Operation.
Node that contains the IUT is --- CTC_2.4.1-2
capable of waking via network
startup (i.e., switching on its
MOST output)
© ISO 2019 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/DIS 21806-3:2019(E)
Item/property Description Reference
to CTC

Delay between connection to Potentially, the UT (see Figure 3) shall wait for All CTCs

power (of the MOST device that a short period of time between connecting the
contains the IUT) and the MOST device that contains the IUT to power
ability of the node that contains and switching on the MOST output to wake up
the IUT to detect wake-up the node that contains the IUT. Otherwise, the
events node that contains the IUT fails to detect a
wake-up event.
s_NetInterface_Normal_Operat
This delay covers: see 7.1.6
ion:
— NetworkMaster: period of time the node CTC_2.6.2-3b
Delay until all FBlocks of the that contains the IUT needs to add own
FBlocks to its central registry after
node that contains the IUT are
Configuration.Status(OK);
available after
Configuration.Status(OK)
— NetworkSlave: delay between
(equivalent to tWaitForApplication) ev_Init_Ready and availability of
application.
t Specific limit for the NetworkMaster to start CTC_2.4.1-9,
WaitBeforeScan
an FBlock scan CTC_2.6.2-5,
CTC_2.6.4-8

Addressing Node that contains the IUT uses If the node that contains the IUT uses a static see 7.1.6

static node address in dynamic logical node address that is in the specified
CTC_2.6.4-4
address range dynamic address range, the address shall be
provided
Free address Logical node address that can be used by a CTC_2.6.4-3
MOST node in the LT during testing
Free FBlock range FBlocks that are not used by the node that CTC_2.6.2-4b,
contains the IUT and which can be used by the CTC_2.6.2-4c
upper tester
Group address of the node that --- CTC_2.7-1
contains the IUT
General t Limit for responding to a command that reads CTC_2.1.0-1,
Property
communication a property. CTC_2.1.0-2,
CTC_2.8.3-2,
CTC_2.8.4-3,
CTC_3.0-1,
CTC_3.1-1,
CTC_3.2-1
t Limit for reacting to a Notification.Set CTC_2.8.3-1a,
NotificationProperty
CTC_2.8.3-1b,
message.
CTC_2.8.3-7
© ISO 2019 – All rights reserved
---------------------- Page: 16 ----------------------
ISO/DIS 21806-3:2019(E)
Item/property Description Reference
to CTC
Physical UIUT_Operating At this voltage level, the MOST device that All CTCs
parameter
contains the IUT operates normally.
(voltage levels)
Unless otherwise stated, all CTCs are
performed at this voltage level.

Messaging Node that contains the IUT The node that contains the IUT is able to send CTC_2.8.4-2,

supports segmented messages and receive segmented messages. CTC_2.8.4-3,
CTC_2.8.4-7,
CTC_2.8.4-8

Sink/Source List of FBlocks, containing sink The list contains all FBlocks reported by CTC_3.0-1

FBlockID.Status.
and/or source functionality
MOST devices with sinks: --- CTC_3.1-1,
CTC_3.1-3,
List of all supported sink
CTC_3.1-4,
numbers with ContentType,
CTC_3.1-5,
ContentDescription (data type
CTC_3.1-6
of the parameter) and
TransmissionClass.
CTC_3.2-1,
MOST devices with sources: ---
CTC_3.2-3,
List of all supported source
CTC_3.2-4,
numbers with ContentType,
CTC_3.2-
ContentDescription (data type
5,CTC_3.2-6,
of the parameter) and
CTC_3.2-7,
TransmissionClass
CTC_3.2-14
MOST devices with sources: --- CTC_3.2-3
BlockWidth and
ConnectionLabel
Node that contains the IUT --- CTC_3.2-14
supports SourceActivity
© ISO 2019 – All rights reserved
---------------------- Page: 17 ----------------------
ISO/DIS 21806-3:2019(E)
7.1.6 Further definitions – States of the node that contains the IUT

Table 3 specifies how the NetInterface state s_NetInterface_Normal_Operation is effectuated and

detected in the node that contains the IUT.
Table 3 — Effectuate and detect s_NetInterface_Normal_Operation
Effectuate state Detect state

a) The IUT is contained in a NetworkSlave: a) The IUT is contained in a NetworkSlave:

— the UT shall start the network; the node that
...

Questions, Comments and Discussion

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