ISO 20794-5:2020

INTERNATIONAL ISO
STANDARD 20794-5
First edition
2020-10
Road vehicles — Clock extension
peripheral interface (CXPI) —
Part 5:
Application layer conformance test
plan
Véhicules routiers — Interface périphérique d’extension d'horloge
(CXPI) —
Partie 5: Plan de test de conformité de la couche application
Reference number
©
ISO 2020
© 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

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms . 3
4.1 Symbols . 3
4.2 Abbreviated terms . 3
5 Conventions . 4
6 General test specification considerations . 4
6.1 General . 4
6.2 Test conditions . 4
6.3 IUT requirements. 4
6.4 CTC definition . 4
6.5 Test system set-up . 5
6.6 Configuration of test system and IUT . 6
6.6.1 General. 6
6.6.2 IUT-specific set-up parameters . 7
6.6.3 User_Specific configurations. 8
6.6.4 W/S_Init configurations . . . 8
6.6.5 W/S_Passive configurations . 8
6.6.6 W/S_RdySleep configurations . 8
6.6.7 W/S_NotRdySleep configurations . 8
6.6.8 A_WSSup configurations . 9
6.6.9 NonW/S configurations . 9
6.6.10 ErrDet configurations . 9
6.6.11 Event configurations . . 9
6.6.12 Polling configurations . 9
6.7 SUT initialisation .10
6.7.1 General.10
6.7.2 Default initialisation .10
6.7.3 Sleep initialisation .10
6.7.4 Power-off initialisation .10
6.7.5 Transmission prohibition initialisation .10
6.7.6 Clock supply of secondary clock master initialisation .10
7 Application conformance test plan .10
7.1 General .10
7.2 Network management .10
7.2.1 General.10
7.2.2 State transition definition .11
7.2.3 State transition CTCs .11
7.2.4 Wake-up request/notification of master node trigger CTCs.15
7.2.5 Wake-up request/notification of slave node trigger CTCs.18
7.2.6 Sleep request/notification CTCs .25
7.2.7 Network Management multi clock master processing CTCs .31
7.3 Fault management .34
7.3.1 Error detection/recovery CTCs .34
7.3.2 CXPI network error CTCs .41
7.3.3 SCT error CTCs .42
7.3.4 Error notification between CXPI nodes CTCs .43
8 Application layer conformance test plan .45
8.1 General .45
8.2 Transfer management CTCs .45
8.2.1 General.45
8.2.2 7.CTC_10.1 – Master node event-triggered method .45
8.2.3 7.CTC_10.2 – Slave node event-triggered method .46
8.2.4 7.CTC_10.3 – Master node polling method .46
8.2.5 7.CTC_10.4 – Slave node polling method .47
8.2.6 7.CTC_10.5 – Behaviour of unknown or invalid ReqId reception .48
8.2.7 7.CTC_10.6 – Master node sets unused bits in response message .48
8.2.8 7.CTC_10.7 – Slave node sets unused bits in response message .49
Bibliography .51
iv © ISO 2020 – All rights reserved

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 20794 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.
Introduction
ISO 20794 (all parts) specifies the application (partly), application layer, transport layer, network
layer, data link layer, and physical layer requirements of an in-vehicle network called "clock extension
peripheral interface (CXPI)".
CXPI is an automotive low-speed single wire network. It is an enabler for reducing vehicle weight and
fuel consumption by reducing wire counts to simple devices like switches and sensors.
CXPI serves as and is designed for automotive control applications, for example door control group,
light switch, and HVAC (Heating Ventilation and Air Condition) systems.
The CXPI services, protocols, and their key characteristics are specified in different parts according to
the OSI layers.
— Application and application layer:
— application measurement and control data communication to exchange information between
applications in different nodes based on message communication;
— wake-up and sleep functionality;
— two kinds of communication methods can be selected at system design by each node:
i) the event-triggered method, which supports application measurement- and control-based
(event-driven) slave node communication; and
ii) the polling method, which supports slave node communication based on a periodic master
schedule;
— performs error detection and reports the result to the application;
— application error management.
— Transport layer and network layer:
— transforms a message into a single packet;
— adds protocol control information for diagnostic and node configuration into each packet;
— adds packet identifier for diagnostic and node configuration into each packet;
— performs error detection and reports the result to higher OSI layers.
— Data link layer and physical layer:
— provides long and short data frames;
— adds a frame identifier into the frame;
— adds frame information into the frame;
— adds a cyclic redundancy check into the frame;
— performs byte-wise arbitration and reports the arbitration result to higher OSI layers;
— performs frame type detection in reception function;
— performs error detection and reports the result to higher OSI layers;
— performs Carrier Sense Multiple Access (CSMA);
— performs Collision Resolution (CR);
vi © ISO 2020 – All rights reserved

— generates a clock, which is transmitted with each bit to synchronise the connected nodes on the
CXPI network;
— supports bit rates up to 20 kbit/s.
To achieve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model specified
[2]
in ISO/IEC 7498-1 and ISO/IEC 10731 , which structures communication systems into seven layers.
Figure 1 illustrates an overview of communication frameworks beyond the scope of this document
including related standards:
— vehicle normal communication framework, which is composed of ISO 20794-2 and this document;
[3] [4]
— vehicle diagnostic communication framework, which is composed of ISO 14229-1 , ISO 14229-2
[5]
and ISO 14229-8 ;
[10]
— presentation layer standards, e.g. vehicle manufacturer specific or ISO 22901-1 ODX ;
[6] [7] [8]
— lower OSI layers framework, which is composed of ISO 20794-3 , ISO 20794-4 , ISO 20794-6
[9]
and ISO 20794-7 .
[5]
ISO 20794 (all parts) and ISO 14229-8 are based on the conventions specified in the OSI Service
[2]
Conventions (ISO/IEC 10731 ) as they apply for all layers and the diagnostic services.
Figure 1 — ISO 20794 documents reference according to OSI model
INTERNATIONAL STANDARD ISO 20794-5:2020(E)
Road vehicles — Clock extension peripheral interface
(CXPI) —
Part 5:
Application layer conformance test plan
1 Scope
This document specifies the conformance test plan for ISO 20794-2:2020 implementations.
It specifies conformance test cases related to:
— concept of operation;
— network management;
— transfer management; and
— error management.
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 7498-1, Information processing systems — Open systems interconnection — Basic reference model
ISO 20794-2:2020, Road vehicles — Clock extension peripheral interface (CXPI) — Part 2: Application layer
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20794-2, ISO/IEC 7498-1 and
the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
clock master
node that transmits clock (3.4) to the lower OSI layers (3.2)
3.2
lower OSI layer
OSI layer lower than application layer
3.3
master node
node that provides the schedule (3.10) master management (include ReqTypeId transmission), the
primary clock (3.7) and optionally the sleep message transmission management
3.4
clock
function that synchronises all nodes on the CXPI network
3.5
initiator
node that transmits messages
3.6
passive
node that receives messages
3.7
primary clock
clock (3.4) that is provided by the master node (3.3)
3.8
REPEAT
pseudo code command for an iteration
3.9
REPEAT END
pseudo code command for ending an iteration
3.10
schedule
origin of periodic frame transmission
3.11
secondary clock
clock (3.4) that is provided by one dedicated slave node (3.13)
3.12
sequence
transmission and reception procedure of messages among two or more nodes
3.13
slave node
node other than master node (3.3) connected to the CXPI network
3.14
slave initiator node
node that is woken up by its own slave node (3.13)
3.15
slave passive node
node that is woken up by another slave node (3.13)
3.16
wake-up pulse
stimulus initiated by a node used for wake-up of other nodes on the CXPI network
2 © ISO 2020 – All rights reserved

4 Symbols and abbreviated terms
4.1 Symbols
--- empty cell/undefined
kbit/s kilobit per second
t master node clock start time
clock_start_m
t master node clock stop time
clock_stop_m
t slave node sleep state transi-
sleep_s
tion time
t master node wake-up time
wakeup_m
t slave node wake-up recovery time
wakeup_recovery_s
t slave node wake-up time
wakeup_s
t master node wake-up schedule
wakeup_schedule_m
time
4.2 Abbreviated terms
ASP abstract service primitive
AL application layer
APP application
CRC cyclic redundancy check
DLC data length code
ECU electronic control unit
EMI electro-magnetic interference
ErrDet error detection
ETS enhanced testability service
IUT implementation under test
OSI open systems interconnection
PDU protocol data unit
PID protected identifier
PCO point of control and observation
ReqId request identifier
ReqTypeId request type identifier
SCT sequence count
SUT system under test
5 Conventions
[2] [1]
This document is based on OSI service conventions as specified in ISO/IEC 10731 and ISO/IEC 9646-1
for conformance test system setup.
6 General test specification considerations
6.1 General
This document covers the conformance test cases (CTC) to verify the requirements described in
ISO 20794-2 application layer document.
6.2 Test conditions
Tests can be performed at room temperature, if the temperature is in the range of 15° C to 35° C. Also,
the tests shall be performed under room EMI (electro-magnetic interference) conditions.
6.3 IUT requirements
The occurrence of the error specified in ISO 20794-2:2020, 9.6.8 shall be notified to the application.
The IUT shall be initialised in the test case respectively.
6.4 CTC definition
The definition of each test case specifies, whether the IUT is a master or slave node. Each CTC is defined
in the structure as defined in Table 1.
Table 1 — CTC definition example
Item Content
CTC # – Title [OSI layer #].CTC_[number_name]
E.g. 8.CTC_1.4 – State machine – Slave node – Sleep permission
Purpose This CTC shall verify …
E.g. This CTC verifies the test for the slave node to transit into the sleep state with sleep per-
mission. This CTC is applicable only to an IUT, which supports the wake-up/sleep feature.
Reference REQ document, REQ number – REQ name
E.g. ISO 20794-2:2020, REQ 8.3 APP – NM – Normal, standby, and sleep states;
Prerequisite The test system set-up shall be in accordance with Figure 2.
The clock master is implemented in the LT of the test system.
Set-up — The IUT shall be configured as a slave node.
— The IUT shall be configured to default (see 6.6) and in addition support W/S_RdySleep
configurations (see 6.6.6).
— The bit rate shall be set to the default value (see 6.6).
— The SUT shall be initialised to the sleep state (see 6.7.3).
4 © ISO 2020 – All rights reserved

Table 1 (continued)
Item Content
Step 1. A short description of the test step e.g. LT shall transmit the wake-up pulse.
2. A short description of the test step e.g. LT shall observe any messages on the CXPI
network and shall report to the UT.
Iteration Definition of repetitions of test procedure steps.
Example:
REPEAT step 1 to step 2, 5 times;
…;
REPEAT END.
Expected Define the expected behaviour of IUT by checking on the CXPI network when the test step is
response executed. Example:
After step 1: the IUT shall receive a wake-up notification pulse, waits t time
cxpi_network_error
from the wake-up pulse.
After step 2: the LT shall report the observation on the CXPI network to the UT.
Remark E.g. either "---" if no remark or "Observation of t time and t time starts
wakeup_schedule_m wakeup_m
from second rising edge of clock."
6.5 Test system set-up
The test system set-up follows ISO/IEC 9646-1 and consists of a test system and a system under test
(SUT) connected via the physical medium. The test system implements an upper tester (UT) and a lower
tester (LT). The test system uses set-up parameters (see Figure 2, key 1) for testing the communication
with the IUT.
The UT uses the test control protocol (see Figure 2, key 2) to control the LT.
The point of control and observation (PCO) functionality between the UT of the test system and the UT
App test stub in the SUT is provided by direct logical access to the abstract service primitive interface
[ASPs (ETSs), PCO, see dashed line in Figure 2, key 3] and the associated parameters of the OSI layer as
specified in the ISO 20794 series.
The UT App test stub in the SUT (see Figure 2, key 4) supports an equivalent part of the ASP (see
Figure 2, key 3) and the associated parameters to control and measure the state(s) of the IUT.
The UT App in the test system, which represents the conformance test controller, manipulates the
service primitive interface parameters in the IUT App test stub via the ASPs (ETSs) and PCO of the OSI
layers to fulfil the purpose of each CTC.
If the IUT is a master node then the LT functions as a slave node. If the IUT is a slave node then the LT
functions as a master node. The test system ensures the precision of the bit time and bit synchronisation
of the master node as specified in ISO 20794-4:2020, 9.3.7.
Key
1 set-up parameters (CXPI node's electronic data sheet)
2 test control protocol
3 abstract service primitives (ASPs) based on enhanced testability services (ETS) and points of control and
observation (PCO)
4 upper tester application test stub
Figure 2 — Test system set-up
6.6 Configuration of test system and IUT
6.6.1 General
The test system requires set-up parameters (see Figure 2 key 1), which specify OSI layer properties
of the IUT. The IUT-specific data sheet (see Figure 2 key 1) includes set-up parameters, which the test
system requires for the conformance test cases.
Table 2 defines the configurations of the test system and the IUT.
6 © ISO 2020 – All rights reserved

Table 2 — Configuration of test system and IUT
Configuration item Configuration of test system and IUT
W/S W/S W/S W/S _ A_WSSup Non ErrDet Event Polling
_Init _passive _Rdy Not Rdy W/S
Sleep Sleep
Internal condition of 1 0 1 1 --- --- --- --- ---
2 2 2 2
wake-up
Transmission method --- --- --- --- --- --- --- event polling
Wake-up/sleep 1 1 1 1 0 --- --- --- ---
2 2 2 2 2
TST_FRM_05_REQ_ --- --- --- --- supported --- supported --- ---
PID_ERRBIT by IUT by IUT
Condition of sleep per- 1 1 1 0 --- 0 0 --- ---
2 2 2 2 2 2
mission (sleep_ind)
Table 3 specifies test message names which are used by the IUT and the test system in the CTCs. In each
CTC description, the message setting is specified in the 'Definition' column. If there is no reference to
Table 3, the settings are specified in the CTC.
Table 3 — Configuration of test messages used by IUT and test system
Name Definition
TST_MSG_00_REQ_PTYPE Test message 00 of master node including a ReqTypeId value (00 ) of
16 16
A_ReqId.
TST_MSG_01_REQ_PID Test message 01 of master or slave node including an A_PID value (01
16 16
to 7F ,) of A_ReqId.
TST_MSG_02_REQ_PID_SLEEP Test message 02 for master node including an A_PID value (1F ) of A_ReqId
16 16
for diagnostic and node configuration requests or sleep message.
TST_MSG_03_REQ_PID_UNKNOWN Test message 03 for master or slave node including a not defined A_PID
value of A_ReqId (not defined for reception/transmission by IUT).
TST_MSG_04_REQ_PID_INVALID Test message 04 for master or slave node including an A_PID value of
A_ReqId (not defined for reception/transmission by IUT with an incorrect
parity bit) determined by A_Length = 01 .
TST_MSG_05_REQ_PID_ERRBIT Test message 05 of master or slave node including an error bit A_PID value
(01 to 7F ) of L_ReqId.
16 16
The value of this PID can use a supplier-specific ReqId.
TST_MSG_10_RESP_0-12 Test message 10 for master or slave node including FI field, DATA field and
CRC field determined by 00 ≤ A_Lenght ≤ 0C .
16 16
TST_MSG_11_RESP_12 Test message 11 for master or slave node including FI field, DATA field and
CRC field determined by A_Length = 0C .
TST_MSG_14_RESP_LONG_0-255 Test message 14 of master or slave node including FI field, DATA field and
CRC field determined by 00 ≤ A_Length ≤ FF .
16 16
TST_MSG_17_RESP_SLEEP_8 Test message 17 of master node including FI field, fixed byte pattern of
DATA field and CRC field fixed byte pattern is (00 , FF , FF , FF , FF ,
16 16 16 16 16
FF , FF , FF ) determined by A_Length = 08 .
16 16 16 16
TST_MSG_18_RESP_ERRBIT_0-12 Test message 18 of master node including FI field, DATA field with an error
bit and CRC field determined by 00 ≤ A_Length ≤ 0C .
16 16
6.6.2 IUT-specific set-up parameters
The set-up parameters include at least the following information.
— The request identifier uses 01 to 7F and uses 00 in the request protected type identifier field.
16 16 16
— The CXPI node wake-up uses a wake-up trigger based on the parameter wakeup_ind value 0 or 1 .
2 2
— The transmission method is set to either the event-triggered method or the polling method.
— The condition of sleep permission uses the bit value 0 or 1 as sleep_ind.
2 2
— The bit rate is set to the default value of 20 kbit/s if not otherwise specified.
— The frame with request identifier 3F and the associated response field is reserved for supplier
specific maintenance, enhanced testability services, and error bit status reporting.
6.6.3 User_Specific configurations
The User_Specific parameters include at least the following information:
— internal condition of wake-up: don't care;
— transmission method: don't care;
— wake-up/sleep: don't care;
— condition of sleep permission (sleep_ind): don't care.
6.6.4 W/S_Init configurations
The W/S_Init parameters include at least the following information:
— internal condition of wake-up: 1 ;
— transmission method: don't care;
— wake-up/sleep: 1 ;
— condition of sleep permission (sleep_ind): 1 .
6.6.5 W/S_Passive configurations
The W/S_Passive parameters include at least the following information:
— Internal condition of wake-up: 0 ;
— transmission method: don't care;
— wake-up/sleep: 1 ;
— condition of sleep permission (sleep_ind): 1 .
6.6.6 W/S_RdySleep configurations
The W/S_RdySleep parameters include at least the following information:
— internal condition of wake-up: 1 ;
— transmission method: don't care;
— wake-up/sleep: 1 ;
— condition of sleep permission (sleep_ind): 1 .
6.6.7 W/S_NotRdySleep configurations
The W/S_NotRdySleep parameters include at least the following information:
— internal condition of wake-up: 1 ;
8 © ISO 2020 – All rights reserved

— transmission method: don't care;
— wake-up/sleep: 1 ;
— condition of sleep permission (sleep_ind): 0 .
6.6.8 A_WSSup configurations
The A_WSSup parameters include at least the following information:
— transmission method: don't care;
— wake-up/sleep: 0 ;
— TST_FRM_05_REQ_PID_ERRBIT: supported by the IUT;
— condition of sleep permission (sleep_ind): don't care.
6.6.9 NonW/S configurations
The NonW/S parameters include at least the following information:
— internal condition of wake-up: not applicable;
— transmission method: don't care;
— wake-up/sleep: not applicable;
— TST_FRM_05_REQ_PID_ERRBIT: supported by the IUT;
— condition of sleep permission (sleep_ind): 0 .
6.6.10 ErrDet configurations
The ErrDet parameters include at least the following information:
— internal condition of wake-up: don't care;
— transmission method: don't care;
— wake-up/sleep: don't care;
— condition of sleep permission (sleep_ind): 0 .
6.6.11 Event configurations
The event parameters include at least the following information:
— internal condition of wake-up: don't care;
— transmission method: event;
— wake-up/sleep: don't care;
— condition of sleep permission (sleep_ind): don't care.
6.6.12 Polling configurations
The polling parameters include at least the following information:
— internal condition of wake-up: don't care;
— transmission method: polling;
— wake-up/sleep: don't care;
— condition of sleep permission (sleep_ind): don't care.
6.7 SUT initialisation
6.7.1 General
An initialisation of the IUT shall be performed before each CTC.
6.7.2 Default initialisation
The IUT shall be reset so that the transmission/reception of an A_ReqIds shall be configured and the
error counter value is reset (0). If the IUT is a master node, it shall be ready to transmit the request field
to the lower OSI layers. If the IUT is a slave node, it shall be ready to transmit the response PDUs upon
the reception of A_ReqId from the master node.
6.7.3 Sleep initialisation
IUT shall support wake-up/sleep function and be in the sleep state specified in ISO 20794-2:2020, 9.3.4.
6.7.4 Power-off initialisation
The IUT shall be in the state of power-off.
6.7.5 Transmission prohibition initialisation
IUT shall be in the transmission prohibition specified in ISO 20794-2:2020, 9.6.6.
6.7.6 Clock supply of secondary clock master initialisation
IUT with secondary clock master function shall be in the state of supplying clock.
7 Application conformance test plan
7.1 General
The application conformance test evaluates the operation sequence of each message according to
ISO 20794-2.
The CTCs specified in this document cover the protocol functionality specified in ISO 20794-2. Such
parameters and features are:
— A_ReqTypeId;
— A_ReqId;
— A_PDU (Response field);
— system state.
7.2 Network management
7.2.1 General
The wake-up/sleep function is an optional feature. Transmission and reception of messages by each
node can be started or stopped. After the master node confirms the sleep prohibition of each slave node,
10 © ISO 2020 – All rights reserved

it directs the stop of the transmission and reception of the message. The restart of the transmission and
reception of the message is achieved by putting a trigger onto the CXPI network, which is received by
each node.
7.2.2 State transition definition
State transitions that occur between wake-up and sleep for each node are specified in ISO 20794-2:
a) sleep state;
b) standby state; and
c) normal state.
7.2.3 State transition CTCs
7.2.3.1 8.CTC_1.1 – State machine – Master node – Wake-up/Sleep supported
Table 4 specifies this CTC.
Table 4 — State machine – Master node – Wake-up/Sleep supported
Item Content
CTC # – Title 8.CTC_1.1 – State machine – Master node – Wake-up/Sleep supported
Purpose This CTC verifies that the master node transits into the sleep state.
This CTC is applicable only to an IUT, which supports the wake-up/sleep feature.
Reference ISO 20794-2:2020:
— REQ 8.3 APP – NM – Normal, standby, and sleep states;
— REQ 8.10 APP – NM – Sleep state (optional);
— REQ 8.11 APP– NM – Wake-up/sleep supported.
Prerequisite The test system set-up shall be in accordance with Figure 2.
Set-up — The IUT shall be configured as a master node.
— The IUT shall be configured to support W/S_Passive configurations (see 6.6.5).
— The bit rate shall be set to the default value (see 6.6).
— The IUT shall be initialised to the power-off (see 6.7.4).
Step 1. The IUT shall be powered.
Iterations Not applicable
Expected re- After step 1: The IUT shall not transmit or receive any messages.
sponse
The LT shall report no message and request transmission to the UT.
Remark ---
7.2.3.2 8.CTC_1.2 – State machine – Master node – Wake-up/Sleep not supported
Table 5 specifies this CTC.
Table 5 — State machine – Master node – Wake-up/Sleep not supported
Item Content
CTC # – Title 8.CTC_1.2 – State machine – Master node – Wake-up/Sleep not supported
Purpose This CTC verifies that the master node transits into the normal state.
This CTC is applicable only to an IUT, which does not support the wake-up/sleep feature.
Reference ISO 20794-2:2020:
— REQ 8.3 APP – NM – Normal, standby, and sleep states;
— REQ 8.4 APP – NM – Event-triggered method in normal state – Wake-up/sleep not
supported;
— REQ 8.43 APP – Measurement and control data – Assignment of ReqId;
— REQ 7.3 AL – Request protected type identifier field;
— REQ 7.4 AL – Request protected type identifier field – General.
Prerequisite The test system set-up shall be in accordance with Figure 2.
Set-up — The IUT shall be configured as a master node.
— The IUT shall be configured to support NonW/S configurations (see 6.6.9), TST_MSG_00_
REQ_PTYPE, and TST_MSG_01_REQ_PID.
— The bit rate shall be set to the default value (see 6.6).
— The IUT shall be initialised to the power-off (see 6.7.4).
Step 1. The IUT shall be powered.
2. The UT shall control the IUT to transmit the clock.
3. The UT shall control the IUT to transmit the TST_MSG_00_REQ_PTYPE or the TST_
MSG_01_REQ_PID.
Iterations Not applicable
Expected re- After step 2: The LT shall detect the clock.
sponse
After step 3: The LT shall receive the TST_MSG_00_REQ_PTYPE or the TST_MSG_01_REQ_PID
and shall report to the UT.
Remark ---
7.2.3.3 8.CTC_1.3 – State machine – Slave node – Wake-up/Sleep supported
Table 6 specifies this CTC.
Table 6 — State machine – Slave node – Wake-up/Sleep supported
Item Content
CTC # – Title 8.CTC_1.3 – State machine – Slave node – Wake-up/Sleep supported
Purpose This CTC verifies that the slave node transits into the sleep state.
This CTC is applicable only to an IUT, which supports the wake-up/sleep feature.
12 © ISO 2020 – All rights reserved

Table 6 (continued)
Item Content
Reference ISO 20794-2:2020:
— REQ 8.3 APP – NM – Normal, standby, and sleep states;
— REQ 8.10 APP – NM – Sleep state (optional);
— REQ 8.11 APP– NM – Wake-up/sleep supported;
— REQ 8.13 APP – NM – Wake-up/sleep supported.
Prerequisite The test system set-up shall be in accordance with Figure 2.
Set-up — The IUT shall be configured as a slave node.
— The IUT shall be configured to support W/S_passive configurations (see 6.6.5).
— The bit rate shall be set to the default value (see 6.6).
— The SUT shall be initialised to the power-off initialisation (see 6.7.4).
Step 1. The IUT shall be powered.
Iterations Not applicable
Expected re- After step 1: The LT shall report no message and request transmission to the UT.
sponse
Remark ---
7.2.3.4 8.CTC_1.4 – State machine – Slave node – Sleep permission
Table 7 specifies this CTC.
Table 7 — State machine – Slave node – Sleep permission
Item Content
CTC # – Title 8.CTC_1.4 – State machine – Slave node – Sleep permission
Purpose This CTC verifies that the slave node transits into the sleep state with sleep permission.
This CTC is applicable only to an IUT, which supports the wake-up/sleep feature.
Reference ISO 20794-2:2020:
— REQ 8.3 APP – NM – Normal, standby, and sleep states;
— REQ 8.15 APP – NM – Master node wake-up request/notification – Internal event
notification;
— REQ 8.16 APP – NM – Master node wake-up request/notification – Transit from standby
state into normal state;
— REQ 8.17 APP – NM – Master node wake-up request/notification – Master node wake-up
sequence;
— REQ 8.18 APP – NM – Master node wake-up request/notification – Master node wake-up
sequence – t time;
clock_start_m
— REQ 8.39 APP – NM – Measurement and/or control data types – Single publisher.
Prerequisite The test system set-up shall be in accordance with Figure 2.
The clock master is not available in the SUT.
Table 7 (continued)
Item Content
Set-up — The IUT shall be configured as a slave node.
— The IUT shall be configured to support W/S_RdySleep configurations (see 6.6.6).
— The bit rate shall be set to the default value (see 6.6).
— The SUT shall be initialised to the sleep state (see 6.7.3).
Step 1. The UT shall control the IUT to transmit wake-up pulse.
2. The LT shall not transmit the clock.
Iterations Not applicable
Expected re- After step 1: The LT shall receive the wake-up pulse and shall report to the UT.
sponse
After step 2: The IUT shall transit into the sleep state after t elapsed.
cxpi_network_error
Remark The UT is connected to a multi-meter to measure current consumption of the IUT.
After the IUT transits into the sleep state, the UT measures that the current consumption of the
IUT is less than the value specified in the IUT data sheet.
7.2.3.5 8.CTC_1.5 – State machine – Slave node – Sleep prohibition
Table 8 specifies this CTC.
Table 8 — State machine – Slave node – Sleep prohibition
Item Content
CTC # – Title 8.CTC_1.5 – State machine – Slave node – Sleep prohibition
Purpose This CTC verifies that the slave node with sleep prohibition does not transit into the sleep state.
This CTC is applicable only to an IUT, which supports the wake-up/sleep feature.
Reference ISO 20794-2:2020:
— REQ 8.3 APP – NM – Normal, standby, and sleep states;
— REQ 8.10 APP – NM – Sleep state (optional);
— REQ 8.12 APP – NM – Standby state (optional).
Prerequisite The test system set-up shall be in accordance with Figure 2.
The clock master is not available in the SUT.
Set-up — The IUT shall be configured as a slave node.
— The IUT shall be configured to support W/S_NotRdySleep configurations (see 6.6.7).
— The bit rate shall be set to the default value (see 6.6).
— The SUT shall be initialised to the sleep state (see 6.7.3).
Step 1. The UT shall control the IUT to transmit wake-up pulse.
2. The LT shall not transmit the clock.
Iterations Not Applicable
Expected re- After step 1: The LT shall receive the wake-up pulse and shall report to the UT.
sponse
After step 2: The IUT shall stay in the standby state after t elapsed.
cxpi_network_error
Remark The UT is connected to a multi-meter to measure current consumption of the IUT.
After the IUT transits into the standby state, the UT measures that the current consumption of
the IUT is less than the value specified in the IUT data sheet.
14 © ISO 2020 – All rights reserved

7.2.3.6 8.CTC_1.6 – State machine – Slave node – Transition into the normal state
Table 9 specifies this CTC.
Table 9 — State machine – Slave node – Transition into the normal state
Item Content
CTC # – Title 8.CTC_1.6 – State machine – Slave node – Transition into the normal state
Purpose This CTC verifies that the slave node transits into the normal state.
This CTC is applicable only to an IUT, which supports the wake-up/sleep feature.
Reference ISO 20794-2:2020:
— REQ 8.3 APP – NM – Normal, standby, and sleep states;
— REQ 8.4 APP – NM – Event-triggered method in normal state – Wake-up/sleep not
supported;
— REQ 8.47 APP – NM – Network management.
Prerequisite The test system set-up shall be in accordance with Figure 2.
Set-up — The IUT shall be configured as a slave node.
— The IUT shall be configured to support NonW/S configurations (see 6.6.9), TST_MSG_01_
REQ_PID and TST_MSG_10_RESP_0-12.
— The bit rate shall be set to the default value (see 6.6).
— The SUT shall be initialised to the power-off (see 6.7.4).
Step 1. The IUT shall be p
...