iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 26021-1:2022

(Main)

Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 1: Application and communication interface

Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 1: Application and communication interface

This document is applicable to road vehicles, where the electronic vehicle interface of the diagnostic link connector (DLC) is used to perform an end-of-life (EoL) activation of in-vehicle pyrotechnic devices. Apart from actual removal, this is the method to assure that no pyrotechnic substances are left in an EoL vehicle. On-board activation is an effective and safe method. This document describes use cases and specifies technical requirements in order to support the end-of-life activation of in-vehicle pyrotechnic devices via the electronic communication interface. This document references the ISO 14229 series unified diagnostic services implemented on diagnostic communication over controller area network (DoCAN) and Internet Protocol (DoIP) along with the required provision of data definitions. This document comprises: — terminology definitions; — definition of end-of-life activation of in-vehicle pyrotechnic devices relevant use cases; — requirements for the establishment of communication between the pyrotechnic device deployment tool (PDT) and the vehicle's pyrotechnic control unit(s) (PCU(s)); — requirements for the optional usage of a credentials-based authentication and authorisation mechanism between the PDT and the vehicle; — requirements for the protection against tampering of the defined end-of-life activation of in-vehicle pyrotechnic devices; — PCU-relevant technical requirements. PDT-relevant requirements are specified in a test equipment-specific standard with PDT-specific requirements.

Véhicules routiers — Activation de fin de vie des dispositifs pyrotechniques embarqués — Partie 1: Interface des couches application et communication

General Information

Status
Published
Publication Date
20-Feb-2022
ICS
43.040.80 - Crash protection and restraint systems
Technical Committee
ISO/TC 22/SC 31 - Data communication
Drafting Committee
ISO/TC 22/SC 31/WG 4 - Network applications
Current Stage
6060 - International Standard published
Start Date
21-Feb-2022
Due Date
29-Jun-2023
Completion Date
21-Feb-2022
Ref Project

Relations

Revises
ISO 26021-5:2009 - Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 5: Additional communication line with pulse width modulated signal
Effective Date
06-Jun-2022
Revises
ISO 26021-4:2009 - Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 4: Additional communication line with bidirectional communication
Effective Date
06-Jun-2022
Revises
ISO 26021-2:2008 - Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 2: Communication requirements
Effective Date
06-Jun-2022
Revises
ISO 26021-1:2008 - Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 1: General information and use case definitions
Effective Date
10-Jul-2021

Buy Standard

ISO 26021-1:2022 - Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 1: Application and communication interface Released:2/21/2022ISO 26021-1:2022 - Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 1: Application and communication interface Released:2/21/2022
PreviousNext
Standard
ISO 26021-1:2022 - Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 1: Application and communication interface Released:2/21/2022
English language
88 pages
sale 15% off
Preview
sale 15% off
Preview
ISO/PRF 26021-1 - Road vehicles -- End-of-life activation of in-vehicle pyrotechnic devicesISO/PRF 26021-1 - Road vehicles -- End-of-life activation of in-vehicle pyrotechnic devices
PreviousNext
Draft
ISO/PRF 26021-1 - Road vehicles -- End-of-life activation of in-vehicle pyrotechnic devices
English language
88 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 26021-1
Second edition
2022-02
Road vehicles — End-of-life activation
of in-vehicle pyrotechnic devices —
Part 1:
Application and communication
interface
Véhicules routiers — Activation de fin de vie des dispositifs
pyrotechniques embarqués —
Partie 1: Interface des couches application et communication
Reference number
ISO 26021-1:2022(E)
© ISO 2022

---------------------- Page: 1 ----------------------
ISO 26021-1:2022(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2022
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 2022 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 26021-1:2022(E)
Contents Page
Foreword .vii
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms.3
4.1 Symbols . 3
4.2 Abbreviated terms . 3
5 Conventions . 5
6 Basic principles and use cases overview . 5
6.1 Basic principles . 5
6.2 Use case groups and associated use cases . 6
7 Use cases definition (UC) . 7
7.1 UCG 1 – Perform communication interface discovery . 7
7.1.1 UC 1.1 – Discover DoCAN communication interface. 7
7.1.2 UC 1.2 – Discover DoIP communication interface. 7
7.2 UCG-2 – Perform authentication . 7
7.2.1 UC 2.1 – Perform PDT authentication . 7
7.2.2 UC 2.2 – Perform fixed-address PCU/PCU(s) authentication . 8
7.3 UCG 3 – Perform system initialisation (Sys-Init) . 8
7.3.1 UC 3.1 – Report PCU hardware deployment method . 8
7.3.2 UC 3.2 – Report number of PCU(s) . 9
7.3.3 UC 3.3 – Report address information of PCU(s) . 9
7.3.4 UC 3.4 – Report vehicle identification number . 9
7.3.5 UC 3.5 – Report dismantling documentation of PCU . 10
7.4 UCG 4 – Perform PCU initialisation (PCU-Init) . 10
7.4.1 UC 4.1 – Report PCU deployment loop identification table . 10
7.4.2 UC 4.2 – Initiate safetySystemDiagnosticSession . 11
7.4.3 UC 4.3 – Keep-alive safetySystemDiagnosticSession . 11
7.4.4 UC 4.4 – Unlock security of PCU .12
7.4.5 UC 4.5 – Execute PCU(s) scrapping program module loader .12
7.5 UCG 5 – Perform PCU and ACL sequence (PCU- and ACL-Scrapping) .13
7.5.1 UC 5.1 – Report ACL deployment sequence (ACL-Init) .13
7.5.2 UC 5.2 – Write dismantling documentation into PCU (Device-Deploy) .13
7.5.3 UC 5.3 – Perform ACL deployment confirmation sequence (Device-Deploy) . 14
7.5.4 UC 5.4 – Perform PCU pyrotechnic device scrapping via loop identification
(Device-Deploy) . 14
7.6 UCG 6 – Terminate PCU pyrotechnic device deployment (PCU-End) .15
7.6.1 UC 6.1 – Terminate PCU pyrotechnic device scrapping via communication
interface .15
7.6.2 UC 6.2 – Terminate PCU pyrotechnic device scrapping via ACL .15
8 Application (APP) .16
8.1 APP – Preconditions of end-of-life activation of pyrotechnic devices. 16
8.2 APP – Overview of end-of-life activation of pyrotechnic devices sequence . . 17
8.3 APP – Software provisions . 19
8.3.1 APP – Scrapping program module (SPM) . 19
8.3.2 APP – Scrapping program module loader (SPL) . 19
8.3.3 APP – PCU loop identification table . 19
8.4 APP – Mapping of use cases to requirements . 20
8.5 APP – Application timing definition . 21
8.6 APP – Discovery of communication interface (Com I/F-Discovery) .22
iii
© ISO 2022 – All rights reserved

---------------------- Page: 3 ----------------------
ISO 26021-1:2022(E)
8.6.1 APP – Overview of discovery of communication interface (Com-Discovery) .22
8.6.2 APP – Setup DoCAN communication interface .22
8.6.3 APP – Setup DoIP communication interface . 24
8.6.4 APP – Determination of DoCAN or DoIP communication interface in the
vehicle . 25
8.7 APP – Perform authentication – Optional (Sys-Auth) . 26
8.7.1 APP – Overview of the authentication – Optional (Sys-Auth) .26
8.7.2 APP – PDT authentication against fixed-address PCU – Optional (Sys-Auth) .26
8.7.3 APP – Fixed-address PCU authentication against PDT – Optional (Sys-Auth). 27
8.8 APP – Perform system initialisation (Sys-Init) . 27
8.8.1 APP – Overview of the system initialisation (Sys-Init) . 27
8.8.2 APP – Report PcuHardwareDeploymentMethod (Sys-Init).28
8.8.3 APP – Report number of PCUs (Sys-Init) .28
8.8.4 APP – Report DoCAN address information of PCUs (Sys-Init) .28
8.8.5 APP – Report DoIP address information of PCUs (Sys-Init) .30
8.8.6 APP – Report vehicle identification number (Sys-Init) . 31
8.8.7 APP – Report dismantling documentation of PCU (Sys-Init) . 31
8.9 APP – Perform PCU initialisation (PCU-Seq) . 31
8.9.1 APP – Overview of the PCU initialisation (PCU-Seq) . 31
8.9.2 APP – Report PCU deployment loop identification table (PCU-Seq) . 32
8.9.3 APP – Initiate safetySystemDiagnosticSession (PCU-Seq) .33
8.9.4 APP – Keep-alive safetySystemDiagnosticSession (PCU-Seq) .33
8.9.5 APP – Unlock security of PCU (PCU-Seq) . 33
8.9.6 APP – Execute PCU scrapping program module loader (PCU-Seq) .33
8.10 APP – Perform PCU and ACL scrapping (Device-Deploy) .34
8.10.1 APP – Overview of the PCU- and ACL-Scrapping (Device-Deploy) .34
8.10.2 APP – Report ACL deployment sequence (ACL-Prep) .34
8.10.3 APP – Write dismantling documentation into PCU (Device-Deploy) . 35
8.10.4 APP – Confirm ACL deployment sequence (Device-Deploy) . 35
8.10.5 APP – Perform device scrapping (Device-Deploy) . 35
8.10.6 APP – Evaluation of device scrapping (Device-Deploy) . 35
8.10.7 APP – Next pyrotechnic device (Device-Deploy) .36
8.11 APP – Terminate PCU and ACL pyrotechnic device deployment (PCU-End) .36
8.11.1 APP – Overview of the PCU- and ACL-Termination (PCU-End) .36
8.11.2 APP – Terminate PCU pyrotechnic device scrapping (PCU-End) .36
8.11.3 APP – Terminate PCU pyrotechnic device scrapping via ACL (PCU-End) . 37
8.12 APP – Terminate system deployment (Sys-End) . 37
9 Service interface (SI) definition between application and OSI layers .37
9.1 SI — A_Data.req, A_Data.ind, and A_Data.conf service interface (SI) . 37
9.2 SI — A_Data.req, A_Data.ind, and A_Data.conf service interface (SI) parameter
mapping .38
9.3 Service interface parameters (SIP) . 39
9.3.1 SIP – General .39
9.3.2 SIP – Data type definitions .39
9.3.3 SIP – Mtype, message type .39
9.3.4 SIP – TAtype, target address type .39
9.3.5 SIP – AE, address extension .39
9.3.6 SIP – TA, target address . 39
9.3.7 SIP – SA, source address .40
9.3.8 SIP – Length, length of PDU .40
9.3.9 SIP – PDU, protocol data unit .40
9.3.10 SIP – Result, result .40
10 Application layer (AL) .40
10.1 AL – Applicable ISO 14229-1 UDS functionality .40
10.2 AL – PCU timing parameters . 41
10.3 AL – Authentication . 41
10.3.1 AL – Requirements specification – PDT authentication . 41
iv
  © ISO 2022 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 26021-1:2022(E)
10.3.2 AL – Requirements specification – Fixed-address PCU/PCU(s) authentication . 42
10.4 AL – ReadDataByIdentifier – Read PCU hardware deployment method . 42
10.4.1 AL – Requirements specification – Read PCU hardware deployment method . 42
10.4.2 AL – Message sequence requirements – Read
PcuHardwareDeploymentMethod . 43
10.4.3 AL – Message sequence example – Read PcuHardwareDeploymentMethod. 43
10.5 AL – ReadDataByIdentifier – Read NumberOfPcu in vehicle .44
10.5.1 AL – Requirements specification – Read NumberOfPcu in vehicle .44
10.5.2 AL – Message sequence requirements – Read number of PCUs in vehicle .44
10.5.3 AL – Message sequence example – Read NumberOfPcu in vehicle . 45
10.6 AL – ReadDataByIdentifier – Read PcuAddressInfo . 45
10.6.1 AL – Requirements specification – Read PcuAddressInfo . 45
10.6.2 AL – Message sequence requirements – Read PcuAddressInfo of PCU .46
10.6.3 AL – Message sequence example – Read PcuAddressInfo of DoCAN PCU .46
10.6.4 AL – Message sequence example – Read PcuAddressInfo of DoIP PCU . 47
10.7 AL – ReadDataByIdentifier – Report VIN from PCU.48
10.7.1 AL – Requirements specification – Report VIN from PCU.48
10.7.2 AL – Message sequence requirements – Report VIN from PCU .48
10.7.3 AL – Message sequence example – Report VIN from PCU .48
10.8 AL – ReadDataByIdentifier – Report dismantler information .49
10.8.1 AL – Requirements specification – Report dismantler information .49
10.8.2 AL – Message sequence requirements – Report dismantler information .50
10.8.3 AL – Message sequence example – Report dismantler information .50
10.9 AL – ReadDataByIdentifier – Read deployment loop identification table .50
10.9.1 AL – Requirements specification – Read deployment loop identification
table .50
10.9.2 AL – Message sequence requirements – Read deployment loop
identification table. 51
10.9.3 AL – Message sequence example – Read deployment loop identification table . 52
10.10 AL – DiagnosticSessionControl – safetySystemDiagnosticSession .53
10.10.1 AL – Requirements specification – safetySystemDiagnosticSession .53
10.10.2 AL – Message sequence requirements – safetySystemDiagnosticSession .53
10.10.3 AL – Message sequence example – safetySystemDiagnosticSession .53
10.11 AL – TesterPresent .54
10.11.1 AL – Requirements specification – TesterPresent.54
10.11.2 AL – Message sequence requirements – TesterPresent .54
10.11.3 AL – Message sequence example – TesterPresent . 55
10.12 AL – SecurityAccess . 55
10.12.1 AL – Requirements specification – SecurityAccess . 55
10.12.2 AL – Message sequence requirements – SecurityAccess .56
10.12.3 AL – Message sequence example – SecurityAccessType = RequestSeed . 57
10.12.4 AL – Message sequence example –
SecurityAccessType = SendDeploymentKey . 57
10.13 AL – WriteDataByIdentifier – Write dismantler information .58
10.13.1 AL – Requirements specification – Write dismantler identification
information .58
10.13.2 AL – Message sequence requirements – Write dismantler identification
information .58
10.13.3 AL – Message sequence example – Write dismantler identification
information . 59
10.14 AL – RoutineControl . 59
10.14.1 AL – Requirements specification – RoutineControl . 59
10.14.2 AL – Message sequence requirements – RoutineControl . 61
10.14.3 AL – Message sequence example – ExecuteSPL with SF = startRoutine . 61
10.14.4 AL – Message sequence example – ExecuteSPL with
SF = requestRoutineResult . 62
10.14.5 AL – Message sequence example – DeployLoopRoutineID with
SF = startRoutine . 62
v
© ISO 2022 – All rights reserved

---------------------- Page: 5 ----------------------
ISO 26021-1:2022(E)
10.14.6 AL – Message sequence example – DeployLoopRoutineID with
SF = requestRoutineResult .63
10.15 AL – ACL request deployment sequence (optional) .64
10.15.1 AL – Requirements specification – ACL request deployment sequence .64
10.15.2 AL – Message sequence requirements – ACL request deployment sequence .64
10.16 AL – ACL confirm deployment sequence (optional) .64
10.16.1 AL – Requirements specification – ACL confirm deployment sequence.64
10.16.2 AL – Message sequence requirements – ACL confirm deployment sequence
(optional) .65
10.17 AL – ACL terminate deployment sequence (optional) .65
10.17.1 AL – Requirements specification – ACL terminate deployment sequence
(optional) .65
10.17.2 AL – Message sequence requirements – ACL terminate deployment sequence .65
10.18 AL – EcuReset .66
10.18.1 AL – Requirements specification – EcuReset.66
10.18.2 AL – Message sequence requirements – EcuReset .66
10.18.3 AL – Message sequence example – hardReset .66
11 Presentation layer (PL) .67
11.1 PL – Data type UNUM8 . 67
11.2 PL – Data type UNUM16 . 67
11.3 PL – Data type UNUM32 . 67
11.4 PL – Data type UCHAR8 . 67
12 Session layer (SL) .67
12.1 SL – Timing parameters . 67
12.2 SL – Error detection .68
13 Transport layer (TL) .68
13.1 TL – DoCAN . .68
13.2 TL – DoIP .68
14 Network layer (NL) .68
14.1 NL – DoCAN .68
14.2 NL – DoIP .69
15 Data link layer (DLL) . .69
15.1 DLL – CAN L_Data frame padding bytes . 69
15.2 DLL – ACL with bidirectional communication . 69
15.2.1 DLL – tP4_Send
...

INTERNATIONAL ISO
STANDARD 26021-1
Second edition
Road vehicles — End-of-life activation
of in-vehicle pyrotechnic devices —
Part 1:
Application and communication
interface
Véhicules routiers — Activation de fin de vie des dispositifs
pyrotechniques embarqués —
Partie 1: Interface des couches application et communication
PROOF/ÉPREUVE
Reference number
ISO 26021-1:2021(E)
© ISO 2021

---------------------- Page: 1 ----------------------
ISO 26021-1:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2021
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
PROOF/ÉPREUVE © ISO 2021 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 26021-1:2021(E)
Contents Page
Foreword .viii
Introduction .ix
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms.3
4.1 Symbols . 3
4.2 Abbreviated terms . 3
5 Conventions . 5
6 Basic principles and use cases overview . 5
6.1 Basic principles . 5
6.2 Use case groups and associated use cases . 6
7 Use cases definition (UC) . 7
7.1 UCG 1 – Perform communication interface discovery . 7
7.1.1 UC 1.1 – Discover DoCAN communication interface. 7
7.1.2 UC 1.2 – Discover DoIP communication interface. 7
7.2 UCG-2 – Perform authentication . 7
7.2.1 UC 2.1 – Perform PDT authentication . 7
7.2.2 UC 2.2 – Perform fixed-address PCU/PCU(s) authentication . 8
7.3 UCG 3 – Perform system initialisation (Sys-Init) . 8
7.3.1 UC 3.1 – Report PCU hardware deployment method . 8
7.3.2 UC 3.2 – Report number of PCU(s) . 9
7.3.3 UC 3.3 – Report address information of PCU(s) . 9
7.3.4 UC 3.4 – Report vehicle identification number . 9
7.3.5 UC 3.5 – Report dismantling documentation of PCU . 10
7.4 UCG 4 – Perform PCU initialisation (PCU-Init) . 10
7.4.1 UC 4.1 – Report PCU deployment loop identification table . 10
7.4.2 UC 4.2 – Initiate safetySystemDiagnosticSession . 11
7.4.3 UC 4.3 – Keep-alive safetySystemDiagnosticSession . 11
7.4.4 UC 4.4 – Unlock security of PCU .12
7.4.5 UC 4.5 – Execute PCU(s) scrapping program module loader .12
7.5 UCG 5 – Perform PCU and ACL sequence (PCU- and ACL-Scrapping) .13
7.5.1 UC 5.1 – Report ACL deployment sequence (ACL-Init) .13
7.5.2 UC 5.2 – Write dismantling documentation into PCU (Device-Deploy) .13
7.5.3 UC 5.3 – Perform ACL deployment confirmation sequence (Device-Deploy) . 14
7.5.4 UC 5.4 – Perform PCU pyrotechnic device scrapping via loop identification
(Device-Deploy) . 14
7.6 UCG 6 – Terminate PCU pyrotechnic device deployment (PCU-End) .15
7.6.1 UC 6.1 – Terminate PCU pyrotechnic device scrapping via communication
interface .15
7.6.2 UC 6.2 – Terminate PCU pyrotechnic device scrapping via ACL .15
8 Application (APP) .16
8.1 APP – Preconditions of end-of-life activation of pyrotechnic devices. 16
8.2 APP – Overview of end-of-life activation of pyrotechnic devices sequence . . 17
8.3 APP – Software provisions . 19
8.3.1 APP – Scrapping program module (SPM) . 19
8.3.2 APP – Scrapping program module loader (SPL) . 19
8.3.3 APP – PCU loop identification table . 19
8.4 APP – Mapping of use cases to requirements . 20
8.5 APP – Application timing definition . 21
8.6 APP – Discovery of communication interface (Com I/F-Discovery) .22
iii
© ISO 2021 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 3 ----------------------
ISO 26021-1:2021(E)
8.6.1 APP – Overview of discovery of communication interface (Com-Discovery) .22
8.6.2 APP – Setup DoCAN communication interface .22
8.6.3 APP – Setup DoIP communication interface . 24
8.6.4 APP – Determination of DoCAN or DoIP communication interface in the
vehicle . 25
8.7 APP – Perform authentication – Optional (Sys-Auth) . 26
8.7.1 APP – Overview of the authentication – Optional (Sys-Auth) .26
8.7.2 APP – PDT authentication against fixed-address PCU – Optional (Sys-Auth) .26
8.7.3 APP – Fixed-address PCU authentication against PDT – Optional (Sys-Auth). 27
8.8 APP – Perform system initialisation (Sys-Init) . 27
8.8.1 APP – Overview of the system initialisation (Sys-Init) . 27
8.8.2 APP – Report PcuHardwareDeploymentMethod (Sys-Init).28
8.8.3 APP – Report number of PCUs (Sys-Init) .28
8.8.4 APP – Report DoCAN address information of PCUs (Sys-Init) .28
8.8.5 APP – Report DoIP address information of PCUs (Sys-Init) .30
8.8.6 APP – Report vehicle identification number (Sys-Init) . 31
8.8.7 APP – Report dismantling documentation of PCU (Sys-Init) . 31
8.9 APP – Perform PCU initialisation (PCU-Seq) . 31
8.9.1 APP – Overview of the PCU initialisation (PCU-Seq) . 31
8.9.2 APP – Report PCU deployment loop identification table (PCU-Seq) . 32
8.9.3 APP – Initiate safetySystemDiagnosticSession (PCU-Seq) . 33
8.9.4 APP – Keep-alive safetySystemDiagnosticSession (PCU-Seq) .33
8.9.5 APP – Unlock security of PCU (PCU-Seq) . 33
8.9.6 APP – Execute PCU scrapping program module loader (PCU-Seq) .33
8.10 APP – Perform PCU and ACL scrapping (Device-Deploy) .34
8.10.1 APP – Overview of the PCU- and ACL-Scrapping (Device-Deploy) .34
8.10.2 APP – Report ACL deployment sequence (ACL-Prep) .34
8.10.3 APP – Write dismantling documentation into PCU (Device-Deploy) .35
8.10.4 APP – Confirm ACL deployment sequence (Device-Deploy) . 35
8.10.5 APP – Perform device scrapping (Device-Deploy) . 35
8.10.6 APP – Evaluation of device scrapping (Device-Deploy) . 35
8.10.7 APP – Next pyrotechnic device (Device-Deploy) .36
8.11 APP – Terminate PCU and ACL pyrotechnic device deployment (PCU-End) .36
8.11.1 APP – Overview of the PCU- and ACL-Termination (PCU-End) .36
8.11.2 APP – Terminate PCU pyrotechnic device scrapping (PCU-End) .36
8.11.3 APP – Terminate PCU pyrotechnic device scrapping via ACL (PCU-End) . 37
8.12 APP – Terminate system deployment (Sys-End) . 37
9 Service interface (SI) definition between application and OSI layers .37
9.1 SI — A_Data.req, A_Data.ind, and A_Data.conf service interface (SI) . 37
9.2 SI — A_Data.req, A_Data.ind, and A_Data.conf service interface (SI) parameter
mapping .38
9.3 Service interface parameters (SIP) . 39
9.3.1 SIP – General .39
9.3.2 SIP – Data type definitions . 39
9.3.3 SIP – Mtype, message type . 39
9.3.4 SIP – TAtype, target address type .39
9.3.5 SIP – AE, address extension . 39
9.3.6 SIP – TA, target address . 39
9.3.7 SIP – SA, source address .40
9.3.8 SIP – Length, length of PDU .40
9.3.9 SIP – PDU, protocol data unit .40
9.3.10 SIP – Result, result .40
10 Application layer (AL) .40
10.1 AL – Applicable ISO 14229-1 UDS functionality .40
10.2 AL – PCU timing parameters . 41
10.3 AL – Authentication . 41
10.3.1 AL – Requirements specification – PDT authentication . 41
iv
PROOF/ÉPREUVE © ISO 2021 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 26021-1:2021(E)
10.3.2 AL – Requirements specification – Fixed-address PCU/PCU(s) authentication . 42
10.4 AL – ReadDataByIdentifier – Read PCU hardware deployment method . 42
10.4.1 AL – Requirements specification – Read PCU hardware deployment method . 42
10.4.2 AL – Message sequence requirements – Read
PcuHardwareDeploymentMethod . 43
10.4.3 AL – Message sequence example – Read PcuHardwareDeploymentMethod. 43
10.5 AL – ReadDataByIdentifier – Read NumberOfPcu in vehicle .44
10.5.1 AL – Requirements specification – Read NumberOfPcu in vehicle .44
10.5.2 AL – Message sequence requirements – Read number of PCUs in vehicle .44
10.5.3 AL – Message sequence example – Read NumberOfPcu in vehicle . 45
10.6 AL – ReadDataByIdentifier – Read PcuAddressInfo . 45
10.6.1 AL – Requirements specification – Read PcuAddressInfo . 45
10.6.2 AL – Message sequence requirements – Read PcuAddressInfo of PCU .46
10.6.3 AL – Message sequence example – Read PcuAddressInfo of DoCAN PCU .46
10.6.4 AL – Message sequence example – Read PcuAddressInfo of DoIP PCU . 47
10.7 AL – ReadDataByIdentifier – Report VIN from PCU.48
10.7.1 AL – Requirements specification – Report VIN from PCU.48
10.7.2 AL – Message sequence requirements – Report VIN from PCU .48
10.7.3 AL – Message sequence example – Report VIN from PCU .48
10.8 AL – ReadDataByIdentifier – Report dismantler information .49
10.8.1 AL – Requirements specification – Report dismantler information .49
10.8.2 AL – Message sequence requirements – Report dismantler information .50
10.8.3 AL – Message sequence example – Report dismantler information .50
10.9 AL – ReadDataByIdentifier – Read deployment loop identification table .50
10.9.1 AL – Requirements specification – Read deployment loop identification
table .50
10.9.2 AL – Message sequence requirements – Read deployment loop
identification table. 51
10.9.3 AL – Message sequence example – Read deployment loop identification table . 52
10.10 AL – DiagnosticSessionControl – safetySystemDiagnosticSession .53
10.10.1 AL – Requirements specification – safetySystemDiagnosticSession .53
10.10.2 .
AL – Message sequence requirements – safetySystemDiagnosticSession .53
10.10.3 .
AL – Message sequence example – safetySystemDiagnosticSession .53
10.11 AL – TesterPresent .54
10.11.1 AL – Requirements specification – TesterPresent.54
10.11.2 .
AL – Message sequence requirements – TesterPresent .54
10.11.3 .
AL – Message sequence example – TesterPresent .55
10.12 AL – SecurityAccess . 55
10.12.1 .
AL – Requirements specification – SecurityAccess .55
10.12.2 .
AL – Message sequence requirements – SecurityAccess .56
10.12.3 .
AL – Message sequence example – SecurityAccessType = RequestSeed . 57
10.12.4 .
AL – Message sequence example –
SecurityAccessType = SendDeploymentKey . 57
10.13 AL – WriteDataByIdentifier – Write dismantler information .58
10.13.1 AL – Requirements specification – Write dismantler identification
information .58
10.13.2 .
AL – Message sequence requirements – Write dismantler identification
information .58
v
© ISO 2021 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 5 ----------------------
ISO 26021-1:2021(E)
10.13.3 .
AL – Message sequence example – Write dismantler identification
information . 59
10.14 AL – RoutineControl . 59
10.14.1 AL – Requirements specification – RoutineControl . 59
10.14.2 AL – Message sequence requirements – RoutineControl . 61
10.14.3 AL – Message sequence example – ExecuteSPL with SF = startRoutine . 61
10.14.4 AL – Message sequence example – ExecuteSPL with
SF = requestRoutineResult . 62
10.14.5 AL – Message sequence example – DeployLoopRoutineID with
SF = startRoutine . 62
10.14.6 AL – Message sequence example – DeployLoopRoutineID with
SF = requestRoutineResult .63
10.15 AL – ACL request deployment sequence (optional) .64
10.15.1 AL – Requirements specification – ACL request deployment sequence .64
10.15.2 .
AL – Message sequence requirements – ACL request deployment sequence .64
10.16 AL – ACL confirm deployment sequence (optional) .64
10.16.1 AL – Requirements specification – ACL confirm deployment sequence.64
10.16.2 .
AL – Message sequence requirements – ACL confirm deployment sequence
(optional) .65
10.17 AL – ACL terminate deployment sequence (optional) .65
10.17.1 AL – Requirements specification – ACL terminate deployment sequence
(optional) .65
10.17.2 AL – Message sequence requirements – ACL terminate deployment sequence .65
10.18 AL – EcuReset .66
10.18.1 AL – Requirements specification – EcuReset.66
10.18.2 .
AL – Message sequence requirements – EcuReset .66
10.18.3 .
AL – Message sequence example – hardReset .66
11 Presentation layer (PL) .67
11.1 PL – Data type UNUM8 . 67
11.2 PL – Data type UNUM16 . 67
11.3 PL – Data type UNUM32 . 67
11.4 PL – Data type UCHAR8 . 67
12 Session layer (SL) .
...

Questions, Comments and Discussion

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

This May Also Interest You

ISO
ISO 26021-3:2022(Main)
Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 3: Data definitions

This document specifies all end-of-life activation of in-vehicle pyrotechnical devices identifiers, data identifiers, routine identifiers, data types, computations, and units. This document is based on: — new safety-relevant system technology designed into the vehicles, — new or more effective end-of-life activation of in-vehicle pyrotechnical devices, which requires additional test data, and routine controls. This document describes the end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements. This document specifies: — identifiers for end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements, — data identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements, — routine identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements.

  • Standard
    14 pages
    English language
    sale 15% off
ISO
ISO 13215-3:2022(Main)
Road vehicles — Reduction of misuse risk of child restraint systems — Part 3: Prediction and assessment of misuse by Misuse Mode and Effect Analysis (MMEA)

This document specifies a method to predict and quantify misuse of child restraint systems (CRS) called Misuse Mode and Effect Analysis (MMEA). Such misuse can degrade the performance of CRSs. As a predictive method it is intended to be applied by CRS manufacturers at an early stage, before the CRS is put into use by consumers. Being predictive implies the possibility of incompleteness and errors. Such errors can be reduced if the proposed method is supported by field studies (for example, according to ISO 13215-1) and panel method evaluation (for example, according to ISO 13215-2).

  • Standard
    11 pages
    English language
    sale 15% off
ISO
ISO 13215-2:2022(Main)
Road vehicles — Reduction of misuse risk of child restraint systems — Part 2: Requirements and test procedures for correct installation (panel method)

This document specifies the requirements and methods for judging the risk of installation misuse of child restraint systems (CRS) with the help of assigned evaluation panels. The methods described can be used regardless of type of installation of the CRS, e.g. with vehicle seat belts, ISOFIX/LATCH and different types of anti-rotation devices. The installation can include the evaluation of the interface between the child and the CRS, e.g. a harness or an impact shield. This document is intended for technical assessment. It can be applied separately or in conjunction with the MMEA evaluation, described in ISO 13215-3.

  • Standard
    11 pages
    English language
    sale 15% off
ISO
ISO 26021-3:2022(Main)
Road vehicles — End-of-life activation of in-vehicle pyrotechnic devices — Part 3: Data definitions

This document specifies all end-of-life activation of in-vehicle pyrotechnical devices identifiers, data identifiers, routine identifiers, data types, computations, and units. This document is based on: — new safety-relevant system technology designed into the vehicles, — new or more effective end-of-life activation of in-vehicle pyrotechnical devices, which requires additional test data, and routine controls. This document describes the end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements. This document specifies: — identifiers for end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements, — data identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements, — routine identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements.

  • Standard
    14 pages
    English language
    sale 15% off
ISO
ISO 23376:2021(Main)
Intelligent transport systems — Vehicle-to-vehicle intersection collision warning systems (VVICW) — Performance requirements and test procedures

This document specifies performance requirements and test procedures for systems capable of warning the subject vehicle driver of a potential crossing-path collision with other vehicles at intersecting road segments. Vehicle-to-vehicle intersection collision warning systems (VVICW) rely on vehicle-to-vehicle (V2V) communications and relative positioning between the subject vehicle and crossing-path vehicles (remote vehicles). V2V data, such as position, speed and heading are used to evaluate if an intersection collision is imminent between the subject and remote vehicles. The performance requirements laid out in this document specify the warning criteria for these systems. In addition, VVICW operate in specified subject and remote vehicle speed ranges, road intersection geometries and target vehicle types. Moreover, the requirements for the V2V data will be specified. The scope of this document includes operations on intersecting road segments (physically intersecting roads), and motor vehicles including cars, trucks, buses and motorcycles. Responsibility for the safe operation of the vehicle remains with the driver.

  • Standard
    18 pages
    English language
    sale 15% off
ISO
ISO/TS 13396:2021(Main)
Road vehicles — Sled test method to enable the evaluation of side impact protection of child restraint systems — Essential parameters

This document comprises a set of essential input parameters that can be used to develop or evaluate side impact test procedures for child restraint systems. Although children are undoubtedly involved in side impact collisions of differing configurations and severities, these input parameters are, in general, associated with the impact test scenario in UN Regulation No. 95 (lateral collision protection of vehicles). This vehicle type-approval regulation comprises a full-scale crash test in which the stationary test vehicle is struck at right angles by a mobile deformable barrier travelling at 50 km/h. This test scenario is the basis for most of ISO’s previous work on side impact testing for child restraint systems. NOTE Countries and regions that do not recognise UN regulations can evaluate vehicles under different conditions and can apply input parameters that reflect the vehicle crash tests in their own regulatory jurisdictions.

  • Technical specification
    24 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off
ISO
ISO 13216-4:2020(Main)
Road vehicles — Anchorages in vehicles and attachments to anchorages for child restraint systems — Part 4: Lower tether anchorages

This document establishes the positioning zones, dimensions and general and static strength requirements for lower tether anchorages. Lower tether anchorages can be used together with seat bight anchorages according to ISO 13216-1, or with other methods for anchoring child restraint systems (CRS) in road vehicles. This document is applicable to all seating positions, intended by the vehicle manufacturer, for use with rearward-facing CRSs. These seating positions can include outer and mid positions in rear seats (second and third row), as well as the front passenger seat. This document also specifies requirements and strength testing of retrofit lower tether anchorages.

  • Standard
    17 pages
    English language
    sale 15% off
  • Draft
    17 pages
    English language
    sale 15% off
ISO
ISO 22078:2020(Main)
Intelligent transport systems — Bicyclist detection and collision mitigation systems (BDCMS) — Performance requirements and test procedures

This document specifies the concept of operation, minimum functionality, system requirements, system interfaces, and test procedures for bicyclist detection and collision mitigation systems (BDCMS). It also defines the system test criteria necessary to verify that a given implementation meets the requirements of this document. Implementation choices are left to system designers, wherever possible. BDCMS are fundamentally intended to provide emergency braking (EB) of equipped vehicles in order to mitigate collision severity between the subject vehicle (SV) and a bicyclist. BDCMS detect bicyclists forward of the SV, determine if the detected bicyclists are in a hazardous situation with respect to the SV, and initiate EB if a hazardous situation exists and a collision is imminent. Systems that include other countermeasures such as evasive steering are outside the scope of this document. This document defines two types of BDCMS (based on operation in different ambient illuminance) and two classes of BDCMS (based on operation on different vehicle size classes), as depicted in Table 1. This document does not apply to motorcycles. The operational design domain is public roads. BDCMS is not intended for off-road use. Responsibility for the safe operation of the vehicle remains with the driver. Licensable motor vehicles intended for use on public roads (i.e. motorcycles, cars, light trucks, buses, motor coaches), and other heavy vehicles as hazards are outside the scope of this document and are covered under ISO 22839. Pedestrians are outside the scope of this document and are covered under ISO 19237. Annex A contains informative information relative to BDCMS.

  • Standard
    18 pages
    English language
    sale 15% off
ISO
ISO 12353-1:2020(Main)
Road vehicles — Traffic accident analysis — Part 1: Vocabulary

This document establishes a vocabulary relating to the investigation and analysis of road traffic accidents and to the application of accident data. It also lists other, commonly used terms in the domain. NOTE Additional terms and definitions, related to configuration aspects of road vehicle collisions, can be found in ISO 6813.

  • Standard
    6 pages
    English language
    sale 15% off
ISO
ISO 13216-3:2018(Main)
Road vehicles — Anchorages in vehicles and attachments to anchorages for child restraint systems — Part 3: Classification of child restraint system and space in vehicle

This document classifies the spatial requirements in a vehicle to enable a child restraint system (CRS) to be conveniently mounted. It also specifies the dimensions of child restraint systems, to ensure that they will fit in vehicles. A classification scheme is provided to determine dimensional compatibility between child restraint systems and the available space at specified seating positions in vehicles. The dimensional requirements refer to forward-facing child restraint systems of three size categories, rearward-facing child restraint systems of three size categories, and lateral-facing child restraint systems of two categories. This edition of the document also incorporates size classification of booster systems.

  • Standard
    25 pages
    English language
    sale 15% off