Diagnostic Extract Template

AUTOSAR CP R20-11

Document Title Diagnostic Extract Template

Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 673

Document Status published

Part of AUTOSAR Standard Classic Platform
Part of Standard Release R20-11

Document Change History

Date Release Changed by Description
AUTOSAR • Handling of Security Events
2020-11-30 R20-11 Release • minor corrections / clarifications /
Management editorial changes
• Increase support for variant handling
• Improved Dem upstream mapping
AUTOSAR • Support for custom service instances
2019-11-28 R19-11 Release • minor corrections / clarifications /
Management editorial changes; For details please
refer to the ChangeDocumentation
• Changed Document Status from
Final to published
AUTOSAR • minor corrections / clarifications /
2018-10-31 4.4.0 Release editorial changes; For details please
Management refer to the ChangeDocumentation
AUTOSAR • minor corrections / clarifications /
2017-12-08 4.3.1 Release editorial changes; For details please
Management refer to the ChangeDocumentation
• Support for OBD
• Support for J1939
AUTOSAR • Support for Fim configuration
2016-11-30 4.3.0 Release • Support for environmental conditions
Management • Minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation

1 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

AUTOSAR • Minor corrections / clarifications /

2015-07-31 4.2.2 Release editorial changes; For details please
Management refer to the ChangeDocumentation
AUTOSAR
2014-10-31 4.2.1 Release • Initial Release
Management

2 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Disclaimer

This work (specification and/or software implementation) and the material contained in
it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the
companies that have contributed to it shall not be liable for any use of the work.
The material contained in this work is protected by copyright and other types of intel-
lectual property rights. The commercial exploitation of the material contained in this
work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the work
may be utilized or reproduced, in any form or by any means, without permission in
writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.

3 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Table of Contents
1 Introduction 11
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1.1 OEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.1.2 Application Developer . . . . . . . . . . . . . . . . . . . . . . 13
1.1.3 ECU-Supplier . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.4 Exchanging of Files . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.5 Relationship to software-component Service Needs . . . . . 15
1.1.6 Recommendation and Hints . . . . . . . . . . . . . . . . . . 16
1.1.7 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3 Binding Times of Constraints . . . . . . . . . . . . . . . . . . . . . . . 18
1.4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.6 Requirements Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2 Use Cases 27
2.1 Use cases for diagnostic data exchange . . . . . . . . . . . . . . . . . 27
2.2 Configuration of DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3 Configuration of DEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4 Configuration of the Fim . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.1 Model Function Inhibition . . . . . . . . . . . . . . . . . . . . 30
2.4.2 Model Fim configuration before Dem exists . . . . . . . . . . 31
2.5 Configuration of J1939 Diagnostics . . . . . . . . . . . . . . . . . . . . 32
2.5.1 Modeling of J1939 Diagnostic Aspects independent of the
Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5.2 J1939 Diagnostic Content modeled in the Diagnostic Extract 32
3 Conceptual Background 33
3.1 Definition of relevant Diagnostic Elements . . . . . . . . . . . . . . . . 33
3.2 Abstraction from EcuC Level . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3 Independence of Definition . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.1 Use of atpSplitable enabling separation of elements
over several physical files . . . . . . . . . . . . . . . . . . . . 34
3.3.2 Use of self-contained mapping elements . . . . . . . . . . . 34
4 Common Meta Model Elements 35
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2 Data Identifier vs. Routine vs. Data Element . . . . . . . . . . . . . . . 35
4.2.1 Usage of SwDataDefProps . . . . . . . . . . . . . . . . . . . 42
4.2.2 Definition of Arrays . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.3 Definition of textual Strings . . . . . . . . . . . . . . . . . . . 48
4.3 Textual Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.4 Diagnostic Contribution . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.5 Diagnostic Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4.6 Diagnostic Common Properties . . . . . . . . . . . . . . . . . . . . . . 61

5 Diagnostic Services 67
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.2 Service Instance vs. Service Class . . . . . . . . . . . . . . . . . . . . 67
5.3 Access Permission, Session, Security Level . . . . . . . . . . . . . . . 70
5.3.1 Introduction to Access Permission . . . . . . . . . . . . . . . 70
5.4 Environmental Conditions for the Execution of Diagnostic Services . . 75
5.4.1 Environmental Condition Formula . . . . . . . . . . . . . . . 77
5.4.2 Atomic Conditions . . . . . . . . . . . . . . . . . . . . . . . . 79
5.4.2.1 Data Condition . . . . . . . . . . . . . . . . . . . . . 80
5.4.2.2 Mode Condition . . . . . . . . . . . . . . . . . . . . . 81
5.5 Diagnostic Services supported by AUTOSAR . . . . . . . . . . . . . . 84
5.5.1 DataByIdentifier . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.5.2 IOControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.5.3 EcuReset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.5.4 ClearDiagnosticInformation . . . . . . . . . . . . . . . . . . . 97
5.5.5 Memory Services . . . . . . . . . . . . . . . . . . . . . . . . 99
5.5.6 CommunicationControl . . . . . . . . . . . . . . . . . . . . . 108
5.5.7 DynamicallyDefineDataIdentifier . . . . . . . . . . . . . . . . 113
5.5.8 ReadDataByPeriodicIdentifier . . . . . . . . . . . . . . . . . . 116
5.5.9 ControlDTCSetting . . . . . . . . . . . . . . . . . . . . . . . . 118
5.5.10 ResponseOnEvent . . . . . . . . . . . . . . . . . . . . . . . . 120
5.5.11 ReadDTCInformation . . . . . . . . . . . . . . . . . . . . . . 124
5.5.12 RoutineControl . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.5.13 SecurityAccess . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.5.14 SessionControl . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.5.15 RequestFileTransfer . . . . . . . . . . . . . . . . . . . . . . . 138
5.6 OBD Diagnostic Services supported by AUTOSAR . . . . . . . . . . . 139
5.6.1 OBD Mode 0x01 (RequestCurrentPowertrainDiagnosticData) 142
5.6.2 OBD Mode 0x02 (RequestPowertrainFreezeFrameData) . . 143
5.6.3 OBD Mode 0x03 / 0x07 (RequestEmissionRelatedDiagnos-
ticTroubleCodes) . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.6.4 OBD Mode 0x04 (ClearResetEmissionRelatedDiagnosticIn-
formation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
5.6.5 OBD Mode 0x06 (RequestOnBoardMonitoringTestResults) . 147
5.6.6 OBD Mode 0x08 (RequestControlOfOnBoardDevice) . . . . 149
5.6.7 OBD Mode 0x09 (RequestVehicleInformation) . . . . . . . . 151
5.6.8 OBD Mode 0x0A (RequestEmissionRelatedDiagnosticTrou-
bleCodesPermanentStatus) . . . . . . . . . . . . . . . . . . . 153
5.7 UDS Diagnostic Services for supporting WWH-OBD . . . . . . . . . . 155
5.8 Diagnostic Service Mapping . . . . . . . . . . . . . . . . . . . . . . . . 155
5.8.1 Diagnostic Service Data Mapping . . . . . . . . . . . . . . . 159
5.8.2 Diagnostic Service Software Mapping . . . . . . . . . . . . . 163
5.8.3 Security Event Reporting Mode Mapping . . . . . . . . . . . 167
6 Diagnostic Event Handling 169

5 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

6.2 DiagnosticEvent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.2.2 Textual description . . . . . . . . . . . . . . . . . . . . . . . . 174
6.2.3 Associated Event Identification . . . . . . . . . . . . . . . . . 177
6.3 DiagnosticTroubleCode . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.4 DiagnosticExtendedDataRecord . . . . . . . . . . . . . . . . . . . . . . 193
6.5 DiagnosticFreezeFrame . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6.6 DiagnosticCondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6.7 Diagnostic Debouncing . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.8 DiagnosticConditionGroup . . . . . . . . . . . . . . . . . . . . . . . . . 204
6.9 DiagnosticMapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.9.1 DiagnosticEvent to DtcUds Mapping . . . . . . . . . . . . . . 207
6.9.2 DiagnosticEvent to DiagnosticOperationCycle Mapping . . . 208
6.9.3 DiagnosticEvent to DebounceAlgorithm Mapping . . . . . . . 209
6.9.4 DiagnosticEvent to EnableConditionGroup Mapping . . . . . 210
6.9.5 DiagnosticEvent to StorageConditionGroup Mapping . . . . 211
6.9.6 DiagnosticEvent to Port Mapping . . . . . . . . . . . . . . . . 213
6.9.7 DiagnosticOperationCycle to Port Mapping . . . . . . . . . . 214
6.9.8 DiagnosticEnableCondition to Port Mapping . . . . . . . . . 216
6.9.9 DiagnosticStorageCondition to Port Mapping . . . . . . . . . 217
6.9.10 Provided Data Mapping . . . . . . . . . . . . . . . . . . . . . 218
6.9.11 Master to Slave Event Mapping . . . . . . . . . . . . . . . . . 221
6.9.12 Diagnostic Event to Security Event Mapping . . . . . . . . . 222
6.10 DiagnosticOperationCycle . . . . . . . . . . . . . . . . . . . . . . . . . 225
6.11 DiagnosticAging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
6.12 DiagnosticIndicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
6.13 DiagnosticTestResult . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
6.14 OBD-related aspects of Dem Configuration . . . . . . . . . . . . . . . 231
6.14.1 Dem Configuration for OBD-II . . . . . . . . . . . . . . . . . 236
6.14.2 Dem Configuration for WWH-OBD . . . . . . . . . . . . . . . 237
7 Functional Inhibition 239
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.2 Alias Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.3 Function Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7.4 Mapping between Inhibition Source and Diagnostic Event . . . . . . . 241
7.5 Alias Event Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
7.6 Mapping of Function Identifiers to the corresponding Monitors . . . . . 247
8 Diagnostics on J1939 250
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
8.2 Suspect Parameter Number . . . . . . . . . . . . . . . . . . . . . . . . 250
8.3 J1939Dcm-related Modeling . . . . . . . . . . . . . . . . . . . . . . . . 251
8.4 Dem-related Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
8.5 Mapping between Software-Components and Controller Applications . 255
8.6 Mapping between DiagnosticEvent and J1939 DTC . . . . . . . . . . . 256

6 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

A Mentioned Class Tables 258

B History of Constraints and Specification Items 287

B.1 Constraint History of this Document according to AUTOSAR R4.2.1 . . 287
B.1.1 Added Specification Items in R4.2.1 . . . . . . . . . . . . . . 287
B.1.2 Added Constraints in R4.2.1 . . . . . . . . . . . . . . . . . . 291
B.2 Constraint History of this Document according to AUTOSAR R4.2.2 . . 293
B.2.1 Added Traceables in R4.2.2 . . . . . . . . . . . . . . . . . . . 293
B.2.2 Changed Traceables in R4.2.2 . . . . . . . . . . . . . . . . . 293
B.2.3 Deleted Traceables in R4.2.2 . . . . . . . . . . . . . . . . . . 293
B.2.4 Added Constraints in R4.2.2 . . . . . . . . . . . . . . . . . . 293
B.2.5 Changed Constraints in R4.2.2 . . . . . . . . . . . . . . . . . 293
B.2.6 Deleted Constraints in R4.2.2 . . . . . . . . . . . . . . . . . . 293
B.3 Constraint History of this Document according to AUTOSAR R4.3.0 . . 294
B.3.1 Added Traceables in R4.3.0 . . . . . . . . . . . . . . . . . . . 294
B.3.2 Changed Traceables in R4.3.0 . . . . . . . . . . . . . . . . . 295
B.3.3 Deleted Traceables in R4.3.0 . . . . . . . . . . . . . . . . . . 296
B.3.4 Added Constraints in R4.3.0 . . . . . . . . . . . . . . . . . . 296
B.3.5 Changed Constraints in R4.3.0 . . . . . . . . . . . . . . . . . 297
B.3.6 Deleted Constraints in R4.3.0 . . . . . . . . . . . . . . . . . . 297
B.4 Constraint History of this Document according to AUTOSAR R4.3.1 . . 297
B.4.1 Added Traceables in 4.3.1 . . . . . . . . . . . . . . . . . . . . 297
B.4.2 Changed Traceables in 4.3.1 . . . . . . . . . . . . . . . . . . 297
B.4.3 Deleted Traceables in 4.3.1 . . . . . . . . . . . . . . . . . . . 298
B.4.4 Added Constraints in 4.3.1 . . . . . . . . . . . . . . . . . . . 298
B.4.5 Changed Constraints in 4.3.1 . . . . . . . . . . . . . . . . . . 298
B.4.6 Deleted Constraints in 4.3.1 . . . . . . . . . . . . . . . . . . 298
B.5 Constraint History of this Document according to AUTOSAR R4.4.0 . . 299
B.5.1 Added Traceables in 4.4.0 . . . . . . . . . . . . . . . . . . . . 299
B.5.2 Changed Traceables in 4.4.0 . . . . . . . . . . . . . . . . . . 299
B.5.3 Deleted Traceables in 4.4.0 . . . . . . . . . . . . . . . . . . . 299
B.5.4 Added Constraints in 4.4.0 . . . . . . . . . . . . . . . . . . . 299
B.5.5 Changed Constraints in 4.4.0 . . . . . . . . . . . . . . . . . . 300
B.5.6 Deleted Constraints in 4.4.0 . . . . . . . . . . . . . . . . . . 300
B.6 Constraint History of this Document according to AUTOSAR R19-11 . 301
B.6.1 Added Traceables in 19-11 . . . . . . . . . . . . . . . . . . . 301
B.6.2 Changed Traceables in 19-11 . . . . . . . . . . . . . . . . . . 301
B.6.3 Deleted Traceables in 19-11 . . . . . . . . . . . . . . . . . . 301
B.6.4 Added Constraints in 19-11 . . . . . . . . . . . . . . . . . . . 301
B.6.5 Changed Constraints in 19-11 . . . . . . . . . . . . . . . . . 302
B.6.6 Deleted Constraints in 19-11 . . . . . . . . . . . . . . . . . . 302
B.7 Constraint History of this Document according to AUTOSAR R20-11 . 302
B.7.1 Added Traceables in R20-11 . . . . . . . . . . . . . . . . . . 302
B.7.2 Changed Traceables in R20-11 . . . . . . . . . . . . . . . . . 302
B.7.3 Deleted Traceables in R20-11 . . . . . . . . . . . . . . . . . 303
B.7.4 Added Constraints in R20-11 . . . . . . . . . . . . . . . . . . 303

7 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.7.5 Changed Constraints in R20-11 . . . . . . . . . . . . . . . . 306

B.7.6 Deleted Constraints in R20-11 . . . . . . . . . . . . . . . . . 306
C Glossary 306

D Modeling of InstanceRef 310

D.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
D.2 Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
E Upstream Mapping 316
E.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
E.2 Dcm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
E.3 Dem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
E.4 Fim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
E.5 J1939 Dcm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
E.6 IdsM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
F Splitable Elements in the Scope of this Document 567

G Variation Points in the Scope of this Document 568

8 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

References
[1] Specification of RTE Software
AUTOSAR_SWS_RTE
[2] Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture
[3] Specification of ECU Configuration
AUTOSAR_TPS_ECUConfiguration
[4] ASAM MCD 2D ODX
http://www.asam.net
ASAM MCD-2D ODX v2.2.0.pdf
[5] XML Schema Production Rules
AUTOSAR_TPS_XMLSchemaProductionRules
[6] System Template
AUTOSAR_TPS_SystemTemplate
[7] Specification of ECU Configuration Parameters (XML)
AUTOSAR_MOD_ECUConfigurationParameters
[8] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate
[9] Basic Software Module Description Template
AUTOSAR_TPS_BSWModuleDescriptionTemplate
[10] Specification of Diagnostic Communication Manager
AUTOSAR_SWS_DiagnosticCommunicationManager
[11] Specification of Diagnostic Event Manager
AUTOSAR_SWS_DiagnosticEventManager
[12] Standardization Template
AUTOSAR_TPS_StandardizationTemplate
[13] Requirements on Diagnostic Extract Template
AUTOSAR_RS_DiagnosticExtractTemplate
[14] Specification of Function Inhibition Manager
AUTOSAR_SWS_FunctionInhibitionManager
[15] SAE J1939 Top Level Document
[16] Unified diagnostic services (UDS) – Part 1: Specification and requirements (Re-
lease 2006-12)
http://www.iso.org
[17] Road vehicles – End-of-life activation of on-board pyrotechnic devices – Part 2:
Communication requirements

9 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

http://www.iso.org
[18] Road vehicles – Communication between vehicle and external equipment for
emission-related diagnostic – Part 5: Emission-related diagnostic services.
http://www.iso.org
[19] Road vehicles – Implementation of World-Wide Harmonized On-Board Diagnos-
tics (WWH-OBD) communication requirements – Part 3: Common message dic-
tionary
http://www.iso.org
[20] Security Extract Template
AUTOSAR_TPS_SecurityExtractTemplate
[21] Specification of Intrusion Detection System Manager
AUTOSAR_SWS_IntrusionDetectionSystemManager
[22] SAE J1939-73 Application Layer – Diagnostics
[23] Software Process Engineering Meta-Model Specification
http://www.omg.org/spec/SPEM/2.0/
[24] Generic Structure Template
AUTOSAR_TPS_GenericStructureTemplate

10 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

1 Introduction

1.1 Overview
The distributed nature of an AUTOSAR ECU development requires an optimized cap-
turing of information. In particular, diagnostic information (i.e. DEM and DCM configu-
ration) shall be captured only once by the person with the best knowledge and therefore
being able to take responsibility better than one centralized individual.
In the configuration approach before the advent of the DiagnosticExtract, the
Basic Software Modules DCM and DEM are entirely configured centrally. During in-
tegration, all SW-Cs above the RTE [1] (Application Software) introduce ports to be
connected to the BSW modules [2]. Additionally, SW-Cs express needs which shall be
fulfilled by the BSW.
The market shows a high demand for transferring diagnostic demands of the OEM-
specific configuration process to their tier-1 suppliers.
In the past, due to the absence of integral options, many file formats like ODX or
EcuC [3] are often used. But neither ODX nor EcuC is well suited to transfer this
information.
For example, ODX [4] lacks in fault memory details and EcuC (which was never de-
signed for becoming the vehicle for data exchange between different organizations)
has a very generic nature that renders the enforcement of a strict model formalization
very difficult.
On top of that, the integration of EcuC definitions into an existing configuration (espe-
cially the PDUs) cannot be fully automated.
Therefore, the obvious solution approach has been to define a new standardized
AUTOSAR exchange format on diagnostic functionality that can be used similar to a
System Description, formalized as an ARXML [5] file.
In this spirit, the configuration of diagnostic functionality becomes similar to the config-
uration of the communication part within the System Description [6].

11 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
concept relevant artifacts
AUTOSAR CP R20-11
concept relevant generated artifacts
Overview concept relevant process activity

Appl. Dev. OEM ECU-Supplier

Use Case 1: OEM as collector for diagnostic requirements Supplier
Diagnostic
OEM Extract
Collecting Diagnostics (.arxml)
SW-Cs and Definitions
SW-Cs merging
(.doc, .xls, …)
Diagnostic by
Diagnostic
Contribution OEM
OEM OEM
Contribution
(.arxml) Diagnostic
(.arxml) specific Diagnostic
System
process Extract
Extract

Mapping to EcuC (AR 4.x)

(.arxml)

EcuC Parameter Values

(.arxml)

ECU-Implementation
Collecting
and merging
Use Case 2: Supplier as collector for diagnostic requirements by
Supplier
OEM
SW-Cs specific
Diagnostic
SW-Cs Extract process
Diagnostic (partially filled)
Diagnostic
Contribution (.arxml)
Contribution
(.arxml)
(.arxml)

Please note:
Figure 1.1: Scope of this document in the ECU Development work-flow
The feedback paths (e.g. from OEM to Application Developer) are not depicted here because they are usually realized company or project specific.

- AUTOSAR Confidential -

Figure
1 1.12013-1107
shows the configuration Decentralized
process of diagnostics for two generalized use
Configuration

cases. This process involves three parties:

• OEM or diagnostic requester
• Application Developer or Application Developer
• ECU-Supplier or integrator
The specific role of these contributors to the diagnostic extract is in detail explained in
the following sub-chapters.

1.1.1 OEM

The OEM or requester of diagnostic data uses the DiagnosticExtract to define the
diagnostic interfaces of one or multiple ECUs. It may also define some InternalBe-
haviors as requirements for the ECU-Supplier or Application Developer
• Defines the values of the DTCs
• Defines the UDS services and sub-services supported by the ECUs
• Defines the required events needed by a specific composition implemented by an
Application Developer
NOTE: This list represents an example; this document does not define a specific own-
ership of each element.

12 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

In the first use case, the DiagnosticExtract is used to exchange information which
is transformed into the EcuC configuration (M2 to M1 mapping, see also [3] and [7]).
Second, the OEM uses the DiagnosticExtract to document requirements to be
implemented by a supplier. These requirements are expressed in textual language
and can not be mapped directly to any EcuC configuration parameters (no M2 to M1
mapping possible).

1.1.2 Application Developer

The Application Developers implement their software-components with the corre-

sponding software-component description. The role “Application Developer” can
be assumed by both an OEM and a supplier. In other words, both OEM and supplier
may contribute application software to a given ECU.
With the introduction of this concept, the Application Developer has the possibility to
provide diagnostic information relevant to the software-components as part of the
DiagnosticExtract.
The Application Developer may also receive some input as requirement from the OEM
within the DiagnosticExtract in textual form as for example:
• Definition of the content of a specific ReadDataByIdentifier implemented by
this software-component
• Definition of the events needed for this software-component
NOTE: Only as example, this document does not define a specific ownership of each
element.
In the first use case, the Application Developer defines the parameters of a specific
ReadDataByIdentifier, i.e. the content of the diagnostic request but not the DID
itself. The DID of this command will usually be defined by the OEM.
Secondly, the software-component events including information like Debouncing and
OperationCycle may be defined by the Application Developer. The Application
Developermay also define events and diagnostic jobs which are not needed by a spe-
cific OEM but for another one.
Suppliers may use the same software for multiple OEMs and need to reuse it. This im-
plies that some DiagnosticExtract information coming from a software-component
may be ignored during the integration if not needed for a specific project.

1.1.3 ECU-Supplier

The ECU-Supplier or integrator receives one or several DiagnosticExtract files

from the OEM and from multiple Application Developers. The main goal of the In-

13 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

tegrator is to integrate all delivered DiagnosticExtract and to generate the EcuC

configuration from it.
Since this concept does not define a specific ownership for each element like DIDs,
parameters of a UDS service, Events, Sessions, etc. the integrator has to ensure that
the complete information is still valid after merging it.
• Mapping of DTCs to Events
• Merge of Events
• Mapping of services
Some DTCs may already be mapped to events - especially in cases where both come
from the same party. But if the DTCs are defined by the OEMand the SW implemented
by other supplier acting as an Application Developer the integrator has to ensure that
both are mapped together.
In some cases, an Event may be defined multiple times. An OEM defines the Events
which shall be implemented by an Application Developer. A Supplier implements a
software-component which will be used in multiple projects and which also detects this
type of error and also defines this same event.
Both events may have different naming but the same meaning. The integrator has to
detect this redundancy during the integration and merge them together.
In another case, the OEM requires a specific ReadDataByIdentifier and an Ap-
plication Developer implements it. If the implementation is performed for one specific
project only, the Application Developer may map the DID from the OEM to the already
defined job in their software-component.
In other cases in which the Application Developer implements a generic diagnostic
job, it will be a task of the ECU-Supplier to merge this information and to map the jobs
to the corresponding DID.

1.1.4 Exchanging of Files

During an ECU development project, the three main roles (OEM, Application Devel-
oper, ECU Integrator) exchange DiagnosticExtract files. The timing and fre-
quency of exchanges and the content in each of these exchanged files is highly de-
pendent on the individual project setup and situation.
Therefore, the DiagnosticExtract format has been designed to allow for gradual
enrichment of definitions contributed at largely arbitrary points in time by the different
roles in order to meet the needs of “Decentralized Configuration”.
For any exchange path between any two roles, the same file format based on the
DiagnosticExtract template is used. It is then up to a company specific process
and tooling to merge the collected DiagnosticExtract files while resolving conflicts
(contradictions, redundancies etc.).

14 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

As final result, a consistent and complete DiagnosticExtract file is available which

is input to derivation of the configuration for the diagnostic modules of the Basic Soft-
ware.

Figure 1.2: Exchange of diagnostic configuration between OEM, Tier-1, and Tier-2

Even after the DiagnosticExtract has been fully integrated and is ready to go for
deriving the configuration of the diagnostic stack on EcuC level it is still foreseen to
feed it back to e.g. an OEM.
In this case the OEM has the ability to review the configuration of the diagnostic stack
on the level of the diagnostic extract.
At some point, this information may also be taken to (directly or via indirection of other
formats) create a configuration of a diagnostic client.

1.1.5 Relationship to software-component Service Needs

Before the introduction of the Diagnostic Extract, Service Needs were used to describe
diagnostic requirements on software-component level. These configuration require-
ments are referenced to the related BSW module DCM or DEM in order to provide the
corresponding configuration on BSW level.
The usage of Service Needs is only possible on Atomic software-component level
whereas the assignment of diagnostic demands must be possible on Composition level.
The software-component Service Needs within the software-component
Description are still to be used along with the DiagnosticExtract in order to
annotate the software-component ports which are relevant for further mapping and
handling as defined by the DiagnosticExtract.
From software-component Developer’s perspective, the DiagnosticExtract is
therefore used partially as substitution and partially as extension of the software-

15 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

component Service Needs. The reasoning for “substitution” is the avoidance of

redundant diagnostic definitions.
Since some diagnostic properties potentially definable by software-component Devel-
opers are not covered in software-component Service Needs, the Diagnos-
ticExtract can also be viewed as “extension” to the original purpose of software-
component Service Needs.

1.1.6 Recommendation and Hints

Multiple parties may have different understanding of which parts shall be provided by
each one. There is no defined rule to indicate who is responsible for each part. At the
end, it is the ECU-Supplier in his role as integrator who has to ensure that all mappings
are done and that the ECU runs as expected by the OEM.
In case the OEM does not have his own diagnostic requirements, the ECU-Supplier
has to provide the complete DiagnosticExtract. In this case, the OEM may only
receive the DiagnosticExtract as part of the delivery. The process itself how the
parties work with this format is not defined within this specification.
Figure 1.1 shows a recommended way how to handle the DiagnosticExtract be-
tween the different parties. In use case 1, some software-components are imple-
mented by the OEM (or by a Supplier of the OEM) and the first merging of Diag-
nosticExtract data occurs at the OEM.
In use case 2, the OEM provides the diagnostic requirements via DiagnosticEx-
tract and multiple Application Developerprovide information related to their imple-
mentation, the merging is performed completely by the ECU-Supplier.
Also, a combination of use cases 1 and 2 is allowed. Also, the ECU-Supplier may
implement some part of the SW inclusive their corresponding DiagnosticExtract.

1.1.7 Limitations

This first release of the DiagnosticExtract template focuses on defining diagnostic

requirements a single ECU only. That means that currently, distributed diagnostic func-
tionality for a system or partial system consisting of multiple ECUs cannot be defined
using the DiagnosticExtract template.
In future releases, the DiagnosticExtract template is expected to be extended to
also cover configuration of distributed diagnostic functionality. Similar to the descrip-
tion of communication dependencies in the System Description, it shall be possible to
describe diagnostic demands on system level to derive the diagnostic demands for a
specific ECU from this description.
In general, the DiagnosticExtract does not support process-related parts to doc-
ument the maturity of diagnostic configuration data. This means, that a data object

16 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

cannot be marked as “draft” or “released”. This issue needs to be solved by AUTOSAR

within a general concept in a future release. Therefore, it does not make sense to
introduce a solution for diagnostics only.

1.2 Scope
This document describes the formal description of contributions to the diagnostic con-
figuration.
On the level of meta-modeling, the content described in this document conceptually re-
lates to the definition of SwcServiceDependency or BswServiceDependency, as
defined by the Software Component Template [8] or Basic Software Mod-
uleDescription Template [9].
Further relations exist to the specification of communication in AUTOSAR systems as
described by the System Template [6].
Further relations exist to the specification of the Diagnostic Communication
Manager [10] as well as to the Diagnostic Event Manager [11].
The relation of the DiagnosticExtract to the rest of the AUTOSAR meta-model is
sketched in Figure 1.3.

17 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

AutosarTopLevelStructure      CommonStructure


   
    
    
    
 

SWComponentTemplate EcuResourceTemplate

AdaptivePlatform

SystemTemplate

DiagnosticExtract

ECUCDescriptionTemplate

ECUCParameterDefTemplate

BswModuleTemplate

AbstractPlatform StandardizationTemplate GenericStructure FeatureModelTemplate

    
   
   
  

Figure 1.3: The relation of the DiagnosticExtract to the rest of the AUTOSAR meta-
model

1.3 Binding Times of Constraints

Constraints in this document have different actual binding times depending on the plat-
form that utilizes a DiagnosticExtract. On the AUTOSAR classic platform, the
binding time is defined as the time when the Ecu configuration of the diagnostic
stack is created.
For the AUTOSAR adaptive platform, the binding time is identified as the time when
the creation of manifest contentis completed.
It would be very cumbersome to list the two binding times for the different platforms in
each constraint separately. Therefore, whenever a constraint is equally applicable to
both the AUTOSAR adaptive platform and the AUTOSAR classic platform the generic
phrase “at the time when the DEXT is complete” is used.

18 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

1.4 Abbreviations
The following table contains a list of abbreviations used in the scope of this document
along with the spelled-out meaning of each of the abbreviations.

Abbreviation meaning
API Application Programming Interface
BSW Basic Software
BswM Basic Software Manager
CAN Controller Area Network
CSE Codes for Scaling Units
DEM Diagnostics Communication Manager
DCY Driving Cycle
DEM Diagnostics Event Manager
DID Diagnostic Identifier
DTC Diagnostic Trouble Code
DTR Diagnostic Test Result
DoIP Diagnostics over IP
ECU Electrical Control Unit
ECUC ECU Configuration
FID Function Identifier
FIM Function Inhibition Manager
GID Group Identifier
ID Identifier
IO Input/Output
IP Internet Protocol
IUMPR In-Use Monitor Performance Ratio
ISO International Organization for Standardization
LIN Local Interconnect Network
NRC Negative Response Code
OBD On-Board Diagnostic
ODX Open Diagnostic Data Exchange
OEM Original Equipment Manufacturer
PDU Protocol Data Unit
PID Parameter Identifier
PTO Power Take Off
RA Routing Activation
RAM Random Access Memory
RID Routine Identifier
ROE Response on Event
ROM Read-Only Memory
RTE Run-TIme Environment
RS Requirements Specification
RX Receive
SPN Suspect Parameter Number
SW Software
5

19 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Abbreviation meaning
SWC Software Component
SWCD Software Component Description
TID Test Identifier
TPS Template Specification
TX Transmit
SWS Software Specification
UDS Unified Diagnostic Services
UML Unified Modeling Language
VFB Virtual Functional Bus
VIN Vehicle Identification Number
WWH-OBD World-Wide Harmonized On-Board Diagnostics
XML Extensible Markup Language
XSD XML Schema Definition

Table 1.1: Abbreviations used in the scope of this Document

1.5 Document Conventions

Technical terms are typeset in mono spaced font, e.g. PortPrototype. As a general
rule, plural forms of technical terms are created by adding "s" to the singular form, e.g.
PortPrototypes. By this means the document resembles terminology used in the
AUTOSAR XML Schema.
This document contains constraints in textual form that are distinguished from the rest
of the text by a unique numerical constraint ID, a headline, and the actual constraint
text starting after the d character and terminated by the c character.
The purpose of these constraints is to literally constrain the interpretation of the
AUTOSAR meta-model such that it is possible to detect violations of the standardized
behavior implemented in an instance of the meta-model (i.e. on M1 level).
Makers of AUTOSAR tools are encouraged to add the numerical ID of a constraint that
corresponds to an M1 modeling issue as part of the diagnostic message issued by the
tool.
The attributes of the classes introduced in this document are listed in form of class
tables. They have the form shown in the example of the top-level element AUTOSAR:
Please note that constraints are not supposed to be enforceable at any given time in an
AUTOSAR workflow. During the development of a model, constraints may legitimately
be violated because an incomplete model will obviously show inconsistencies.
However, at specific points in the workflow, constraints shall be enforced as a safeguard
against misconfiguration.
The points in the workflow where constraints shall be enforced, sometimes also known
as the "binding time" of the constraint, are different for each model category, e.g. on the

20 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

classic platform, the constraints defined for software-components are typically enforced
prior to the generation of the RTE while the constraints against the definition of an Ecu
extract shall be applied when the Ecu configuration for the Com stack is created.
For each document, possible binding times of constraints are defined and the binding
times are typically mentioned in the constraint themselves to give a proper orientation
for implementers of AUTOSAR authoring tools.
Class AUTOSAR
Package M2::AUTOSARTemplates::AutosarTopLevelStructure
Note Root element of an AUTOSAR description, also the root element in corresponding XML documents.
Tags:xml.globalElement=true
Base ARObject
Attribute Type Mult. Kind Note
adminData AdminData 0..1 aggr This represents the administrative data of an Autosar file.
Tags:xml.sequenceOffset=10
arPackage ARPackage * aggr This is the top level package in an AUTOSAR model.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=arPackage.shortName, arPackage.variation
Point.shortLabel
vh.latestBindingTime=blueprintDerivationTime
xml.sequenceOffset=30
fileInfo FileInfoComment 0..1 aggr This represents a possibility to provide a structured
Comment comment in an AUTOSAR file.
Stereotypes: atpStructuredComment
Tags:
xml.roleElement=true
xml.sequenceOffset=-10
xml.typeElement=false
introduction DocumentationBlock 0..1 aggr This represents an introduction on the Autosar file. It is
intended for example to rpresent disclaimers and legal
notes.
Tags:xml.sequenceOffset=20

Table 1.2: AUTOSAR

The first rows in the table have the following meaning:

Class: The name of the class as defined in the UML model.
Package: The UML package the class is defined in. This is only listed to help locating
the class in the overall meta model.
Note: The comment the modeler gave for the class (class note). Stereotypes and UML
tags of the class are also denoted here.
Base Classes: If applicable, the list of direct base classes.
The headers in the table have the following meaning:
Attribute: The name of an attribute of the class. Note that AUTOSAR does not distin-
guish between class attributes and owned association ends.
Type: The type of an attribute of the class.

21 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Mul.: The assigned multiplicity of the attribute, i.e. how many instances of the given
data type are associated with the attribute.
Kind: Specifies, whether the attribute is aggregated in the class (aggr aggregation),
an UML attribute in the class (attr primitive attribute), or just referenced by it (ref
reference). Instance references are also indicated (iref instance reference) in this
field.
Note: The comment the modeler gave for the class attribute (role note). Stereotypes
and UML tags of the class are also denoted here.
Please note that the chapters that start with a letter instead of a numerical value rep-
resent the appendix of the document. The purpose of the appendix is to support the
explanation of certain aspects of the document and does not represent binding con-
ventions of the standard. The verbal forms for the expression of obligation specified
in [TPS_STDT_00053] shall be used to indicate requirements, see Standardization
Template, chapter Support for Traceability ([12]).
The representation of requirements in AUTOSAR documents follows the table specified
in [TPS_STDT_00078], see Standardization Template, chapter Support for Traceability
([12]).

22 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

1.6 Requirements Tracing

The following table references the requirements specified in [13] and links to the fulfill-
ment of these.
Requirement Description Satisfied by
[RS_DEXT_00001] Diagnostic data exchange [TPS_DEXT_01003] [TPS_DEXT_01004] [TPS_DEXT_01005]
[TPS_DEXT_01007] [TPS_DEXT_01008] [TPS_DEXT_01014]
[TPS_DEXT_01019] [TPS_DEXT_01020] [TPS_DEXT_01022]
[TPS_DEXT_01023] [TPS_DEXT_01024] [TPS_DEXT_01025]
[TPS_DEXT_01026] [TPS_DEXT_01027] [TPS_DEXT_01028]
[TPS_DEXT_01029] [TPS_DEXT_01038] [TPS_DEXT_01046]
[TPS_DEXT_01047] [TPS_DEXT_01055] [TPS_DEXT_01056]
[TPS_DEXT_01057] [TPS_DEXT_01060] [TPS_DEXT_01066]
[TPS_DEXT_01069] [TPS_DEXT_01075]
[RS_DEXT_00003] SessionControl [TPS_DEXT_01039] [TPS_DEXT_01045] [TPS_DEXT_01081]
[TPS_DEXT_01082]
[RS_DEXT_00004] ECUReset [TPS_DEXT_01019] [TPS_DEXT_01020] [TPS_DEXT_01021]
[TPS_DEXT_01045] [TPS_DEXT_01056]
[RS_DEXT_00005] ClearDiagnosticInformation [TPS_DEXT_01022] [TPS_DEXT_01045]
[RS_DEXT_00006] ReadDTCInformation [TPS_DEXT_01034] [TPS_DEXT_01045] [TPS_DEXT_01060]
[RS_DEXT_00007] ReadDataByIdentifier [TPS_DEXT_01045] [TPS_DEXT_01050] [TPS_DEXT_01054]
[TPS_DEXT_01146]
[RS_DEXT_00008] ReadMemoryByAddress [TPS_DEXT_01024] [TPS_DEXT_01045]
[RS_DEXT_00009] SecurityAccess [TPS_DEXT_01036] [TPS_DEXT_01037] [TPS_DEXT_01038]
[TPS_DEXT_01045] [TPS_DEXT_01053]
[RS_DEXT_00010] CommunicationControl [TPS_DEXT_01029] [TPS_DEXT_01030] [TPS_DEXT_01031]
[TPS_DEXT_01032] [TPS_DEXT_01045] [TPS_DEXT_01057]
[TPS_DEXT_01074]
[RS_DEXT_00011] ReadDataByPeriodicIdentifier [TPS_DEXT_01045]
[RS_DEXT_00012] DynamicallyDefineDataIdentifier [TPS_DEXT_01045]
[RS_DEXT_00013] WriteDataByIdentifier [TPS_DEXT_01045] [TPS_DEXT_01050] [TPS_DEXT_01054]
[RS_DEXT_00014] IOControl [TPS_DEXT_01015] [TPS_DEXT_01016] [TPS_DEXT_01017]
[TPS_DEXT_01018] [TPS_DEXT_01045] [TPS_DEXT_01051]
[TPS_DEXT_01150]
[RS_DEXT_00015] RoutineControl [TPS_DEXT_01035] [TPS_DEXT_01045] [TPS_DEXT_01049]
[TPS_DEXT_01077] [TPS_DEXT_01078] [TPS_DEXT_01079]
[TPS_DEXT_01080]
[RS_DEXT_00016] RequestDownload [TPS_DEXT_01027] [TPS_DEXT_01045]
[RS_DEXT_00017] RequestUpload [TPS_DEXT_01028] [TPS_DEXT_01045]
[RS_DEXT_00018] TransferData [TPS_DEXT_01026] [TPS_DEXT_01045]
[RS_DEXT_00019] RequestTransferExit [TPS_DEXT_01025] [TPS_DEXT_01045]
[RS_DEXT_00020] WriteMemoryByAddress [TPS_DEXT_01023] [TPS_DEXT_01045]
[RS_DEXT_00021] ControlDTCSetting [TPS_DEXT_01045] [TPS_DEXT_01075]
[RS_DEXT_00022] ResponseOnEvent [TPS_DEXT_01033] [TPS_DEXT_01045]
[RS_DEXT_00023] Configuration of events [TPS_DEXT_01048] [TPS_DEXT_01067] [TPS_DEXT_01068]
[TPS_DEXT_01069] [TPS_DEXT_01083] [TPS_DEXT_01084]
[TPS_DEXT_01085] [TPS_DEXT_01151] [TPS_DEXT_03002]
[TPS_DEXT_03003] [TPS_DEXT_03004] [TPS_DEXT_03005]
[TPS_DEXT_03007] [TPS_DEXT_03011] [TPS_DEXT_03015]
[TPS_DEXT_03016]
5

23 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Requirement Description Satisfied by
[RS_DEXT_00024] Configuration of DTCs [TPS_DEXT_01064] [TPS_DEXT_01065] [TPS_DEXT_01066]
[TPS_DEXT_01086] [TPS_DEXT_03000] [TPS_DEXT_03003]
[TPS_DEXT_03012] [TPS_DEXT_03013] [TPS_DEXT_03014]
[RS_DEXT_00025] Combined Events [TPS_DEXT_03003]
[RS_DEXT_00026] Enable Conditions [TPS_DEXT_03015] [TPS_DEXT_03018]
[RS_DEXT_00027] Storage Conditions [TPS_DEXT_03001] [TPS_DEXT_03006] [TPS_DEXT_03010]
[TPS_DEXT_03016] [TPS_DEXT_03019]
[RS_DEXT_00028] Enable Condition Groups [TPS_DEXT_01084] [TPS_DEXT_03010] [TPS_DEXT_03015]
[RS_DEXT_00029] Storage Condition Groups [TPS_DEXT_01084] [TPS_DEXT_03016]
[RS_DEXT_00030] Assignment of Enable Condition [TPS_DEXT_03010]
Groups
[RS_DEXT_00031] Assignment of Storage Condition [TPS_DEXT_03010]
Group
[RS_DEXT_00032] Configuration of Extended Data [TPS_DEXT_03008]
Records
[RS_DEXT_00033] Configuration of Snapshot Records [TPS_DEXT_01143] [TPS_DEXT_01144] [TPS_DEXT_03009]
[RS_DEXT_00034] Description of Data Identifiers [TPS_DEXT_01000] [TPS_DEXT_01001] [TPS_DEXT_01002]
[TPS_DEXT_01017] [TPS_DEXT_01050] [TPS_DEXT_01054]
[TPS_DEXT_01072] [TPS_DEXT_01134] [TPS_DEXT_01135]
[TPS_DEXT_01136] [TPS_DEXT_01138] [TPS_DEXT_01146]
[TPS_DEXT_01150]
[RS_DEXT_00035] Description of Dynamic Data [TPS_DEXT_01000]
Identifiers
[RS_DEXT_00036] Description of Routine Identifiers [TPS_DEXT_01088]
[RS_DEXT_00037] Description of I/O Identifiers [TPS_DEXT_01089]
[RS_DEXT_00038] Description of array data types [TPS_DEXT_01001] [TPS_DEXT_01002]
[RS_DEXT_00039] Diagnostic Service Table [TPS_DEXT_01006]
[RS_DEXT_00040] Diagnostic Sessions [TPS_DEXT_01011] [TPS_DEXT_01081] [TPS_DEXT_01082]
[TPS_DEXT_01139]
[RS_DEXT_00041] Access Permissions [TPS_DEXT_01012] [TPS_DEXT_01071]
[RS_DEXT_00042] Security Levels [TPS_DEXT_01012] [TPS_DEXT_01038] [TPS_DEXT_01053]
[RS_DEXT_00043] Description of data elements [TPS_DEXT_01142] [TPS_DEXT_03020]
[RS_DEXT_00045] Textual descriptions [TPS_DEXT_01064] [TPS_DEXT_01065] [TPS_DEXT_01066]
[TPS_DEXT_01067] [TPS_DEXT_01068] [TPS_DEXT_01069]
[TPS_DEXT_01071]
[RS_DEXT_00047] Custom Diagnostic Service [TPS_DEXT_01021] [TPS_DEXT_01030] [TPS_DEXT_01031]
[TPS_DEXT_01147]
[RS_DEXT_00049] Properties of individual diagnostic [TPS_DEXT_01013]
services
[RS_DEXT_00051] Subfunctions of Diagnostic [TPS_DEXT_01013] [TPS_DEXT_01014] [TPS_DEXT_01018]
Services [TPS_DEXT_01019] [TPS_DEXT_01020] [TPS_DEXT_01021]
[TPS_DEXT_01022] [TPS_DEXT_01023] [TPS_DEXT_01024]
[TPS_DEXT_01025] [TPS_DEXT_01026] [TPS_DEXT_01027]
[TPS_DEXT_01028] [TPS_DEXT_01029] [TPS_DEXT_01030]
[TPS_DEXT_01031] [TPS_DEXT_01034] [TPS_DEXT_01039]
[TPS_DEXT_01056] [TPS_DEXT_01057] [TPS_DEXT_01060]
[TPS_DEXT_01075] [TPS_DEXT_01078]
[RS_DEXT_00052] Mapping of diagnostic services to [TPS_DEXT_01040] [TPS_DEXT_01041] [TPS_DEXT_01042]
the PortPrototypes of Application [TPS_DEXT_01043] [TPS_DEXT_01044] [TPS_DEXT_01049]
SwComponentTypes [TPS_DEXT_01050] [TPS_DEXT_01051] [TPS_DEXT_01142]
[TPS_DEXT_03002] [TPS_DEXT_03007] [TPS_DEXT_03017]
[TPS_DEXT_03018] [TPS_DEXT_03019] [TPS_DEXT_03020]
5

24 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Requirement Description Satisfied by
[RS_DEXT_00053] Debouncing of diagnostic events [TPS_DEXT_01048] [TPS_DEXT_03004] [TPS_DEXT_03005]
[TPS_DEXT_03017]
[RS_DEXT_00054] Operation cycles [TPS_DEXT_01086] [TPS_DEXT_01087]
[RS_DEXT_00055] Aging [TPS_DEXT_03021]
[RS_DEXT_00056] Indicator [TPS_DEXT_03022]
[RS_DEXT_00057] RequestFileTransfer [TPS_DEXT_01090]
[RS_DEXT_00058] Indicate that an ECU supports [TPS_DEXT_01122]
ODB
[RS_DEXT_00059] Support for different protocols [TPS_DEXT_01124]
[RS_DEXT_00060] Function [TPS_DEXT_01096] [TPS_DEXT_01097] [TPS_DEXT_01098]
[TPS_DEXT_01099] [TPS_DEXT_01100] [TPS_DEXT_01101]
[TPS_DEXT_01121]
[RS_DEXT_00061] Relationship between functions [TPS_DEXT_01095] [TPS_DEXT_01098] [TPS_DEXT_01099]
and diagnostic events [TPS_DEXT_01100] [TPS_DEXT_01101]
[RS_DEXT_00062] Pre-configuration of the Fim when [TPS_DEXT_01095]
the Dem configuration is not yet
available
[RS_DEXT_00063] Relation between functions on Fim [TPS_DEXT_01102]
level and software-components
[RS_DEXT_00064] Definition of an SPN [TPS_DEXT_01103] [TPS_DEXT_01106]
[RS_DEXT_00065] Definition of freeze frames on [TPS_DEXT_01104] [TPS_DEXT_01105]
J1939
[RS_DEXT_00066] Mapping between a J1939 [TPS_DEXT_01108]
controller application and a
software-component
[RS_DEXT_00067] Definition of J1939 DTC [TPS_DEXT_01107] [TPS_DEXT_01145]
[RS_DEXT_00068] Definition of a Diagnostic [TPS_DEXT_01092]
Parameter Identifier
[RS_DEXT_00069] Support for OBD Mode 0x01 [TPS_DEXT_01125]
(RequestCurrentPowertrain
DiagnosticData)
[RS_DEXT_00070] Support for OBD Mode 0x02 [TPS_DEXT_01126]
(RequestPowertrainFreezeFrame
Data)
[RS_DEXT_00071] Support for OBD ModeModes 0x03 [TPS_DEXT_01127]
/ 0x07 / 0x0A (RequestEmission
RelatedDiagnosticTroubleCodes)
[RS_DEXT_00072] Support for OBD Mode 0x04 (Clear [TPS_DEXT_01128]
ResetEmissionRelatedDiagnostic
Information)
[RS_DEXT_00073] Support for OBD Mode 0x06 [TPS_DEXT_01129] [TPS_DEXT_01141]
(RequestOnBoardMonitoringTest
Results)
[RS_DEXT_00074] Support for OBD Mode 0x08 [TPS_DEXT_01130]
(RequestControlOfOnBoard
Device)
[RS_DEXT_00075] Support for OBD Mode 0x09 [TPS_DEXT_01131]
(RequestVehicleInformation)
[RS_DEXT_00076] Definition of Diagnostic Test [TPS_DEXT_01132]
Identifier
[RS_DEXT_00077] Description of the utilization of [TPS_DEXT_01133]
UDS for supporting WWH-OBD
5

25 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Requirement Description Satisfied by
[RS_DEXT_00078] Support for In Use Monitor [TPS_DEXT_01148] [TPS_DEXT_01149]
Performance Ratio
[RS_DEXT_00079] Support for environment conditions [TPS_DEXT_01113] [TPS_DEXT_01114] [TPS_DEXT_01115]
[TPS_DEXT_01116] [TPS_DEXT_01117] [TPS_DEXT_01118]
[TPS_DEXT_01119] [TPS_DEXT_01120]
[RS_DEXT_00080] Support for persisting Security [TPS_DEXT_01153]
Events
[RS_DEXT_00081] Support for updating the Reporting [TPS_DEXT_01152]
Mode of Security Events

Table 1.3: RequirementsTracing

26 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

2 Use Cases

2.1 Use cases for diagnostic data exchange

The basic usage of the DiagnosticExtract is the exchange of diagnostic data be-
tween the different parties involved in the diagnostic development process to allow the
configuration of the DCM and the DEM and to provide the description of corresponding
application interfaces to implement diagnostic services and fault handling.

2.2 Configuration of DCM

The configuration of the DCM includes the setup of diagnostic services and the assign-
ment of data objects provided by one or more software components (e.g. Composition
1, Composition 2).

Composition Composition
1 2

RTE

$22 DID DATA DATA

$31 RID DATA DATA

DCM

Figure 2.1: Assignment of DCM-related data objects

27 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

2.3 Configuration of DEM

Composition Composition
1 2

RTE

DTC 1

DTC 2

DEM

Figure 2.2: Assignment of DEM-related data objects

The configuration of the DEM includes fault memory data (DTCs and environmental
data) and the assignment of corresponding data by one or more SwComponentTypes
(e.g. Composition 1, Composition 2).
As already explained, the diagnostic development process is distributed among differ-
ent parties. On the one hand side, the OEM needs to describe the general require-
ments for a diagnostic system that have to be implemented by an ECU:
1. Depending on the diagnostic system, the OEM can provide a completely or partly-
filled DiagnosticExtract including the description of PortInterfaces:
• Integrator/SWC developer (OEM or Tier 1) is responsible for the completion
(detailing of predefined diagnostic content).
• Integrator/SWC developer (OEM or Tier 1) is responsible for the specific
configuration of diagnostic content defined by himself.
• New integration of updated Diagnostic descriptions by integrator.
2. Return of completely or partly-filled DiagnosticExtract to OEM for:
• Documentation

28 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• ECU testing
• Integration reviews
• Failure correction
Use case examples:
• Configuration of UDS service 0x22 (ReadDataByIdentifier)
• Configuration of UDS service 0x2E (WriteDataByIdentifier)
• Configuration of UDS service 0x31 (RoutineControl)
• Configuration of UDS service 0x2F (I/O-Control)
• Configuration of DEM DTCs
• Configuration of Combined Events
• Mapping of events to DTCs
• Configuration of DTC-related environmental data
• Mapping of DEM Events to their corresponding Enable Conditions and Storage
Conditions
• Configure general DCM parameters
• Description of diagnostic demands that are not relevant for code generation but
have to be exchanged between OEM and Tier1 (e.g. set and reset condition for a
DTC)
Refinement of use cases:
The OEM already provides a System Template for an ECU which describes the ECU
Supplier SW parts as a CompositionSwComponentType where only inputs and out-
puts are known.
1. The OEM creates a DiagnosticExtract which describes the diagnostic in-
terfaces of an ECU. Supported services are described (e.g. RDBI/WDBI/Routine
Control) as well as their corresponding input/output parameters and return values
(those which are optional in UDS standard).
2. SWC Developer at OEM or OEM SW Supplier develops SWC and also describes
the Diagnostic information using ServiceNeeds as diagnostic contribution.
3. The OEM Diagnose Responsible for a Project creates the mappings between the
DiagnosticExtract and the SWC available on OEM side (from 2.).
4. The OEM Diagnostic Responsible for a Project creates the mappings between
the DiagnosticExtract and the CompositionSwComponentTypes which
will be implemented by the ECU Supplier or SW Developer.
5. The ECU Suppliers receives the ECU Extract including DiagnosticExtract
from the OEM and imports it to the project.

29 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6. In the same way is in point 2., the SWC Developer on supplier or Tier 2 side
describes the Diagnostic information using ServiceNeeds as diagnostic contri-
bution.
In the same way as in point 3: The ECU Supplier Diagnostic Responsible creates the
mapping between the PortInterfaces of the DiagnosticExtract (from 5.) and
the SwComponentTypes as provided in 6.
For the usage of indicators, it might happen that indicators defined on BSW level in
DEM might not be automatically mapped to the implementation on SWC level. This
would then require a manual mapping step by the integrator to resolve the mismatch.

Imports the ECU extact and

extends the diagnostic extract
Creates an ECU description including communication with own software-components
extract, diagnostic extract, software-component
descriptions, etc.

Provides ECU extract incl.

partially or completely filled
«flow» diagnostic extract «flow»
OEM ECU supplier

«flow» «flow»

Provides software-component Provides software-component

description incl. related part of description incl. related part of
diagnostic extract diagnostic extract

«flow» «flow»

Software-component Software-component
developer by OEM or any developer by Tier-1 or
other software supplier Tier-2 supplier

Figure 2.3: Workflow scenario for diagnostic data exchange

2.4 Configuration of the Fim

2.4.1 Model Function Inhibition

A typical use case for the Fim is the definition of “control mechanisms for software
components and the functionality therein” [14]. By this means, the Fim can significantly

30 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

modify the behavior of the application software at run-time, e.g. in response to a sensor
failure.
The conditions for deciding about inhibitions are derived from diagnostic events. If a
diagnostic event that relates to a hardware sensor is reported as “failed” then the Fim
can degrade the behavior of the application software to no longer rely on the sensor
information that has become unreliable.
Consequently, the DiagnosticExtract needs to provide the basic mechanisms to
create the definition of such inhibition rules that relate pieces of the application soft-
ware (which are visible to the DiagnosticExtract as formally defined SwCompo-
nentTypes) to the definition of diagnostic events.

2.4.2 Model Fim configuration before Dem exists

The configuration of the Fim module and the Dem module are closely intertwined be-
cause the Fim uses the diagnostic events defined in the context of the Dem. This
means that the Fim can only be configured if the Dem exists as a basis for creating this
configuration.
Clearly, this is contradicting the approach of a “decentralized configuration” of the di-
agnostics stack’s behavior. It may happen that the configuration of the Fim and the
configuration of the Dem by means of the DiagnosticExtract are distributed over
different organizations within a concrete vehicle project.
However, the organizations would not be able to make progress independently of each
other because the work product of one is the immediate prerequisite that the other
organization can start working.
Therefore, one important use case for the DiagnosticExtract is the ability to con-
figure the Fim module in the scope of the DiagnosticExtract without the immedi-
ate need to already have access to the corresponding configuration of the Dem
module.
In other words, a typical work-flow could look like this:
1. Create the Fim configuration on the basis of a collection of alias objects that
represent the diagnostic events that are defined in the context of the Dem module
within the configuration of the Fim and in parallel create the Dem configuration
and thereby add definitions of the actual diagnostic events.
2. Ship the configuration of the Dem to the organization that is responsible for the
creation of the configuration of the Fim.
3. Let this organization take care of resolving the alias diagnostic events by way
of referring from the Fim configuration to the diagnostic events contained in the
actual Dem configuration.

31 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

2.5 Configuration of J1939 Diagnostics

Within the System Extract, J1939 diagnostic is configured on a service level by the
diagnostic messages DM01 .. DM57, which will be handled by J1939 Dcm.
The diagnostic content which is provided by the diagnostic messages is defined within
the DiagnosticExtract separately for each J1939 function, and contributes to the
configuration of the J1939 Dcm as well as the parts of the Dem configuration that are
relevant for J1939.
J1939 functions (known as Controller Application or CA within the SAE J1939 Stan-
dard [15]) are identified by a NAME and an address (assigned at run-time) and are
represented in AUTOSAR by the J1939NmNode.

2.5.1 Modeling of J1939 Diagnostic Aspects independent of the Deployment

The main use case for modeling the J1939 in the DiagnosticExtract is the pos-
sibility to create the diagnostic configuration relevant for a J1939 function, even if the
underlying communication architecture is not (fully) defined and if no vehicle model
(represented by a System) exists.
The J1939 diagnostics modeling is done during functional development before the
System exists where the functions are deployed. This approach represents a case of
decentralized configuration of the diagnostic stack.

2.5.2 J1939 Diagnostic Content modeled in the Diagnostic Extract

The diagnostic content for J1939 consists of the following topics:

SPN The Suspect Parameter Number is used throughout the J1939 specification to
identify measured values (physical signals) and commands, the communication
signals to which these are mapped, and diagnostic events caused by these.
Signals Communication signals that are relevant for diagnostics are specifically anno-
tated, and reported by the J1939 diagnostics.
DTCs J1939 DTCs consist of an SPN, identifying the source of the diagnostic event,
and an FMI (Failure Mode Indicator), identifying the problem with this source, like
a boundary exception. In addition, an event counter is contained in the DTC.
Freeze Frames contain measured valued captured at the time a diagnostic event is
reported as failed. J1939 supports two different kinds of freeze frames:
• standardized freeze frames (reported by DM04), which have a legislated
layout
• expanded freeze frames (reported by DM24/DM25), which have a config-
urable layout

32 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

3 Conceptual Background
Chapter 1 has already given an overview on the intended way of using the Diagnos-
ticExtract template and files. This chapter gives further background information on
the overall concept behind the new format to create a better basis for understanding of
the meta-model described in Chapter 4.

3.1 Definition of relevant Diagnostic Elements

[TPS_DEXT_01046] ECU configuration is not suitable to be exchanged between
partners in an ECU development project dThe ECU configuration (EcuC) parameters
defined by the AUTOSAR Software Specification (SWS) documents for Dem and Dcm
are not suitable to be exchanged between partners in an ECU development project.
Besides proprietary ways of using the EcuC format, the main reason for EcuC param-
eters being inappropriate to be exchanged is their closeness to implementation (e.g.
parameter on buffer sizes).c(RS_DEXT_00001)
[TPS_DEXT_01047] Differences in the development processes for diagnostics at
automotive OEMs and ECU suppliers dAdditionally, there are differences in the de-
velopment processes for diagnostics at automotive OEMs and ECU suppliers resulting
in different views on relevant diagnostic properties to be exchanged and different ways
of deriving and defining them as diagnostic requirements.c(RS_DEXT_00001)
Therefore, the identification of all diagnostic properties and requirements as superset
from the companies’ views forms the basis on which the DiagnosticExtract tem-
plate has been defined.

3.2 Abstraction from EcuC Level

The DiagnosticExtract template does not only focus on relevant diagnostic prop-
erties and requirements but also - if required - lift them onto an appropriate abstraction
level to make them meaningfully exchangeable (e.g. debouncing requirements that ab-
stract from mapping on a concrete ECU).
However, for many EcuC parameters identified as relevant, an abstraction is not useful
or not required and thus, these parameters are mapped 1:1 to equivalent elements of
the DiagnosticExtract template.
[TPS_DEXT_01140] Values contained in DiagnosticExtract shall be taken for
the derivation of basic software modules dThe values specified in a given Diag-
nosticExtract shall be taken for the derivation of basic software modules in the
diagnostic stack.
This means that parameter values in the Ecuc are created that could be subject to
constraints, e.g. a valid interval.c()

33 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Therefore, model elements in the DiagnosticExtract shall be carefully checked

against the constraints formulated in EcuC. However, this document does not contain
specific constraints on a detailed basis.

3.3 Independence of Definition

With respect to development processes, the DiagnosticExtract format also en-
ables more independence when defining requirements on diagnostic functionality than
possible with EcuC parameters. The approach of “decentralized configuration” is met
in the DiagnosticExtract template in mainly two ways described in the following
sub-chapters.

3.3.1 Use of atpSplitable enabling separation of elements over several

physical files

Most elements of the DiagnosticExtract template can be split over several phys-
ical files. Therefore, parts of these elements (e.g. certain attributes) can be defined
by, for example, an OEM and other parts of these elements by, for example, an ECU
supplier.

3.3.2 Use of self-contained mapping elements

Many diagnostic requirements are established by mappings between diagnostic ele-

ments (e.g., DTC to DemEvent mapping). However, the “decentralized configuration”
approach requires that these mappings can be flexibly defined at almost any time within
the ECU development process and by any of the involved companies respectively roles.
Therefore, the DiagnosticExtract template defines self-contained mapping ele-
ments that have references to two (or potentially more) diagnostic elements to define
a mapping.
The self-contained mapping elements can be created any time after the diagnostic
elements to be mapped together have been defined. Alternatively, a mapping element
can be created after only one diagnostic element has been defined indicating the need
to make the mapping complete by defining the additional diagnostic element(s) to map
to.

34 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4 Common Meta Model Elements

4.1 Introduction
This chapter contains a description of the meta-model for the specification of the
DiagnosticExtract in AUTOSAR. The goal of the specification of the Diagnos-
ticExtract is to contribute to the description of the configuration of the Diagnostic
Communication Manager [10] (Dcm) and the Diagnostic Event Manager [11]
(Dem)
The meta-model can be roughly divided into five sections
• A common section that contains meta-classes shared between the description of
the diagnostic services (that roughly corresponds to the Dcm) and the diagnostic
event handling (that roughly corresponds to the Dem), see section 4.2.
• A section dedicated to the configuration of the diagnostic services, see section 5.
• A section dedicated to the configuration of the diagnostic event handling, see
section 6.
• A section dedicated to the configuration of the functional inhibition from the diag-
nostics point of view, see section 7.
• A section dedicated to the configuration of the diagnostics on J1939, see section
8.

4.2 Data Identifier vs. Routine vs. Data Element

This chapter highlights the formal modeling of some of the central parts of AUTOSAR
diagnostics when it comes to configuration. There are some concepts widely used that
need to be reflected in the meta-model.
The purpose of the DiagnosticCommonElement is to provide a common reference
target for all kinds of diagnostic elements. This aspect is explained in more detail in
section 4.4.
The purpose of a Data Identifier (DID) is to associate a unique numerical value to
a piece of data related to diagnostics. From the modeling point of view, this means that
the modeling of the Data Identifier needs to provide an attribute that represents
the numeric value as well as a relation to a Data Element representing a set of
diagnostic piece of data.

35 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

«atpVariation»
SwDataDefProps

+ additionalNativeTypeQualifier: NativeDeclarationString [0..1]

+ displayFormat: DisplayFormatString [0..1]
+ displayPresentation: DisplayPresentationEnum [0..1]
+ stepSize: Float [0..1]
+ swAlignment: AlignmentType [0..1]
+ swCalibrationAccess: SwCalibrationAccessEnum [0..1] «enumeration»
+ swImplPolicy: SwImplPolicyEnum [0..1] ArraySizeSemanticsEnum
+ swIntendedResolution: Numerical [0..1]
+ swInterpolationMethod: Identifier [0..1] fixedSize
+ swIsVirtual: Boolean [0..1] variableSize
«atpVariation»
+ swValueBlockSize: Numerical [0..1]
+ swValueBlockSizeMult: Numerical [0..*] {ordered} Identifiable
DiagnosticDataElement
+swDataDefProps
+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]
0..1 + maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

+dataElement 0..1

DiagnosticCommonElement
DiagnosticSupportInfoByte
DiagnosticAbstractDataIdentifier
+ position: PositiveInteger [0..1] «atpVariation,atpSplitable»
«atpVariation» + size: PositiveInteger [0..1]
+ id: PositiveInteger [0..1]

  
+supportInfoByte 0..1 +supportInfoByte 0..1    


DiagnosticCommonElement
DiagnosticDynamicDataIdentifier DiagnosticDataIdentifier DiagnosticParameterSupportInfo
DiagnosticParameterIdentifier
+ didSize: PositiveInteger [0..1] + supportInfoBit: PositiveInteger [0..1]
+ representsVin: Boolean [0..1] + id: PositiveInteger [0..1]
+ pidSize: PositiveInteger [0..1]

+supportInfo 0..1

   «atpVariation,atpSplitable» «atpSplitable,atpVariation»
   

+dataElement 0..* +dataElement 0..*

DiagnosticParameter

«atpIdentityContributor»
+ bitOffset: PositiveInteger [0..1]

+request 0..* 0..* +request 0..* +response 0..* +response 0..* +request 0..*
+response

DiagnosticRoutineSubfunction DiagnosticRoutineSubfunction DiagnosticRoutineSubfunction

DiagnosticRequestRoutineResults DiagnosticStartRoutine DiagnosticStopRoutine

+requestResult 0..1 +start 0..1 +stop 0..1

DiagnosticCommonElement
DiagnosticRoutine

+ routineInfo: PositiveInteger [0..1]

«atpVariation»
+ id: PositiveInteger [0..1]

Figure 4.1: Common Diagnostic elements

[TPS_DEXT_01000] AUTOSAR diagnostics supports two kinds of data identifiers

dIn AUTOSAR, two kinds of data identifiers are supported:
• The DiagnosticDataIdentifier inherits from DiagnosticAbstract-
DataIdentifier and is used to define data identifiers fully known at config-
uration time. A DiagnosticDataIdentifier shall have at least 1 dataEle-
ment.
• The DiagnosticDynamicDataIdentifier inherits from DiagnosticAb-
stractDataIdentifier and is used to define data identifiers fully known only

36 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

at run time. Consequently, there is no formal means to define dataElement at

configuration time.
c(RS_DEXT_00034, RS_DEXT_00035)
Class DiagnosticCommonElement (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents a common base class for all diagnostic elements. It does not contribute any
specific functionality other than the ability to become the target of a reference.
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Subclasses DiagnosticAbstractAliasEvent, DiagnosticAbstractDataIdentifier , DiagnosticAccessPermission,
DiagnosticAging, DiagnosticCondition, DiagnosticConditionGroup, DiagnosticCustomServiceClass,
DiagnosticDataIdentifierSet, DiagnosticEcuInstanceProps, DiagnosticEnvironmentalCondition,
DiagnosticEvent, DiagnosticExtendedDataRecord, DiagnosticFimEventGroup, DiagnosticFreezeFrame,
DiagnosticFunctionIdentifier, DiagnosticFunctionIdentifierInhibit, DiagnosticIndicator, DiagnosticInfoType,
DiagnosticIumpr, DiagnosticIumprDenominatorGroup, DiagnosticIumprGroup, DiagnosticJ1939
ExpandedFreezeFrame, DiagnosticJ1939FreezeFrame, DiagnosticJ1939Node, DiagnosticJ1939Spn,
DiagnosticJ1939SwMapping, DiagnosticMapping, DiagnosticMasterToSlaveEventMapping, Diagnostic
MeasurementIdentifier, DiagnosticMemoryDestination, DiagnosticMemoryIdentifier, DiagnosticOperation
Cycle, DiagnosticParameterIdentifier, DiagnosticPowertrainFreezeFrame, DiagnosticProtocol, Diagnostic
Routine, DiagnosticSecurityLevel, DiagnosticServiceClass, DiagnosticServiceInstance, Diagnostic
ServiceTable, DiagnosticSession, DiagnosticTestResult, DiagnosticTestRoutineIdentifier, Diagnostic
TroubleCode, DiagnosticTroubleCodeGroup, DiagnosticTroubleCodeProps
Attribute Type Mult. Kind Note
– – – – –
Table 4.1: DiagnosticCommonElement

Class DiagnosticParameter
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to describe information relevant for the execution of a specific
diagnostic service, i.e. it can be taken to parameterize the service.
Base ARObject
Attribute Type Mult. Kind Note
bitOffset PositiveInteger 0..1 attr This represents the bitOffset of the DiagnosticParameter
Stereotypes: atpIdentityContributor
dataElement DiagnosticDataElement 0..1 aggr This represents the related dataElement of the Diagnostic
Parameter
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=dataElement.shortName, data
Element.variationPoint.shortLabel
vh.latestBindingTime=postBuild
supportInfo DiagnosticParameter 0..1 aggr This attribute represents the ability to define which bit of
SupportInfo the support info byte is representing this part of the PID.

Table 4.2: DiagnosticParameter

[constr_1790] Existence of attribute DiagnosticParameter.bitOffset dFor

each DiagnosticParameter, attribute bitOffset shall exist at the time when the
DEXT is complete.c()
[constr_1791] Existence of attribute DiagnosticParameter.dataElement dFor
each DiagnosticParameter, attribute dataElement shall exist at the time when
the DEXT is complete.c()

37 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticDataIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to model a diagnostic data identifier (DID) that is fully specified
regarding the payload at configuration-time.
Tags:atp.recommendedPackage=DiagnosticDataIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticAbstractDataIdentifier , DiagnosticCommon
Element, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataElement DiagnosticParameter * aggr This is the dataElement associated with the Diagnostic
DataIdentifier.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=dataElement.bitOffset, dataElement.variation
Point.shortLabel
vh.latestBindingTime=postBuild
didSize PositiveInteger 0..1 attr This attribute indicates the size in bytes of the Diagnostic
DataIdentifier.
representsVin Boolean 0..1 attr This attributes indicates whether the specific Diagnostic
DataIdentifier represents the vehicle identification.
supportInfoByte DiagnosticSupportInfo 0..1 aggr This attribute represents the supported information
Byte associated with the DiagnosticDataIdentifier.

Table 4.3: DiagnosticDataIdentifier

[constr_1792] Existence of DiagnosticDataIdentifier.dataElement dFor

each DiagnosticDataIdentifier, the aggregation of DiagnosticParameter
in the role dataElement shall exist at lest once at the time when the DEXT is com-
plete.c()
Class DiagnosticDynamicDataIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to define a diagnostic data identifier (DID) at run-time.
Tags:atp.recommendedPackage=DiagnosticDataIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticAbstractDataIdentifier , DiagnosticCommon
Element, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 4.4: DiagnosticDynamicDataIdentifier

Class DiagnosticAbstractDataIdentifier (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents an abstract base class for the modeling of a diagnostic data identifier (DID).
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticDataIdentifier, DiagnosticDynamicDataIdentifier
Attribute Type Mult. Kind Note
5

38 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticAbstractDataIdentifier (abstract)
id PositiveInteger 0..1 attr This is the numerical identifier used to identify the
DiagnosticAbstractDataIdentifier in the scope of
diagnostic workflow
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 4.5: DiagnosticAbstractDataIdentifier

[constr_1793] Existence of attribute DiagnosticAbstractDataIdentifier.id

dFor each DiagnosticAbstractDataIdentifier, attribute id shall exist at the
time when the DEXT is complete.c()
[TPS_DEXT_01072] Purpose of attribute DiagnosticDataIdentifier.repre-
sentsVin dThere is a use case for identifying a specific DiagnosticDataIdenti-
fier that carries the so-called vehicle identification number (VIN).
It is therefore important to be able to formally indicate this characteristic. For this
purpose the attribute DiagnosticDataIdentifier.representsVin is available.c
(RS_DEXT_00034)
[constr_1324] Existence of attribute DiagnosticDataIdentifier.repre-
sentsVin dWithin the context of a given DiagnosticContributionSet, the at-
tribute DiagnosticDataIdentifier.representsVin shall have the value true
for only a single DiagnosticDataIdentifier.c()
Please note that the VIN is only relevant in the context of diagnostics over IP (DoIP).
However, there is no constraint that bounds the validity of [constr_1324] to the exis-
tence of a DiagnosticConnection that is build on top of an IP stack.
If the attribute exists and there is no IP used then the meaning of the attribute is simply
irrelevant. Anyway, this situation should not be attributed to a misconfiguration.
The concept of the Data Element represents a piece of information decomposed
from the data identified by a DID and exchanged between the DEM and, for example,
a tester.
The nature of such a Data Element could be compared to the nature of an ISignal1
and therefore the modeling of a Data Element by means of the meta-class Diag-
nosticDataElement aggregates SwDataDefProps in the role swDataDefProps
in order to provide a reference to SwBaseType.
The aggregation of SwDataDefProps can also be used to refer to a DataConstr in
order to specify a valid data range for the DiagnosticDataElement.
1
which represents the payload in “regular” bus communication

39 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticDataElement
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to describe a concrete piece of data to be taken into account for
diagnostic purposes.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
arraySize ArraySizeSemantics 0..1 attr This attribute controls the meaning of the value of the
Semantics Enum array size.
maxNumberOf PositiveInteger 0..1 attr The existence of this attribute turns the data instance into
Elements an array of data. The attribute determines the size of the
array in terms of how many elements the array can take.
scalingInfoSize PositiveInteger 0..1 attr Size in bytes of scaling information for the DiagnosticData
Element if used with DiagnosticReadScalingDataBy
Identifier
swDataDef SwDataDefProps 0..1 aggr This property allows to specify data definition properties
Props in order to support the definition of e.g. computation
formulae and data constraints.
Table 4.6: DiagnosticDataElement

[constr_1394] Value of DiagnosticDataElement.maxNumberOfElements de-

pending on its existence dIf the attribute DiagnosticDataElement.maxNumberO-
fElements exists then its value shall be greater than 0.c()
[TPS_DEXT_01134] Definition of a DiagnosticDataElement used in the con-
text of a DID obtained by sender-receiver communication dIf the Diagnostic-
DataElement is aggregated by a DiagnosticParameter that in turn is aggregated
by a subclass of DiagnosticAbstractDataIdentifier and the Diagnostic-
DataElement is also referenced by a DiagnosticServiceDataMapping then the
referenced DiagnosticDataElement (by way of SwDataDefProps) shall refer to
a SwBaseType with attribute baseTypeSize set to either 8, 16, or 32 and attribute
baseTypeEncoding set to either
• NONE (for 8, 16, or 32 bit) or
• 2C (for 8, 16, or 32 bit) or
• IEEE754 (for 32 bit).
In this case it is possible to define the DiagnosticDataElement either as a scalar
or as an array (see [TPS_DEXT_01001], [TPS_DEXT_01002]).c(RS_DEXT_00034)
[TPS_DEXT_01135] Definition of a DiagnosticDataElement used in the context
of a DID obtained by client/server communication dIf the DiagnosticDataEle-
ment is aggregated by a DiagnosticParameter that in turn is aggregated by a sub-
class of DiagnosticAbstractDataIdentifier and the DiagnosticDataEle-
ment is also referenced by a DiagnosticServiceSwMapping then the referenced
DiagnosticDataElement (by way of SwDataDefProps) shall refer to a SwBase-
Type with attribute baseTypeSize set to either 8, 16, or 32 and attribute baseType-
Encoding set to either
• NONE (for 8, 16, or 32 bit) or

40 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• 2C (for 8, 16, or 32 bit) or

• IEEE754 (for 32 bit).
In this case it is only possible to define the DiagnosticDataElement as an array
(see [TPS_DEXT_01001], [TPS_DEXT_01002]). The ability to define a Variable-Size
Array shall only be used for the last element of the DID.c(RS_DEXT_00034)
[TPS_DEXT_01136] Definition of a DiagnosticDataElement used in the context
of a diagnostic routine dIf the DiagnosticDataElement is aggregated by a Di-
agnosticParameter that in turn is aggregated by either a DiagnosticStartRou-
tine, DiagnosticStopRoutine, or DiagnosticRequestRoutineResults then
the DiagnosticDataElement (by way of SwDataDefProps) shall refer to a
SwBaseType with attribute baseTypeSize to either 8, 16, or 32 and attribute base-
TypeEncoding set to either
• NONE (for 8, 16, or 32 bit) or
• 2C (for 8, 16, or 32 bit) or
• IEEE754 (for 32 bit).
In this case it is possible to define the DiagnosticDataElement either as a scalar
or as an array (see [TPS_DEXT_01001], [TPS_DEXT_01002]). The ability to define a
Variable-Size Array shall only be used for the last argument to the diagnostic routine.c
(RS_DEXT_00034)
[constr_1470] Value of DiagnosticParameter.bitOffset dThe value of Diag-
nosticParameter.bitOffset shall only be set to a multiple of 8.c()
Enumeration ArraySizeSemanticsEnum
Package M2::AUTOSARTemplates::CommonStructure::ImplementationDataTypes
Note This type controls how the information about the number of elements in an ApplicationArrayDataType
is to be interpreted.
Literal Description
fixedSize This means that the ApplicationArrayDataType will always have a fixed number of elements.
Tags:atp.EnumerationLiteralIndex=0
variableSize This implies that the actual number of elements in the ApplicationArrayDataType might vary at
run-time. The value of arraySize represents the maximum number of elements in the array.
Tags:atp.EnumerationLiteralIndex=1

Table 4.7: ArraySizeSemanticsEnum

The attribute DiagnosticDataIdentifier.didSize should be used if size of the

DID data is intended to be enforced2 .
[constr_1552] DiagnosticDataIdentifier referenced by Diagnostic-
DataIdentifierSet dIf a DiagnosticDataIdentifier is referenced by
DiagnosticDataIdentifierSet then the DiagnosticDataIdentifier shall
not have gaps in between individual elements (as indicated by DiagnosticParam-
2
one use case for this enforcement was described by the removed [constr_1471] contained in former
versions of this document

41 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

eter.bitOffset and the length of the aggregated DiagnosticDataElement)

or at the end of the DiagnosticDataIdentifier (as indicated by attribute
DiagnosticDataIdentifier.didSize).c()
[TPS_DEXT_01138] Applicability of DiagnosticDataIdentifier.supportIn-
foByte dThe attribute DiagnosticDataIdentifier.supportInfoByte may ex-
ist if the value of DiagnosticDataIdentifier.id is in the range 0xF400-0xF4FF.
A typical case for the existence of DiagnosticDataIdentifier.supportIn-
foByte is the understanding that the DiagnosticDataIdentifier is relevant for
OBD and the DiagnosticDataIdentifier.id is in the designated range.c(RS_-
DEXT_00034)
[constr_1472] Existence of DiagnosticDataIdentifier.supportInfoByte
dThe attribute DiagnosticDataIdentifier.supportInfoByte shall not exist
if the value of DiagnosticDataIdentifier.id is outside the range 0xF400-
0xF4FF.c()

4.2.1 Usage of SwDataDefProps

Please note that the definitions of properties like computation methods3 , limits4 , or
units5 of diagnostic data elements is based on shared resources of the AUTOSAR
meta-model, namely by aggregation of meta-class SwDataDefProps.
This meta-class contributes a wealth of possible properties related to the definition of
data in general and, in this case, diagnostics in particular.
However, it is important to understand that SwDataDefProps is so expressive and
versatile that its applicability needs to be constrained (in this specific case, see [con-
str_1325]) for specific deployments according to the requirements that originate from
the semantics of the piece of data that is decorated by SwDataDefProps.
[constr_1325] Allowed attributes of SwDataDefProps for DiagnosticDataEle-
ment.swDataDefProps dThe allowed attributes of SwDataDefProps for the aggre-
gation in the role DiagnosticDataElement.swDataDefProps are defined in table
4.8.c()
3
formalized as CompuMethod in AUTOSAR
4
formalized as DataConstr in AUTOSAR
5
formalized as Unit in AUTOSAR

42 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Attributes of SwDataDefProps DiagnosticDataElement.swDataDefProps

additionalNativeTypeQualifier N/A
annotation N/A
baseType.baseTypeDefinition.baseTypeEncoding D
baseType.baseTypeDefinition.baseTypeSize D
baseType.baseTypeDefinition.byteOrder D
baseType.baseTypeDefinition.memAlignment N/A
baseType.baseTypeDefinition.nativeDeclaration N/A
compuMethod D
dataConstr D
displayFormat D
displayPresentation N/A
implementationDataType N/A
invalidValue N/A
swAddrMethod N/A
swAlignment N/A
swBitRepresentation N/A
swCalibrationAccess N/A
swCalprmAxisSet N/A
swComparisonVariable N/A
swDataDependency N/A
swImplPolicy N/A
swIntendedResolution N/A
swInterpolationMethod N/A
swIsVirtual N/A
swPointerTargetProps N/A
swRecordLayout N/A
swRefreshTiming N/A
swTextProps N/A
swValueBlockSize N/A
unit D
valueAxisDataType N/A

Table 4.8: Allowed attributes of SwDataDefProps for DiagnosticDataElement.

swDataDefProps

The following legend applies to table 4.8:

Abbr. Description
D Define the attribute independent from settings to the left.
I Inherit the definition from the left for usage in the scope of this element.
N/A Attribute is not applicable for usage in the scope of this element.
M Attribute is meaningless in the scope of this element. As it was allowed in previous versions, declaring it as Not
Applicable (NA) would break compatibility. Tools shall ignore such an attribute without a warning.

Table 4.9: Legend of table “Allowed attributes of SwDataDefProps for Diagnostic-

DataElement.swDataDefProps”

Please note that, in comparison to similar tables appearing in other AUTOSAR docu-
ments (e.g. [8]), table 4.8 intentionally goes into more detail regarding the applicability

43 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

of the attributes of SwBaseType. This is in contrast to similar tables contained in, e.g.
the specification of the Software-Component Template [8]
The attributes of SwBaseType are considered of paramount importance for the def-
inition of the semantics of the enclosing DiagnosticDataElement and thus the
emphasis is justified.
Class <<atpVariation>> SwDataDefProps
Package M2::MSR::DataDictionary::DataDefProperties
Note This class is a collection of properties relevant for data objects under various aspects. One could
consider this class as a "pattern of inheritance by aggregation". The properties can be applied to all
objects of all classes in which SwDataDefProps is aggregated.
Note that not all of the attributes or associated elements are useful all of the time. Hence, the process
definition (e.g. expressed with an OCL or a Document Control Instance MSR-DCI) has the task of
implementing limitations.
SwDataDefProps covers various aspects:
• Structure of the data element for calibration use cases: is it a single value, a curve, or a map, but
also the recordLayouts which specify how such elements are mapped/converted to the Data
Types in the programming language (or in AUTOSAR). This is mainly expressed by properties
like swRecordLayout and swCalprmAxisSet
• Implementation aspects, mainly expressed by swImplPolicy, swVariableAccessImplPolicy, sw
AddrMethod, swPointerTagetProps, baseType, implementationDataType and additionalNative
TypeQualifier
• Access policy for the MCD system, mainly expressed by swCalibrationAccess
• Semantics of the data element, mainly expressed by compuMethod and/or unit, dataConstr,
invalidValue
• Code generation policy provided by swRecordLayout
Tags:vh.latestBindingTime=codeGenerationTime
Base ARObject
Attribute Type Mult. Kind Note
additionalNative NativeDeclarationString 0..1 attr This attribute is used to declare native qualifiers of the
TypeQualifier programming language which can neither be deduced
from the baseType (e.g. because the data object
describes a pointer) nor from other more abstract
attributes. Examples are qualifiers like "volatile", "strict" or
"enum" of the C-language. All such declarations have to
be put into one string.
Tags:xml.sequenceOffset=235
annotation Annotation * aggr This aggregation allows to add annotations (yellow pads
...) related to the current data object.
Tags:
xml.roleElement=true
xml.roleWrapperElement=true
xml.sequenceOffset=20
xml.typeElement=false
xml.typeWrapperElement=false
baseType SwBaseType 0..1 ref Base type associated with the containing data object.
Tags:xml.sequenceOffset=50
compuMethod CompuMethod 0..1 ref Computation method associated with the semantics of
this data object.
Tags:xml.sequenceOffset=180
5

44 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpVariation>> SwDataDefProps
dataConstr DataConstr 0..1 ref Data constraint for this data object.
Tags:xml.sequenceOffset=190
displayFormat DisplayFormatString 0..1 attr This property describes how a number is to be rendered
e.g. in documents or in a measurement and calibration
system.
Tags:xml.sequenceOffset=210
display DisplayPresentation 0..1 attr This attribute controls the presentation of the related data
Presentation Enum for measurement and calibration tools.
implementation AbstractImplementation 0..1 ref This association denotes the ImplementationDataType of
DataType DataType a data declaration via its aggregated SwDataDefProps. It
is used whenever a data declaration is not directly
referring to a base type. Especially
• redefinition of an ImplementationDataType via a
"typedef" to another ImplementationDatatype
• the target type of a pointer (see SwPointerTarget
Props), if it does not refer to a base type directly
• the data type of an array or record element within
an ImplementationDataType, if it does not refer to
a base type directly
• the data type of an SwServiceArg, if it does not
refer to a base type directly
Tags:xml.sequenceOffset=215
invalidValue ValueSpecification 0..1 aggr Optional value to express invalidity of the actual data
element.
Tags:xml.sequenceOffset=255
stepSize Float 0..1 attr This attribute can be used to define a value which is
added to or subtracted from the value of a DataPrototype
when using up/down keys while calibrating.
swAddrMethod SwAddrMethod 0..1 ref Addressing method related to this data object. Via an
association to the same SwAddrMethod it can be
specified that several DataPrototypes shall be located in
the same memory without already specifying the memory
section itself.
Tags:xml.sequenceOffset=30
swAlignment AlignmentType 0..1 attr The attribute describes the intended alignment of the
DataPrototype. If the attribute is not defined the alignment
is determined by the swBaseType size and the memory
AllocationKeywordPolicy of the referenced SwAddr
Method.
Tags:xml.sequenceOffset=33
swBit SwBitRepresentation 0..1 aggr Description of the binary representation in case of a bit
Representation variable.
Tags:xml.sequenceOffset=60
swCalibration SwCalibrationAccess 0..1 attr Specifies the read or write access by MCD tools for this
Access Enum data object.
Tags:xml.sequenceOffset=70
swCalprmAxis SwCalprmAxisSet 0..1 aggr This specifies the properties of the axes in case of a
Set curve or map etc. This is mainly applicable to calibration
parameters.
Tags:xml.sequenceOffset=90
5

45 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpVariation>> SwDataDefProps
swComparison SwVariableRefProxy * aggr Variables used for comparison in an MCD process.
Variable
Tags:
xml.sequenceOffset=170
xml.typeElement=false
swData SwDataDependency 0..1 aggr Describes how the value of the data object has to be
Dependency calculated from the value of another data object (by the
MCD system).
Tags:xml.sequenceOffset=200
swHostVariable SwVariableRefProxy 0..1 aggr Contains a reference to a variable which serves as a
host-variable for a bit variable. Only applicable to bit
objects.
Tags:
xml.sequenceOffset=220
xml.typeElement=false
swImplPolicy SwImplPolicyEnum 0..1 attr Implementation policy for this data object.
Tags:xml.sequenceOffset=230
swIntended Numerical 0..1 attr The purpose of this element is to describe the requested
Resolution quantization of data objects early on in the design
process.
The resolution ultimately occurs via the conversion
formula present (compuMethod), which specifies the
transition from the physical world to the standardized
world (and vice-versa) (here, "the slope per bit" is present
implicitly in the conversion formula).
In the case of a development phase without a fixed
conversion formula, a pre-specification can occur through
swIntendedResolution.
The resolution is specified in the physical domain
according to the property "unit".
Tags:xml.sequenceOffset=240
swInterpolation Identifier 0..1 attr This is a keyword identifying the mathematical method to
Method be applied for interpolation. The keyword needs to be
related to the interpolation routine which needs to be
invoked.
Tags:xml.sequenceOffset=250
swIsVirtual Boolean 0..1 attr This element distinguishes virtual objects. Virtual objects
do not appear in the memory, their derivation is much
more dependent on other objects and hence they shall
have a swDataDependency .
Tags:xml.sequenceOffset=260
swPointerTarget SwPointerTargetProps 0..1 aggr Specifies that the containing data object is a pointer to
Props another data object.
Tags:xml.sequenceOffset=280
swRecord SwRecordLayout 0..1 ref Record layout for this data object.
Layout
Tags:xml.sequenceOffset=290
swRefresh MultidimensionalTime 0..1 aggr This element specifies the frequency in which the object
Timing involved shall be or is called or calculated. This timing
can be collected from the task in which write access
processes to the variable run. But this cannot be done by
the MCD system.
5
5

46 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpVariation>> SwDataDefProps
4
So this attribute can be used in an early phase to express
the desired refresh timing and later on to specify the real
refresh timing.
Tags:xml.sequenceOffset=300
swTextProps SwTextProps 0..1 aggr the specific properties if the data object is a text object.
Tags:xml.sequenceOffset=120
swValueBlock Numerical 0..1 attr This represents the size of a Value Block
Size
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=80
swValueBlock Numerical * attr This attribute is used to specify the dimensions of a value
SizeMult block (VAL_BLK) for the case that that value block has
(ordered) more than one dimension.
The dimensions given in this attribute are ordered such
that the first entry represents the first dimension, the
second entry represents the second dimension, and so
on.
For one-dimensional value blocks the attribute swValue
BlockSize shall be used and this attribute shall not exist.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
unit Unit 0..1 ref Physical unit associated with the semantics of this data
object. This attribute applies if no compuMethod is
specified. If both units (this as well as via compuMethod)
are specified the units shall be compatible.
Tags:xml.sequenceOffset=350
valueAxisData ApplicationPrimitive 0..1 ref The referenced ApplicationPrimitiveDataType represents
Type DataType the primitive data type of the value axis within a
compound primitive (e.g. curve, map). It supersedes
CompuMethod, Unit, and BaseType.
Tags:xml.sequenceOffset=355

Table 4.10: SwDataDefProps

4.2.2 Definition of Arrays

There are several use cases for a DiagnosticDataElement that actually represents
an array of information. In some cases the array size is static and will not change at
run-time, and in some cases the array size needs to change at run-time to fulfill the
intended purpose.
[TPS_DEXT_01001] Definition of a fixed-sized array dA DiagnosticDataEle-
ment shall be interpreted as a fixed-size array if all of the following conditions apply:
1. The attribute DiagnosticDataElement.maxNumberOfElements exists.
2. The value of the attribute DiagnosticDataElement.maxNumberOfElements
is set to a value > 0.

47 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

3. The value of DiagnosticDataElement.arraySizeSemantics either does

not exist or is set to ArraySizeSemanticsEnum.fixedSize.
c(RS_DEXT_00034, RS_DEXT_00038)
[TPS_DEXT_01002] Definition of a variable-sized array dA DiagnosticDataEle-
ment shall be interpreted as a variable-size array if all of the following conditions
apply:
1. The attribute DiagnosticDataElement.maxNumberOfElements exists.
2. The value of the attribute DiagnosticDataElement.maxNumberOfElements
is set to a value > 0.
3. The value of DiagnosticDataElement.arraySizeSemantics is set to Ar-
raySizeSemanticsEnum.variableSize.
The value of DiagnosticDataElement.maxNumberOfElements shall be consid-
ered the maximum array size in terms of the number of elements.c(RS_DEXT_00034,
RS_DEXT_00038)
[constr_1326] Existence of a variable-sized array dThe value of the attribute Diag-
nosticDataElement.arraySizeSemantics shall not be set to ArraySizeSe-
manticsEnum.variableSize if the respective DiagnosticDataElement is refer-
enced from a DiagnosticServiceDataMapping.c()

4.2.3 Definition of textual Strings

DiagnosticDataElement can be used to model a textual string that shall be send

to or received from the ECU by the tester.
In this case it will be necessary to define the intended encoding such that the part of
the software on the ECU that produces or consumes of the string on the ECU can be
checked (after the establishment of a DiagnosticMapping) for a matching encoding
specification.
The encoding in the scope of the DiagnosticDataElement can be defined using
the attribute DiagnosticDataElement.swDataDefProps.baseType.baseType-
Definition.baseTypeEncoding.

4.3 Textual Documentation

A Data Identifier also usually comes with some textual description that explains
the meaning of the Data Identifier in short form. This ability is available via the
inheritance from Identifiable, in particular by means of the attributes desc and/or
introduction (see Figure 4.2).

48 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

This also means that the ability to add some form of textual description is widely usable
in the scope of the DiagnosticExtract. Many meta-classes are derived from e.g.
DiagnosticCommonElement (which inherits from Identifiable) or directly from
Identifiable and therefore qualify for the described form of documentation.
In other words, the technology described in Figures 4.2 and 4.3 is not limited to Diag-
nosticDataElement but has a much wider applicability in the context of the Diag-
nosticExtract.
Referrable

«atpIdentityContributor»
+ shortName: Identifier

MultilanguageReferrable MultilanguageLongName
+longName

0..1

   

  
  
   
   
    

Identifiable MultiLanguageOverviewParagraph
+desc
+ category: CategoryString [0..1]
+ uuid: String [0..1] 0..1

AdminData
+adminData
+ language: LEnum [0..1]
0..1

«atpMixed»
+introduction DocumentationBlock

0..1

GeneralAnnotation
+annotation Annotation

0..*

Figure 4.2: Definition of a textual description by means of desc and introduction

The details regarding the specification of textual content that goes along a given di-
agnostics element is detailed in Figure 4.3. In fact, DocumentationBlock provides
a very sophisticated ability to define structured text that may consist e.g. of multiple
paragraphs (formalized by meta-class MultiLanguageOverviewParagraph aggre-
gated in the role p).
In addition to the ability to attach structured text, it is also possible to use the anno-
tation (see Figure 4.2) to add short annotations (comparable to the usage of sticky
notes) to diagnostic elements.

49 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

 

    

«atpMixed» +p Paginateable
DocumentationBlock «atpVariation» 0..1 MultiLanguageParagraph

Paginateable
+verbatim
MultiLanguageVerbatim
«atpVariation» 0..1

+list +item
Paginateable Paginateable
«atpVariation» «atpVariation» 1..*
0..1 List Item

+itemContents 1

+defList +defItem
Paginateable MultilanguageReferrable
«atpVariation» 0..1 «atpVariation» 1..* Paginateable
DefList
+def DefItem

1
+labeledList
Paginateable +labeledItem Paginateable
«atpVariation» 0..1 LabeledList LabeledItem
«atpVariation» 1..*
+itemContents

0..1

Paginateable
+formula
MlFormula
«atpVariation» 0..1

+itemLabel 1

+figure Paginateable
MultiLanguageOverviewParagraph
MlFigure
«atpVariation» 0..1

+note
Paginateable
«atpVariation» 0..1 Note
+noteText

+trace Identifiable
Paginateable
«atpVariation» 0..1 Traceable
+text TraceableText
1

+structuredReq Identifiable
Paginateable
«atpVariation» 0..1 Traceable
StructuredReq

+msrQueryResultP2 MsrQueryP2
0..1
+msrQueryP2

0..1
+entryContents
Entry
  
 

 
 
  

1     
     
   

Figure 4.3: Details of the modeling of DocumentationBlock

50 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class <<atpMixed>> DocumentationBlock

Package M2::MSR::Documentation::BlockElements
Note This class represents a documentation block. It is made of basic text structure elements which can be
displayed in a table cell.
Base ARObject
Attribute Type Mult. Kind Note
defList DefList 0..1 aggr This represents a definition list in the documentation
block.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=40
figure MlFigure 0..1 aggr This represents a figure in the documentation block.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=70
formula MlFormula 0..1 aggr This is a formula in the definition block.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=60
labeledList LabeledList 0..1 aggr This represents a labeled list.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=50
list List 0..1 aggr This represents numbered or unnumbered list.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=30
msrQueryP2 MsrQueryP2 0..1 aggr This represents automatically contributed contents
provided by an msrquery in the context of Documentation
Block.
note Note 0..1 aggr This represents a note in the text flow.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=80
p MultiLanguage 0..1 aggr This is one particular paragraph.
Paragraph
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=10
structuredReq StructuredReq 0..1 aggr This aggregation supports structured requirements
embedded in a documentation block.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=100
5

51 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpMixed>> DocumentationBlock
trace TraceableText 0..1 aggr This represents traceable text in the documentation block.
This allows to specify requirements/constraints in any
documentation block.
The kind of the trace is specified in the category.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=90
verbatim MultiLanguageVerbatim 0..1 aggr This represents one particular verbatim text.
Stereotypes: atpVariation
Tags:
vh.latestBindingTime=postBuild
xml.sequenceOffset=20

Table 4.11: DocumentationBlock

Class MultiLanguageOverviewParagraph
Package M2::MSR::Documentation::TextModel::MultilanguageData
Note This is the content of a multilingual paragraph in an overview item.
Base ARObject
Attribute Type Mult. Kind Note
l2 LOverviewParagraph 1..* aggr This represents the text in one particular language.
Tags:
xml.roleElement=true
xml.roleWrapperElement=false
xml.sequenceOffset=20
xml.typeElement=false
xml.typeWrapperElement=false

Table 4.12: MultiLanguageOverviewParagraph

4.4 Diagnostic Contribution

[TPS_DEXT_01003] DiagnosticContributionSet is the central part of the Di-
agnosticExtract dThe central part of formalization of the concept of the Diagnos-
ticExtract is the DiagnosticContributionSet.
To some extent, it fulfills a similar role as the System [6] in the communication domain.c
(RS_DEXT_00001)
The DiagnosticContributionSet maintains references to DiagnosticCom-
monElement and by this means the actual definition of the extent of diagnostic contri-
bution takes place.
In other words, the actual extent of a given contribution is created by the collection of
DiagnosticCommonElements referenced by the DiagnosticContributionSet.
[TPS_DEXT_01004] DiagnosticContributionSet defines the scope of the Di-
agnosticExtract dThe DiagnosticContributionSet has the ability to define
the scope of the given DiagnosticExtract. This means that the DiagnosticCon-

52 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

tributionSet represents the DiagnosticExtract for the rest of the AUTOSAR

model.
In other words, the DiagnosticContributionSet assumes a similar crucial role
as the System in that it defines the extent to which a given description of diagnostic
behavior is valid.
Any downstream processing of the description of diagnostic behavior shall take the
scope of information to be processed from the definition of the DiagnosticContri-
butionSet in its role as the root element of the description of diagnostic behavior.
During different stages of the design methodology, the scope of the Diagnostic-
ContributionSet may vary between the scope of an entire system down to the
contribution of a specific tier-1 supplier to a much bigger context.c(RS_DEXT_00001)
[TPS_DEXT_01055] Standardized values of DiagnosticContributionSet.
category dThe scope of the DiagnosticContributionSet, on the other hand
is determined by the value of its category. The following values are predefined by
AUTOSAR:
DIAGNOSTICS_ABSTRACT_SYSTEM_DESCRIPTION this DiagnosticContribu-
tionSet represents a more or less high-level definition that can be taken as a
template for creating concrete DiagnosticContributionSets of category
DIAGNOSTICS_SYSTEM_EXTRACT or DIAGNOSTICS_ECU_EXTRACT
DIAGNOSTICS_SYSTEM_EXTRACT the scope of this DiagnosticContribution-
Set consists of several EcuInstances.
DIAGNOSTICS_ECU_EXTRACT the scope of this DiagnosticContributionSet
consists of a single EcuInstances. A DiagnosticContributionSet of
category DIAGNOSTICS_ECU_EXTRACT shall be taken as the basis for the
derivation of service software-components of the diagnostic stack.
c(RS_DEXT_00001)
[constr_1327] Multiplicity of DiagnosticEcuInstanceProps.ecuInstance
dThe multiplicity of DiagnosticEcuInstanceProps.ecuInstance shall be limited
to 1 and the enclosing DiagnosticContributionSet shall only refer to at most one
DiagnosticEcuInstanceProps if the enclosing DiagnosticContributionSet
is of category DIAGNOSTICS_ECU_EXTRACT.c()
[constr_1328] Consistency of DiagnosticEcuInstanceProps.ecuInstance
and DiagnosticServiceTable.ecuInstance dEach DiagnosticServic-
eTable referenced by any given DiagnosticContributionSet in the role
serviceTable shall define a reference in the role DiagnosticServiceTable.
ecuInstance to an EcuInstance that is also referenced in the role Diagnos-
ticEcuInstanceProps.ecuInstance by a DiagnosticEcuInstanceProps
referenced by the mentioned DiagnosticContributionSet if the respective
DiagnosticContributionSet is of category DIAGNOSTICS_ECU_EXTRACT.c()

53 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Please note that [constr_1328] resolves an intentional redundancy in the meta-model.

Both DiagnosticContributionSet and DiagnosticServiceTable are able re-
fer to EcuInstance with the idea that both DiagnosticContributionSet and
DiagnosticServiceTable can be modeled independently of each other.
Of course, once the DiagnosticContributionSet and DiagnosticServic-
eTable are integrated in the same context (in particular by establishing the refer-
ence DiagnosticContributionSet.serviceTable) the individual references to
the applicable EcuInstances need to be consistent.
+diagnosticConnection ARElement
DiagnosticServiceTable
DiagnosticConnection
«atpVariation,atpSplitable» 0..*
+ protocolKind: NameToken [0..1]

  
   
 FibexElement
EcuInstance

+ comConfigurationGwTimeBase: TimeValue [0..1]

+ comConfigurationRxTimeBase: TimeValue [0..1]
+ comConfigurationTxTimeBase: TimeValue [0..1]
+ecuInstance + comEnableMDTForCyclicTransmission: Boolean [0..1]
0..1 + ethSwitchPortGroupDerivation: Boolean [0..1]
+ pncPrepareSleepTimer: TimeValue [0..1]
+ pncSynchronousWakeup: Boolean [0..1]
+ pnResetTime: TimeValue [0..1]
+ sleepModeSupported: Boolean
+ v2xSupported: V2xSupportEnum [0..1]
+ wakeUpOverBusSupported: Boolean

+ecuInstance 0..*

«atpSplitable»

ARElement
DiagnosticEcuInstanceProps
0..* DiagnosticContributionSet
«atpVariation,atpSplitable» + obdSupport: DiagnosticObdSupportEnum [0..1]
+serviceTable

«atpVariation,atpSplitable»

  
+element 0..*
   
 ARElement «enumeration»
DiagnosticCommonElement DiagnosticObdSupportEnum

masterEcu
secondaryEcu
primaryEcu
noObdSupport
+serviceInstance 0..*

DiagnosticServiceInstance

Figure 4.4: Diagnostic Contribution

[TPS_DEXT_01005] DiagnosticContributionSet can exist independently

dThe DiagnosticContributionSet has been modeled as an ARElement so that
its instances can exist independently of the existence of context-providing model-
elements inside a given ARPackage.c(RS_DEXT_00001)
[TPS_DEXT_01005] elaborates on an important aspect that makes the Diagnos-
ticExtract independent of the existence of a context. For example, it would have
been possible to aggregate DiagnosticContributionSet somewhere, e.g. at
System.
This kind of modeling intentionally puts DiagnosticContributionSet on the same
level as e.g. System, as far as model granularity is concerned.

54 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticContributionSet
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticContribution
Note This meta-class represents a root node of a diagnostic extract. It bundles a given set of diagnostic model
elements. The granularity of the DiagonsticContributionSet is arbitrary in order to support the aspect of
decentralized configuration, i.e. different contributors can come up with an own DiagnosticContribution
Set.
Tags:atp.recommendedPackage=DiagnosticContributionSets
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
common DiagnosticCommon 0..1 aggr This attribute represents a collection of diagnostic
Properties Props properties that are shared among the entire Diagnostic
ContributionSet.
Stereotypes: atpSplitable
Tags:atp.Splitkey=commonProperties
element DiagnosticCommon * ref This represents a DiagnosticCommonElement considered
Element in the context of the DiagnosticContributionSet
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=element.diagnosticCommonElement,
element.variationPoint.shortLabel
vh.latestBindingTime=postBuild
serviceTable DiagnosticServiceTable * ref This represents the collection of DiagnosticServiceTables
to be considered in the scope of this Diagnostic
ContributionSet.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=serviceTable.diagnosticServiceTable, service
Table.variationPoint.shortLabel
vh.latestBindingTime=postBuild

Table 4.13: DiagnosticContributionSet

The purpose of the DiagnosticContributionSet is to refer to all Diagnostic-

CommonElements that are relevant in the context of the DiagnosticContribu-
tionSet.
It is not sufficient that a given DiagnosticCommonElement is referenced by another
DiagnosticCommonElement but is not referenced by the same DiagnosticCon-
tributionSet that also references the referencing DiagnosticCommonElement.
[constr_1745] Indirect reference to DiagnosticCommonElement dIf a Diagnos-
ticCommonElement is referenced from within the context of another Diagnostic-
CommonElement and the referencing DiagnosticCommonElement is in turn refer-
enced by a DiagnosticContributionSet in the role element then the referenced
DiagnosticCommonElement shall also be referenced by the same Diagnostic-
ContributionSet.c()
Example: a DiagnosticDataIdentifier that is referenced by a Diagnostic-
DataIdentifierSet that is referenced by a DiagnosticContributionSet shall
also be referenced by that DiagnosticContributionSet. This scenario is depicted
in Figure 4.5.

55 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticContributionSet

element element
DiagnosticCommonElement DiagnosticCommonElement
dataIdentifier
DiagnosticDataIdentifierSet DiagnosticDataIdentifier

Figure 4.5: Visualization of example scenario for the indirect reference to Diagnostic-
CommonElement

4.5 Diagnostic Protocol

[TPS_DEXT_01124] Semantics of meta-class DiagnosticProtocol dThe meta-
class DiagnosticProtocol can be used to describe the usage of different diagnos-
tic protocols as well as their priority.c(RS_DEXT_00059)
Class DiagnosticProtocol
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticContribution
Note This meta-class represents the ability to define a diagnostic protocol.
Tags:atp.recommendedPackage=DiagnosticProtocols
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnostic DiagnosticConnection * ref This represents the collection of applicable Diagnostic
Connection Connections for this DiagnosticProtocol.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=diagnosticConnection.diagnosticConnection,
diagnosticConnection.variationPoint.shortLabel
vh.latestBindingTime=postBuild
priority PositiveInteger 0..1 attr This represents the priority of the diagnostic protocol in
comparison to other diagnostic protocols. Lower numeric
values represent higher protocol priority:
• 0 - Highest protocol priority
• 255 - Lowest protocol priority
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
protocolKind NameToken 0..1 attr This identifies the applicable protocol.
5

56 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticProtocol
sendRespPend Boolean 0..1 attr The purpose of this attribute is to define whether or not
OnTransToBoot the ECU should send a NRC 0x78 (response pending)
before transitioning to the bootloader (in this case the
attribute shall be set to "true") or if the transition shall be
initiated without sending NRC 0x78 (in this case the
attribute shall be set to "false").
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
serviceTable DiagnosticServiceTable 0..1 ref This represents the service table applicable for the given
diagnostic protocol.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=serviceTable.diagnosticServiceTable, service
Table.variationPoint.shortLabel
vh.latestBindingTime=postBuild

Table 4.14: DiagnosticProtocol

FibexElement
EcuInstance

+ comConfigurationGwTimeBase: TimeValue [0..1]

+ comConfigurationRxTimeBase: TimeValue [0..1]
+ comConfigurationTxTimeBase: TimeValue [0..1]
+ comEnableMDTForCyclicTransmission: Boolean [0..1]
+ ethSwitchPortGroupDerivation: Boolean [0..1]
+ pncPrepareSleepTimer: TimeValue [0..1]
+ pncSynchronousWakeup: Boolean [0..1]
+ pnResetTime: TimeValue [0..1]
+ sleepModeSupported: Boolean
+ v2xSupported: V2xSupportEnum [0..1]
+ wakeUpOverBusSupported: Boolean

+ecuInstance 0..1

DiagnosticCommonElement ARElement
+diagnosticConnection
DiagnosticServiceTable DiagnosticConnection
«atpVariation,atpSplitable» 0..*
+ protocolKind: NameToken [0..1]

  
+diagnosticConnection 0..*
   

«atpVariation,atpSplitable»

DiagnosticCommonElement
DiagnosticProtocol

+ protocolKind: NameToken [0..1]

+serviceTable «atpVariation»
«atpVariation,atpSplitable» +
0..1
priority: PositiveInteger [0..1]
+ sendRespPendOnTransToBoot: Boolean [0..1]

+serviceInstance 0..*

DiagnosticCommonElement
DiagnosticServiceInstance

Figure 4.6: Modeling of DiagnosticProtocol

[constr_1794] Existence of attribute DiagnosticProtocol.priority dFor each

DiagnosticProtocol, attribute priority shall exist at the time when the DEXT
is complete.c()
[constr_1795] Existence of attribute DiagnosticProtocol.protocolKind dFor
each DiagnosticProtocol, attribute protocolKind shall exist at the time when
the DEXT is complete.c()

57 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Each DiagnosticProtocol refers to at most one DiagnosticServiceTable and

to a collection of DiagnosticConnections.
Please note that both DiagnosticServiceTable and DiagnosticProtocol have
an attribute named protocolKind.
Class DiagnosticServiceTable
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticContribution
Note This meta-class represents a model of a diagnostic service table, i.e. the UDS services applicable for a
given ECU.
Tags:atp.recommendedPackage=DiagnosticServiceTables
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnostic DiagnosticConnection * ref This represents the DiagnosticConnection that is taken
Connection for handling the data transmission for the enclosing
DiagnosticServiceTable.
It is possible to refer to more than one diagnostic
Connections in order to support more than one diagnostic
tester.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=diagnosticConnection.diagnosticConnection,
diagnosticConnection.variationPoint.shortLabel
vh.latestBindingTime=postBuild
ecuInstance EcuInstance 0..1 ref This represents the applicable EcuInstance for this
DiagnosticServiceTable.
protocolKind NameToken 0..1 attr This identifies the applicable protocol.
serviceInstance DiagnosticService * ref This represents the collection of DiagnosticService
Instance Instances to be considered in the scope of this Diagnostic
ServiceTable,

Table 4.15: DiagnosticServiceTable

[constr_1796] Existence of attribute DiagnosticServiceTable.serviceIn-

stance dFor each DiagnosticServiceTable, attribute serviceInstance shall
exist at the time when the DEXT is complete.c()
[constr_1797] Existence of attribute DiagnosticServiceTable.protocolKind
dFor each DiagnosticServiceTable, attribute protocolKind shall exist at the
time when the DEXT is complete.c()
The attribute DiagnosticServiceTable.protocolKind shall be used to define
the applicability of a DiagnosticServiceTable for a given protocol before the for-
mal definition of the protocol even exists.
In other words, the attribute gives the designer of the DiagnosticServiceTable a
means to express an intention about the usage of the DiagnosticServiceTable.
The attribute DiagnosticServiceTable.protocolKind, on the other hand, is
used to define the actual nature of the DiagnosticProtocol.

58 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

By means of DiagnosticProtocol.serviceTable both “ends” of this aspect are

put together and therefore it is reasonable to express a constraint about the value of
attribute protocolKind.
[constr_1405] Value of DiagnosticProtocol.serviceTable vs. Diagnostic-
ServiceTable.protocolKind dIf the reference DiagnosticProtocol.servic-
eTable exists then the value of DiagnosticProtocol.protocolKind shall be
identical to the value of DiagnosticServiceTable.protocolKind.c()
[TPS_DEXT_01006] The role of DiagnosticServiceTables dThe existence of a
DiagnosticServiceTable creates a formal relation between a collection of Di-
agnosticServiceInstances and the DiagnosticConnection that formalizes a
conduit for specific pairs of diagnostic request and response messages taken to trans-
mit the diagnostic service invocations from a tester to the applicable instance of the
AUTOSAR diagnostic stack and convey the response of the diagnostic stack back to
the tester.
In particular, this means that a DiagnosticServiceTable describes the set of
DiagnosticServiceInstances that are available via DiagnosticConnection
which is finally a request message to address a diagnostic service to an ECU and a
response message to be used by the ECU to respond to the service.c(RS_DEXT_-
00039)
Class DiagnosticConnection
Package M2::AUTOSARTemplates::SystemTemplate::DiagnosticConnection
Note DiagnosticConncection that is used to describe the relationship between several TP connections.
Tags:atp.recommendedPackage=DiagnosticConnections
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
functional TpConnectionIdent * ref Reference to functional request messages.
Request
periodic PduTriggering * ref Reference to UUDT responses.
ResponseUudt
physical TpConnectionIdent 0..1 ref Reference to a physical request message.
Request
response TpConnectionIdent 0..1 ref In the vast majority of cases a response is required.
However, there are also cases where providing the
response is not possible and/or not allowed.
responseOn TpConnectionIdent 0..1 ref Reference to a ROE message.
Event
Table 4.16: DiagnosticConnection

Here is an example of a service table for UDS diagnostics:

$14 - GroupOfDTC: 0xFFFFFF
$19 - Subfunction: $02, Subfunction $06
$22 - DataID: 0x1111, DataID: 0x2222
$2E - DataID: 0x1111, DataID: 0x2222

59 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

$2F - IO-ID:0x3333
[TPS_DEXT_01091] Relation between a DiagnosticServiceTable and one or
more DiagnosticConnections dIn principle, the relation between a Diagnostic-
ServiceTable and one or more DiagnosticConnections can be established in
two possible ways:
• By means of the reference DiagnosticServiceTable.diagnosticConnec-
tion. This way, the concept of protocols and their priorities relative to each other
is not considered.
• By means of the references DiagnosticProtocol.diagnosticConnection
and DiagnosticProtocol.serviceTable. This way, the existence of several
protocols and their priorities is positively considered.
c()
Please note that alternatives mentioned in [TPS_DEXT_01091] may or may not be
handled as alternatives in actual projects. It may be possible that in a first modeling
step protocols are ignored entirely and therefore the respective relations are created
by means of DiagnosticServiceTable.diagnosticConnection.
Later in time and as the project progresses, protocols may become a thing and are con-
sequently introduced in the model. In response to this change, the relation in question
is now created by means of the references DiagnosticProtocol.diagnostic-
Connection and DiagnosticProtocol.serviceTable.
However, the existing relation created by means of the reference DiagnosticSer-
viceTable.diagnosticConnection is not necessarily required to be removed. It
may just as well continue to exist. However, in this case an obvious consistency rule
as described in [constr_1406] applies.
[constr_1406] DiagnosticServiceTable.diagnosticConnection vs. Diag-
nosticProtocol.diagnosticConnection dIf a DiagnosticServiceTable ex-
ists that fulfills the following conditions:
• reference DiagnosticServiceTable.diagnosticConnection exists
• the DiagnosticServiceTable is referenced by means of DiagnosticPro-
tocol.serviceTable
then all of the DiagnosticConnections referenced by means of DiagnosticSer-
viceTable.diagnosticConnection shall also be referenced in the role diagnos-
ticConnection from a DiagnosticProtocol that in turn references the respective
DiagnosticServiceTable in the role DiagnosticProtocol.serviceTable.c()

60 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

+functionalRequest
Referrable ARElement
TpConnection
+ident TpConnectionIdent 0..* DiagnosticConnection

0..1
+response

0..1

FlexrayArTpConnection
+responseOnEvent
+ connectionPrioPdus: Integer [0..1]
0..1

+physicalRequest

J1939TpConnection 0..1

+ broadcast: Boolean
+ bufferRatio: PositiveInteger [0..1]
+ cancellation: Boolean [0..1]
+ dynamicBs: Boolean [0..1]
+ maxBs: PositiveInteger [0..1]
+ maxExpBs: PositiveInteger [0..1]
+ retry: Boolean [0..1]

LinTpConnection

+ dropNotRequestedNad: Boolean [0..1]

+ maxNumberOfRespPendingFrames: PositiveInteger [0..1]
+ p2Max: TimeValue [0..1]
+ p2Timing: TimeValue [0..1]
+ timeoutAs: TimeValue [0..1]
+ timeoutCr: TimeValue [0..1]
+ timeoutCs: TimeValue [0..1]

CanTpConnection

+ addressingFormat: CanTpAddressingFormatType
+ cancellation: Boolean [0..1]
+ maxBlockSize: Integer [0..1]
+ paddingActivation: Boolean
+ taType: NetworkTargetAddressType [0..1]
+ timeoutBr: TimeValue [0..1]
+ timeoutBs: TimeValue [0..1]
+ timeoutCr: TimeValue [0..1]
+ timeoutCs: TimeValue [0..1]

FlexrayTpConnection

+ bandwidthLimitation: Boolean

+periodicResponseUudt 0..*

Identifiable
DoIpTpConnection
+tpSdu PduTriggering

+doIpSourceAddress 1 +doIpTargetAddress 1

Identifiable
DoIpLogicAddress

+ address: Integer

Figure 4.7: Modeling of DiagnosticConnection

4.6 Diagnostic Common Properties

[TPS_DEXT_01007] Common properties of a DiagnosticExtract dThere are
some properties of a DiagnosticExtract that are shared among all elements of the
DiagnosticExtract. These properties are modeled by means of the meta-class
DiagnosticCommonProps.c(RS_DEXT_00001)

61 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

ARElement
DiagnosticContributionSet

«atpSplitable»

+commonProperties 0..1

«atpVariation»
DiagnosticCommonProps

+ agingRequiresTestedCycle: Boolean [0..1]

+ clearDtcLimitation: DiagnosticClearDtcLimitationEnum [0..1]
+ defaultEndianness: ByteOrderEnum [0..1]
+ environmentDataCapture: DiagnosticDataCaptureEnum [0..1]
+ maxNumberOfRequestCorrectlyReceivedResponsePending: PositiveInteger [0..1]
+ occurrenceCounterProcessing: DiagnosticOccurrenceCounterProcessingEnum [0..1]
+ resetConfirmedBitOnOverflow: Boolean [0..1]
+ responseOnAllRequestSids: Boolean [0..1]
+ responseOnSecondDeclinedRequest: Boolean [0..1]
+ securityDelayTimeOnBoot: TimeValue [0..1]
+ statusBitHandlingTestFailedSinceLastClear: DiagnosticStatusBitHandlingTestFailedSinceLastClearEnum [0..1]
+ statusBitStorageTestFailed: Boolean [0..1]

+debounceAlgorithmProps 0..*

«enumeration» Referrable
DiagnosticDebounceBehaviorEnum DiagnosticDebounceAlgorithmProps

freeze + debounceCounterStorage: Boolean [0..1]

reset «atpVariation»
+ debounceBehavior: DiagnosticDebounceBehaviorEnum [0..1]

«enumeration» «enumeration» «enumeration»

DiagnosticMemoryEntryStorageTriggerEnum DiagnosticEventDisplacementStrategyEnum DiagnosticDataCaptureEnum

confirmed full captureSynchronouslyToReporting

fdcThreshold none captureAsynchronouslyToReporting
pending prioOcc
testFailed

«enumeration» «enumeration» «enumeration»

DiagnosticTypeOfDtcSupportedEnum DiagnosticOccurrenceCounterProcessingEnum DiagnosticClearDtcLimitationEnum

iso11992_4 testFailedBit allSupportedDtcs

iso14229_1 confirmedDtcBit clearAllDtcs
iso15031_6
saeJ1939_73
saeJ2012_da

«enumeration»
DiagnosticStatusBitHandlingTestFailedSinceLastClearEnum

statusBitNormal
statusBitAgingAndDisplacement

Figure 4.8: Common Diagnostic Properties

[TPS_DEXT_01008] DiagnosticContributionSet defines the scope for the ap-

plication of the common diagnostic properties dDiagnosticContributionSet
aggregates DiagnosticCommonProps and by this means defines the scope for the
application of the common diagnostic properties.c(RS_DEXT_00001)

62 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class <<atpVariation>> DiagnosticCommonProps

Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticCommonProps
Note This meta-class aggregates a number of common properties that are shared among a diagnostic extract.
Tags:vh.latestBindingTime=codeGenerationTime
Base ARObject
Attribute Type Mult. Kind Note
agingRequires Boolean 0..1 attr Defines whether the aging cycle counter is processed
TestedCycle every aging cycles or else only tested aging cycle are
considered.
If the attribute is set to TRUE: only tested aging cycle are
considered for aging cycle counter.
If the attribute is set to FALSE: aging cycle counter is
processed every aging cycle.
clearDtc DiagnosticClearDtc 0..1 attr Defines the scope of the DEM_ClearDTC Api.
Limitation LimitationEnum
debounce DiagnosticDebounce * aggr Defines the used debounce algorithms relevant in the
AlgorithmProps AlgorithmProps context of the enclosing DiagnosticCommonProps.
Usually, there is a variety of debouncing algorithms to
take into account and therefore the multiplicity of this
aggregation is set to 0..*.
default ByteOrderEnum 0..1 attr Defines the default endianness of the data belonging to a
Endianness DID or RID which is applicable if the DiagnosticData
Element does not define the endianness via the swData
DefProps.baseType attribute.
environment DiagnosticDataCapture 0..1 attr This attribute determines whether the capturing of
DataCapture Enum environment data is done synchronously inside the report
API function or whether the capturing shall be done
asynchronously, i.e. after the report API function already
terminated.
maxNumberOf PositiveInteger 0..1 attr Maximum number of negative responses with response
Request code 0x78 (requestCorrectlyReceived-ResponsePending)
Correctly allowed per request. DCM will send a negative response
Received with response code 0x10 (generalReject), in case the limit
Response value gets reached. Value 0xFF means that no limit
Pending number of NRC 0x78 response apply.
occurrence DiagnosticOccurrence 0..1 attr This attribute defines the consideration of the fault
Counter CounterProcessing confirmation process for the occurrence counter.
Processing Enum
resetConfirmed Boolean 0..1 attr This attribute defines, whether the confirmed bit is reset
BitOnOverflow or not while an event memory entry will be displaced.
responseOnAll Boolean 0..1 attr If set to FALSE the DCM will not respond to diagnostic
RequestSids request that contains a service ID which is in the range
from 0x40 to 0x7F or in the range from 0xC0 to 0xFF
(Response IDs).
responseOn Boolean 0..1 attr Defines the reaction upon a second request (ClientB) that
Second can not be processed (e.g. due to priority assessment).
Declined
TRUE: when the second request (Client B) can not be
Request
processed, it shall be answered with NRC21 BusyRepeat
Request.
FALSE: when the second request (Client B) can not be
processed, it shall not be responded.
securityDelay TimeValue 0..1 attr Start delay timer on power on in seconds.
TimeOnBoot
This delay indicates the time at ECU boot power-on time
where the Dcm remains in the default session and does
not accept a security access.
5

63 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpVariation>> DiagnosticCommonProps
statusBit DiagnosticStatusBit 0..1 attr This attribute defines, whether the aging and
HandlingTest HandlingTestFailed displacement mechanism shall be applied to the "Test
FailedSinceLast SinceLastClearEnum FailedSinceLastClear" status bits.
Clear
statusBit Boolean 0..1 attr This parameter is used to activate/deactivate the
StorageTest permanent storage of the "TestFailed" status bits.
Failed
true: storage activated
false: storage deactivated

Table 4.17: DiagnosticCommonProps

Enumeration DiagnosticMemoryEntryStorageTriggerEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note Trigger types to allocate an event memory entry.
Literal Description
confirmed Status information of UDS DTC status bit 3
Tags:atp.EnumerationLiteralIndex=0
fdcThreshold Threshold to allocate an event memory entry and to capture the Freeze Frame.
Tags:atp.EnumerationLiteralIndex=1
pending Status information of UDS DTC status bit 2.
Tags:atp.EnumerationLiteralIndex=2
testFailed Status information of UDS DTC status bit 0.
Tags:atp.EnumerationLiteralIndex=3

Table 4.18: DiagnosticMemoryEntryStorageTriggerEnum

Enumeration DiagnosticDataCaptureEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticCommonProps
Note Data triggering types
Literal Description
capture This represents the intention to capture the environment data asynchronously after the actual capture
AsynchronouslyTo API function terminated.
Reporting
Tags:atp.EnumerationLiteralIndex=0
capture This represents the intention to capture the environment data synchronously within the capture API
SynchronouslyTo function.
Reporting
Tags:atp.EnumerationLiteralIndex=1

Table 4.19: DiagnosticDataCaptureEnum

Enumeration DiagnosticClearDtcLimitationEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticCommonProps
Note Scope of the DEM_ClearDTC Api.
Literal Description
5

64 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticClearDtcLimitationEnum
allSupportedDtcs DEM_ClearDtc API accepts all supported DTC values.
Tags:atp.EnumerationLiteralIndex=0
clearAllDtcs DEM_ClearDtc API accepts ClearAllDTCs only.
Tags:atp.EnumerationLiteralIndex=1

Table 4.20: DiagnosticClearDtcLimitationEnum

Enumeration DiagnosticEventDisplacementStrategyEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note Defines the displacement strategy.
Literal Description
full Event memory entry displacement is enabled, by consideration of priority active/passive status, and
occurrence.
Tags:atp.EnumerationLiteralIndex=0
none Event memory entry displacement is disabled.
Tags:atp.EnumerationLiteralIndex=1
prioOcc Event memory entry displacement is enabled, by consideration of priority and occurrence (but without
active/passive status).
Tags:atp.EnumerationLiteralIndex=2

Table 4.21: DiagnosticEventDisplacementStrategyEnum

Enumeration DiagnosticOccurrenceCounterProcessingEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticCommonProps
Note The occurrence counter triggering types.
Literal Description
confirmedDtcBit The occurrence counter is triggered by the TestFailed bit if the fault confirmation was successful
(ConfirmedDTC bit is set).
Tags:atp.EnumerationLiteralIndex=0
testFailedBit The occurrence counter is only triggered by the TestFailed bit (and the fault confirmation is not
considered).
Tags:atp.EnumerationLiteralIndex=1

Table 4.22: DiagnosticOccurrenceCounterProcessingEnum

Enumeration DiagnosticTypeOfDtcSupportedEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note Supported Dtc Types
Literal Description
iso11992_4 ISO11992-4 DTC format
Tags:atp.EnumerationLiteralIndex=0
iso14229_1 ISO14229-1 DTC format (3 byte format)
Tags:atp.EnumerationLiteralIndex=1
5

65 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticTypeOfDtcSupportedEnum
iso15031_6 ISO15031-6 DTC format (2 byte format)
Tags:atp.EnumerationLiteralIndex=2
saeJ1939_73 SAEJ1939-73 DTC format
Tags:atp.EnumerationLiteralIndex=3
saeJ2012_da SAE_J2012-DA_DTCFormat_00 (3 byte format)
Tags:atp.EnumerationLiteralIndex=4

Table 4.23: DiagnosticTypeOfDtcSupportedEnum

66 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

5 Diagnostic Services

5.1 Introduction
The meta-model for the diagnostic services according to AUTOSAR, to a large degree,
takes over aspects of the description of diagnostic services according to the definition
of Unified Diagnostic Services (UDS) as of ISO 14229 [16].

5.2 Service Instance vs. Service Class

When it comes to diagnostic services, the meta-model distinguishes between the con-
cept of a diagnostic service instance vs. the concept of a diagnostic service class.
As the terminology suggests, the diagnostic service instance (formalized as Diagnos-
ticServiceInstance) implements a concrete use of a diagnostic service in a given
context whereas purpose of the diagnostic service class (formalized as Diagnostic-
ServiceClass) is to provide properties that are shared among all existing diagnostic
service instances in the model.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticServiceInstance +accessPermission DiagnosticAccessPermission

0..1

DiagnosticCommonElement
+serviceClass
DiagnosticServiceClass
«atpAbstract» 0..1

DiagnosticCommonElement
DiagnosticCustomServiceClass

+ customServiceId: PositiveInteger [0..1]

Figure 5.1: Common service elements

[constr_1329] Existence of concrete sub-classes of DiagnosticServiceClass

in the context created by a DiagnosticContributionSet dOne of the following
mutually exclusive conditions shall apply for the existence of any concrete sub-class
of DiagnosticServiceClass in the context created by a DiagnosticContribu-
tionSet:
• The subclass of DiagnosticServiceClass shall only appear once in the con-
text created by a DiagnosticContributionSet
• If the subclass of DiagnosticServiceClass appears multiple times in the
context created by a DiagnosticContributionSet then all instances shall
have identical values for all of their attributes.
In case of aggregations the number of aggregated elements shall be identical and
the values of primitive attributes of aggregated elements shall again be identical.

67 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

c()
The background of [constr_1329] is obviously related to the semantics of Diagnos-
ticServiceClass which is to define model attributes that are shared among all
DiagnosticServiceInstances.
This would not be possible if more that one DiagnosticServiceClass with a di-
verging set of attribute values exists.
Class DiagnosticServiceClass (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommonService
Note This meta-class provides the ability to define common properties that are shared among all instances of
sub-classes of DiagnosticServiceInstance.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticClearDiagnosticInformationClass, DiagnosticClearResetEmissionRelatedInfoClass, Diagnostic
ComControlClass, DiagnosticControlDTCSettingClass, DiagnosticCustomServiceClass, DiagnosticData
TransferClass, DiagnosticDynamicallyDefineDataIdentifierClass, DiagnosticEcuResetClass, DiagnosticIo
ControlClass, DiagnosticReadDTCInformationClass, DiagnosticReadDataByIdentifierClass, Diagnostic
ReadDataByPeriodicIDClass, DiagnosticReadMemoryByAddressClass, DiagnosticReadScalingDataBy
IdentifierClass, DiagnosticRequestControlOfOnBoardDeviceClass, DiagnosticRequestCurrentPowertrain
DataClass, DiagnosticRequestDownloadClass, DiagnosticRequestEmissionRelatedDTCClass,
DiagnosticRequestEmissionRelatedDTCPermanentStatusClass, DiagnosticRequestFileTransferClass,
DiagnosticRequestOnBoardMonitoringTestResultsClass, DiagnosticRequestPowertrainFreezeFrame
DataClass, DiagnosticRequestUploadClass, DiagnosticRequestVehicleInfoClass, DiagnosticResponse
OnEventClass, DiagnosticRoutineControlClass, DiagnosticSecurityAccessClass, DiagnosticSession
ControlClass, DiagnosticTransferExitClass, DiagnosticWriteDataByIdentifierClass, DiagnosticWrite
MemoryByAddressClass
Attribute Type Mult. Kind Note
– – – – –
Table 5.1: DiagnosticServiceClass

Class DiagnosticServiceInstance (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommonService
Note This represents a concrete instance of a diagnostic service.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticClearDiagnosticInformation, DiagnosticClearResetEmissionRelatedInfo, DiagnosticCom
Control, DiagnosticControlDTCSetting, DiagnosticCustomServiceInstance, DiagnosticDataByIdentifier ,
DiagnosticDynamicallyDefineDataIdentifier, DiagnosticEcuReset, DiagnosticIOControl, Diagnostic
MemoryByAddress, DiagnosticReadDTCInformation, DiagnosticReadDataByPeriodicID, Diagnostic
RequestControlOfOnBoardDevice, DiagnosticRequestCurrentPowertrainData, DiagnosticRequest
EmissionRelatedDTC, DiagnosticRequestEmissionRelatedDTCPermanentStatus, DiagnosticRequestFile
Transfer, DiagnosticRequestOnBoardMonitoringTestResults, DiagnosticRequestPowertrainFreezeFrame
Data, DiagnosticRequestVehicleInfo, DiagnosticResponseOnEvent, DiagnosticRoutineControl,
DiagnosticSecurityAccess, DiagnosticSessionControl
Attribute Type Mult. Kind Note
access DiagnosticAccess 0..1 ref This represents the collection of DiagnosticAccess
Permission Permission Permissions that allow for the execution of the referencing
DiagnosticServiceInstance..
5

68 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticServiceInstance (abstract)
serviceClass DiagnosticServiceClass 0..1 ref This represents the corresponding "class", i.e. this
meta-class provides properties that are shared among all
instances of applicable sub-classes of DiagnosticService
Instance.
The subclasses that affected by this pattern implement
references to the applicable "class"-role that substantiate
this abstract reference.
Stereotypes: atpAbstract

Table 5.2: DiagnosticServiceInstance

[constr_1798] Existence of DiagnosticServiceInstance.serviceClass dFor

each subclass of DiagnosticServiceInstance, a reference with the abstract role
serviceClass shall exist at the time when the DEXT is complete to a matching
subclass of DiagnosticServiceClass.
This rule applies unless a rule for a specific combination of matching sub-classes of
DiagnosticServiceInstance and DiagnosticServiceClass exists.c()
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass DiagnosticServiceClass
«atpAbstract» 0..1

DiagnosticCommonElement
DiagnosticCustomServiceInstance
+customServiceClass DiagnosticCustomServiceClass

0..1 + customServiceId: PositiveInteger [0..1]

{redefines
serviceClass}

Figure 5.2: Modeling of custom service instance

[TPS_DEXT_01147] Support for custom service instance dMeta-class Diagnos-

ticCustomServiceInstance can be used to define the existence of an instance of
a custom diagnostic service.c(RS_DEXT_00047)
Custom services can obviously not be configured using standardized attributes, but
there is the ability to use Sdg in the context of adminData for this purpose.
There is no obligation for a given tool to be able to properly process the definition of
the custom service instance.
Class DiagnosticCustomServiceInstance
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CustomServiceInstance
Note This meta-class has the ability to define an instance of a custom diagnostic service.
Tags:atp.recommendedPackage=DiagnosticCustomInstances
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
5

69 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticCustomServiceInstance
Attribute Type Mult. Kind Note
customService DiagnosticCustom 0..1 ref Reference to the corresponding DiagnosticCustom
Class ServiceClass ServiceClass.

Table 5.3: DiagnosticCustomServiceInstance

[constr_1330] Custom service identifier shall not overlap with standardized ser-
vice identifiers dThe value of the attribute customServiceId shall not be set to
any of the values reserved for standardized service identifiers as defined by the ISO
14229-1, see [16].c()
Class DiagnosticCustomServiceClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommonService
Note This represents the ability to define a custom diagnostic service class and assign an ID to it. Further
configuration is not foreseen from the point of view of the diagnostic extract and consequently needs to
be done on the level of ECUC.
Tags:atp.recommendedPackage=DiagnosticCustomServiceClasses
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
customService PositiveInteger 0..1 attr This attribute may only be used for the definition of
Id custom services. The values shall not overlap with
existing standardized service IDs.

Table 5.4: DiagnosticCustomServiceClass

5.3 Access Permission, Session, Security Level

This chapter discusses a set of meta-classes that have been created to represent the
concept of an access permission used in the context of the Dcm.

5.3.1 Introduction to Access Permission

The DiagnosticAccessPermission is used to describe the ability (or the lack

thereof) to execute a diagnostic service depending on the referenced Diagnostic-
SecurityLevel and DiagnosticSession (see Figure 5.3).
At runtime, DiagnosticSessions are used to create a context for the execution of
diagnostic functionality. Servers usually support a variety of different Diagnostic-
Sessions. It is possible to switch between DiagnosticSessions at runtime.

70 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement
DiagnosticEnvironmentalCondition

+environmentalCondition 0..1

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticSession
+diagnosticSession
+ id: PositiveInteger [0..1]
0..* + jumpToBootLoader: DiagnosticJumpToBootLoaderEnum [0..1]
+ p2ServerMax: TimeValue [0..1]
+ p2StarServerMax: TimeValue [0..1]

+securityLevel 0..*

DiagnosticCommonElement «enumeration»
DiagnosticSecurityLevel DiagnosticJumpToBootLoaderEnum

+ accessDataRecordSize: PositiveInteger [0..1] noBoot

+ keySize: PositiveInteger [0..1] oemBoot
+ numFailedSecurityAccess: PositiveInteger [0..1] systemSupplierBoot
+ securityDelayTime: TimeValue [0..1] oemBootRespApp
+ seedSize: PositiveInteger [0..1] systemSupplierBootRespApp

Figure 5.3: Common model elements relevant for the Dcm

[TPS_DEXT_01139] Semantics of the references from DiagnosticAccessPer-

mission dThe semantics of the references from DiagnosticAccessPermission
to
• DiagnosticSession in the role diagnosticSession
• DiagnosticSecurityLevel in the role securityLevel
• DiagnosticEnvironmentalCondition in the role environmentalCondi-
tion
in terms of how access permission is granted is subject to the specification of the
Dcm [10].c(RS_DEXT_00040)
[TPS_DEXT_01011] Semantics of DiagnosticSession.id dThe value of the at-
tribute DiagnosticSession.id has a given semantics according to ISO 14229-
1 [16]. For the sake of completeness, the dedicated values of DiagnosticSession.
id are:
0x01 This represents the default session. This session has a specific semantics in the
context of diagnostics communication such that e.g. any diagnostic service that
is supposed to execute in the default session cannot require any reference to a
DiagnosticSecurityLevel.
0x02 This represents the programming session.
0x03 This represents the extended diagnostic session.
0x04 This represents the safety system diagnostic session.
The value range 0x40 .. 0x5F is reserved for manufacturer-specific use.c(RS_DEXT_-
00040)

71 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticSecurityLevel
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm
Note This meta-class represents the ability to define a security level considered for diagnostic purposes.
Tags:atp.recommendedPackage=DiagnosticSecurityLevels
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
accessData PositiveInteger 0..1 attr This represents the size of the AccessDataRecord used
RecordSize in GetSeed. Unit:byte.
keySize PositiveInteger 0..1 attr This represents the size of the security key. Unit: byte.
numFailed PositiveInteger 0..1 attr This represents the number of failed security accesses
SecurityAccess after which the delay time is activated.
securityDelay TimeValue 0..1 attr This represents the delay time after a failed security
Time access. Unit: second.
seedSize PositiveInteger 0..1 attr This represents the size of the security seed. Unit: byte.

Table 5.5: DiagnosticSecurityLevel

[TPS_DEXT_01012] Rationale for the modeling of the multiplicity of Diag-

nosticAccessPermission.securityLevel dThe multiplicity of DiagnosticAc-
cessPermission.securityLevel has been set to 0..* with the following motivation:
• The DiagnosticSession where the attribute DiagnosticSession.id is set
to 0x01 shall not be associated with a DiagnosticSecurityLevel.
• There are no associated DiagnosticSecurityLevels required. As a conse-
quence, the execution of the DiagnosticServiceInstance that references
the given DiagnosticAccessPermission is always possible.
c(RS_DEXT_00041, RS_DEXT_00042)
[TPS_DEXT_01070] Description of textually semi-formal formulated pre- and run-
conditions for the validity of DiagnosticAccessPermission dAUTOSAR sup-
ports the description of textually formulated semi-formal pre- and run-conditions for
the validity of DiagnosticAccessPermission.
This can be done by means of the attribute DiagnosticAccessPermission.in-
troduction.structuredReq.c()
For more details regarding the modeling of the semi-formal text please refer to Fig-
ure 4.3. An example of how the definition of pre- and run-conditions may look like in
ARXML is sketched in listing 5.1.
To make this approach work it is important to standardize possible values of the at-
tribute category such that the semi-formal semantics of the definition of pre- and
run-conditions is protected by regulation of the AUTOSAR standard.
[TPS_DEXT_01071] Standardized values of DiagnosticAccessPermission.
introduction.structuredReq dThe following possible values of Diagnos-
ticAccessPermission.introduction.structuredReq are standardized by
AUTOSAR:

72 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• DIAG_ACCESS_PERM_PRE_COND: this value describes the pre-condition of

the corresponding DiagnosticAccessPermission.
• DIAG_ACCESS_PERM_RUN_COND: this value describes the run-condition of
the corresponding DiagnosticAccessPermission.
c(RS_DEXT_00041, RS_DEXT_00045)
Listing 5.1: Example for the definition of pre- and run-conditions for DiagnosticAc-
cessPermission
<DIAGNOSTIC-ACCESS-PERMISSION>
<SHORT-NAME>exampleAccessPermission</SHORT-NAME>
<INTRODUCTION>
<STRUCTURED-REQ>
<SHORT-NAME>precondition</SHORT-NAME>
<CATEGORY>DIAG_ACCESS_PERM_PRE_COND</CATEGORY>
<DESCRIPTION>
<P>
<L-1 L="EN">This is a textual description of a pre-
condition</L-1>
</P>
</DESCRIPTION>
</STRUCTURED-REQ>
<STRUCTURED-REQ>
<SHORT-NAME>runcondition</SHORT-NAME>
<CATEGORY>DIAG_ACCESS_PERM_RUN_COND</CATEGORY>
<DESCRIPTION>
<P>
<L-1 L="EN">This is a textual description of a run-
condition</L-1>
</P>
</DESCRIPTION>
</STRUCTURED-REQ>
</INTRODUCTION>
<DIAGNOSTIC-SESSION-REFS>
<DIAGNOSTIC-SESSION-REF DEST="DIAGNOSTIC-SESSION">/AUTOSAR/
UseCase_230/ExampleSession</DIAGNOSTIC-SESSION-REF>
</DIAGNOSTIC-SESSION-REFS>
<SECURITY-LEVEL-REFS>
<SECURITY-LEVEL-REF DEST="DIAGNOSTIC-SECURITY-LEVEL">/AUTOSAR/
UseCase_230/ExampleSecurityLevel</SECURITY-LEVEL-REF>
</SECURITY-LEVEL-REFS>
</DIAGNOSTIC-ACCESS-PERMISSION>

[constr_1419] Value of DiagnosticSecurityLevel.accessDataRecordSize

dIf the attribute DiagnosticSecurityLevel.accessDataRecordSize exists then
its value shall be greater than zero.c()

73 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticAccessPermission
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm
Note This represents the specification of whether a given service can be accessed according to the existence
of meta-classes referenced by a particular DiagnosticAccessPermission.
In other words, this meta-class acts as a mapping element between several (otherwise unrelated) pieces
of information that are put into context for the purpose of checking for access rights.
Tags:atp.recommendedPackage=DiagnosticAccessPermissions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnostic DiagnosticSession * ref This represents the associated DiagnosticSessions
Session
environmental Diagnostic 0..1 ref This represents the environmental conditions associated
Condition EnvironmentalCondition with the access permission.
securityLevel DiagnosticSecurityLevel * ref This represents the associated DiagnosticSecurityLevels

Table 5.6: DiagnosticAccessPermission

Class DiagnosticSession
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm
Note This meta-class represents the ability to define a diagnostic session.
Tags:atp.recommendedPackage=DiagnosticSessions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
id PositiveInteger 0..1 attr This is the numerical identifier used to identify the
DiagnosticSession in the scope of diagnostic workflow
jumpToBoot DiagnosticJumpToBoot 0..1 attr This attribute represents the ability to define whether this
Loader LoaderEnum diagnostic session allows to jump to Bootloader (OEM
Bootloader or System Supplier Bootloader).
If this diagnostic session doesn’t allow to jump to
Bootloader the value JumpToBootLoaderEnum.noBoot
shall be chosen.
p2ServerMax TimeValue 0..1 attr This is the session value for P2ServerMax in seconds
(per Session Control).
The AUTOSAR configuration standard is to use SI units,
so this parameter is defined as a float value in seconds.
p2StarServer TimeValue 0..1 attr This is the session value for P2*ServerMax in seconds
Max (per Session Control).
The AUTOSAR configuration standard is to use SI units,
so this parameter is defined as a float value in seconds.

Table 5.7: DiagnosticSession

Enumeration DiagnosticJumpToBootLoaderEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm
Note This enumeration contains the options for jumping to a boot loader.
Literal Description
5

74 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticJumpToBootLoaderEnum
noBoot This diagnostic session doesn’t allow to jump to Bootloader.
Tags:atp.EnumerationLiteralIndex=0
oemBoot This diagnostic session allows to jump to OEM Bootloader. In this case the bootloader send the final
response.
Tags:atp.EnumerationLiteralIndex=1
oemBootRespApp This diagnostic session allows to jump to OEM Bootloader and application sends final response.
Tags:atp.EnumerationLiteralIndex=3
systemSupplierBoot This diagnostic session allows to jump to System Supplier Bootloader. In this case the bootloader
send the final response.
Tags:atp.EnumerationLiteralIndex=2
systemSupplierBoot This diagnostic session allows to jump to System Supplier Bootloader and application sends final
RespApp response.
Tags:atp.EnumerationLiteralIndex=4

Table 5.8: DiagnosticJumpToBootLoaderEnum

5.4 Environmental Conditions for the Execution of Diagnostic Ser-

vices
In some cases, diagnostic functionality can only be executed if the vehicle is in a (safe)
state that allows for the respective diagnostics function. For example, one such condi-
tion is that the vehicle is not driving, i.e. vehicle speed == 0.
The meta-class DiagnosticEnvironmentalCondition formalizes the idea of a
condition which is evaluated during runtime of the ECU by looking at “environmental”
states (such as the mentioned vehicle speed).
DiagnosticEnvironmentalConditions are based on the active modes in the ap-
plication software or basic software or by comparison of DiagnosticDataElements
with constant values. Atomic conditions can be combined by logical operations to form
more complex conditions.
Please note that it is possible to create a nested hierarchy (of arbitrary depth) of Di-
agnosticEnvConditionFormula. This modeling is supported by the fact that Di-
agnosticEnvConditionFormula inherits from and, at the same time, aggregates
DiagnosticEnvConditionFormulaPart.

75 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement
DiagnosticEnvironmentalCondition

+modeElement 0..* +formula 0..1

Referrable «enumeration» DiagnosticEnvConditionFormula

DiagnosticEnvModeElement DiagnosticLogicalOperatorEnum
+ nrcValue: PositiveInteger [0..1]
logicalAnd + op: DiagnosticLogicalOperatorEnum [0..1]
logicalOr

0..1 +modeElement

+part 0..* {ordered}

DiagnosticEnvConditionFormulaPart

DiagnosticEnvCompareCondition

+ compareType: DiagnosticCompareTypeEnum

DiagnosticEnvModeCondition DiagnosticEnvDataCondition

«enumeration»
DiagnosticCompareTypeEnum +compareValue 0..1 +dataElement
0..1
isEqual Identifiable
ValueSpecification
isNotEqual DiagnosticDataElement
isLessThan + shortLabel: Identifier [0..1]
isLessOrEqual + arraySizeSemantics: ArraySizeSemanticsEnum [0..1]
isGreaterThan + maxNumberOfElements: PositiveInteger [0..1]
isGreaterOrEqual + scalingInfoSize: PositiveInteger [0..1]

Figure 5.4: Formal modeling of the consideration of environmental conditions

Class DiagnosticEnvironmentalCondition
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note The meta-class DiagnosticEnvironmentalCondition formalizes the idea of a condition which is evaluated
during runtime of the ECU by looking at "environmental" states (e.g. one such condition is that the
vehicle is not driving, i.e. vehicle speed == 0).
Tags:atp.recommendedPackage=DiagnosticEnvironmentalConditions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
formula DiagnosticEnvCondition 0..1 aggr This attribute represents the formula part of the
Formula DiagnosticEnvironmentalCondition.
modeElement DiagnosticEnvMode * aggr This aggregation contains a representation of Mode
Element Declarations in the context of a DiagnosticEnvironmental
Condition.

Table 5.9: DiagnosticEnvironmentalCondition

[constr_1799] Existence of DiagnosticEnvironmentalCondition.formula

dFor each DiagnosticEnvironmentalCondition, the aggregation of Diagnos-
ticEnvConditionFormula in the role formula shall exist at the time when the
DEXT is complete.c()

76 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

5.4.1 Environmental Condition Formula

The core part of a DiagnosticEnvironmentalCondition is the DiagnosticEn-

vConditionFormula.
Class DiagnosticEnvConditionFormula
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note A DiagnosticEnvConditionFormula embodies the computation instruction that is to be evaluated at
runtime to determine if the DiagnosticEnvironmentalCondition is currently present (i.e. the formula is
evaluated to true) or not (otherwise). The formula itself consists of parts which are combined by the
logical operations specified by DiagnosticEnvConditionFormula.op.
If a diagnostic functionality cannot be executed because an environmental condition fails then the
diagnostic stack shall send a negative response code (NRC) back to the client. The value of the NRC is
directly related to the specific formula and is therefore formalized in the attribute DiagnosticEnvCondition
Formula.nrcValue.
Base ARObject, DiagnosticEnvConditionFormulaPart
Attribute Type Mult. Kind Note
nrcValue PositiveInteger 0..1 attr This attribute represents the concrete NRC value that
shall be returned if the condition fails.
op DiagnosticLogical 0..1 attr This attribute represents the concrete operator
OperatorEnum (supported operators: and, or) of the condition formula.
part (ordered) DiagnosticEnvCondition * aggr This aggregation represents the collection of formula
FormulaPart parts that can be combined by logical operators.

Table 5.10: DiagnosticEnvConditionFormula

[constr_1800] Existence of DiagnosticEnvConditionFormula.op dFor each

DiagnosticEnvConditionFormula, that attribute op shall exist at the time when
the DEXT is complete.c()
Enumeration DiagnosticLogicalOperatorEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note Logical AND and OR operation (&&, ||)
Literal Description
logicalAnd Logical AND
Tags:atp.EnumerationLiteralIndex=0
logicalOr Logical OR
Tags:atp.EnumerationLiteralIndex=1

Table 5.11: DiagnosticLogicalOperatorEnum

[TPS_DEXT_01113] Evaluation of a DiagnosticEnvConditionFormula dA Di-

agnosticEnvConditionFormula embodies the computation instruction that is to
be evaluated at runtime to determine if the DiagnosticEnvironmentalCondition
is currently present (i.e. the formula is evaluated to true) or not (otherwise).
The DiagnosticEnvConditionFormula itself consists of parts which are com-
bined by the logical operations represented by the attribute op.c(RS_DEXT_00079)

77 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEnvConditionFormulaPart (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note A DiagnosticEnvConditionFormulaPart can either be a atomic condition, e.g. a DiagnosticEnvCompare
Condition, or a DiagnosticEnvConditionFormula, again, which allows arbitrary nesting.
Base ARObject
Subclasses DiagnosticEnvCompareCondition, DiagnosticEnvConditionFormula
Attribute Type Mult. Kind Note
– – – – –
Table 5.12: DiagnosticEnvConditionFormulaPart

[TPS_DEXT_01114] DiagnosticEnvConditionFormula that has no parts dA

DiagnosticEnvConditionFormula that has no parts shall be evaluated to false.
This rule shall apply independently of the value of DiagnosticEnvConditionFor-
mula.op.c(RS_DEXT_00079)
[TPS_DEXT_01115] DiagnosticEnvConditionFormula that has one part dA
DiagnosticEnvConditionFormula that has one part shall be evaluated to the
evaluation result of this part. This rule shall apply independently of the value of Diag-
nosticEnvConditionFormula.op.c(RS_DEXT_00079)
[TPS_DEXT_01116] DiagnosticEnvConditionFormula that has more than one
part dThe evaluation result of a DiagnosticEnvConditionFormula with more
than one part shall be calculated by combining the results of the parts with the
logical Operation specified by DiagnosticEnvConditionFormula.op.
The evaluation shall be done in a “short-cut” manner, i.e. following the rules for the
evaluation of the logical operators in C.
The consequences of this approach are:
• The parts shall be evaluated in the specified order starting at the first element.
This is why the aggregation of part is decorated by the ordered qualifier.
• after the evaluation of each part a check shall be executed if it is still possible
that the evaluation of the remaining parts (to true or false) could change the
overall result.
• As soon as a change of the overall result is no longer possible, i.e. any of the
following conditions evaluates to false:
– there are no parts left
– the current part was evaluated to false and DiagnosticEnvCon-
ditionFormula.op == DiagnosticLogicalOperatorEnum.logica-
lAnd
– the current part was evaluated to true and DiagnosticEnvCondi-
tionFormula.op == DiagnosticLogicalOperatorEnum.logicalOr
the evaluation of the parts shall be finalized and the evaluation result of the
current part shall be considered the overall evaluation result of the formula.

78 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Regarding the strategy for returning NRC values please refer to the specification
of the SWS Dcm [10].
c(RS_DEXT_00079)
[TPS_DEXT_01117] Semantics of DiagnosticEnvConditionFormula.nrc-
Value dIf a diagnostic functionality cannot be executed because an environmental
condition fails, i.e. the formula is evaluated to false, then the diagnostic stack shall
send an optional negative response code (NRC) back to the client (if it is present).
If no value for NRC is defined then a pre-defined NRC value as defined in the SWS
Dcm [10] will be sent back. The value of the NRC is directly related to the specific
DiagnosticEnvConditionFormula and is therefore formalized in the attribute Di-
agnosticEnvConditionFormula.nrcValue.c(RS_DEXT_00079)
[constr_1464] Allowed value range of DiagnosticEnvConditionFormula.nrc-
Value dThe value of attribute DiagnosticEnvConditionFormula.nrcValue shall
be limited to the interval [1..255].c()
The rationale for the existence of [constr_1464] is provided by ISO 14229-1 [16].

5.4.2 Atomic Conditions

Atomic conditions in the context of a DiagnosticEnvConditionFormula are de-

scribed by means of meta-class DiagnosticEnvCompareConditions. The formu-
lation of DiagnosticEnvCompareConditions is based on the idea of a comparison
at runtime of some variable data with a constant value.
The actual type of the comparison (==, !=, <, <=, ...) is specified by means of the
attribute DiagnosticEnvCompareCondition.compareType.
Class DiagnosticEnvCompareCondition (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note DiagnosticCompareConditions are atomic conditions. They are based on the idea of a comparison at
runtime of some variable data with something constant. The type of the comparison (==, !=, <, <=, ...) is
specified in DiagnosticCompareCondition.compareType.
Base ARObject, DiagnosticEnvConditionFormulaPart
Subclasses DiagnosticEnvDataCondition, DiagnosticEnvModeCondition
Attribute Type Mult. Kind Note
compareType DiagnosticCompare 1 attr This attributes represents the concrete type of the
TypeEnum comparison.

Table 5.13: DiagnosticEnvCompareCondition

[constr_1801] Existence of DiagnosticEnvCompareCondition.compareType

dFor each DiagnosticEnvCompareCondition, that attribute compareType shall
exist at the time when the DEXT is complete.c()

79 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Enumeration DiagnosticCompareTypeEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note Enumeration for the type of a comparison of values usually expressed by the following operators: ==,
!=, <, <=, >, >=
Literal Description
isEqual equal
Tags:atp.EnumerationLiteralIndex=0
isGreaterOrEqual greater than or equal
Tags:atp.EnumerationLiteralIndex=5
isGreaterThan greater than
Tags:atp.EnumerationLiteralIndex=4
isLessOrEqual less than or equal
Tags:atp.EnumerationLiteralIndex=3
isLessThan less than
Tags:atp.EnumerationLiteralIndex=2
isNotEqual not equal
Tags:atp.EnumerationLiteralIndex=1

Table 5.14: DiagnosticCompareTypeEnum

DiagnosticEnvCompareCondition is an abstract meta-class that acts as a base

class for two concrete meta-classes designed to handle different operand types.
The specific sub-classes (the details are explained in sections 5.4.2.1 and 5.4.2.2) of
DiagnosticEnvCompareCondition support a different set of attributes of Diag-
nosticCompareTypeEnum for setting the value of attribute compareType.

5.4.2.1 Data Condition

[TPS_DEXT_01118] Semantics of DiagnosticEnvDataCondition dThe meta-

class DiagnosticEnvDataCondition represents an atomic condition that com-
pares the current value of the referenced DiagnosticDataElement with a constant
value defined by the ValueSpecification aggregated in the role compareValue.c
(RS_DEXT_00079)
[constr_1465] Allowed values of compareType in the context of a Diagnosti-
cEnvDataCondition dWithin the context of a DiagnosticEnvDataCondition all
values of DiagnosticCompareTypeEnum are supported for the inherited attribute
compareType.c()

80 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEnvDataCondition
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note A DiagnosticEnvDataCondition is an atomic condition that compares the current value of the referenced
DiagnosticDataElement with a constant value defined by the ValueSpecification. All compareTypes are
supported.
Base ARObject, DiagnosticEnvCompareCondition, DiagnosticEnvConditionFormulaPart
Attribute Type Mult. Kind Note
compareValue ValueSpecification 0..1 aggr This attribute represents a fixed compare value taken to
evaluate the compare condition.
dataElement DiagnosticDataElement 0..1 ref This reference represents the related diagnostic data
element.
Table 5.15: DiagnosticEnvDataCondition

[constr_1802] Existence of DiagnosticEnvDataCondition.compareValue

dFor each DiagnosticEnvDataCondition, that attribute compareValue shall ex-
ist at the time when the DEXT is complete.c()
[constr_1803] Existence of DiagnosticEnvDataCondition.dataElement dFor
each DiagnosticEnvDataCondition, that attribute dataElement shall exist at
the time when the DEXT is complete.c()

5.4.2.2 Mode Condition

[TPS_DEXT_01119] Semantics of DiagnosticEnvModeCondition dThe meta-

class DiagnosticEnvModeCondition represents an atomic condition that com-
pares the current value of the referenced ModeDeclarationGroupPrototype with
the value of a ModeDeclaration taken as the reference value.c(RS_DEXT_00079)
The concrete modeling of this aspect is sketched in Figure D.4.
Please note that the ModeDeclarationGroupPrototype as well as the applicable
ModeDeclaration are both referenced in the concrete modeling of the attribute
DiagnosticEnvSwcModeElement.mode.
The idea behind this modeling approach (for more information, please refer to Figure
D.4) is that the ModeDeclaration can only be a member of the specific ModeDec-
larationGroup taken to type the respective ModeDeclarationGroupPrototype
anyway.
Admittedly, this relation could be expressed by means of two references and a formal
constraint or it could be expressed by way of a single reference that’s implying an
interpreting of the model in a specific way. AUTOSAR opts for the latter alternative,
which is detailed by [TPS_DEXT_01120].

81 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Referrable
DiagnosticEnvModeElement

DiagnosticEnvSwcModeElement DiagnosticEnvBswModeElement

«instanceRef»
«instanceRef»

+mode 0..1 +mode 0..1

AtpStructureElement
Identifiable
ModeDeclaration

+ value: PositiveInteger [0..1]

Figure 5.5: Specializations of DiagnosticEnvModeElement

[TPS_DEXT_01120] Comparison of the value of a ModeDeclarationGroupPro-

totype with a ModeDeclaration dFor the comparison of the value of a ModeDec-
larationGroupPrototype with a ModeDeclaration, two alternatives apply, de-
pending on whether mode condition is executed in application software (swc) or basic
software (bsw):
• The ModeDeclarationGroupPrototype referenced in the role Diagnos-
ticEnvSwcModeElement.mode.contextModeDeclarationGroup shall be
compared to the ModeDeclaration referenced in the role DiagnosticEn-
vSwcModeElement.mode.targetMode.
• The ModeDeclarationGroupPrototype referenced in the role Diagnos-
ticEnvBswModeElement.mode.contextModeDeclarationGroup shall be
compared to the ModeDeclaration referenced in the role DiagnosticEn-
vBswModeElement.mode.targetMode.
c(RS_DEXT_00079)
Please note that the two alternatives mentioned in [TPS_DEXT_01120] are described
in Figure 5.5.
[constr_1466] Allowed values of compareType in the context of a Diagnos-
ticEnvModeCondition dWithin the context of a DiagnosticEnvDataCondition
only a subset of the values of DiagnosticCompareTypeEnum is supported for the
inherited attribute compareType, namely:
• DiagnosticCompareTypeEnum.isEqual
• DiagnosticCompareTypeEnum.isNotEqual
c()

82 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1467] References in DiagnosticEnvModeCondition dIn a Diagnosti-

cEnvModeCondition the reference modeElement shall only point to a Diagnosti-
cEnvModeElement that is aggregated inside the same DiagnosticEnvironmen-
talCondition as the DiagnosticEnvModeCondition itself.c()
Please note that the main benefit of the existence of the dedicated meta-class Diag-
nosticEnvModeElement is to keep the (serialized) model clean. Given the fulfillment
of [constr_1467], the potentially lengthy InstanceRef for identifying the operands of
a mode comparison does not (if applicable) have to be repeated but can be reused
multiple times in the context of the enclosing DiagnosticEnvironmentalCondi-
tion.
Class DiagnosticEnvModeCondition
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note DiagnosticEnvModeCondition are atomic condition based on the comparison of the active Mode
Declaration in a ModeDeclarationGroupProtoype with the constant value of a ModeDeclaration.
The formulation of this condition uses only one DiagnosticEnvElement, which contains enough
information to deduce the variable part (i.e. the part that changes at runtime) as well as the constant part
of the comparison.
Only DiagnosticCompareTypeEnum.isEqual or DiagnosticCompareTypeEnum.isNotEqual are eligible
values for DiagnosticAtomicCondition.compareType.
Base ARObject, DiagnosticEnvCompareCondition, DiagnosticEnvConditionFormulaPart
Attribute Type Mult. Kind Note
modeElement DiagnosticEnvMode 0..1 ref This reference represents both the ModeDeclaration
Element GroupPrototype and the ModeDeclaration relevant for the
mode comparison.

Table 5.16: DiagnosticEnvModeCondition

[constr_1804] Existence of DiagnosticEnvModeCondition.modeElement dFor

each DiagnosticEnvModeCondition, that attribute modeElement shall exist at
the time when the DEXT is complete.c()
Class DiagnosticEnvModeElement (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note All ModeDeclarations that are referenced in a DiagnosticEnvModeCondition shall be defined as a
DiagnosticEnvModeElement of this DiagnosticEnvironmentalCondition.
This concept keeps the ARXML clean: It avoids that the DiagnosticEnvConditionFormula is cluttered by
lengthy InstanceRef definitions.
Furthermore, it allows that an InstanceRef only needs to be defined once and can be used multiple times
in the different DiagnosticEnvModeConditions.
Base ARObject, Referrable
Subclasses DiagnosticEnvBswModeElement, DiagnosticEnvSwcModeElement
Attribute Type Mult. Kind Note
– – – – –
Table 5.17: DiagnosticEnvModeElement

83 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEnvSwcModeElement
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note This meta-class represents the ability to refer to a ModeDeclaration in a concrete System context.
Base ARObject, DiagnosticEnvModeElement, Referrable
Attribute Type Mult. Kind Note
mode ModeDeclaration 0..1 iref This reference identifies both the ModeDeclarationGroup
Prototype and the ModeDeclaration for the specific mode
comparison.
InstanceRef implemented by:PModeInSystemInstance
Ref
Table 5.18: DiagnosticEnvSwcModeElement

[constr_1805] Existence of DiagnosticEnvSwcModeElement.mode dFor each

DiagnosticEnvSwcModeElement, that attribute mode shall exist at the time when
the DEXT is complete.c()
Class DiagnosticEnvBswModeElement
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition
Note This meta-class represents the ability to refer to a specific ModeDeclaration in the scope of a BswModule
Description.
Base ARObject, DiagnosticEnvModeElement, Referrable
Attribute Type Mult. Kind Note
mode ModeDeclaration 1 iref This reference identifies both the ModeDeclarationGroup
Prototype and the ModeDeclaration for the specific mode
comparison.
InstanceRef implemented by:ModeInBswModule
DescriptionInstanceRef

Table 5.19: DiagnosticEnvBswModeElement

[constr_1806] Existence of DiagnosticEnvBswModeElement.mode dFor each

DiagnosticEnvBswModeElement, that attribute mode shall exist at the time when
the DEXT is complete.c()

5.5 Diagnostic Services supported by AUTOSAR

The following sub-chapters describe the modeling of the collection of relevant diag-
nostic services as defined in the ISO 14229-1 [16]. This means that the definition of
the AUTOSAR DiagnosticExtract does not explicitly support the total collection of
diagnostic services as defined by [16].
Some diagnostic services compiled in this document define so-called sub-functions
that need to be identified to fully specify the nature of the respective diagnostic service.
[TPS_DEXT_01045] Supported diagnostic services dThe table 5.20 shows the UDS
services supported by the DiagnosticExtract.c(RS_DEXT_00003, RS_DEXT_-
00004, RS_DEXT_00005, RS_DEXT_00006, RS_DEXT_00007, RS_DEXT_00008,

84 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

RS_DEXT_00009, RS_DEXT_00010, RS_DEXT_00011, RS_DEXT_00012, RS_-

DEXT_00013, RS_DEXT_00014, RS_DEXT_00015, RS_DEXT_00016, RS_DEXT_-
00017, RS_DEXT_00018, RS_DEXT_00019, RS_DEXT_00020, RS_DEXT_00021,
RS_DEXT_00022)
ID Service
0x10 SessionControl
0x11 EcuReset
0x14 ClearDiagnosticInformation
0x19 ClearDTCInformation
0x22 ReadDataByIdentifier
0x23 ReadMemoryByAddress
0x27 SecurityAccess
0x28 CommunicationControl
0x2A ReadDataByPeriodicIdentifier
0x2C DynamicallyDefineDataIdentifier
0x2E WriteDataByIdentifier
0x2F IOControl
0x31 RoutineControl
0x34 RequestDownload
0x35 RequestUpload
0x36 TransferData
0x37 RequestTransferExit
0x3D WriteMemoryByAddress
0x85 ControlDTCSetting
0x86 ResponseOnEvent

Table 5.20: Supported diagnostic services

[TPS_DEXT_01013] Specification of sub-functions by means of attribute Diag-

nosticServiceInstance.category d
In all cases where a diagnostic service defines a sub-function according to ISO 14229-
1 [16], the value of the attribute category of the applicable sub-class of Diagnos-
ticServiceInstance can be used to specify the applicable sub-function as a textual
token.
Constraints are defined to clarify the existence of standardized values of the attribute
category for the given sub-function. This implies that an instance of the given sub-
class of DiagnosticServiceInstance only has a single sub-function at a time.c
(RS_DEXT_00049, RS_DEXT_00051)
[TPS_DEXT_01014] Possible values of the category attribute for diagnostic ser-
vices dAUTOSAR claims the right to standardize the possible values of the attribute
category for given diagnostic services.c(RS_DEXT_00001, RS_DEXT_00051)
If applicable, AUTOSAR allows for the usage of values of the attribute category other
than the standardized values.

85 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

In this case, however, proprietary values of the attribute category shall be prefixed
with a company-specific name fragment in order to avoid collisions that could occur if or
when the list of possible values claimed by the AUTOSAR standard itself is extended.
Example:
Listing 5.2: Example for the definition of a custom category
<AR-PACKAGE>
<SHORT-NAME>DiagnosticExtractExample</SHORT-NAME>
<ELEMENTS>
<DIAGNOSTIC-ECU-RESET>
<SHORT-NAME>ResetTheHardWay</SHORT-NAME>
<CATEGORY>ACME_REALLY_HARD_RESET</CATEGORY>
</DIAGNOSTIC-ECU-RESET>
</ELEMENTS>
</AR-PACKAGE>

5.5.1 DataByIdentifier

This chapter describes the modeling of diagnostic services ReadDataByIdentifier

(0x22) and WriteDataByIdentifier (0x2E).
The purpose of this diagnostic service is to enable a tester to request the values of
data records from the AUTOSAR diagnostics stack. The data records are identified by
a formally modeled DiagnosticDataIdentifier.
The modeling of this diagnostic service comprises the two meta-classes Diagnos-
ticReadDataByIdentifier and DiagnosticWriteDataByIdentifier. These
meta-classes both need to specify the set of DiagnosticDataIdentifiers and the
set of applicable DiagnosticAccessPermissions.
As these properties are shared between instances of DiagnosticReadDataByI-
dentifier and DiagnosticWriteDataByIdentifier, an abstract base class
named DiagnosticDataByIdentifier has been created that provides the ac-
tual references to DiagnosticDataIdentifier and DiagnosticAccessPer-
mission.
[TPS_DEXT_01054] Existence of DiagnosticDataByIdentifier.dataIdenti-
fier dThe configuration of a given DiagnosticDataByIdentifier is consid-
ered incomplete until the reference in the role DiagnosticDataByIdentifier.
dataIdentifier exists.c(RS_DEXT_00007, RS_DEXT_00013, RS_DEXT_00034)
The meaning of [TPS_DEXT_01054] is that the reference may be missing in intermedi-
ate steps of the configuration work flow. But at the point in time when ECU configuration
is generated from the DiagnosticExtract the reference is needed to able to make
sense of the model for the given DiagnosticDataByIdentifier.
The ability to read multiple DIDs at run-time is controlled via attribute Diagnosti-
cReadDataByIdentifierClass.maxDidToRead and therefore it is sufficient to (at
configuration-time) limit the multiplicity of attribute dataIdentifier to 1.

86 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

0..1 +accessPermission

DiagnosticCommonElement
DiagnosticServiceInstance
+serviceClass

«atpAbstract» 0..1

DiagnosticDataByIdentifier DiagnosticReadDataByIdentifierClass

+ maxDidToRead: PositiveInteger [0..1]

0..1
+readClass
{redefines
serviceClass}
0..1 +dataIdentifier
DiagnosticCommonElement
DiagnosticReadDataByIdentifier
DiagnosticAbstractDataIdentifier

«atpVariation»
+ id: PositiveInteger [0..1]

DiagnosticDataIdentifier DiagnosticDynamicDataIdentifier

+ didSize: PositiveInteger [0..1]

+ representsVin: Boolean [0..1]

DiagnosticWriteDataByIdentifier DiagnosticWriteDataByIdentifierClass
+writeClass

0..1
{redefines
serviceClass}

Figure 5.6: Modeling of diagnostic services ReadDataByIdentifier (0x22) and Write-

DataByIdentifier (0x2E)

Please note that the reference DiagnosticDataByIdentifier.dataIdentifier

goes to DiagnosticAbstractDataIdentifier. This modeling approach allows to
actually reference any of the meta-classes that inherit from DiagnosticAbstract-
DataIdentifier.
Class DiagnosticReadDataByIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This represents an instance of the "Read Data by Identifier" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticDataByIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticDataByIdentifier ,
DiagnosticServiceInstance, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
readClass DiagnosticReadDataBy 0..1 ref This reference substantiates that abstract reference in the
IdentifierClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticReadDataBy
Identifier in the given context.

Table 5.21: DiagnosticReadDataByIdentifier

87 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1807] Existence of reference DiagnosticDataByIdentifier.

dataIdentifier dFor each DiagnosticDataByIdentifier, the reference
dataIdentifier shall exist at the time when the DEXT is complete.c()
Class DiagnosticWriteDataByIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This represents an instance of the "Write Data by Identifier" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticDataByIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticDataByIdentifier ,
DiagnosticServiceInstance, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
writeClass DiagnosticWriteDataBy 0..1 ref This reference substantiates that abstract reference in the
IdentifierClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticWriteDataBy
Identifier in the given context.

Table 5.22: DiagnosticWriteDataByIdentifier

Class DiagnosticWriteDataByIdentifierClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This meta-class contains attributes shared by all instances of the "Write Data by Identifier" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticDataByIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.23: DiagnosticWriteDataByIdentifierClass

Class DiagnosticDataByIdentifier (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This represents an abstract base class for all diagnostic services that access data by identifier.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses DiagnosticReadDataByIdentifier, DiagnosticReadScalingDataByIdentifier, DiagnosticWriteDataBy
Identifier
Attribute Type Mult. Kind Note
dataIdentifier DiagnosticAbstractData 0..1 ref This represents the linked DiagnosticDataIdentifier.
Identifier
Table 5.24: DiagnosticDataByIdentifier

The modeling of DiagnosticDataByIdentifier represents concrete instances of

diagnostic services within a DiagnosticExtract. However, there are attributes that
are shared among all instances of DiagnosticReadDataByIdentifier.
For this purpose the dedicated service class DiagnosticReadDataByIdenti-
fierClass has been introduced.

88 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticReadDataByIdentifierClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This meta-class contains attributes shared by all instances of the "Read Data by Identifier" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticDataByIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
maxDidToRead PositiveInteger 0..1 attr This attribute represents the maximum number of allowed
DIDs in a single instance of DiagnosticReadDataBy
Identifier.
Table 5.25: DiagnosticReadDataByIdentifierClass

Please note that it is possible to create a reference to a concrete Diagnostic-

DataIdentifier from different DiagnosticServiceInstances.
[TPS_DEXT_01050] Consistency of DiagnosticServiceSwMapping with re-
spect to data IDs dFor each DiagnosticServiceSwMapping that references a
DiagnosticValueNeeds and a DiagnosticDataByIdentifier, the value of
DiagnosticValueNeeds.didNumber shall be ignored and the value of Diagnos-
ticDataByIdentifier.dataIdentifier.id shall be taken instead.c(RS_DEXT_-
00007, RS_DEXT_00013, RS_DEXT_00034, RS_DEXT_00052)
Class DiagnosticValueNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the general needs on the configuration of the Diagnostic Communication Manager (DCM)
which are not related to a particular item (e.g. a PID). The main use case is the mapping of service ports
to the DCM which are not related to a particular item.
In the case of using a sender receiver communicated value, the related value shall be taken via assigned
Data in the role "signalBasedDiagnostics".
In case of using a client/server communicated value, the related value shall be communicated via the
port referenced by asssignedPort. The details of this communication (e.g. appropriate naming
conventions) are specified in the related software specifications (SWS).
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
dataLength PositiveInteger 0..1 attr This attribute is applicable only if the ServiceNeed is
aggregated within BswModuleDependency.
This attribute represents the length of data (in bytes)
provided for this particular PID signal.
diagnosticValue DiagnosticValueAccess 0..1 attr This attribute controls whether the data can be read and
Access Enum written or whether it is to be handled read-only.
didNumber PositiveInteger 0..1 attr This represents a Data identifier for the diagnostic value.
This allows to predefine the DID number if the responsible
function developer has received a particular requirement
from the OEM or from a standardization body.
fixedLength Boolean 0..1 attr This attribute controls whether the data length of the data
is fixed.
5

89 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticValueNeeds
processingStyle DiagnosticProcessing 0..1 attr This attribute controls whether interaction requires the
StyleEnum software-component to react synchronously on a request
or whether it processes the request in background but still
the DCM has to issue the call again to eventually obtain
the result of the request.

Table 5.26: DiagnosticValueNeeds

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

0..1 +accessPermission

DiagnosticCommonElement
DiagnosticServiceInstance
+serviceClass

«atpAbstract» 0..1

DiagnosticCommonElement
DiagnosticDataByIdentifier
+dataIdentifier DiagnosticAbstractDataIdentifier

0..1 «atpVariation»
+ id: PositiveInteger [0..1]

DiagnosticDataIdentifier

+ didSize: PositiveInteger [0..1]

+ representsVin: Boolean [0..1]

«atpVariation,atpSplitable»

+dataElement 0..*

DiagnosticParameter

  
    «atpIdentityContributor»

+ bitOffset: PositiveInteger [0..1]

«atpVariation,atpSplitable»
+dataElement 0..1

Identifiable
DiagnosticDataElement

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

DiagnosticReadScalingDataByIdentifier DiagnosticReadScalingDataByIdentifierClass
+readScalingDataClass

0..1

Figure 5.7: Modeling of diagnostic services ReadScalingDataByIdentifier (0x24)

[TPS_DEXT_01146] Support for service ReadScalingDataByIdentifier

(0x24) dThe AUTOSAR Diagnostic Extract supports the configuration of UDS ser-
vice ReadScalingDataByIdentifier (0x24). For this purpose meta-classes

90 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticReadScalingDataByIdentifier and DiagnosticReadScaling-

DataByIdentifierClass shall be used.c(RS_DEXT_00007, RS_DEXT_00034)
[constr_1623] Restriction on DiagnosticReadScalingDataByIdentifier.
dataIdentifier dThe reference DiagnosticReadScalingDataByIdentifier.
dataIdentifier shall only refer to a DiagnosticDataIdentifier.c()
[constr_1624] Existence of DiagnosticDataElement.scalingInfoSize dThe
attribute DiagnosticDataElement.scalingInfoSize shall only exist if the en-
closing DiagnosticParameter is aggregated by a DiagnosticDataIdentifier
that is referenced by a DiagnosticReadScalingDataByIdentifier in the role
DiagnosticReadScalingDataByIdentifier.dataIdentifier.c()
Class DiagnosticReadScalingDataByIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This represents an instance of the "Read Scaling Data by Identifier" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticDataByIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticDataByIdentifier ,
DiagnosticServiceInstance, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
readScaling DiagnosticReadScaling 0..1 ref This reference substantiates that abstract reference in the
DataClass DataByIdentifierClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticReadScalingData
ByIdentifier in the given context.

Table 5.27: DiagnosticReadScalingDataByIdentifier

Class DiagnosticReadScalingDataByIdentifierClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier
Note This meta-class contains attributes shared by all instances of the "Read Scaling Data by Identifier"
diagnostic service.
Tags:atp.recommendedPackage=DiagnosticDataByIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.28: DiagnosticReadScalingDataByIdentifierClass

5.5.2 IOControl

This chapter describes the modeling of diagnostic services InputOutput Control

(0x2F). The purpose of this service is to provide the tester with the ability to override
values exchanged with the AUTOSAR hardware abstraction.
[TPS_DEXT_01015] Meaning of attributes of DiagnosticIOControl dThe at-
tributes freezeCurrentState, resetToDefault, and shortTermAdjustment

91 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

represent the capabilities of the server rather than a concrete request message.c(RS_-
DEXT_00014)
[TPS_DEXT_01016] The capability returnControlToEcu dAccording to the state-
ment made by [TPS_DEXT_01015], there is no formal means provided to configure the
capability to execute returnControlToEcu. This lack of configuration is intentional be-
cause the capability is always available and cannot be revoked anyway.c(RS_DEXT_-
00014)
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticIOControl +ioControlClass DiagnosticIoControlClass

+ freezeCurrentState: Boolean [0..1]

+ resetToDefault: Boolean [0..1] 0..1
+ shortTermAdjustment: Boolean [0..1] {redefines serviceClass}

DiagnosticControlEnableMaskBit

+controlEnableMaskBit + bitNumber: PositiveInteger [0..1]

0..*

+dataIdentifier 0..1 +controlledDataElement 0..*

DiagnosticAbstractDataIdentifier Identifiable
DiagnosticDataIdentifier DiagnosticDataElement

+ didSize: PositiveInteger [0..1] + arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ representsVin: Boolean [0..1] + maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 5.8: Modeling of diagnostic service IOControl (0x2F)

[TPS_DEXT_01017] Meaning of DiagnosticIOControl.dataIdentifier dThe

DiagnosticIOControl.dataIdentifier is taken for specifying the payload for
the service.
However, in some cases dataIdentifier models the payload of the request mes-
sage (DiagnosticIOControl.shortTermAdjustment is set to true) and in some
cases it represents the payload of the response message.c(RS_DEXT_00014, RS_-
DEXT_00034)
Please note that the referenced dataIdentifier itself may aggregate several Di-
agnosticDataElements.
At run-time, only some DiagnosticDataElements may be relevant for a specific
execution of the service InputOutput Control. For this purpose, the diagnostic
message contains the so-called ControlEnableMaskRecord (for more information,
please refer to [SWS_DCM_00581]).

92 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01089] Definition of an identifier of a DiagnosticIOControl dThe

identifier of a DiagnosticIOControl is defined by the attribute DiagnosticIO-
Control.dataIdentifier.id.c(RS_DEXT_00037)
Class DiagnosticIOControl
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::IOControl
Note This represents an instance of the "I/O Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticIoControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
controlEnable DiagnosticControl * aggr This aggregation represents the control mask record
MaskBit EnableMaskBit consiting of single bits.
dataIdentifier DiagnosticDataIdentifier 0..1 ref This represents the corresponding DiagnosticData
Identifier
freezeCurrent Boolean 0..1 attr Setting this attribute to true represents the ability of the
State Dcm to execute a freezeCurrentState.
ioControlClass DiagnosticIoControl 0..1 ref This reference substantiates that abstract reference in the
Class role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticIOControl in the
given context.
resetToDefault Boolean 0..1 attr Setting this attribute to true represents the ability of the
Dcm to execute a resetToDefault.
shortTerm Boolean 0..1 attr Setting this attribute to true represents the ability of the
Adjustment Dcm to execute a shortTermAdjustment.

Table 5.29: DiagnosticIOControl

Class DiagnosticIoControlClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::IOControl
Note This meta-class contains attributes shared by all instances of the "IO Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticIoControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.30: DiagnosticIoControlClass

[TPS_DEXT_01018] InputOutput Control does not define any sub-functions

dThe diagnostic service InputOutput Control does not define any sub-functions,
therefore the value of DiagnosticIOControl.category does not need to be con-
strained.c(RS_DEXT_00014, RS_DEXT_00051)
[TPS_DEXT_01051] Consistency of DiagnosticServiceSwMapping with re-
spect to data IDs dFor each DiagnosticServiceSwMapping that references a
DiagnosticIoControlNeeds and a DiagnosticIOControl, the value of Diag-
nosticIoControlNeeds.didNumber shall be ignored and the value of Diagnos-
ticIOControl.dataIdentifier.id shall be taken instead.c(RS_DEXT_00014,
RS_DEXT_00052)

93 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticIoControlNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the general needs on the configuration of the Diagnostic Communication Manager (DCM)
which are not related to a particular item (e.g. a PID). The main use case is the mapping of service ports
to the Dcm which are not related to a particular item.
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
currentValue DiagnosticValueNeeds 0..1 ref Reference to the DiagnosticValueNeeds indicating the
access to the current value via signalBasedDiagnostics.
didNumber PositiveInteger 0..1 attr This represents a Data identifier for the diagnostic value.
This allows to predefine the DID number if the a function
developer has received a particular requirement from the
OEM or from a standardization body.
freezeCurrent Boolean 0..1 attr This attribute determines, if the referenced port supports
StateSupported temporary freezing of I/O value.
resetToDefault Boolean 0..1 attr This represents a flag for the existence of the ResetTo
Supported Default operation in the service interface.
shortTerm Boolean 0..1 attr This attribute determines, if the referenced port supports
Adjustment temporarily setting of I/O value to a specific value
Supported provided by the diagnostic tester.

Table 5.31: DiagnosticIoControlNeeds

[TPS_DEXT_01150] Semantics of meta-class DiagnosticControlEnable-

MaskBit dBy aggregating DiagnosticControlEnableMaskBit at Diagnosti-
cIOControl it is possible to specify I/O control channels in the diagnostic extract.
The reference DiagnosticControlEnableMaskBit.controlledDataElement
identifies all DiagnosticDataElements that belong to the I/O control channel rep-
resented by the bit in the control mask record.c(RS_DEXT_00014, RS_DEXT_00034)
Class DiagnosticControlEnableMaskBit
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::IOControl
Note This meta-class has the ability to represent one bit in the control enable mask record.
Base ARObject
Attribute Type Mult. Kind Note
bitNumber PositiveInteger 0..1 attr This attribute represents the bit number of the bit in the
control mask record. Bit number 0 is the most significant
bit (MSB) in the first byte of the CEMR in the network
presentation.
controlledData DiagnosticDataElement * ref This reference represents the collection of Diagnostic
Element DataElements that are controlled by this bit of the control
mask record.
Table 5.32: DiagnosticControlEnableMaskBit

Please note that the modeling of the controlEnableMaskBit intentionally does not
use the ordered annotation to assign bit numbers to the aggregated Diagnostic-
ControlEnableMaskBits.
The control mask record does not necessarily have to be used from top to bottom
without gaps. Example: bit 3 could be unused, but 0,1, and 4 could be used.

94 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1721] DiagnosticControlEnableMaskBit.bitNumber shall be unique

dWithin the context of the enclosing DiagnosticIOControl the value of attribute
DiagnosticIOControl.controlEnableMaskBit.bitNumber shall be unique.c()
Please note that within the context of a DiagnosticIOControl, it is not required
to have 0 as the lowest value of aggregated DiagnosticIOControl.controlEn-
ableMaskBit.bitNumber.
[constr_1722] Relation between reference DiagnosticIOControl.dataIden-
tifier and attribute DiagnosticIOControl.controlEnableMaskBit dAny
DiagnosticDataElement referenced in the role DiagnosticIOControl.con-
trolEnableMaskBit.controlledDataElement shall be defined in the scope of
the DiagnosticDataIdentifier that is referenced in the role DiagnosticIO-
Control.dataIdentifier.c()

5.5.3 EcuReset

This chapter describes the modeling of diagnostic services EcuReset (0x11).

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
+serviceClass
DiagnosticServiceInstance
«atpAbstract» 0..1

DiagnosticEcuReset DiagnosticEcuResetClass
+ecuResetClass
+ customSubFunctionNumber: PositiveInteger [0..1] + respondToReset: DiagnosticResponseToEcuResetEnum [0..1]
0..1
{redefines
serviceClass}

«enumeration»
DiagnosticResponseToEcuResetEnum

respondBeforeReset
respondAfterReset

Figure 5.9: Modeling of diagnostic service EcuReset (0x11)

Class DiagnosticEcuReset
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EcuReset
Note This represents an instance of the "ECU Reset" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticEcuResets
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
5

95 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticEcuReset
customSub PositiveInteger 0..1 attr This attribute shall be used to define a custom
Function sub-function number if none of the standardized values of
Number category shall be used.
ecuResetClass DiagnosticEcuReset 0..1 ref This reference substantiates that abstract reference in the
Class role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticEcuReset in the
given context.

Table 5.33: DiagnosticEcuReset

Class DiagnosticEcuResetClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EcuReset
Note This meta-class contains attributes shared by all instances of the "Ecu Reset" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticEcuResets
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
respondTo DiagnosticResponseTo 0..1 attr This attribute defines whether the response to the Ecu
Reset EcuResetEnum Reset service shall be transmitted before or after the
actual reset.
Table 5.34: DiagnosticEcuResetClass

Enumeration DiagnosticResponseToEcuResetEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::EcuReset
Note
Literal Description
respondAfterReset Answer to EcuReset service should come after the reset.
Tags:atp.EnumerationLiteralIndex=0
respondBefore Answer to EcuReset service should come before the reset.
Reset
Tags:atp.EnumerationLiteralIndex=1

Table 5.35: DiagnosticResponseToEcuResetEnum

Please note that (as already explained in section 5.5) the SubFunctions of this ser-
vice are modeled by means of the category attribute.
[TPS_DEXT_01056] Applicable values for DiagnosticEcuReset.category dThe
following values of the attribute DiagnosticEcuReset.category are standardized
by AUTOSAR:
• HARD_RESET
• KEY_OFF_ON_RESET
• SOFT_RESET
• ENABLE_RAPID_POWER_SHUT_DOWN
• DISABLE_RAPID_POWER_SHUT_DOWN

96 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

The meaning of these values is described in the applicable ISO document [16].c(RS_-
DEXT_00001, RS_DEXT_00004, RS_DEXT_00051)
[TPS_DEXT_01019] Correspondence of category values to numerical values
mentioned in the ISO 14229-1 dThe ISO 14229-1 [16] standard document defines
specific numerical values for the sub-functions of the diagnostic service EcuReset.
The correspondence of the numerical values to the pre-defined values of category
according to [TPS_DEXT_01056] is pretty obvious because the definition of values
defined in [TPS_DEXT_01056] has been directly inspired by the ISO 14229-1 [16]
standard document.c(RS_DEXT_00001, RS_DEXT_00004, RS_DEXT_00051)
[TPS_DEXT_01020] Manufacturer-specific values for sub-functions of service
EcuReset dThe ISO 14229-1 [16] standard document, beyond the standardized nu-
merical values for sub-functions, reserves a numerical range of subFunction identifiers
for manufacturer- or supplier-specific use.
In this case it is possible to define further values for category, provided that a custom
prefix is used to avoid potential name clashes with further extensions of the AUTOSAR
standard, namely [TPS_DEXT_01056].c(RS_DEXT_00001, RS_DEXT_00004, RS_-
DEXT_00051)
[TPS_DEXT_01021] Semantics of DiagnosticEcuReset.customSubFunction-
Number dThe attribute DiagnosticEcuReset.customSubFunctionNumber has
been introduced to allow for the specification of a manufacturer- or supplier-specific
value to represent the custom sub-function in the diagnostic communication.
The tuple created by the values of attributes DiagnosticEcuReset.category and
DiagnosticEcuReset.customSubFunctionNumber fully specifies identification of
the manufacturer- or supplier-specific sub-function.c(RS_DEXT_00004, RS_DEXT_-
00047, RS_DEXT_00051)
[constr_1331] Existence of DiagnosticEcuReset.customSubFunctionNumber
dThe attribute DiagnosticEcuReset.customSubFunctionNumber shall only exist
if the value of DiagnosticEcuReset.category is outside the standardized set of
values as defined by [TPS_DEXT_01056].c()
[constr_1332] Value range for DiagnosticEcuReset.customSubFunctionNum-
ber dThe allowed value for DiagnosticEcuReset.customSubFunctionNumber
shall always be within the closed interval 0x40 .. 0x7E.c()

5.5.4 ClearDiagnosticInformation

This chapter describes the modeling of diagnostic services ClearDiagnosticIn-

formation (0x14). As the name suggests, the purpose of the service is to clear
diagnostic information in the AUTOSAR diagnostics stack.

97 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance
+serviceClass

«atpAbstract» 0..1

DiagnosticClearDiagnosticInformation DiagnosticClearDiagnosticInformationClass
+clearDiagnosticInformationClass

0..1
{redefines
serviceClass}

Figure 5.10: Modeling of diagnostic service ClearDiagnosticInformation (0x14)

Please note that there is nothing to configure for DiagnosticClearDiagnosticIn-

formation beyond its mere existence.
Class DiagnosticClearDiagnosticInformation
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ClearDiagnosticInfo
Note This represents an instance of the "Clear Diagnostic Information" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticClearDiagnosticInformations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
clearDiagnostic DiagnosticClear 0..1 ref This reference substantiates that abstract reference in the
Information DiagnosticInformation role serviceClass for this specific concrete class.
Class Class
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticClearDiagnostic
Information in the given context.

Table 5.36: DiagnosticClearDiagnosticInformation

Class DiagnosticClearDiagnosticInformationClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ClearDiagnosticInfo
Note This meta-class contains attributes shared by all instances of the "Clear Diagnostic Information"
diagnostic service.
Tags:atp.recommendedPackage=DiagnosticClearDiagnosticInformations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.37: DiagnosticClearDiagnosticInformationClass

[TPS_DEXT_01022] ClearDiagnosticInformation does not define any sub-

functions dThe diagnostic service ClearDiagnosticInformation does not define
any sub-functions, therefore the value of DiagnosticClearDiagnosticInforma-
tion.category does not need to be constrained.c(RS_DEXT_00001, RS_DEXT_-
00005, RS_DEXT_00051)

98 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

5.5.5 Memory Services

This chapter describes the modeling of diagnostic services for memory access (0x23,
0x3D, 0x34-0x37). The purpose of these services is to access memory on the diag-
nostic stack on request of the tester.
The service description for accessing memory for diagnostic purposes is modeled by
the abstract meta-class DiagnosticMemoryByAddress. It is supposed to provide
all model properties relevant for the memory access.
The description of memory access, to some extent, requires a formal description of the
memory segments to take into account. For this purpose the meta-class Diagnos-
ticMemoryIdentifier has been introduced and referenced by DiagnosticMem-
oryAddressableRangeAccess in the role memoryRange.
The intent of this modeling was not to provide a generic memory model but to allow for
the specification of memory properties just as far as diagnostics is concerned.
The aggregation of DiagnosticMemoryIdentifier at DiagnosticMemoryByAd-
dress may or may not be relevant for an OEM. However, there is certainly a use case
for adding this information to a DiagnosticExtract that goes back from a tier-1
supplier to an OEM as sort of documentation of the diagnostic configuration.
DiagnosticCommonElement
DiagnosticServiceInstance

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticAccessPermission

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticMemoryByAddress
DiagnosticMemoryIdentifier

+ id: PositiveInteger [0..1]

+ memoryHighAddress: PositiveInteger [0..1]
+ memoryHighAddressLabel: String [0..1]
+ memoryLowAddress: PositiveInteger [0..1]
+ memoryLowAddressLabel: String [0..1]

+memoryRange 0..*

DiagnosticTransferExit DiagnosticDataTransfer DiagnosticMemoryAddressableRangeAccess

DiagnosticWriteMemoryByAddress DiagnosticReadMemoryByAddress DiagnosticRequestDownload DiagnosticRequestUpload

Figure 5.11: Modeling of diagnostic services Memory (0x23, 0x3D, 0x34-0x37)

99 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

As DiagnosticMemoryByAddress represents a generic base class for all kinds of

diagnostic memory access, it is also necessary to model the particular sub-classes
that address specific use cases for diagnostic memory access.
These sub-classes are conceptually on the same level as other sub-classes of Diag-
nosticServiceInstance.
In other words, the case of memory access deviates from the modeling of other diag-
nostic services such that there is one further abstract base class involved.
[constr_1333] Existence of DiagnosticMemoryIdentifier.memoryLowAd-
dress and DiagnosticMemoryIdentifier.memoryHighAddress dThe at-
tributes DiagnosticMemoryIdentifier.memoryLowAddress as well as Diag-
nosticMemoryIdentifier.memoryHighAddress shall not exist if the Diagnos-
ticMemoryIdentifier referenced in the role memoryRange is referenced by a
DiagnosticRequestDownload or a DiagnosticRequestUpload.c()
[constr_1411] Existence of DiagnosticMemoryIdentifier.memoryHighAd-
dressLabel vs. DiagnosticMemoryIdentifier.memoryHighAddress dAt
most one of the attributes in the following list shall exist:
• DiagnosticMemoryIdentifier.memoryHighAddressLabel
• DiagnosticMemoryIdentifier.memoryHighAddress
c()
[constr_1412] Existence of DiagnosticMemoryIdentifier.memoryLowAd-
dressLabel vs. DiagnosticMemoryIdentifier.memoryLowAddress dAt most
one of the attributes in the following list shall exist:
• DiagnosticMemoryIdentifier.memoryLowAddressLabel
• DiagnosticMemoryIdentifier.memoryLowAddress
c()
Please note that it does not make sense to describe a memory address in this con-
text both numerically and symbolically. If the address is described at all (see [con-
str_1333]) then it shall be done either symbolically or numerically. This is the motiva-
tion of the existence of [constr_1411] and [constr_1412].
Class DiagnosticMemoryByAddress (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an abstract base class for diagnostic services that deal with accessing memory by
address.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses DiagnosticDataTransfer, DiagnosticMemoryAddressableRangeAccess, DiagnosticTransferExit
5

100 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticMemoryByAddress (abstract)
Attribute Type Mult. Kind Note
– – – – –
Table 5.38: DiagnosticMemoryByAddress

Class DiagnosticMemoryAddressableRangeAccess (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This abstract base class
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemoryByAddress,
DiagnosticServiceInstance, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses DiagnosticReadMemoryByAddress, DiagnosticRequestDownload, DiagnosticRequestUpload, Diagnostic
WriteMemoryByAddress
Attribute Type Mult. Kind Note
memoryRange DiagnosticMemory * ref This represents the formal description of the memory
Identifier segment to which the DiagnosticMemoryByAddress
applies.

Table 5.39: DiagnosticMemoryAddressableRangeAccess

Class DiagnosticMemoryIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class represents the ability to define memory properties from the diagnostics point of view.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
access DiagnosticAccess 0..1 ref This represents that access permission defined for the
Permission Permission specific DiagnosticMemoryIdentifier.
id PositiveInteger 0..1 attr This represents the identification of the memory segment.
memoryHigh PositiveInteger 0..1 attr This represents the upper bound for addresses of the
Address memory segment.
memoryHigh String 0..1 attr This represents a symbolic label for the upper bound for
AddressLabel addresses of the memory segment.
memoryLow PositiveInteger 0..1 attr This represents the lower bound for addresses of the
Address memory segment.
memoryLow String 0..1 attr This represents a symbolic label for the lower bound for
AddressLabel addresses of the memory segment.

Table 5.40: DiagnosticMemoryIdentifier

Class DiagnosticWriteMemoryByAddress
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an instance of the "Write Memory by Address" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
AddressableRangeAccess, DiagnosticMemoryByAddress, DiagnosticServiceInstance, Identifiable,
MultilanguageReferrable, PackageableElement, Referrable
5

101 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticWriteMemoryByAddress
Attribute Type Mult. Kind Note
writeClass DiagnosticWriteMemory 0..1 ref This reference substantiates that abstract reference in the
ByAddressClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticWritememoryBy
Address in the given context.

Table 5.41: DiagnosticWriteMemoryByAddress

Class DiagnosticWriteMemoryByAddressClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class contains attributes shared by all instances of the "Write Memory by Address" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.42: DiagnosticWriteMemoryByAddressClass

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticMemoryByAddress

DiagnosticMemoryAddressableRangeAccess

DiagnosticWriteMemoryByAddress DiagnosticWriteMemoryByAddressClass
+writeClass

0..1
{redefines serviceClass}

Figure 5.12: Modeling of diagnostic service WriteMemoryByAddress (0x3D)

[TPS_DEXT_01023] WriteMemoryByAddress does not define any sub-functions

dThe diagnostic service WriteMemoryByAddress does not define any sub-functions,
therefore the value of DiagnosticWriteMemoryByAddress.category does not
need to be constrained.c(RS_DEXT_00001, RS_DEXT_00020, RS_DEXT_00051)

102 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticReadMemoryByAddress
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an instance of the "Read Memory by Address" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
AddressableRangeAccess, DiagnosticMemoryByAddress, DiagnosticServiceInstance, Identifiable,
MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
readClass DiagnosticReadMemory 0..1 ref This reference substantiates that abstract reference in the
ByAddressClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticReadMemoryBy
Addresst in the given context.

Table 5.43: DiagnosticReadMemoryByAddress

Class DiagnosticReadMemoryByAddressClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class contains attributes shared by all instances of the "Read Memory by Address" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.44: DiagnosticReadMemoryByAddressClass

DiagnosticCommonElement DiagnosticCommonElement
Dcm::DiagnosticAccessPermission CommonService::DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
CommonService::DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticMemoryByAddress

DiagnosticMemoryAddressableRangeAccess

DiagnosticReadMemoryByAddress DiagnosticReadMemoryByAddressClass
+readClass

0..1
{redefines
serviceClass}

Figure 5.13: Modeling of diagnostic service ReadMemoryByAddress (0x23)

103 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01024] ReadMemoryByAddress does not define any sub-functions

dThe diagnostic service ReadMemoryByAddress does not define any sub-functions,
therefore the value of DiagnosticReadMemoryByAddress.category does not
need to be constrained.c(RS_DEXT_00001, RS_DEXT_00008, RS_DEXT_00051)
Class DiagnosticTransferExit
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an instance of the "Transfer Exit" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemoryByAddress,
DiagnosticServiceInstance, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
transferExit DiagnosticTransferExit 0..1 ref This reference substantiates that abstract reference in the
Class Class role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticTransferExit in the
given context.

Table 5.45: DiagnosticTransferExit

Class DiagnosticTransferExitClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class contains attributes shared by all instances of the "Transfer Exit" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.46: DiagnosticTransferExitClass

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticMemoryByAddress

DiagnosticTransferExit DiagnosticTransferExitClass
+transferExitClass

0..1
{redefines serviceClass}

Figure 5.14: Modeling of diagnostic service TransferExit (0x37)

[TPS_DEXT_01025] TransferExit does not define any sub-functions dThe diag-

nostic service TransferExit does not define any sub-functions, therefore the value

104 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

of DiagnosticTransferExit.category does not need to be constrained.c(RS_-

DEXT_00001, RS_DEXT_00019, RS_DEXT_00051)
Class DiagnosticDataTransfer
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an instance of the "Data Transfer" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemoryByAddress,
DiagnosticServiceInstance, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataTransfer DiagnosticDataTransfer 0..1 ref This reference substantiates that abstract reference in the
Class Class role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticDataTransfer in the
given context.

Table 5.47: DiagnosticDataTransfer

Class DiagnosticDataTransferClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class contains attributes shared by all instances of the "Data Transfer" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.48: DiagnosticDataTransferClass

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance
+serviceClass

«atpAbstract» 0..1

DiagnosticMemoryByAddress

DiagnosticDataTransfer DiagnosticDataTransferClass
+dataTransferClass

0..1
{redefines
serviceClass}

Figure 5.15: Modeling of diagnostic service DataTransfer (0x36)

[TPS_DEXT_01026] DataTransfer does not define any sub-functions dThe diag-

nostic service DataTransfer does not define any sub-functions, therefore the value
of DiagnosticDataTransfer.category does not need to be constrained.c(RS_-
DEXT_00001, RS_DEXT_00018, RS_DEXT_00051)

105 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestDownload
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an instance of the "Request Download" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
AddressableRangeAccess, DiagnosticMemoryByAddress, DiagnosticServiceInstance, Identifiable,
MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
request DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
DownloadClass DownloadClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRequestDownload
in the given context.

Table 5.49: DiagnosticRequestDownload

Class DiagnosticRequestDownloadClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class contains attributes shared by all instances of the "Request Download" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.50: DiagnosticRequestDownloadClass

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticMemoryByAddress

DiagnosticMemoryAddressableRangeAccess

DiagnosticRequestDownload DiagnosticRequestDownloadClass
+requestDownloadClass

0..1
{redefines
serviceClass}

Figure 5.16: Modeling of diagnostic service RequestDownload (0x34)

106 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01027] RequestDownload does not define any sub-functions dThe

diagnostic service RequestDownload does not define any sub-functions, therefore
the value of DiagnosticRequestDownload.category does not need to be con-
strained.c(RS_DEXT_00001, RS_DEXT_00016, RS_DEXT_00051)
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
+serviceClass
DiagnosticServiceInstance
«atpAbstract» 0..1

DiagnosticMemoryByAddress

DiagnosticMemoryAddressableRangeAccess

DiagnosticRequestUpload DiagnosticRequestUploadClass
+requestUploadClass

0..1
{redefines serviceClass}

Figure 5.17: Modeling of diagnostic service RequestDownload (0x35)

Class DiagnosticRequestUpload
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This represents an instance of the "Request Upload" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
AddressableRangeAccess, DiagnosticMemoryByAddress, DiagnosticServiceInstance, Identifiable,
MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
requestUpload DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
Class UploadClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRequestUpload in
the given context.

Table 5.51: DiagnosticRequestUpload

107 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestUploadClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress
Note This meta-class contains attributes shared by all instances of the "Request Upload" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticMemoryByAdresss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.52: DiagnosticRequestUploadClass

[TPS_DEXT_01028] RequestUpload does not define any sub-functions dThe di-

agnostic service RequestUpload does not define any sub-functions, therefore the
value of DiagnosticRequestUpload.category does not need to be constrained.c
(RS_DEXT_00001, RS_DEXT_00017, RS_DEXT_00051)

5.5.6 CommunicationControl

This chapter describes the modeling of diagnostic services CommunicationControl

(0x28). The purpose of this diagnostic service is to enable or disable ISignalIP-
duGroups.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticComControl DiagnosticComControlClass
+comControlClass
+ customSubFunctionNumber: PositiveInteger [0..1]
0..1
{redefines
serviceClass}

+subNodeChannel 0..* +specificChannel 0..*

DiagnosticComControlSubNodeChannel DiagnosticComControlSpecificChannel

+ subNodeNumber: PositiveInteger [0..1] + subnetNumber: PositiveInteger [0..1]

+subNodeChannel 0..1 +allChannels 0..* +specificChannel 0..1

FibexElement
«atpVariation»
CommunicationCluster

+ baudrate: PositiveUnlimitedInteger [0..1]

+ protocolName: String [0..1]
+ protocolVersion: String [0..1]

Figure 5.18: Modeling of diagnostic service CommunicationControl (0x28)

108 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

However, the actual implementation of the enabling or disabling is obviously not exe-
cuted directly within the diagnostic stack. It requires some interaction with the BswM
that in turn implements the enabling algorithm.
Therefore, the meta-class modeled for this purpose does not need to refer to ISig-
nalIPduGroups but implements a mode request to the BswM.
[TPS_DEXT_01057] Allowed values of DiagnosticComControl.category dThe
sub-functions of the diagnostic services CommunicationControl are identified by
means of the attribute DiagnosticComControl.category. Standardized values of
DiagnosticComControl.category are:
• ENABLE_RX_AND_TX
• DISABLE_RX_AND_TX
• ENABLE_RX_AND_DISABLE_TX
• DISABLE_RX_AND_ENABLE_TX
• ENABLE_RX_AND_DISABLE_TX_WITH_ENHANCED_ADDRESS_INFORMATION
• ENABLE_RX_AND_TX_WITH_ENHANCED_ADDRESS_INFORMATION
The meaning of these values is described in the applicable ISO document [16].c(RS_-
DEXT_00001, RS_DEXT_00010, RS_DEXT_00051)
[TPS_DEXT_01029] Correspondence of category values to numerical values
mentioned in the ISO 14229-1 dThe ISO 14229-1 [16] standard document defines
specific numerical values for the sub-functions of the diagnostic service Communica-
tionControl.
The correspondence of the numerical values to the pre-defined values of category
according to [TPS_DEXT_01057] is pretty obvious because the definition of values
defined in [TPS_DEXT_01057] has been directly inspired by the ISO 14229-1 [16]
standard document.c(RS_DEXT_00001, RS_DEXT_00010, RS_DEXT_00051)
[TPS_DEXT_01030] Manufacturer-specific values for sub-functions of service
CommunicationControl dThe ISO 14229-1 [16] standard document, beyond the
standardized numerical values for sub-functions, reserves a numerical range of sub-
Function identifiers for manufacturer-specific use.
In this case it is possible to define further values for category, provided that a custom
prefix is used to avoid potential name clashes with further extensions of the AUTOSAR
standard, namely [TPS_DEXT_01057].c(RS_DEXT_00010, RS_DEXT_00047, RS_-
DEXT_00051)
[TPS_DEXT_01031] Semantics of DiagnosticComControl.customSubFunc-
tionNumber dThe attribute DiagnosticComControl.customSubFunctionNum-
ber has been introduced to allow for the specification of a manufacturer-or supplier-
specific value to represent the custom sub-function in the diagnostic communication.

109 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

The tuple created by the values of attributes DiagnosticComControl.category

and DiagnosticComControl.customSubFunctionNumber fully specifies identifi-
cation of the manufacturer- or supplier-specific sub-function.c(RS_DEXT_00010, RS_-
DEXT_00047, RS_DEXT_00051)
[constr_1334] Existence of DiagnosticComControl.customSubFunctionNum-
ber dThe attribute DiagnosticComControl.customSubFunctionNumber shall
only exist if the value of DiagnosticComControl.category is outside the stan-
dardized set of values as defined by [TPS_DEXT_01057].c()
[constr_1335] Possible values for DiagnosticComControl.customSubFunc-
tionNumber dGiven the fulfillment of [constr_1334], the value of a given Diagnos-
ticComControl.customSubFunctionNumber shall always be within the closed in-
terval 0x40 .. 0x5F (for manufacturer-specific sub-functions) or the closed interval
0x60 .. 0x7E (for supplier-specific sub-functions).c()
[TPS_DEXT_01032] Impact of the DiagnosticComControlClass on the state
management for CommunicationClusters dThe impact of the DiagnosticCom-
ControlClass on the state management for CommunicationClusters can have
two alternative consequences:
• All CommunicationClusters are affected. For this purpose the attribute
allChannels has the ability to identify the applicable CommunicationClus-
ters.
It may seem counterintuitive to require a reference to all applicable Communica-
tionClusters when the expected semantics is actually to define an impact on
all of them.
However, there could be private CommunicationClusters that are not partici-
pating in the diagnostics work-flow: These need to be kept out of scope and there-
fore the explicit identification of applicable CommunicationClusters makes
sense.
• A selected number of CommunicationClusters is affected. This is conceptu-
ally different from the other use case in that it requires an additional attribute that
keeps a subnetNumber that is typically assigned by the OEM role.
c(RS_DEXT_00010)
Class <<atpVariation>> CommunicationCluster (abstract)
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreTopology
5

110 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpVariation>> CommunicationCluster (abstract)
Note The CommunicationCluster is the main element to describe the topological connection of communicating
ECUs.
A cluster describes the ensemble of ECUs, which are linked by a communication medium of arbitrary
topology (bus, star, ring, ...). The nodes within the cluster share the same communication protocol, which
may be event-triggered, time-triggered or a combination of both.
A CommunicationCluster aggregates one or more physical channels.
Tags:vh.latestBindingTime=postBuild
Base ARObject, CollectableElement, FibexElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Subclasses AbstractCanCluster , EthernetCluster, FlexrayCluster, LinCluster, UserDefinedCluster
Attribute Type Mult. Kind Note
baudrate PositiveUnlimitedInteger 0..1 attr Channels speed in bits/s.
physical PhysicalChannel 1..* aggr This relationship defines which channel element belongs
Channel to which cluster. A channel shall be assigned to exactly
one cluster, whereas a cluster may have one or more
channels.
Note: This atpSplitable property has no atp.Splitkey due
to atpVariation (PropertySetPattern).
Stereotypes: atpSplitable; atpVariation
Tags:vh.latestBindingTime=systemDesignTime
protocolName String 0..1 attr The name of the protocol used.
protocolVersion String 0..1 attr The version of the protocol used.

Table 5.53: CommunicationCluster

[constr_1336] Applicable value range for DiagnosticComControlSpecific-

Channel.subnetNumber dThe value of attribute DiagnosticComControlSpeci-
ficChannel.subnetNumber shall be within the closed interval 1 .. 14.c()
Please note that the regulation implied by [constr_1336] has not been introduced on an
arbitrary basis but gets its conceptual background from the ISO 14229-1 [16] standard
document.
Obviously, a diagnostic service with the name CommunicationControl will have
an impact on the enclosing ECU’s mode management. This impact, however, is not
defined by any further attributes or references, the DiagnosticComControl is the
impact.
By defining a DiagnosticComControl and setting the category to one of the applica-
ble values (e.g. ENABLE_RX_AND_TX), it is possible to express the intended semantics
to the full extent.
[constr_1337] Allowed value range for attribute DiagnosticComControlSubN-
odeChannel.subNodeNumber dThe value of attribute DiagnosticComControl-
SubNodeChannel.subNodeNumber shall not exceed the closed interval 0 .. 65535.c
()

111 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01074] Difference between the attributes DiagnosticComControl-

Class.specificChannel and DiagnosticComControlClass.subNodeChan-
nel dThe semantical difference between the attributes DiagnosticComControl-
Class.specificChannel and DiagnosticComControlClass.subNodeChan-
nel is that DiagnosticComControlClass.specificChannel actually refers
to a CommunicationCluster whereas DiagnosticComControlClass.subN-
odeChannel basically refers to a CommunicationCluster to which the nodes with
the given identification numbers are connected.c(RS_DEXT_00010)
Class DiagnosticComControl
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl
Note This represents an instance of the "Communication Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticCommunicationControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
comControl DiagnosticComControl 0..1 ref This reference substantiates that abstract reference in the
Class Class role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticComControl in the
given context.
customSub PositiveInteger 0..1 attr This attribute shall be used to define a custom
Function sub-function number if none of the standardized values of
Number category shall be used.

Table 5.54: DiagnosticComControl

Class DiagnosticComControlSpecificChannel
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl
Note This represents the ability to add further attributes to the definition of a specific channel that is subject to
the diagnostic service "communication control".
Base ARObject
Attribute Type Mult. Kind Note
specificChannel CommunicationCluster 0..1 ref This represents the affected CommunicationClusters in
the role specificChannel
subnetNumber PositiveInteger 0..1 attr This represents the applicable subnet number (which is
an arbitrary number ranging from 1..14)

Table 5.55: DiagnosticComControlSpecificChannel

Class DiagnosticComControlClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl
Note This meta-class contains attributes shared by all instances of the "Communication Control" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticCommunicationControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
5

112 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticComControlClass
allChannels CommunicationCluster * ref This reference represents the semantics that all available
channels shall be affected. It is still necessary to refer to
individual CommunicatuionClusters because there could
be private CommunicationClusters in the System Extract
that are not subject to the service "communication
control".
By referring to the applicable CommunicationClusters it
can be made sure that only the affected Communication
Clusters are accessed.
specificChannel DiagnosticComControl * aggr This represents the ability to add additional attributes to
SpecificChannel the case that only specific channels are supposed to be
considered,
subNode DiagnosticComControl * aggr This attribute represents the ability to add further
Channel SubNodeChannel attributes to the definition of a specific sub-node channel
that is subject to the diagnostic service "communication
control".
Table 5.56: DiagnosticComControlClass

Class DiagnosticComControlSubNodeChannel
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl
Note This represents the ability to add further attributes to the definition of a specific sub-node channel that is
subject to the diagnostic service "communication control".
Base ARObject
Attribute Type Mult. Kind Note
subNode CommunicationCluster 0..1 ref This represents the affected CommunicationClusters in
Channel the role subNodeChannel
subNode PositiveInteger 0..1 attr This represents the applicable subNode number. The
Number value corresponds to the request message parameter
nodeIdentificationNumber of diagnostic service
CommunicationControl (0x28).

Table 5.57: DiagnosticComControlSubNodeChannel

5.5.7 DynamicallyDefineDataIdentifier

This chapter describes the modeling of diagnostic services DynamicallyDefine-

DataIdentifier (0x2C). The purpose of the service is to allow for defining data
identifiers (DID) at run-time.
By this means it is possible to combine existing diagnostic data into a single DID.
This semantics is reflected by the modeling of the meta-class DiagnosticDynami-
callyDefineDataIdentifier that refers to a DiagnosticDynamicDataIden-
tifier in the role dataIdentifier.
Also, the DiagnosticDynamicallyDefineDataIdentifier inherits a reference
to accessPermission from DiagnosticServiceInstance.

113 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticDynamicallyDefineDataIdentifier

+ maxSourceElement: PositiveInteger [0..1]

0..1
{redefines
+dataIdentifier 0..1 +dynamicallyDefineDataIdentifierClass serviceClass}
DiagnosticAbstractDataIdentifier
DiagnosticDynamicallyDefineDataIdentifierClass
DiagnosticDynamicDataIdentifier
+ checkPerSourceId: Boolean [0..1]
+ configurationHandling: DiagnosticHandleDDDIConfigurationEnum [0..1]
+ subfunction: DiagnosticDynamicallyDefineDataIdentifierSubfunctionEnum [0..*]

«enumeration» «enumeration»
DiagnosticHandleDDDIConfigurationEnum DiagnosticDynamicallyDefineDataIdentifierSubfunctionEnum

volatile defineByIdentifier
nonVolatile defineByMemoryAddress
clearDynamicallyDefineDataIdentifier

Figure 5.19: Modeling of diagnostic service DynamicallyDefineDataIdentifier

(0x2C)

[constr_1421] Consistency of DiagnosticDynamicallyDefineDataIdenti-

fierClass.subfunction dThe values of DiagnosticDynamicallyDefine-
DataIdentifierClass.subfunction shall not repeat, i.e. every value of Diag-
nosticDynamicallyDefineDataIdentifierSubfunctionEnum shall at most
appear once in the subfunction attribute.c()
Class DiagnosticDynamicallyDefineDataIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineDataIdentifier
Note This represents an instance of the "Dynamically Define Data Identifier" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticDynamicallyDefineDataIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataIdentifier DiagnosticDynamicData 0..1 ref This represents the applicable DiagnosticDynamicData
Identifier Identfier.
dynamically DiagnosticDynamically 0..1 ref This reference substantiates that abstract reference in the
DefineData DefineDataIdentifier role serviceClass for this specific concrete class.
IdentifierClass Class
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticDynamicallyDefine
DataIdentifier in the given context.
maxSource PositiveInteger 0..1 attr This represents the maximum number of source elements
Element of the dynamically created DID.

Table 5.58: DiagnosticDynamicallyDefineDataIdentifier

114 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1808] Existence of reference DiagnosticDynamicallyDefine-

DataIdentifier.dataIdentifier dFor each DiagnosticDynamicallyDe-
fineDataIdentifier, the reference to DiagnosticDynamicDataIdentifier
in the role dataIdentifier shall exist at the time when the DEXT is complete.c()
Class DiagnosticDynamicallyDefineDataIdentifierClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineDataIdentifier
Note This meta-class contains attributes shared by all instances of the "Dynamically Define Data Identifier"
diagnostic service.
Tags:atp.recommendedPackage=DiagnosticDynamicallyDefineDataIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
checkPer Boolean 0..1 attr If set to TRUE, the Dcm module shall check the session,
SourceId security and mode dependencies per source DIDs with a
ReadDataByIdentifier (0x22) with DID in the range 0x
F200 to 0xF3FF.
If set to FALSE. the Dcm module shall not check the
session, security and mode dependencies per source
DIDs with a ReadDataByIdentifier (0x22) with DID in the
range 0xF200 to 0xF3FF.
configuration DiagnosticHandleDDDI 0..1 attr This configuration switch defines whether DDDID
Handling ConfigurationEnum definition is handled as non-volatile information or not.
subfunction DiagnosticDynamically * attr This attribute contains a list of applicable subfunctions for
DefineDataIdentifier all DiagnosticDynamicallyDefineDataIdentifier that
SubfunctionEnum reference the DiagnosticDynamicallyDefineDataIdentifier
Class.

Table 5.59: DiagnosticDynamicallyDefineDataIdentifierClass

Enumeration DiagnosticHandleDDDIConfigurationEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineData
Identifier
Note This meta-class represents the options for controlling how the configuration of the DynamicallyDefine
DataIdentifiers is done in the given context.
Literal Description
nonVolatile This indicates that the configuration of DynamicallyDefineDataIdentifier shall be stored as non-volatile
data.
Tags:atp.EnumerationLiteralIndex=0
volatile This indicates that the configuration of DynamicallyDefineDataIdentifier shall be handled as volatile
data.
Tags:atp.EnumerationLiteralIndex=1

Table 5.60: DiagnosticHandleDDDIConfigurationEnum

Enumeration DiagnosticDynamicallyDefineDataIdentifierSubfunctionEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineData
Identifier
Note This meta-class contains a list of possible subfunctions for the UDS service 0x2C.
Literal Description
5

115 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticDynamicallyDefineDataIdentifierSubfunctionEnum
clearDynamically Clear the specified dynamic data identifier.
DefineDataIdentifier
Tags:atp.EnumerationLiteralIndex=0
defineByIdentifier The definition of dynamic data identifier shall be done via a reference to a diagnostic data identifier.
Tags:atp.EnumerationLiteralIndex=1
defineByMemory The definition of dynamic data identifier shall be done via a reference to a memory address.
Address
Tags:atp.EnumerationLiteralIndex=2

Table 5.61: DiagnosticDynamicallyDefineDataIdentifierSubfunctionEnum

5.5.8 ReadDataByPeriodicIdentifier

This chapter describes the modeling of diagnostic services ReadDataByPeriodicI-

dentifier (0x2A).
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticReadDataByPeriodicID DiagnosticReadDataByPeriodicIDClass
+readDataClass
+ maxPeriodicDidToRead: PositiveInteger [0..1]
0..1 + schedulerMaxNumber: PositiveInteger [0..1]
{redefines serviceClass}

+periodicRate 0..*
«enumeration»
DiagnosticPeriodicRateCategoryEnum DiagnosticPeriodicRate

periodicRateSlow + period: TimeValue [0..1]

periodicRateMedium + periodicRateCategory: DiagnosticPeriodicRateCategoryEnum [0..1]
periodicRateFast

Figure 5.20: Modeling of diagnostic service ReadDataByPeriodicIdentifier (0x2A)

[constr_1338] Maximum number of aggregated DiagnosticReadDataByPeri-

odicIDClass.periodicRate dThe number of aggregated periodicRate within
the context of one DiagnosticReadDataByPeriodicIDClass shall be within the
closed interval 1..3.c()

116 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticReadDataByPeriodicID
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID
Note This represents an instance of the "Read Data by periodic Identifier" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticReadDataByPeriodicIds
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
readDataClass DiagnosticReadDataBy 0..1 ref This reference substantiates that abstract reference in the
PeriodicIDClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticReadDataBy
PeriodicID in the given context.

Table 5.62: DiagnosticReadDataByPeriodicID

Class DiagnosticReadDataByPeriodicIDClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID
Note This meta-class contains attributes shared by all instances of the "Read Data by periodic Identifier"
diagnostic service.
Tags:atp.recommendedPackage=DiagnosticReadDataByPeriodicIds
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
maxPeriodicDid PositiveInteger 0..1 attr This represents the maximum number of data identifiers
ToRead that can be included in one request.
periodicRate DiagnosticPeriodicRate * aggr This represents the description of a collection of periodic
rates in which the service can be executed.
schedulerMax PositiveInteger 0..1 attr This represents the maximum number of periodic data
Number identifiers that can be scheduled in parallel.

Table 5.63: DiagnosticReadDataByPeriodicIDClass

[constr_1810] Existence of aggregation DiagnosticReadDataByPeriodicID-

Class.periodicRate dFor each DiagnosticReadDataByPeriodicIDClass,
the aggregation of DiagnosticPeriodicRate in the role periodicRate shall exist
at least once at the time when the DEXT is complete.c()
[constr_1811] Existence of attribute DiagnosticReadDataByPeriodicID-
Class.maxPeriodicDidToRead dFor each DiagnosticReadDataByPeriodi-
cIDClass, the attribute maxPeriodicDidToRead shall exist at least once at the
time when the DEXT is complete.c()
[constr_1812] Existence of attribute DiagnosticReadDataByPeriodicID-
Class.schedulerMaxNumber dFor each DiagnosticReadDataByPeriodicID-
Class, the attribute schedulerMaxNumber shall exist at least once at the time when
the DEXT is complete.c()

117 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticPeriodicRate
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID
Note This represents the ability to define a periodic rate for the specification of the "read data by periodic ID"
diagnostic service.
Base ARObject
Attribute Type Mult. Kind Note
period TimeValue 0..1 attr This represents the period of the DiagnosticPeriodicRate
in seconds.
periodicRate DiagnosticPeriodicRate 0..1 attr This attribute represents the category of the periodic rate.
Category CategoryEnum

Table 5.64: DiagnosticPeriodicRate

[constr_1763] Existence of attribute DiagnosticPeriodicRate.periodi-

cRateCategory dFor each DiagnosticPeriodicRate, the attribute periodi-
cRateCategory shall exist at the time when the DEXT is complete.c()
Enumeration DiagnosticPeriodicRateCategoryEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID
Note This meta-class provides possible values for the setting of the periodic rate.
Literal Description
periodicRateFast This value represents a fast periodic rate.
Tags:atp.EnumerationLiteralIndex=0
periodicRate This value represents a medium periodic rate.
Medium
Tags:atp.EnumerationLiteralIndex=1
periodicRateSlow This value represents a slow periodic rate.
Tags:atp.EnumerationLiteralIndex=2

Table 5.65: DiagnosticPeriodicRateCategoryEnum

The meaning of the values defined in DiagnosticPeriodicRateCategoryEnum is

described in the applicable ISO document [16].

5.5.9 ControlDTCSetting

This chapter describes the modeling of diagnostic services ControlDTCSetting

(0x85). The purpose of the diagnostic service is to let the tester tell the diagnostic
stack to either stop or resume the updating of a diagnostic trouble code.
[TPS_DEXT_01075] standardized values for the attribute DiagnosticCon-
trolDTCSetting.category dAUTOSAR does not standardize any of the possible
values for the attribute DiagnosticControlDTCSetting.category.c(RS_DEXT_-
00001, RS_DEXT_00021, RS_DEXT_00051)

118 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticControlDTCSetting DiagnosticControlDTCSettingClass
+dtcSettingClass
+ controlOptionRecordPresent: Boolean [0..1]
0..1
{redefines
serviceClass}

Figure 5.21: Modeling of diagnostic service ControlDTCSetting (0x85)

Class DiagnosticControlDTCSetting
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ControlDTCSetting
Note This represents an instance of the "Control DTC Setting" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticControlDtcSettings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dtcSettingClass DiagnosticControlDTC 0..1 ref This reference substantiates that abstract reference in the
SettingClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticControlDTCSetting
in the given context.

Table 5.66: DiagnosticControlDTCSetting

Class DiagnosticControlDTCSettingClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ControlDTCSetting
Note This meta-class contains attributes shared by all instances of the "Control DTC Setting" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticControlDtcSettings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
controlOption Boolean 0..1 attr This represents the decision whether the DTCSetting
RecordPresent ControlOptionRecord (see ISO 14229-1) is in general
supported in the request message.

Table 5.67: DiagnosticControlDTCSettingClass

119 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

5.5.10 ResponseOnEvent

This chapter describes the modeling of diagnostic services ResponseOnEvent

(0x86). The purpose of this service is to instruct the AUTOSAR diagnostic stack with
respect to the starting or stopping of sending responses to a specific event to the tester.
Each DiagnosticResponseOnEvent provides the ability to define a collection of
triggers (modelled by means of the abstract meta-class DiagnosticResponseOn-
EventTrigger) that cause the sending of a response message.
The actual trigger behavior is defined by the sub-class of DiagnosticResponseOn-
EventTrigger used to specify whether the trigger shall be created in response to a
data change or in response to a DTC change.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticResponseOnEvent +responseOnEventClass DiagnosticResponseOnEventClass

+ responseOnEventAction: DiagnosticResponseOnEventActionEnum [0..1] + interMessageTime: TimeValue [0..1]

0..1
+ storeEventSupport: DiagnosticStoreEventSupportEnum [0..1]
{redefines serviceClass}

DiagnosticEventWindow
+eventWindow
+ eventWindowTime: DiagnosticEventWindowTimeEnum [0..1]
0..* + storageStateEvaluation: Boolean [0..1]

DiagnosticResponseOnEventTrigger
+event + initialEventStatus: DiagnosticInitialEventStatusEnum [0..1]

0..*

«enumeration»
DiagnosticEventWindowTimeEnum DiagnosticDtcChangeTrigger DiagnosticDataChangeTrigger

eventWindowInfinite + dtcStatusMask: PositiveInteger [0..1]

eventWindowCurrentAndFollowingCycle
eventWindowCurrentCycle

«enumeration»
DiagnosticResponseOnEventActionEnum «enumeration»
DiagnosticStoreEventSupportEnum +dataIdentifier 0..1
stop
start noStoreEvent DiagnosticAbstractDataIdentifier
clear storeEvent
DiagnosticDataIdentifier
report all
+ didSize: PositiveInteger [0..1]
+ representsVin: Boolean [0..1]
«enumeration»
DiagnosticInitialEventStatusEnum

returnOnEventCleared
returnOnEventStopped

Figure 5.22: Modeling of diagnostic service ResponseOnEvent (0x86)

[TPS_DEXT_01033] Semantics of triggers in the context of a DiagnosticRe-

sponseOnEvent dThe semantics of a trigger in the context of a DiagnosticRe-
sponseOnEvent can be defined in two ways:

120 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• The meta-class DiagnosticDataChangeTrigger allows for defining a trig-

ger that activates on the change of the value of the referenced (in the role
dataIdentifier) DiagnosticDataIdentifier.
• The meta-class DiagnosticDtcChangeTrigger allows for defining a trigger
for the activation of the service. The entire proceedings of how the trigger ac-
tivates and what DTCs are affected in managed at run-time and therefore no
further configuration is required at this point.
c(RS_DEXT_00022)
[constr_1365] Multiplicity of DiagnosticResponseOnEvent.event dThe multi-
plicity of DiagnosticResponseOnEvent.event shall not exceed the upper bound
255.c()
[constr_1366] Event ID in the context of diagnostic service ResponseOnEvent
shall be unique dThe value of DiagnosticResponseOnEvent.event.dataIden-
tifier.id shall be unique within the context of a given DiagnosticResponseOn-
Event.c()
[constr_1633] Existence of DiagnosticResponseOnEvent.event vs. Diag-
nosticResponseOnEvent.responseOnEventAction dThe existence of attributes
DiagnosticResponseOnEvent.event vs. DiagnosticResponseOnEvent.re-
sponseOnEventAction is mutually exclusive, i.e. one shall only exist if the other
does not exist.c()
Class DiagnosticResponseOnEvent
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents an instance of the "Response on Event" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticResponseOnEvents
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
event DiagnosticResponseOn * aggr This represents the collection of DiagnosticResponseOn
EventTrigger EventTriggers defined in the context of the enclosing
DiagnosticResponseOnEvent.
eventWindow DiagnosticEventWindow * aggr This represents the applicable DiagnosticEventWindows
responseOn DiagnosticResponseOn 0..1 attr Defines sub-functions of the service ResponseOnEvent.
EventAction EventActionEnum
responseOn DiagnosticResponseOn 0..1 ref This reference substantiates that abstract reference in the
EventClass EventClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticResponseOnEvent
in the given context.
storeEvent DiagnosticStoreEvent 0..1 attr Defines how a specific event shall be handled.
Support SupportEnum

Table 5.68: DiagnosticResponseOnEvent

121 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticResponseOnEventClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to define common properties for alle instances of the "Response on Event"
diagnostic service.
Tags:atp.recommendedPackage=DiagnosticResponseOnEvents
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
interMessage TimeValue 0..1 attr Provide the minimum time in seconds between two
Time consecutive transmissions of an ROE event.

Table 5.69: DiagnosticResponseOnEventClass

Class DiagnosticEventWindow
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to define the characteristics of the applicable event window
Base ARObject
Attribute Type Mult. Kind Note
eventWindow DiagnosticEventWindow 0..1 attr This attribute clarifies the validity of the eventWindow
Time TimeEnum
storageState Boolean 0..1 attr If this attribute is set to TRUE the StorageStateBit will be
Evaluation evaluated if this EventWindowTime is requested.

Table 5.70: DiagnosticEventWindow

[constr_1813] Existence of reference DiagnosticEventWindow.eventWindow-

Time dFor each DiagnosticEventWindow, attribute eventWindowTime shall exist
at the time when the DEXT is complete.c()
[constr_1814] Existence of reference DiagnosticEventWindow.storageSta-
teEvaluation dFor each DiagnosticEventWindow, attribute storageStateE-
valuation shall exist at the time when the DEXT is complete.c()
Class DiagnosticResponseOnEventTrigger (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to further specify the events that are associated with the execution of the
diagnostic service.
Base ARObject
Subclasses DiagnosticDataChangeTrigger, DiagnosticDtcChangeTrigger
Attribute Type Mult. Kind Note
initialEvent DiagnosticInitialEvent 0..1 attr This represents the initial status of the enclosing
Status StatusEnum DiagnosticResponseOnEventTrigger.

Table 5.71: DiagnosticResponseOnEventTrigger

122 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticDataChangeTrigger
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to define a trigger based on the change of a given DiagnosticDataIdentifier.
Base ARObject, DiagnosticResponseOnEventTrigger
Attribute Type Mult. Kind Note
dataIdentifier DiagnosticDataIdentifier 0..1 ref This represents the corresponding DiagnosticData
Identifier.
Table 5.72: DiagnosticDataChangeTrigger

Class DiagnosticDtcChangeTrigger
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to define a trigger that executes on the change of any DiagnosticTroubleCode.
Base ARObject, DiagnosticResponseOnEventTrigger
Attribute Type Mult. Kind Note
dtcStatusMask PositiveInteger 0..1 attr This attribute represents the ability to define a status
mask for the triggering of an ROE response on the
change of a DTC.

Table 5.73: DiagnosticDtcChangeTrigger

Enumeration DiagnosticInitialEventStatusEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to define an initial status for the ROE service.
Literal Description
returnOnEvent This means that the ResponseOnEvent is initially cleared.
Cleared
Tags:atp.EnumerationLiteralIndex=0
returnOnEvent This means that the ResponseOnEvent is initially stopped.
Stopped
Tags:atp.EnumerationLiteralIndex=1

Table 5.74: DiagnosticInitialEventStatusEnum

Enumeration DiagnosticEventWindowTimeEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This represents the ability to define the semantics of the event window.
Literal Description
eventWindow This means that the window extends to this and the following cycle.
CurrentAnd
Tags:atp.EnumerationLiteralIndex=0
FollowingCycle
eventWindow This means that the window is limited to the current cycle.
CurrentCycle
Tags:atp.EnumerationLiteralIndex=1
eventWindowInfinite This means that the window extents without a border.
Tags:atp.EnumerationLiteralIndex=2

Table 5.75: DiagnosticEventWindowTimeEnum

123 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Enumeration DiagnosticStoreEventSupportEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This meta-class has the ability to define how a specific event in the context of the UDS service
ResponseOnEvent shall be handled.
Literal Description
all The server supports both, storing and not storing the event.
Tags:atp.EnumerationLiteralIndex=2
noStoreEvent The event terminates when the server is powered down.
Tags:atp.EnumerationLiteralIndex=0
storeEvent The event is persisted over a power down cycle.
Tags:atp.EnumerationLiteralIndex=1

Table 5.76: DiagnosticStoreEventSupportEnum

Enumeration DiagnosticResponseOnEventActionEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent
Note This meta-class has the ability to define sub-functions of the UDS service ResponseOnEvent.
Literal Description
clear Clears the configured events.
Tags:atp.EnumerationLiteralIndex=2
report Reports the activated events.
Tags:atp.EnumerationLiteralIndex=3
start Starts the response on event service.
Tags:atp.EnumerationLiteralIndex=1
stop Stops the response on event service.
Tags:atp.EnumerationLiteralIndex=0

Table 5.77: DiagnosticResponseOnEventActionEnum

5.5.11 ReadDTCInformation

This chapter describes the modeling of diagnostic services ReadDTCInformation

(0x19). The purpose of this service is to enable a tester to read a Diagnostic Trou-
ble Code from the AUTOSAR Dcm [10] (that, in turn, fetches the information from the
AUTOSAR Dem [11]).
[TPS_DEXT_01034] Sub-functions of the service ReadDTCInformation dThe di-
agnostics service ReadDTCInformation defines a number of sub-functions that are,
as far as the modeling in AUTOSAR goes, identified by a textual identifier.
These sub-functions are not modeled explicitly but can be specified by defining a
DiagnosticReadDTCInformation and by setting the DiagnosticReadDTCIn-
formation.category to the identifier of the respective sub-function.
The possible values, as far as the AUTOSAR standard is concerned, are defined by
[TPS_DEXT_01060].c(RS_DEXT_00006, RS_DEXT_00051)

124 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticReadDTCInformation DiagnosticReadDTCInformationClass
+readDTCInformationClass

0..1
{redefines serviceClass}

Figure 5.23: Modeling of diagnostic service ReadDTCInformation (0x19)

[TPS_DEXT_01060] Applicable values for DiagnosticReadDTCInformation.

category dThe following values of the attribute DiagnosticReadDTCInforma-
tion.category are standardized by AUTOSAR:
• REPORT_NUMBER_OF_DTC_BY_STATUS_MASK
• REPORT_DTC_BY_STATUS_MASK
• REPORT_MIRROR_MEMORY_DTC_BY_STATUS_MASK
• REPORT_NUMBER_OF_MIRROR_MEMORY_DTC_BY_STATUS_MASK
• REPORT_NUMBER_OF_EMISSIONS_OBD_DTC_BY_STATUS_MASK
• REPORT_EMISSIONS_OBD_DTC_BY_STATUS_MASK
• REPORT_DTC_SNAPSHOT_IDENTIFICATION
• REPORT_DTC_SNAPSHOT_RECORD_BY_DTC_NUMBER
• REPORT_DTC_STORED_DATA_BY_RECORD_NUMBER
• REPORT_DTC_EXT_DATA_RECORD_BY_DTC_NUMBER
• REPORT_MIRROR_MEMORY_DTC_EXT_DATA_RECORD_BY_DTC_NUMBER
• REPORT_NUMBER_OF_DTC_BY_SEVERITY_MASK_RECORD
• REPORT_DTC_BY_SEVERITY_MASK_RECORD
• REPORT_SEVERITY_INFORMATION_OF_DTC
• REPORT_SUPPORTED_DTC
• REPORT_FIRST_TEST_FAILED_DTC
• REPORT_FIRST_CONFIRMED_DTC
• REPORT_MOST_RECENT_TEST_FAILED_DTC
• REPORT_MOST_RECENT_CONFIRMED_DTC

125 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• REPORT_DTC_FAULT_DETECTION_COUNTER
• REPORT_DTC_WITH_PERMANENT_STATUS
• REPORT_DTC_EXT_DATA_RECORD_BY_RECORD_NUMBER
• REPORT_USER_DEF_MEMORY_DTC_BY_STATUS_MASK
• REPORT_USER_DEF_MEMORY_DTC_SNAPSHOT_RECORD_BY_DTC_NUMBER
• REPORT_USER_DEF_MEMORY_DTC_EXT_DATA_RECORD_BY_DTC_NUMBER
• REPORT_WWH_OBD_DTC_BY_MASK_RECORD
• REPORT_WWH_OBD_DTC_WITH_PERMANENT_STATUS
The meanings of these values are described in the applicable ISO document (ISO
14229-1) [16].c(RS_DEXT_00001, RS_DEXT_00006, RS_DEXT_00051)
Please note that there is nothing to configure for DiagnosticReadDTCInformation
beyond its mere existence.
Class DiagnosticReadDTCInformation
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ReadDTCInformation
Note This represents an instance of the "Read DTC Information" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticReadDtcInformations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
read DiagnosticReadDTC 0..1 ref This reference substantiates that abstract reference in the
DTCInformation InformationClass role serviceClass for this specific concrete class.
Class
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRead
DTCInformation in the given context.

Table 5.78: DiagnosticReadDTCInformation

Class DiagnosticReadDTCInformationClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::ReadDTCInformation
Note This meta-class contains attributes shared by all instances of the "ReadDTCInformation" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticReadDtcInformations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.79: DiagnosticReadDTCInformationClass

126 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

5.5.12 RoutineControl

This chapter describes the modeling of diagnostic services RoutineControl (0x31).

The purpose of this diagnostic service is to execute a piece of code, a Diagnostic
Routine, on the diagnostic stack at the request of the tester.
Diagnostic Routines consist of up to three possible components:
• Start Routine
• Stop Routine
• Request Routine Results
The impact of this architecture on the meta-model is described by [TPS_DEXT_01077]:
[TPS_DEXT_01077] Modeling of DiagnosticRoutine dFrom the meta-modeling
point of view, the semantics of DiagnosticRoutine is created by aggregating three
further meta-classes that represent subfunctions of service RoutineControl (0x31):
• DiagnosticStartRoutine
• DiagnosticStopRoutine
• DiagnosticRequestRoutineResults
c(RS_DEXT_00015)
Identifiable
DiagnosticRoutineSubfunction

DiagnosticStartRoutine DiagnosticStopRoutine DiagnosticRequestRoutineResults

Figure 5.24: Abstract base class for subfunctions of diagnostic service RoutineCon-
trol (0x31)

Class DiagnosticRoutineSubfunction (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class acts as an abstract base class to routine subfunctions.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Subclasses DiagnosticRequestRoutineResults, DiagnosticStartRoutine, DiagnosticStopRoutine
Attribute Type Mult. Kind Note
access DiagnosticAccess 0..1 ref This reference represents the access permission of the
Permission Permission owning routine subfunction.

Table 5.80: DiagnosticRoutineSubfunction

127 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01088] Semantics of DiagnosticRoutine.id dThe attribute Diag-

nosticRoutine.id represents the so-called identifier of the DiagnosticRoutine.c
(RS_DEXT_00036)
[TPS_DEXT_01078] Not possible to use the attribute category for the identifica-
tion of the sub-function of diagnostic service RoutineControl dIn the case of
DiagnosticRoutine, it is not possible to use the attribute category for the identi-
fication of the sub-function.c(RS_DEXT_00015, RS_DEXT_00051)
The sub-functions actually have different properties i.e. the arguments to a Diagnos-
ticRoutine that require a dedicated modeling for this purpose.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass DiagnosticServiceClass
«atpAbstract» 0..1

DiagnosticRoutineControl DiagnosticRoutineControlClass
+routineControlClass

0..1
{redefines serviceClass}

+routine 1

DiagnosticCommonElement
DiagnosticRoutine

+ routineInfo: PositiveInteger [0..1]

«atpVariation»
+ id: PositiveInteger [0..1]

+start 0..1 +stop 0..1 +requestResult 0..1

DiagnosticRoutineSubfunction DiagnosticRoutineSubfunction DiagnosticRoutineSubfunction

DiagnosticStartRoutine DiagnosticStopRoutine DiagnosticRequestRoutineResults

+request 0..* +response 0..* +request 0..* +response 0..* +request 0..* +response 0..*

DiagnosticParameter

«atpIdentityContributor»
+ bitOffset: PositiveInteger [0..1]

«atpVariation,atpSplitable»

+dataElement 0..1
  

   
Identifiable 
DiagnosticDataElement

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 5.25: Modeling of diagnostic service RoutineControl (0x31)

[TPS_DEXT_01079] Modeling of the arguments to a DiagnosticRoutine dThe

arguments to a DiagnosticRoutine are modeled by means of DiagnosticPa-
rameter that is aggregated in the following roles:
• DiagnosticStartRoutine.request
• DiagnosticStartRoutine.response

128 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• DiagnosticStopRoutine.request
• DiagnosticStopRoutine.response
• DiagnosticRequestRoutineResults.response
• DiagnosticRequestRoutineResults.request
• DiagnosticRequestRoutineResults.response
c(RS_DEXT_00015)
A DiagnosticParameter, in turn, aggregates a DiagnosticDataElement (see
section 4.2) in the role dataElement.
[TPS_DEXT_01080] Diagnostic Routine needs to be started dISO 14229-1 [16]
does not foresee the existence of a Diagnostic Routine that is already executing
at boot time. Therefore, a Diagnostic Routine needs to be started at some point
in order to make sense of it.c(RS_DEXT_00015)
[constr_1339] Existence of DiagnosticRoutine.start dIn a complete Diagnos-
ticExtract, the attribute DiagnosticRoutine.start shall always exist for any
given DiagnosticRoutine.c()
[TPS_DEXT_01035] Existence of DiagnosticRoutine.stop and Diagnosti-
cRoutine.requestResult dIn contrast to DiagnosticRoutine.start (as clari-
fied by [constr_1339]), the existence of DiagnosticRoutine.stop and Diagnos-
ticRoutine.requestResult is truly optional.c(RS_DEXT_00015)
[constr_1340] Consistency of DiagnosticServiceSwMapping with respect
to synchronously called DiagnosticRoutines dEach DiagnosticSer-
viceSwMapping that references a DiagnosticRoutineControl that only
aggregates a DiagnosticStartRoutine in the role start shall only reference a
SwcServiceDependency or BswServiceDependency that in turn aggregates a
DiagnosticRoutineNeeds with attribute diagRoutineType set to Diagnosti-
cRoutineTypeEnum.synchronous.c()
[constr_1341] Consistency of DiagnosticServiceSwMapping with respect
to asynchronously called DiagnosticRoutines dEach DiagnosticSer-
viceSwMapping that references a DiagnosticRoutineControl that aggregates
a DiagnosticStopRoutine and/or DiagnosticRequestRoutineResults in the
role stop or requestResult shall only reference a SwcServiceDependency or
BswServiceDependency that in turn aggregates a DiagnosticRoutineNeeds
with attribute diagRoutineType set to DiagnosticRoutineTypeEnum.asyn-
chronous.c()
[TPS_DEXT_01049] Consistency of DiagnosticServiceSwMapping with re-
spect to routine IDs dFor each DiagnosticServiceSwMapping that references
a DiagnosticRoutineNeeds and a DiagnosticRoutineControl, the value of
DiagnosticRoutineNeeds.ridNumber shall be ignored and the value of Diag-
nosticRoutineControl.routine.id shall be taken instead.c(RS_DEXT_00015,
RS_DEXT_00052)

129 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement
DiagnosticAccessPermission

+accessPermission 0..1

Identifiable
DiagnosticRoutineSubfunction

Figure 5.26: Permission is granted per subfunction

The DiagnosticRoutineControl service is the only UDS service with both sub-
function and identifier. ISO 14229-1 [16] treats the service with respect to session and
security as a service with identifier.
In other words a DiagnosticRoutine—with its three subfunctions start, stop and
requestResult—for the same identifier can have only DiagnosticAccessPer-
mission with the same referenced DiagnosticSession and DiagnosticSecu-
rityLevel.
However, different DiagnosticEnvironmentalConditions may exist for the sub-
functions of a DiagnosticRoutine with the same identifier (DiagnosticRoutine.
id).
[constr_1772] Unique DiagnosticSession and DiagnosticSecurityLevel
for diagnostic routines that have the same identifier dAll DiagnosticAc-
cessPermissions referenced from DiagnosticRoutines where attribute Diag-
nosticRoutine.id has the identical value shall refer to the identical set of Diag-
nosticSession and DiagnosticSecurityLevel.c()
For this purpose, the reference from the abstract base class1 DiagnosticRoutine-
Subfunction to DiagnosticAccessPermission in the role accessPermission
exists (see Figure 5.26).
Consequently, the reference from meta-class DiagnosticRoutineControl (via its
abstract base class DiagnosticServiceInstance) to meta-class Diagnosti-
cAccessPermission has no meaning.
[constr_1612] Reference from DiagnosticRoutineControl to DiagnosticAc-
cessPermission has no meaning dThe reference from DiagnosticRoutineCon-
trol (via its abstract base class DiagnosticServiceInstance) in the role
accessPermission to meta-class DiagnosticAccessPermission shall not be
used.c()
1
of meta-classes DiagnosticStartRoutine, DiagnosticStopRoutine, and DiagnosticRe-
questRoutineResults

130 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRoutine
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to define a diagnostic routine.
Tags:atp.recommendedPackage=DiagnosticRoutines
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
id PositiveInteger 0..1 attr This is the numerical identifier used to identify the
DiagnosticRoutine in the scope of diagnostic workflow
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
requestResult DiagnosticRequest 0..1 aggr This represents the ability to request the result of a
RoutineResults running routine.
routineInfo PositiveInteger 0..1 attr This represents the routine info byte. The info byte
contains a manufacturer-specific value (for the
identification of record identifiers) that is reported to the
tester.
Other use cases for this attribute are mentioned in ISO
27145 and ISO 26021.
start DiagnosticStartRoutine 0..1 aggr This represents the ability to start a routine
stop DiagnosticStopRoutine 0..1 aggr This represents the ability to stop a running routine.

Table 5.81: DiagnosticRoutine

[constr_1815] Existence of attribute DiagnosticRoutine.id dFor each Diag-

nosticRoutine, the attribute id shall exist at least once at the time when the DEXT
is complete.c()
Class DiagnosticStartRoutine
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This represents the ability to start a diagnostic routine.
Base ARObject, DiagnosticRoutineSubfunction, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
request DiagnosticParameter * aggr This represents the request parameters.
response DiagnosticParameter * aggr This represents the response parameters.

Table 5.82: DiagnosticStartRoutine

Class DiagnosticStopRoutine
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This represents the ability to stop a diagnostic routine.
Base ARObject, DiagnosticRoutineSubfunction, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
request DiagnosticParameter * aggr This represents the request parameters.
response DiagnosticParameter * aggr This represents the response parameters.

Table 5.83: DiagnosticStopRoutine

131 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestRoutineResults
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to define the result of a diagnostic routine execution.
Base ARObject, DiagnosticRoutineSubfunction, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
request DiagnosticParameter * aggr This represents the request parameters.
response DiagnosticParameter * aggr This represents the response parameters.

Table 5.84: DiagnosticRequestRoutineResults

Class DiagnosticRoutineControl
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::RoutineControl
Note This represents an instance of the "Routine Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRoutineControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
routine DiagnosticRoutine 1 ref This refers to the applicable DiagnosticRoutine.
routineControl DiagnosticRoutine 0..1 ref This reference substantiates that abstract reference in the
Class ControlClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRoutineControl in
the given context.

Table 5.85: DiagnosticRoutineControl

Class DiagnosticRoutineControlClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::RoutineControl
Note This meta-class contains attributes shared by all instances of the "Routine Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRoutineControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.86: DiagnosticRoutineControlClass

Class DiagnosticRoutineNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the general needs on the configuration of the Diagnostic Communication Manager (Dcm) which
are not related to a particular item (e.g. a PID). The main use case is the mapping of service ports to the
Dcm which are not related to a particular item.
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
diagRoutine DiagnosticRoutineType 0..1 attr This denotes the type of diagnostic routine which is
Type Enum implemented by the referenced server port.
5

132 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticRoutineNeeds
ridNumber PositiveInteger 0..1 attr This represents a routine identifier for the diagnostic
routine. This allows to predefine the RID number if the a
function developer has received a particular requirement
from the OEM or from a standardization body.

Table 5.87: DiagnosticRoutineNeeds

Enumeration DiagnosticRoutineTypeEnum
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note This enumerator specifies the different types of diagnostic routines.
Literal Description
asynchronous This indicates that the diagnostic server is not blocked while the diagnostic routine is running.
Tags:atp.EnumerationLiteralIndex=0
synchronous This indicates that the diagnostic routine blocks the diagnostic server in the ECU while the routine is
running.
Tags:atp.EnumerationLiteralIndex=1

Table 5.88: DiagnosticRoutineTypeEnum

5.5.13 SecurityAccess

This chapter describes the modeling of diagnostic services SecurityAccess (0x27).

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass
«atpAbstract» 0..1

DiagnosticSecurityAccess DiagnosticSecurityAccessClass
+securityAccessClass
+ requestSeedId: PositiveInteger [0..1]
0..1
{redefines serviceClass}

«atpSplitable»
0..* +securityLevel +securityLevel 0..1

DiagnosticCommonElement
DiagnosticSecurityLevel

+ accessDataRecordSize: PositiveInteger [0..1]

+ keySize: PositiveInteger [0..1]
+ numFailedSecurityAccess: PositiveInteger [0..1]
+ securityDelayTime: TimeValue [0..1]
+ seedSize: PositiveInteger [0..1]

Figure 5.27: Modeling of diagnostic service SecurityAccess (0x27)

[TPS_DEXT_01053] Existence of DiagnosticSecurityAccess.securityLevel

dThe configuration of a given DiagnosticSecurityAccess is considered incom-
plete until the reference in the role DiagnosticSecurityAccess.securityLevel
exists.c(RS_DEXT_00009, RS_DEXT_00042)

133 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

The meaning of [TPS_DEXT_01053] is that the reference may be missing in intermedi-

ate steps of the configuration work flow. But at the point in time when ECU configuration
is generated from the DiagnosticExtract the reference is needed to able to make
sense of the model for the given DiagnosticSecurityAccess.
Please note that (as already explained in section 5.5) the sub-functions of this service
are modeled by means of the category attribute.
In response to conceptual differences between many other diagnostic services and
SecurityAccess, the applicable sub-functions for the diagnostic service Security-
Access are not defined by means of the attribute DiagnosticSecurityAccess.
category.
[TPS_DEXT_01036] Work-flow within the execution of the diagnostic service Se-
curityAccess dThe work-flow within the execution of the diagnostic service Secu-
rityAccess basically boils down to the tester sending the request to obtain a seed
from the diagnostic stack and then sending back a key to the stack.
Thus, the sub-functions could be generically be described as requestSeed and send-
Key, which is precisely what the ISO 14229-1 [16] does.
According to this logic, the requestSeed could get a specific number assigned to iden-
tify the sub-function and then the sendKey sub-function would get assigned the number
of the requestSeed sub-function + 1. Again, this is fully in line with the ISO 14229-
1 [16].c(RS_DEXT_00009)
However, there is further dimension to take into account, namely the DiagnosticSe-
curityLevel. According to ISO 14229-1 [16], different security levels make different
numbers for the sub-function identifier.
[TPS_DEXT_01037] Semantics of DiagnosticSecurityAccess.requestSee-
dId dThe attribute DiagnosticSecurityAccess.requestSeedId shall be used
to define the number of the sub-function of the diagnostic service SecurityAccess
according to the intended security level.c(RS_DEXT_00009)
[constr_1342] Possible values for DiagnosticSecurityAccess.requestSee-
dId dThe value of the attribute DiagnosticSecurityAccess.requestSeedId
shall only be set to an odd number2 .
The supported value range consists of the following list:
• all odd numbers in the closed interval 0x01 .. 0x41
• 0x5F (this corresponds to the case of end-of-life activation of on-board pyrotech-
nic devices according to ISO 26021-2 [17])
• all odd numbers in the closed interval 0x61 .. 0x7E
c()
2
The even numbers are reserved for the identification of the corresponding sendKey sub-function, as
explained by [TPS_DEXT_01036].

134 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

In contrast to a similar situation in the case of the diagnostic service SessionControl

(see section 5.5.14), there is no real evidence that a DiagnosticSecurityLevel al-
ways exists before the referencing DiagnosticSecurityAccess is created in order
to properly establish the reference in the role DiagnosticSecurityAccess.secu-
rityLevel.
[TPS_DEXT_01038] Motivation for making the reference DiagnosticSecu-
rityAccess.securityLevel atpSplitable dThe reference Diagnostic-
SecurityAccess.securityLevel needs to be decorated with the stereotype
atpSplitable in order to advertise the idea that the reference to a correspond-
ing DiagnosticSecurityLevel is created (potentially in a different artifact) some
time after the actual creation of the given DiagnosticSecurityAccess.c(RS_-
DEXT_00001, RS_DEXT_00009, RS_DEXT_00042)
Of course, if the DiagnosticSecurityLevel factually exists before the definition of
DiagnosticSecurityAccess the reference can directly be inserted into the model.
Class DiagnosticSecurityAccess
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::SecurityAccess
Note This represents an instance of the "Security Access" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticSecurityAccesss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
requestSeedId PositiveInteger 0..1 attr This would be 0x01, 0x03, 0x05, ...
The sendKey id can be computed by adding 1 to the
requestSeedId
securityAccess DiagnosticSecurity 0..1 ref This reference substantiates that abstract reference in the
Class AccessClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticSecurityAccess in
the given context.
securityLevel DiagnosticSecurityLevel 0..1 ref This reference identifies the applicable security level for
the security access.
Stereotypes: atpSplitable
Tags:atp.Splitkey=securityLevel

Table 5.89: DiagnosticSecurityAccess

[constr_1816] Existence of attribute DiagnosticSecurityAccess.request-

SeedId dFor each DiagnosticSecurityAccess, the attribute requestSeedId
shall exist at least once at the time when the DEXT is complete.c()
[constr_1817] Existence of attribute DiagnosticSecurityAccess.secu-
rityLevel dFor each DiagnosticSecurityAccess, the attribute secu-
rityLevel shall exist at least once at the time when the DEXT is complete.c
()

135 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticSecurityAccessClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::SecurityAccess
Note This meta-class contains attributes shared by all instances of the "Security Access" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticSecurityAccesss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.90: DiagnosticSecurityAccessClass

5.5.14 SessionControl

This chapter describes the modeling of diagnostic services SessionControl (0x10).

The obvious goal of the service is to support the switching from one diagnostic session
to another.
[TPS_DEXT_01081] Modeling of DiagnosticSessionControl dFor the purpose
of providing a means to specify the switching from one diagnostic session to another di-
agnostic session, DiagnosticSessionControl refers to a DiagnosticSession
in the role diagnosticSession.c(RS_DEXT_00003, RS_DEXT_00040)
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticSessionControl DiagnosticSessionControlClass
+sessionControlClass

0..1
{redefines serviceClass}

0..* +diagnosticSession +diagnosticSession 0..1

DiagnosticCommonElement
DiagnosticSession

+ id: PositiveInteger [0..1]

+ jumpToBootLoader: DiagnosticJumpToBootLoaderEnum [0..1]
+ p2ServerMax: TimeValue [0..1]
+ p2StarServerMax: TimeValue [0..1]

Figure 5.28: Modeling of diagnostic service SessionControl (0x10)

According to ISO 14229-1 [16], the diagnostic service SessionControl defines sub-
functions.
[TPS_DEXT_01039] Identification of the sub-function of DiagnosticSession-
Control dIn the case of DiagnosticSessionControl it would not be a good idea

136 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

to encode the applicable sub-function by means of the attribute DiagnosticSes-

sionControl.category.
Actually, the possible sub-functions are strongly related to the concept of the diagnostic
session, represented by the meta-class DiagnosticSession.
The latter, in turn, has an attribute id that directly corresponds to the number of the
applicable sub-function for DiagnosticSessionControl.
In other words, the sub-function of DiagnosticSessionControl is identified
by means of the reference DiagnosticSessionControl.diagnosticSession.c
(RS_DEXT_00003, RS_DEXT_00051)
[TPS_DEXT_01082] Existence of DiagnosticSessionControl.diagnostic-
Session dThe idea of modeling the sub-function of DiagnosticSessionControl
by means of the reference DiagnosticSessionControl.diagnosticSession
implies that the applicable DiagnosticSession already exists at the time when the
given DiagnosticSessionControl is created.
It is assumed that this will always be the case because the definition of Diagnos-
ticSessions is part of laying the groundwork3 for diagnostic communication.c(RS_-
DEXT_00003, RS_DEXT_00040)
It is hard to foresee a scenario where the DiagnosticSessions are defined near the
very end of the work-flow that leads to a complete DiagnosticExtract.
Class DiagnosticSessionControl
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::SessionControl
Note This represents an instance of the "Session Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticSessionControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnostic DiagnosticSession 0..1 ref This represents the applicable DiagnosticSessions
Session
sessionControl DiagnosticSession 0..1 ref This reference substantiates that abstract reference in the
Class ControlClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticSessionControl in
the given context.

Table 5.91: DiagnosticSessionControl

[constr_1818] Existence of reference DiagnosticSessionControl.diagnos-

ticSession dFor each DiagnosticSessionControl, the reference to Diagnos-
ticSession in the role diagnosticSession shall exist at the time when the DEXT
is complete.c()
3
This is similar to the definition of commonly used data types in a software development project

137 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticSessionControlClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::SessionControl
Note This meta-class contains attributes shared by all instances of the "Session Control" diagnostic service.
Tags:atp.recommendedPackage=DiagnosticSessionControls
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.92: DiagnosticSessionControlClass

5.5.15 RequestFileTransfer

This chapter describes the modeling of diagnostic services RequestFileTransfer

(0x38). The purpose of the service is the triggering of the transfer of a file from or to
the AUTOSAR diagnostic stack.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

0..1 +accessPermission

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestFileTransfer DiagnosticRequestFileTransferClass
+requestFileTransferClass

0..1
{redefines serviceClass}

Figure 5.29: Modeling of diagnostic service RequestFileTransfer (0x38)

Please note that there is nothing to configure for DiagnosticRequestFileTrans-

fer beyond its mere existence.
[TPS_DEXT_01090] Diagnostic service RequestFileTransfer does not define
any sub-functions dThe diagnostic service RequestFileTransfer does not define
any sub-functions. therefore, the usage of the attribute category is not constrained
for meta-class DiagnosticRequestFileTransfer.c(RS_DEXT_00057)
Class DiagnosticRequestFileTransfer
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::RequestFileTransfer
Note This diagnostic service instance implements the UDS service 0x38.
Tags:atp.recommendedPackage=DiagnosticRequestFileTransfers
5

138 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticRequestFileTransfer
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
requestFile DiagnosticRequestFile 0..1 ref This reference substantiates that abstract reference in the
TransferClass TransferClass role serviceClass for this specific concrete class.
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRequestFile
Transfer in the given context.

Table 5.93: DiagnosticRequestFileTransfer

Class DiagnosticRequestFileTransferClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::DiagnosticService::RequestFileTransfer
Note This meta-class contains attributes shared by all instances of the "Request File transfer" diagnostic
service.
Tags:atp.recommendedPackage=DiagnosticRequestFileTransfers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.94: DiagnosticRequestFileTransferClass

5.6 OBD Diagnostic Services supported by AUTOSAR

Support for diagnostic services for on-board diagnostics (OBD) [18] requires the defi-
nition of further meta-classes similar to e.g. DiagnosticDataIdentifier or Diag-
nosticRoutine.
[TPS_DEXT_01092] Semantics of DiagnosticParameterIdentifier dThe
meta-class DiagnosticParameterIdentifier is used to reflect the concept of the
so-called Parameter Identifiers (PID) in the diagnostic extract. A DiagnosticParam-
eterIdentifier defines the following properties:
• Each DiagnosticParameterIdentifier gets a numerical ID carried in the
attribute DiagnosticParameterIdentifier.id.
• DiagnosticParameterIdentifier may also contain a so-called Support
Info Byte, modeled as DiagnosticSupportInfoByte.
• The definition of a DiagnosticParameterIdentifier also contains a list of
data associated with the PID. This list is modeled as an aggregation of Diag-
nosticParameter.
c(RS_DEXT_00068)
As already mentioned in [TPS_DEXT_01092], the DiagnosticParameterIdenti-
fier shall not be confused with the DiagnosticParameter. The latter is used

139 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

“inside” the definition of DiagnosticParameterIdentifier, but also in Diag-

nosticDataIdentifier or DiagnosticRoutine, to define one (out of potentially
many) piece of information held in the scope of a DiagnosticParameterIdenti-
fier.
[constr_1447] Restrictions for the value of DiagnosticParameterIdentifier.
id dThe values 0x00, 0x20, 0x40, 0x60, 0x80, 0xA0, 0xC0, and 0xE0 are not allowed
to appear in the value of DiagnosticParameterIdentifier.id.c()
[constr_1448] Interval of DiagnosticParameterIdentifier.id dThe allowed
interval for values of DiagnosticParameterIdentifier.id shall not exceed
[0..255].c()
«atpVariation»
DataDefProperties::SwDataDefProps

+ additionalNativeTypeQualifier: NativeDeclarationString [0..1]

+ displayFormat: DisplayFormatString [0..1]
+ displayPresentation: DisplayPresentationEnum [0..1]
+ stepSize: Float [0..1]
+ swAlignment: AlignmentType [0..1]
+ swCalibrationAccess: SwCalibrationAccessEnum [0..1]
+ swImplPolicy: SwImplPolicyEnum [0..1]
+ swIntendedResolution: Numerical [0..1]
+ swInterpolationMethod: Identifier [0..1]
+ swIsVirtual: Boolean [0..1]
«atpVariation»
+ swValueBlockSize: Numerical [0..1] «enumeration»
+ swValueBlockSizeMult: Numerical [0..*] {ordered} ImplementationDataTypes::
ArraySizeSemanticsEnum

fixedSize
variableSize

+swDataDefProps 0..1

DiagnosticCommonElement Identifiable
DiagnosticParameterIdentifier DiagnosticDataElement

+ id: PositiveInteger [0..1] + arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ pidSize: PositiveInteger [0..1] + maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

+dataElement 0..1

+supportInfoByte 0..1

DiagnosticSupportInfoByte «atpVariation,atpSplitable»
+ position: PositiveInteger [0..1]
+ size: PositiveInteger [0..1]

  
   


«atpSplitable,atpVariation»

DiagnosticParameterSupportInfo

+ supportInfoBit: PositiveInteger [0..1]

+supportInfo 0..1

+dataElement 0..*

DiagnosticParameter

«atpIdentityContributor»
+ bitOffset: PositiveInteger [0..1]

Figure 5.30: Modeling of the DiagnosticParameterIdentifier

[constr_1449] PID shall only carry a fixed-length collection of data dThe

value of DiagnosticParameterIdentifier.dataElement.dataElement.ar-
raySizeSemantics shall not be set to variableSize.c()

140 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1750] Existence of attribute DiagnosticParameterIdentifier.pid-

Size dAttribute DiagnosticParameterIdentifier.pidSize is only relevant if a
gap exists at the end of the DiagnosticParameterIdentifier. If this gap does
not exist, the size of the DiagnosticParameterIdentifier can be computed.c()
Class DiagnosticParameterIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to model a diagnostic parameter identifier (PID) for the purpose of
executing on-board diagnostics (OBD).
Tags:atp.recommendedPackage=DiagnosticParameterIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataElement DiagnosticParameter * aggr This represents the data carried by the Diagnostic
ParameterIdentifier.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=dataElement.bitOffset, dataElement.variation
Point.shortLabel
vh.latestBindingTime=postBuild
id PositiveInteger 0..1 attr This is the numerical identifier used to identify the
DiagnosticParameterIdentifier in the scope of diagnostic
workflow (see SAE J1979-DA).
pidSize PositiveInteger 0..1 attr The size of the entire PID can be greater than the sum of
the data elements because padding might be applied.
Unit: byte.
supportInfoByte DiagnosticSupportInfo 0..1 aggr This represents the supported information associated
Byte with the DiagnosticParameterIdentifier.

Table 5.95: DiagnosticParameterIdentifier

[constr_1819] Existence of attribute DiagnosticParameterIdentifier.id

dFor each DiagnosticParameterIdentifier, attribute id shall exist at the time
when the derivation to Ecuc starts.c()
Class DiagnosticParameterSupportInfo
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This represents a way to define which bit of the supportInfo is representing this part of the PID
Base ARObject
Attribute Type Mult. Kind Note
supportInfoBit PositiveInteger 0..1 attr defines the bit in the SupportInfo byte, which represents
the PID DataElement pidSize / position / size. Unit: byte.

Table 5.96: DiagnosticParameterSupportInfo

141 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticSupportInfoByte
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class defines the support information (typically byte A) to declare the usability of the Data
Elements within the so-called packeted PIDs (e.g. PID$68).
Base ARObject
Attribute Type Mult. Kind Note
position PositiveInteger 0..1 attr This represents the position of the supportInfo in the PID.
Unit: byte.
size PositiveInteger 0..1 attr This represents the size of the supportInfo within the PID.
Unit: byte.

Table 5.97: DiagnosticSupportInfoByte

5.6.1 OBD Mode 0x01 (RequestCurrentPowertrainDiagnosticData)

The service RequestCurrentPowertrainDiagnosticData is modeled in Figure

5.31.
[TPS_DEXT_01125] Support for diagnostic service RequestCurrentPower-
trainDiagnosticData dThe modeling support for the OBD diagnostic ser-
vice RequestCurrentPowertrainDiagnosticData utilizes the new meta-class
DiagnosticParameterIdentifier such that the meta-class DiagnosticRe-
questCurrentPowertrainData maintains a reference to DiagnosticParame-
terIdentifier in the role pid.c(RS_DEXT_00069)
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestCurrentPowertrainData DiagnosticRequestCurrentPowertrainDataClass
+requestCurrentPowertrainDiagnosticDataClass

0..1
{redefines serviceClass}

+pid 0..1

DiagnosticCommonElement
DiagnosticParameterIdentifier

+ id: PositiveInteger [0..1]

+ pidSize: PositiveInteger [0..1]

Figure 5.31: Modeling of diagnostic service for OBD Mode 0x01

142 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestCurrentPowertrainData
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x01_RequestCurrentPowertrain
DiagnosticData
Note This meta-class represents the ability to model an instance of the OBD mode 0x01 service.
Tags:atp.recommendedPackage=DiagnosticRequestCurrentPowertrainDatas
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
pid DiagnosticParameter 0..1 ref This represents the PID associated with this instance of
Identifier the OBD mode 0x01 service.
requestCurrent DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
Powertrain CurrentPowertrainData role serviceClass for this specific concrete class.
DiagnosticData Class
Thereby, the reference represents the ability to access
Class
shared attributes among all DiagnosticRequestCurrent
PowertrainData in the given context.

Table 5.98: DiagnosticRequestCurrentPowertrainData

[constr_1820] Existence of reference DiagnosticRequestCurrentPower-

trainData.pid dFor each DiagnosticRequestCurrentPowertrainData, the
reference to DiagnosticParameterIdentifier in the role pid shall exist at the
time when the derivation to Ecuc starts.c()
Class DiagnosticRequestCurrentPowertrainDataClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x01_RequestCurrentPowertrain
DiagnosticData
Note This meta-class represents the ability to define common properties for all instances of the "Request
current Powertrain Data" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRequestCurrentPowertrainDatas
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.99: DiagnosticRequestCurrentPowertrainDataClass

5.6.2 OBD Mode 0x02 (RequestPowertrainFreezeFrameData)

The service RequestPowertrainFreezeFrameData is modeled in Figure 5.32.

[TPS_DEXT_01126] Support of OBD service RequestPowertrainFreeze-
FrameData dThe modeling support for the ODB diagnostic service RequestPower-
trainFreezeFrameData utilizes the new meta-class DiagnosticParameterI-
dentifier such that the meta-class DiagnosticRequestCurrentPowertrain-
Data maintains a reference to DiagnosticParameterIdentifier in the role
pid.c(RS_DEXT_00070)

143 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestPowertrainFreezeFrameData +requestPowertrainFreezeFrameData DiagnosticRequestPowertrainFreezeFrameDataClass

0..1
{redefines serviceClass}

+freezeFrame 0..1

DiagnosticCommonElement
DiagnosticPowertrainFreezeFrame

+pid 0..*

DiagnosticCommonElement
DiagnosticParameterIdentifier

+ id: PositiveInteger [0..1]

+ pidSize: PositiveInteger [0..1]

Figure 5.32: Modeling of diagnostic service for OBD Mode 0x02

Class DiagnosticRequestPowertrainFreezeFrameData
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x02_RequestPowertrainFreeze
FrameData
Note This meta-class represents the ability to model an instance of the OBD mode 0x02 service.
Tags:atp.recommendedPackage=DiagnosticPowertrainFreezeFrames
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
freezeFrame DiagnosticPowertrain 0..1 ref This represents the associated freeze-frame.
FreezeFrame
request DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
Powertrain PowertrainFreezeFrame role serviceClass for this specific concrete class.
FreezeFrame DataClass
Thereby, the reference represents the ability to access
Data
shared attributes among all DiagnosticRequestPowertrain
FreezeFrameData in the given context.

Table 5.100: DiagnosticRequestPowertrainFreezeFrameData

[constr_1821] Existence of reference DiagnosticRequestPowertrainFreeze-

FrameData.freezeFrame dFor each DiagnosticRequestPowertrainFreeze-
FrameData, the reference to DiagnosticParameterIdentifier in the role
freezeFrame shall exist at the time when the derivation to Ecuc starts.c()

144 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestPowertrainFreezeFrameDataClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x02_RequestPowertrainFreeze
FrameData
Note This meta-class represents the ability to define common properties for all instances of the "Request
Powertrain Freeze Frame Data" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticPowertrainFreezeFrames
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.101: DiagnosticRequestPowertrainFreezeFrameDataClass

Class DiagnosticPowertrainFreezeFrame
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x02_RequestPowertrainFreeze
FrameData
Note This meta-class represents a powertrain-related freeze-frame. In theory, this meta-class would need an
additional id attribute. However, legal regulations requires only a single value for this attribute anyway.
Tags:atp.recommendedPackage=DiagnosticPowertrainFreezeFrames
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
pid DiagnosticParameter * ref This represents the PID associated with this instance of
Identifier the OBD mode 0x02 service.

Table 5.102: DiagnosticPowertrainFreezeFrame

5.6.3 OBD Mode 0x03 / 0x07 (RequestEmissionRelatedDiagnosticTrouble-

Codes)

[TPS_DEXT_01127] Semantics of meta-class DiagnosticRequestEmissionRe-

latedDTC dTwo very similar OBD services, subsumed as RequestEmissionRe-
latedDiagnosticTroubleCodes are supported by means of the meta-class Di-
agnosticRequestEmissionRelatedDTC.c(RS_DEXT_00071)
The modeling is sketched in Figure 5.33.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestEmissionRelatedDTC DiagnosticRequestEmissionRelatedDTCClass
+requestEmissionRelatedDtcClass

0..1
{redefines serviceClass}

Figure 5.33: Modeling of diagnostic service for OBD Modes 0x03, 0x07

145 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestEmissionRelatedDTC
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x03_0x07_RequestEmission
RelatedDTC
Note This meta-class represents the ability to model an instance of the OBD mode 0x03/0x07 service.
Tags:atp.recommendedPackage=DiagnosticRequestEmissionRelatedDTCs
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
request DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
Emission EmissionRelatedDTC role serviceClass for this specific concrete class.
RelatedDtc Class
Thereby, the reference represents the ability to access
Class
shared attributes among all DiagnosticRequestEmission
RelatedDTC in the given context.

Table 5.103: DiagnosticRequestEmissionRelatedDTC

Class DiagnosticRequestEmissionRelatedDTCClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x03_0x07_RequestEmission
RelatedDTC
Note This meta-class represents the ability to define common properties for all instances of the "Request
Emission Related DTC" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRequestEmissionRelatedDTCs
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.104: DiagnosticRequestEmissionRelatedDTCClass

5.6.4 OBD Mode 0x04 (ClearResetEmissionRelatedDiagnosticInformation)

[TPS_DEXT_01128] Semantics of meta-class DiagnosticClearResetEmis-

sionRelatedInfo dThe OBD diagnostic service ClearResetEmissionRelated-
DiagnosticInformation is supported by means of the meta-class Diagnostic-
ClearResetEmissionRelatedInfo.c(RS_DEXT_00072)
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticClearResetEmissionRelatedInfo DiagnosticClearResetEmissionRelatedInfoClass
+clearResetEmissionRelatedDiagnosticInfoClass

0..1
{redefines serviceClass}

Figure 5.34: Modeling of diagnostic service for OBD Mode 0x04

146 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

The modeling is sketched in Figure 5.34.

Class DiagnosticClearResetEmissionRelatedInfo
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x04_ClearResetEmission
RelatedInfo
Note This meta-class represents the ability to model an instance of the OBD mode 0x04 service.
Tags:atp.recommendedPackage=DiagnosticClearResetEmissionRelatedInfos
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
clearReset DiagnosticClearReset 0..1 ref This reference substantiates that abstract reference in the
Emission EmissionRelatedInfo role serviceClass for this specific concrete class.
Related Class
Thereby, the reference represents the ability to access
DiagnosticInfo
shared attributes among all DiagnosticClearReste
Class
EmissionRelatedInfo in the given context.

Table 5.105: DiagnosticClearResetEmissionRelatedInfo

Class DiagnosticClearResetEmissionRelatedInfoClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x04_ClearResetEmission
RelatedInfo
Note This meta-class represents the ability to define common properties for all instances of the "Clear Reset
Emission Related Data" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticClearResetEmissionRelatedInfos
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.106: DiagnosticClearResetEmissionRelatedInfoClass

5.6.5 OBD Mode 0x06 (RequestOnBoardMonitoringTestResults)

[TPS_DEXT_01129] Support for OBD diagnostic service RequestOnBoardMon-

itoringTestResults dThe OBD diagnostic service RequestOnBoardMonitor-
ingTestResults is supported by manes of meta-class DiagnosticRequestOn-
BoardMonitoringTestResults that refers to the representation of the test result
modeled as meta-class DiagnosticTestResultc(RS_DEXT_00073)
The modeling is sketched in Figure 5.35.
In general, the mode 0x06 supports the querying of supported test identifiers from
a given server. However, this functionality is not supported in AUTOSAR, hence the
existence of [constr_1462].
[constr_1462] Restrictions for the value of DiagnosticTestResult.testIden-
tifier.id dThe values 0x00, 0x20, 0x40, 0x60, 0x80, 0xA0, 0xC0, and 0xE0 are not
allowed to appear in the value of DiagnosticTestResult.testIdentifier.id.c
()

147 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestOnBoardMonitoringTestResults DiagnosticRequestOnBoardMonitoringTestResultsClass
+requestOnBoardMonitoringTestResultsClass

0..1
{redefines serviceClass}

+diagnosticTestResult 0..*

DiagnosticCommonElement
DiagnosticTestResult

«atpVariation»
+ updateKind: DiagnosticTestResultUpdateEnum [0..1]

Figure 5.35: Modeling of diagnostic service for OBD Mode 0x06

[TPS_DEXT_01141] Definition of a collection of test results dIt is possible to assign

a collection of test results to the mode 0x06.
For this purpose, DiagnosticRequestOnBoardMonitoringTestResults shall
refer to multiple DiagnosticTestResults in the role diagnosticTestResult
that in turn refers to the identical DiagnosticMeasurementIdentifier in the role
monitoredIdentifier (taken as the identification of related test results in down-
stream processing of a diagnostic extract).c(RS_DEXT_00073)
Class DiagnosticRequestOnBoardMonitoringTestResults
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x06_RequestOnBoard
MonitoringTestResults
Note This meta-class represents the ability to model an instance of the OBD mode 0x06 service.
Tags:atp.recommendedPackage=DiagnosticRequestOnBoardMonitoringTestResultss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticTest DiagnosticTestResult * ref This reference identifies the applicable collection of test
Result identifiers for setting up a request message for mode
0x06.
requestOn DiagnosticRequestOn 0..1 ref This reference substantiates that abstract reference in the
Board BoardMonitoringTest role serviceClass for this specific concrete class.
MonitoringTest ResultsClass
Thereby, the reference represents the ability to access
ResultsClass
shared attributes among all DiagnosticRequestOnBoard
MonitoringTestResults in the given context.

Table 5.107: DiagnosticRequestOnBoardMonitoringTestResults

148 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestOnBoardMonitoringTestResultsClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x06_RequestOnBoard
MonitoringTestResults
Note This meta-class represents the ability to define common properties for all instances of the "Request
On-Board Monitoring Test Results" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRequestOnBoardMonitoringTestResultss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.108: DiagnosticRequestOnBoardMonitoringTestResultsClass

5.6.6 OBD Mode 0x08 (RequestControlOfOnBoardDevice)

[TPS_DEXT_01130] Support of OBD diagnostic service RequestControlOfOn-

BoardDevice dThe OBD diagnostic service RequestControlOfOnBoardDevice
is supported by means of meta-class DiagnosticRequestControlOfOnBoard-
Device that in turn refers to a DiagnosticTestRoutineIdentifier in the role
testIdc(RS_DEXT_00074)
The modeling is sketched in Figure 5.36.
In general, the mode 0x06 supports the querying of supported test routine identifiers
from a given server. However, this functionality is not supported in AUTOSAR, hence
the existence of [constr_1461].
[constr_1461] Restrictions for the value of DiagnosticTestRoutineIdenti-
fier.id dThe values 0x00, 0x20, 0x40, 0x60, 0x80, 0xA0, 0xC0, and 0xE0 are not
allowed to appear in the value of DiagnosticTestRoutineIdentifier.id.c()
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestControlOfOnBoardDevice DiagnosticRequestControlOfOnBoardDeviceClass
+requestControlOfOnBoardDeviceClass

0..1
{redefines serviceClass}

+testId 0..1

DiagnosticCommonElement
DiagnosticTestRoutineIdentifier

+ id: PositiveInteger
+ requestDataSize: PositiveInteger
+ responseDataSize: PositiveInteger

Figure 5.36: Modeling of diagnostic service for OBD Mode 0x08

149 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticRequestControlOfOnBoardDevice
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x08_RequestControlOfOnBoard
Device
Note This meta-class represents the ability to model an instance of the OBD mode 0x08 service.
Tags:atp.recommendedPackage=DiagnosticRequestControlOfOnBoardDevices
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
requestControl DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
OfOnBoard ControlOfOnBoard role serviceClass for this specific concrete class.
DeviceClass DeviceClass
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRequestControlOf
OnBoardDevice in the given context.
testId DiagnosticTestRoutine 0..1 ref This represents the test Id for the mode 0x08.
Identifier
Table 5.109: DiagnosticRequestControlOfOnBoardDevice

[constr_1822] Existence of reference DiagnosticRequestControlOfOnBoard-

Device.testId dFor each DiagnosticRequestControlOfOnBoardDevice, the
reference to DiagnosticParameterIdentifier in the role testId shall exist at
the time when the derivation to Ecuc starts.c()
Class DiagnosticRequestControlOfOnBoardDeviceClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x08_RequestControlOfOnBoard
Device
Note This meta-class represents the ability to define common properties for all instances of the "Request
Control Of On-Board Device" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRequestControlOfOnBoardDevices
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.110: DiagnosticRequestControlOfOnBoardDeviceClass

Class DiagnosticTestRoutineIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x08_RequestControlOfOnBoard
Device
Note This represents the test id of the DiagnosticTestIdentifier.
Tags:atp.recommendedPackage=DiagnosticTestRoutineIdentifier
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
id PositiveInteger 1 attr This represents the numerical id of the DiagnosticTest
Identifier (see SAE J1979-DA).
requestData PositiveInteger 1 attr This represents the specified data size for the request
Size message. Unit: byte.
5

150 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticTestRoutineIdentifier
responseData PositiveInteger 1 attr This represents the specified data size for the response
Size message. Unit:byte.

Table 5.111: DiagnosticTestRoutineIdentifier

[constr_1823] Existence of attribute DiagnosticTestRoutineIdentifier.id

dFor each DiagnosticTestRoutineIdentifier, attribute id shall exist at the
time when the derivation to Ecuc starts.c()
[constr_1824] Existence of attribute DiagnosticTestRoutineIdentifier.re-
questDataSize dFor each DiagnosticTestRoutineIdentifier, attribute re-
questDataSize shall exist at the time when the derivation to Ecuc starts.c()
[constr_1825] Existence of attribute DiagnosticTestRoutineIdentifier.re-
sponseDataSize dFor each DiagnosticTestRoutineIdentifier, attribute re-
sponseDataSize shall exist at the time when the derivation to Ecuc starts.c()

5.6.7 OBD Mode 0x09 (RequestVehicleInformation)

[TPS_DEXT_01131] Support for OBD diagnostic service RequestVehicleIn-

formation dThe OBD diagnostic service RequestVehicleInformation is sup-
ported by means of meta-class DiagnosticRequestVehicleInfo that in turn ref-
erences a DiagnosticInfoType in the role infoType.c(RS_DEXT_00075)
The modeling is sketched in Figure 5.37.
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestVehicleInfo DiagnosticRequestVehicleInfoClass
+requestVehicleInformationClass

0..1
{redefines serviceClass}

+infoType 0..1

DiagnosticCommonElement
DiagnosticParameter
DiagnosticInfoType +dataElement

0..* «atpIdentityContributor»
  

+ id: PositiveInteger [0..1]
«atpSplitable» + bitOffset: PositiveInteger [0..1]    


«atpVariation,atpSplitable»
+dataElement 0..1

Identifiable
DiagnosticDataElement

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 5.37: Modeling of diagnostic service for OBD Mode 0x09

151 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

«atpVariation»
DataDefProperties::SwDataDefProps

+ additionalNativeTypeQualifier: NativeDeclarationString [0..1]

+ displayFormat: DisplayFormatString [0..1]
+ displayPresentation: DisplayPresentationEnum [0..1]
+ stepSize: Float [0..1]
+ swAlignment: AlignmentType [0..1]
+ swCalibrationAccess: SwCalibrationAccessEnum [0..1]
+ swImplPolicy: SwImplPolicyEnum [0..1]
+ swIntendedResolution: Numerical [0..1]
+ swInterpolationMethod: Identifier [0..1]
+ swIsVirtual: Boolean [0..1]
«atpVariation»
+ swValueBlockSize: Numerical [0..1]
+ swValueBlockSizeMult: Numerical [0..*] {ordered}

+swDataDefProps 0..1

Identifiable DiagnosticCommonElement
DiagnosticDataElement DiagnosticInfoType

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1] + id: PositiveInteger [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

+dataElement 0..1

   «atpVariation,atpSplitable»
   
 «atpSplitable»

+dataElement 0..*

DiagnosticParameter

«atpIdentityContributor»
+ bitOffset: PositiveInteger [0..1]

Figure 5.38: Modeling of DiagnosticInfoType

[constr_1460] Restrictions for the value of DiagnosticInfoType.id dThe values

0x00, 0x20, 0x40, 0x60, 0x80, 0xA0, 0xC0, and 0xE0 are not allowed to appear in the
value of DiagnosticInfoType.id.c()
[constr_1749] Existence of DiagnosticInfoType.dataElement dFor each Di-
agnosticInfoType, at least one aggregation of DiagnosticParameter in the role
dataElement shall exist at the time when the DEXT is complete.c()
Class DiagnosticRequestVehicleInfo
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x09_RequestVehicleInformation
Note This meta-class represents the ability to model an instance of the OBD mode 0x09 service.
Tags:atp.recommendedPackage=DiagnosticRequestVehicleInfos
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
infoType DiagnosticInfoType 0..1 ref This represents the info type associated with the mode
0x09 service.
requestVehicle DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
Information VehicleInfoClass role serviceClass for this specific concrete class.
Class
Thereby, the reference represents the ability to access
shared attributes among all DiagnosticRequesVehicleInfo
in the given context.

Table 5.112: DiagnosticRequestVehicleInfo

152 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1826] Existence of reference DiagnosticRequestVehicleInfo.info-

Type dFor each DiagnosticRequestVehicleInfo, the reference to Diagnos-
ticParameterIdentifier in the role infoType shall exist at the time when the
derivation to Ecuc starts.c()
Class DiagnosticRequestVehicleInfoClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x09_RequestVehicleInformation
Note This meta-class represents the ability to define common properties for all instances of the "Request
Vehicle Info" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRequestVehicleInfos
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.113: DiagnosticRequestVehicleInfoClass

Class DiagnosticInfoType
Package M2::AUTOSARTemplates::DiagnosticExtract::CommonDiagnostics
Note This meta-class represents the ability to model an OBD info type.
Tags:atp.recommendedPackage=DiagnosticInfoTypes
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataElement DiagnosticParameter * aggr This represents the data associated with the enclosing
DiagnosticInfoType.
Stereotypes: atpSplitable
Tags:atp.Splitkey=dataElement.bitOffset, data
Element.variationPoint.shortLabel
id PositiveInteger 0..1 attr This attribute represents the value of InfoType (see SAE
J1979-DA).

Table 5.114: DiagnosticInfoType

[constr_1827] Existence of attribute DiagnosticInfoType.id dFor each Diag-

nosticInfoType, attribute id shall exist at the time when the derivation to Ecuc
starts.c()

5.6.8 OBD Mode 0x0A (RequestEmissionRelatedDiagnosticTroubleCodesPer-

manentStatus)

[TPS_DEXT_01132] Support for OBD diagnostic service RequestEmissionRe-

latedDiagnosticTroubleCodesPermanentStatus dThe OBD diagnostic ser-
vice RequestEmissionRelatedDiagnosticTroubleCodesPermanentStatus
is supported by means of meta-class DiagnosticRequestEmissionRelated-
DTCPermanentStatus.c(RS_DEXT_00076)
The modeling is sketched in Figure 5.39.

153 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticAccessPermission DiagnosticServiceClass

+accessPermission 0..1

DiagnosticCommonElement
DiagnosticServiceInstance +serviceClass

«atpAbstract» 0..1

DiagnosticRequestEmissionRelatedDTCPermanentStatusClass

0..1 +requestEmissionRelatedDtcClassPermanentStatus
{redefines serviceClass}

DiagnosticRequestEmissionRelatedDTCPermanentStatus

Figure 5.39: Modeling of diagnostic service for OBD Modes 0x0A

Class DiagnosticRequestEmissionRelatedDTCPermanentStatus
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x0A_RequestEmissionRelated
DTCPermanentStatus
Note This meta-class represents the ability to model an instance of the OBD mode 0x0A service.
Tags:atp.recommendedPackage=DiagnosticRequestEmissionRelatedDTCPermanentStatuss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceInstance,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
request DiagnosticRequest 0..1 ref This reference substantiates that abstract reference in the
Emission EmissionRelatedDTC role serviceClass for this specific concrete class.
RelatedDtc PermanentStatusClass
Thereby, the reference represents the ability to access
Class
shared attributes among all DiagnosticRequestEmission
Permanent
RelatedDTCPermanentStatus in the given context.
Status

Table 5.115: DiagnosticRequestEmissionRelatedDTCPermanentStatus

Class DiagnosticRequestEmissionRelatedDTCPermanentStatusClass
Package M2::AUTOSARTemplates::DiagnosticExtract::Dcm::ObdService::Mode_0x0A_RequestEmissionRelated
DTCPermanentStatus
Note This meta-class represents the ability to define common properties for all instances of the "Request
Emission Related DTC Permanent Status" OBD diagnostic service.
Tags:atp.recommendedPackage=DiagnosticRequestEmissionRelatedDTCPermanentStatuss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticServiceClass,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.116: DiagnosticRequestEmissionRelatedDTCPermanentStatusClass

154 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

5.7 UDS Diagnostic Services for supporting WWH-OBD

[TPS_DEXT_01133] Support for WWH-OBD within the diagnostic extract dA sup-
port for WWH-OBD [19] within the diagnostic extract involves the usage of the following
UDS services and their respective subfunctions:
DiagnosticReadDataByIdentifier (0x22) where the value of attribute Diag-
nosticDataIdentifier.id inside the interval defined by the OBD range, i.e.:
• F400-F4FF
• F600-F6FF
• F800-F8FF
Please note that the usage of this diagnostic service in an implementation of
WWH-OBD corresponds to the existence of a DiagnosticValueNeeds on the
side of an AtomicSwComponentType that interacts with the diagnostic service.
DiagnosticRoutineControl (0x31) where the value of attribute Diagnosti-
cRoutine.id is inside the interval defined by the OBD range, i.e. E000-E0FF.
Please note that the usage of this diagnostic service in an implementation of
WWH-OBD corresponds to the existence of a DiagnosticRoutineNeeds on
the side of an AtomicSwComponentType that implements routines executed
within the diagnostic service.
DiagnosticClearDiagnosticInformation (0x14)
DiagnosticReadDTCInformation (0x19) with the subfunctions (0x4, 0x6, 0x42)
c(RS_DEXT_00077)
When used in a WWH-OBD environment, meta-class DiagnosticRoutine utilizes
the attribute routineInfo to support the configuration of the diagnostic response. In
a pure UDS environment (except in an application of ISO 26021 [17]) the attribute has
no semantics.

5.8 Diagnostic Service Mapping

Automotive diagnostics interacts with both application software and basic software in
various ways that can be formalized using the AUTOSAR meta-model. This chapter
contains a description of the formalization of this interaction along with the applicable
constraints.
[TPS_DEXT_01040] Use case where the DiagnosticExtract refers to software-
components dThis is a list of the potential use case where the DiagnosticExtract
refers to software-components in general and PortPrototypes in the context of ei-
ther CompositionSwComponentTypes or AtomicSwComponentTypes:

155 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• DiagnosticExtract refers to PortPrototype (for the access to dataEle-

ment) or SwcServiceDependency in the context of a AtomicSwComponent-
Type embedded in the hierarchy created by the rootSoftwareComposition.
• DiagnosticExtract refers to a PortPrototype(for the access to dataEle-
ment) or SwcServiceDependency in the context of a AtomicSwComponent-
Type embedded in the hierarchy created by a CompositionSwComponent-
Type that is nowhere aggregated (for the time being).
• DiagnosticExtract refers to a PortPrototype (for the access to
dataElement) or SwcServiceDependencyin the context of an Atomic-
SwComponentType.
• DiagnosticExtract refers to a BswServiceDependency.
c(RS_DEXT_00052)
Class SwcServiceDependency
Package M2::AUTOSARTemplates::SWComponentTemplate::SwcInternalBehavior::ServiceMapping
Note Specialization of ServiceDependency in the context of an SwcInternalBehavior. It allows to associate
ports, port groups and (in special cases) data defined for an atomic software component to a given
ServiceNeeds element.
Base ARObject, AtpClassifier , AtpFeature, AtpStructureElement, Identifiable, MultilanguageReferrable,
Referrable, ServiceDependency
Attribute Type Mult. Kind Note
assignedData RoleBasedData * aggr Defines the role of an associated data object of the same
Assignment component.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
assignedPort RoleBasedPort * aggr Defines the role of an associated port of the same
Assignment component.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=assignedPort, assignedPort.variation
Point.shortLabel
vh.latestBindingTime=preCompileTime
representedPort PortGroup 0..1 ref This reference specifies an association between the
Group ServiceNeeeds and a PortGroup, for example to request
a communication mode which applies for communication
via these ports. The referred PortGroup shall be local to
this atomic SWC, but via the links between the Port
Groups, a tool can evaluate this information such that all
the ports linked via this port group on the same ECU can
be found.
serviceNeeds ServiceNeeds 0..1 aggr The associated ServiceNeeds.

Table 5.117: SwcServiceDependency

156 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class BswServiceDependency
Package M2::AUTOSARTemplates::BswModuleTemplate::BswBehavior
Note Specialization of ServiceDependency in the context of an BswInternalBehavior. It allows to associate
BswModuleEntries and data defined for a BSW module or cluster to a given ServiceNeeds element.
Base ARObject, ServiceDependency
Attribute Type Mult. Kind Note
assignedData RoleBasedData * aggr Defines the role of an associated data object (owned by
Assignment this module or cluster) in the context of the ServiceNeeds
element.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
assignedEntry RoleBasedBswModule * aggr Defines the role of an associated BswModuleEntry in the
Role EntryAssignment context of the ServiceNeeds element.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=assignedEntryRole, assignedEntry
Role.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
ident BswService 0..1 aggr This adds the ability to become referrable to BswService
DependencyIdent Dependency.
Stereotypes: atpIdentityContributor
Tags:
atp.Status=shallBecomeMandatory
xml.sequenceOffset=-100
serviceNeeds ServiceNeeds 1 aggr The associated ServiceNeeds.

Table 5.118: BswServiceDependency

[constr_1450] Service mapping for ODB mode 0x01 for DiagnosticParame-

terIdentifier dif a DiagnosticServiceSwMapping or DiagnosticService-
DataMapping refers to a DiagnosticRequestCurrentPowertrainData and a
DiagnosticDataElement that is aggregated by a DiagnosticParameterIden-
tifier then then one of two alternative model configurations shall exist:
• SwcServiceDependency referenced by the same DiagnosticSer-
viceSwMapping or DiagnosticServiceDataMapping shall aggregate
an ObdPidServiceNeeds in the role serviceNeeds.
• The BswServiceDependencyIdent referenced by the same Diagnostic-
ServiceSwMapping shall aggregate an ObdPidServiceNeeds in the role
serviceNeeds.
c()
[constr_1451] Service mapping for OBD mode 0x09 for DiagnosticInfoType dif
a DiagnosticServiceSwMapping refers to DiagnosticRequestVehicleInfo
and a DiagnosticDataElement that is aggregated by a DiagnosticInfoType
then one of two alternative model configurations shall exist:
• The SwcServiceDependency referenced by the same DiagnosticSer-
viceSwMapping shall aggregate a ObdInfoServiceNeeds in the role ser-
viceNeeds.

157 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• The BswServiceDependencyIdent referenced by the same Diagnostic-

ServiceSwMapping shall aggregate an ObdInfoServiceNeeds in the role
serviceNeeds.
c()
[constr_1452] Service mapping for OBD mode 0x08 for DiagnosticInfoType
dif a DiagnosticServiceSwMapping refers to a DiagnosticRequestControlO-
fOnBoardDevice then the SwcServiceDependency referenced by the same Di-
agnosticServiceSwMapping shall aggregate an ObdControlServiceNeeds in
the role serviceNeeds.c()
Class ObdInfoServiceNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the abstract needs of a component or module on the configuration of OBD Services in relation
to a given InfoType (OBD Service 09) which is supported by this component or module.
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
dataLength PositiveInteger 0..1 attr This attribute is applicable only if the ServiceNeeds is
aggregated within BswModuleDependency.
This attribute represents the length of data (in bytes)
provided for this InfoType.
infoType PositiveInteger 0..1 attr The InfoType according to ISO 15031-5

Table 5.119: ObdInfoServiceNeeds

Class ObdPidServiceNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the abstract needs of a component or module on the configuration of OBD Services in relation
to a particular PID (parameter identifier) which is supported by this component or module.
In case of using a client/server communicated value, the related value shall be communicated via the
port referenced by asssignedPort. The details of this communication (e.g. appropriate naming
conventions) are specified in the related software specifications (SWS).
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
dataLength PositiveInteger 0..1 attr This attribute is applicable only if the ServiceNeeds is
aggregated within BswModuleDependency.
This attribute represents the length of data (in bytes)
provided for this particular PID signal.
parameterId PositiveInteger 0..1 attr Standardized parameter identifier (PID) according to the
OBD standard specified in attribute "standard".
standard String 0..1 attr Annotates the standard according to which the PID is
given, e.g. "ISO15031-5" or "SAE J1979 Rev May 2007".

Table 5.120: ObdPidServiceNeeds

158 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class ObdControlServiceNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the abstract needs of a component or module on the configuration of OBD Service 08 (request
control of on-board system) in relation to a particular test-Identifier (TID) supported by this component or
module.
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
testId PositiveInteger 0..1 attr Test Identifier (TID) according to ISO 15031-5.

Table 5.121: ObdControlServiceNeeds

5.8.1 Diagnostic Service Data Mapping

Please note that the Dcm is in general entitled to both read and write a dataElement.
This applies even if the corresponding PortPrototype is a PPortPrototype. This
means that the diagnostic service data mapping is limited to SenderReceiverIn-
terface.
ARElement
DiagnosticCommonElement

DiagnosticAbstractDataIdentifier
DiagnosticDataIdentifier

DiagnosticMapping + didSize: PositiveInteger [0..1]

+ representsVin: Boolean [0..1]

«atpVariation,atpSplitable»

+dataElement 0..*

DiagnosticServiceDataMapping DiagnosticParameter

«atpIdentityContributor»
+ bitOffset: PositiveInteger [0..1]

«atpVariation,atpSplitable»
«instanceRef»

+mappedDataElement 0..1 +diagnosticDataElement 0..1 +dataElement 0..1

AtpPrototype Identifiable
DataPrototype DiagnosticDataElement

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 5.40: Dcm service data mapping

If several DiagnosticServiceDataMappings exist that refer to the context of the

same VariableDataPrototype and different DiagnosticDataElements aggre-
gated by the same DiagnosticDataIdentifier then this is a strong indication that
an atomic access to a structured data type is intended.
The association of elements of the data structure to DiagnosticDataElements is
implicitly given by means of matching shortName or by explicit references into the
internals of the VariableDataPrototype.

159 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Please note that this approach of associating elements of a composite data structure
to DiagnosticDataElements of one DiagnosticDataIdentifier based on the
shortName can only work if the depth of the composite data structure is limited to 1.
[TPS_DEXT_01041] Semantics of attribute DiagnosticServiceDataMapping.
diagnosticDataElement dBy means of the attribute DiagnosticService-
DataMapping.diagnosticDataElement it is possible to specify that the Dcm has
access to
• a dataElement in a PortPrototype typed by a SenderReceiverInter-
face or
• an nvData in a PortPrototype typed by an NvDataInterface.
This type of data access is suitable for the diagnostic services ReadDataByI-
dentifier (0x22), WriteDataByIdentifier (0x2E), and InputOutputControl
(0x2F).c(RS_DEXT_00052)
Class DiagnosticServiceDataMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This represents the ability to define a mapping of a diagnostic service to a software-component.
This kind of service mapping is applicable for the usage of SenderReceiverInterfaces or event/notifier
semantics in ServiceInterfaces on the adaptive platform.
Tags:atp.recommendedPackage=DiagnosticServiceMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticData DiagnosticDataElement 0..1 ref This represents the applicable payload that corresponds
Element to the referenced DataPrototype in the role mappedData
Element or (in case of a usage on the adaptive platform)
mappedApDataElement.
mappedData DataPrototype 0..1 iref This represents the dataElement in the application
Element software that is accessed for diagnostic purpose. This
role is applicable on the classic platform.
InstanceRef implemented by:DataPrototypeInSystem
InstanceRef
Table 5.122: DiagnosticServiceDataMapping

[constr_1828] Existence of referenced from DiagnosticServiceDataMapping

dFor each DiagnosticServiceDataMapping, the following references shall exist
at the time when the DEXT is complete:
• Reference to DiagnosticDataElement in the role diagnosticDataEle-
ment
• Reference to DataPrototype in the role mappedDataElement
c()
[constr_1343] Simultaneous existence of the attributes DiagnosticService-
DataMapping.diagnosticDataElement and DiagnosticDataByIdentifier.

160 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

dataIdentifier dA DiagnosticServiceDataMapping.diagnosticDataEle-
ment shall also be aggregated by a DiagnosticDataByIdentifier in the role
dataIdentifier.dataElement.dataElement.c()
Please note that [constr_1343] shall only apply for the step in the methodology where
the DiagnosticExtract is considered complete to the point that the configuration
of the Dcm and Dem can be derived. Any intermediate step, e.g. hand-over from OEM
to tier-1 supplier does not actually enforce [constr_1343].
In other words, [constr_1343] makes sure that there is a connection between
the DiagnosticServiceDataMapping and the corresponding DiagnosticRead-
DataByIdentifier or DiagnosticWriteDataByIdentifier.
Only by this means the diagnostic service becomes fully usable.
[constr_1344] Condition for the identification of data types of attributes Di-
agnosticServiceDataMapping.mappedDataElement dDiagnosticService-
DataMapping.mappedDataElement shall be typed by either:
• ApplicationPrimitiveDataType where the value of attribute category is
set to VALUE.
• ApplicationArrayDataType where the value of attribute element.cate-
gory is set to VALUE.
c()
Rationale: the DiagnosticServiceDataMapping.mappedDataElement is
mapped to a single DiagnosticDataElement that in turn can only be a primitive
value or an array of primitive values.
Also, the modeling of the reference DiagnosticServiceDataMapping.mapped-
DataElement only supports the case where the target DataPrototype is typed by
an ApplicationDataType.
Class ApplicationPrimitiveDataType
Package M2::AUTOSARTemplates::SWComponentTemplate::Datatype::Datatypes
Note A primitive data type defines a set of allowed values.
Tags:atp.recommendedPackage=ApplicationDataTypes
Base ARElement, ARObject, ApplicationDataType, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType,
AutosarDataType, CollectableElement, Identifiable, MultilanguageReferrable, PackageableElement,
Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.123: ApplicationPrimitiveDataType

161 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class ImplementationDataType
Package M2::AUTOSARTemplates::CommonStructure::ImplementationDataTypes
Note Describes a reusable data type on the implementation level. This will typically correspond to a typedef in
C-code.
Tags:atp.recommendedPackage=ImplementationDataTypes
Base ARElement, ARObject, AbstractImplementationDataType, AtpBlueprint, AtpBlueprintable, AtpClassifier ,
AtpType, AutosarDataType, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
dynamicArray String 0..1 attr Specifies the profile which the array will follow in case this
SizeProfile data type is a variable size array.
isStructWith Boolean 0..1 attr This attribute is only valid if the attribute category is set to
Optional STRUCTURE.
Element
If set to True, this attribute indicates that the
ImplementationDataType has been created with the
intention to define at least one element of the structure as
optional.
subElement ImplementationData * aggr Specifies an element of an array, struct, or union data
(ordered) TypeElement type.
The aggregation of ImplementionDataTypeElement is
subject to variability with the purpose to support the
conditional existence of elements inside a Implementation
DataType representing a structure.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
symbolProps SymbolProps 0..1 aggr This represents the SymbolProps for the Implementation
DataType.
Stereotypes: atpSplitable
Tags:atp.Splitkey=symbolProps.shortName
typeEmitter NameToken 0..1 attr This attribute is used to control which part of the
AUTOSAR toolchain is supposed to trigger data type
definitions.
Table 5.124: ImplementationDataType

In other words, [constr_1344] requires that both DiagnosticServiceDataMap-

ping.mappedDataElement4 and DiagnosticServiceDataMapping.diagnos-
ticDataElement shall be typed by a primitive data type.
Please refer to [8] for a detailed explanation of the meaning of the value of a data type
category.
[constr_1345] DiagnosticDataElement shall not (finally) be aggregated by a
DiagnosticRoutine dA DiagnosticDataElement that is referenced by a Diag-
nosticServiceDataMapping shall not (finally) be aggregated by a Diagnosti-
cRoutine.c()
[TPS_DEXT_01042] Dem uses DiagnosticServiceDataMapping dThere is a use
case for the Dem to utilize a DiagnosticServiceDataMapping such that elements
of a DiagnosticExtendedDataRecord are fetched from dataElements in an Ap-
plicationSwComponentType.
4
DiagnosticServiceDataMapping.mappedDataElement can be an element of a (potentially
large) composite data type. The utility of this is that this way the footprint of the data access to the
payload of request and response messages can be kept as low as possible.

162 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Therefore, [constr_1345] does intentionally not exclude the aggregation of Diagnos-

ticDataElement by DiagnosticExtendedDataRecord in the context of Diag-
nosticServiceDataMapping.c(RS_DEXT_00052)
Class ApplicationSwComponentType
Package M2::AUTOSARTemplates::SWComponentTemplate::Components
Note The ApplicationSwComponentType is used to represent the application software.
Tags:atp.recommendedPackage=SwComponentTypes
Base ARElement, ARObject, AtomicSwComponentType, AtpBlueprint, AtpBlueprintable, AtpClassifier , Atp
Type, CollectableElement, Identifiable, MultilanguageReferrable, PackageableElement, Referrable, Sw
ComponentType
Attribute Type Mult. Kind Note
– – – – –
Table 5.125: ApplicationSwComponentType

[constr_1584] DiagnosticDataElement shall not be used more than once in

I/O Control instance dA given DiagnosticDataElement shall not be used by more
than one DiagnosticServiceDataMapping that in turn refers to a DataProto-
type defined in the context of a DataInterface that is used to type a PortPro-
totype that in turn is referenced by a RoleBasedPortAssignment where attribute
role is set to the value IOControlRequest.c()

5.8.2 Diagnostic Service Software Mapping

The diagnostic service software mapping is limited to ClientServerInterface or

a direct function call (in the case of basic software or complex driver).
Class ClientServerInterface
Package M2::AUTOSARTemplates::SWComponentTemplate::PortInterface
Note A client/server interface declares a number of operations that can be invoked on a server by a client.
Tags:atp.recommendedPackage=PortInterfaces
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, PortInterface, Referrable
Attribute Type Mult. Kind Note
operation ClientServerOperation * aggr ClientServerOperation(s) of this ClientServerInterface.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=blueprintDerivationTime
possibleError ApplicationError * aggr Application errors that are defined as part of this interface.

Table 5.126: ClientServerInterface

The following constraint only applies to the case where I/O Control is implemented via
sender-receiver-communication (see [TPS_SWCT_01654])
[TPS_DEXT_01043] Purpose of DiagnosticServiceSwMapping dThe meta-class
DiagnosticServiceSwMapping has been introduced to support the creation of

163 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

a relationship between the definition of a given diagnostic service to the SwcSer-

viceDependency (if the service applies to the application software) or BswSer-
viceDependency (if the service applies to the basic software).c(RS_DEXT_00052)
It is required to use the applicable form of reference to the target SwcServiceDepen-
dency depending on the context of the enclosing AtomicSwComponentType.
ARElement
DiagnosticCommonElement

DiagnosticMapping

DiagnosticSwMapping

Identifiable
DiagnosticServiceSwMapping
DiagnosticDataElement +diagnosticDataElement
+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1] 0..1
+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

AtpStructureElement +mappedFlatSwcServiceDependency
Identifiable
ServiceDependency 0..1
SwcServiceDependency

+mappedSwcServiceDependencyInSystem

0..1 «instanceRef»

IdentCaption
BswServiceDependencyIdent +mappedBswServiceDependency

0..1

+ident 0..1
«atpIdentityContributor»
+serviceInstance 0..1

ServiceDependency
DiagnosticServiceInstance
BswServiceDependency

Figure 5.41: Dcm service software mapping

Class DiagnosticSwMapping (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This represents the ability to define a mapping between a diagnostic information (at this point there is no
way to become more specific about the semantics) to a software-component.
5

164 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticSwMapping (abstract)
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses DiagnosticEnableConditionPortMapping, DiagnosticEventPortMapping, DiagnosticFimFunctionMapping,
DiagnosticOperationCyclePortMapping, DiagnosticServiceSwMapping, DiagnosticStorageConditionPort
Mapping
Attribute Type Mult. Kind Note
– – – – –
Table 5.127: DiagnosticSwMapping

Class DiagnosticServiceSwMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This represents the ability to define a mapping of a diagnostic service to a software-component or a
basic-software module. If the former is used then this kind of service mapping is applicable for the usage
of ClientServerInterfaces.
Tags:atp.recommendedPackage=DiagnosticServiceMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
DiagnosticSwMapping, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticData DiagnosticDataElement 0..1 ref This represents a DiagnosticDataElement required to
Element execute the respective diagnostic service in the context of
the diagnostic service mapping,
mappedBsw BswService 0..1 ref This is supposed to represent a reference to a Bsw
Service DependencyIdent ServiceDependency. the latter is not derived from
Dependency Referrable and therefore this detour needs to be
implemented to still let BswServiceDependency become
the target of a reference.
mappedFlatSwc SwcService 0..1 ref This represents the ability to refer to an AtomicSw
Service Dependency ComponentType that is available without the definition of
Dependency how it will be embedded into the component hierarchy.
mappedSwc SwcService 0..1 iref This represents the ability to point into the component
Service Dependency hiearchy (under possible consideration of the root
DependencyIn SoftwareComposition)
System
InstanceRef implemented by:SwcServiceDependency
InSystemInstanceRef
serviceInstance DiagnosticService 0..1 ref This represents the service instance that needs to be
Instance considered in this diagnostics service mapping.

Table 5.128: DiagnosticServiceSwMapping

[TPS_DEXT_01044] BswServiceDependency needs to act as the target of

a reference dThe intention of DiagnosticServiceSwMapping.mappedBswSer-
viceDependency is to refer to a BswServiceDependency in the same way as e.g.
DiagnosticServiceSwMapping.mappedFlatSwcServiceDependency does.
However, BswServiceDependency is not derived from meta-class Referrable
and can therefore never become the target of a reference like DiagnosticSer-
viceSwMapping.mappedBswServiceDependency.
The remedy for this issue is to define meta-class BswServiceDependencyIdent
that inherits from IdentCaption that in turn inherits from Referrable.

165 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Then, by aggregating BswServiceDependencyIdent at BswServiceDependency

in the role ident BswServiceDependency can factually become the target of the
reference and thus the original idea of DiagnosticServiceSwMapping.mappedB-
swServiceDependency becomes feasible.c(RS_DEXT_00052)
Please find further details in Figure 5.41.
Please note that the introduction [TPS_DEXT_01044], although being dangerously
close to a hack, is necessary to keep the AUTOSAR XML Schema fully backwards-
compatible.
In other words, if BswServiceDependency were updated to inherit from Re-
ferrable the consequence would be that all existing AUTOSAR models that con-
tain instances BswServiceDependency would suddenly become invalid because
Referrable.shortName is a mandatory attribute in the AUTOSAR XML Schema.
Class BswServiceDependencyIdent
Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This meta-class is created to add the ability to become the target of a reference to the non-Referrable
BswServiceDependency.
Base ARObject, AtpClassifier , AtpFeature, AtpStructureElement, IdentCaption, Identifiable, Multilanguage
Referrable, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 5.129: BswServiceDependencyIdent

[constr_1346] Allowed values of DiagnosticServiceSwMapping.serviceIn-

stance dThe applicability of the DiagnosticServiceSwMapping is limited to pre-
defined set of diagnostic services.
By regulation of the AUTOSAR standard, DiagnosticServiceSwMapping.servi-
ceInstance shall only point to the following sub-classes of DiagnosticService-
Instance:
• DiagnosticRoutine
• DiagnosticSecurityAccess
• DiagnosticReadDataByIdentifier
• DiagnosticWriteDataByIdentifier
• DiagnosticIOControl
c()
[constr_1347] Existence of attributes of DiagnosticServiceSwMapping dFor
any given DiagnosticServiceSwMapping, one and only one of the following ref-
erences shall exist:
• DiagnosticServiceSwMapping.mappedFlatSwcServiceDependency

166 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• DiagnosticServiceSwMapping.mappedSwcServiceDependencyInSys-
tem
• DiagnosticServiceSwMapping.mappedBswServiceDependency
c()
[constr_1347], among further clarifications, reflects the fact that at most a single Swc-
ServiceDependency can be referenced by a DiagnosticServiceSwMapping
and this SwcServiceDependency cannot be identified by both mappedSwcSer-
viceDependencyInSystem and mappedFlatSwcServiceDependency.

5.8.3 Security Event Reporting Mode Mapping

The reporting mode of particular security events (see [20]) can be updated via diag-
nostic services.
ARElement
DiagnosticCommonElement

DiagnosticAbstractDataIdentifier
DiagnosticDataIdentifier
DiagnosticMapping
+ didSize: PositiveInteger [0..1]
+ representsVin: Boolean [0..1]

«atpVariation,atpSplitable»
+dataElement 0..*


DiagnosticSecurityEventReportingModeMapping   DiagnosticParameter
 
  «atpIdentityContributor»
 + bitOffset: PositiveInteger [0..1]

«atpVariation,atpSplitable»

+securityEvent 0..1 +dataElement 0..1 +dataElement 0..1

Identifiable Identifiable
SecurityEventContextProps DiagnosticDataElement

+ defaultReportingMode: SecurityEventReportingModeEnum [0..1] + arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ persistentStorage: Boolean [0..1] + maxNumberOfElements: PositiveInteger [0..1]
+ sensorInstanceId: PositiveInteger [0..1] + scalingInfoSize: PositiveInteger [0..1]
+ severity: PositiveInteger [0..1]

«atpVariation»
  
  
   
+securityEvent 0..1  

IdsCommonElement
SecurityEventDefinition

+ id: PositiveInteger [0..1]

Figure 5.42: Modeling of the security event reporting model mapping

[TPS_DEXT_01152]{DRAFT} Semantics of meta-class DiagnosticSecuri-

tyEventReportingModeMapping dFor this purpose, it is necessary to reserve a
spot in a DID over which the new value for the reporting mode can be transferred from
a diagnostic tester to the diagnostic stack on the target Ecu, and from there to the
IdsM [21].

167 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

From the modeling point of view, this relation is created by means of meta-class Di-
agnosticSecurityEventReportingModeMapping.c(RS_DEXT_00081)
It is important to understand that this mapping is used to formalize the relation of two
basic software modules to each other. No kind of application software is involved in
this relation.
Class DiagnosticSecurityEventReportingModeMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This meta-class represents the ability to associate a location in a DID with a security event. The purpose
of this mapping is that the location in the DID contains the setting of the reporting mode for the specific
security event. This means that the reporting mode of the security event can be set via the diagnostic
service WriteDataByIdentifier.
Tags:
atp.Status=draft
atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataElement DiagnosticDataElement 0..1 ref This reference identifies the data element that carries the
information about the reporting mode.
Tags:atp.Status=draft
securityEvent SecurityEventContext 0..1 ref This reference identifies the mapped security event.
Props
Tags:atp.Status=draft

Table 5.130: DiagnosticSecurityEventReportingModeMapping

[constr_10024]{DRAFT} Existence of reference in the role DiagnosticSecuri-

tyEventReportingModeMapping.dataElement dFor each DiagnosticSecu-
rityEventReportingModeMapping, the reference to DiagnosticDataElement
in the role dataElement shall exist at the time when the DEXT is complete.c()
[constr_10025]{DRAFT} Existence of reference in the role DiagnosticSecu-
rityEventReportingModeMapping.securityEvent dFor each Diagnostic-
SecurityEventReportingModeMapping, the reference to SecurityEventCon-
textProps in the role securityEvent shall exist at the time when the DEXT is
complete.c()

168 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6 Diagnostic Event Handling

6.1 Introduction
This subchapter describes the meta-model elements that define the handling of and
the functionality around diagnostic events.
In a standard AUTOSAR Basic Software architecture, the definitions based on the
model elements described in this subchapter are realized by the Diagnostic Event Man-
ager (Dem) module.
The following figure gives an overview on the model elements related to the diagnostic
event functionality.
ARElement
DiagnosticContributionSet

«atpVariation,atpSplitable»
+element 0..*

ARElement
DiagnosticCommonElement

DiagnosticMapping DiagnosticConditionGroup DiagnosticCondition DiagnosticExtendedDataRecord DiagnosticFreezeFrame

DiagnosticEvent DiagnosticTroubleCode DiagnosticIndicator DiagnosticOperationCycle DiagnosticTroubleCodeGroup DiagnosticAging

Figure 6.1: Common model elements relevant for the Dem

For the definition of the diagnostic event functionality, a number of model elements
are derived from DiagnosticCommonElement. These elements are described in the
following sub-chapters.

6.2 DiagnosticEvent

6.2.1 Overview

[TPS_DEXT_01083] Semantics of a DiagnosticEvent dA DiagnosticEvent -

the atomic unit handled by the Dem module - has to be defined together with its prop-
erties which affect the event handling behavior and possible interfaces to software-
components.c(RS_DEXT_00023)

169 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Figure 6.2 depicts the definition of DiagnosticEvent together with its properties.
DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

  
   


«atpVariation,atpSplitable»

+connectedIndicator 0..*
Identifiable DiagnosticCommonElement
DiagnosticConnectedIndicator DiagnosticIndicator
+indicator
+ behavior: DiagnosticConnectedIndicatorBehaviorEnum [0..1] «atpVariation»
0..1
«atpVariation» + type: DiagnosticIndicatorTypeEnum [0..1]
+ healingCycleCounterThreshold: PositiveInteger [0..1]

DiagnosticCommonElement
DiagnosticOperationCycle
+healingCycle
+ automaticEnd: Boolean [0..1]
0..1 + cycleStatusStorage: Boolean [0..1]
+ type: DiagnosticOperationCycleTypeEnum [0..1]

«enumeration» «enumeration» «enumeration»

DiagnosticIndicatorTypeEnum DiagnosticClearEventAllowedBehaviorEnum DiagnosticConnectedIndicatorBehaviorEnum

warning noStatusByteChange continuousOnMode

malfunction onlyThisCycleAndReadiness blinkMode
amberWarning blinkOrContinuousOnMode
protectLamp slowFlashingMode
redStopLamp fastFlashingMode

«enumeration»
«enumeration» DiagnosticEventClearAllowedEnum
DiagnosticEventKindEnum
always
bsw requiresCallbackExecution
swc

Figure 6.2: Modeling of DiagnosticEvent

The DiagnosticExtract allows the definition of an arbitrary number of Diagnos-

ticEvents.
Although the exchange of a DiagnosticExtract between companies usually in-
volves DiagnosticEvents related to SWC functionality, the event kind BSW is also
supported in order to enable definition of handling of BSW events (e.g. definition of
associated DiagnosticTroubleCode).
[TPS_DEXT_03011] Clearing request for a DiagnosticEvent dFurthermore, a
clearing request for a DiagnosticEvent might require invocation of a callback to
a SWC in order to allow or to prohibit the clearing operation.
The expectation on this callback interface can be expressed using the attribute event-
ClearAllowed:
• always indicates that a clearing request for the DiagnosticEvent shall un-
conditionally be executed.
• In case of requiresCallbackExecution, the execution of a callback shall
decide whether the clearing is permitted.

170 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

In other words, the implementation of this decision is up to the developer of the

corresponding AtomicSwComponentType.
The latter shall define a SwcServiceDependency with appropriate Diagnos-
ticEventNeeds and a RoleBasedPortAssignment where the value of the
attribute role is set to CallbackClearEventAllowed.
c(RS_DEXT_00023)
Class DiagnosticEvent
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This element is used to configure DiagnosticEvents.
Tags:atp.recommendedPackage=DiagnosticEvents
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
associated PositiveInteger 0..1 attr This attribute represents the identification number that is
Event associated with the enclosing DiagnosticEvent and allows
Identification to identify it when placed into a snapshot record or
extended data record storage.
This value can be reported as internal data element in
snapshot records or extended data records.
clearEvent DiagnosticClearEvent 0..1 attr This attribute defines the resulting UDS status byte for the
Allowed AllowedBehaviorEnum related event, which shall not be cleared according to the
Behavior ClearEventAllowed callback
confirmation PositiveInteger 0..1 attr This attribute defines the number of operation cycles with
Threshold a failed result before a confirmed DTC is set to 1. The
semantic of this attribute is a by "1" increased value
compared to the confirmation threshold of the "trip
counter" mentioned in ISO 14229-1 in figure D.4. A value
of "1" defines the immediate confirmation of the DTC
along with the first reported failed. This is also sometimes
called "zero trip DTC". A value of "2" defines a DTC
confirmation in the operation cycle after the first occurred
failed. A value of "2" is typically used in the US for OBD
DTC confirmation.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
connected DiagnosticConnected * aggr Event specific description of Indicators.
Indicator Indicator
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=connectedIndicator.shortName, connected
Indicator.variationPoint.shortLabel
vh.latestBindingTime=postBuild
eventClear DiagnosticEventClear 0..1 attr This attribute defines whether the Dem has access to a
Allowed AllowedEnum "ClearEventAllowed" callback.
eventKind DiagnosticEventKind 0..1 attr This attribute is used to distinguish between SWC and
Enum BSW events.
prestorage Boolean 0..1 attr This attribute describes whether the Prestorage of Freeze
FreezeFrame Frames is supported by the assigned event or not.
True: Prestorage of FreezeFrames is supported
False: Prestorage of FreezeFrames is not supported
5

171 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticEvent
prestored Boolean 0..1 attr If the Event uses a prestored freeze-frame (using the
Freezeframe operations PrestoreFreezeFrame and ClearPrestored
StoredInNvm FreezeFrame of the service interface DiagnosticMonitor)
this attribute indicates if the Event requires the data to be
stored in non-volatile memory. TRUE = Dem shall store
the prestored data in non-volatile memory, FALSE = Data
can be lost at shutdown (not stored in Nvm)
recoverableIn Boolean 0..1 attr If the attribute is set to true then reporting PASSED will
SameOperation reset the indication of a failed test in the current operation
Cycle cycle. If the attribute is set to false then reporting
PASSED will be ignored and not lead to a reset of the
indication of a failed test.
Table 6.1: DiagnosticEvent

Enumeration DiagnosticClearEventAllowedBehaviorEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This enumeration defines the possible behavior for clear event allowed
Literal Description
noStatusByte The event status byte keeps unchanged.
Change
Tags:atp.EnumerationLiteralIndex=0
onlyThisCycleAnd The OperationCycle and readiness bits of the event status byte are reset.
Readiness
Tags:atp.EnumerationLiteralIndex=1

Table 6.2: DiagnosticClearEventAllowedBehaviorEnum

Class RoleBasedPortAssignment
Package M2::AUTOSARTemplates::SWComponentTemplate::SwcInternalBehavior::ServiceMapping
Note This class specifies an assignment of a role to a particular service port (RPortPrototype or PPort
Prototype) of an AtomicSwComponentType. With this assignment, the role of the service port can be
mapped to a specific ServiceNeeds element, so that a tool is able to create the correct connector.
Base ARObject
Attribute Type Mult. Kind Note
portPrototype PortPrototype 0..1 ref Service PortPrototype used in the assigned role. This
PortPrototype shall either belong to the same AtomicSw
ComponentType as the SwcInternalBehavior which owns
the ServiceDependency or to the same NvBlockSw
ComponentType as the NvBlockDescriptor.
role Identifier 0..1 attr This is the role of the assigned Port in the given context.
The value shall be a shortName of the Blueprint of a Port
Interface as standardized in the Software Specification of
the related AUTOSAR Service.

Table 6.3: RoleBasedPortAssignment

[TPS_DEXT_01085] DiagnosticEvent can be connected to one or multiple in-

dicators dA DiagnosticEvent can be connected to one or multiple indicators (mod-
eled by means of aggregating DiagnosticIndicator in the role connectedIndi-
cator) of a certain type and with certain behavior.c(RS_DEXT_00023)

172 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticConnectedIndicator
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note Description of indicators that are defined per DiagnosticEvent.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
behavior DiagnosticConnected 0..1 attr Behavior of the linked indicator.
IndicatorBehaviorEnum
healingCycle DiagnosticOperation 0..1 ref The deactivation of indicators per event is defined as
Cycle healing of a diagnostic event. The operation cycle in
which the warning indicator will be switched off is defined
here.
healingCycle PositiveInteger 0..1 attr This attribute defines the number of healing cycles for the
Counter WarningIndicatorOffCriteria
Threshold
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
indicator DiagnosticIndicator 0..1 ref Reference to the used indicator.

Table 6.4: DiagnosticConnectedIndicator

[constr_1829] Existence of reference DiagnosticConnectedIndicator.indi-

cator dFor each DiagnosticConnectedIndicator, the reference to Diagnos-
ticIndicator in the role indicator shall exist at the time when the DEXT is
complete.c()
[constr_1761] Existence of attribute DiagnosticConnectedIndicator.heal-
ingCycle dDiagnosticConnectedIndicator.healingCycle shall only exist if
the value of DiagnosticConnectedIndicator.healingCycleCounterThresh-
old is not equal to 0.c()
Enumeration DiagnosticEventClearAllowedEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note Denotes whether clearing of events is allowed.
Literal Description
always The clearing is allowed unconditionally.
Tags:atp.EnumerationLiteralIndex=0
requiresCallback In case the clearing of a Diagnostic Event has to be allowed or prohibited through the SWC interface
Execution CallbackClearEventAllowed, the SWC has to indicate this by defining appropriate ServiceNeeds (i.e.
DiagnosticEventNeeds).
Tags:atp.EnumerationLiteralIndex=2

Table 6.5: DiagnosticEventClearAllowedEnum

Enumeration DiagnosticEventKindEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note Applicability of the diagnostic event.
Literal Description
5

173 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticEventKindEnum
bsw The event is assigned to a BSW module.
Tags:atp.EnumerationLiteralIndex=0
swc The event is assigned to a SWC.
Tags:atp.EnumerationLiteralIndex=1

Table 6.6: DiagnosticEventKindEnum

Enumeration DiagnosticConnectedIndicatorBehaviorEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note Behavior of the indicator.
Literal Description
blinkMode The indicator blinks when the event has status FAILED.
Tags:atp.EnumerationLiteralIndex=0
blinkOrContinuous The indicator is active and blinks when the event has status FAILED.
OnMode
Tags:atp.EnumerationLiteralIndex=1
continuousOnMode The indicator is active when the event has status FAILED.
Tags:atp.EnumerationLiteralIndex=2
fastFlashingMode Flash Indicator Lamp should be set to "Fast Flash".
Tags:atp.EnumerationLiteralIndex=3
slowFlashingMode Flash Indicator Lamp should be set to "Slow Flash".
Tags:atp.EnumerationLiteralIndex=4

Table 6.7: DiagnosticConnectedIndicatorBehaviorEnum

6.2.2 Textual description

[TPS_DEXT_01067] Textually formulated content attached to DiagnosticEvent

dThe definition of a DiagnosticEvent also consists of textually formulated content
that is formalized in structure but cannot be formalized in content.
The purpose of this content is to define e.g. a mature condition that relates to the
specific DiagnosticEvent.c(RS_DEXT_00023, RS_DEXT_00045)
[TPS_DEXT_01068] Textual description with respect to the DiagnosticEvent
dTextual description that has the character of requirements with respect to the Diag-
nosticEvent shall be provided by means of the meta-class StructuredReq, i.e. by
means of introduction.structuredReq.c(RS_DEXT_00023, RS_DEXT_00045)

174 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class StructuredReq
Package M2::MSR::Documentation::BlockElements::RequirementsTracing
Note This represents a structured requirement. This is intended for a case where specific requirements for
features are collected.
Note that this can be rendered as a labeled list.
Base ARObject, DocumentViewSelectable, Identifiable, MultilanguageReferrable, Paginateable, Referrable,
Traceable
Attribute Type Mult. Kind Note
appliesTo standardNameEnum * attr This attribute represents the platform the requirement is
assigned to.
Tags:
xml.namePlural=APPLIES-TO-DEPENDENCIES
xml.sequenceOffset=25
conflicts DocumentationBlock 0..1 aggr This represents an informal specification of conflicts.
Tags:xml.sequenceOffset=40
date DateTime 1 attr This represents the date when the requirement was
initiated.
Tags:xml.sequenceOffset=5
dependencies DocumentationBlock 0..1 aggr This represents an informal specifiaction of
dependencies. Note that upstream tracing should be
formalized in the property trace provided by the
superclass Traceable.
Tags:xml.sequenceOffset=30
description DocumentationBlock 0..1 aggr Ths represents the general description of the
requirement.
Tags:xml.sequenceOffset=10
importance String 1 attr This allows to represent the importance of the
requirement.
Tags:xml.sequenceOffset=8
issuedBy String 1 attr This represents the person, organization or authority
which issued the requirement.
Tags:xml.sequenceOffset=6
rationale DocumentationBlock 0..1 aggr This represents the rationale of the requirement.
Tags:xml.sequenceOffset=20
remark DocumentationBlock 0..1 aggr This represents an informal remark. Note that this is not
modeled as annotation, since these remark is still
essential part of the requirement.
Tags:xml.sequenceOffset=60
supporting DocumentationBlock 0..1 aggr This represents an informal specifiaction of the
Material supporting material.
Tags:xml.sequenceOffset=50
testedItem Traceable * ref This assocation represents the ability to trace on the
same specification level. This supports for example the of
acceptance tests.
Tags:xml.sequenceOffset=70
type String 1 attr This attribute allows to denote the type of requirement to
denote for example is it an "enhancement", "new feature"
etc.
Tags:xml.sequenceOffset=7
5

175 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class StructuredReq
useCase DocumentationBlock 0..1 aggr This describes the relevant use cases. Note that formal
references to use cases should be done in the trace
relation.
Tags:xml.sequenceOffset=35

Table 6.8: StructuredReq

For more details regarding the modeling of the semi-formal text please refer to Figure
4.3.
[TPS_DEXT_01069] Standardized values of DiagnosticEvent.introduction.
structuredReq dThe following possible values of DiagnosticEvent.introduc-
tion.structuredReq are standardized by AUTOSAR:
• DIAG_EVENT_MON_COND: this value describes the monitoring condition of the
corresponding DiagnosticEvent.
• DIAG_EVENT_MON_TYPE: this value describes the monitoring type of the corre-
sponding DiagnosticEvent.
• DIAG_EVENT_MON_RATE: this value describes the monitoring rate for the corre-
sponding DiagnosticEvent.
• DIAG_EVENT_MAT_COND: this value describes a mature condition of the Diag-
nosticEvent.
• DIAG_EVENT_DEMAT_COND: this value describes a de-mature condition of the
DiagnosticEvent.
• DIAG_EVENT_AGING: this value describes the behavior of the Diagnos-
ticEvent regarding aging.
• DIAG_EVENT_LIMP_IN_ACT: this value describes the associated limp-in action
for the DiagnosticEvent.
• DIAG_EVENT_MAT_TIME: this value describes the mature time for the corre-
sponding DiagnosticEvent, i.e. how long or how often the fault must exist.
• DIAG_EVENT_DEMAT_TIME: this value describes the de-mature time for the cor-
responding DiagnosticEvent, i.e. how long or how often must the OK condi-
tions be fulfilled.
c(RS_DEXT_00001, RS_DEXT_00023, RS_DEXT_00045)
The following ARXML fragment exemplifies the usage of StructuredReq along with
the standardized values of the attribute category to attach semi-formal textual de-
scriptions of an exemplary mature condition and a de-mature condition to a Diagnos-
ticEvent.
Listing 6.1: Example for the definition of a semi-formal textual element in the context of
a DiagnosticEvent

176 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

<DIAGNOSTIC-EVENT>
<SHORT-NAME>ExampleEvent_0001</SHORT-NAME>
<INTRODUCTION>
<STRUCTURED-REQ>
<SHORT-NAME>MatureCondition</SHORT-NAME>
<CATEGORY>DIAG_EVENT_MAT_COND</CATEGORY>
<DESCRIPTION>
<P>
<L-1 L="EN">This DTC is set if System Voltage is
below 9 Volts</L-1>
</P>
</DESCRIPTION>
</STRUCTURED-REQ>
<STRUCTURED-REQ>
<SHORT-NAME>DematureCondition</SHORT-NAME>
<CATEGORY>DIAG_EVENT_DEMAT_COND</CATEGORY>
<DESCRIPTION>
<P>
<L-1 L="EN">This DTC is set if System Voltage is
above 10 Volts<XFILE><SHORT-NAME>
Requirement_Specification</SHORT-NAME><URL>http:
//autosar.org</URL></XFILE>
</L-1>
</P>
</DESCRIPTION>
</STRUCTURED-REQ>
</INTRODUCTION>
<CLEAR-EVENT-BEHAVIOR>ONLY-THIS-CYCLE-AND-READINESS</CLEAR-EVENT-
BEHAVIOR>
<EVENT-CLEAR-ALLOWED>ALWAYS</EVENT-CLEAR-ALLOWED>
<EVENT-FAILURE-CYCLE-COUNTER-THRESHOLD>100</EVENT-FAILURE-CYCLE-COUNTER
-THRESHOLD>
<EVENT-KIND>SWC</EVENT-KIND>
<PRESTORAGE-FREEZE-FRAME>false</PRESTORAGE-FREEZE-FRAME>
</DIAGNOSTIC-EVENT>

6.2.3 Associated Event Identification

[TPS_DEXT_01151] Semantics of attribute DiagnosticEvent.associatedE-

ventIdentification dUse cases exist where DiagnosticEvents are not as-
sociated with the DiagnosticTroubleCode but the occurrence of the event shall
nonetheless be reported as part of the dtcProps.snapshotRecordContent.
dataIdentifier of a given DiagnosticTroubleCodeUds.
For this purpose, it is necessary that the tester can identify the occurrence of the
DiagnosticEvent by means of the value of attribute DiagnosticEvent.associ-
atedEventIdentification.c(RS_DEXT_00023)

177 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticMapping
DiagnosticEventToTroubleCodeUdsMapping

+diagnosticEvent 0..1 +troubleCodeUds 0..1

DiagnosticCommonElement DiagnosticTroubleCode
DiagnosticEvent DiagnosticTroubleCodeUds

+ associatedEventIdentification: PositiveInteger [0..1] + considerPtoStatus: Boolean [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1] + eventObdReadinessGroup: NameToken [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1] + functionalUnit: PositiveInteger [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1] + severity: DiagnosticUdsSeverityEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1] «atpVariation»
+ prestoredFreezeframeStoredInNvm: Boolean [0..1] + udsDtcValue: PositiveInteger [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1] + wwhObdDtcClass: DiagnosticWwhObdDtcClassEnum [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

+dtcProps 0..1

DiagnosticCommonElement
DiagnosticTroubleCodeProps

+ environmentCaptureToReporting: EnvironmentCaptureToReportingEnum [0..1]

+ immediateNvDataStorage: Boolean [0..1]
+ maxNumberFreezeFrameRecords: PositiveInteger [0..1]
+ significance: DiagnosticSignificanceEnum [0..1]
«atpVariation»
+ priority: PositiveInteger [0..1]

«atpVariation,atpSplitable» «atpVariation»
+extendedDataRecord
0..* +snapshotRecordContent 0..1

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticExtendedDataRecord DiagnosticDataIdentifierSet

+ customTrigger: String [0..1]

+ recordNumber: PositiveInteger [0..1]
+ trigger: DiagnosticRecordTriggerEnum [0..1]
+ update: Boolean [0..1]

0..*
+recordElement 0..* +dataIdentifier {ordered}

DiagnosticAbstractDataIdentifier
DiagnosticParameter
+dataElement DiagnosticDataIdentifier
«atpIdentityContributor»
0..* «atpVariation,atpSplitable» + didSize: PositiveInteger [0..1]
+ bitOffset: PositiveInteger [0..1]
+ representsVin: Boolean [0..1]

«atpVariation,atpSplitable»
  
+dataElement 0..1    

Identifiable DiagnosticMapping
DiagnosticDataElement DiagnosticDemProvidedDataMapping
+dataElement
+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1] + dataProvider: NameToken [0..1]
0..1
+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 6.3: Modeling of associated event identification

[constr_1768] Existence of attribute DiagnosticEvent.associatedEventI-

dentification dAttribute DiagnosticEvent.associatedEventIdentifica-
tion shall exist if the respective DiagnosticEvent is mapped to a Diagnostic-
TroubleCodeUds and one of the following conditions is fulfilled:
• The reference DiagnosticTroubleCodeUds.dtcProps.snapshotRecord-
Content exists and the referenced DiagnosticDataIdentifierSet refer-
ences at least one dataIdentifier.dataElement.dataElement that is also
referenced by a DiagnosticDemProvidedDataMapping that has attribute
dataProvider set to the value DEM_EVENT_ASSOCIATED_IDENTIFICATION.

178 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• The reference DiagnosticTroubleCodeUds.dtcProps.extended-

DataRecord exists and the referenced DiagnosticExtendedDataRecord
aggregates at least one recordElement.dataElement that is also ref-
erenced by a DiagnosticDemProvidedDataMapping that has attribute
dataProvider set to the value DEM_EVENT_ASSOCIATED_IDENTIFICA-
TION.
c()
The use case described in [TPS_DEXT_01151] and [constr_1768] is depicted in Fig-
ure 6.3.
Please note that [constr_1768] only describes the minimum viable scenario for the
usage of attribute DiagnosticEvent.associatedEventIdentification. It is
also possible that more than one DiagnosticDataElement exists that is referenced
by a DiagnosticDemProvidedDataMapping where attribute dataProvider is set
to the value DEM_EVENT_ASSOCIATED_IDENTIFICATION.

6.3 DiagnosticTroubleCode
DiagnosticTroubleCodes (i.e. the ECU external view on diagnostic events) are
defined together with their properties and mapped to DiagnosticEvents using Di-
agnosticEventToTroubleCodeUdsMapping.
[TPS_DEXT_03012] Three kinds of DTCs dThere are three kinds of DTCs repre-
sented as specializations of DiagnosticTroubleCode:
• non OBD relevant DTCs (DiagnosticTroubleCodeUds)
• OBD relevant DTCs (DiagnosticTroubleCodeObd)
• J1939 [22] relevant DTCs (DiagnosticTroubleCodeJ1939)
Properties individual to such a DTC specialization are modeled as attributes of Di-
agnosticTroubleCodeUds, DiagnosticTroubleCodeObd and Diagnostic-
TroubleCodeJ1939, respectively.c(RS_DEXT_00024)

179 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

  
   

DiagnosticCommonElement DiagnosticCommonElement «enumeration»
DiagnosticTroubleCodeGroup +dtc DiagnosticTroubleCode DiagnosticTroubleCodeJ1939DtcKindEnum
«atpVariation,atpSplitable» 0..* standard
«atpVariation»
+ groupNumber: PositiveInteger [0..1] serviceOnly

DiagnosticTroubleCodeUds DiagnosticTroubleCodeJ1939

+ considerPtoStatus: Boolean [0..1] + fmi: PositiveInteger [0..1]

+ eventObdReadinessGroup: NameToken [0..1] + kind: DiagnosticTroubleCodeJ1939DtcKindEnum [0..1]
+ functionalUnit: PositiveInteger [0..1]
+ severity: DiagnosticUdsSeverityEnum [0..1]
«atpVariation»
+ udsDtcValue: PositiveInteger [0..1]
+ wwhObdDtcClass: DiagnosticWwhObdDtcClassEnum [0..1]

DiagnosticTroubleCodeObd

«atpVariation»
+ considerPtoStatus: Boolean [0..1]
+ obdDTCValue: PositiveInteger [0..1]

+dtcProps 0..1 +dtcProps 0..1 +dtcProps 0..1 +spn 0..1

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticTroubleCodeProps DiagnosticJ1939Spn

+ environmentCaptureToReporting: EnvironmentCaptureToReportingEnum [0..1] + spn: PositiveInteger [0..1]

+ immediateNvDataStorage: Boolean [0..1]
+ maxNumberFreezeFrameRecords: PositiveInteger [0..1]
+ significance: DiagnosticSignificanceEnum [0..1]
«atpVariation»
+ priority: PositiveInteger [0..1]

«enumeration» «enumeration»
DiagnosticWwhObdDtcClassEnum DiagnosticUdsSeverityEnum

demDtcWwhObdClassB1 noSeverity
demDtcWwhObdClassA maintenanceOnly
demDtcWwhObdClassB2 immediately
demDtcWwhObdClassC checkAtNextHalt
demDtcWwhObdClassNoInformation

Figure 6.4: Modeling of DiagnosticTroubleCode

Class DiagnosticTroubleCodeUds
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This element is used to describe non OBD-relevant DTCs.
Tags:atp.recommendedPackage=DiagnosticTroubleCodes
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticTroubleCode,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
considerPto Boolean 0..1 attr This attribute describes the affection of the event by the
Status Dem PTO handling.
True: the event is affected by the Dem PTO handling.
False: the event is not affected by the Dem PTO handling.
dtcProps DiagnosticTroubleCode 0..1 ref Defined properties associated with the DemDTC.
Props
eventObd NameToken 0..1 attr This attribute specifies the Event OBD Readiness group
Readiness for PID $01 and PID $41 computation. This attribute is
Group only applicable for emission-related ECUs.
5

180 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticTroubleCodeUds
functionalUnit PositiveInteger 0..1 attr This attribute specifies a 1-byte value which identifies the
corresponding basic vehicle / system function which
reports the DTC. This parameter is necessary for the
report of severity information.
severity DiagnosticUdsSeverity 0..1 attr DTC severity according to ISO 14229-1.
Enum
udsDtcValue PositiveInteger 0..1 attr Unique Diagnostic Trouble Code value for UDS.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
wwhObdDtc DiagnosticWwhObdDtc 0..1 attr This attribute is used to identify (if applicable) the
Class ClassEnum corresponding severity class of an WWH-OBD DTC.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.9: DiagnosticTroubleCodeUds

[constr_1757] Existence of attribute DiagnosticTroubleCodeUds.udsDtc-

Value dFor each DiagnosticTroubleCodeUds, attribute udsDtcValue shall exist
at the time when the DEXT is complete.c()
Class DiagnosticTroubleCodeObd
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This element is used to define OBD-relevant DTCs.
Tags:atp.recommendedPackage=DiagnosticTroubleCodes
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticTroubleCode,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
considerPto Boolean 0..1 attr This attribute describes the affection of the event by the
Status Dem PTO handling.
True: the event is affected by the Dem PTO handling.
False: the event is not affected by the Dem PTO handling.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
dtcProps DiagnosticTroubleCode 0..1 ref Defined properties associated with the DemDTC.
Props
eventReadiness EventObdReadiness 0..1 aggr This aggregation allows for the variant definition of the
Group Group attribute eventObdReadinessGroup.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=eventReadinessGroup, eventReadiness
Group.variationPoint.shortLabel
vh.latestBindingTime=postBuild
obdDTCValue PositiveInteger 0..1 attr Unique Diagnostic Trouble Code value for OBD.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.10: DiagnosticTroubleCodeObd

181 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticAbstractDataIdentifier
DiagnosticDataIdentifierSet DiagnosticDataIdentifier
+dataIdentifier
+ didSize: PositiveInteger [0..1]
0..*
+ representsVin: Boolean [0..1]
{ordered}

+snapshotRecordContent 0..1 +legislatedFreezeFrameContentWwhObd 0..1

  
   
«atpVariation» «atpVariation»
 

DiagnosticCommonElement DiagnosticTroubleCode
DiagnosticTroubleCodeProps DiagnosticTroubleCodeUds

+ environmentCaptureToReporting: EnvironmentCaptureToReportingEnum [0..1] + considerPtoStatus: Boolean [0..1]

+ immediateNvDataStorage: Boolean [0..1] +dtcProps + eventObdReadinessGroup: NameToken [0..1]
+ maxNumberFreezeFrameRecords: PositiveInteger [0..1] + functionalUnit: PositiveInteger [0..1]
0..1
+ significance: DiagnosticSignificanceEnum [0..1] + severity: DiagnosticUdsSeverityEnum [0..1]
«atpVariation» «atpVariation»
+ priority: PositiveInteger [0..1] + udsDtcValue: PositiveInteger [0..1]
+ wwhObdDtcClass: DiagnosticWwhObdDtcClassEnum [0..1]

DiagnosticCommonElement
DiagnosticAging
+aging
«atpVariation»
0..1 + threshold: PositiveInteger [0..1]

  
   
«atpVariation,atpSplitable»   «atpVariation,atpSplitable»
«atpVariation,atpSplitable»

+extendedDataRecord 0..* +freezeFrame 0..* +agingCycle 0..1

DiagnosticCommonElement DiagnosticCommonElement DiagnosticCommonElement

DiagnosticExtendedDataRecord DiagnosticFreezeFrame DiagnosticOperationCycle

+ customTrigger: String [0..1] + customTrigger: String [0..1] + automaticEnd: Boolean [0..1]

+ recordNumber: PositiveInteger [0..1] + trigger: DiagnosticRecordTriggerEnum [0..1] + cycleStatusStorage: Boolean [0..1]
+ trigger: DiagnosticRecordTriggerEnum [0..1] + update: Boolean [0..1] + type: DiagnosticOperationCycleTypeEnum [0..1]
+ update: Boolean [0..1] «atpVariation»
+ recordNumber: PositiveInteger [0..1]

+memoryDestination 0..*

DiagnosticCommonElement
DiagnosticMemoryDestination

+ dtcStatusAvailabilityMask: PositiveInteger [0..1]

+ eventDisplacementStrategy: DiagnosticEventDisplacementStrategyEnum [0..1]
+ maxNumberOfEventEntries: PositiveInteger [0..1]
+ memoryEntryStorageTrigger: DiagnosticMemoryEntryStorageTriggerEnum [0..1]
+ typeOfFreezeFrameRecordNumeration: DiagnosticTypeOfFreezeFrameRecordNumerationEnum [0..1]

«enumeration» «enumeration» «enumeration»

DiagnosticRecordTriggerEnum DiagnosticWwhObdDtcClassEnum DiagnosticOperationCycleTypeEnum

confirmed demDtcWwhObdClassB1 ignition

fdcThreshold demDtcWwhObdClassA obdDrivingCycle
pending demDtcWwhObdClassB2 warmup
testFailed demDtcWwhObdClassC other
custom demDtcWwhObdClassNoInformation
testFailedThisOperationCycle

«enumeration» «enumeration»
DiagnosticSignificanceEnum EnvironmentCaptureToReportingEnum

fault captureSynchronousToReporting
occurence captureAsynchronousToReporting

Figure 6.5: Modeling of DiagnosticTroubleCodeUds

Class EventObdReadinessGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This meta-class represents the ability to define the value of attribute eventObdReadinessGroup. It is only
introduced to allow for a variant modeling of this attribute.
Base ARObject
5

182 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class EventObdReadinessGroup
Attribute Type Mult. Kind Note
eventObd NameToken 0..1 attr This attribute specifies the Event OBD Readiness group
Readiness for PID $01 and PID $41 computation. This attribute is
Group only applicable for emission-related ECUs.

Table 6.11: EventObdReadinessGroup

[constr_1758] Existence of attribute DiagnosticTroubleCodeObd.obdDTC-

Value dFor each DiagnosticTroubleCodeObd, attribute obdDTCValue shall exist
at the time when the DEXT is complete.c()
[TPS_DEXT_03013] Common properties of a DTC dProperties that are often com-
mon for a group of DiagnosticTroubleCodeUds elements are modeled as at-
tributes of DiagnosticTroubleCodeProps.c(RS_DEXT_00024)
[constr_1349] Value of udsDtcValue shall be unique dThe value of Diagnos-
ticTroubleCodeUds.udsDtcValue shall be unique for all DiagnosticTrouble-
CodeUds that refer to the same DiagnosticMemoryDestination via the reference
DiagnosticTroubleCodeUds.dtcProps.memoryDestination.c()
Class DiagnosticTroubleCode (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note A diagnostic trouble code defines a unique identifier that is shown to the diagnostic tester.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticTroubleCodeJ1939, DiagnosticTroubleCodeObd, DiagnosticTroubleCodeUds
Attribute Type Mult. Kind Note
– – – – –
Table 6.12: DiagnosticTroubleCode

[TPS_DEXT_03014] Semantics of DiagnosticTroubleCodeGroup dThe Diag-

nosticTroubleCodeGroup element is used to define groups of DTCs that belong
together. Each DiagnosticTroubleCodeGroup has its own groupNumber value
assigned.c(RS_DEXT_00024)
Class DiagnosticTroubleCodeGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note The diagnostic trouble code group defines the DTCs belonging together and thereby forming a group.
Tags:atp.recommendedPackage=DiagnosticTroubleCodes
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
5

183 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticTroubleCodeGroup
dtc DiagnosticTroubleCode * ref This represents the collection of DiagnosticTroubleCodes
defined by this DiagnosticTroubleCodeGroup.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=dtc.diagnosticTroubleCode, dtc.variation
Point.shortLabel
vh.latestBindingTime=postBuild
groupNumber PositiveInteger 0..1 attr This represents the base number of the DTC group.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.13: DiagnosticTroubleCodeGroup

[constr_1830] Existence of DiagnosticTroubleCodeGroup.groupNumber dFor

each DiagnosticTroubleCodeGroup, attribute groupNumber shall exist at the
time when the DEXT is complete.c()
[constr_1350] Value of DiagnosticTroubleCodeGroup.groupNumber shall be
unique dThe value of DiagnosticTroubleCodeGroup.groupNumber shall be
unique to any other DTC and DTC group value.c()
[constr_1351] Value of DiagnosticTroubleCodeGroup.groupNumber dTo be
compliant to ISO, the value of DiagnosticTroubleCodeGroup.groupNumber shall
be set as defined in ISO 14229-1 [16].c()
[TPS_DEXT_03000] ISO 14229-1 reserves values of DiagnosticTroubleCode-
Group.groupNumber dAny values other than those mentioned in [constr_1351] are
reserved by ISO 14229-1 [16].c(RS_DEXT_00024)
[constr_1352] Existence of maxNumberFreezeFrameRecords vs. freezeFrame
dIf the attribute DiagnosticTroubleCodeProps.maxNumberFreezeFrameRe-
cords exists than the attribute DiagnosticTroubleCodeProps.freezeFrame
shall not exist or vice versa.c()
[constr_1353] Applicability of [1352] d[constr_1352] shall apply in the identical way
(either one or the other attribute shall exist) for all DiagnosticTroubleCodeProps
within the context of all DiagnosticContributionSets of category DIAGNOS-
TIC_ECU_EXTRACT that refer to the same EcuInstance.c()
[constr_1354] Existence of attribute DiagnosticTroubleCodeProps.snap-
shotRecordContent dIf one of the attributes DiagnosticTroubleCode-
Props.maxNumberFreezeFrameRecords or DiagnosticTroubleCodeProps.
freezeFrame exists then the attribute DiagnosticTroubleCodeProps.snap-
shotRecordContent shall exist.c()
[TPS_DEXT_01064] Textually formulated content attached to DiagnosticTrou-
bleCode dThe definition of a DiagnosticTroubleCode also consists of textually
formulated content that is formalized in structure but cannot be formalized in content.

184 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

The purpose of this content is to define e.g. an error text or the possible cause that
relates to the specific DiagnosticTroubleCode.c(RS_DEXT_00024, RS_DEXT_-
00045)
[TPS_DEXT_01065] Different approaches to provide semi-formal textual content
attached to a DiagnosticTroubleCode dThere are different approaches to provide
semi-formal textual content attached to a DiagnosticTroubleCode:
• Textual description that has the character of descriptions of the Diagnostic-
TroubleCode shall be provided by means of the meta-class TraceableText,
i.e. by means of introduction.trace.
• Textual description that characterizes the DiagnosticTroubleCode with re-
spect to the ODX long name shall be provided by means of the attribute long-
Name.
c(RS_DEXT_00024, RS_DEXT_00045)
Class TraceableText
Package M2::MSR::Documentation::BlockElements::RequirementsTracing
Note This meta-class represents the ability to denote a traceable text item such as requirements etc.
The following approach applies:
• shortName represents the tag for tracing
• longName represents the head line
• category represents the kind of the tagged text
Base ARObject, DocumentViewSelectable, Identifiable, MultilanguageReferrable, Paginateable, Referrable,
Traceable
Attribute Type Mult. Kind Note
text DocumentationBlock 1 aggr This represents the text to which the tag applies.
Tags:
xml.roleElement=false
xml.roleWrapperElement=false
xml.sequenceOffset=30
xml.typeElement=false
xml.typeWrapperElement=false

Table 6.14: TraceableText

Class MultilanguageReferrable (abstract)

Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::Identifiable
Note Instances of this class can be referred to by their identifier (while adhering to namespace borders). They
also may have a longName. But they are not considered to contribute substantially to the overall
structure of an AUTOSAR description. In particular it does not contain other Referrables.
Base ARObject, Referrable
Subclasses Caption, DefItem, DocumentationContext, Identifiable, SdgCaption, TraceReferrable, Traceable
Attribute Type Mult. Kind Note
longName MultilanguageLong 0..1 aggr This specifies the long name of the object. Long name is
Name targeted to human readers and acts like a headline.

Table 6.15: MultilanguageReferrable

For more details regarding the modeling of the semi-formal text please refer to Figure
4.3.

185 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

The usage of TraceableText and StructuredReq alone would not qualify as a

semi-formal textual attachment. It is necessary to standardize the value of the cate-
gory in order to get some level of semi-formal textual description.
[TPS_DEXT_01066] Standardized values of DiagnosticTroubleCode.intro-
duction.trace dThe following possible values of DiagnosticTroubleCode.in-
troduction.trace are standardized by AUTOSAR:
• DIAG_DTC_ERROR_TEXT: this value shall be used to describe an error text.
• DIAG_DTC_REP_ACT: this value describes the associated repair for the corre-
sponding DiagnosticTroubleCode.
• DIAG_DTC_CUS_PER_SYMP: this value describes the possible customer per-
ception symptom for the corresponding DiagnosticTroubleCode.
• DIAG_DTC_POSS_CAUSE: This value describes the possible cause for the cor-
responding DiagnosticTroubleCode.
c(RS_DEXT_00001, RS_DEXT_00024, RS_DEXT_00045)
The following ARXML fragment exemplifies the usage of TraceableText along with
the standardized values of the attribute category to attach semi-formal textual de-
scriptions to a DiagnosticTroubleCodeUds.
Listing 6.2: Example for the definition of a semi-formal textual element in the context of
a DiagnosticTroubleCode
<DIAGNOSTIC-TROUBLE-CODE-UDS>
<SHORT-NAME>ExampleDTC_0001</SHORT-NAME>
<LONG-NAME>
<L-4 L="EN">My little ODX long name</L-4>
</LONG-NAME>
<DESC>
<L-2 L="EN">This DTC is a System Error DTC</L-2>
</DESC>
<INTRODUCTION>
<TRACE>
<SHORT-NAME>MyErrorText</SHORT-NAME>
<CATEGORY>DIAG_DTC_ERROR_TEXT</CATEGORY>
<P>
<L-1 L="LA">Lorem ipsum dolor sit amet, consectetur
adipisicing elit</L-1>
</P>
</TRACE>
</INTRODUCTION>
<DTC-PROPS-REF DEST="DIAGNOSTIC-TROUBLE-CODE-PROPS">/AUTOSAR/
UseCase_230/ExampleDTC_0001_Props</DTC-PROPS-REF>
<FUNCTIONAL-UNIT>1</FUNCTIONAL-UNIT>
<SEVERITY>CHECK-AT-NEXT-HALT</SEVERITY>
<UDS-DTC-VALUE>0x000001</UDS-DTC-VALUE>
</DIAGNOSTIC-TROUBLE-CODE-UDS>

[constr_1376] Multiplicity of reference DiagnosticTroubleCodeProps.memo-

ryDestination dFor every given DiagnosticTroubleCodeProps, the reference

186 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

in the role DiagnosticTroubleCodeProps.memoryDestination shall not ex-

ceed the upper multiplicity 2. [constr_1377] applies.c()
[constr_1377] Existence of reference DiagnosticTroubleCodeProps.memory-
Destination dThe reference DiagnosticTroubleCodeProps.memoryDestina-
tion shall only have the upper multiplicity 2 if one (and only one) of the referenced
DiagnosticTroubleCodeProps.memoryDestination is a DiagnosticMemo-
ryDestinationMirror.c()
DiagnosticCommonElement DiagnosticCommonElement
DiagnosticFreezeFrame DiagnosticExtendedDataRecord

+ customTrigger: String [0..1] + customTrigger: String [0..1]

+ trigger: DiagnosticRecordTriggerEnum [0..1] + recordNumber: PositiveInteger [0..1]
+ update: Boolean [0..1] + trigger: DiagnosticRecordTriggerEnum [0..1]
«atpVariation» + update: Boolean [0..1]
+ recordNumber: PositiveInteger [0..1]

  
+extendedDataRecord 0..*    
+freezeFrame 0..*
 
«atpVariation,atpSplitable» «atpVariation,atpSplitable»

DiagnosticCommonElement
DiagnosticTroubleCodeProps

+ environmentCaptureToReporting: EnvironmentCaptureToReportingEnum [0..1]

+ immediateNvDataStorage: Boolean [0..1]
+ maxNumberFreezeFrameRecords: PositiveInteger [0..1]
+ significance: DiagnosticSignificanceEnum [0..1]
«atpVariation»
+ priority: PositiveInteger [0..1]

+memoryDestination 0..*

DiagnosticCommonElement
DiagnosticMemoryDestination

+ dtcStatusAvailabilityMask: PositiveInteger [0..1]

+ eventDisplacementStrategy: DiagnosticEventDisplacementStrategyEnum [0..1]
+ maxNumberOfEventEntries: PositiveInteger [0..1]
+ memoryEntryStorageTrigger: DiagnosticMemoryEntryStorageTriggerEnum [0..1]
+ typeOfFreezeFrameRecordNumeration: DiagnosticTypeOfFreezeFrameRecordNumerationEnum [0..1]

DiagnosticMemoryDestinationPrimary DiagnosticMemoryDestinationMirror DiagnosticMemoryDestinationUserDefined

+ typeOfDtcSupported: DiagnosticTypeOfDtcSupportedEnum [0..1] + memoryId: PositiveInteger [0..1]

«enumeration» «enumeration» «enumeration»

DiagnosticTypeOfFreezeFrameRecordNumerationEnum DiagnosticTypeOfDtcSupportedEnum DiagnosticMemoryEntryStorageTriggerEnum

calculated iso11992_4 confirmed

configured iso14229_1 fdcThreshold
iso15031_6 pending
saeJ1939_73 testFailed
saeJ2012_da
«enumeration»
DiagnosticEventDisplacementStrategyEnum

full
none
prioOcc

Figure 6.6: Modeling of DiagnosticMemoryDestination

187 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticMemoryDestination (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This abstract meta-class represents a possible memory destination for a diagnostic event.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticMemoryDestinationMirror, DiagnosticMemoryDestinationPrimary, DiagnosticMemory
DestinationUserDefined
Attribute Type Mult. Kind Note
dtcStatus PositiveInteger 0..1 attr Mask for the supported DTC status bits by the Dem.
AvailabilityMask
event DiagnosticEvent 0..1 attr This attribute defines, whether support for event
Displacement DisplacementStrategy displacement is enabled or not, and which displacement
Strategy Enum strategy is followed.
maxNumberOf PositiveInteger 0..1 attr This attribute fixes the maximum number of event entries
EventEntries in the fault memory.
memoryEntry DiagnosticMemoryEntry 0..1 attr Describes the trigger to allocate an event memory entry.
StorageTrigger StorageTriggerEnum
typeOfFreeze DiagnosticTypeOf 0..1 attr This attribute defines the type of assigning freeze frame
FrameRecord FreezeFrameRecord record numbers for event-specific freeze frame records.
Numeration NumerationEnum
Table 6.16: DiagnosticMemoryDestination

Class DiagnosticMemoryDestinationPrimary
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This represents a primary memory for a diagnostic event.
Tags:atp.recommendedPackage=DiagnosticMemoryDestinations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
Destination, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
typeOfDtc DiagnosticTypeOfDtc 0..1 attr This attribute defines the format returned by Dem_Dcm
Supported SupportedEnum GetTranslationType and does not relate to/influence the
supported Dem functionality.

Table 6.17: DiagnosticMemoryDestinationPrimary

Class DiagnosticMemoryDestinationMirror
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This represents a mirror memory for a diagnostic event.
Tags:atp.recommendedPackage=DiagnosticMemoryDestinations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
Destination, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 6.18: DiagnosticMemoryDestinationMirror

188 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticMemoryDestinationUserDefined
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This represents a user-defined memory for a diagnostic event.
Tags:atp.recommendedPackage=DiagnosticMemoryDestinations
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMemory
Destination, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
memoryId PositiveInteger 0..1 attr This represents the identifier of the user-defined memory.

Table 6.19: DiagnosticMemoryDestinationUserDefined

[constr_1378] Value of DiagnosticMemoryDestinationUserDefined.memo-

ryId dWithin the scope of one DiagnosticContributionSet, no two (or more)
DiagnosticMemoryDestinationUserDefineds shall exist that share the same
value for attribute DiagnosticMemoryDestinationUserDefined.memoryIdc()
In other words, the value of the attribute DiagnosticMemoryDestinationUserDe-
fined.memoryId shall be unique within any given DiagnosticExtract.
On top of that, it is necessary to make sure that only one primary memory and only
one mirror memory is defined.
DiagnosticMapping
DiagnosticTroubleCodeUdsToTroubleCodeObdMapping

+troubleCodeUds 0..1 +troubleCodeObd 0..1

DiagnosticTroubleCode DiagnosticTroubleCode
DiagnosticTroubleCodeUds DiagnosticTroubleCodeObd

+ considerPtoStatus: Boolean [0..1] «atpVariation»

+ eventObdReadinessGroup: NameToken [0..1] + considerPtoStatus: Boolean [0..1]
+ functionalUnit: PositiveInteger [0..1] + obdDTCValue: PositiveInteger [0..1]
+ severity: DiagnosticUdsSeverityEnum [0..1]
«atpVariation»
+ udsDtcValue: PositiveInteger [0..1]
+ wwhObdDtcClass: DiagnosticWwhObdDtcClassEnum [0..1]

+dtcProps 0..1 +dtcProps 0..1

DiagnosticCommonElement
DiagnosticTroubleCodeProps

+ environmentCaptureToReporting: EnvironmentCaptureToReportingEnum [0..1]

+ immediateNvDataStorage: Boolean [0..1]
+ maxNumberFreezeFrameRecords: PositiveInteger [0..1]
+ significance: DiagnosticSignificanceEnum [0..1]
«atpVariation»
+ priority: PositiveInteger [0..1]

+aging 0..1

DiagnosticCommonElement
DiagnosticAging

«atpVariation»
+ threshold: PositiveInteger [0..1]

Figure 6.7: Mapping of UDS DTC to OBD DTC

189 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1379] Existence of DiagnosticMemoryDestinationPrimary dWithin

the scope of one DiagnosticContributionSet only one DiagnosticMemory-
DestinationPrimary shall exist.c()
[constr_1380] Existence of DiagnosticMemoryDestinationMirror dWithin the
scope of one DiagnosticContributionSet only one DiagnosticMemoryDes-
tinationMirror shall exist.c()
[constr_1725] Applicability of attribute DiagnosticMemoryDestination.dtc-
StatusAvailabilityMask dAttribute DiagnosticMemoryDestination.dtc-
StatusAvailabilityMask shall not be defined in the context of a Diagnos-
ticMemoryDestinationMirror.c()
[constr_1711] Restriction of applicability of attribute typeOfFreezeFrameRe-
cordNumeration dThe attribute typeOfFreezeFrameRecordNumeration shall
not be used in the context of a DiagnosticMemoryDestinationMirror.c()
[TPS_DEXT_01094] Semantics of meta-class DiagnosticTroubleCodeUd-
sToTroubleCodeObdMapping dThe meta-class DiagnosticTroubleCodeUd-
sToTroubleCodeObdMapping can be used to associate a DiagnosticTrouble-
CodeUds with a DiagnosticTroubleCodeObd.c()
Class DiagnosticTroubleCodeProps
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This element defines common Dtc properties that can be reused by different non OBD-relevant DTCs.
Tags:atp.recommendedPackage=DiagnosticTroubleCodePropss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
aging DiagnosticAging 0..1 ref Reference to an aging algorithm in case that an aging/
unlearning of the event is allowed.
environment EnvironmentCaptureTo 0..1 attr This attribute determines the point in time, when the data
CaptureTo ReportingEnum actually is captured.
Reporting
extendedData DiagnosticExtended * ref Defines the links to an extended data class sampler.
Record DataRecord
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=extendedDataRecord.diagnosticExtended
DataRecord, extendedDataRecord.variationPoint.short
Label
vh.latestBindingTime=preCompileTime
freezeFrame DiagnosticFreezeFrame * ref Define the links to a freeze frame class sampler.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=freezeFrame.diagnosticFreezeFrame, freeze
Frame.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
5

190 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticTroubleCodeProps
immediateNv Boolean 0..1 attr Switch to enable immediate storage triggering of an
DataStorage according event memory entry persistently to NVRAM.
true: immediate non-volatile storage triggering enabled
false: immediate non-volatile storage triggering disabled
legislated DiagnosticDataIdentifier 0..1 ref This reference identifies the layout of the WWH-OBD
FreezeFrame Set freeze frame.
ContentWwh
Stereotypes: atpVariation
Obd
Tags:vh.latestBindingTime=preCompileTime
maxNumber PositiveInteger 0..1 attr This attribute defines the number of according freeze
FreezeFrame frame records, which can maximal be stored for this
Records event. Therefore all these freeze frame records have the
same freeze frame class.
memory DiagnosticMemory * ref The event destination assigns events to none, one or
Destination Destination multiple origins.
priority PositiveInteger 0..1 attr Priority of the event, in view of full event buffer. A lower
value means higher priority.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
significance DiagnosticSignificance 0..1 attr Significance of the event, which indicates additional
Enum information concerning fault classification and resolution.
snapshot DiagnosticDataIdentifier 0..1 ref This represents the freeze frame layout as a set of DIDs.
RecordContent Set
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.20: DiagnosticTroubleCodeProps

[constr_1831] Existence of DiagnosticTroubleCodeProps.priority dFor each

DiagnosticTroubleCodeProps, attribute priority shall exist at the time when
the DEXT is complete.c()
Enumeration DiagnosticSignificanceEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note Significance level of a diagnostic event.
Literal Description
fault Failure, which affects the component/ECU itself.
Tags:atp.EnumerationLiteralIndex=0
occurence Issue, which indicates additional information concerning insufficient system behavior.
Tags:atp.EnumerationLiteralIndex=1

Table 6.21: DiagnosticSignificanceEnum

Enumeration DiagnosticUdsSeverityEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note Severity types for a DTC according to ISO 14229-1.
Literal Description
5

191 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticUdsSeverityEnum
checkAtNextHalt Check at next halt.
Tags:atp.EnumerationLiteralIndex=0
immediately Check immediately.
Tags:atp.EnumerationLiteralIndex=1
maintenanceOnly Maintenance required.
Tags:atp.EnumerationLiteralIndex=2
noSeverity No severity information available.
Tags:atp.EnumerationLiteralIndex=3

Table 6.22: DiagnosticUdsSeverityEnum

Class DiagnosticDataIdentifierSet
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This represents the ability to define a list of DiagnosticDataIdentifiers that can be reused in different
contexts.
Tags:atp.recommendedPackage=DiagnosticDataIdentifierSets
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataIdentifier DiagnosticDataIdentifier * ref Reference to an orderd list of Data Identifiers.
(ordered)

Table 6.23: DiagnosticDataIdentifierSet

Enumeration DiagnosticWwhObdDtcClassEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This meta-class represents the ability to model severity classes of an WWH-OBD DTC.
Literal Description
demDtcWwhObd This attribute represents the severity class A.
ClassA
Tags:atp.EnumerationLiteralIndex=0
demDtcWwhObd This attribute represents the severity class B1.
ClassB1
Tags:atp.EnumerationLiteralIndex=1
demDtcWwhObd This attribute represents the severity class B2.
ClassB2
Tags:atp.EnumerationLiteralIndex=2
demDtcWwhObd This attribute represents the severity class C.
ClassC
Tags:atp.EnumerationLiteralIndex=3
demDtcWwhObd This attribute represents the option to intentionally not describe a dedicated severity class of an
ClassNoInformation WWH-OBD DTC.
Tags:atp.EnumerationLiteralIndex=4

Table 6.24: DiagnosticWwhObdDtcClassEnum

192 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticTroubleCodeUdsToTroubleCodeObdMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note This meta-class represents the ability to associate a UDS trouble code to an OBD trouble code.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
troubleCode DiagnosticTroubleCode 0..1 ref This represents the OBD DTC referenced in the mapping
Obd Obd between UDS and OBD DTCs.
troubleCodeUds DiagnosticTroubleCode 0..1 ref This represents the UDS DTC referenced in the mapping
Uds between UDS and OBD DTCs.

Table 6.25: DiagnosticTroubleCodeUdsToTroubleCodeObdMapping

Enumeration DiagnosticTypeOfFreezeFrameRecordNumerationEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note FreezeFrame record numeration type
Literal Description
calculated Freeze frame records will be numbered consecutive starting by 1 in their chronological order.
Tags:atp.EnumerationLiteralIndex=0
configured Freeze frame records will be numbered based on the given configuration in their chronological order.
Tags:atp.EnumerationLiteralIndex=1

Table 6.26: DiagnosticTypeOfFreezeFrameRecordNumerationEnum

6.4 DiagnosticExtendedDataRecord
[TPS_DEXT_03008] Semantics of DiagnosticExtendedDataRecord dA Diag-
nosticExtendedDataRecord contains DiagnosticDataElements that are or-
dered by the bitOffset.c(RS_DEXT_00032)
[constr_1355] Value of extendedDataRecord.recordNumber dTo be compliant to
ISO, the value of extendedDataRecord.recordNumber shall be set in the interval
as defined in ISO 14229-1 [16].c()
[constr_1509] extendedDataRecord.recordNumber shall be unique within pri-
mary fault memory dFor all DiagnosticTroubleCodeProps that refer to Diag-
nosticMemoryDestinationPrimary in the role memoryDestination there shall
be no two extendedDataRecord.recordNumber with the same value.c()
[constr_1510] extendedDataRecord.recordNumber shall be unique within mir-
ror fault memory dFor all DiagnosticTroubleCodeProps that refer to Diagnos-
ticMemoryDestinationMirror in the role memoryDestination there shall be
no two extendedDataRecord.recordNumber with the same value.c()

193 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

ARElement «enumeration»
DiagnosticCommonElement DiagnosticRecordTriggerEnum

confirmed
fdcThreshold
pending
testFailed
custom
testFailedThisOperationCycle

DiagnosticExtendedDataRecord DiagnosticParameter
+recordElement
+ customTrigger: String [0..1] «atpIdentityContributor»
+ recordNumber: PositiveInteger [0..1] 0..* + bitOffset: PositiveInteger [0..1]
+ trigger: DiagnosticRecordTriggerEnum [0..1]
+ update: Boolean [0..1]

«atpVariation,atpSplitable»

+dataElement 0..1

  
Identifiable
   
 DiagnosticDataElement

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 6.8: Modeling of DiagnosticExtendedDataRecord

[constr_1511] extendedDataRecord.recordNumber shall be unique within

user-defined fault memory dFor all DiagnosticTroubleCodeProps that refer to
DiagnosticMemoryDestinationUserDefined in the role memoryDestination
there shall be no two extendedDataRecord.recordNumber with the same value for
any DiagnosticMemoryDestinationUserDefined referenced as Diagnostic-
TroubleCodeProps.memoryDestination with a given value of memoryId.c()
[TPS_DEXT_01143] Definition of a custom trigger for an extended data record dIt
is possible to define a custom trigger for the capturing of an extended data record. The
custom nature, however, severely limits the possibilities for a formal description of such
a trigger. Therefore, AUTOSAR can only provide a means to verbally describe how the
custom trigger shall operate.
For this purpose the attribute DiagnosticExtendedDataRecord.customTrigger
has been defined.c(RS_DEXT_00033)
[constr_1616] Existence of attribute DiagnosticExtendedDataRecord.cus-
tomTrigger dThe attribute DiagnosticExtendedDataRecord.customTrigger
shall only exist if the attribute DiagnosticExtendedDataRecord.trigger is set to
the value DiagnosticRecordTriggerEnum.custom.c()
Class DiagnosticExtendedDataRecord
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticExtendedDataRecord
Note Description of an extended data record.
Tags:atp.recommendedPackage=DiagnosticExtendedDataRecords
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
customTrigger String 0..1 attr This attribute shall be taken to verbally describe the
nature of the custom trigger.
5

194 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticExtendedDataRecord
recordElement DiagnosticParameter * aggr Defined DataElements in the extended record element.
recordNumber PositiveInteger 0..1 attr This attribute specifies an unique identifier for an
extended data record.
trigger DiagnosticRecord 0..1 attr This attribute specifies the primary trigger to allocate an
TriggerEnum event memory entry.
update Boolean 0..1 attr This attribute defines when an extended data record is
captured.
True: This extended data record is captured every time.
False: This extended data record is only captured for new
event memory entries.

Table 6.27: DiagnosticExtendedDataRecord

[constr_1756] Existence of attributes DiagnosticExtendedDataRecord.trig-

ger and update dFor each DiagnosticExtendedDataRecord, attributes trig-
ger and update shall only exist at the time when the DEXT is complete if at
least one DiagnosticDataElement is aggregated by a DiagnosticExtended-
DataRecord.recordElement in the role dataElement to which no reference in the
role DiagnosticDemProvidedDataMapping.dataElement exists.c()
[constr_1760] Existence of DiagnosticExtendedDataRecord.recordElement
dFor each DiagnosticExtendedDataRecord, at least one aggregation of Diag-
nosticParameter in the role recordElement shall exist at the time when the
DEXT is complete.c()
[constr_1832] Existence of DiagnosticExtendedDataRecord.recordNumber
dFor each DiagnosticExtendedDataRecord, attribute recordNumber shall exist
at the time when the DEXT is complete.c()
Enumeration DiagnosticRecordTriggerEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticFreezeFrame
Note Triggers to allocate an event memory entry.
Literal Description
confirmed capture on "Confirmed"
Tags:atp.EnumerationLiteralIndex=0
custom implement custom capture
Tags:atp.EnumerationLiteralIndex=4
fdcThreshold capture on "FDC Threshold"
Tags:atp.EnumerationLiteralIndex=1
pending capture on "Pending"
Tags:atp.EnumerationLiteralIndex=2
testFailed capture on "Test Failed"
Tags:atp.EnumerationLiteralIndex=3
5

195 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticRecordTriggerEnum
testFailedThis Test Failed This Operation Cycle.
OperationCycle
Tags:atp.EnumerationLiteralIndex=5

Table 6.28: DiagnosticRecordTriggerEnum

[constr_1859] Usage of DiagnosticRecordTriggerEnum.testFailedThisOp-

erationCycle dThe enumeration value DiagnosticRecordTriggerEnum.test-
FailedThisOperationCycle shall only be used in the context of meta-class Di-
agnosticFreezeFrame.c()

6.5 DiagnosticFreezeFrame
[TPS_DEXT_03009] Semantics of DiagnosticFreezeFrame dA Diagnos-
ticFreezeFrame needs an ordered list of references to DiagnosticDataIdenti-
fiers. However, this reference is not modeled directly but in the context of meta-class
DiagnosticTroubleCodeProps.c(RS_DEXT_00033)
For more details, please refer to Figure 6.4.
[constr_1357] Value of freezeFrame.recordNumber dTo be compliant to ISO, the
value of freezeFrame.recordNumber shall be set in the interval as defined in ISO
14229-1 [16].c()
[constr_1512] freezeFrame.recordNumber shall be unique within primary fault
memory dFor all DiagnosticTroubleCodeProps that refer to DiagnosticMem-
oryDestinationPrimary in the role memoryDestination there shall be no two
freezeFrame.recordNumber with the same value.c()
[constr_1513] freezeFrame.recordNumber shall be unique within mirror fault
memory dFor all DiagnosticTroubleCodeProps that refer to DiagnosticMem-
oryDestinationMirror in the role memoryDestination there shall be no two
freezeFrame.recordNumber with the same value.c()
[constr_1514] freezeFrame.recordNumber shall be unique within user-defined
fault memory dFor all DiagnosticTroubleCodeProps that refer to Diagnos-
ticMemoryDestinationUserDefined in the role memoryDestination there
shall be no two freezeFrame.recordNumber with the same value for any Diag-
nosticMemoryDestinationUserDefined referenced as DiagnosticTrouble-
CodeProps.memoryDestination with a given value of memoryId.c()
[TPS_DEXT_01144] Definition of a custom trigger for a freeze frame dIt is possible
to define a custom trigger for the capturing of a freeze frame. The custom nature, how-
ever, severely limits the possibilities for a formal description of such a trigger. There-
fore, AUTOSAR can only provide a means to verbally describe how the custom trigger
shall operate.

196 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

For this purpose the attribute DiagnosticFreezeFrame.customTrigger has been

defined.c(RS_DEXT_00033)
ARElement
DiagnosticCommonElement

«enumeration» DiagnosticFreezeFrame
DiagnosticRecordTriggerEnum
+ customTrigger: String [0..1]
confirmed + trigger: DiagnosticRecordTriggerEnum [0..1]
fdcThreshold + update: Boolean [0..1]
pending
«atpVariation»
testFailed
+ recordNumber: PositiveInteger [0..1]
custom
testFailedThisOperationCycle

Figure 6.9: Modeling of DiagnosticFreezeFrame

[constr_1617] Existence of attribute DiagnosticFreezeFrame.customTrig-

ger dThe attribute DiagnosticFreezeFrame.customTrigger shall only exist if
the attribute DiagnosticFreezeFrame.trigger is set to the value Diagnosti-
cRecordTriggerEnum.custom.c()
Class DiagnosticFreezeFrame
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticFreezeFrame
Note This element describes combinations of DIDs for a non OBD relevant freeze frame.
Tags:atp.recommendedPackage=DiagnosticFreezeFrames
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
customTrigger String 0..1 attr This attribute shall be taken to verbally describe the
nature of the custom trigger.
recordNumber PositiveInteger 0..1 attr This attribute defines a record number for a freeze frame
record.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
trigger DiagnosticRecord 0..1 attr This attribute defines the primary trigger to allocate an
TriggerEnum event memory entry.
update Boolean 0..1 attr This attribute defines the approach when the freeze frame
record is stored/updated.
True: FreezeFrame record is captured every time.
False: FreezeFrame record is only captured for new event
memory entries.

Table 6.29: DiagnosticFreezeFrame

[constr_1833] Existence of DiagnosticFreezeFrame.trigger dFor each Diag-

nosticFreezeFrame, attribute trigger shall exist at the time when the DEXT is
complete.c()

197 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.6 DiagnosticCondition
[TPS_DEXT_03010] Combination of DiagnosticConditions to Diagnostic-
ConditionGroups dDiagnosticConditions are combined to Diagnostic-
ConditionGroups and define a certain number of checks (e.g. correct voltage range)
before the event report is accepted or the event gets qualified.c(RS_DEXT_00027,
RS_DEXT_00028, RS_DEXT_00030, RS_DEXT_00031)
ARElement
DiagnosticCommonElement

DiagnosticCondition

+ initValue: Boolean [0..1]

DiagnosticStorageCondition DiagnosticEnableCondition

Figure 6.10: Modeling of DiagnosticCondition

[TPS_DEXT_03001] Different types of conditions dThere are two different types

of conditions: DiagnosticEnableConditions and DiagnosticStorageCondi-
tion:
• As long as the DiagnosticEnableCondition is not fulfilled, the event reports
are not valid and therefore will not be accepted.
• As long as the DiagnosticStorageCondition is not fulfilled, the event is not
stored in the event memory.
c(RS_DEXT_00027)
Class DiagnosticCondition (abstract)
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticCondition
Note Abstract element for StorageConditions and EnableConditions.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticEnableCondition, DiagnosticStorageCondition
Attribute Type Mult. Kind Note
5

198 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticCondition (abstract)
initValue Boolean 0..1 attr Defines the initial status for enable or disable of
acceptance/storage of event reports of a diagnostic event.
The value is the initialization after power up (before this
condition is reported the first time).
true: acceptance/storage of a diagnostic event enabled
false: acceptance/storage of a diagnostic event disabled

Table 6.30: DiagnosticCondition

[constr_1834] Existence of DiagnosticCondition.initValue dFor each Diag-

nosticCondition, attribute initValue shall exist at the time when the DEXT is
complete.c()
Class DiagnosticEnableCondition
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticCondition
Note Specification of an enable condition.
Tags:atp.recommendedPackage=DiagnosticConditions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticCondition,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 6.31: DiagnosticEnableCondition

Class DiagnosticStorageCondition
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticCondition
Note Specification of a storage condition.
Tags:atp.recommendedPackage=DiagnosticConditions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticCondition,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 6.32: DiagnosticStorageCondition

6.7 Diagnostic Debouncing

[TPS_DEXT_01048] Actual algorithm for the diagnostic event debouncing dThe
actual algorithm for the debouncing is represented by subclasses of DiagEvent-
DebounceAlgorithm aggregated in the role DiagnosticDebounceAlgorithm-
Props.debounceAlgorithm.c(RS_DEXT_00023, RS_DEXT_00053)

199 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

ARElement
DiagnosticContributionSet

«atpSplitable»
+commonProperties 0..1

«atpVariation»
DiagnosticCommonProps

+ agingRequiresTestedCycle: Boolean [0..1]

+ clearDtcLimitation: DiagnosticClearDtcLimitationEnum [0..1]
+ defaultEndianness: ByteOrderEnum [0..1]
+ environmentDataCapture: DiagnosticDataCaptureEnum [0..1]
+ maxNumberOfRequestCorrectlyReceivedResponsePending: PositiveInteger [0..1]
+ occurrenceCounterProcessing: DiagnosticOccurrenceCounterProcessingEnum [0..1]
+ resetConfirmedBitOnOverflow: Boolean [0..1]
+ responseOnAllRequestSids: Boolean [0..1]
+ responseOnSecondDeclinedRequest: Boolean [0..1]
+ securityDelayTimeOnBoot: TimeValue [0..1]
+ statusBitHandlingTestFailedSinceLastClear: DiagnosticStatusBitHandlingTestFailedSinceLastClearEnum [0..1]
+ statusBitStorageTestFailed: Boolean [0..1]

+debounceAlgorithmProps 0..*

Referrable
«enumeration» DiagnosticDebounceAlgorithmProps
DiagnosticDebounceBehaviorEnum
+ debounceCounterStorage: Boolean [0..1]
freeze
reset «atpVariation»
+ debounceBehavior: DiagnosticDebounceBehaviorEnum [0..1]

+debounceAlgorithm 0..1

Identifiable
DiagEventDebounceAlgorithm

DiagEventDebounceCounterBased DiagEventDebounceTimeBased DiagEventDebounceMonitorInternal

+ counterBasedFdcThresholdStorageValue: Integer [0..1] «atpVariation»

«atpVariation» + timeBasedFdcThresholdStorageValue: TimeValue [0..1]
+ counterDecrementStepSize: Integer [0..1] + timeFailedThreshold: TimeValue [0..1]
+ counterFailedThreshold: Integer [0..1] + timePassedThreshold: TimeValue [0..1]
+ counterIncrementStepSize: Integer [0..1]
+ counterJumpDown: Boolean [0..1]
+ counterJumpDownValue: Integer [0..1]
+ counterJumpUp: Boolean [0..1]
+ counterJumpUpValue: Integer [0..1]
+ counterPassedThreshold: Integer [0..1]

Figure 6.11: Details of DiagnosticDebounceAlgorithmProps

In other words, the debouncing of diagnostic events can be formulated in three different
ways:
• The DiagEventDebounceCounterBased represents the ability to implement a
counter-based debouncing.
• The DiagEventDebounceTimeBased represents the ability to implement a
time-based debouncing.
• The DiagEventDebounceMonitorInternal represents the ability to imple-
ment the debouncing inside the implementation of the diagnostic monitor itself.

200 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1359] Condition for the existence of attribute DiagnosticDebounceAl-

gorithmProps.debounceCounterStorage dAttribute debounceCounterStor-
age of meta-class DiagnosticDebounceAlgorithmProps shall only exist if the ag-
gregation of attribute debounceAlgorithm at DiagnosticDebounceAlgorithm-
Props actually aggregates a DiagEventDebounceCounterBasedc()
Class DiagEventDebounceAlgorithm (abstract)
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note This class represents the ability to specify the pre-debounce algorithm which is selected and/or required
by the particular monitor.
This class inherits from Identifiable in order to allow further documentation of the expected or
implemented debouncing and to use the category for the identification of the expected / implemented
debouncing.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Subclasses DiagEventDebounceCounterBased, DiagEventDebounceMonitorInternal, DiagEventDebounceTime
Based
Attribute Type Mult. Kind Note
– – – – –
Table 6.33: DiagEventDebounceAlgorithm

Class DiagEventDebounceCounterBased
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note This meta-class represents the ability to indicate that the counter-based debounce algorithm shall be
used by the DEM for this diagnostic monitor.
This is related to set the ECUC choice container DemDebounceAlgorithmClass to DemDebounce
CounterBased.
Base ARObject, DiagEventDebounceAlgorithm, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
counterBased Integer 0..1 attr Threshold to allocate an event memory entry and to
FdcThreshold capture the Freeze Frame.
StorageValue
counter Integer 0..1 attr This value shall be taken to decrement the internal
DecrementStep debounce counter.
Size
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
counterFailed Integer 0..1 attr This value defines the event-specific limit that indicates
Threshold the "failed" counter status.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
counter Integer 0..1 attr This value shall be taken to increment the internal
IncrementStep debounce counter.
Size
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
counterJump Boolean 0..1 attr This value activates or deactivates the counter
Down jump-down behavior.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
5

201 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagEventDebounceCounterBased
counterJump Integer 0..1 attr This value represents the initial value of the internal
DownValue debounce counter if the counting direction changes from
incrementing to decrementing.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
counterJumpUp Boolean 0..1 attr This value activates or deactivates the counter jump-up
behavior.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
counterJumpUp Integer 0..1 attr This value represents the initial value of the internal
Value debounce counter if the counting direction changes from
decrementing to incrementing.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
counterPassed Integer 0..1 attr This value defines the event-specific limit that indicates
Threshold the "passed" counter status.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.34: DiagEventDebounceCounterBased

[constr_1835] Existence of DiagEventDebounceCounterBased.counter-

DecrementStepSize dFor each DiagEventDebounceCounterBased, attribute
counterDecrementStepSize shall exist at the time when the DEXT is complete.c
()
[constr_1836] Existence of DiagEventDebounceCounterBased.counterIn-
crementStepSize dFor each DiagEventDebounceCounterBased, attribute
counterIncrementStepSize shall exist at the time when the DEXT is complete.c
()
[constr_1837] Existence of DiagEventDebounceCounterBased.counter-
FailedThreshold dFor each DiagEventDebounceCounterBased, attribute
counterFailedThreshold shall exist at the time when the DEXT is complete.c()
[constr_1838] Existence of DiagEventDebounceCounterBased.counter-
PassedThreshold dFor each DiagEventDebounceCounterBased, attribute
counterPassedThreshold shall exist at the time when the DEXT is complete.c()
[constr_1766] Existence of DiagEventDebounceCounterBased.counterJump-
DownValue dFor each DiagEventDebounceCounterBased, attribute counter-
JumpDownValue shall only exist at the time when the DEXT is complete if attribute
counterJumpDown exists and is set to True.c()
[constr_1767] Existence of DiagEventDebounceCounterBased.counter-
JumpUpValue dFor each DiagEventDebounceCounterBased, attribute coun-
terJumpUpValue shall only exist at the time when the DEXT is complete if attribute
counterJumpUp exists and is set to True.c()

202 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagEventDebounceTimeBased
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note This meta-class represents the ability to indicate that the time-based pre-debounce algorithm shall be
used by the Dem for this diagnostic monitor.
This is related to set the EcuC choice container DemDebounceAlgorithmClass to DemDebounceTime
Base.
Base ARObject, DiagEventDebounceAlgorithm, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
timeBasedFdc TimeValue 0..1 attr Threshold to allocate an event memory entry and to
Threshold capture the Freeze Frame.
StorageValue
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
timeFailed TimeValue 0..1 attr This value represents the event-specific delay indicating
Threshold the "failed" status.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
timePassed TimeValue 0..1 attr This value represents the event-specific delay indicating
Threshold the "passed" status.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.35: DiagEventDebounceTimeBased

[constr_1839] Existence of attribute DiagEventDebounceTimeBased.time-

FailedThreshold dFor each DiagEventDebounceTimeBased, attribute time-
FailedThreshold shall exist at the time when the DEXT is complete.c()
[constr_1840] Existence of attribute DiagEventDebounceTimeBased.
timePassedThreshold dFor each DiagEventDebounceTimeBased, attribute
timePassedThreshold shall exist at the time when the DEXT is complete.c()
Class DiagEventDebounceMonitorInternal
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note "This meta-class represents the ability to indicate that no Dem pre-debounce algorithm shall be used for
this diagnostic monitor. The SWC might implement an internal debouncing algorithm and report qualified
(debounced) results to the Dem/DM.
Base ARObject, DiagEventDebounceAlgorithm, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 6.36: DiagEventDebounceMonitorInternal

Enumeration DiagnosticDebounceBehaviorEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm
Note Event debounce algorithm behavior options.
Literal Description
5

203 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Enumeration DiagnosticDebounceBehaviorEnum
freeze The event debounce counter will be frozen with the current value and will not change while a related
enable condition is not fulfilled or ControlDTCSetting of the related event is disabled. After all related
enable conditions are fulfilled and ControlDTCSetting of the related event is enabled again, the event
qualification will continue with the next report of the event (i.e. SetEventStatus).
Tags:atp.EnumerationLiteralIndex=0
reset The event debounce counter will be reset to initial value if a related enable condition is not fulfilled or
ControlDTCSetting of the related event is disabled. The qualification of the event will be restarted with
the next valid event report.
Tags:atp.EnumerationLiteralIndex=1

Table 6.37: DiagnosticDebounceBehaviorEnum

6.8 DiagnosticConditionGroup
[TPS_DEXT_01084] Semantics of DiagnosticConditionGroups dDiagnos-
ticConditionGroups are used to collect DiagnosticConditions that in turn
are assigned to DiagnosticEvents.c(RS_DEXT_00023, RS_DEXT_00028, RS_-
DEXT_00029)
ARElement
DiagnosticCommonElement

DiagnosticConditionGroup

DiagnosticStorageConditionGroup DiagnosticEnableConditionGroup

«atpVariation,atpSplitable»
   «atpVariation,atpSplitable»

   

+storageCondition 1..* +enableCondition 1..*

DiagnosticCondition DiagnosticCondition
DiagnosticStorageCondition DiagnosticEnableCondition

Figure 6.12: Modeling of DiagnosticConditionGroup

204 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticConditionGroup (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticConditionGroup
Note Abstract element for StorageConditionGroups and EnableConditionGroups.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticEnableConditionGroup, DiagnosticStorageConditionGroup
Attribute Type Mult. Kind Note
– – – – –
Table 6.38: DiagnosticConditionGroup

Class DiagnosticEnableConditionGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticConditionGroup
Note Enable condition group which includes one or several enable conditions.
Tags:atp.recommendedPackage=DiagnosticConditions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticConditionGroup,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
enableCondition DiagnosticEnable 1..* ref Reference to enableConditions that are part of the Enable
Condition ConditionGroup.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=enableCondition.diagnosticEnableCondition,
enableCondition.variationPoint.shortLabel
vh.latestBindingTime=postBuild

Table 6.39: DiagnosticEnableConditionGroup

[constr_1841] Existence of DiagnosticEnableConditionGroup.enableCon-

dition dFor each DiagnosticEnableConditionGroup, attribute enableCondi-
tion shall exist at the time when the DEXT is complete.c()
Class DiagnosticStorageConditionGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticConditionGroup
Note Storage condition group which includes one or several storage conditions.
Tags:atp.recommendedPackage=DiagnosticConditions
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticConditionGroup,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
storage DiagnosticStorage 1..* ref Reference to storageConditions that are part of the
Condition Condition StorageConditionGroup.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=storageCondition.diagnosticStorage
Condition, storageCondition.variationPoint.shortLabel
vh.latestBindingTime=postBuild

Table 6.40: DiagnosticStorageConditionGroup

[constr_1842] Existence of DiagnosticStorageConditionGroup.storage-

Condition dFor each DiagnosticStorageConditionGroup, attribute storage-
Condition shall exist at the time when the DEXT is complete.c()

205 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.9 DiagnosticMapping
The mapping concept of the DiagnosticExtract template has been designed to
support the decentralized and independent definition of diagnostic requirements that
can be linked together at a late point during the development process.
It also supports the use of mapping contributions collected from various sources in
order to reduce manual mapping work by the ECU integrator.
[TPS_DEXT_03002] Two kind of mappings dFor diagnostic event handling, there are
two kinds of mappings:
• Mapping between a DiagnosticEvent and another diagnostic definition.
• Mapping between a DiagnosticEvent and a SWC service port.
c(RS_DEXT_00023, RS_DEXT_00052)
Figure 6.13 gives an overview on the different types of mappings available for diagnos-
tic event handling.
ARElement
DiagnosticCommonElement

DiagnosticMapping

DiagnosticSwMapping

DiagnosticEventPortMapping DiagnosticEnableConditionPortMapping DiagnosticOperationCyclePortMapping DiagnosticStorageConditionPortMapping

DiagnosticFimFunctionMapping

Figure 6.13: Modeling of DiagnosticMapping

206 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticMapping (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Abstract element for different kinds of diagnostic mappings.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticDemProvidedDataMapping, DiagnosticEventToDebounceAlgorithmMapping, DiagnosticEvent
ToEnableConditionGroupMapping, DiagnosticEventToOperationCycleMapping, DiagnosticEventTo
SecurityEventMapping, DiagnosticEventToStorageConditionGroupMapping, DiagnosticEventToTrouble
CodeJ1939Mapping, DiagnosticEventToTroubleCodeUdsMapping, DiagnosticFimAliasEventGroup
Mapping, DiagnosticFimAliasEventMapping, DiagnosticInhibitSourceEventMapping, DiagnosticJ1939
SpnMapping, DiagnosticSecurityEventReportingModeMapping, DiagnosticServiceDataMapping,
DiagnosticSwMapping, DiagnosticTroubleCodeUdsToTroubleCodeObdMapping
Attribute Type Mult. Kind Note
– – – – –
Table 6.41: DiagnosticMapping

6.9.1 DiagnosticEvent to DtcUds Mapping

[TPS_DEXT_03003] Semantics of DiagnosticEventToTroubleCodeUdsMap-

ping dThe DiagnosticEventToTroubleCodeUdsMapping is used to assign one
(1:1) or multiple (n:1) DiagnosticEvents to a DiagnosticTroubleCodeUds.
In case of n:1, multiple instances of DiagnosticEventToTroubleCodeUdsMap-
ping with the same reference of role troubleCodeUds but different references of
role diagnosticEvent have to be defined.c(RS_DEXT_00023, RS_DEXT_00024,
RS_DEXT_00025)
DiagnosticMapping
DiagnosticEventToTroubleCodeUdsMapping

+diagnosticEvent 0..1 +troubleCodeUds 0..1

DiagnosticCommonElement DiagnosticTroubleCode
DiagnosticEvent DiagnosticTroubleCodeUds

+ associatedEventIdentification: PositiveInteger [0..1] + considerPtoStatus: Boolean [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1] + eventObdReadinessGroup: NameToken [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1] + functionalUnit: PositiveInteger [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1] + severity: DiagnosticUdsSeverityEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1] «atpVariation»
+ prestoredFreezeframeStoredInNvm: Boolean [0..1] + udsDtcValue: PositiveInteger [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1] + wwhObdDtcClass: DiagnosticWwhObdDtcClassEnum [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 6.14: DiagnosticEventToDtcUdsMapping

207 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEventToTroubleCodeUdsMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines which UDS Diagnostic Trouble Code is applicable for a DiagnosticEvent.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref Reference to a DiagnosticEvent to which a UDS
Diagnostic Trouble Code is assigned.
troubleCodeUds DiagnosticTroubleCode 0..1 ref Reference to an UDS Diagnostic Trouble Code assigned
Uds to a DiagnosticEvent.

Table 6.42: DiagnosticEventToTroubleCodeUdsMapping

6.9.2 DiagnosticEvent to DiagnosticOperationCycle Mapping

[TPS_DEXT_01086] Reference to DiagnosticOperationCycle dA Diagnos-

ticEvent needs to be assigned to exactly one DiagnosticOperationCycle.c
(RS_DEXT_00024, RS_DEXT_00054)
DiagnosticMapping
DiagnosticEventToOperationCycleMapping

+diagnosticEvent 0..1 +operationCycle 0..1

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticEvent DiagnosticOperationCycle

+ associatedEventIdentification: PositiveInteger [0..1] + automaticEnd: Boolean [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1] + cycleStatusStorage: Boolean [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1] + type: DiagnosticOperationCycleTypeEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

«enumeration»
DiagnosticOperationCycleTypeEnum

ignition
obdDrivingCycle
warmup
other

Figure 6.15: DiagnosticEventToOperationCycleMapping

208 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEventToOperationCycleMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines which OperationCycle is applicable for a DiagnosticEvent.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref Reference to a DiagnosticEvent to which an Operation
Cycle is assigned.
operationCycle DiagnosticOperation 0..1 ref Reference to an OperationCycle assigned to a Diagnostic
Cycle Event.

Table 6.43: DiagnosticEventToOperationCycleMapping

6.9.3 DiagnosticEvent to DebounceAlgorithm Mapping

[TPS_DEXT_03004] DiagnosticEvent and DiagnosticDebounceAlgorithm-

Props dIf a DiagnosticEvent has to be debounced, it must be mapped to
the appropriate DiagnosticDebounceAlgorithmProps.c(RS_DEXT_00023, RS_-
DEXT_00053)
[TPS_DEXT_03005] Existence of DiagnosticEventToDebounceAlgorith-
mMapping dThe DiagnosticEventToDebounceAlgorithmMapping shall not be
created if the DiagnosticEvent is not debounced.c(RS_DEXT_00023, RS_DEXT_-
00053)
DiagnosticMapping
DiagnosticEventToDebounceAlgorithmMapping

+diagnosticEvent 0..1 +debounceAlgorithm 0..1

DiagnosticCommonElement Referrable
DiagnosticEvent DiagnosticDebounceAlgorithmProps

+ associatedEventIdentification: PositiveInteger [0..1] + debounceCounterStorage: Boolean [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1] «atpVariation»
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1] + debounceBehavior: DiagnosticDebounceBehaviorEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 6.16: DiagnosticEventToDebounceAlgorithmMapping

209 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEventToDebounceAlgorithmMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines which Debounce Algorithm is applicable for a DiagnosticEvent.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
debounce DiagnosticDebounce 0..1 ref Reference to a DebounceAlgorithm assigned to a
Algorithm AlgorithmProps DiagnosticEvent.
diagnosticEvent DiagnosticEvent 0..1 ref Reference to a DiagnosticEvent to which a Debounce
Algorithm is assigned.

Table 6.44: DiagnosticEventToDebounceAlgorithmMapping

Class DiagnosticDebounceAlgorithmProps
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm
Note Defines properties for the debounce algorithm class.
Base ARObject, Referrable
Attribute Type Mult. Kind Note
debounce DiagEventDebounce 0..1 aggr This represents the actual debounce algorithm.
Algorithm Algorithm
debounce DiagnosticDebounce 0..1 attr This attribute defines how the event debounce algorithm
Behavior BehaviorEnum will behave, if a related enable condition is not fulfilled or
ControlDTCSetting of the related event is disabled.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
debounce Boolean 0..1 attr Switch to store the debounce counter value non-volatile
CounterStorage or not.
true: debounce counter value shall be stored non-volatile
false: debounce counter value is volatile
Table 6.45: DiagnosticDebounceAlgorithmProps

The details regarding the formalization of debouncing behavior are depicted in Figure
6.11.
In particular, DiagnosticCommonProps aggregates DiagnosticDebounceAl-
gorithmProps in the role debounceAlgorithmProps. The DiagnosticDe-
bounceAlgorithmProps itself does not actually represent the debouncing algorithm
but provides attributes relevant for the actual debouncing algorithm.

6.9.4 DiagnosticEvent to EnableConditionGroup Mapping

[TPS_DEXT_03015] EnableConditions have to be put into a DiagnosticEn-

ableConditionGroup dEnableConditions that are assigned to a Diagnos-
ticEvent have to be put into a DiagnosticEnableConditionGroup since only a
group of EnableConditions can be mapped to a DiagnosticEvent.c(RS_DEXT_-
00023, RS_DEXT_00026, RS_DEXT_00028)

210 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1361] Number of DiagnosticEventToEnableConditionGroupMap-

ping elements per DiagnosticEvent dThe mapping element DiagnosticEvent-
ToEnableConditionGroupMapping shall be created no more than once per Diag-
nosticEvent.
If several DiagnosticEventToEnableConditionGroupMapping elements refer-
ring to the same DiagnosticEvent are defined, then the Enable Condition
Group mapping shall be regarded as defective.c()
DiagnosticMapping
DiagnosticEventToEnableConditionGroupMapping

+diagnosticEvent 0..1 +enableConditionGroup 0..1

DiagnosticCommonElement DiagnosticConditionGroup
DiagnosticEvent DiagnosticEnableConditionGroup

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 6.17: DiagnosticEventToEnableConditionGroupMapping

Class DiagnosticEventToEnableConditionGroupMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines which EnableConditionGroup is applicable for a DiagnosticEvent.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref Reference to a DiagnosticEvent to which an Enable
ConditionGroup is assigned.
enableCondition DiagnosticEnable 0..1 ref Reference to an EnableConditionGroup assigned to a
Group ConditionGroup DiagnosticEvent.

Table 6.46: DiagnosticEventToEnableConditionGroupMapping

6.9.5 DiagnosticEvent to StorageConditionGroup Mapping

[TPS_DEXT_03016] StorageConditions have to be put into a Diagnostic-

StorageConditionGroup dStorageConditions that are assigned to a Diagnos-
ticEvent have to be put into a DiagnosticStorageConditionGroup since only
a group of StorageConditions can be mapped to a DiagnosticEvent.c(RS_-
DEXT_00023, RS_DEXT_00027, RS_DEXT_00029)

211 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1362] Number of DiagnosticEventToStorageConditionGroupMap-

ping elements per DiagnosticEvent dThe mapping element DiagnosticEvent-
ToStorageConditionGroupMapping shall be created no more than once or once
per DiagnosticEvent.
If several DiagnosticEventToStorageConditionGroupMapping elements re-
ferring to the same DiagnosticEvent are defined, then the Storage Condition
Group mapping shall be regarded as defective.c()
DiagnosticMapping
DiagnosticEventToStorageConditionGroupMapping

+diagnosticEvent 0..1 +storageConditionGroup 0..1

DiagnosticCommonElement DiagnosticConditionGroup
DiagnosticEvent DiagnosticStorageConditionGroup

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 6.18: DiagnosticEventToStorageConditionGroupMapping

[TPS_DEXT_03006] Values of the individual DiagnosticStorageConditions

dThe values of the individual DiagnosticStorageConditions need to be algorith-
mically evaluated in order to find out whether or not the storage of the Diagnos-
ticEvent is permitted.
The algorithm that is supposed to be implemented for this purpose is documented in
[SWS_Dem_00459].c(RS_DEXT_00027)
Class DiagnosticEventToStorageConditionGroupMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines which StorageConditionGroup is applicable for a DiagnosticEvent.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref Reference to a DiagnosticEvent to which a Storage
ConditionGroup is assigned.
storage DiagnosticStorage 0..1 ref Reference to a StorageConditionGroup assigned to a
ConditionGroup ConditionGroup DiagnosticEvent.

Table 6.47: DiagnosticEventToStorageConditionGroupMapping

212 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.9.6 DiagnosticEvent to Port Mapping

[TPS_DEXT_03007] Semantics of DiagnosticEventPortMapping dA Diagnos-

ticEventPortMapping defines which SwcServiceDependencys of a Atomic-
SwComponentType or BswServiceDependency of a BswModuleDescription
have to be connected to which DiagnosticEvent.
This is realized by defining a DiagnosticEventPortMapping referencing a Diag-
nosticEvent and (using instanceRef) an instance of SwcServiceDepen-
dency (or BswServiceDependency).c(RS_DEXT_00023, RS_DEXT_00052)
If such an instance is not yet available, an ordinary reference to SwcServiceDepen-
dency can be given alternatively (i.e. without specifying a certain instance).
ServiceDependency
BswServiceDependency

«atpIdentityContributor»

+ident 0..1

DiagnosticSwMapping IdentCaption
+bswServiceDependency
DiagnosticEventPortMapping BswServiceDependencyIdent

0..1

DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+diagnosticEvent + prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
0..1
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

AtpStructureElement
+swcServiceDependencyInSystem
Identifiable
«instanceRef» 0..1 ServiceDependency
SwcServiceDependency
+swcFlatServiceDependency

0..1

Figure 6.19: DiagnosticEventPortMapping

In this way, the ECU integrator is able to directly derive the actual mapping between
SWC (or BSW) service ports and the ports of the Service Components during ECU
configuration.
[constr_1435] Debouncing in the presence of a DiagnosticEventPortMapping
dIf a DiagnosticEventPortMapping exists and the enclosed DiagnosticEvent-
PortMapping.diagnosticEvent is also referenced by a DiagnosticEvent-
ToDebounceAlgorithmMapping then the concrete subclass of the respective
DiagnosticEventToDebounceAlgorithmMapping.debounceAlgorithm.de-
bounceAlgorithm shall be identical to the DiagnosticEventPortMapping.
swcServiceDependencyInSystem/swcFlatServiceDependency.service-
Needs.diagEventDebounceAlgorithm.

213 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

It is assumed that the target of reference DiagnosticEventPortMapping.swcSer-

viceDependencyInSystem resp. swcFlatServiceDependency aggregates a
DiagnosticEventNeeds.c()
Class DiagnosticEventPortMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines to which SWC service ports with DiagnosticEventNeeds the DiagnosticEvent is mapped.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
DiagnosticSwMapping, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
bswService BswService 0..1 ref Reference to a BswServiceDependency that links Service
Dependency DependencyIdent Needs to BswModuleEntries.
diagnosticEvent DiagnosticEvent 0..1 ref Reference to the DiagnosticEvent that is assigned to
SWC service ports with DiagnosticEventNeeds.
swcFlatService SwcService 0..1 ref Reference to a SwcServiceDependencyType that links
Dependency Dependency ServiceNeeds to SWC service ports.
swcService SwcService 0..1 iref Instance reference to a SwcServiceDependency that links
DependencyIn Dependency ServiceNeeds to SWC service ports.
System
InstanceRef implemented by:SwcServiceDependency
InSystemInstanceRef

Table 6.48: DiagnosticEventPortMapping

[constr_1843] Existence of reference DiagnosticEventPortMapping.diag-

nosticEvent dFor each DiagnosticEventPortMapping, the reference to Diag-
nosticEvent in the role diagnosticEvent shall exist at the time when the DEXT
is complete.c()
[constr_1762] Existence of references owned by DiagnosticEventPortMap-
ping dFor each DiagnosticEventPortMapping, only one of the references
• to BswServiceDependency in the role bswServiceDependency
• to SwcServiceDependency in the role swcFlatServiceDependency
• to SwcServiceDependency in the role swcServiceDependencyInSystem
shall exist at the time when the DEXT is complete.c()

6.9.7 DiagnosticOperationCycle to Port Mapping

[TPS_DEXT_03017] Semantics of DiagnosticOperationCyclePortMapping

dA DiagnosticOperationCyclePortMapping defines which SWC service port(s)
have to be connected to which DiagnosticOperationCycle.
This is realized by defining a DiagnosticOperationCyclePortMapping referenc-
ing a DiagnosticOperationCycle and an instance of SwcServiceDependency.c
(RS_DEXT_00052, RS_DEXT_00053)

214 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

If such an instance is not yet available, an ordinary reference to SwcServiceDepen-

dency can be given alternatively (i.e. without specifying a certain instance).
DiagnosticSwMapping DiagnosticCommonElement
DiagnosticOperationCyclePortMapping DiagnosticOperationCycle
+operationCycle + automaticEnd: Boolean [0..1]
+ cycleStatusStorage: Boolean [0..1]
0..1
+ type: DiagnosticOperationCycleTypeEnum [0..1]

+swcFlatServiceDependency AtpStructureElement
Identifiable
0..1
ServiceDependency
+swcServiceDependencyInSystem SwcServiceDependency
«instanceRef» 0..1

Figure 6.20: DiagnosticOperationCyclePortMapping

Class DiagnosticOperationCyclePortMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines to which SWC service ports with DiagnosticOperationCycleNeeds the DiagnosticOperationCycle
is mapped.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
DiagnosticSwMapping, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
operationCycle DiagnosticOperation 0..1 ref Reference to the DiagnosticOperationCycle that is
Cycle assigned to SWC service ports with DiagnosticOperation
CycleNeeds.
swcFlatService SwcService 0..1 ref Reference to a SwcServiceDependencyType that links
Dependency Dependency ServiceNeeds to SWC service ports.
swcService SwcService 0..1 iref Instance reference to a SwcServiceDependency that links
DependencyIn Dependency ServiceNeeds to SWC service ports.
System
InstanceRef implemented by:SwcServiceDependency
InSystemInstanceRef

Table 6.49: DiagnosticOperationCyclePortMapping

[constr_1844] Existence of reference DiagnosticOperationCyclePortMap-

ping.operationCycle dFor each DiagnosticOperationCyclePortMapping,
the reference to DiagnosticOperationCycle in the role operationCycle shall
exist at the time when the DEXT is complete.c()
[constr_1759] Existence of references owned by DiagnosticOperationCycle-
PortMapping dFor each DiagnosticOperationCyclePortMapping, only one of
the following references
• to SwcServiceDependency in the role swcFlatServiceDependency
• to SwcServiceDependency in the role swcServiceDependencyInSystem
shall exist at the time when the DEXT is complete.c()

215 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.9.8 DiagnosticEnableCondition to Port Mapping

[TPS_DEXT_03018] Semantics of DiagnosticEnableConditionPortMapping

dA DiagnosticEnableConditionPortMapping defines which SWC service
port(s) have to be connected to which DiagnosticEnableCondition. This is real-
ized by defining a DiagnosticEnableConditionPortMapping referencing a Di-
agnosticEnableCondition and an instance of SwcServiceDependency.c(RS_-
DEXT_00026, RS_DEXT_00052)
If such an instance is not yet available, an ordinary reference to SwcServiceDepen-
dency can be given alternatively (i.e. without specifying a certain instance).
DiagnosticSwMapping DiagnosticCondition
DiagnosticEnableConditionPortMapping +enableCondition DiagnosticEnableCondition

0..1

AtpStructureElement
Identifiable
ServiceDependency
+swcServiceDependencyInSystem SwcServiceDependency
«instanceRef» 0..1

+swcFlatServiceDependency

0..1

Figure 6.21: DiagnosticEnableConditionPortMapping

[constr_1752] Existence of references owned by DiagnosticEnableCondi-

tionPortMapping dFor each DiagnosticEnableConditionPortMapping, only
one of the following references
• to SwcServiceDependency in the role swcFlatServiceDependency
• to SwcServiceDependency in the role swcServiceDependencyInSystem
may exist at the time when the DEXT is complete.c()
Class DiagnosticEnableConditionPortMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines to which SWC service ports with DiagnosticEnableConditionNeeds the DiagnosticEnable
Condition is mapped.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
DiagnosticSwMapping, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
enableCondition DiagnosticEnable 0..1 ref Reference to the EnableCondition which is mapped to a
Condition SWC service port with DiagnosticEnableConditionNeeds.
5

216 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticEnableConditionPortMapping
swcFlatService SwcService 0..1 ref Reference to a SwcServiceDependencyType that links
Dependency Dependency ServiceNeeds to SWC service ports. This reference can
be used in early stages of the development in order to
identify the SwcServiceDependency without a full System
Context.
swcService SwcService 0..1 iref Instance reference to a SwcServiceDependency that links
DependencyIn Dependency ServiceNeeds to SWC service ports.
System
InstanceRef implemented by:SwcServiceDependency
InSystemInstanceRef

Table 6.50: DiagnosticEnableConditionPortMapping

[constr_1845] Existence of reference DiagnosticEnableConditionPortMap-

ping.enableCondition dFor each DiagnosticEnableConditionPortMap-
ping, the reference to DiagnosticEnableCondition in the role enableCondi-
tion shall exist at the time when the DEXT is complete.c()

6.9.9 DiagnosticStorageCondition to Port Mapping

[TPS_DEXT_03019] Semantics of DiagnosticStorageConditionPortMap-

ping dA DiagnosticStorageConditionPortMapping defines which SWC ser-
vice port(s) have to be connected to which DiagnosticStorageCondition. This
is realized by defining a DiagnosticStorageConditionPortMapping referencing
a DiagnosticStorageCondition and an instance of SwcServiceDependency.c
(RS_DEXT_00027, RS_DEXT_00052)
If such an instance is not yet available, an ordinary reference to SwcServiceDepen-
dency can be given alternatively (i.e. without specifying a certain instance).
DiagnosticSwMapping DiagnosticCondition
+diagnosticStorageCondition
DiagnosticStorageConditionPortMapping DiagnosticStorageCondition
0..1

AtpStructureElement
+swcFlatServiceDependency Identifiable
0..1 ServiceDependency
SwcServiceDependency

+swcServiceDependencyInSystem

«instanceRef» 0..1

Figure 6.22: DiagnosticStorageConditionPortMapping

[constr_1753] Existence of references owned by DiagnosticStorageCon-

ditionPortMapping dFor each DiagnosticStorageConditionPortMapping,
only one of the following references
• to SwcServiceDependency in the role swcFlatServiceDependency
• to SwcServiceDependency in the role swcServiceDependencyInSystem

217 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

may exist at the time when the DEXT is complete.c()

Class DiagnosticStorageConditionPortMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note Defines to which SWC service ports with DiagnosticStorageConditionNeeds the DiagnosticStorage
Condition is mapped.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
DiagnosticSwMapping, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnostic DiagnosticStorage 0..1 ref Reference to the StorageCondition which is mapped to a
Storage Condition SWC service port with DiagnosticStorageCondition
Condition Needs.
swcFlatService SwcService 0..1 ref Reference to a SwcServiceDependencyType that links
Dependency Dependency ServiceNeeds to SWC service ports.
swcService SwcService 0..1 iref Instance reference to a SwcServiceDependency that links
DependencyIn Dependency ServiceNeeds to SWC service ports.
System
InstanceRef implemented by:SwcServiceDependency
InSystemInstanceRef

Table 6.51: DiagnosticStorageConditionPortMapping

[constr_1846] Existence of reference DiagnosticStorageConditionPortMap-

ping.diagnosticStorageCondition dFor each DiagnosticStorageCondi-
tionPortMapping, the reference to DiagnosticStorageCondition in the role
diagnosticStorageCondition shall exist at the time when the DEXT is com-
plete.c()

6.9.10 Provided Data Mapping

[TPS_DEXT_03020] Semantics of DiagnosticDemProvidedDataMapping dThe

meta-class DiagnosticDemProvidedDataMapping does not seem to fulfill the con-
dition for representing a mapping class because it only has one reference to a Diag-
nosticDataElement in the role dataElement.
However, the specific nature of this mapping is that the second element (the Diag-
nosticDemProvidedDataMapping.dataProvider) that is supposed to take place
in the mapping cannot precisely be modeled as a single meta-class.
Therefore, there is no better way than to model the DiagnosticDemProvided-
DataMapping.dataProvider by a NameToken.
The semantics of this mapping is to further qualify the access to the Diagnos-
ticDataElement referenced in the role dataElement from within the Dem.c(RS_-
DEXT_00043, RS_DEXT_00052)
[TPS_DEXT_01142] Standardized values for DiagnosticDemProvided-
DataMapping.dataProvider dFor attribute DiagnosticDemProvidedDataMap-
ping.dataProvider, the following values are reserved by the AUTOSAR standard:
• DEM_AGINGCTR_DOWNCNT: map down-counting Dem-internal aging counter.

218 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• DEM_AGINGCTR_UPCNT: map up-counting Dem-internal aging counter.

• DEM_AGINGCTR_UPCNT_FIRST_ACTIVE: Map up-counting Dem-internal aging
counter, starting at 1 when aging starts.
• DEM_CLR_DIST: Distance since diagnostic trouble codes cleared.
• DEM_CLR_TIME: Time since diagnostic trouble codes cleared
• DEM_CURRENT_FDC: map Dem-internal fault detection counter.
• DEM_CYCLES_SINCE_FIRST_FAILED: map Dem-internal Operation Cycle
Counter - cycles since first failed.
• DEM_CYCLES_SINCE_LAST_FAILED: map Dem-internal Operation Cycle
Counter - cycles since last failed.
• DEM_DTC_PRIORITY: DTC priority statically assigned to this DTC.
• DEM_FAILED_CYCLES: map Dem-internal Operation Cycle Counter - failed cy-
cles.
• DEM_MAX_FDC_DURING_CURRENT_CYCLE: map Dem-internal DTC Fault Detec-
tion Counter maximum value during current operation cycle.
• DEM_MAX_FDC_SINCE_LAST_CLEAR: map Dem-internal DTC Fault Detection
Counter maximum value since last clear.
• DEM_MIL_DIST: Distance traveled While MIL is activated.
• DEM_MIL_TIME: Time run by the engine while MIL is activated.
• DEM_OCCCTR: map Dem-internal occurrence counter.
• DEM_OVFLIND: map Dem-internal overflow indication.
• DEM_SIGNIFICANCE: map (static) Dem-internal event significance.
• DEM_WARM_UPS: Number of warm-ups since diagnostic trouble codes cleared.
• DEM_J1939LAMP_STATUS: Current state of applicable lamp(s) for this DTC in
SAE J1939 DM31 format.
• DEM_EVENT_ASSOCIATED_IDENTIFICATION: static event identification value
associated to an event, see [TPS_DEXT_01151].
c(RS_DEXT_00043, RS_DEXT_00052)
Please note that, where applicable, AUTOSAR allows for the usage of values of the at-
tribute DiagnosticDemProvidedDataMapping.dataProvider other than the val-
ues standardized by [TPS_DEXT_01142].
In this case, however, proprietary values of the attribute DiagnosticDemProvided-
DataMapping.dataProvider shall be prefixed with a company-specific name frag-
ment in order to avoid collisions that could occur if or when the list of possible values
claimed by the AUTOSAR standard itself is extended.

219 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1782] Usage of internal data elements only for extended data records
dA DiagnosticDemProvidedDataMapping shall only refer to a Diagnostic-
DataElement that is aggregated by a DiagnosticExtendedDataRecord in the
role recordElement.dataElement.c()
Please note the existence of [constr_1756].
ARElement
DiagnosticCommonElement

DiagnosticMapping

DiagnosticDemProvidedDataMapping

+ dataProvider: NameToken [0..1]

+dataElement 0..1

Identifiable
DiagnosticDataElement

+ arraySizeSemantics: ArraySizeSemanticsEnum [0..1]

+ maxNumberOfElements: PositiveInteger [0..1]
+ scalingInfoSize: PositiveInteger [0..1]

Figure 6.23: Modeling of the DiagnosticDemProvidedDataMapping

Class DiagnosticDemProvidedDataMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This represents the ability to define the nature of a data access for a DiagnosticDataElement in the Dem.
Tags:atp.recommendedPackage=DiagnosticServiceMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataElement DiagnosticDataElement 0..1 ref This represents the DiagnosticDataElement for which the
access is further qualified by the DiagnosticDemProvided
DataMapping.
dataProvider NameToken 0..1 attr This represents the ability to further specify the access
within the Dem.
Table 6.52: DiagnosticDemProvidedDataMapping

[constr_1847] Existence of reference DiagnosticDemProvidedDataMapping.

dataElement dFor each DiagnosticDemProvidedDataMapping, the reference
to DiagnosticDataElement in the role dataElement shall exist at the time when
the DEXT is complete.c()

220 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.9.11 Master to Slave Event Mapping

AUTOSAR provides the ability to associate multiple diagnostic events in the way that
the reporting of one event (also known as the master event) from a diagnostic monitor
automatically triggers the reporting of one or more other diagnostic events (also known
as slave events) with the same test result.
Please note that the existence of the DiagnosticMasterToSlaveEventMapping
is primarily motivated by the need to store the result of event reporting simultaneously
in different fault memories within the affected ECU.
As a consequence, a model that references a given DiagnosticEvent as both mas-
terEvent and slaveEvent shall be considered broken, as further clarified in [con-
str_1590].
In the same spirit, a model where one specific DiagnosticEvent is referenced more
than once in the role masterEvent or the role slaveEvent is also considered bro-
ken.
[constr_1590] DiagnosticEvent referenced in the role masterEvent or
slaveEvent dAny given DiagnosticEvent shall at most once be referenced from
a DiagnosticMasterToSlaveEventMapping.c()
A diagnostic slave event shall never be reported directly by a diagnostic monitor. Slave
events are exclusively reported internally in the Dem. This important aspect is covered
by [constr_1591].
[constr_1591] DiagnosticEvent referenced as slaveEvent shall not be re-
ported by diagnostic monitor dA DiagnosticEvent referenced in the role Diag-
nosticMasterToSlaveEventMapping.slaveEvent shall not be referenced in the
role DiagnosticEventPortMapping.diagnosticEvent and vice versa.c()
DiagnosticCommonElement
DiagnosticMasterToSlaveEventMapping

+masterEvent 0..1 +slaveEvent 0..1

DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 6.24: Modeling of the DiagnosticMasterToSlaveEventMapping

221 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticMasterToSlaveEventMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note This meta-class provides the ability to map a master diagnostic event with a slave diagnostic event such
that reporting of the master event with a given value also reports the slave event with the same value
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
masterEvent DiagnosticEvent 0..1 ref This represents the master diagnostic event.
slaveEvent DiagnosticEvent 0..1 ref This represents the slave diagnostic event.

Table 6.53: DiagnosticMasterToSlaveEventMapping

6.9.12 Diagnostic Event to Security Event Mapping

AUTOSAR provides the ability to define so-called security events (formalized by

meta-class SecurityEventDefinition) to indicate a possible intrusion into an
AUTOSAR system.
The details are described in the specification of the TPS Security Extract Template [20].
[TPS_DEXT_01153]{DRAFT} Semantics of meta-class DiagnosticEventToSe-
curityEventMapping dThe occurrence of some security events need to be persisted
in the context of the Dem.
Technically, this mechanism boils down to a reporting of a diagnostic event in response
to the occurrence of a security event.
This approach is made possible by the existence of the DiagnosticEventToSecu-
rityEventMapping.c(RS_DEXT_00080)
DiagnosticMapping
DiagnosticEventToSecurityEventMapping

+securityEventProps 0..1 +diagnosticEvent 0..1

Identifiable DiagnosticCommonElement
SecurityEventContextProps DiagnosticEvent

+ defaultReportingMode: SecurityEventReportingModeEnum [0..1] + associatedEventIdentification: PositiveInteger [0..1]

+ persistentStorage: Boolean [0..1] + clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ sensorInstanceId: PositiveInteger [0..1] + eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ severity: PositiveInteger [0..1] + eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation» «atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

+securityEvent 0..1

IdsCommonElement
SecurityEventDefinition

+ id: PositiveInteger [0..1]
  

  
     

Figure 6.25: Modeling of the DiagnosticEventToSecurityEventMapping

222 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticEventToSecurityEventMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticMapping
Note This meta-class represents the ability to map a security event that is defined in the context of the Security
Extract to a diagnostic event defined on the context of the DiagnosticExtract.
Tags:
atp.Status=draft
atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref This reference identifies the applicable diagnostic event.
Tags:atp.Status=draft
securityEvent SecurityEventContext 0..1 ref This reference identifies the qualification of the applicable
Props Props security event
Tags:atp.Status=draft

Table 6.54: DiagnosticEventToSecurityEventMapping

[constr_10026]{DRAFT} Existence of reference in the role DiagnosticEvent-

ToSecurityEventMapping.diagnosticEvent dFor each DiagnosticEvent-
ToSecurityEventMapping, the reference to DiagnosticEvent in the role di-
agnosticEvent shall exist at the time when the DEXT is complete.c()
[constr_10027]{DRAFT} Existence of reference in the role DiagnosticEvent-
ToSecurityEventMapping.securityEventProps dFor each Diagnos-
ticEventToSecurityEventMapping, the reference to SecurityEventCon-
textProps in the role securityEventProps shall exist at the time when the
DEXT is complete.c()
It is important to understand that the mapping to a security event is not directed at
SecurityEventDefinition. This meta-class represents a high-level design object
that needs some more context in order to be considered in a specific project.
This additional context is provided by SecurityEventContextProps, which conse-
quentially becomes the target of the reference in the role DiagnosticEventToSe-
curityEventMapping.securityEventProps.
At first glance, it may seem that the definition of the DiagnosticEventToSecuri-
tyEventMapping and the existence of attribute SecurityEventContextProps.
persistentStorage create a certain level of redundancy. However, this is not really
the case.
This means in particular that the existence of SecurityEventContextProps.per-
sistentStorage can be used to indicate the need to persist the respective security
event.
The corresponding DiagnosticEventToSecurityEventMapping may be created
later in the workflow where the formal information which security event shall be per-
sisted represents an important input to the workflow.

223 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class SecurityEventContextProps
Package M2::AUTOSARTemplates::SecurityExtractTemplate
Note This meta-class specifies the SecurityEventDefinition to be mapped to an IdsmInstance and adds
mapping-dependent properties of this security event valid only for this specific mapping.
Tags:atp.Status=draft
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
contextData SecurityEventContext 0..1 aggr This aggregation represents the definition of optional
Data context data for security events.
Stereotypes: atpVariation
Tags:
atp.Status=draft
vh.latestBindingTime=systemDesignTime
default SecurityEventReporting 0..1 attr This attribute defines the default reporting mode for the
ReportingMode ModeEnum referenced security event.
persistent Boolean 0..1 attr This attribute controls whether qualified reportings of the
Storage referenced security event shall be stored persistently by
the mapped IdsmInstance or not.
securityEvent SecurityEventDefinition 0..1 ref This reference defines the security event that is mapped
and enriched by SecurityEventMappingProps with
mapping dependent properties.
Stereotypes: atpVariation
Tags:
atp.Status=draft
vh.latestBindingTime=systemDesignTime
sensorInstance PositiveInteger 0..1 attr This attribute defines the ID of the security sensor that
Id detects the referenced security event.
severity PositiveInteger 0..1 attr This attribute defines how critical/severe the referenced
security event is. Please note that currently, the severity
level meanings of specific integer values is not specified
by AUTOSAR but left to the party responsible for the IDS
system design (e.g. the OEM).

Table 6.55: SecurityEventContextProps

Class SecurityEventDefinition
Package M2::AUTOSARTemplates::SecurityExtractTemplate
Note This meta-class defines a security-related event as part of the intrusion detection system.
Tags:
atp.Status=draft
atp.recommendedPackage=SecurityEventDefinitions
Base ARElement, ARObject, CollectableElement, Identifiable, IdsCommonElement, MultilanguageReferrable,
PackageableElement, Referrable
Attribute Type Mult. Kind Note
eventSymbol SymbolProps 0..1 aggr This aggregation defines optionally an alternative Event
Name Name for the SecurityEventDefinition in case there is a
collision of shortNames.
Stereotypes: atpSplitable
Tags:
atp.Splitkey=eventSymbolName.shortName
atp.Status=draft
5

224 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class SecurityEventDefinition
id PositiveInteger 0..1 attr This attribute represents the numerical identification of
the defined security event. The identification shall be
unique within the scope of the IDS.
Tags:atp.Status=draft

Table 6.56: SecurityEventDefinition

6.10 DiagnosticOperationCycle
[TPS_DEXT_01087] Semantics of DiagnosticOperationCycle dDifferent types
of DiagnosticOperationCycles are supported and defined by the type attribute,
e.g. the time between ignition on and ignition off.c(RS_DEXT_00054)
ARElement
DiagnosticCommonElement

«enumeration»
DiagnosticOperationCycleTypeEnum
DiagnosticOperationCycle
ignition
obdDrivingCycle + automaticEnd: Boolean [0..1]
warmup + cycleStatusStorage: Boolean [0..1]
other + type: DiagnosticOperationCycleTypeEnum [0..1]

Figure 6.26: Modeling of DiagnosticOperationCycle

Class DiagnosticOperationCycle
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticOperationCycle
Note Definition of an operation cycle that is the base of the event qualifying and for Dem scheduling.
Tags:atp.recommendedPackage=DiagnosticOperationCycles
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
automaticEnd Boolean 0..1 attr If set to true the driving cycle shall automatically end at
either Dem_Shutdown() or Dem_Init().
This attribute is only relevant for the AUTOSAR adaptive
platform. It no longer has a meaning on the AUTOSAR
classic platform.
cycleStatus Boolean 0..1 attr Defines if the operation cycle state is available over the
Storage power cycle (stored non-volatile) or not.
• true: the operation cycle state is stored
non-volatile
5
5

225 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticOperationCycle
4
• false: the operation cycle state is only stored
volatile
This attribute is only relevant for the AUTOSAR adaptive
platform. It no longer has a meaning on the AUTOSAR
classic platform.
type DiagnosticOperation 0..1 attr Operation cycles types for the Dem.
CycleTypeEnum

Table 6.57: DiagnosticOperationCycle

Enumeration DiagnosticOperationCycleTypeEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticOperationCycle
Note Operation cycles types used to identify certain Operation cycles with a certain semantics.
Literal Description
ignition Ignition ON / OFF cycle
Tags:atp.EnumerationLiteralIndex=0
obdDrivingCycle OBD Driving cycle
Tags:atp.EnumerationLiteralIndex=1
other further operation cycle
Tags:atp.EnumerationLiteralIndex=2
warmup OBD Warm up cycle
Tags:atp.EnumerationLiteralIndex=5

Table 6.58: DiagnosticOperationCycleTypeEnum

6.11 DiagnosticAging
[TPS_DEXT_03021] Aging dIt is possible to remove a specific event from the event
memory, if its fault conditions are not fulfilled for a certain period of time. This process
is called as aging or unlearning.
This semantics is formalized by means of the meta-class DiagnosticAging.c(RS_-
DEXT_00055)

226 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

ARElement
DiagnosticCommonElement

DiagnosticAging

«atpVariation»
+ threshold: PositiveInteger [0..1]

«atpVariation,atpSplitable»
+agingCycle 0..1

DiagnosticOperationCycle

+ automaticEnd: Boolean [0..1]

+ cycleStatusStorage: Boolean [0..1]
+ type: DiagnosticOperationCycleTypeEnum [0..1]

Figure 6.27: Modeling of DiagnosticAging

Class DiagnosticAging
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticAging
Note Defines the aging algorithm.
Tags:atp.recommendedPackage=DiagnosticAgings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
agingCycle DiagnosticOperation 0..1 ref This represents the applicable aging cycle.
Cycle
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=agingCycle.diagnosticOperationCycle, aging
Cycle.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
threshold PositiveInteger 0..1 attr Number of aging cycles needed to unlearn/delete the
event.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.59: DiagnosticAging

[constr_1848] Existence of attribute DiagnosticAging.agingCycle dFor each

DiagnosticAging, attribute agingCycle shall exist at the time when the DEXT is
complete.c()
[constr_1849] Existence of attribute DiagnosticAging.threshold dFor each
DiagnosticAging, attribute threshold shall exist at the time when the DEXT is
complete.c()

6.12 DiagnosticIndicator
[TPS_DEXT_03022] Different kinds of DiagnosticIndicators dDifferent types
of Indicators can be defined with the DiagnosticIndicator element. For this, the
attribute DiagnosticIndicator.type shall be used.c(RS_DEXT_00056)

227 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

ARElement
DiagnosticCommonElement

«enumeration»
DiagnosticIndicatorTypeEnum

warning DiagnosticIndicator
malfunction
amberWarning «atpVariation»
protectLamp + type: DiagnosticIndicatorTypeEnum [0..1]
redStopLamp

Figure 6.28: Modeling of DiagnosticIndicator

Class DiagnosticIndicator
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticIndicator
Note Definition of an indicator.
Tags:atp.recommendedPackage=DiagnosticIndicators
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
type DiagnosticIndicatorType 0..1 attr Defines the type of the indicator.
Enum
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.60: DiagnosticIndicator

Enumeration DiagnosticIndicatorTypeEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticIndicator
Note Type of an indicator.
Literal Description
amberWarning Amber Warning Lamp
Tags:atp.EnumerationLiteralIndex=0
malfunction Malfunction Indicator Lamp
Tags:atp.EnumerationLiteralIndex=1
protectLamp Protect Lamp
Tags:atp.EnumerationLiteralIndex=2
redStopLamp Red Stop Lamp
Tags:atp.EnumerationLiteralIndex=3
warning Warning
Tags:atp.EnumerationLiteralIndex=4

Table 6.61: DiagnosticIndicatorTypeEnum

6.13 DiagnosticTestResult
The meta-class DiagnosticTestResult allows for a formal definition of a diagnostic
test result. The purpose of this meta-class is to support the reporting of the latest test
results back to a client. This is of special importance for the OBD service mode 0x06,
see chapter 5.6.5.

228 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

«enumeration»
DiagnosticTestResultUpdateEnum

always
steady

DiagnosticCommonElement
DiagnosticTestIdentifier
DiagnosticTestResult +testIdentifier
«atpVariation»
«atpVariation» 0..1
+ id: PositiveInteger
+ updateKind: DiagnosticTestResultUpdateEnum [0..1] + uasId: PositiveInteger

DiagnosticCommonElement

+monitoredIdentifier DiagnosticMeasurementIdentifier

0..1 «atpVariation»
+ obdMid: PositiveInteger

DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+diagnosticEvent + prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
«atpVariation»0..1 + recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

  
   
 

Figure 6.29: Modeling of DiagnosticTestResult

Class DiagnosticTestResult
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTestResult
Note This meta-class represents the ability to define diagnostic test results.
Tags:atp.recommendedPackage=DiagnosticTestResults
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref This attribute represents the diagnostic event that is
related to the diagnostic test result.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
monitored Diagnostic 0..1 ref This attribute represents the related diagnostic monitored
Identifier MeasurementIdentifier identifier.
testIdentifier DiagnosticTestIdentifier 0..1 aggr This attribute represents the applicable test identifier.
updateKind DiagnosticTestResult 0..1 attr This attribute controls the update behavior of the
UpdateEnum enclosing DiagnosticTestResult.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.62: DiagnosticTestResult

[constr_1850] Existence of aggregation DiagnosticTestResult.testIdenti-

fier dFor each DiagnosticTestResult, the aggregation of meta-class Diagnos-
ticTestIdentifier in the role testIdentifier shall exist at the time when the
DEXT is complete.c()

229 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1851] Existence of reference DiagnosticTestResult.monitoredI-

dentifier dFor each DiagnosticTestResult, the reference to meta-class Di-
agnosticTestIdentifier in the role monitoredIdentifier shall exist at the
time when the DEXT is complete.c()
Enumeration DiagnosticTestResultUpdateEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTestResult
Note This meta-class represents the ability to define the update behavior of a DiagnosticTestResult.
Literal Description
always Any DTR result reported by the monitor is used by the Dem.
Tags:atp.EnumerationLiteralIndex=0
steady The Dem accepts reported DTRs only when the configured debouncing mechanism is stable at the
FAIL or PASS limit.
Tags:atp.EnumerationLiteralIndex=1

Table 6.63: DiagnosticTestResultUpdateEnum

Class DiagnosticTestIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTestResult
Note This meta-class represents the ability to create a diagnostic test identifier.
Base ARObject
Attribute Type Mult. Kind Note
id PositiveInteger 1 attr This represents the numerical id associated with the
diagnostic test identifier.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
uasId PositiveInteger 1 attr This represents the unit and scaling Id of the diagnostic
test result.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.64: DiagnosticTestIdentifier

Class DiagnosticMeasurementIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTestResult
Note This meta-class represents the ability to describe a measurement identifier.
Tags:atp.recommendedPackage=DiagnosticMeasurementIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
obdMid PositiveInteger 1 attr This represents the numerical measurement Id
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime

Table 6.65: DiagnosticMeasurementIdentifier

230 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

6.14 OBD-related aspects of Dem Configuration

The support for OBD-related [18] modeling requires the addition of some pretty global
(i.e. on the level of an entire ECU) attribute that could be added to the EcuInstance.
However, this would not align with the idea of a decentralized configuration of the di-
agnostic stack where information is added at a point in time when an actual EcuIn-
stance is not yet available.
ARElement ARElement
DiagnosticCommonElement +element DiagnosticContributionSet

0..* «atpVariation,atpSplitable»

FibexElement
DiagnosticEcuInstanceProps
EcuInstance
+ecuInstance
+ obdSupport: DiagnosticObdSupportEnum [0..1]
+ comConfigurationGwTimeBase: TimeValue [0..1]
«atpSplitable» 0..* + comConfigurationRxTimeBase: TimeValue [0..1]
+ comConfigurationTxTimeBase: TimeValue [0..1]
+ comEnableMDTForCyclicTransmission: Boolean [0..1]
+ ethSwitchPortGroupDerivation: Boolean [0..1]
«enumeration» + pncPrepareSleepTimer: TimeValue [0..1]
DiagnosticObdSupportEnum + pncSynchronousWakeup: Boolean [0..1]
+ pnResetTime: TimeValue [0..1]
masterEcu + sleepModeSupported: Boolean
secondaryEcu + v2xSupported: V2xSupportEnum [0..1]
primaryEcu + wakeUpOverBusSupported: Boolean
noObdSupport

Figure 6.30: Modeling of DiagnosticEcuInstanceProps

Therefore, the attributes applying for the ECU-level are added to the meta-class Di-
agnosticEcuInstanceProps.
[TPS_DEXT_01122] Indication whether a EcuInstance supports OBD dThe at-
tribute DiagnosticEcuInstanceProps.obdSupport is taken to define whether a
given EcuInstance shall support OBD and in which way OBD shall be supported on
this Ecu.c(RS_DEXT_00058)
Class DiagnosticEcuInstanceProps
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticContribution
Note This meta-class represents the ability to model properties that are specific for a given EcuInstance but on
the other hand represent purely diagnostic-related information.
In the spirit of decentralized configuration it is therefore possible to specify the diagnostic-related
information related to a given EcuInstance even if the EcuInstance does not yet exist.
Tags:atp.recommendedPackage=DiagnosticEcuInstancePropss
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
ecuInstance EcuInstance * ref This represents the actual EcuInstance to which the
information conatined in the DiagnosticEcuInstance
contribute.
Stereotypes: atpSplitable
Tags:atp.Splitkey=ecuInstance
5

231 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticEcuInstanceProps
obdSupport DiagnosticObdSupport 0..1 attr This attribute is used to specify the role (if applicable) in
Enum which the DiagnosticEcuInstance supports OBD.

Table 6.66: DiagnosticEcuInstanceProps

[constr_1852] Existence of attribute DiagnosticEcuInstanceProps.obdSup-

port dFor each DiagnosticEcuInstanceProps, attribute obdSupport shall exist
at the time when the DEXT is complete.c()
Enumeration DiagnosticObdSupportEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::DiagnosticContribution
Note This meta-class represents the ability to model the roles in which a participation in OBD is foreseen.
At the moment, this applies exclusively to the Dem. However, future extension of the Dcm may
require this setting as well.
Literal Description
masterEcu This represent the role "master ECU".
Tags:atp.EnumerationLiteralIndex=0
noObdSupport This represents the ability to explicitly specify that no participation in OBD is foreseen.
Tags:atp.EnumerationLiteralIndex=1
primaryEcu This represents the role "primary ECU".
Tags:atp.EnumerationLiteralIndex=2
secondaryEcu This represents the role "secondary ECU".
Tags:atp.EnumerationLiteralIndex=3

Table 6.67: DiagnosticObdSupportEnum

Another OBD-related feature of the Dem is the support for the computation of the
In-Use-Monitor Performance Ratio (IUMPR). It is possible to define a so-called Di-
agnosticIumprGroup that encapsulates the computation of a group of Diagnos-
ticEvents.
The modeling of the DiagnosticIumprDenominatorGroup supports the configu-
ration of additional environmental conditions that shall be applied on the increment of
the IUMPR denominator.
From the modeling point of view, neither DiagnosticIumprGroup nor Diagnosti-
cIumprDenominatorGroup reference the associated DiagnosticEvent directly.
But since the DiagnosticIumpr referenced in the role iumpr in turn references
at most one DiagnosticEvent the resulting relation effectively boils down to Di-
agnosticIumprGroup and DiagnosticIumprDenominatorGroup being able to
precisely define the collection of affected DiagnosticEvents.
[TPS_DEXT_01148] Standardized values of DiagnosticIumprGroup.category
dThe semantics of meta-class DiagnosticIumprGroup is identified by means of the
value of attribute DiagnosticIumprGroup.category.
Standardized values of attribute DiagnosticIumprGroup.category are:

232 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• IUMPR_AFRI1
• IUMPR_AFRI2
• IUMPR_BOOSTPRS
• IUMPR_CAT1
• IUMPR_CAT2
• IUMPR_EGR
• IUMPR_EGSENSOR
• IUMPR_EVAP
• IUMPR_FLSYS
• IUMPR_NMHCCAT
• IUMPR_NOXADSORB
• IUMPR_NOXCAT
• IUMPR_OXS1
• IUMPR_OXS2
• IUMPR_PF1
• IUMPR_PF2
• IUMPR_PMFILTER
• IUMPR_PRIVATE
• IUMPR_SAIR
• IUMPR_SECOXS1
• IUMPR_SECOXS2
c(RS_DEXT_00078)
[TPS_DEXT_01149] Standardized values of DiagnosticIumprDenominator-
Group.category dThe semantics of meta-class DiagnosticIumprDenominator-
Group is identified by means of the value of attribute DiagnosticIumprDenomina-
torGroup.category.
Standardized values of attribute DiagnosticIumprDenominatorGroup.category
are:
• IUMPR_DENOMINATOR_500_MILES
• IUMPR_DENOMINATOR_COLDSTART
• IUMPR_DENOMINATOR_EVAP

233 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

• IUMPR_DENOMINATOR_NONE
• IUMPR_DENOMINATOR_PHYSICAL_API
c(RS_DEXT_00078)
DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

+event 0..1

DiagnosticCommonElement
DiagnosticIumpr

+iumpr 0..* +iumpr 0..*

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticIumprGroup DiagnosticIumprDenominatorGroup

«atpVariation,atpSplitable»
  
+iumprGroupIdentifier 0..1    

DiagnosticIumprGroupIdentifier

+ groupId: NameToken [0..1]

Figure 6.31: Modeling of IUMPR handling for diagnostic events

Class DiagnosticIumpr
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This meta-class represents he ability to model the in-us monitor performance ratio. The latter computes
to the number of times a fault could have been found divided by the number of times the vehicle
conditions have been properly fulfilled.
Tags:atp.recommendedPackage=DiagnosticIumprs
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
event DiagnosticEvent 0..1 ref This reference represents the DiagnosticEvent that
corresoponds to the IUMPR computation.

Table 6.68: DiagnosticIumpr

234 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticIumprGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This meta-class represents the ability to model a IUMPR groups.
Tags:atp.recommendedPackage=DiagnosticIumprGroups
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
iumpr DiagnosticIumpr * ref This reference collects DiagnosticIumpr to a Diagnostic
IumprGroup.
iumprGroup DiagnosticIumprGroup 0..1 aggr This aggregation allows for the variant modeling of the
Identifier Identifier groupIdentifier.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=iumprGroupIdentifier, iumprGroup
Identifier.variationPoint.shortLabel
vh.latestBindingTime=postBuild

Table 6.69: DiagnosticIumprGroup

[constr_1853] Existence of attribute DiagnosticIumprGroup.iumprGroupI-

dentifier dFor each DiagnosticIumprGroup, attribute iumprGroupIdenti-
fier shall exist at the time when the DEXT is complete.c()
Class DiagnosticIumprGroupIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This meta-class provides the ability to the define the group identifier for an IumprGroup.
Base ARObject
Attribute Type Mult. Kind Note
groupId NameToken 0..1 attr This attribute shall be taken to define an identifier for the
IUMPR group. Please note that the value of this identifier
is driven by regulations outside the scope of AUTOSAR
and can therefore not be limited to the set of characters
suitable for a shortName.
Table 6.70: DiagnosticIumprGroupIdentifier

[constr_1854] Existence of attribute DiagnosticIumprGroupIdentifier.

groupId dFor each DiagnosticIumprGroupIdentifier, attribute groupId shall
exist at the time when the DEXT is complete.c()
Class DiagnosticIumprDenominatorGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This meta-class represents the ability to model a IUMPR denominator groups.
Tags:atp.recommendedPackage=DiagnosticIumprDenominatorGroup
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
5

235 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticIumprDenominatorGroup
iumpr DiagnosticIumpr * ref This reference collects DiagnosticIumpr to a Diagnostic
IumprDenominatorGroup.

Table 6.71: DiagnosticIumprDenominatorGroup

6.14.1 Dem Configuration for OBD-II

The modeling of DTCs for the OBD-II use case is pretty similar to the modeling of DTCs
for the UDS use case. In other words, DiagnosticTroubleCodeObd references the
DiagnosticTroubleCodeProps in the same way that this meta-class is referenced
from DiagnosticTroubleCodeUds.
Please note that the meta-class DiagnosticTroubleCodeObd is only applicable for
the implementation of OBD-II.
[TPS_DEXT_01111] Legislative freeze frame for the OBD-II case dFor the imple-
mentation of OBD-II, the legislative freeze frame is obtained from running the OBD
Mode 0x02 service, modeled by means of meta-class DiagnosticPowertrain-
FreezeFrame.c()
[constr_1459] Existence of attributes of DiagnosticTroubleCodeProps dThe
following list of attributes of meta-class DiagnosticTroubleCodeProps are not re-
quired and therefore shall be ignored if the DiagnosticTroubleCodeProps is ref-
erenced in the role dtcProps from a DiagnosticTroubleCodeObd:
• freezeFrame
• snapshotRecordContent
• memoryDestination
• extendedDataRecord
• aging
c()

236 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticAbstractDataIdentifier
DiagnosticDataIdentifierSet DiagnosticDataIdentifier
+dataIdentifier
+ didSize: PositiveInteger [0..1]
0..* + representsVin: Boolean [0..1]
{ordered}
+snapshotRecordContent 0..1 +legislatedFreezeFrameContentWwhObd 0..1
EventObdReadinessGroup
«atpVariation» «atpVariation»
+ eventObdReadinessGroup: NameToken [0..1]

  
    +eventReadinessGroup 0..1

  
    
«atpVariation,atpSplitable»
 

DiagnosticCommonElement DiagnosticTroubleCode
DiagnosticTroubleCodeProps DiagnosticTroubleCodeObd
+dtcProps
+ environmentCaptureToReporting: EnvironmentCaptureToReportingEnum [0..1] «atpVariation»
+ immediateNvDataStorage: Boolean [0..1] 0..1 + considerPtoStatus: Boolean [0..1]
+ maxNumberFreezeFrameRecords: PositiveInteger [0..1] + obdDTCValue: PositiveInteger [0..1]
+ significance: DiagnosticSignificanceEnum [0..1]
«atpVariation»
+ priority: PositiveInteger [0..1]
DiagnosticCommonElement
DiagnosticAging
+aging
«atpVariation»
0..1 + threshold: PositiveInteger [0..1]

  
   
«atpVariation,atpSplitable» «atpVariation,atpSplitable» «atpVariation,atpSplitable»
 
+freezeFrame 0..* +extendedDataRecord 0..* +agingCycle 0..1

DiagnosticCommonElement DiagnosticCommonElement DiagnosticCommonElement

DiagnosticFreezeFrame DiagnosticExtendedDataRecord DiagnosticOperationCycle

+ customTrigger: String [0..1] + customTrigger: String [0..1] + automaticEnd: Boolean [0..1]

+ trigger: DiagnosticRecordTriggerEnum [0..1] + recordNumber: PositiveInteger [0..1] + cycleStatusStorage: Boolean [0..1]
+ update: Boolean [0..1] + trigger: DiagnosticRecordTriggerEnum [0..1] + type: DiagnosticOperationCycleTypeEnum [0..1]
«atpVariation» + update: Boolean [0..1]
+ recordNumber: PositiveInteger [0..1]

+memoryDestination 0..*

DiagnosticCommonElement
DiagnosticMemoryDestination

+ dtcStatusAvailabilityMask: PositiveInteger [0..1]

+ eventDisplacementStrategy: DiagnosticEventDisplacementStrategyEnum [0..1]
+ maxNumberOfEventEntries: PositiveInteger [0..1]
+ memoryEntryStorageTrigger: DiagnosticMemoryEntryStorageTriggerEnum [0..1]
+ typeOfFreezeFrameRecordNumeration: DiagnosticTypeOfFreezeFrameRecordNumerationEnum [0..1]

«enumeration» «enumeration» «enumeration»

DiagnosticRecordTriggerEnum DiagnosticWwhObdDtcClassEnum DiagnosticOperationCycleTypeEnum

confirmed demDtcWwhObdClassB1 ignition

fdcThreshold demDtcWwhObdClassA obdDrivingCycle
pending demDtcWwhObdClassB2 warmup
testFailed demDtcWwhObdClassC other
custom demDtcWwhObdClassNoInformation
testFailedThisOperationCycle

«enumeration» «enumeration»
DiagnosticSignificanceEnum EnvironmentCaptureToReportingEnum

fault captureSynchronousToReporting
occurence captureAsynchronousToReporting

Figure 6.32: Modeling of DTCs for OBD-II

6.14.2 Dem Configuration for WWH-OBD

[TPS_DEXT_01112] Definition of a diagnostic trouble code for the implementa-

tion of WWH-OBD dThe definition of a diagnostic trouble code for the implementation
of WWH-OBD implies the existence of a DiagnosticTroubleCodeUds where at-
tribute wwhObdDtcClass is set to any value other than demDtcWwhObdClassNoIn-
formation.c()

237 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01093] Definition of legislative freeze frame for WWWH-OBD dThe

legislative WWH-OBD freeze frame is identified by the reference DiagnosticTrou-
bleCodeProps.freezeFrame where attribute recordNumber is set to the value 0.
Optionally, the existence of a reference in the role DiagnosticTroubleCodeProps.
extendedDataRecord with attribute recordNumber set to the value 90 is sup-
ported.c()

238 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

7 Functional Inhibition

7.1 Introduction
Conceptually, the Fim [14] is closely related to the Dem since it handles the relation of
functionality (expressed via the so-called function identifier, or in short-form: Fid) and
linked DiagnosticEvents.

7.2 Alias Events

The close relation of Fim and Dem may have consequences in a distributed configura-
tion: it may not be possible to configure the Fim before the Dem is configured because
model elements (especially DiagnosticEvent) from the Dem configuration are re-
quired to model the Fim configuration.
This leads to the definition of DiagnosticFimAliasEvents that can be taken to
model the Fim configuration even of no Dem configuration exists or if configurations
with different Dem event names shall be considered for the final projects.
Please note, however, that the definition of DiagnosticFimAliasEvents is not
mandatory for the configuration of the Fim. It is possible to directly take the existence
of DiagnosticEvents into account and thereby bypass the definition of Diagnos-
ticFimAliasEvents.
Class DiagnosticFimAliasEvent
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class is used to represent a given event semantics. However, the name of the actual events
used in a specific project is sometimes not defined yet, not known or not in the responsibility of the
author. Therefore, the DiagnosticFimAliasEvent has a reference to the actual DiagnosticEvent and by this
the final connection is created.
Tags:atp.recommendedPackage=DiagnosticFimAliasEvents
Base ARElement, ARObject, CollectableElement, DiagnosticAbstractAliasEvent, DiagnosticCommonElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 7.1: DiagnosticFimAliasEvent

Class DiagnosticAbstractAliasEvent (abstract)

Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This meta-class represents an abstract base class for all diagnostic alias events.
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Subclasses DiagnosticFimAliasEvent, DiagnosticFimAliasEventGroup
5

239 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticAbstractAliasEvent (abstract)
Attribute Type Mult. Kind Note
– – – – –
Table 7.2: DiagnosticAbstractAliasEvent

7.3 Function Identifier

The support of the Fim as an extension of the Dem meta-model requires the modeling
of additional meta-classes to describe the various ways of possible mappings between
DiagnosticEvents and Fids (or, in terms of the meta-model, DiagnosticFunc-
tionIdentifier).
[TPS_DEXT_01121] Semantics of DiagnosticFunctionIdentifier dA Diag-
nosticFunctionIdentifier can be inhibited by different sources, i.e. in different
ways:
Event This corresponds to the DiagnosticEvent.
Fim Event Group This represents a group of events that is defined in the scope of
the Fim (within the Fim terminology, this is also known as a summary event).
In the meta-model, a Fim Event Group is represented by means of meta-class
DiagnosticFimEventGroup.
To emphasize the locality the corresponding meta-class has been named Diag-
nosticFimEventGroup. DiagnosticFimEventGroup is able to reference
0..* DiagnosticEvents in the role event.
This way, the membership of DiagnosticEvents in the hypothetical group of
events formed by the DiagnosticFimEventGroup is expressed.
c(RS_DEXT_00060)
Please note that DiagnosticEvent is discussed in chapter 6.2.
Class DiagnosticFunctionIdentifier
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents a diagnostic function identifier (a.k.a. FID).
Tags:atp.recommendedPackage=DiagnosticFunctionIdentifiers
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table 7.3: DiagnosticFunctionIdentifier

Finally all sources will refer to DiagnosticEvents.

240 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

7.4 Mapping between Inhibition Source and Diagnostic Event

The configuration of the Fim requires the clarification of the relation between a partic-
ular inhibition source (modeled as DiagnosticFunctionInhibitSource) and one
or many diagnostic events (modeled as DiagnosticEvent).
The easiest way to provide this information is the usage of the DiagnosticInhibit-
SourceEventMapping that is able to create an association between a Diagnostic-
FunctionInhibitSource on the one hand and either a DiagnosticEvent or a
DiagnosticFimEventGroup on the other hand.
This is only possible if the DiagnosticEvents referenced by the DiagnosticIn-
hibitSourceEventMapping already exist. This existence is subject to the devel-
opment workflow and may or may not apply. For more details, please refer to Figure
7.1.
Class DiagnosticInhibitSourceEventMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to map a DiagnosticFunctionInhibitSource directly to alternatively
one DiagnosticEvent or one DiagnosticFimSummaryEvent. This model element shall be used if the
approach via the alias events is not applicable, i.e. when diagnostic events defined by the Dem are
already available at the time the Fim configuration within the diagnostic extract is created.
Tags:atp.recommendedPackage=DiagnosticInhibitSourceEventMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref This represents the reference to the diagnostic event.
eventGroup DiagnosticFimEvent 0..1 ref This represents the reference to the event group
Group
inhibitionSource DiagnosticFunction 0..1 ref This represents the reference to the inhibition source.
InhibitSource

Table 7.4: DiagnosticInhibitSourceEventMapping

7.5 Alias Event Mapping

[TPS_DEXT_01095] Definition of “alias” diagnostic event for the creation of a
Fim configuration in the diagnostic extract dA pre-configuration of the Fim function
inhibition can be created on the basis of the following meta-classes:
DiagnosticFimAliasEventMapping in this case the definition of “alias” diagnostic
event corresponds to a single DiagnosticEvent
DiagnosticFimAliasEventGroupMapping in this case the definition of a group of
“alias” diagnostic events corresponds to a group of single DiagnosticEvents
c(RS_DEXT_00061, RS_DEXT_00062)

241 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class DiagnosticFimAliasEventMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticEvent
Note This meta-class represents the ability to model the mapping of a DiagnosticEvent to a DiagnosticAlias
Event. By this means the "preliminary" modeling by way of a DiagnosticAliasEvent is further
substantiated.
Tags:atp.recommendedPackage=DiagnosticFimEventMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
actualEvent DiagnosticEvent 0..1 ref This represents the reference to the actual diagnostic
event.
aliasEvent DiagnosticFimAlias 0..1 ref This represents the reference to the alias event.
Event
Table 7.5: DiagnosticFimAliasEventMapping

Class DiagnosticFimAliasEventGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to define an alias for a Fim summarized event. This alias can be
used in early phases of the configuration process until a further refinement is possible.
Tags:atp.recommendedPackage=DiagnosticFimAliasEventGroups
Base ARElement, ARObject, CollectableElement, DiagnosticAbstractAliasEvent, DiagnosticCommonElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
groupedAlias DiagnosticFimAlias * ref By means of this reference the grouping of Diagnostic
Event Event AliasEvents within the DiagnosticFimSummaryEvent can
be specified.

Table 7.6: DiagnosticFimAliasEventGroup

Class DiagnosticFimAliasEventGroupMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to map a DiagnosticFimEventGroup to a DiagnosticFimAliasEvent
Group. By this means the "preliminary" modeling by way of a DiagnosticFimAliasEventGroup is further
substantiated.
Tags:atp.recommendedPackage=DiagnosticFimAliasEventGroupMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
actualEvent DiagnosticFimEvent 0..1 ref This represents the reference to the actual summary
Group event.
aliasEvent DiagnosticFimAlias 0..1 ref This represents the reference to the alias summary event.
EventGroup

Table 7.7: DiagnosticFimAliasEventGroupMapping

Ultimately, the modeling approach for the Fim starts at the definition of the concept of
a function itself by means of the meta-class DiagnosticFunctionIdentifier.

242 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement
DiagnosticFunctionIdentifier

+functionIdentifier 0..1
«enumeration»
DiagnosticInhibitionMaskEnum
DiagnosticCommonElement
lastFailed
DiagnosticFunctionIdentifierInhibit
notTested
+ inhibitionMask: DiagnosticInhibitionMaskEnum [0..1] tested
testedAndFailed

+inhibitSource 0..*

Identifiable
DiagnosticFunctionInhibitSource

0..1
+event 0..1 +eventGroup 0..1 +inhibitionSource

DiagnosticAbstractAliasEvent DiagnosticAbstractAliasEvent
DiagnosticFimAliasEvent +groupedAliasEvent DiagnosticFimAliasEventGroup

0..*

+aliasEvent 0..1 +aliasEvent 0..1

DiagnosticMapping DiagnosticMapping DiagnosticMapping

DiagnosticFimAliasEventMapping DiagnosticFimAliasEventGroupMapping DiagnosticInhibitSourceEventMapping

+actualEvent 0..1 +eventGroup 0..1

DiagnosticCommonElement
DiagnosticFimEventGroup

+actualEvent 0..1 +event 0..* +diagnosticEvent 0..1

DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 7.1: Big Picture of Fim diagnostics configuration

Class DiagnosticFunctionIdentifierInhibit
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to define the inhibition of a specific function identifier within the Fim
configuration.
Tags:atp.recommendedPackage=DiagnosticFunctionIdentifierInhibits
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
function DiagnosticFunction 0..1 ref This represents the corresponding function identifier.
Identifier Identifier
5

243 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticFunctionIdentifierInhibit
inhibitionMask DiagnosticInhibition 0..1 attr This represents the value of the inhibition mask behavior.
MaskEnum
inhibitSource DiagnosticFunction * aggr This represents a collection of DiagnosticFunctionInhibit
InhibitSource Source that contribute to the configuration of the
enclosing DiagnosticFunctionIdentiferInhibit.

Table 7.8: DiagnosticFunctionIdentifierInhibit

[constr_1855] Existence of attribute DiagnosticFunctionIdentifierIn-

hibit.inhibitionMask dFor each DiagnosticFunctionIdentifierInhibit,
attribute inhibitionMask shall exist at the time when the DEXT is complete.c()
Class DiagnosticFunctionInhibitSource
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to define an inhibition source in the context of the Fim configuration.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
event DiagnosticFimAlias 0..1 ref This represents the alias event appllicable for the
Event referencing inhibition source.
eventGroup DiagnosticFimAlias 0..1 ref This represents the event group applicable for the
EventGroup referencing inhibition source.

Table 7.9: DiagnosticFunctionInhibitSource

Enumeration DiagnosticInhibitionMaskEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to define different kinds of inhibition mask behavior.
Literal Description
lastFailed This represents the inhibition mask behavior "last failed".
Tags:atp.EnumerationLiteralIndex=0
notTested This represents the inhibition mask behavior "not tested".
Tags:atp.EnumerationLiteralIndex=1
tested This represents the inhibition mask behavior "tested".
Tags:atp.EnumerationLiteralIndex=3
testedAndFailed This represents the inhibition mask behavior "tested and failed".
Tags:atp.EnumerationLiteralIndex=2

Table 7.10: DiagnosticInhibitionMaskEnum

[TPS_DEXT_01096] Semantics of DiagnosticFunctionInhibitSource dThe

function inhibition itself is modeled by means of a different meta-class named Di-
agnosticFunctionIdentifierInhibit. This meta-class, in turn, references the
DiagnosticFunctionIdentifier and it also aggregates 0..* instances of a further
meta-class named DiagnosticFunctionInhibitSource.
DiagnosticFunctionInhibitSource inherits from Identifiable in order to be
able to utilize attributes like desc, adminData, and introduction for the purpose of
textually explaining the reason for defining a certain inhibit source.c(RS_DEXT_00060)

244 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01097] Standardized value of StructuredReq.category for the

modeling of DiagnosticFunctionInhibitSource dIf DiagnosticFunction-
InhibitSource.introduction.structuredReq is used to document the reason
for a specific function inhibition then DiagnosticFunctionInhibitSource.in-
troduction.structuredReq.category shall be set to the value InhibitRea-
son.c(RS_DEXT_00060)
[constr_1453] References from DiagnosticFunctionInhibitSource dEach
DiagnosticFunctionInhibitSource may either reference one of the following
meta-classes in their respective roles:
• DiagnosticFimAliasEventMapping in the role event
• DiagnosticFimAliasEventGroupMapping in the role eventGroup
c()
Class DiagnosticFimEventGroup
Package M2::AUTOSARTemplates::DiagnosticExtract::Fim
Note This meta-class represents the ability to model a Fim event group, also known as a summary event in
Fim terminology. This represents a group of single diagnostic events.
Tags:atp.recommendedPackage=DiagnosticFimEventGroups
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
event DiagnosticEvent * ref This reference represents the way of grouping diagnostic
events into a summary event in the context of the Fim.

Table 7.11: DiagnosticFimEventGroup

[TPS_DEXT_01098] Semantics of attribute DiagnosticFunctionInhibit-

Source.event dIf the reference DiagnosticFunctionInhibitSource.event ex-
ists this means the inhibition applies for a single DiagnosticEventc(RS_DEXT_-
00060, RS_DEXT_00061)
[TPS_DEXT_01099] Semantics of attribute DiagnosticFunctionInhibit-
Source.eventGroup dIf the reference DiagnosticFunctionInhibitSource.
eventGroup exists this means that the inhibition effectively applies for a group of
DiagnosticEvents where the actual grouping is defined in the scope of the Fim.c
(RS_DEXT_00060, RS_DEXT_00061)
[TPS_DEXT_01100] Consequence of the existence of DiagnosticFimAliasEv-
entMapping dThe references from meta-class DiagnosticFimAliasEventMap-
ping in the roles actualEvent and aliasEvent do not necessarily have to exist at
the same time. The following rules apply:
Only actualEvent exists: In this case there is no DiagnosticFimAliasEvent
available and the actual DiagnosticEvent can directly be taken for creating
the Fim configuration.

245 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Only aliasEvent exists: In this case the configuration is considered incomplete and
only defines the intended semantics from the point of view of a pre-configuration
of the Fim.
Both actualEvent and aliasEvent exist: In this case it is obvious that the con-
figuration has undergone a pre-configuration step in which a DiagnosticFi-
mAliasEvent has been used. However, since the DiagnosticEvent in the
role actualEvent exists the Diagnostic Extract is considered complete with re-
spect to this aspect of the Fim configuration.
c(RS_DEXT_00060, RS_DEXT_00061)
DiagnosticCommonElement
DiagnosticFunctionIdentifier

+functionIdentifier 0..1

DiagnosticCommonElement
DiagnosticFunctionIdentifierInhibit

+ inhibitionMask: DiagnosticInhibitionMaskEnum [0..1]

+inhibitSource 0..* «enumeration»

DiagnosticInhibitionMaskEnum
Identifiable
lastFailed
DiagnosticFunctionInhibitSource
notTested
tested
testedAndFailed

DiagnosticMapping
DiagnosticFimAliasEventMapping

+event 0..1 +aliasEvent 0..1 +actualEvent 0..1

DiagnosticAbstractAliasEvent DiagnosticCommonElement
DiagnosticFimAliasEvent DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 7.2: Inhibition of events in Fim for diagnostics configuration

[TPS_DEXT_01101] Consequence of the existence of DiagnosticFimAliasEv-

entGroupMapping dThe references from meta-class DiagnosticFimAliasEv-
entGroupMapping in the roles actualEvent and aliasEvent do not necessarily
have to exist at the same time. The following rules apply:
Only actualEvent exists: In this case there is no DiagnosticFimAliasEvent-
Group available and the actual DiagnosticFimEventGroup can directly be
taken for creating the Fim configuration.

246 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Only aliasEvent exists: In this case the configuration is considered incomplete and
only defines the intended semantics from the point of view of a pre-configuration
of the Fim.
Both actualEvent and aliasEvent exist: In this case it is obvious that the con-
figuration has undergone a pre-configuration step in which a Diagnostic-
FimAliasEventGroup has been used. However, since the Diagnostic-
FimEventGroup in the role actualEvent exists the Diagnostic Extract is con-
sidered complete with respect to this aspect of the Fim configuration.
c(RS_DEXT_00060, RS_DEXT_00061)
«enumeration»
DiagnosticCommonElement DiagnosticInhibitionMaskEnum
DiagnosticFunctionIdentifier lastFailed
notTested
tested
testedAndFailed
+functionIdentifier 0..1

DiagnosticCommonElement Identifiable
DiagnosticFunctionIdentifierInhibit +inhibitSource DiagnosticFunctionInhibitSource

+ inhibitionMask: DiagnosticInhibitionMaskEnum [0..1] 0..*

+eventGroup 0..1

DiagnosticMapping DiagnosticAbstractAliasEvent
+aliasEvent
DiagnosticFimAliasEventGroupMapping DiagnosticFimAliasEventGroup
0..1

+actualEvent 0..1

DiagnosticCommonElement DiagnosticCommonElement
DiagnosticFimEventGroup +event DiagnosticEvent

0..* + associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

Figure 7.3: Inhibition of event groups in Fim for diagnostics configuration

7.6 Mapping of Function Identifiers to the corresponding Monitors

Beside the ability to model a function inhibition itself, it is equally important that this
inhibition can be connected to the applicable monitors.
This relation can be expressed by means of the DiagnosticFimFunctionMapping.
The details are sketched in Figure 7.4.
[TPS_DEXT_01102] Semantics of DiagnosticFimFunctionMapping dThe meta-
class DiagnosticFimFunctionMapping represents the ability to map a Diagnos-
ticFunctionIdentifier to a SwcServiceDependency that addresses function
inhibition.c(RS_DEXT_00063)

247 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[constr_1454] DiagnosticFimFunctionMapping shall only reference a Swc-

ServiceDependency that aggregates FunctionInhibitionNeeds dA Diag-
nosticFimFunctionMapping shall only reference a SwcServiceDependency
that aggregates FunctionInhibitionNeeds in the role serviceNeeds.c()
The modeling of this mapping is closely related to the existing modeling of mappings
that involve SwcServiceDependency in the context of the diagnostic extract.
ARElement
DiagnosticCommonElement

DiagnosticMapping

DiagnosticSwMapping

DiagnosticFunctionIdentifier DiagnosticFimFunctionMapping
+mappedFunction

0..1

AtpStructureElement +mappedSwcServiceDependency
Identifiable
0..1 «instanceRef»
ServiceDependency
SwcServiceDependency +mappedFlatSwcServiceDependency

0..1

IdentCaption
BswServiceDependencyIdent +mappedBswServiceDependency

0..1

+ident 0..1
«atpIdentityContributor»

ServiceDependency
BswServiceDependency

Figure 7.4: Mapping of function identifiers to the corresponding monitors

Class DiagnosticFimFunctionMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::ServiceMapping
Note This meta-class represents the ability to define a mapping between a function identifier (FID) and the
corresponding SwcServiceDependency in the application software resp. basic software.
Tags:atp.recommendedPackage=DiagnosticFimFunctionMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
DiagnosticSwMapping, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
5

248 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticFimFunctionMapping
Attribute Type Mult. Kind Note
mappedBsw BswService 0..1 ref This is supposed to represent a reference to a Bsw
Service DependencyIdent ServiceDependency. the latter is not derived from
Dependency Referrable and therefore this detour needs to be
implemented to still let BswServiceDependency become
the target of a reference.
mappedFlatSwc SwcService 0..1 ref This represents the ability to refer to an AtomicSw
Service Dependency ComponentType that is available without the definition of
Dependency how it will be embedded into the component hierarchy.
mapped DiagnosticFunction 0..1 ref This represents the mapped FID.
Function Identifier
mappedSwc SwcService 0..1 iref This represents the ability to point into the component
Service Dependency hierarchy (under possible consideration of the root
Dependency SoftwareComposition).
InstanceRef implemented by:SwcServiceDependency
InSystemInstanceRef

Table 7.12: DiagnosticFimFunctionMapping

Class FunctionInhibitionNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the abstract needs on the configuration of the Function Inhibition Manager for one Function
Identifier (FID). This class currently contains no attributes. Its name can be regarded as a symbol
identifying the FID from the viewpoint of the component or module which owns this class.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable, ServiceNeeds
Attribute Type Mult. Kind Note
– – – – –
Table 7.13: FunctionInhibitionNeeds

249 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

8 Diagnostics on J1939

8.1 Introduction
Diagnostics on J1939 is to some extent similar to the “rest of the world”. In other words,
J1939 uses a Dcm and a Dem similarly as other communication networks do.
On the other hand, there are significant differences between J1939 and the “rest of
the world” that justify the creation of a separate chapter that focuses entirely on how a
diagnostic extract for J1939 shall look like.
That said, a support for Dcm-related model elements for J1939 is mainly happening
in the domain of the AUTOSAR System Template [6] rather than in the scope of this
document.
The actual configuration of services supported by the J1939Dcm is done by assigning
DMx messages in the System Description.
The mapping of the J1939DcmIPdus to the diagnostic services of J1939 Dcm happens
during derivation to EcuC.
In the following sections this document focuses on explaining the modeling with respect
to the Dem.

8.2 Suspect Parameter Number

In the J1939 terminology, a Suspect Parameter Number represents a signal identi-
fier. The numerical value of this signal identifier is stored in the attribute Diagnos-
ticJ1939Spn.spn.
Conceptually, the Suspect Parameter Number binds to the SystemSignal, i.e. by
attaching a Suspect Parameter Number to a SystemSignal a J1939 signal is created.
At the first sight, it may seem like a good idea to attach the spn attribute to the Sys-
temSignal itself. However, this would place a very specific J1939-related model se-
mantics in a very prominent place.
This just doesn’t seem right and thanks to the existence of meta-class Diagnos-
ticJ1939SpnMapping it is possible to “inject” the J1939 signal identifier into a Sys-
temSignal without actually touching the SystemSignal.
[TPS_DEXT_01103] Semantics of meta-class DiagnosticJ1939SpnMapping
dThe DiagnosticJ1939SpnMapping has the ability to associate a Diagnos-
ticJ1939Spn with a SystemSignal. By this means it is possible to express that
a given SystemSignal is taken to transport a J1939 Suspect Parameter Number.c
(RS_DEXT_00064)

250 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Please note that the modeling of the DiagnosticJ1939SpnMapping also implies

that the same SPN can be sent by different J1939NmNodes. This ability is positively
supported.
Class DiagnosticJ1939Spn
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::J1939
Note This meta-class represents the ability to model a J1939 Suspect Parameter Number (SPN).
Tags:atp.recommendedPackage=DiagnosticJ1939Spns
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
spn PositiveInteger 0..1 attr This attribute represents the concrete numerical
identification for the enclosing SPN.

Table 8.1: DiagnosticJ1939Spn

[constr_1856] Existence of attribute DiagnosticJ1939Spn.spn dFor each Diag-

nosticJ1939Spn, attribute spn shall exist at the time when the DEXT is complete.c
()

8.3 J1939Dcm-related Modeling

The modeling of the J1939Dcm-related configuration within the Diagnostic Extract ex-
tends to the definition of a new attribute of meta-class J1939Cluster. The latter
provides an attribute named networkId. For more information, please refer to [6].
The actual configuration of the services supported by J1939Dcm is done by assigning
DMx messages in the System Description.

8.4 Dem-related Modeling

The modeling of Dem-related support for J1939 is centered around the Diagnos-
ticJ1939Node. This meta-class literally acts as a sort of “inverted”1 hub for all the
Dem-related model elements. The DiagnosticJ1939Node represents a specific
function, or in terms of the J1939 terminology, a Controller Application.
This aspect is stressed in Figure 8.1.
Since, according to the J1939 concept, each controller application represents an inde-
pendent entity in terms of network management, the following constraint applies:
[constr_1455] Relation of DiagnosticJ1939Node to J1939NmNode dEach
J1939NmNode shall only be referenced in the role nmNode by a single Diagnos-
ticJ1939Node.c()
1
Meaning: several meta-classes are referencing the DiagnosticJ1939Node.

251 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticCommonElement DiagnosticMapping
DiagnosticJ1939Spn +spn DiagnosticJ1939SpnMapping

+ spn: PositiveInteger [0..1] 0..1

+spn 0..1 +spn 0..* +spn 0..*

{ordered} {ordered}

    

+systemSignal 0..1

DiagnosticCommonElement DiagnosticCommonElement ARElement

DiagnosticJ1939FreezeFrame DiagnosticJ1939ExpandedFreezeFrame SystemSignal

+ dynamicLength: Boolean

+node 0..1 +node 0..1 0..* +sendingNode

DiagnosticCommonElement
DiagnosticJ1939Node

+node 0..1

+nmNode 0..1

DiagnosticTroubleCode «enumeration» NmNode

DiagnosticTroubleCodeJ1939 DiagnosticTroubleCodeJ1939DtcKindEnum J1939NmNode

+ fmi: PositiveInteger [0..1] standard

+ kind: DiagnosticTroubleCodeJ1939DtcKindEnum [0..1] serviceOnly

Figure 8.1: Big Picture of J1939 diagnostics configuration

J1939 supports the capturing of information similar to the definition of Diagnos-

ticFreezeFrame, as explained in chapter 6.5. In the case of J1939, however, two
different kinds of freeze frames can be defined:
[TPS_DEXT_01104] Difference between DiagnosticJ1939FreezeFrame and
DiagnosticJ1939ExpandedFreezeFrame dA DiagnosticJ1939FreezeFrame
is transmitted via J1939 DM04 while a DiagnosticJ1939ExpandedFreezeFrame
is transmitted via J1939 DM24/DM25.c(RS_DEXT_00065)
[TPS_DEXT_01105] Relation of DiagnosticJ1939Spn to Diagnos-
ticJ1939FreezeFrame and DiagnosticJ1939ExpandedFreezeFrame dIt
is possible that a given DiagnosticJ1939Spn is referenced by both a Diagnos-
ticJ1939FreezeFrame and a DiagnosticJ1939ExpandedFreezeFrame.
In other words, the Suspect Parameter Number can be part of a normal freeze frame
and, at the same time, an expanded freeze frame.c(RS_DEXT_00065)
Class DiagnosticJ1939FreezeFrame
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::J1939
Note This meta-class represents the ability to model a J1939 Freeze Frame.
Tags:atp.recommendedPackage=DiagnosticJ1939FreezeFrames
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
node DiagnosticJ1939Node 0..1 ref This represents the DiagnosticJ1939Node to which the
J1939 freeze frame is associated.
5

252 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticJ1939FreezeFrame
spn (ordered) DiagnosticJ1939Spn * ref This represents the collection of SPNs that make the
J1939 Freeze Frame.

Table 8.2: DiagnosticJ1939FreezeFrame

Class DiagnosticJ1939ExpandedFreezeFrame
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::J1939
Note This meta-class represents the ability to model an expanded J1939 Freeze Frame.
Tags:atp.recommendedPackage=DiagnosticJ1939ExpandedFreezeFrames
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
node DiagnosticJ1939Node 0..1 ref This represents the DiagnosticJ1939Node to which the
J1939 expanded freeze frame is associated.
spn (ordered) DiagnosticJ1939Spn * ref This represents the collection of SPNs that make the
expanded J1939 Freeze Frame.

Table 8.3: DiagnosticJ1939ExpandedFreezeFrame

Enumeration DiagnosticTroubleCodeJ1939DtcKindEnum
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This meta-class represents the ability to further specify a J1939 DTC in terms of its semantics.
Literal Description
serviceOnly this represents a DTC that is only relevant for service in a garage, reported by e.g. DM53.
Tags:atp.EnumerationLiteralIndex=0
standard This represents a non-specific DTC reported by e.g. DM1.
Tags:atp.EnumerationLiteralIndex=1

Table 8.4: DiagnosticTroubleCodeJ1939DtcKindEnum

[TPS_DEXT_01106] Relation of Controller Application to SPN dIt is technically pos-

sible that several Controller Applications, formally represented by the meta-class Di-
agnosticJ1939Node, can send the same Suspect Parameter Number.
In response to this specific characteristic of the J1939 approach, the multiplicity of
the reference DiagnosticJ1939SpnMapping.sendingNode has been set to 0..*.c
(RS_DEXT_00064)
Class DiagnosticJ1939SpnMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::J1939
Note This meta-class represents the ability to define a mapping between an SPN and a SystemSignal. The
existence of a mapping means that neither the SPN nor the SystemSignal need to be updated if the
relation between the two changes.
Tags:atp.recommendedPackage=DiagnosticJ1939SpnMappings
5

253 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticJ1939SpnMapping
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
sendingNode DiagnosticJ1939Node * ref This additional reference has a supporting role in that it
identifies all sending nodes of a given SPN. It is positively
possible thata given SPN is sent by more than one node.
Even tough the reference targets the Diagnostic
J1939Node the semantics of the reference is bound to
the J1939NmNode that is in turn referenced by the
DiagnosticJ1939Node.
spn DiagnosticJ1939Spn 0..1 ref This reference goes to the SPN that shall be associated
with a SystemSignal.
systemSignal SystemSignal 0..1 ref This reference goes to the SystemSignal that shall be
associated with an SPN.

Table 8.5: DiagnosticJ1939SpnMapping

Class DiagnosticJ1939Node
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::J1939
Note This meta-class represents the diagnostic configuration of a J1939 Nm node, which in turn represents a
"virtual Ecu" on the J1939 communication bus.
Tags:atp.recommendedPackage=DiagnosticJ1939Nodes
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
nmNode J1939NmNode 0..1 ref This represents the reference to the "virtual Ecu" to which
the enclosing DiagnosticJ1939Node is associated.

Table 8.6: DiagnosticJ1939Node

[constr_1456] Valid interval for attribute DiagnosticTroubleCodeJ1939.fmi

dThe value of the attribute DiagnosticTroubleCodeJ1939.fmi shall be in the in-
terval 0..31.c()
Please note that the rationale for the existence of [constr_1456] as well as the mean-
ing of the individual values of the attribute fmi can be found in the respective SAE
J1939 [22] specification.
Class DiagnosticTroubleCodeJ1939
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::DiagnosticTroubleCode
Note This meta-class represents the ability to model specific trouble-code related properties for J1939.
Tags:atp.recommendedPackage=DiagnosticTroubleCodes
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticTroubleCode,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dtcProps DiagnosticTroubleCode 0..1 ref Defined properties associated with the J1939 DTC.
Props
5

254 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticTroubleCodeJ1939
fmi PositiveInteger 0..1 attr This attribute represents the behavior of the Failure Mode
Indicator.
kind DiagnosticTroubleCode 0..1 attr This attribute further specifies the DTC in terms of its
J1939DtcKindEnum semantics.
node DiagnosticJ1939Node 0..1 ref This represents the related DiagnosticJ1939Node.
spn DiagnosticJ1939Spn 0..1 ref This represents the releated SPN.

Table 8.7: DiagnosticTroubleCodeJ1939

[constr_1780] Existence of attribute DiagnosticTroubleCodeJ1939.fmi dFor

each DiagnosticTroubleCodeJ1939, attribute fmi shall exist at the time when
the DEXT is complete.c()
[constr_1781] Existence of attribute DiagnosticTroubleCodeJ1939.spn dFor
each DiagnosticTroubleCodeJ1939, attribute spn shall exist at the time when
the DEXT is complete.c()
[TPS_DEXT_01107] Definition of service-only DTC dIt is possible to specify whether
given DTCs on J1939 are only relevant for a service session in a garage or workshop.
The common property of service-only DTCs is that they shall be located in a memory
section that is exclusively used by service-only DTCs.c(RS_DEXT_00067)
The statement made by [TPS_DEXT_01107] needs to be secured by two constraints:
[constr_1457] Service-only DTCs shall refer to a common memory section dAll
DiagnosticTroubleCodeJ1939 with attribute kind set to the value serviceOnly
that reference the same DiagnosticJ1939Node shall also reference the same Di-
agnosticTroubleCodeProps.memoryDestination.c()
[constr_1458] Reference to DiagnosticMemoryDestination dA Diagnos-
ticMemoryDestination that is referenced by a DiagnosticTroubleCodeJ1939.
dtcProps.memoryDestination where the value of attribute DiagnosticTrou-
bleCodeJ1939.kind is set to serviceOnly shall not be referenced by any other
DiagnosticTroubleCodeJ1939 where attribute kind is set to any other value than
serviceOnly.c()

8.5 Mapping between Software-Components and Controller Appli-

cations
Another aspect of the modeling of J1939 diagnostics is that a mapping between the
DiagnosticJ1939Node (which formally represents a Controller Application) and the
AUTOSAR way of specifying a “function” (by means of the meta-class SwComponent-
Prototype) is required.
This leads to the definition of the DiagnosticJ1939SwMapping.

255 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

[TPS_DEXT_01108] Purpose of the DiagnosticJ1939SwMapping dThe purpose

of the DiagnosticJ1939SwMapping is to associate a SwComponentPrototype
with a DiagnosticJ1939Node. By this means a concrete functionality is mapped to
the abstract J1939 Controller Application.c(RS_DEXT_00066)
Please note that the basis for this mapping is the existence of a CompositionSwCom-
ponentType rather than a System. The mapping can therefore (and this is the main
motivation for this kind of modeling) be done independently of the deployment to a
concrete project.
AtpInstanceRef
ComponentInCompositionInstanceRef

+swComponentPrototype 0..1

0..*
0..1 {ordered,
+targetComponent {redefines atpTarget} +contextComponent subsets atpContextElement}
AtpPrototype DiagnosticCommonElement
SwComponentPrototype +swComponentPrototype DiagnosticJ1939SwMapping

0..1 «instanceRef»

DiagnosticCommonElement
DiagnosticJ1939Node +node

0..1

Figure 8.2: Mapping between Software-Components and Controller Applications

Class DiagnosticJ1939SwMapping
Package M2::AUTOSARTemplates::DiagnosticExtract::SwMapping
Note This meta-class represents the ability to map a piece of application software to a J1939DiagnosticNode.
By this means the diagnostic configuration can be associated with the application software.
Tags:atp.recommendedPackage=DiagnosticJ1939SwMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
node DiagnosticJ1939Node 0..1 ref This represents the mapped DiagnosticJ1939Node.
swComponent SwComponent 0..1 iref This represents the mapped SwComponentPrototype.
Prototype Prototype
InstanceRef implemented by:ComponentInComposition
InstanceRef
Table 8.8: DiagnosticJ1939SwMapping

8.6 Mapping between DiagnosticEvent and J1939 DTC

[TPS_DEXT_01145] Semantics of meta-class DiagnosticEventToTrouble-
CodeJ1939Mapping dThe DiagnosticEventToTroubleCodeJ1939Mapping is
used to assign one (1:1) or multiple (n:1) DiagnosticEvents to a Diagnostic-
TroubleCodeJ1939.

256 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

In case of an n:1 mapping, multiple instances of DiagnosticEventToTrouble-

CodeJ1939Mapping with the same reference of role troubleCodeJ1939 but dif-
ferent references of role diagnosticEvent have to be defined.c(RS_DEXT_00067)
DiagnosticCommonElement
DiagnosticEvent

+ associatedEventIdentification: PositiveInteger [0..1]

+ clearEventAllowedBehavior: DiagnosticClearEventAllowedBehaviorEnum [0..1]
+ eventClearAllowed: DiagnosticEventClearAllowedEnum [0..1]
+ eventKind: DiagnosticEventKindEnum [0..1]
+ prestorageFreezeFrame: Boolean [0..1]
+ prestoredFreezeframeStoredInNvm: Boolean [0..1]
+ recoverableInSameOperationCycle: Boolean [0..1]
«atpVariation»
+ confirmationThreshold: PositiveInteger [0..1]

+diagnosticEvent 0..1

DiagnosticMapping
DiagnosticEventToTroubleCodeJ1939Mapping

+troubleCodeJ1939 0..1

DiagnosticTroubleCode
DiagnosticTroubleCodeJ1939

+ fmi: PositiveInteger [0..1]

+ kind: DiagnosticTroubleCodeJ1939DtcKindEnum [0..1]

Figure 8.3: Mapping between DiagnosticEvent and DiagnosticTroubleCodeJ1939

Class DiagnosticEventToTroubleCodeJ1939Mapping
Package M2::AUTOSARTemplates::DiagnosticExtract::Dem::J1939
Note By means of this meta-class it is possible to associate a DiagnosticEvent to a DiagnosticTroubleCode
J1939.
Tags:atp.recommendedPackage=DiagnosticMappings
Base ARElement, ARObject, CollectableElement, DiagnosticCommonElement, DiagnosticMapping,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
diagnosticEvent DiagnosticEvent 0..1 ref Reference to a DiagnosticEvent to which a J1939
Diagnostic Trouble Code is assigned.
troubleCode DiagnosticTroubleCode 0..1 ref Reference to a J1939 Diagnostic Trouble Code to which a
J1939 J1939 DiagnosticEvent is assigned.

Table 8.9: DiagnosticEventToTroubleCodeJ1939Mapping

[constr_1857] Existence of the reference DiagnosticEventToTrouble-

CodeJ1939Mapping.diagnosticEvent dFor each DiagnosticEventToTrou-
bleCodeJ1939Mapping, reference diagnosticEvent shall exist at the time when
the DEXT is complete.c()
[constr_1858] Existence of the attribute DiagnosticEventToTrouble-
CodeJ1939Mapping.troubleCodeJ1939 dFor each DiagnosticEventToTrou-
bleCodeJ1939Mapping, attribute troubleCodeJ1939 shall exist at the time when
the DEXT is complete.c()

257 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

A Mentioned Class Tables

For the sake of completeness, this chapter contains a set of class tables representing
meta-classes mentioned in the context of this document but which are not contained
directly in the scope of describing specific meta-model semantics.
Class ARElement (abstract)
Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::ARPackage
Note An element that can be defined stand-alone, i.e. without being part of another element (except for
packages of course).
Base ARObject, CollectableElement, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses AclObjectSet, AclOperation, AclPermission, AclRole, AliasNameSet, ApplicationPartition, AutosarData
Type, BaseType, BlueprintMappingSet, BswEntryRelationshipSet, BswModuleDescription, BswModule
Entry, BuildActionManifest, CalibrationParameterValueSet, ClientIdDefinitionSet, ClientServerInterfaceTo
BswModuleEntryBlueprintMapping, Collection, CompuMethod, ConsistencyNeedsBlueprintSet, Constant
Specification, ConstantSpecificationMappingSet, CpSoftwareCluster, CpSoftwareClusterBinaryManifest
Descriptor, CpSoftwareClusterMappingSet, CpSoftwareClusterResourcePool, CryptoServiceCertificate,
CryptoServiceKey, CryptoServicePrimitive, CryptoServiceQueue, DataConstr, DataExchangePoint, Data
TransformationSet, DataTypeMappingSet, DiagnosticCommonElement, DiagnosticConnection,
DiagnosticContributionSet, Documentation, E2EProfileCompatibilityProps, EcucDefinitionCollection,
EcucDestinationUriDefSet, EcucModuleConfigurationValues, EcucModuleDef, EcucValueCollection, End
ToEndProtectionSet, EthIpProps, EthTcpIpIcmpProps, EthTcpIpProps, EvaluatedVariantSet, FMFeature,
FMFeatureMap, FMFeatureModel, FMFeatureSelectionSet, FlatMap, GeneralPurposeConnection, Hw
Category, HwElement, HwType, IPSecConfigProps, IPv6ExtHeaderFilterSet, IdsCommonElement, Ids
Design, Implementation, InterpolationRoutineMappingSet, J1939ControllerApplication, KeywordSet, Life
CycleInfoSet, LifeCycleStateDefinitionGroup, McFunction, McGroup, ModeDeclarationGroup, Mode
DeclarationMappingSet, PhysicalDimension, PhysicalDimensionMappingSet, PortInterface, PortInterface
MappingSet, PortPrototypeBlueprint, PostBuildVariantCriterion, PostBuildVariantCriterionValueSet,
PredefinedVariant, RapidPrototypingScenario, SdgDef, SignalServiceTranslationPropsSet, SomeipSd
ClientEventGroupTimingConfig, SomeipSdClientServiceInstanceConfig, SomeipSdServerEventGroup
TimingConfig, SomeipSdServerServiceInstanceConfig, SwAddrMethod, SwAxisType, SwComponent
Type, SwRecordLayout, SwSystemconst, SwSystemconstantValueSet, SwcBswMapping, System,
SystemSignal, SystemSignalGroup, TDCpSoftwareClusterMappingSet, TcpOptionFilterSet, Timing
Extension, TlvDataIdDefinitionSet, TransformationPropsSet, Unit, UnitGroup, ViewMapSet
Attribute Type Mult. Kind Note
– – – – –
Table A.1: ARElement

Class ARPackage
Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::ARPackage
Note AUTOSAR package, allowing to create top level packages to structure the contained ARElements.
ARPackages are open sets. This means that in a file based description system multiple files can be used
to partially describe the contents of a package.
This is an extended version of MSR’s SW-SYSTEM.
Base ARObject, AtpBlueprint, AtpBlueprintable, CollectableElement, Identifiable, MultilanguageReferrable,
Referrable
Attribute Type Mult. Kind Note
5

258 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class ARPackage
arPackage ARPackage * aggr This represents a sub package within an ARPackage,
thus allowing for an unlimited package hierarchy.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=arPackage.shortName, arPackage.variation
Point.shortLabel
vh.latestBindingTime=blueprintDerivationTime
xml.sequenceOffset=30
element PackageableElement * aggr Elements that are part of this package
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=element.shortName, element.variation
Point.shortLabel
vh.latestBindingTime=systemDesignTime
xml.sequenceOffset=20
referenceBase ReferenceBase * aggr This denotes the reference bases for the package. This is
the basis for all relative references within the package.
The base needs to be selected according to the base
attribute within the references.
Stereotypes: atpSplitable
Tags:
atp.Splitkey=referenceBase.shortLabel
xml.sequenceOffset=10

Table A.2: ARPackage

Class ApplicationArrayDataType
Package M2::AUTOSARTemplates::SWComponentTemplate::Datatype::Datatypes
Note An application data type which is an array, each element is of the same application data type.
Tags:atp.recommendedPackage=ApplicationDataTypes
Base ARElement, ARObject, ApplicationCompositeDataType, ApplicationDataType, AtpBlueprint, Atp
Blueprintable, AtpClassifier , AtpType, AutosarDataType, CollectableElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dynamicArray String 0..1 attr Specifies the profile which the array will follow if it is a
SizeProfile variable size array.
element ApplicationArray 0..1 aggr This association implements the concept of an array
Element element. That is, in some cases it is necessary to be able
to identify single array elements, e.g. as input values for
an interpolation routine.

Table A.3: ApplicationArrayDataType

Class ApplicationDataType (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::Datatype::Datatypes
Note ApplicationDataType defines a data type from the application point of view. Especially it should be used
whenever something "physical" is at stake.
An ApplicationDataType represents a set of values as seen in the application model, such as
measurement units. It does not consider implementation details such as bit-size, endianess, etc.
It should be possible to model the application level aspects of a VFB system by using ApplicationData
Types only.
5

259 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class ApplicationDataType (abstract)
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, AutosarDataType,
CollectableElement, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses ApplicationCompositeDataType, ApplicationPrimitiveDataType
Attribute Type Mult. Kind Note
– – – – –
Table A.4: ApplicationDataType

Class AtomicSwComponentType (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::Components
Note An atomic software component is atomic in the sense that it cannot be further decomposed and
distributed across multiple ECUs.
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable, SwComponentType
Subclasses ApplicationSwComponentType, ComplexDeviceDriverSwComponentType, EcuAbstractionSwComponent
Type, NvBlockSwComponentType, SensorActuatorSwComponentType, ServiceProxySwComponent
Type, ServiceSwComponentType
Attribute Type Mult. Kind Note
internalBehavior SwcInternalBehavior 0..1 aggr The SwcInternalBehaviors owned by an AtomicSw
ComponentType can be located in a different physical file.
Therefore the aggregation is <<atpSplitable>>.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=internalBehavior.shortName, internal
Behavior.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
symbolProps SymbolProps 0..1 aggr This represents the SymbolProps for the AtomicSw
ComponentType.
Stereotypes: atpSplitable
Tags:atp.Splitkey=symbolProps.shortName

Table A.5: AtomicSwComponentType

Class AtpInstanceRef (abstract)

Package M2::AUTOSARTemplates::GenericStructure::AbstractStructure
Note An M0 instance of a classifier may be represented as a tree rooted at that instance, where under each
node come the sub-trees representing the instances which act as features under that node.
An instance ref specifies a navigation path from any M0 tree-instance of the base (which is a classifier) to
a leaf (which is an instance of the target).
Base ARObject
Subclasses AnyInstanceRef, ApplicationCompositeElementInPortInterfaceInstanceRef, ComponentInComposition
InstanceRef, ComponentInSystemInstanceRef, DataPrototypeInPortInterfaceInstanceRef , Data
PrototypeInSystemInstanceRef, InnerDataPrototypeGroupInCompositionInstanceRef, InnerPortGroupIn
CompositionInstanceRef, InnerRunnableEntityGroupInCompositionInstanceRef, InstanceEventIn
CompositionInstanceRef, ModeDeclarationGroupPrototypeInSystemInstanceRef, ModeGroupInAtomic
SwcInstanceRef , ModeInBswModuleDescriptionInstanceRef, ModeInSwcInstanceRef, Operation
ArgumentInComponentInstanceRef, OperationInAtomicSwcInstanceRef , OperationInSystemInstance
Ref, PModeInSystemInstanceRef, ParameterDataPrototypeInSystemInstanceRef, ParameterInAtomicS
WCTypeInstanceRef, PortGroupInSystemInstanceRef, PortInCompositionTypeInstanceRef , RModeIn
5
5

260 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class AtpInstanceRef (abstract)
4
AtomicSwcInstanceRef, RteEventInEcuInstanceRef, RunnableEntityInCompositionInstanceRef, Swc
ServiceDependencyInSystemInstanceRef, TriggerInAtomicSwcInstanceRef , TriggerInSystemInstance
Ref, VariableAccessInEcuInstanceRef, VariableDataPrototypeInCompositionInstanceRef, VariableData
PrototypeInSystemInstanceRef, VariableInAtomicSWCTypeInstanceRef, VariableInAtomicSwcInstance
Ref , VariableInComponentInstanceRef
Attribute Type Mult. Kind Note
atpBase AtpClassifier 1 ref This is the base from which the navigaion path starts.
Stereotypes: atpAbstract; atpDerived
atpContext AtpPrototype * ref This is one particular step in the navigation path.
Element
Stereotypes: atpAbstract
(ordered)
atpTarget AtpFeature 1 ref This is the target of the instance ref. In other words it is
the terminal of the navigation path.
Stereotypes: atpAbstract

Table A.6: AtpInstanceRef

Class BaseType (abstract)

Package M2::MSR::AsamHdo::BaseTypes
Note This abstract meta-class represents the ability to specify a platform dependant base type.
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Subclasses SwBaseType
Attribute Type Mult. Kind Note
baseType BaseTypeDefinition 1 aggr This is the actual definition of the base type.
Definition
Tags:
xml.roleElement=false
xml.roleWrapperElement=false
xml.sequenceOffset=20
xml.typeElement=false
xml.typeWrapperElement=false

Table A.7: BaseType

Class BaseTypeDirectDefinition
Package M2::MSR::AsamHdo::BaseTypes
Note This BaseType is defined directly (as opposite to a derived BaseType)
Base ARObject, BaseTypeDefinition
Attribute Type Mult. Kind Note
baseType BaseTypeEncoding 0..1 attr This specifies, how an object of the current BaseType is
Encoding String encoded, e.g. in an ECU within a message sequence.
Tags:xml.sequenceOffset=90
baseTypeSize PositiveInteger 0..1 attr Describes the length of the data type specified in the
container in bits.
Tags:xml.sequenceOffset=70
byteOrder ByteOrderEnum 0..1 attr This attribute specifies the byte order of the base type.
Tags:xml.sequenceOffset=110
5

261 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class BaseTypeDirectDefinition
memAlignment PositiveInteger 0..1 attr This attribute describes the alignment of the memory
object in bits. E.g. "8" specifies, that the object in
question is aligned to a byte while "32" specifies that it is
aligned four byte. If the value is set to "0" the meaning
shall be interpreted as "unspecified".
Tags:xml.sequenceOffset=100
native NativeDeclarationString 0..1 attr This attribute describes the declaration of such a base
Declaration type in the native programming language, primarily in the
Programming language C. This can then be used by a
code generator to include the necessary declarations into
a header file. For example
BaseType with shortName: "MyUnsignedInt" native
Declaration: "unsigned short"
Results in
typedef unsigned short MyUnsignedInt;
If the attribute is not defined the referring Implementation
DataTypes will not be generated as a typedef by RTE.
If a nativeDeclaration type is given it shall fulfill the
characteristic given by basetypeEncoding and baseType
Size.
This is required to ensure the consistent handling and
interpretation by software components, RTE, COM and
MCM systems.
Tags:xml.sequenceOffset=120

Table A.8: BaseTypeDirectDefinition

Class BswModuleDescription
Package M2::AUTOSARTemplates::BswModuleTemplate::BswOverview
Note Root element for the description of a single BSW module or BSW cluster. In case it describes a BSW
module, the short name of this element equals the name of the BSW module.
Tags:atp.recommendedPackage=BswModuleDescriptions
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpFeature, AtpStructureElement,
CollectableElement, Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
bswModule BswModuleDependency * aggr Describes the dependency to another BSW module.
Dependency
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=bswModuleDependency.shortName, bsw
ModuleDependency.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=20
bswModule SwComponent 0..1 aggr This adds a documentation to the BSW module.
Documentation Documentation
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=bswModuleDocumentation, bswModule
Documentation.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=6
5

262 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class BswModuleDescription
expectedEntry BswModuleEntry * ref Indicates an entry which is required by this module.
Replacement of outgoingCallback / requiredEntry.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=expectedEntry.bswModuleEntry, expected
Entry.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
implemented BswModuleEntry * ref Specifies an entry provided by this module which can be
Entry called by other modules. This includes "main" functions,
interrupt routines, and callbacks. Replacement of
providedEntry / expectedCallback.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=implementedEntry.bswModuleEntry,
implementedEntry.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
internalBehavior BswInternalBehavior * aggr The various BswInternalBehaviors associated with a Bsw
ModuleDescription can be distributed over several
physical files. Therefore the aggregation is <<atp
Splitable>>.
Stereotypes: atpSplitable
Tags:
atp.Splitkey=internalBehavior.shortName
xml.sequenceOffset=65
moduleId PositiveInteger 0..1 attr Refers to the BSW Module Identifier defined by the
AUTOSAR standard. For non-standardized modules, a
proprietary identifier can be optionally chosen.
Tags:xml.sequenceOffset=5
providedClient BswModuleClientServer * aggr Specifies that this module provides a client server entry
ServerEntry Entry which can be called from another parition or core.This
entry is declared locally to this context and will be
connected to the requiredClientServerEntry of another or
the same module via the configuration of the BSW
Scheduler.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=providedClientServerEntry.shortName,
providedClientServerEntry.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=45
providedData VariableDataPrototype * aggr Specifies a data prototype provided by this module in
order to be read from another partition or core.The
providedData is declared locally to this context and will be
connected to the requiredData of another or the same
module via the configuration of the BSW Scheduler.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=providedData.shortName, provided
Data.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=55
5

263 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class BswModuleDescription
providedMode ModeDeclarationGroup * aggr A set of modes which is owned and provided by this
Group Prototype module or cluster. It can be connected to the required
ModeGroups of other modules or clusters via the
configuration of the BswScheduler. It can also be
synchronized with modes provided via ports by an
associated ServiceSwComponentType, EcuAbstraction
SwComponentType or ComplexDeviceDriverSw
ComponentType.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=providedModeGroup.shortName, provided
ModeGroup.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=25
releasedTrigger Trigger * aggr A Trigger released by this module or cluster. It can be
connected to the requiredTriggers of other modules or
clusters via the configuration of the BswScheduler. It can
also be synchronized with Triggers provided via ports by
an associated ServiceSwComponentType, Ecu
AbstractionSwComponentType or ComplexDeviceDriver
SwComponentType.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=releasedTrigger.shortName, released
Trigger.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=35
requiredClient BswModuleClientServer * aggr Specifies that this module requires a client server entry
ServerEntry Entry which can be implemented on another parition or
core.This entry is declared locally to this context and will
be connected to the providedClientServerEntry of another
or the same module via the configuration of the BSW
Scheduler.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=requiredClientServerEntry.shortName,
requiredClientServerEntry.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=50
requiredData VariableDataPrototype * aggr Specifies a data prototype required by this module in oder
to be provided from another partition or core.The required
Data is declared locally to this context and will be
connected to the providedData of another or the same
module via the configuration of the BswScheduler.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=requiredData.shortName, required
Data.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=60
requiredMode ModeDeclarationGroup * aggr Specifies that this module or cluster depends on a certain
Group Prototype mode group. The requiredModeGroup is local to this
context and will be connected to the providedModeGroup
of another module or cluster via the configuration of the
BswScheduler.
5
5

264 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class BswModuleDescription
4
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=requiredModeGroup.shortName, required
ModeGroup.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=30
requiredTrigger Trigger * aggr Specifies that this module or cluster reacts upon an
external trigger.This requiredTrigger is declared locally to
this context and will be connected to the providedTrigger
of another module or cluster via the configuration of the
BswScheduler.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=requiredTrigger.shortName, required
Trigger.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=40

Table A.9: BswModuleDescription

Class CompositionSwComponentType
Package M2::AUTOSARTemplates::SWComponentTemplate::Composition
Note A CompositionSwComponentType aggregates SwComponentPrototypes (that in turn are typed by Sw
ComponentTypes) as well as SwConnectors for primarily connecting SwComponentPrototypes among
each others and towards the surface of the CompositionSwComponentType. By this means hierarchical
structures of software-components can be created.
Tags:atp.recommendedPackage=SwComponentTypes
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable, SwComponentType
Attribute Type Mult. Kind Note
component SwComponent * aggr The instantiated components that are part of this
Prototype composition. The aggregation of SwComponentPrototype
is subject to variability with the purpose to support the
conditional existence of a SwComponentPrototype.
Please be aware: if the conditional existence of Sw
ComponentPrototypes is resolved post-build the
deselected SwComponentPrototypes are still contained in
the ECUs build but the instances are inactive in in that
they are not scheduled by the RTE.
The aggregation is marked as atpSplitable in order to
allow the addition of service components to the ECU
extract during the ECU integration.
The use case for having 0 components owned by the
CompositionSwComponentType could be to deliver an
empty CompositionSwComponentType to e.g. a supplier
for filling the internal structure.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=component.shortName, component.variation
Point.shortLabel
vh.latestBindingTime=postBuild
5

265 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class CompositionSwComponentType
connector SwConnector * aggr SwConnectors have the principal ability to establish a
connection among PortPrototypes. They can have many
roles in the context of a CompositionSwComponentType.
Details are refined by subclasses.
The aggregation of SwConnectors is subject to variability
with the purpose to support variant data flow.
The aggregation is marked as atpSplitable in order to
allow the extension of the ECU extract with AssemblySw
Connectors between ApplicationSwComponentTypes and
ServiceSwComponentTypes during the ECU integration.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=connector.shortName, connector.variation
Point.shortLabel
vh.latestBindingTime=postBuild
constantValue ConstantSpecification * ref Reference to the ConstantSpecificationMapping to be
Mapping MappingSet applied for initValues of PPortComSpecs and RPortCom
Spec.
Stereotypes: atpSplitable
Tags:atp.Splitkey=constantValueMapping
dataType DataTypeMappingSet * ref Reference to the DataTypeMapping to be applied for the
Mapping used ApplicationDataTypes in PortInterfaces.
Background: when developing subsystems it may happen
that ApplicationDataTypes are used on the surface of
CompositionSwComponentTypes. In this case it would be
reasonable to be able to also provide the intended
mapping to the ImplementationDataTypes. However, this
mapping shall be informal and not technically binding for
the implementors mainly because the RTE generator is
not concerned about the CompositionSwComponent
Types.
Rationale: if the mapping of ApplicationDataTypes on the
delegated and inner PortPrototype matches then the
mapping to ImplementationDataTypes is not impacting
compatibility.
Stereotypes: atpSplitable
Tags:atp.Splitkey=dataTypeMapping
instantiation InstantiationRTEEvent * aggr This allows to define instantiation specific properties for
RTEEventProps Props RTE Events, in particular for instance specific scheduling.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=instantiationRTEEventProps.shortLabel,
instantiationRTEEventProps.variationPoint.shortLabel
vh.latestBindingTime=codeGenerationTime

Table A.10: CompositionSwComponentType

Class CompuMethod
Package M2::MSR::AsamHdo::ComputationMethod
5

266 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class CompuMethod
Note This meta-class represents the ability to express the relationship between a physical value and the
mathematical representation.
Note that this is still independent of the technical implementation in data types. It only specifies the
formula how the internal value corresponds to its physical pendant.
Tags:atp.recommendedPackage=CompuMethods
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, CollectableElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
compuInternal Compu 0..1 aggr This specifies the computation from internal values to
ToPhys physical values.
Tags:xml.sequenceOffset=80
compuPhysTo Compu 0..1 aggr This represents the computation from physical values to
Internal the internal values.
Tags:xml.sequenceOffset=90
displayFormat DisplayFormatString 0..1 attr This property specifies, how the physical value shall be
displayed e.g. in documents or measurement and
calibration tools.
Tags:xml.sequenceOffset=20
unit Unit 0..1 ref This is the physical unit of the Physical values for which
the CompuMethod applies.
Tags:xml.sequenceOffset=30

Table A.11: CompuMethod

Class DataConstr
Package M2::MSR::AsamHdo::Constraints::GlobalConstraints
Note This meta-class represents the ability to specify constraints on data.
Tags:atp.recommendedPackage=DataConstrs
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, CollectableElement, Identifiable, Multilanguage
Referrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
dataConstrRule DataConstrRule * aggr This is one particular rule within the data constraints.
Tags:
xml.roleElement=true
xml.roleWrapperElement=true
xml.sequenceOffset=30
xml.typeElement=false
xml.typeWrapperElement=false

Table A.12: DataConstr

Class DataInterface (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::PortInterface
Note The purpose of this meta-class is to act as an abstract base class for subclasses that share the
semantics of being concerned about data (as opposed to e.g. operations).
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, PortInterface, Referrable
5

267 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DataInterface (abstract)
Subclasses NvDataInterface, ParameterInterface, SenderReceiverInterface
Attribute Type Mult. Kind Note
– – – – –
Table A.13: DataInterface

Class DataPrototype (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::Datatype::DataPrototypes
Note Base class for prototypical roles of any data type.
Base ARObject, AtpFeature, AtpPrototype, Identifiable, MultilanguageReferrable, Referrable
Subclasses ApplicationCompositeElementDataPrototype, AutosarDataPrototype
Attribute Type Mult. Kind Note
swDataDef SwDataDefProps 0..1 aggr This property allows to specify data definition properties
Props which apply on data prototype level.

Table A.14: DataPrototype

Class DiagnosticEventNeeds
Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note Specifies the abstract needs on the configuration of the Diagnostic Event Manager for one diagnostic
event. Its shortName can be regarded as a symbol identifying the diagnostic event from the viewpoint of
the component or module which owns this element.
In case the diagnostic event specifies a production error, the shortName shall be the name of the
production error.
Base ARObject, DiagnosticCapabilityElement, Identifiable, MultilanguageReferrable, Referrable, Service
Needs
Attribute Type Mult. Kind Note
considerPto Boolean 0..1 attr PTO (Power Take Off) has an impact on the respective
Status emission-related event (OBD). This information shall be
provided by SW-C description in order to consider the
PTO relevance e.g. for readiness (PID $01) computation.
For events with dtcKind set to ’nonEmmissionRelatedDtc’
this attribute is typically false.
deferringFid FunctionInhibitionNeeds * ref This reference contains the link to a function identifier
within the FiM which is used by the monitor before
delivering a result.
diagEvent DiagEventDebounce 0..1 aggr Specifies the abstract need on the Debounce Algorithm
Debounce Algorithm applied by the Diagnostic Event Manager.
Algorithm
dtcKind DtcKindEnum 0..1 attr This attribute indicates the kind of the diagnostic monitor
according to the SWS Diagnostic Event Manger.
This attribute applies for the UDS diagnostics use case.
obdDtcNumber PositiveInteger 0..1 attr This represents a reasonable Diagnostic Trouble Code.
This allows to predefine the Diagnostic Trouble Code, e.g.
if the a function developer has received a particular
requirement from the OEM or from a standardization
body.
This attribute applies for the OBD diagnostics use case.
5

268 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class DiagnosticEventNeeds
prestored Boolean 0..1 attr If the Event uses a prestored freeze-frame (using the
Freezeframe operations PrestoreFreezeFrame and ClearPrestored
StoredInNvm FreezeFrame of the service interface DiagnosticMonitor)
this attribute indicates if the Event requires the data to be
stored in non-volatile memory. TRUE = Dem shall store
the prestored data in non-volatile memory, FALSE = Data
can be lost at shutdown (not stored in Nvm).
reportBehavior ReportBehaviorEnum 0..1 attr This switch indicates whether or not the BSW module is
allowed to report the related Events before Dem_Init().
udsDtcNumber PositiveInteger 0..1 attr This represents a reasonable Diagnostic Trouble Code.
This allows to predefine the Diagnostic Trouble Code, e.g.
if the a function developer has received a particular
requirement from the OEM or from a standardization
body.
This attribute applies for the UDS diagnostics use case.
usesMonitor Boolean 0..1 attr This attribute defines whether additional monitor data
Data shall be added to the reporting of events.

Table A.15: DiagnosticEventNeeds

Class EcuInstance
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreTopology
Note ECUInstances are used to define the ECUs used in the topology. The type of the ECU is defined by a
reference to an ECU specified with the ECU resource description.
Tags:atp.recommendedPackage=EcuInstances
Base ARObject, CollectableElement, FibexElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
associatedCom ISignalIPduGroup * ref With this reference it is possible to identify which ISignal
IPduGroup IPduGroups are applicable for which Communication
Connector/ ECU.
Only top level ISignalIPduGroups shall be referenced by
an EcuInstance. If an ISignalIPduGroup contains other
ISignalIPduGroups than these contained ISignalIPdu
Groups shall not be referenced by the EcuInstance.
Contained ISignalIPduGroups are associated to an Ecu
Instance via the top level ISignalIPduGroup.
associated ConsumedProvided * ref With this reference it is possible to identify which
Consumed ServiceInstanceGroup ConsumedProvidedServiceInstanceGroups are
Provided applicable for which ECUInstance.
ServiceInstance
Stereotypes: atpVariation
Group
Tags:vh.latestBindingTime=postBuild
associatedPdur PdurIPduGroup * ref With this reference it is possible to identify which PduR
IPduGroup IPdu Groups are applicable for which Communication
Connector/ ECU.
clientIdRange ClientIdRange 0..1 aggr Restriction of the Client Identifier for this Ecu to an
allowed range of numerical values. The Client Identifier of
the transaction handle is generated by the client RTE for
inter-Ecu Client/Server communication.
com TimeValue 0..1 attr The period between successive calls to Com_Main
Configuration FunctionRouteSignals of the AUTOSAR COM module in
GwTimeBase seconds.
5

269 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class EcuInstance
com TimeValue 0..1 attr The period between successive calls to Com_Main
ConfigurationRx FunctionRx of the AUTOSAR COM module in seconds.
TimeBase
com TimeValue 0..1 attr The period between successive calls to Com_Main
ConfigurationTx FunctionTx of the AUTOSAR COM module in seconds.
TimeBase
comEnable Boolean 0..1 attr Enables for the Com module of this EcuInstance the
MDTForCyclic minimum delay time monitoring for cyclic and repeated
Transmission transmissions (TransmissionModeTiming has cyclic
Timing assigned or eventControlledTiming with numberOf
Repetitions > 0).
commController Communication 1..* aggr CommunicationControllers of the ECU.
Controller
Stereotypes: atpVariation
Tags:vh.latestBindingTime=postBuild
connector Communication * aggr All channels controlled by a single controller.
Connector
Stereotypes: atpVariation
Tags:vh.latestBindingTime=postBuild
dltConfig DltConfig 0..1 aggr Describes the Dlt configuration on this EcuInstance.
doIpConfig DoIpConfig 0..1 aggr DoIp configuration on this EcuInstance.
Tags:atp.Status=draft
ethSwitchPort Boolean 0..1 attr Defines whether the derivation of SwitchPortGroups
Group based on VLAN and/or CouplingPort.pncMapping shall be
Derivation performed for this EcuInstance. If not defined the
derivation shall not be done.
partition EcuPartition * aggr Optional definition of Partitions within an Ecu.
pncPrepare TimeValue 0..1 attr Time in seconds the PNC state machine shall wait in
SleepTimer PNC_PREPARE_SLEEP.
pnc Boolean 0..1 attr If this parameter is available and set to true then all
Synchronous available PNCs will be woken up as soon as a channel
Wakeup wakeup occurs. This is ensured by adding all PNCs to all
channel wakeup sources during upstream mapping.
pnResetTime TimeValue 0..1 attr Specifies the runtime of the reset timer in seconds. This
reset time is valid for the reset of PN requests in the EIRA
and in the ERA.
sleepMode Boolean 1 attr Specifies whether the ECU instance may be put to a "low
Supported power mode"
• true: sleep mode is supported
• false: sleep mode is not supported
Note: This flag may only be set to "true" if the feature is
supported by both hardware and basic software.
tcpIpIcmpProps EthTcpIpIcmpProps 0..1 ref EcuInstance specific ICMP (Internet Control Message
Protocol) attributes
tcpIpProps EthTcpIpProps 0..1 ref EcuInstance specific TcpIp Stack attributes.
v2xSupported V2xSupportEnum 0..1 attr This attribute is used to control the existence of the V2X
stack on the given EcuInstance.
wakeUpOver Boolean 1 attr Driver support for wakeup over Bus.
BusSupported

Table A.16: EcuInstance

270 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class ISignal
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note Signal of the Interaction Layer. The RTE supports a "signal fan-out" where the same System Signal is
sent in different SignalIPdus to multiple receivers.
To support the RTE "signal fan-out" each SignalIPdu contains ISignals. If the same System Signal is to
be mapped into several SignalIPdus there is one ISignal needed for each ISignalToIPduMapping.
ISignals describe the Interface between the Precompile configured RTE and the potentially Postbuild
configured Com Stack (see ECUC Parameter Mapping).
In case of the SystemSignalGroup an ISignal shall be created for each SystemSignal contained in the
SystemSignalGroup.
Tags:atp.recommendedPackage=ISignals
Base ARObject, CollectableElement, FibexElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
data DataTransformation 0..1 ref Optional reference to a DataTransformation which
Transformation represents the transformer chain that is used to transform
the data that shall be placed inside this ISignal.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=dataTransformation.dataTransformation,
dataTransformation.variationPoint.shortLabel
vh.latestBindingTime=codeGenerationTime
dataTypePolicy DataTypePolicyEnum 1 attr With the aggregation of SwDataDefProps an ISignal
specifies how it is represented on the network. This
representation follows a particular policy. Note that this
causes some redundancy which is intended and can be
used to support flexible development methodology as well
as subsequent integrity checks.
If the policy "networkRepresentationFromComSpec" is
chosen the network representation from the ComSpec
that is aggregated by the PortPrototype shall be used. If
the "override" policy is chosen the requirements specified
in the PortInterface and in the ComSpec are not fulfilled
by the networkRepresentationProps. In case the System
Description doesn’t use a complete Software Component
Description (VFB View) the "legacy" policy can be
chosen.
initValue ValueSpecification 0..1 aggr Optional definition of a ISignal’s initValue in case the
System Description doesn’t use a complete Software
Component Description (VFB View). This supports the
inclusion of legacy system signals.
This value can be used to configure the Signal’s "Init
Value".
If a full DataMapping exist for the SystemSignal this
information may be available from a configured Sender
ComSpec and ReceiverComSpec. In this case the
initvalues in SenderComSpec and/or ReceiverComSpec
override this optional value specification. Further
restrictions apply from the RTE specification.
iSignalProps ISignalProps 0..1 aggr Additional optional ISignal properties that may be stored
in different files.
Stereotypes: atpSplitable
Tags:atp.Splitkey=iSignalProps
iSignalType ISignalTypeEnum 0..1 attr This attribute defines whether this iSignal is an array that
results in a UINT8_N / UINT8_DYN ComSignalType in the
COM configuration or a primitive type.
5

271 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class ISignal
length Integer 1 attr Size of the signal in bits. The size needs to be derived
from the mapped VariableDataPrototype according to the
mapping of primitive DataTypes to BaseTypes as used in
the RTE. Indicates maximum size for dynamic length
signals.
The ISignal length of zero bits is allowed.
network SwDataDefProps 0..1 aggr Specification of the actual network representation. The
Representation usage of SwDataDefProps for this purpose is restricted to
Props the attributes compuMethod and baseType. The optional
baseType attributes "memAllignment" and "byteOrder"
shall not be used.
The attribute "dataTypePolicy" in the SystemTemplate
element defines whether this network representation shall
be ignored and the information shall be taken over from
the network representation of the ComSpec.
If "override" is chosen by the system integrator the
network representation can violate against the
requirements defined in the PortInterface and in the
network representation of the ComSpec.
In case that the System Description doesn’t use a
complete Software Component Description (VFB View)
this element is used to configure "ComSignalDataInvalid
Value" and the Data Semantics.
systemSignal SystemSignal 1 ref Reference to the System Signal that is supposed to be
transmitted in the ISignal.
timeout ValueSpecification 0..1 aggr Defines and enables the ComTimeoutSubstituition for this
Substitution ISignal.
Value
transformation TransformationISignal * aggr A transformer chain consists of an ordered list of
ISignalProps Props transformers. The ISignal specific configuration
properties for each transformer are defined in the
TransformationISignalProps class. The transformer
configuration properties that are common for all ISignals
are described in the TransformationTechnology class.

Table A.17: ISignal

Class ISignalIPduGroup
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note The AUTOSAR COM Layer is able to start and to stop sending and receiving configurable groups of
I-Pdus during runtime. An ISignalIPduGroup contains either ISignalIPdus or ISignalIPduGroups.
Tags:atp.recommendedPackage=ISignaliPduGroup
Base ARObject, CollectableElement, FibexElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
communication Communication 1 attr This attribute determines in which direction IPdus that are
Direction DirectionType contained in this IPduGroup will be transmitted
(communication direction can be either In or Out).
communication String 1 attr This attribute defines the use-case for this ISignalIPdu
Mode Group (e.g. diagnostic, debugging etc.). For example, in a
diagnostic mode all IPdus - which are not involved in
diagnostic - are disabled. The use cases are not limited to
a fixed enumeration and can be specified as a string.
5

272 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class ISignalIPduGroup
contained ISignalIPduGroup * ref An I-Pdu group can be included in other I-Pdu groups.
ISignalIPdu Contained I-Pdu groups shall not be referenced by the
Group EcuInstance.
iSignalIPdu ISignalIPdu * ref Reference to a set of Signal I-Pdus, which are contained
in the ISignal I-Pdu Group.
atpVariation: The content of a ISignal I-Pdu group can
vary (->vehicle modes).
Stereotypes: atpVariation
Tags:vh.latestBindingTime=postBuild
nmPdu NmPdu * ref Reference to a set of NmPdus with NmUserData, which
are contained in the ISignalIPduGroup.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=postBuild

Table A.18: ISignalIPduGroup

Class IdentCaption (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::RPTScenario
Note This meta-class represents the caption. This allows having some meta classes optionally identifiable.
Base ARObject, AtpClassifier , AtpFeature, AtpStructureElement, Identifiable, MultilanguageReferrable,
Referrable
Subclasses BswServiceDependencyIdent, ExternalTriggeringPointIdent, ModeAccessPointIdent
Attribute Type Mult. Kind Note
– – – – –
Table A.19: IdentCaption

Class Identifiable (abstract)

Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::Identifiable
Note Instances of this class can be referred to by their identifier (within the namespace borders). In addition to
this, Identifiables are objects which contribute significantly to the overall structure of an AUTOSAR
description. In particular, Identifiables might contain Identifiables.
Base ARObject, MultilanguageReferrable, Referrable
Subclasses ARPackage, AbstractDoIpLogicAddressProps, AbstractEvent, AbstractImplementationDataTypeElement,
AbstractSecurityEventFilter , AbstractSecurityIdsmInstanceFilter , AbstractServiceInstance, Application
Endpoint, ApplicationError, ApplicationPartitionToEcuPartitionMapping, AsynchronousServerCallResult
Point, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpFeature, AutosarOperationArgumentInstance,
AutosarVariableInstance, BinaryManifestAddressableObject, BinaryManifestItemDefinition, Binary
ManifestResource, BinaryManifestResourceDefinition, BlockState, BswInternalTriggeringPoint, Bsw
ModuleDependency, BuildActionEntity , BuildActionEnvironment, CanTpAddress, CanTpChannel, CanTp
Node, Chapter, ClassContentConditional, ClientIdDefinition, ClientServerOperation, Code, Collectable
Element, ComManagementMapping, CommConnectorPort, CommunicationConnector , Communication
Controller , Compiler, ConsistencyNeeds, ConsumedEventGroup, CouplingPort, CouplingPortStructural
Element, CpSoftwareClusterResource, CpSoftwareClusterResourceToApplicationPartitionMapping, Cp
SoftwareClusterToEcuInstanceMapping, CpSoftwareClusterToResourceMapping, CryptoService
Mapping, DataPrototypeGroup, DataTransformation, DependencyOnArtifact, DiagEventDebounce
Algorithm, DiagnosticConnectedIndicator, DiagnosticDataElement, DiagnosticFunctionInhibitSource,
DiagnosticRoutineSubfunction, DltArgument, DltLogChannel, DltMessage, DoIpInterface, DoIpLogic
Address, DoIpRoutingActivation, ECUMapping, EOCExecutableEntityRefAbstract, EcuPartition, Ecuc
ContainerValue, EcucDefinitionElement, EcucDestinationUriDef, EcucEnumerationLiteralDef, Ecuc
Query, EcucValidationCondition, EndToEndProtection, EthernetWakeupSleepOnDatalineConfig,
5
5

273 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class Identifiable (abstract)
4
ExclusiveArea, ExecutableEntity , ExecutionTime, FMAttributeDef, FMFeatureMapAssertion, FMFeature
MapCondition, FMFeatureMapElement, FMFeatureRelation, FMFeatureRestriction, FMFeatureSelection,
FlatInstanceDescriptor, FlexrayArTpNode, FlexrayTpConnectionControl, FlexrayTpNode, FlexrayTpPdu
Pool, FrameTriggering, GeneralParameter, GlobalTimeGateway, GlobalTimeMaster , GlobalTimeSlave,
HeapUsage, HwAttributeDef, HwAttributeLiteralDef, HwPin, HwPinGroup, IPSecRule, IPv6ExtHeader
FilterList, ISignalToIPduMapping, ISignalTriggering, IdentCaption, InternalTriggeringPoint, J1939Shared
AddressCluster, J1939TpNode, Keyword, LifeCycleState, LinScheduleTable, LinTpNode, Linker, Mac
MulticastGroup, McDataInstance, MemorySection, ModeDeclaration, ModeDeclarationMapping, Mode
SwitchPoint, NetworkEndpoint, NmCluster , NmEcu, NmNode, NvBlockDescriptor, PackageableElement,
ParameterAccess, PduToFrameMapping, PduTriggering, PerInstanceMemory, PhysicalChannel, Port
ElementToCommunicationResourceMapping, PortGroup, PortInterfaceMapping, PossibleErrorReaction,
ResourceConsumption, RootSwCompositionPrototype, RptComponent, RptContainer, RptExecutable
Entity, RptExecutableEntityEvent, RptExecutionContext, RptProfile, RptServicePoint, RunnableEntity
Group, SdgAttribute, SdgClass, SecureCommunicationAuthenticationProps, SecureCommunication
FreshnessProps, SecurityEventContextProps, ServerCallPoint, ServiceNeeds, SignalServiceTranslation
ElementProps, SignalServiceTranslationEventProps, SignalServiceTranslationProps, SocketAddress,
SomeipTpChannel, SpecElementReference, StackUsage, StaticSocketConnection, StructuredReq, Sw
GenericAxisParamType, SwServiceArg, SwcServiceDependency, SwcToApplicationPartitionMapping,
SwcToEcuMapping, SwcToImplMapping, SystemMapping, TDCpSoftwareClusterMapping, TDCp
SoftwareClusterResourceMapping, TcpOptionFilterList, TimingCondition, TimingConstraint, Timing
Description, TimingExtensionResource, TimingModeInstance, TlsCryptoCipherSuite, Topic1, TpAddress,
TraceableTable, TraceableText, TracedFailure, TransformationProps, TransformationTechnology, Trigger,
VariableAccess, VariationPointProxy, ViewMap, VlanConfig, WaitPoint
Attribute Type Mult. Kind Note
adminData AdminData 0..1 aggr This represents the administrative data for the identifiable
object.
Tags:xml.sequenceOffset=-40
annotation Annotation * aggr Possibility to provide additional notes while defining a
model element (e.g. the ECU Configuration Parameter
Values). These are not intended as documentation but
are mere design notes.
Tags:xml.sequenceOffset=-25
category CategoryString 0..1 attr The category is a keyword that specializes the semantics
of the Identifiable. It affects the expected existence of
attributes and the applicability of constraints.
Tags:xml.sequenceOffset=-50
desc MultiLanguageOverview 0..1 aggr This represents a general but brief (one paragraph)
Paragraph description what the object in question is about. It is only
one paragraph! Desc is intended to be collected into
overview tables. This property helps a human reader to
identify the object in question.
More elaborate documentation, (in particular how the
object is built or used) should go to "introduction".
Tags:xml.sequenceOffset=-60
introduction DocumentationBlock 0..1 aggr This represents more information about how the object in
question is built or is used. Therefore it is a
DocumentationBlock.
Tags:xml.sequenceOffset=-30
uuid String 0..1 attr The purpose of this attribute is to provide a globally
unique identifier for an instance of a meta-class. The
values of this attribute should be globally unique strings
prefixed by the type of identifier. For example, to include a
DCE UUID as defined by The Open Group, the UUID
would be preceded by "DCE:". The values of this attribute
5
5

274 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class Identifiable (abstract)
4
may be used to support merging of different AUTOSAR
models. The form of the UUID (Universally Unique
Identifier) is taken from a standard defined by the Open
Group (was Open Software Foundation). This standard is
widely used, including by Microsoft for COM (GUIDs) and
by many companies for DCE, which is based on CORBA.
The method for generating these 128-bit IDs is published
in the standard and the effectiveness and uniqueness of
the IDs is not in practice disputed. If the id namespace is
omitted, DCE is assumed. An example is
"DCE:2fac1234-31f8-11b4-a222-08002b34c003". The
uuid attribute has no semantic meaning for an AUTOSAR
model and there is no requirement for AUTOSAR tools to
manage the timestamp.
Tags:xml.attribute=true

Table A.20: Identifiable

Class InternalBehavior (abstract)

Package M2::AUTOSARTemplates::CommonStructure::InternalBehavior
Note Common base class (abstract) for the internal behavior of both software components and basic software
modules/clusters.
Base ARObject, AtpClassifier , AtpFeature, AtpStructureElement, Identifiable, MultilanguageReferrable,
Referrable
Subclasses BswInternalBehavior, SwcInternalBehavior
Attribute Type Mult. Kind Note
constant ParameterData * aggr Describes a read only memory object containing
Memory Prototype characteristic value(s) implemented by this Internal
Behavior.
The shortName of ParameterDataPrototype has to be
equal to the ”C’ identifier of the described constant.
The characteristic value(s) might be shared between Sw
ComponentPrototypes of the same SwComponentType.
The aggregation of constantMemory is subject to
variability with the purpose to support variability in the
software component or module implementations.
Typically different algorithms in the implementation are
requiring different number of memory objects.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=constantMemory.shortName, constant
Memory.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
constantValue ConstantSpecification * ref Reference to the ConstanSpecificationMapping to be
Mapping MappingSet applied for the particular InternalBehavior
Stereotypes: atpSplitable
Tags:atp.Splitkey=constantValueMapping
dataType DataTypeMappingSet * ref Reference to the DataTypeMapping to be applied for the
Mapping particular InternalBehavior
Stereotypes: atpSplitable
Tags:atp.Splitkey=dataTypeMapping
5

275 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class InternalBehavior (abstract)
exclusiveArea ExclusiveArea * aggr This specifies an ExclusiveArea for this InternalBehavior.
The exclusiveArea is local to the component resp.
module. The aggregation of ExclusiveAreas is subject to
variability. Note: the number of ExclusiveAreas might vary
due to the conditional existence of RunnableEntities or
BswModuleEntities.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=exclusiveArea.shortName, exclusive
Area.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
exclusiveArea ExclusiveAreaNesting * aggr This represents the set of ExclusiveAreaNestingOrder
NestingOrder Order owned by the InternalBehavior.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=exclusiveAreaNestingOrder.shortName,
exclusiveAreaNestingOrder.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
staticMemory VariableDataPrototype * aggr Describes a read and writeable static memory object
representing measurerment variables implemented by
this software component. The term "static" is used in the
meaning of "non-temporary" and does not necessarily
specify a linker encapsulation. This kind of memory is
only supported if supportsMultipleInstantiation is FALSE.
The shortName of the VariableDataPrototype has to be
equal with the ”C’ identifier of the described variable.
The aggregation of staticMemory is subject to variability
with the purpose to support variability in the software
component’s implementations.
Typically different algorithms in the implementation are
requiring different number of memory objects.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=staticMemory.shortName, static
Memory.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime

Table A.21: InternalBehavior

Class <<atpVariation>> J1939Cluster

Package M2::AUTOSARTemplates::SystemTemplate::Fibex::Fibex4Can::CanTopology
Note J1939 specific cluster attributes.
Tags:atp.recommendedPackage=CommunicationClusters
Base ARObject, AbstractCanCluster , CollectableElement, CommunicationCluster , FibexElement, Identifiable,
MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
networkId PositiveInteger 0..1 attr This represents the network ID for the J1939 cluster.
re- Boolean 0..1 attr Enables support for the Request2 PGN (RQST2).
quest2Support
5

276 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class <<atpVariation>> J1939Cluster
usesAddress Boolean 0..1 attr Defines whether the nodes attached to this channel use
Arbitration an initial address claim, and whether they react to
contending address claims of other nodes.
True: The initial address claim is sent, and the node
reacts to address claims of other nodes.
False: The node only sends an address claim upon
request, and does not care for contending address claims.

Table A.22: J1939Cluster

Class J1939DcmIPdu
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note Represents the IPdus handled by J1939Dcm.
Tags:atp.recommendedPackage=Pdus
Base ARObject, CollectableElement, FibexElement, IPdu, Identifiable, MultilanguageReferrable, Packageable
Element, Pdu, Referrable
Attribute Type Mult. Kind Note
diagnostic PositiveInteger 0..1 attr This attribute is used to identify the actual DMx message,
MessageType e.g 1 means DM01, etc.

Table A.23: J1939DcmIPdu

Class J1939NmNode
Package M2::AUTOSARTemplates::SystemTemplate::NetworkManagement
Note J1939 specific NM Node attributes.
Base ARObject, Identifiable, MultilanguageReferrable, NmNode, Referrable
Attribute Type Mult. Kind Note
nodeName J1939NodeName 0..1 aggr NodeName configuration

Table A.24: J1939NmNode

Class ModeDeclaration
Package M2::AUTOSARTemplates::CommonStructure::ModeDeclaration
Note Declaration of one Mode. The name and semantics of a specific mode is not defined in the meta-model.
Base ARObject, AtpClassifier , AtpFeature, AtpStructureElement, Identifiable, MultilanguageReferrable,
Referrable
Attribute Type Mult. Kind Note
value PositiveInteger 0..1 attr The RTE shall take the value of this attribute for
generating the source code representation of this Mode
Declaration.
Table A.25: ModeDeclaration

277 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class ModeDeclarationGroup
Package M2::AUTOSARTemplates::CommonStructure::ModeDeclaration
Note A collection of Mode Declarations. Also, the initial mode is explicitly identified.
Tags:atp.recommendedPackage=ModeDeclarationGroups
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
initialMode ModeDeclaration 0..1 ref The initial mode of the ModeDeclarationGroup. This
mode is active before any mode switches occurred.
mode ModeDeclaration * aggr The ModeDeclarations collected in this ModeDeclaration
Declaration Group.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=blueprintDerivationTime
modeManager ModeErrorBehavior 0..1 aggr This represents the ability to define the error behavior
ErrorBehavior expected by the mode manager in case of errors on the
mode user side (e.g. terminated mode user).
modeTransition ModeTransition * aggr This represents the avaliable ModeTransitions of the
ModeDeclarationGroup
modeUserError ModeErrorBehavior 0..1 aggr This represents the definition of the error behavior
Behavior expected by the mode user in case of errors on the mode
manager side (e.g. terminated mode manager).
onTransition PositiveInteger 0..1 attr The value of this attribute shall be taken into account by
Value the RTE generator for programmatically representing a
value used for the transition between two statuses.
Table A.26: ModeDeclarationGroup

Class ModeDeclarationGroupPrototype
Package M2::AUTOSARTemplates::CommonStructure::ModeDeclaration
Note The ModeDeclarationGroupPrototype specifies a set of Modes (ModeDeclarationGroup) which is
provided or required in the given context.
Base ARObject, AtpFeature, AtpPrototype, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
swCalibration SwCalibrationAccess 0..1 attr This allows for specifying whether or not the enclosing
Access Enum ModeDeclarationGroupPrototype can be measured at
run-time.
type ModeDeclarationGroup 0..1 tref The "collection of ModeDeclarations" ( = ModeDeclaration
Group) supported by a component
Stereotypes: isOfType

Table A.27: ModeDeclarationGroupPrototype

Class ModeInBswModuleDescriptionInstanceRef
Package M2::AUTOSARTemplates::BswModuleTemplate::BswOverview::InstanceRefs
Note
Base ARObject, AtpInstanceRef
Attribute Type Mult. Kind Note
base BswModuleDescription 0..1 ref Stereotypes: atpDerived
Tags:xml.sequenceOffset=10
5

278 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class ModeInBswModuleDescriptionInstanceRef
contextMode ModeDeclarationGroup 0..1 ref Tags:xml.sequenceOffset=20
Declaration Prototype
Group
targetMode ModeDeclaration 0..1 ref Tags:xml.sequenceOffset=30

Table A.28: ModeInBswModuleDescriptionInstanceRef

Primitive NameToken
Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::PrimitiveTypes
Note This is an identifier as used in xml, e.g. xml-names. Basic difference to Identifier is the fact that it can
contain "-".
Tags:
xml.xsd.customType=NMTOKEN-STRING
xml.xsd.type=NMTOKEN

Table A.29: NameToken

Class NvDataInterface
Package M2::AUTOSARTemplates::SWComponentTemplate::PortInterface
Note A non volatile data interface declares a number of VariableDataPrototypes to be exchanged between non
volatile block components and atomic software components.
Tags:atp.recommendedPackage=PortInterfaces
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
DataInterface, Identifiable, MultilanguageReferrable, PackageableElement, PortInterface, Referrable
Attribute Type Mult. Kind Note
nvData VariableDataPrototype * aggr The VariableDataPrototype of this nv data interface.

Table A.30: NvDataInterface

Class PPortPrototype
Package M2::AUTOSARTemplates::SWComponentTemplate::Components
Note Component port providing a certain port interface.
Base ARObject, AbstractProvidedPortPrototype, AtpBlueprintable, AtpFeature, AtpPrototype, Identifiable,
MultilanguageReferrable, PortPrototype, Referrable
Attribute Type Mult. Kind Note
provided PortInterface 0..1 tref The interface that this port provides.
Interface
Stereotypes: isOfType

Table A.31: PPortPrototype

Class PortInterface (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::PortInterface
Note Abstract base class for an interface that is either provided or required by a port of a software component.
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
5

279 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class PortInterface (abstract)
Subclasses ClientServerInterface, DataInterface, ModeSwitchInterface, TriggerInterface
Attribute Type Mult. Kind Note
isService Boolean 0..1 attr This flag is set if the PortInterface is to be used for
communication between an
• ApplicationSwComponentType or
• ServiceProxySwComponentType or
• SensorActuatorSwComponentType or
• ComplexDeviceDriverSwComponentType
• ServiceSwComponentType
• EcuAbstractionSwComponentType
and a ServiceSwComponentType (namely an AUTOSAR
Service) located on the same ECU. Otherwise the flag is
not set.
serviceKind ServiceProviderEnum 0..1 attr This attribute provides further details about the nature of
the applied service.

Table A.32: PortInterface

Class PortPrototype (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::Components
Note Base class for the ports of an AUTOSAR software component.
The aggregation of PortPrototypes is subject to variability with the purpose to support the conditional
existence of ports.
Base ARObject, AtpBlueprintable, AtpFeature, AtpPrototype, Identifiable, MultilanguageReferrable, Referrable
Subclasses AbstractProvidedPortPrototype, AbstractRequiredPortPrototype
Attribute Type Mult. Kind Note
clientServer ClientServerAnnotation * aggr Annotation of this PortPrototype with respect to client/
Annotation server communication.
delegatedPort DelegatedPort 0..1 aggr Annotations on this delegated port.
Annotation Annotation
ioHwAbstraction IoHwAbstractionServer * aggr Annotations on this IO Hardware Abstraction port.
Server Annotation
Annotation
modePort ModePortAnnotation * aggr Annotations on this mode port.
Annotation
nvDataPort NvDataPortAnnotation * aggr Annotations on this non voilatile data port.
Annotation
parameterPort ParameterPort * aggr Annotations on this parameter port.
Annotation Annotation
senderReceiver SenderReceiver * aggr Collection of annotations of this ports sender/receiver
Annotation Annotation communication.
triggerPort TriggerPortAnnotation * aggr Annotations on this trigger port.
Annotation
Table A.33: PortPrototype

280 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class Referrable (abstract)

Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::Identifiable
Note Instances of this class can be referred to by their identifier (while adhering to namespace borders).
Base ARObject
Subclasses AtpDefinition, BswDistinguishedPartition, BswModuleCallPoint, BswModuleClientServerEntry, Bsw
VariableAccess, CouplingPortTrafficClassAssignment, DiagnosticDebounceAlgorithmProps, Diagnostic
EnvModeElement, EthernetPriorityRegeneration, EventHandler, ExclusiveAreaNestingOrder, Hw
DescriptionEntity , ImplementationProps, LinSlaveConfigIdent, ModeTransition, MultilanguageReferrable,
PduActivationRoutingGroup, PncMappingIdent, SingleLanguageReferrable, SoConIPduIdentifier, Socket
ConnectionBundle, TimeSyncServerConfiguration, TpConnectionIdent
Attribute Type Mult. Kind Note
shortName Identifier 1 attr This specifies an identifying shortName for the object. It
needs to be unique within its context and is intended for
humans but even more for technical reference.
Stereotypes: atpIdentityContributor
Tags:
xml.enforceMinMultiplicity=true
xml.sequenceOffset=-100
shortName ShortNameFragment * aggr This specifies how the Referrable.shortName is
Fragment composed of several shortNameFragments.
Tags:xml.sequenceOffset=-90

Table A.34: Referrable

Class Sdg
Package M2::MSR::AsamHdo::SpecialData
Note Sdg (SpecialDataGroup) is a generic model which can be used to keep arbitrary information which is not
explicitly modeled in the meta-model.
Sdg can have various contents as defined by sdgContentsType. Special Data should only be used
moderately since all elements should be defined in the meta-model.
Thereby SDG should be considered as a temporary solution when no explicit model is available. If an sdg
Caption is available, it is possible to establish a reference to the sdg structure.
Base ARObject
Attribute Type Mult. Kind Note
gid NameToken 1 attr This attributes specifies an identifier. Gid comes from the
SGML/XML-Term "Generic Identifier" which is the
element name in XML. The role of this attribute is the
same as the name of an XML - element.
Tags:xml.attribute=true
sdgCaption SdgCaption 0..1 aggr This aggregation allows to assign the properties of
Identifiable to the sdg. By this, a shortName etc. can be
assigned to the Sdg.
Tags:xml.sequenceOffset=20
sdgContents SdgContents 0..1 aggr This is the content of the Sdg.
Type
Tags:
xml.roleElement=false
xml.roleWrapperElement=false
xml.sequenceOffset=30
xml.typeElement=false
xml.typeWrapperElement=false

Table A.35: Sdg

281 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class SenderReceiverInterface
Package M2::AUTOSARTemplates::SWComponentTemplate::PortInterface
Note A sender/receiver interface declares a number of data elements to be sent and received.
Tags:atp.recommendedPackage=PortInterfaces
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
DataInterface, Identifiable, MultilanguageReferrable, PackageableElement, PortInterface, Referrable
Attribute Type Mult. Kind Note
dataElement VariableDataPrototype * aggr The data elements of this SenderReceiverInterface.
invalidation InvalidationPolicy * aggr InvalidationPolicy for a particular dataElement
Policy
metaDataItem MetaDataItemSet * aggr This aggregation defines fixed sets of meta-data items
Set associated with dataElements of the enclosing Sender
ReceiverInterface
Table A.36: SenderReceiverInterface

Class ServiceNeeds (abstract)

Package M2::AUTOSARTemplates::CommonStructure::ServiceNeeds
Note This expresses the abstract needs that a Software Component or Basic Software Module has on the
configuration of an AUTOSAR Service to which it will be connected. "Abstract needs" means that the
model abstracts from the Configuration Parameters of the underlying Basic Software.
Base ARObject, Identifiable, MultilanguageReferrable, Referrable
Subclasses BswMgrNeeds, ComMgrUserNeeds, CryptoKeyManagementNeeds, CryptoServiceJobNeeds, Crypto
ServiceNeeds, DiagnosticCapabilityElement, DltUserNeeds, DoIpServiceNeeds, EcuStateMgrUser
Needs, ErrorTracerNeeds, FunctionInhibitionAvailabilityNeeds, FunctionInhibitionNeeds, Global
SupervisionNeeds, HardwareTestNeeds, IdsMgrCustomTimestampNeeds, IdsMgrNeeds, IndicatorStatus
Needs, J1939DcmDm19Support, J1939RmIncomingRequestServiceNeeds, J1939RmOutgoingRequest
ServiceNeeds, NvBlockNeeds, SecureOnBoardCommunicationNeeds, SupervisedEntityCheckpoint
Needs, SupervisedEntityNeeds, SyncTimeBaseMgrUserNeeds, V2xFacUserNeeds, V2xMUserNeeds,
VendorSpecificServiceNeeds
Attribute Type Mult. Kind Note
– – – – –
Table A.37: ServiceNeeds

Class SwBaseType
Package M2::MSR::AsamHdo::BaseTypes
Note This meta-class represents a base type used within ECU software.
Tags:atp.recommendedPackage=BaseTypes
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, BaseType, CollectableElement, Identifiable,
MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
– – – – –
Table A.38: SwBaseType

282 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class SwComponentPrototype
Package M2::AUTOSARTemplates::SWComponentTemplate::Composition
Note Role of a software component within a composition.
Base ARObject, AtpFeature, AtpPrototype, Identifiable, MultilanguageReferrable, Referrable
Attribute Type Mult. Kind Note
type SwComponentType 0..1 tref Type of the instance.
Stereotypes: isOfType

Table A.39: SwComponentPrototype

Class SwComponentType (abstract)

Package M2::AUTOSARTemplates::SWComponentTemplate::Components
Note Base class for AUTOSAR software components.
Base ARElement, ARObject, AtpBlueprint, AtpBlueprintable, AtpClassifier , AtpType, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Subclasses AtomicSwComponentType, CompositionSwComponentType, ParameterSwComponentType
Attribute Type Mult. Kind Note
consistency ConsistencyNeeds * aggr This represents the collection of ConsistencyNeeds
Needs owned by the enclosing SwComponentType.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=consistencyNeeds.shortName, consistency
Needs.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
port PortPrototype * aggr The PortPrototypes through which this SwComponent
Type can communicate.
The aggregation of PortPrototype is subject to variability
with the purpose to support the conditional existence of
PortPrototypes.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=port.shortName, port.variationPoint.short
Label
vh.latestBindingTime=preCompileTime
portGroup PortGroup * aggr A port group being part of this component.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=preCompileTime
swComponent SwComponent 0..1 aggr This adds a documentation to the SwComponentType.
Documentation Documentation
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=swComponentDocumentation, sw
ComponentDocumentation.variationPoint.shortLabel
vh.latestBindingTime=preCompileTime
xml.sequenceOffset=-10
unitGroup UnitGroup * ref This allows for the specification of which UnitGroups are
relevant in the context of referencing SwComponentType.

Table A.40: SwComponentType

283 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class System
Package M2::AUTOSARTemplates::SystemTemplate
Note The top level element of the System Description. The System description defines five major elements:
Topology, Software, Communication, Mapping and Mapping Constraints.
The System element directly aggregates the elements describing the Software, Mapping and Mapping
Constraints; it contains a reference to an ASAM FIBEX description specifying Communication and
Topology.
Tags:atp.recommendedPackage=Systems
Base ARElement, ARObject, AtpClassifier , AtpFeature, AtpStructureElement, CollectableElement,
Identifiable, MultilanguageReferrable, PackageableElement, Referrable
Attribute Type Mult. Kind Note
clientId ClientIdDefinitionSet * ref Set of Client Identifiers that are used for inter-ECU
DefinitionSet client-server communication in the System.
containerIPdu ByteOrderEnum 0..1 attr Defines the byteOrder of the header in ContainerIPdus.
HeaderByte
Order
ecuExtract RevisionLabelString 0..1 attr Version number of the Ecu Extract.
Version
fibexElement FibexElement * ref Reference to ASAM FIBEX elements specifying
Communication and Topology.
All Fibex Elements used within a System Description shall
be referenced from the System Element.
atpVariation: In order to describe a product-line, all Fibex
Elements can be optional.
Stereotypes: atpVariation
Tags:vh.latestBindingTime=postBuild
interpolation InterpolationRoutine * ref This reference identifies the InterpolationRoutineMapping
Routine MappingSet Sets that are relevant in the context of the enclosing
MappingSet System.
j1939Shared J1939SharedAddress * aggr Collection of J1939Clusters that share a common
AddressCluster Cluster address space for the routing of messages.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=j1939SharedAddressCluster.shortName,
j1939SharedAddressCluster.variationPoint.shortLabel
vh.latestBindingTime=postBuild
mapping SystemMapping * aggr Aggregation of all mapping aspects (mapping of SW
components to ECUs, mapping of data elements to
signals, and mapping constraints).
In order to support OEM / Tier 1 interaction and shared
development for one common System this aggregation is
atpSplitable and atpVariation. The content of System
Mapping can be provided by several parties using
different names for the SystemMapping.
This element is not required when the System description
is used for a network-only use-case.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=mapping.shortName, mapping.variation
Point.shortLabel
vh.latestBindingTime=postBuild
pncVector PositiveInteger 0..1 attr Length of the partial networking request release
Length information vector (in bytes).
5

284 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Class System
pncVectorOffset PositiveInteger 0..1 attr Absolute offset (with respect to the NM-PDU) of the
partial networking request release information vector that
is defined in bytes as an index starting with 0.
rootSoftware RootSwComposition 0..1 aggr Aggregation of the root software composition, containing
Composition Prototype all software components in the System in a hierarchical
structure. This element is not required when the System
description is used for a network-only use-case.
atpVariation: The RootSwCompositionPrototype can vary.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=rootSoftwareComposition.shortName, root
SoftwareComposition.variationPoint.shortLabel
vh.latestBindingTime=systemDesignTime
swCluster CpSoftwareCluster * ref CP Software Clusters of this System
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=swCluster.cpSoftwareCluster, sw
Cluster.variationPoint.shortLabel
atp.Status=draft
vh.latestBindingTime=systemDesignTime
system Chapter * aggr Possibility to provide additional documentation while
Documentation defining the System. The System documentation can be
composed of several chapters.
Stereotypes: atpSplitable; atpVariation
Tags:
atp.Splitkey=systemDocumentation.shortName, system
Documentation.variationPoint.shortLabel
vh.latestBindingTime=systemDesignTime
xml.sequenceOffset=-10
systemVersion RevisionLabelString 1 attr Version number of the System Description.

Table A.41: System

Class SystemSignal
Package M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication
Note The system signal represents the communication system’s view of data exchanged between SW
components which reside on different ECUs. The system signals allow to represent this communication
in a flattened structure, with exactly one system signal defined for each data element prototype sent and
received by connected SW component instances.
Tags:atp.recommendedPackage=SystemSignals
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
dynamicLength Boolean 1 attr The length of dynamic length signals is variable in
run-time. Only a maximum length of such a signal is
specified in the configuration (attribute length in ISignal
element).
physicalProps SwDataDefProps 0..1 aggr Specification of the physical representation.

Table A.42: SystemSignal

285 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class Unit
Package M2::MSR::AsamHdo::Units
Note This is a physical measurement unit. All units that might be defined should stem from SI units. In order to
convert one unit into another factor and offset are defined.
For the calculation from SI-unit to the defined unit the factor (factorSiToUnit ) and the offset (offsetSiTo
Unit ) are applied as follows:
x [{unit}] := y * [{siUnit}] * factorSiToUnit [[unit]/{siUnit}] + offsetSiToUnit [{unit}]
For the calculation from a unit to SI-unit the reciprocal of the factor (factorSiToUnit ) and the negation of
the offset (offsetSiToUnit ) are applied.
y {siUnit} := (x*{unit} - offsetSiToUnit [{unit}]) / (factorSiToUnit [[unit]/{siUnit}]
Tags:atp.recommendedPackage=Units
Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable
Element, Referrable
Attribute Type Mult. Kind Note
displayName SingleLanguageUnit 0..1 aggr This specifies how the unit shall be displayed in
Names documents or in user interfaces of tools.The displayName
corresponds to the Unit.Display in an ASAM MCD-2MC
file.
Tags:xml.sequenceOffset=20
factorSiToUnit Float 0..1 attr This is the factor for the conversion from SI Units to units.
The inverse is used for conversion from units to SI Units.
Tags:xml.sequenceOffset=30
offsetSiToUnit Float 0..1 attr This is the offset for the conversion from and to siUnits.
Tags:xml.sequenceOffset=40
physical PhysicalDimension 0..1 ref This association represents the physical dimension to
Dimension which the unit belongs to. Note that only values with units
of the same physical dimensions might be converted.
Tags:xml.sequenceOffset=50

Table A.43: Unit

Class ValueSpecification (abstract)

Package M2::AUTOSARTemplates::CommonStructure::Constants
Note Base class for expressions leading to a value which can be used to initialize a data object.
Base ARObject
Subclasses AbstractRuleBasedValueSpecification, ApplicationValueSpecification, CompositeValueSpecification,
ConstantReference, NotAvailableValueSpecification, NumericalValueSpecification, ReferenceValue
Specification, TextValueSpecification
Attribute Type Mult. Kind Note
shortLabel Identifier 0..1 attr This can be used to identify particular value specifications
for human readers, for example elements of a record type.

Table A.44: ValueSpecification

286 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class VariableDataPrototype
Package M2::AUTOSARTemplates::SWComponentTemplate::Datatype::DataPrototypes
Note A VariableDataPrototype is used to contain values in an ECU application. This means that most likely a
VariableDataPrototype allocates "static" memory on the ECU. In some cases optimization strategies
might lead to a situation where the memory allocation can be avoided.
In particular, the value of a VariableDataPrototype is likely to change as the ECU on which it is used
executes.
Base ARObject, AtpFeature, AtpPrototype, AutosarDataPrototype, DataPrototype, Identifiable, Multilanguage
Referrable, Referrable
Attribute Type Mult. Kind Note
initValue ValueSpecification 0..1 aggr Specifies initial value(s) of the VariableDataPrototype

Table A.45: VariableDataPrototype

B History of Constraints and Specification Items

B.1 Constraint History of this Document according to AUTOSAR

R4.2.1

B.1.1 Added Specification Items in R4.2.1

Number Heading
[TPS_DEXT_01000] AUTOSAR diagnostics supports two kinds of data identifiers
[TPS_DEXT_01001] Definition of a fixed-sized array
[TPS_DEXT_01002] Definition of a variable-sized array
DiagnosticContributionSet is the central part of the DiagnosticEx-
[TPS_DEXT_01003]
tract
DiagnosticContributionSet defines the scope of the DiagnosticEx-
[TPS_DEXT_01004]
tract
[TPS_DEXT_01005] DiagnosticContributionSet can exist independently
The role of DiagnosticServiceTables in the context of a Diagnostic-
[TPS_DEXT_01006]
ContributionSet
[TPS_DEXT_01007] Common properties of a DiagnosticExtract
DiagnosticContributionSet defines the scope for the application of the
[TPS_DEXT_01008]
common diagnostic properties
[TPS_DEXT_01009] Limited support for the configuration of custom diagnostic services
[TPS_DEXT_01010] Configuration of custom diagnostic services
[TPS_DEXT_01011] Semantics of DiagnosticSession.id
Rationale for the modeling of the multiplicity of DiagnosticAccessPermis-
[TPS_DEXT_01012]
sion.securityLevel
Specification of sub-functions by means of attribute DiagnosticService-
[TPS_DEXT_01013]
Instance.category
5

287 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
[TPS_DEXT_01014] Possible values of the category attribute for diagnostic services
[TPS_DEXT_01015] Meaning of attributes of DiagnosticIOControl
[TPS_DEXT_01016] The capability returnControlToEcu
[TPS_DEXT_01017] Meaning of DiagnosticIOControl.dataIdentifier
[TPS_DEXT_01018] InputOutput Control does not define any sub-functions
Correspondence of category values to numerical values mentioned in the
[TPS_DEXT_01019]
ISO 14229-1
[TPS_DEXT_01020] Manufacturer-specific values for sub-functions of service EcuReset
[TPS_DEXT_01021] Semantics of DiagnosticEcuReset.customSubFunctionNumber
[TPS_DEXT_01022] ClearDiagnosticInformation does not define any sub-functions
[TPS_DEXT_01023] WriteMemoryByAddress does not define any sub-functions
[TPS_DEXT_01024] ReadMemoryByAddress does not define any sub-functions
[TPS_DEXT_01025] TransferExit does not define any sub-functions
[TPS_DEXT_01026] DataTransfer does not define any sub-functions
[TPS_DEXT_01027] RequestDownload does not define any sub-functions
[TPS_DEXT_01028] RequestUpload does not define any sub-functions
Correspondence of category values to numerical values mentioned in the
[TPS_DEXT_01029]
ISO 14229-1
Manufacturer-specific values for sub-functions of service Communication-
[TPS_DEXT_01030]
Control
[TPS_DEXT_01031] Semantics of DiagnosticComControl.customSubFunctionNumber
Impact of the DiagnosticComControlClass on the state management for
[TPS_DEXT_01032]
CommunicationClusters
[TPS_DEXT_01033] Semantics of triggers in the context of a DiagnosticResponseOnEvent
[TPS_DEXT_01034] Sub-functions of the service ReadDTCInformation
Existence of DiagnosticRoutine.stop and DiagnosticRoutine.re-
[TPS_DEXT_01035]
questResult
[TPS_DEXT_01036] Work-flow within the execution of the diagnostic service SecurityAccess
[TPS_DEXT_01037] Semantics of DiagnosticSecurityAccess.requestSeedId
Motivation for making the reference DiagnosticSecurityAccess.secu-
[TPS_DEXT_01038]
rityLevelatpSplitable
[TPS_DEXT_01039] Identification of the sub-function of DiagnosticSessionControl
[TPS_DEXT_01040] Use case where the DiagnosticExtract refers to software-components
Semantics of attribute DiagnosticServiceDataMapping.diagnostic-
[TPS_DEXT_01041]
DataElement
[TPS_DEXT_01042] Dem uses DiagnosticServiceDataMapping
[TPS_DEXT_01043] Purpose of DiagnosticServiceSwMapping
[TPS_DEXT_01044] BswServiceDependency needs to act as the target of a reference
[TPS_DEXT_01045] Supported diagnostic services
5

288 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
ECU configuration is not suitable to be exchanged between partners in an ECU
[TPS_DEXT_01046]
development project
Differences in the development processes for diagnostics at automotive OEMs
[TPS_DEXT_01047]
and ECU suppliers
[TPS_DEXT_01048] Actual algorithm for the diagnostic event debouncing
[TPS_DEXT_01049] Consistency of DiagnosticServiceSwMapping with respect to routine IDs
[TPS_DEXT_01050] Consistency of DiagnosticServiceSwMapping with respect to data IDs
[TPS_DEXT_01051] Consistency of DiagnosticServiceSwMapping with respect to data IDs
[TPS_DEXT_01052] Existence of attribute DiagnosticServiceInstance.accessPermission
[TPS_DEXT_01053] Existence of DiagnosticSecurityAccess.securityLevel
[TPS_DEXT_01054] Existence of DiagnosticDataByIdentifier.dataIdentifier
[TPS_DEXT_01055] Standardized values of DiagnosticContributionSet.category
[TPS_DEXT_01056] Applicable values for DiagnosticEcuReset.category
[TPS_DEXT_01057] Allowed values of DiagnosticComControl.category
Standardized values for DiagnosticDynamicallyDefineDataIdenti-
[TPS_DEXT_01058]
fier.category
[TPS_DEXT_01059] Applicable values for DiagnosticPeriodicRate.category
[TPS_DEXT_01060] Applicable values for DiagnosticReadDTCInformation.category
[TPS_DEXT_01061] Supported scenarios for the definition of access permission
Existence of DiagnosticServiceClass.accessPermissionValidity
[TPS_DEXT_01062]
in an incomplete model
Existence of DiagnosticServiceClass.accessPermissionValidity
[TPS_DEXT_01063]
in a complete model
[TPS_DEXT_01064] Textually formulated content attached to DiagnosticTroubleCode
Different approaches to provide semi-formal textual content attached to a Di-
[TPS_DEXT_01065]
agnosticTroubleCode
[TPS_DEXT_01066] Standardized values of DiagnosticTroubleCode.introduction.trace
[TPS_DEXT_01067] Textually formulated content attached to DiagnosticEvent
[TPS_DEXT_01068] Textual description with respect to the DiagnosticEvent
Standardized values of DiagnosticEvent.introduction.structure-
[TPS_DEXT_01069]
dReq
Description of textually semi-formal formulated pre- and post-conditions for the
[TPS_DEXT_01070]
validity of DiagnosticAccessPermission
Standardized values of DiagnosticAccessPermission.introduction.
[TPS_DEXT_01071]
structuredReq
[TPS_DEXT_01072] Purpose of attribute DiagnosticDataIdentifier.representsVin
[TPS_DEXT_01073] Diagnostic properties that are specific to an individual EcuInstance
Difference between the attributes DiagnosticComCon-
[TPS_DEXT_01074]
trol.specificChannel and DiagnosticComControl.subNodeChannel
5

289 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
standardized values for the attribute DiagnosticControlDTCSetting.
[TPS_DEXT_01075]
category
[TPS_DEXT_01076] Identification of sub-functions of diagnostic service ControlDTCSetting
[TPS_DEXT_01077] Modeling of DiagnosticRoutine
Not possible to use the attribute category for the identification of the sub-
[TPS_DEXT_01078]
function of diagnostic service RoutineControl
[TPS_DEXT_01079] Modeling of the arguments to a DiagnosticRoutine
[TPS_DEXT_01080] Diagnostic Routine needs to be started
[TPS_DEXT_01081] Modeling of DiagnosticSessionControl
[TPS_DEXT_01082] Existence of DiagnosticSessionControl.diagnosticSession
[TPS_DEXT_01083] Semantics of a DiagnosticEvent
[TPS_DEXT_01084] DiagnosticEvent can be connected to one or multiple indicators
[TPS_DEXT_01085] Semantics of DiagnosticConditionGroups
[TPS_DEXT_01086] Reference to DiagnosticOperationCycle
[TPS_DEXT_01087] Semantics of DiagnosticOperationCycle
[TPS_DEXT_01088] Semantics of DiagnosticRoutine.id
[TPS_DEXT_01089] Definition of an identifier of a DiagnosticIOControl
Diagnostic service RequestFileTransfer does not define any sub-
[TPS_DEXT_01090]
functions
ISO 14229-1 reserves values of DiagnosticTroubleCodeGroup.group-
[TPS_DEXT_03000]
Number
[TPS_DEXT_03001] Different types of conditions
[TPS_DEXT_03002] Two kind of mappings
[TPS_DEXT_03003] Semantics of DiagnosticEventToTroubleCodeUdsMapping
[TPS_DEXT_03004] DiagnosticEvent and DiagnosticDebounceAlgorithmProps
[TPS_DEXT_03005] Existence of DiagnosticEventToDebounceAlgorithmMapping
[TPS_DEXT_03006] Values of the individual DiagnosticStorageConditions
[TPS_DEXT_03007] Semantics of DiagnosticEventPortMapping
[TPS_DEXT_03008] Semantics of DiagnosticExtendedDataRecord
[TPS_DEXT_03009] Semantics of DiagnosticFreezeFrame
Combination of DiagnosticConditions to DiagnosticCondition-
[TPS_DEXT_03010]
Groups
[TPS_DEXT_03011] Clearing request for a DiagnosticEvent
[TPS_DEXT_03012] Three kinds of DTCs
[TPS_DEXT_03013] Common properties of a DTC
[TPS_DEXT_03014] Semantics of DiagnosticTroubleCodeGroup
EnableConditions have to be put into a DiagnosticEnableCondition-
[TPS_DEXT_03015]
Group
5

290 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
StorageConditions have to be put into a DiagnosticStorageCondi-
[TPS_DEXT_03016]
tionGroup
[TPS_DEXT_03017] Semantics of DiagnosticOperationCyclePortMapping
[TPS_DEXT_03018] Semantics of DiagnosticEnableConditionPortMapping
[TPS_DEXT_03019] Semantics of DiagnosticStorageConditionPortMapping
[TPS_DEXT_03020] Semantics of DiagnosticDemProvidedDataMapping
[TPS_DEXT_03021] Aging
[TPS_DEXT_03022] Different kinds of DiagnosticIndicators
Table B.1: Added Specification Items in 4.2.1

B.1.2 Added Constraints in R4.2.1

Number Heading
[constr_1324] Existence of attribute DiagnosticDataIdentifier.representsVin
Allowed attributes of SwDataDefProps for DiagnosticDataElement.sw-
[constr_1325]
DataDefProps
[constr_1326] Existence of a variable-sized array
[constr_1327] Multiplicity of DiagnosticContributionSet.ecuInstance

[constr_1328] Consistency of DiagnosticContributionSet.ecuInstance and Diagnostic-

ServiceTable.ecuInstance
Existence of concrete sub-classes of DiagnosticServiceClass in the context cre-
[constr_1329]
ated by a DiagnosticContributionSet
[constr_1330] Custom service identifier shall not overlap with standardized service identifiers
[constr_1331] Existence of DiagnosticEcuReset.customSubFunctionNumber
[constr_1332] Value range for DiagnosticEcuReset.customSubFunctionNumber
Existence of DiagnosticMemoryIdentifier.memoryLowAddress and Diag-
[constr_1333]
nosticMemoryIdentifier.memoryHighAddress
[constr_1334] Existence of DiagnosticComControl.customSubFunctionNumber
[constr_1335] Possible values for DiagnosticComControl.customSubFunctionNumber

[constr_1336] Applicable value range for DiagnosticComControlSpecificChannel.subnet-

Number
[constr_1337] Allowed value range for attribute DiagnosticComControlSubNodeChannel.
subNodeNumber
[constr_1338] Maximum number of aggregated DiagnosticReadDataByPeriodicIDClass.pe-
riodicRate
[constr_1339] Existence of DiagnosticRoutine.start
Consistency of DiagnosticServiceSwMapping with respect to synchronously
[constr_1340]
called DiagnosticRoutines
Consistency of DiagnosticServiceSwMapping with respect to asynchronously
[constr_1341]
called DiagnosticRoutines
5

291 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
[constr_1342] Possible values for DiagnosticSecurityAccess.requestSeedId
Simultaneous existence of the attributes DiagnosticServiceDataMapping.
[constr_1343] diagnosticDataElement and DiagnosticDataByIdentifier.dataIdenti-
fier
Condition for the identification of data types of attributes DiagnosticSer-
[constr_1344] viceDataMapping.mappedDataElement and DiagnosticServiceDataMap-
ping.diagnosticDataElement

[constr_1345] DiagnosticDataElement shall not (finally) be aggregated by a DiagnosticRou-

tine
[constr_1346] Allowed values of DiagnosticServiceSwMapping.serviceInstance
[constr_1347] Existence of attributes of DiagnosticServiceSwMapping
[constr_1349] Value of udsDtcValue shall be unique
[constr_1350] Value of DiagnosticTroubleCodeGroup.groupNumber shall be unique
[constr_1351] Value of DiagnosticTroubleCodeGroup.groupNumber
[constr_1352] Existence of maxNumberFreezeFrameRecords vs. freezeFrame
[constr_1353] Applicability of [constr_1352]
[constr_1354] Existence of attribute DiagnosticTroubleCodeProps.freezeFrameContent
[constr_1355] Value of recordNumber
[constr_1356] Value of recordNumber shall be unique
[constr_1357] Value of recordNumber
[constr_1358] Value of recordNumber shall be unique
Existence of attribute DiagnosticDebounceAlgorithmProps.debounceCoun-
[constr_1359]
terStorage
Usage of DiagEventDebounceMonitorInternal is not supported in the context
[constr_1360]
of DiagnosticDebounceAlgorithmProps
Number of DiagnosticEventToEnableConditionGroupMapping elements per
[constr_1361]
DiagnosticEvent
Number of DiagnosticEventToStorageConditionGroupMapping elements
[constr_1362]
per DiagnosticEvent
[constr_1365] Multiplicity of DiagnosticResponseOnEvent.event
[constr_1366] Event ID in the context of diagnostic service ResponseOnEvent shall be unique
[constr_1376] Multiplicity of reference DiagnosticTroubleCodeProps.memoryDestination
[constr_1377] Existence of reference DiagnosticTroubleCodeProps.memoryDestination
[constr_1378] Value of DiagnosticMemoryDestinationUserDefined.memoryId
[constr_1379] Existence of DiagnosticMemoryDestinationPrimary
[constr_1380] Existence of DiagnosticMemoryDestinationMirror
Table B.2: Added Constraints in R4.2.1

292 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.2 Constraint History of this Document according to AUTOSAR

R4.2.2

B.2.1 Added Traceables in R4.2.2

none

B.2.2 Changed Traceables in R4.2.2

none

B.2.3 Deleted Traceables in R4.2.2

none

B.2.4 Added Constraints in R4.2.2

Number Heading

[constr_1394] Value of DiagnosticDataElement.maxNumberOfElements depending on its ex-

istence
Table B.3: Added Constraints in R4.2.2

B.2.5 Changed Constraints in R4.2.2

none

B.2.6 Deleted Constraints in R4.2.2

none

293 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.3 Constraint History of this Document according to AUTOSAR

R4.3.0

B.3.1 Added Traceables in R4.3.0

Number Heading
Relation between a DiagnosticServiceTable and one or more Diagnos-
[TPS_DEXT_01091]
ticConnections
[TPS_DEXT_01092] Semantics of DiagnosticParameterIdentifier
[TPS_DEXT_01093] Definition of legislative freeze frame for WWWH-OBD
Semantics of meta-class DiagnosticTroubleCodeUdsToTrouble-
[TPS_DEXT_01094]
CodeObdMapping
Definition of “alias” diagnostic event for the creation of a Fim configuration in
[TPS_DEXT_01095]
the diagnostic extract
[TPS_DEXT_01096] Semantics of DiagnosticFunctionInhibitSource
Standardized value of StructuredReq.category for the modeling of Diag-
[TPS_DEXT_01097]
nosticFunctionInhibitSource
[TPS_DEXT_01098] Semantics of attribute DiagnosticFunctionInhibitSource.event
Semantics of attribute DiagnosticFunctionInhibitSource.event-
[TPS_DEXT_01099]
Group
[TPS_DEXT_01100] Consequence of the existence of DiagnosticFimAliasEventMapping
Consequence of the existence of DiagnosticFimAliasEventGroupMap-
[TPS_DEXT_01101]
ping
[TPS_DEXT_01102] Semantics of DiagnosticFimFunctionMapping
[TPS_DEXT_01103] Semantics of meta-class DiagnosticJ1939SpnMapping
Difference between DiagnosticJ1939FreezeFrame and Diagnos-
[TPS_DEXT_01104]
ticJ1939ExpandedFreezeFrame
Relation of DiagnosticJ1939Spn to DiagnosticJ1939FreezeFrame
[TPS_DEXT_01105]
and DiagnosticJ1939ExpandedFreezeFrame
[TPS_DEXT_01106] Relation of Controller Application to SPN
[TPS_DEXT_01107] Definition of service-only DTC
[TPS_DEXT_01108] Purpose of the DiagnosticJ1939SwMapping
[TPS_DEXT_01110] Standardized values of DiagnosticIumprGroup.category
[TPS_DEXT_01111] Legislative freeze frame for the OBD-II case
[TPS_DEXT_01112] Definition of a diagnostic trouble code for the implementation of WWH-OBD
[TPS_DEXT_01113] Evaluation of a DiagnosticEnvConditionFormula
[TPS_DEXT_01114] DiagnosticEnvConditionFormula that has no parts
[TPS_DEXT_01115] DiagnosticEnvConditionFormula that has one part
[TPS_DEXT_01116] DiagnosticEnvConditionFormula that has more than one part
[TPS_DEXT_01117] Semantics of DiagnosticEnvConditionFormula.nrcValue
[TPS_DEXT_01118] Semantics of DiagnosticEnvDataCondition
[TPS_DEXT_01119] Semantics of DiagnosticEnvModeCondition
5

294 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
Comparison of the value of a ModeDeclarationGroupPrototype with a
[TPS_DEXT_01120]
ModeDeclaration
[TPS_DEXT_01121] Semantics of DiagnosticFunctionIdentifier
[TPS_DEXT_01122] Indication whether a EcuInstance supports OBD
[TPS_DEXT_01124] Semantics of meta-class DiagnosticProtocol
Support for diagnostic service RequestCurrentPowertrainDiagnostic-
[TPS_DEXT_01125]
Data
[TPS_DEXT_01126] Support of OBD service RequestPowertrainFreezeFrameData
[TPS_DEXT_01127] Semantics of meta-class DiagnosticRequestEmissionRelatedDTC
[TPS_DEXT_01128] Semantics of meta-class DiagnosticClearResetEmissionRelatedInfo
Support for OBD diagnostic service RequestOnBoardMonitoringTestRe-
[TPS_DEXT_01129]
sults
[TPS_DEXT_01130] Support of OBD diagnostic service RequestControlOfOnBoardDevice
[TPS_DEXT_01131] Support for OBD diagnostic service RequestVehicleInformation
Support for OBD diagnostic service RequestEmissionRelatedDiagnos-
[TPS_DEXT_01132]
ticTroubleCodesPermanentStatus
[TPS_DEXT_01133] Support for WWH-OBD within the diagnostic extract
Definition of a DiagnosticDataElement used in the context of a DID ob-
[TPS_DEXT_01134]
tained by sender-receiver communication
Definition of a DiagnosticDataElement used in the context of a DID ob-
[TPS_DEXT_01135]
tained by client/server communication
Definition of a DiagnosticDataElement used in the context of a diagnostic
[TPS_DEXT_01136]
routine
[TPS_DEXT_01137] Applicability of DiagnosticDataIdentifier.didSize
[TPS_DEXT_01138] Applicability of DiagnosticDataIdentifier.supportInfoByte
[TPS_DEXT_01139] Semantics of the references from DiagnosticAccessPermission
Table B.4: Added Traceabless in 4.3.0

B.3.2 Changed Traceables in R4.3.0

Number Heading
[TPS_DEXT_01006] The role of DiagnosticServiceTables
[TPS_DEXT_01052] Existence of attribute DiagnosticServiceInstance.accessPermission
[TPS_DEXT_01060] Applicable values for DiagnosticReadDTCInformation.category
Difference between the attributes DiagnosticComControlClass.speci-
[TPS_DEXT_01074]
ficChannel and DiagnosticComControlClass.subNodeChannel
[TPS_DEXT_03003] Semantics of DiagnosticEventToTroubleCodeUdsMapping
Table B.5: Changed Traceables in R4.3.0

295 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.3.3 Deleted Traceables in R4.3.0

Number Heading
Standardized values for DiagnosticDynamicallyDefineDataIdenti-
[TPS_DEXT_01058]
fier.category
[TPS_DEXT_01059] Applicable values for DiagnosticPeriodicRate.category
Table B.6: Deleted Traceables in R4.3.0

B.3.4 Added Constraints in R4.3.0

Number Heading
Value of DiagnosticProtocol.serviceTable vs. DiagnosticServiceTable.
[constr_1405]
protocolKind
DiagnosticServiceTable.diagnosticConnection vs. DiagnosticProto-
[constr_1406]
col.diagnosticConnection
Existence of DiagnosticMemoryIdentifier.memoryHighAddressLabel vs.
[constr_1411]
DiagnosticMemoryIdentifier.memoryHighAddress
Existence of DiagnosticMemoryIdentifier.memoryLowAddressLabel vs.
[constr_1412]
DiagnosticMemoryIdentifier.memoryLowAddress
[constr_1419] Value of DiagnosticSecurityLevel.accessDataRecordSize

[constr_1421] Consistency of DiagnosticDynamicallyDefineDataIdentifierClass.sub-

function
[constr_1435] Debouncing in the presence of a DiagnosticEventPortMapping
[constr_1447] Restrictions for the value of DiagnosticParameterIdentifier.id
[constr_1448] Interval of DiagnosticParameterIdentifier.id
[constr_1449] PID shall only carry a fixed-length collection of data
[constr_1450] Service mapping for ODB mode 0x01 for DiagnosticParameterIdentifier
[constr_1451] Service mapping for OBD mode 0x09 for DiagnosticInfoType
[constr_1452] Service mapping for OBD mode 0x08 for DiagnosticInfoType
[constr_1453] References from DiagnosticFunctionInhibitSource
DiagnosticFimFunctionMapping shall only reference a SwcServiceDepen-
[constr_1454]
dency that aggregates FunctionInhibitionNeeds
[constr_1455] Relation of DiagnosticJ1939Node to J1939NmNode
[constr_1456] Valid interval for attribute DiagnosticTroubleCodeJ1939.fmi
[constr_1457] Service-only DTCs shall refer to a common memory section
[constr_1458] Reference to DiagnosticMemoryDestination
[constr_1459] Existence of attributes of DiagnosticTroubleCodeProps
[constr_1460] Restrictions for the value of DiagnosticInfoType.id
[constr_1461] Restrictions for the value of DiagnosticTestRoutineIdentifier.id
[constr_1462] Restrictions for the value of DiagnosticTestResult.testIdentifier.id
[constr_1464] Allowed value range of DiagnosticEnvConditionFormula.nrcValue

[constr_1465] Allowed values of compareType in the context of a DiagnosticEnvDataCondi-

tion
5

296 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading

[constr_1466] Allowed values of compareType in the context of a DiagnosticEnvModeCondi-

tion
[constr_1467] References in DiagnosticEnvModeCondition
[constr_1470] Value of DiagnosticParameter.bitOffset
[constr_1471] Existence of DiagnosticDataIdentifier.didSize
[constr_1472] Existence of DiagnosticDataIdentifier.supportInfoByte
Table B.7: Added Constraints in R4.3.0

B.3.5 Changed Constraints in R4.3.0

Number Heading
Allowed attributes of SwDataDefProps for DiagnosticDataElement.sw-
[constr_1325]
DataDefProps
[constr_1327] Multiplicity of DiagnosticEcuInstanceProps.ecuInstance

[constr_1328] Consistency of DiagnosticEcuInstanceProps.ecuInstance and Diagnos-

ticServiceTable.ecuInstance
Table B.8: Changed Constraints in R4.3.0

B.3.6 Deleted Constraints in R4.3.0

none

B.4 Constraint History of this Document according to AUTOSAR

R4.3.1

B.4.1 Added Traceables in 4.3.1

Number Heading
Values contained in DiagnosticExtract shall be taken for the derivation
[TPS_DEXT_01140]
of basic software modules
Table B.9: Added Traceables in 4.3.1

B.4.2 Changed Traceables in 4.3.1

Number Heading
[TPS_DEXT_01087] Semantics of DiagnosticOperationCycle
Table B.10: Changed Traceables in 4.3.1

297 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.4.3 Deleted Traceables in 4.3.1

Number Heading
[TPS_DEXT_01073] Diagnostic properties that are specific to an individual EcuInstance
Table B.11: Deleted Traceables in 4.3.1

B.4.4 Added Constraints in 4.3.1

Number Heading
extendedDataRecord.recordNumber shall be unique within primary fault mem-
[constr_1509]
ory
[constr_1510] extendedDataRecord.recordNumber shall be unique within mirror fault memory
extendedDataRecord.recordNumber shall be unique within user-defined fault
[constr_1511]
memory
[constr_1512] freezeFrame.recordNumber shall be unique within primary fault memory
[constr_1513] freezeFrame.recordNumber shall be unique within mirror fault memory
[constr_1514] freezeFrame.recordNumber shall be unique within user-defined fault memory
Reference from DiagnosticRoutineControl to DiagnosticAccessPermis-
[constr_1515]
sion has no meaning
Table B.12: Added Constraints in 4.3.1

B.4.5 Changed Constraints in 4.3.1

Number Heading
Allowed attributes of SwDataDefProps for DiagnosticDataElement.sw-
[constr_1325]
DataDefProps
[constr_1450] Service mapping for ODB mode 0x01 for DiagnosticParameterIdentifier
[constr_1451] Service mapping for OBD mode 0x09 for DiagnosticInfoType
Table B.13: Changed Constraints in 4.3.1

B.4.6 Deleted Constraints in 4.3.1

Number Heading
[constr_1356] Value of recordNumber shall be unique
[constr_1358] Value of recordNumber shall be unique
Table B.14: Deleted Constraints in 4.3.1

298 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.5 Constraint History of this Document according to AUTOSAR

R4.4.0

B.5.1 Added Traceables in 4.4.0

Number Heading
[TPS_DEXT_01141] Definition of a collection of test results
Standardized values for DiagnosticDemProvidedDataMapping.dat-
[TPS_DEXT_01142]
aProvider
[TPS_DEXT_01143] Definition of a custom trigger for an extended data record
[TPS_DEXT_01144] Definition of a custom trigger for a freeze frame
Semantics of meta-class DiagnosticEventToTrouble-
[TPS_DEXT_01145]
CodeJ1939Mapping
[TPS_DEXT_01146] Support for service ReadScalingDataByIdentifier (0x24)
Table B.15: Added Traceables in 4.4.0

B.5.2 Changed Traceables in 4.4.0

Number Heading
DiagnosticContributionSet defines the scope of the DiagnosticEx-
[TPS_DEXT_01004]
tract
Semantics of attribute DiagnosticServiceDataMapping.diagnostic-
[TPS_DEXT_01041]
DataElement
[TPS_DEXT_01055] Standardized values of DiagnosticContributionSet.category
[TPS_DEXT_01079] Modeling of the arguments to a DiagnosticRoutine
[TPS_DEXT_03011] Clearing request for a DiagnosticEvent
[TPS_DEXT_03020] Semantics of DiagnosticDemProvidedDataMapping
Table B.16: Changed Traceables in 4.4.0

B.5.3 Deleted Traceables in 4.4.0

Number Heading
[TPS_DEXT_01137] Applicability of DiagnosticDataIdentifier.didSize
Table B.17: Deleted Traceables in 4.4.0

B.5.4 Added Constraints in 4.4.0

Number Heading

[constr_1552] DiagnosticDataIdentifier referenced by DiagnosticDataIdentifier-

Set
[constr_1584] DiagnosticDataElement shall not be used more than once in I/O Control in-
stance
5

299 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
[constr_1590] DiagnosticEvent referenced in the role masterEvent or slaveEvent

[constr_1591] DiagnosticEvent referenced as slaveEvent shall not be reported by diagnostic

monitor
Reference from DiagnosticRoutineControl to DiagnosticAccessPermis-
[constr_1612]
sion has no meaning
[constr_1616] Existence of attribute DiagnosticExtendedDataRecord.customTrigger
[constr_1617] Existence of attribute DiagnosticFreezeFrame.customTrigger
Restriction on DiagnosticReadScalingDataByIdentifier.dataIdenti-
[constr_1623]
fier
[constr_1624] Existence of DiagnosticDataElement.scalingInfoSize
Existence of DiagnosticResponseOnEvent.event vs. DiagnosticRespon-
[constr_1633]
seOnEvent.responseOnEventAction
Table B.18: Added Constraints in 4.4.0

B.5.5 Changed Constraints in 4.4.0

Number Heading
Allowed attributes of SwDataDefProps for DiagnosticDataElement.sw-
[constr_1325]
DataDefProps

[constr_1328] Consistency of DiagnosticEcuInstanceProps.ecuInstance and Diagnos-

ticServiceTable.ecuInstance
Table B.19: Changed Constraints in 4.4.0

B.5.6 Deleted Constraints in 4.4.0

Number Heading
[constr_1471] Existence of DiagnosticDataIdentifier.didSize
Reference from DiagnosticRoutineControl to DiagnosticAccessPermis-
[constr_1515]
sion has no meaning
Table B.20: Deleted Constraints in 4.4.0

300 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

B.6 Constraint History of this Document according to AUTOSAR

R19-11

B.6.1 Added Traceables in 19-11

Number Heading
[TPS_DEXT_01147] Support for custom service instance
[TPS_DEXT_01148] Standardized values of DiagnosticIumprGroup.category
Standardized values of DiagnosticIumprDenominatorGroup.cate-
[TPS_DEXT_01149]
gory
[TPS_DEXT_01150] Semantics of meta-class DiagnosticControlEnableMaskBit
Table B.21: Added Traceables in 19-11

B.6.2 Changed Traceables in 19-11

Number Heading
[TPS_DEXT_01060] Applicable values for DiagnosticReadDTCInformation.category
Definition of a DiagnosticDataElement used in the context of a DID ob-
[TPS_DEXT_01134]
tained by sender-receiver communication
Definition of a DiagnosticDataElement used in the context of a DID ob-
[TPS_DEXT_01135]
tained by client/server communication
Definition of a DiagnosticDataElement used in the context of a diagnostic
[TPS_DEXT_01136]
routine
Table B.22: Changed Traceables in 19-11

B.6.3 Deleted Traceables in 19-11

Number Heading
[TPS_DEXT_01009] Limited support for the configuration of custom diagnostic services
[TPS_DEXT_01010] Configuration of custom diagnostic services
[TPS_DEXT_01110] Standardized values of DiagnosticIumprGroup.category
Table B.23: Deleted Traceables in 19-11

B.6.4 Added Constraints in 19-11

Number Heading
[constr_1711] Restriction of applicability of attribute typeOfFreezeFrameRecordNumeration
[constr_1721] DiagnosticControlEnableMaskBit.bitNumber shall be unique
Relation between reference DiagnosticIOControl.dataIdentifier and at-
[constr_1722]
tribute DiagnosticIOControl.controlEnableMaskBit
5

301 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
Applicability of attribute DiagnosticMemoryDestination.dtcStatusAvail-
[constr_1725]
abilityMask
Table B.24: Added Constraints in 19-11

B.6.5 Changed Constraints in 19-11

Number Heading
Condition for the identification of data types of attributes DiagnosticService-
[constr_1344]
DataMapping.mappedDataElement
[constr_1349] Value of udsDtcValue shall be unique

[constr_1354] Existence of attribute DiagnosticTroubleCodeProps.snapshotRecordCon-

tent
[constr_1459] Existence of attributes of DiagnosticTroubleCodeProps
Table B.25: Changed Constraints in 19-11

B.6.6 Deleted Constraints in 19-11

none

B.7 Constraint History of this Document according to AUTOSAR

R20-11

B.7.1 Added Traceables in R20-11

Number Heading
Semantics of attribute DiagnosticEvent.associatedEventIdentifi-
[TPS_DEXT_01151]
cation
Semantics of meta-class DiagnosticSecurityEventReporting-
[TPS_DEXT_01152]
ModeMapping
[TPS_DEXT_01153] Semantics of meta-class DiagnosticEventToSecurityEventMapping
Table B.26: Added Traceables in R20-11

B.7.2 Changed Traceables in R20-11

Number Heading
Semantics of attribute DiagnosticServiceDataMapping.diagnostic-
[TPS_DEXT_01041]
DataElement
5

302 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
Standardized values for DiagnosticDemProvidedDataMapping.dat-
[TPS_DEXT_01142]
aProvider
Table B.27: Changed Traceables in R20-11

B.7.3 Deleted Traceables in R20-11

Number Heading
[TPS_DEXT_01052] Existence of attribute DiagnosticServiceInstance.accessPermission
[TPS_DEXT_01061] Supported scenarios for the definition of access permission
Existence of DiagnosticServiceClass.accessPermissionValidity
[TPS_DEXT_01062]
in an incomplete model
Existence of DiagnosticServiceClass.accessPermissionValidity
[TPS_DEXT_01063]
in a complete model
[TPS_DEXT_01076] Identification of sub-functions of diagnostic service ControlDTCSetting
Table B.28: Deleted Traceables in R20-11

B.7.4 Added Constraints in R20-11

Number Heading
[constr_1745] Indirect reference to DiagnosticCommonElement
[constr_1749] Existence of DiagnosticInfoType.dataElement
[constr_1750] Existence of attribute DiagnosticParameterIdentifier.pidSize
[constr_1752] Existence of references owned by DiagnosticEnableConditionPortMapping
Existence of references owned by DiagnosticStorageConditionPortMap-
[constr_1753]
ping
[constr_1756] Existence of attributes DiagnosticExtendedDataRecord.trigger and update
[constr_1757] Existence of attribute DiagnosticTroubleCodeUds.udsDtcValue
[constr_1758] Existence of attribute DiagnosticTroubleCodeObd.obdDTCValue
[constr_1759] Existence of references owned by DiagnosticOperationCyclePortMapping
[constr_1760] Existence of DiagnosticExtendedDataRecord.recordElement
[constr_1761] Existence of attribute DiagnosticConnectedIndicator.healingCycle
[constr_1762] Existence of references owned by DiagnosticEventPortMapping
[constr_1763] Existence of attribute DiagnosticPeriodicRate.periodicRateCategory
[constr_1766] Existence of DiagEventDebounceCounterBased.counterJumpDownValue
[constr_1767] Existence of DiagEventDebounceCounterBased.counterJumpUpValue
[constr_1768] Existence of attribute DiagnosticEvent.associatedEventIdentification

[constr_1772] Unique DiagnosticSession and DiagnosticSecurityLevel for diagnostic

routines that have the same identifier
[constr_1780] Existence of attribute DiagnosticTroubleCodeJ1939.fmi
5

303 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
[constr_1781] Existence of attribute DiagnosticTroubleCodeJ1939.spn
[constr_1782] Usage of internal data elements only for extended data records
[constr_1790] Existence of attribute DiagnosticParameter.bitOffset
[constr_1791] Existence of attribute DiagnosticParameter.dataElement
[constr_1792] Existence of DiagnosticDataIdentifier.dataElement
[constr_1793] Existence of attribute DiagnosticAbstractDataIdentifier.id
[constr_1794] Existence of attribute DiagnosticProtocol.priority
[constr_1795] Existence of attribute DiagnosticProtocol.protocolKind
[constr_1796] Existence of attribute DiagnosticServiceTable.serviceInstance
[constr_1797] Existence of attribute DiagnosticServiceTable.protocolKind
[constr_1798] Existence of DiagnosticServiceInstance.serviceClass
[constr_1799] Existence of DiagnosticEnvironmentalCondition.formula
[constr_1800] Existence of DiagnosticEnvConditionFormula.op
[constr_1801] Existence of DiagnosticEnvCompareCondition.compareType
[constr_1802] Existence of DiagnosticEnvDataCondition.compareValue
[constr_1803] Existence of DiagnosticEnvDataCondition.dataElement
[constr_1804] Existence of DiagnosticEnvModeCondition.modeElement
[constr_1805] Existence of DiagnosticEnvSwcModeElement.mode
[constr_1806] Existence of DiagnosticEnvBswModeElement.mode
[constr_1807] Existence of reference DiagnosticDataByIdentifier.dataIdentifier

[constr_1808] Existence of reference DiagnosticDynamicallyDefineDataIdentifier.

dataIdentifier
[constr_1810] Existence of aggregation DiagnosticReadDataByPeriodicIDClass.period-
icRate
[constr_1811] Existence of attribute DiagnosticReadDataByPeriodicIDClass.maxPeriod-
icDidToRead
[constr_1812] Existence of attribute DiagnosticReadDataByPeriodicIDClass.scheduler-
MaxNumber
[constr_1813] Existence of reference DiagnosticEventWindow.eventWindowTime
[constr_1814] Existence of reference DiagnosticEventWindow.storageStateEvaluation
[constr_1815] Existence of attribute DiagnosticRoutine.id
[constr_1816] Existence of attribute DiagnosticSecurityAccess.requestSeedId
[constr_1817] Existence of attribute DiagnosticSecurityAccess.securityLevel
[constr_1818] Existence of reference DiagnosticSessionControl.diagnosticSession
[constr_1819] Existence of attribute DiagnosticParameterIdentifier.id
[constr_1820] Existence of reference DiagnosticRequestCurrentPowertrainData.pid

[constr_1821] Existence of reference DiagnosticRequestPowertrainFreezeFrameData.

freezeFrame
[constr_1822] Existence of reference DiagnosticRequestControlOfOnBoardDevice.
testId
5

304 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
[constr_1823] Existence of attribute DiagnosticTestRoutineIdentifier.id

[constr_1824] Existence of attribute DiagnosticTestRoutineIdentifier.requestData-

Size
[constr_1825] Existence of attribute DiagnosticTestRoutineIdentifier.responseData-
Size
[constr_1826] Existence of reference DiagnosticRequestVehicleInfo.infoType
[constr_1827] Existence of attribute DiagnosticInfoType.id
[constr_1828] Existence of referenced from DiagnosticServiceDataMapping
[constr_1829] Existence of reference DiagnosticConnectedIndicator.indicator
[constr_1830] Existence of DiagnosticTroubleCodeGroup.groupNumber
[constr_1831] Existence of DiagnosticTroubleCodeProps.priority
[constr_1832] Existence of DiagnosticExtendedDataRecord.recordNumber
[constr_1833] Existence of DiagnosticFreezeFrame.trigger
[constr_1834] Existence of DiagnosticCondition.initValue

[constr_1835] Existence of DiagEventDebounceCounterBased.counterDecrementStep-

Size
[constr_1836] Existence of DiagEventDebounceCounterBased.counterIncrementStep-
Size
[constr_1837] Existence of DiagEventDebounceCounterBased.counterFailedThreshold
[constr_1838] Existence of DiagEventDebounceCounterBased.counterPassedThreshold
[constr_1839] Existence of attribute DiagEventDebounceTimeBased.timeFailedThreshold
[constr_1840] Existence of attribute DiagEventDebounceTimeBased.timePassedThreshold
[constr_1841] Existence of DiagnosticEnableConditionGroup.enableCondition
[constr_1842] Existence of DiagnosticStorageConditionGroup.storageCondition
[constr_1843] Existence of reference DiagnosticEventPortMapping.diagnosticEvent
Existence of reference DiagnosticOperationCyclePortMapping.opera-
[constr_1844]
tionCycle

[constr_1845] Existence of reference DiagnosticEnableConditionPortMapping.enable-

Condition
Existence of reference DiagnosticStorageConditionPortMapping.diag-
[constr_1846]
nosticStorageCondition
[constr_1847] Existence of reference DiagnosticDemProvidedDataMapping.dataElement
[constr_1848] Existence of attribute DiagnosticAging.agingCycle
[constr_1849] Existence of attribute DiagnosticAging.threshold
[constr_1850] Existence of aggregation DiagnosticTestResult.testIdentifier
[constr_1851] Existence of reference DiagnosticTestResult.monitoredIdentifier
[constr_1852] Existence of attribute DiagnosticEcuInstanceProps.obdSupport
[constr_1853] Existence of attribute DiagnosticIumprGroup.iumprGroupIdentifier
[constr_1854] Existence of attribute DiagnosticIumprGroupIdentifier.groupId

[constr_1855] Existence of attribute DiagnosticFunctionIdentifierInhibit.inhibi-

tionMask
5

305 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Number Heading
[constr_1856] Existence of attribute DiagnosticJ1939Spn.spn
Existence of the reference DiagnosticEventToTroubleCodeJ1939Mapping.
[constr_1857]
diagnosticEvent

[constr_1858] Existence of the attribute DiagnosticEventToTroubleCodeJ1939Mapping.

troubleCodeJ1939
[constr_1859] Usage of DiagnosticRecordTriggerEnum.testFailedThisOperationCy-
cle
Existence of reference in the role DiagnosticSecurityEventReporting-
[constr_10024]
ModeMapping.dataElement
Existence of reference in the role DiagnosticSecurityEventReporting-
[constr_10025]
ModeMapping.securityEvent
Existence of reference in the role DiagnosticEventToSecurityEventMapping.
[constr_10026]
diagnosticEvent
Existence of reference in the role DiagnosticEventToSecurityEventMapping.
[constr_10027]
securityEventProps
Table B.29: Added Constraints in R20-11

B.7.5 Changed Constraints in R20-11

none

B.7.6 Deleted Constraints in R20-11

Number Heading
Usage of DiagEventDebounceMonitorInternal is not supported in the context
[constr_1360]
of DiagnosticDebounceAlgorithmProps
Table B.30: Deleted Constraints in R20-11

C Glossary
Artifact This is a Work Product Definition that provides a description and definition for
tangible work product types. Artifacts may be composed of other artifacts ([23]).
At a high level, an artifact is represented as a single conceptual file.
AUTOSAR Tool This is a software tool which supports one or more tasks defined as
AUTOSAR tasks in the methodology. Depending on the supported tasks, an
AUTOSAR tool can act as an authoring tool, a converter tool, a processor tool or
as a combination of those (see separate definitions).
AUTOSAR Authoring Tool An AUTOSAR Tool used to create and modify AUTOSAR
XML Descriptions. Example: System Description Editor.

306 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

AUTOSAR Converter Tool An AUTOSAR Tool used to create AUTOSAR XML files by
converting information from other AUTOSAR XML files. Example: ECU Flattener
AUTOSAR Definition This is the definition of parameters which can have values. One
could say that the parameter values are Instances of the definitions. But in the
meta model hierarchy of AUTOSAR, definitions are also instances of the meta
model and therefore considered as a description. Examples for AUTOSAR def-
initions are: EcucParameterDef, PostBuildVariantCriterion, SwSys-
temconst.
AUTOSAR XML Description In AUTOSAR this means "filled Template". In fact an
AUTOSAR XML description is the XML representation of an AUTOSAR model.
The AUTOSAR XML description can consist of several files. Each individual file
represents an AUTOSAR partial model and shall validate successfully against the
AUTOSAR XML schema.
AUTOSAR Meta-Model This is an UML2.0 model that defines the language for de-
scribing AUTOSAR systems. The AUTOSAR meta-model is an UML represen-
tation of the AUTOSAR templates. UML2.0 class diagrams are used to describe
the attributes and their interrelationships. Stereotypes, UML tags and OCL ex-
pressions (object constraint language) are used for defining specific semantics
and constraints.
AUTOSAR Meta-Model Tool The AUTOSAR Meta-Model Tool is the tool that gener-
ates different views (class tables, list of constraints, diagrams, XML Schema etc.)
on the AUTOSAR meta-model.
AUTOSAR Model This is a representation of an AUTOSAR product. The AUTOSAR
model represents aspects suitable to the intended use according to the
AUTOSAR methodology.
Strictly speaking, this is an instance of the AUTOSAR meta-model. The infor-
mation contained in the AUTOSAR model can be anything that is representable
according to the AUTOSAR meta-model.
AUTOSAR Partial Model In AUTOSAR, the possible partitioning of models is marked
in the meta-model by atpSplitable. One partial model is represented in
an AUTOSAR XML description by one file. The partial model does not need to
fulfill all semantic constraints applicable to an AUTOSAR model.
AUTOSAR Processor Tool An AUTOSAR Tool used to create non-AUTOSAR files by
processing information from AUTOSAR XML files. Example: RTE Generator
AUTOSAR Specification Element An AUTOSAR Specification Element is a named
element that is part of an AUTOSAR specification. Examples: requirement, con-
straint, specification item, class or attribute in the meta model, methodology, de-
liverable, methodology activity, model element, bsw module etc.
AUTOSAR Template The term "Template" is used in AUTOSAR to describe the for-
mat different kinds of descriptions. The term template comes from the idea, that

307 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

AUTOSAR defines a kind of form which shall be filled out in order to describe a
model. The filled form is then called the description.
In fact the AUTOSAR templates are now defined as a meta-model.
AUTOSAR Validation Tool A specialized AUTOSAR Tool which is able to check an
AUTOSAR model against the rules defined by a profile.
AUTOSAR XML Schema This is a W3C XML schema that defines the language for
exchanging AUTOSAR models. This Schema is derived from the AUTOSAR
meta-model. The AUTOSAR XML Schema defines the AUTOSAR data exchange
format.
Blueprint This is a model from which other models can be derived by copy and re-
finement. Note that in contrast to meta model resp. types, this process is not an
instantiation.
Instance Generally this is a particular exemplar of a model or of a type.
Life Cycle Life Cycle is the course of development/evolutionary stages of a model
element during its life time.
Meta-Model This defines the building blocks of a model. In that sense, a Meta-Model
represents the language for building models.
Meta-Data This includes pertinent information about data, including information about
the authorship, versioning, access-rights, timestamps etc.
Model A Model is an simplified representation of reality. The model represents the
aspects suitable for an intended purpose.
Partial Model This is a part of a model which is intended to be persisted in one par-
ticular artifact.
Pattern in GST This is an approach to simplify the definition of the meta model by ap-
plying a model transformation. This transformation creates an enhanced model
out of an annotated model.
Profile Authoring Support Data Data that is used for efficient authoring of a profile.
E.g. list of referable constraints, meta-classes, meta-attributes or other reusable
model assets (blueprints)
Profile Authoring Tool A specialized AUTOSAR Tool which focuses on the authoring
of profiles for data exchange points. It e.g. provides support for the creation of
profiles from scratch, modification of existing profiles or composition of existing
profiles.
Profile Compatibility Checker Tool A specialized AUTOSAR Tool which focuses on
checking the compatibility of profiles for data exchange. Note that this compat-
ibility check includes manual compatibility checks by engineers and automated
assistance using more formal algorithms.

308 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Profile Consistency Checker Tool A specialized AUTOSAR Tool which focuses on

checking the consistency of profiles.
Property A property is a structural feature of an object. As an example a “connector”
has the properties “receive port” and “send port”
Properties are made variant by the atpVariation.
Prototype This is the implementation of a role of a type within the definition of another
type. In other words a type may contain Prototypes that in turn are typed by
"Types". Each one of these prototypes becomes an instance when this type is
instantiated.
Type A type provides features that can appear in various roles of this type.
Value This is a particular value assigned to a “Definition”.
Variability Variability of a system is its quality to describe a set of variants. These
variants are characterized by variant specific property settings and / or selections.
As an example, such a system property selection manifests itself in a particular
“receive port” for a connection.
This is implemented using the atpVariation.
Variant A system variant is a concrete realization of a system, so that all its proper-
ties have been set respectively selected. The software system has no variability
anymore with respect to the binding time.
This is implemented using EvaluatedVariantSet.
Variation Binding A variant is the result of a variation binding process that resolves
the variability of the system by assigning particular values/selections to all the
system’s properties.
This is implemented by VariationPoint.
Variation Binding Time The variation binding time determines the step in the method-
ology at which the variability given by a set of variable properties is resolved.
This is implemented by vh.LatestBindingtime at the related properties.
Variation Definition Time The variation definition time determines the step in the
methodology at which the variation points are defined.
Variation Point A variation point indicates that a property is subject to variation. Fur-
thermore, it is associated with a condition and a binding time which define the
system context for the selection / setting of a concrete variant.
This is implemented by VariationPoint.

309 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

D Modeling of InstanceRef

D.1 Introduction
The existence of so-called InstanceRefs is a direct consequence to the usage of the
type-prototype pattern for modeling within AUTOSAR. When referencing a pro-
totype it is also necessary to include a reference to the prototypes typed by their
corresponding types that in turn aggregate further prototypes to set up the context.
In other words, InstanceRefs are representing structured references that, on the
one hand, consist of references to context prototypes (indicated by a subsetting or
redefinition of atpContextElement) and finally a reference to the applicable target
prototype (indicated by a redefinition of atpTarget).
Note that it is not uncommon to have more than a single context in the modeling of
particular InstanceRefs.
For the reader of specifications, the modeling of InstanceRefs manifests as a UML
dependency stereotyped instanceRef drawn from one meta-class to another.
This is a simplified indication that the source of the dependency implements an In-
stanceRef to the meta-class at the target of the dependency. Again, in most cases
this is everything a reader needs to understand in order to figure out the modeling.
The formal modeling of InstanceRefs is done by creating subclasses of the abstract
meta-class AtpInstanceRef.
Wherever a more detailed understanding of the modeling is advised in the context of
the specific chapter of this document, the modeling of a specific subclasses of AtpIn-
stanceRef is explained directly in the context of the corresponding chapter.
In all other cases, a deeper understanding of the modeling of particular subclasses of
AtpInstanceRefs can be obtained from reading this chapter.
Class tables included in this chapter are not fully filled out in the sense that most of the
notes inside the class tables are missing.
The primary purpose of these class tables is to provide information about the in-
tended order in which InstanceRefs are serialized in M1 AUTOSAR models.
In particular, the information about the order in serialized M1 models can be obtained
from the value of the tag xml.sequenceOffset of each attribute of an InstanceRef
meta-class.
For more information about the general concept of modeling AtpInstanceRef (e.g.
the conceptual background of redefining or subsetting an association from a subclass
of AtpInstanceRef to other meta-classes) please refer to [24].

310 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

D.2 Modeling
Class DataPrototypeInSystemInstanceRef
Package M2::AUTOSARTemplates::DiagnosticExtract::InstanceRefs
Note
Base ARObject, AtpInstanceRef
Attribute Type Mult. Kind Note
base System 0..1 ref This represents the base of the InstanceRef
Stereotypes: atpDerived
Tags:xml.sequenceOffset=10
context SwComponent * ref Tags:xml.sequenceOffset=30
Component Prototype
contextData ApplicationComposite * ref Tags:xml.sequenceOffset=50
Prototype ElementDataPrototype
(ordered)
contextPort PortPrototype 0..1 ref This represents the PortPrototype that is contained in the
InstanceRef.
Tags:xml.sequenceOffset=40
contextRoot RootSwComposition 0..1 ref Tags:xml.sequenceOffset=20
Composition Prototype
targetData DataPrototype 0..1 ref This represents the target of the InstanceRef
Prototype
Tags:xml.sequenceOffset=60

Table D.1: DataPrototypeInSystemInstanceRef

311 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

ARElement
AtpStructureElement
System

+ containerIPduHeaderByteOrder: ByteOrderEnum [0..1]

+ ecuExtractVersion: RevisionLabelString [0..1]
+ pncVectorLength: PositiveInteger [0..1]
+ pncVectorOffset: PositiveInteger [0..1]
+ systemVersion: RevisionLabelString

+base 0..1
{redefines atpBase}

«atpVariation,atpSplitable»
+rootSoftwareComposition 0..1
AtpPrototype
CompositionSwComponentType
Identifiable +softwareComposition
«isOfType»
«atpDerived» RootSwCompositionPrototype
1
{redefines
+contextRootComposition 0..1 atpType}
{redefines
atpContextElement}

«atpVariation,atpSplitable»
AtpInstanceRef
DataPrototypeInSystemInstanceRef

0..* +component

AtpPrototype
+contextComponent
SwComponentPrototype

0..*
{subsets
atpContextElement}

«isOfType»
0..1
{redefines
+targetDataPrototype atpContextElement} 0..1
{redefines 0..1
AtpPrototype +contextPort atpContextElement} {redefines atpType} +type
DataPrototype ARElement
AtpBlueprintable
AtpPrototype AtpBlueprint
+port AtpBlueprintable
PortPrototype AtpType
0..* 0..*«atpVariation,atpSplitable» SwComponentType
{ordered,
subsets
+contextDataPrototype atpContextElement}

ApplicationCompositeElementDataPrototype

Figure D.1: Modeling of DataPrototypeInSystemInstanceRef

DiagnosticMapping 0..1 AtpPrototype

«instanceRef»
DiagnosticServiceDataMapping DataPrototype
+mappedDataElement

+targetDataPrototype 0..1
{redefines atpContextElement}

+mappedDataElement 0..1

AtpInstanceRef
DataPrototypeInSystemInstanceRef

Figure D.2: Modeling of DiagnosticServiceDataMapping

312 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class SwcServiceDependencyInSystemInstanceRef
Package M2::AUTOSARTemplates::DiagnosticExtract::InstanceRefs
Note
Base ARObject, AtpInstanceRef
Attribute Type Mult. Kind Note
contextRootSw RootSwComposition 0..1 ref
Composition Prototype
contextSw SwComponent * ref
Component Prototype
Prototype
targetSwc SwcService 0..1 ref
Service Dependency
Dependency

Table D.2: SwcServiceDependencyInSystemInstanceRef

AtpInstanceRef ARElement
SwcServiceDependencyInSystemInstanceRef AtpStructureElement
System

+ containerIPduHeaderByteOrder: ByteOrderEnum [0..1]

+ ecuExtractVersion: RevisionLabelString [0..1]
+ pncVectorLength: PositiveInteger [0..1]
+ pncVectorOffset: PositiveInteger [0..1]
+ systemVersion: RevisionLabelString

«atpVariation,atpSplitable»

+rootSoftwareComposition 0..1
AtpPrototype
+contextRootSwComposition Identifiable
RootSwCompositionPrototype
0..1
{subsets
atpContextElement}
ARElement
AtpBlueprint
AtpBlueprintable
AtpType
«isOfType» SwComponentType

+type 0..1
1 {redefines atpType}
+softwareComposition {redefines atpType}

CompositionSwComponentType

«isOfType»

«atpVariation,atpSplitable»

+component 0..*

+contextSwComponentPrototype AtpPrototype
AtomicSwComponentType
SwComponentPrototype
0..*
{subsets
atpContextElement}

0..1
«atpVariation,atpSplitable»
{redefines
+targetSwcServiceDependency atpTarget}
+internalBehavior 0..1
AtpStructureElement
InternalBehavior
Identifiable
+serviceDependency SwcInternalBehavior
ServiceDependency
SwcServiceDependency 0..* «atpVariation,atpSplitable» + handleTerminationAndRestart: HandleTerminationAndRestartEnum [0..1]
+ supportsMultipleInstantiation: Boolean [0..1]

Figure D.3: Modeling of SwcServiceDependencyInSystemInstanceRef

313 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

Class PModeInSystemInstanceRef
Package M2::AUTOSARTemplates::DiagnosticExtract::InstanceRefs
Note
Base ARObject, AtpInstanceRef
Attribute Type Mult. Kind Note
base System 0..1 ref Stereotypes: atpDerived
Tags:xml.sequenceOffset=10
context SwComponent * ref Tags:xml.sequenceOffset=30
Component Prototype
context RootSwComposition 0..1 ref Tags:xml.sequenceOffset=20
Composition Prototype
contextMode ModeDeclarationGroup 0..1 ref Tags:xml.sequenceOffset=50
Declaration Prototype
Group
contextPPort AbstractProvidedPort 0..1 ref Tags:xml.sequenceOffset=40
Prototype
targetMode ModeDeclaration 0..1 ref Tags:xml.sequenceOffset=60

Table D.3: PModeInSystemInstanceRef

314 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

DiagnosticEnvModeElement
DiagnosticEnvSwcModeElement

«instanceRef»

+mode 0..1 +mode 0..1

AtpStructureElement AtpInstanceRef
Identifiable PModeInSystemInstanceRef
ModeDeclaration
0..1+targetMode
+ value: PositiveInteger [0..1] {redefines atpTarget}

AtpPrototype +contextModeDeclarationGroup
ModeDeclarationGroupPrototype
0..1
+ swCalibrationAccess: SwCalibrationAccessEnum [0..1]
{subsets atpContextElement}

PortPrototype
AbstractProvidedPortPrototype +contextPPort

0..1
{subsets atpContextElement}

AtpPrototype
+contextComponent
SwComponentPrototype

0..*
{subsets atpContextElement}

AtpPrototype
Identifiable +contextComposition
RootSwCompositionPrototype
0..1
{subsets atpContextElement}

+rootSoftwareComposition 0..1

«atpVariation,atpSplitable»

ARElement
AtpStructureElement
System
+base «atpDerived»
+ containerIPduHeaderByteOrder: ByteOrderEnum [0..1]
+ ecuExtractVersion: RevisionLabelString [0..1] 0..1
+ pncVectorLength: PositiveInteger [0..1] {redefines atpBase}
+ pncVectorOffset: PositiveInteger [0..1]
+ systemVersion: RevisionLabelString

Figure D.4: Formal modeling of the comparison of a ModeDeclarationGroupProto-

type with a ModeDeclaration

315 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

E Upstream Mapping

E.1 Introduction
This chapter describes the mapping of the ECU Configuration parameters (M1 model)
onto the meta-classes and attributes of the AUTOSAR upstream templates (System
Template, SW Component Template and ECU Resource Template).
The relationships between upstream templates and ECU Configuration are described
in order to answer typical questions like:
• How shall a supplier use the information in a System Description in order to fulfill
the needs defined by the systems engineer?
• How is a tool vendor supposed to generate an ECU Configuration Description out
of ECU Extract of System Description?
Please note that the tables contain the following columns:
bsw module: Name of BSW module
bsw context: Reference to parameter container
bsw type: Type of parameter
bsw param: Name of the BSW parameter
bsw desc: Description from the configuration document
m2 template: System Template, SW Component Template, ECU Resource Template
m2 param: Name of the upstream template parameter
m2 description: Description from the upstream template definition
mapping rule: Textual description on how to transform between M2 and BSW do-
mains
mapping type:
• local: no mapping needed since parameter local to BSW
• partial: some data can be automatically mapped but not all
• full: all data can be automatically mapped

316 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

E.2 Dcm
BSW Module BSW Context
Dcm Dcm/DcmConfigSet/DcmDsd
BSW Parameter BSW Type
DcmDsdServiceTable ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (DSD parameters) for a Service Identifier Table.
Note: It is allowed to add OBD services to a DcmDsdServiceTable related to a UDS Protocol. But it is not allowed to add UDS
services to a DcmDsdServiceTable related to an OBD Protocol.
Template Description
This meta-class represents a model of a diagnostic service table, i.e. the UDS services applicable for a given ECU.
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticServiceTable
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00732]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService
BSW Parameter BSW Type
DcmDsdSidTabSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Security Level in which the service is allowed to be executed. Multiple references are allowed for a service.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Service Security Access levels."
If there is no reference configured, no service security verification shall be performed.
Template Description
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00733]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService
BSW Parameter BSW Type
DcmDsdSidTabServiceId ECUC-INTEGER-PARAM-DEF
BSW Description
Identifier of the service.
The possible service identifiers are defined in ISO 14229-1 and ISO 15031-5.
Template Description
This meta-class provides the ability to define common properties that are shared among all instances of sub-classes of
DiagnosticServiceInstance.
5

317 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommonService::DiagnosticServiceClass
Mapping Rule Mapping Type
Service identifiers of the used DiagnosticServiceClass full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00735]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService
BSW Parameter BSW Type
DcmDsdSidTabSessionLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Session Level in which the service is allowed to be executed. Multiple references are allowed for a service.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Diagnostic Session".
If there is no reference configured, no diagnostic session verification shall be performed.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00734]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService
BSW Parameter BSW Type
DcmDsdSidTabSubfuncAvail ECUC-BOOLEAN-PARAM-DEF
BSW Description
Information about whether the service has subfunctions or not. This parameter is used for the handling of the "suppressPos
RspMsgIndicationBit" as defined in ISO 14229-1, which can be used as a reference for the configuration.
true - service has subfunctions, suppressPosRspMsgIndicationBit is available
false - service has no subfunctions, suppressPosRspMsgIndicationBit is not available
Template Description
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
GenericStructure::GeneralTemplateClasses::Identifiable::Identifiable.category
Mapping Rule Mapping Type
Stanadardized sub-functions of diagnostic services are mainly identified by the category. There are full
further specific attributes in the meta-model that allow for handling custom subfunctions,
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00737]

318 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService/DcmDsdSubService
BSW Parameter BSW Type
DcmDsdSubServiceFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Callback function of the ECU Supplier specific component for the particular service. The function’s prototype is as described
for <Module>_<DiagnosticService>_<SubService>.
If this parameter is not configured, the subservice is handled Dcm-internally.
Template Description
This attribute shall be used to define a custom sub-function number if none of the standardized values of category shall be
used.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControl.customSubFunctionNumber
Mapping Rule Mapping Type
The existence of a custom subfunction number shall trigger the creation of a custom processor. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00942]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService/DcmDsdSubService
BSW Parameter BSW Type
DcmDsdSubServiceId ECUC-INTEGER-PARAM-DEF
BSW Description
Identifier of the subservice.
The possible subservice identifiers are defined in ISO 14229-1 and ISO 15031-5.
Template Description
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
GenericStructure::GeneralTemplateClasses::Identifiable::Identifiable.category
Mapping Rule Mapping Type
Numerical values of diagnostic service according to ISO 14229 correspond to values of Diagnostic partial
ServiceInstance.category.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00803]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService/DcmDsdSubService
BSW Parameter BSW Type
DcmDsdSubServiceSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Security Level in which the subservice is allowed to be executed. Multiple references are allowed for a
subservice.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Service Security Access levels."
If there is no reference configured, no subservice security verification shall be performed.
Template Description
5

319 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00812]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceTable/DcmDsdService/DcmDsdSubService
BSW Parameter BSW Type
DcmDsdSubServiceSessionLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Session Level in which the subservice is allowed to be executed. Multiple references are allowed for a
subservice.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Diagnostic Session".
If there is no reference configured, no diagnostic session verification shall be performed.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00804]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslDiagResp
BSW Parameter BSW Type
DcmDslDiagRespMaxNumRespPend ECUC-INTEGER-PARAM-DEF
BSW Description
Maximum number of negative responses with response code 0x78 (requestCorrectlyReceivedResponsePending) allowed for
a request. If Dcm reaches this limit, an automatic 0x10 (generalReject) final response will be trasmitted and the service
processing will be cancelled. Value 0x00 means that no NRC 0x78 response will be transmitted.
Template Description
Maximum number of negative responses with response code 0x78 (requestCorrectlyReceived-ResponsePending) allowed
per request. DCM will send a negative response with response code 0x10 (generalReject), in case the limit value gets
reached. Value 0xFF means that no limit number of NRC 0x78 response apply.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.
maxNumberOfRequestCorrectlyReceivedResponsePending
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00693]

320 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslDiagResp
BSW Parameter BSW Type
DcmDslDiagRespOnSecondDeclinedRequest ECUC-BOOLEAN-PARAM-DEF
BSW Description
Defines the reaction upon a second request (ClientB) that can not be processed (e.g. due to priority assessment).
TRUE: when the second request (Client B) can not be processed, it shall be answered with NRC21 BusyRepeatRequest.
FALSE: when the second request (Client B) can not be processed, it shall not be responded.
Template Description
Defines the reaction upon a second request (ClientB) that can not be processed (e.g. due to priority assessment).
TRUE: when the second request (Client B) can not be processed, it shall be answered with NRC21 BusyRepeatRequest.
FALSE: when the second request (Client B) can not be processed, it shall not be responded.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.responseOnSecondDeclinedRequest
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00914]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol
BSW Parameter BSW Type
DcmDslProtocolRow ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration of one particular diagnostic protocol used in Dcm.
Template Description
This meta-class represents the ability to define a diagnostic protocol.
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticProtocol
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00695]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
MainConnection
BSW Parameter BSW Type
DcmDslProtocolComMChannelRef ECUC-REFERENCE-DEF
BSW Description
Reference to the ComMChannel on which the DcmDslProtocolRxPdu is received and the DcmDslProtocolTxPdu is
transmitted.
Template Description
5

321 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
The CommunicationCluster is the main element to describe the topological connection of communicating ECUs.
A cluster describes the ensemble of ECUs, which are linked by a communication medium of arbitrary topology (bus, star, ring,
...). The nodes within the cluster share the same communication protocol, which may be event-triggered, time-triggered or a
combination of both.
A CommunicationCluster aggregates one or more physical channels.
M2 Parameter
SystemTemplate::Fibex::FibexCore::CoreTopology::CommunicationCluster
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00952]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
MainConnection/DcmDslProtocolRx/DcmDslProtocolRxAddrType
BSW Parameter BSW Type
DCM_FUNCTIONAL_TYPE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
FUNCTIONAL = 1 to n communication
Template Description
Reference to functional request messages.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.functionalRequest
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
MainConnection/DcmDslProtocolRx/DcmDslProtocolRxAddrType
BSW Parameter BSW Type
DCM_PHYSICAL_TYPE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
PHYSICAL = 1 to 1 communications using physical addressing
Template Description
Reference to a physical request message.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.physicalRequest
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

322 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
MainConnection/DcmDslProtocolRx
BSW Parameter BSW Type
DcmDslProtocolRxPduRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Pdu in EcuC that is used for this reception channel.
Template Description
The IPdu (Interaction Layer Protocol Data Unit) element is used to sum up all Pdus that are routed by the PduR.
M2 Parameter
SystemTemplate::Fibex::FibexCore::CoreCommunication::IPdu
Mapping Rule Mapping Type
Reference to IPdu of xxxTpConnection for DiagnosticConnection.physicalRequest / Diagnostic full
Connection.functionalRequest
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00770]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
MainConnection
BSW Parameter BSW Type
DcmDslProtocolTx ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration parameters of a transmission channel in a diagnostic connection.
The PDU referenced by this transmission channel can produce meta data items of type TARGET_ADDRESS_16 and
SOURCE_ADDRESS_16.
Template Description
In the vast majority of cases a response is required. However, there are also cases where providing the response is not
possible and/or not allowed.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.response
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00711]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
MainConnection/DcmDslProtocolTx
BSW Parameter BSW Type
DcmDslProtocolTxPduRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Pdu in EcuC that is used for this transmission channel.
Template Description
The IPdu (Interaction Layer Protocol Data Unit) element is used to sum up all Pdus that are routed by the PduR.
M2 Parameter
SystemTemplate::Fibex::FibexCore::CoreCommunication::IPdu
5

323 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
Reference to IPdu of xxxTpConnection for DiagnosticConnection.response full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00772]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
PeriodicTransmission/DcmDslPeriodicConnection
BSW Parameter BSW Type
DcmDslPeriodicTxPduRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Pdu in EcuC that is used for this periodic transmission channel.
Template Description
The IPdu (Interaction Layer Protocol Data Unit) element is used to sum up all Pdus that are routed by the PduR.
M2 Parameter
SystemTemplate::Fibex::FibexCore::CoreCommunication::IPdu
Mapping Rule Mapping Type
Reference to IPdu of xxxTpConnection in case of DiagnosticConnection.periodicResponseTp or full
IPdu of PduTriggering in case of DiagnosticConnection.periodicResponseUudt
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00742]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslConnection/DcmDsl
ResponseOnEvent
BSW Parameter BSW Type
DcmDslRoeTxPduRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Pdu in EcuC that is used for this ResponseOnEvent transmission connection.
Template Description
The IPdu (Interaction Layer Protocol Data Unit) element is used to sum up all Pdus that are routed by the PduR.
M2 Parameter
SystemTemplate::Fibex::FibexCore::CoreCommunication::IPdu
Mapping Rule Mapping Type
Reference to IPdu of xxxTpConnection for DiagnosticConnection.responseOnEvent full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00743]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow
BSW Parameter BSW Type
DcmDslProtocolPriority ECUC-INTEGER-PARAM-DEF
BSW Description
5

324 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Protocol priority used during protocol preemption. A higher priority protocol may preempt a lower priority protocol. Lower
numeric values represent higher protocol priority:
0 - Highest protocol priority
255 - Lowest protocol priority
Template Description
This represents the priority of the diagnostic protocol in comparison to other diagnostic protocols. Lower numeric values
represent higher protocol priority:
• 0 - Highest protocol priority
• 255 - Lowest protocol priority
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticProtocol.priority
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00699]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolTransType
BSW Parameter BSW Type
TYPE1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Messages on the DcmTxPduId already used for normal diagnostic responses. The outgoing messages must be synchronized
with ’normal outgoing messages’, which have a higher priority.
Template Description
Reference to a ROE message.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.responseOnEvent
Mapping Rule Mapping Type
TYPE1 : periodicResponseTp / responseOnEvent using same reference as the normal response full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolTransType
BSW Parameter BSW Type
TYPE2 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Messages on a separate DcmTxPduId.
Template Description
Reference to a ROE message.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.responseOnEvent
Mapping Rule Mapping Type
TYPE2: periodicResponseTp / responseOnEvent using other reference as the normal response full
Mapping Status ECUC Parameter ID
5

325 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_PERIODICTRANS_ON_CAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
AbstractCanPhysicalChannel:
Abstract class that is used to collect the common TtCAN and CAN PhysicalChannel attributes.
DiagnosticConnection.periodicResponseUudt:
Reference to UUDT responses.
M2 Parameter
SystemTemplate::Fibex::Fibex4Can::CanTopology::AbstractCanPhysicalChannel, SystemTemplate::Diagnostic
Connection::DiagnosticConnection.periodicResponseUudt
Mapping Rule Mapping Type
If DiagnosticConnection.periodicResponseUudt exists and PhysicalChannel given as AbstractCan full
PhysicalChannel.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_PERIODICTRANS_ON_IP ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
StaticSocketConnection:
Definition of static SocketConnection between the Socket that is defined by the aggregating SocketAddress and the remote
Address.
DiagnosticConnection.periodicResponseUudt:
Reference to UUDT responses.
EthernetPhysicalChannel:
The EthernetPhysicalChannel represents a VLAN or an untagged channel. An untagged channel is modeled as an Ethernet
PhysicalChannel without an aggregated VLAN.
M2 Parameter
SystemTemplate::Fibex::Fibex4Ethernet::ServiceInstances::StaticSocketConnection, SystemTemplate::Diagnostic
Connection::DiagnosticConnection.periodicResponseUudt, SystemTemplate::Fibex::Fibex4Ethernet::EthernetTopology::
EthernetPhysicalChannel
Mapping Rule Mapping Type
If DiagnosticConnection.periodicResponseUudt exists and PhysicalChannel given as Ethernet full
PhysicalChannel.
Mapping Status ECUC Parameter ID
valid

326 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_ROE_ON_CAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticConnection.responseOnEvent:
Reference to a ROE message.
CanTpConnection:
A connection identifies the sender and the receiver of this particular communication. The CanTp module routes a Pdu
through this connection.
atpVariation: Derived, because TpNode can vary.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.responseOnEvent, SystemTemplate::TransportProtocols::
CanTpConnection
Mapping Rule Mapping Type
In case DiagnosticConnection.responseOnEvent exists and TpConnectionIdent.ident belongs to a full
CanTpConnection.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_ROE_ON_FLEXRAY ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticConnection.responseOnEvent:
Reference to a ROE message.
FlexrayTpConnection:
A connection identifies the sender and the receiver of this particular communication. The FlexRayTp module routes a Pdu
through this connection.
In a System Description the references to the PduPools are mandatory. In an ECU Extract these references can be optional:
On unicast connections these references are always mandatory. On multicast the txPduPool is mandatory on the sender
side. The rxPduPool is mandatory on the receiver side. On Gateway ECUs both references are mandatory.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.responseOnEvent, SystemTemplate::TransportProtocols::
FlexrayTpConnection
Mapping Rule Mapping Type
In case DiagnosticConnection.responseOnEvent exists and TpConnectionIdent.ident belongs to full
FlexRayTpConnection
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
5

327 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DCM_ROE_ON_IP ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticConnection.responseOnEvent:
Reference to a ROE message.
StaticSocketConnection:
Definition of static SocketConnection between the Socket that is defined by the aggregating SocketAddress and the remote
Address.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.responseOnEvent, System
Template::Fibex::Fibex4Ethernet::ServiceInstances::StaticSocketConnection
Mapping Rule Mapping Type
In case DiagnosticConnection.responseOnEvent exists and TpConnectionIdent.ident belongs to full
SocketConnection
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_UDS_ON_CAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
UDS on CAN (ISO15765-3; ISO14229-1)
Template Description
DiagnosticConnection.physicalRequest:
Reference to a physical request message.
CanTpConnection:
A connection identifies the sender and the receiver of this particular communication. The CanTp module routes a Pdu
through this connection.
atpVariation: Derived, because TpNode can vary.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.physicalRequest, SystemTemplate::TransportProtocols::
CanTpConnection
Mapping Rule Mapping Type
In case DiagnosticConnection.physicalRequest exists and TpConnectionIdent.ident belongs to full
CanTpConnection
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_UDS_ON_FLEXRAY ECUC-ENUMERATION-LITERAL-DEF
BSW Description
UDS on FlexRay (Manufacturer specific; ISO14229-1)
Template Description
5

328 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticConnection.physicalRequest:
Reference to a physical request message.
FlexrayTpConnection:
A connection identifies the sender and the receiver of this particular communication. The FlexRayTp module routes a Pdu
through this connection.
In a System Description the references to the PduPools are mandatory. In an ECU Extract these references can be optional:
On unicast connections these references are always mandatory. On multicast the txPduPool is mandatory on the sender
side. The rxPduPool is mandatory on the receiver side. On Gateway ECUs both references are mandatory.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.physicalRequest, SystemTemplate::TransportProtocols::
FlexrayTpConnection
Mapping Rule Mapping Type
In case DiagnosticConnection.physicalRequest exists and TpConnectionIdent.ident belongs to full
FlexRayTpConnection
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocolType
BSW Parameter BSW Type
DCM_UDS_ON_IP ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticConnection.physicalRequest:
Reference to a physical request message.
StaticSocketConnection:
Definition of static SocketConnection between the Socket that is defined by the aggregating SocketAddress and the remote
Address.
M2 Parameter
SystemTemplate::DiagnosticConnection::DiagnosticConnection.physicalRequest, System
Template::Fibex::Fibex4Ethernet::ServiceInstances::StaticSocketConnection
Mapping Rule Mapping Type
In case DiagnosticConnection.physicalRequest exists and TpConnectionIdent.ident belongs to a full
SocketConnection
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlAllChannel
BSW Parameter BSW Type
DcmDspAllComMChannelRef ECUC-REFERENCE-DEF
BSW Description
Reference to ComM channel.
Template Description
This reference represents the semantics that all available channels shall be affected. It is still necessary to refer to individual
CommunicatuionClusters because there could be private CommunicationClusters in the System Extract that are not subject
to the service "communication control".
By referring to the applicable CommunicationClusters it can be made sure that only the affected CommunicationClusters are
accessed.
5

329 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControlClass.allChannels
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00902]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSpecificChannel
BSW Parameter BSW Type
DcmDspSpecificComMChannelRef ECUC-REFERENCE-DEF
BSW Description
Reference to ComM channel.
Template Description
This represents the ability to add additional attributes to the case that only specific channels are supposed to be considered,
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControlClass.specificChannel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00904]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSpecificChannel
BSW Parameter BSW Type
DcmDspSubnetNumber ECUC-INTEGER-PARAM-DEF
BSW Description
Subnet Number which controls the specific ComMChannel.
Template Description
This represents the applicable subnet number (which is an arbitrary number ranging from 1..14)
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControlSpecificChannel.subnetNumber
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00905]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspComControl
BSW Parameter BSW Type
DcmDspComControlSubNode ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container gives information about the node identification number and the ComM channel used to address a sub-network.
Template Description
5

330 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This attribute represents the ability to add further attributes to the definition of a specific sub-node channel that is subject to
the diagnostic service "communication control".
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControlClass.subNodeChannel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01033]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSubNode
BSW Parameter BSW Type
DcmDspComControlSubNodeComMChannelRef ECUC-REFERENCE-DEF
BSW Description
This parameter references a ComM channel where this node is connected to.
Template Description
This represents the affected CommunicationClusters in the role subNodeChannel
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControlSubNodeChannel.
subNodeChannel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01030]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSubNode
BSW Parameter BSW Type
DcmDspComControlSubNodeId ECUC-INTEGER-PARAM-DEF
BSW Description
The node identification number DcmDspComControlSubNodeId is addressed by the CommunicationControl (0x28) request.
Template Description
This represents the applicable subNode number. The value corresponds to the request message parameter node
IdentificationNumber of diagnostic service CommunicationControl (0x28).
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::CommunicationControl::DiagnosticComControlSubNodeChannel.
subNodeNumber
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01031]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
5

331 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspCommonAuthorization ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for the common Authorization being equal for several services /
sub-services.
Template Description
This represents an instance of the "Routine Control" diagnostic service.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::RoutineControl::DiagnosticRoutineControl
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01025]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspControlDTCSetting
BSW Parameter BSW Type
DcmSupportDTCSettingControlOptionRecord ECUC-BOOLEAN-PARAM-DEF
BSW Description
This configuration switch defines if the DTCSettingControlOptionRecord is in general supported in the request message or
not.
Template Description
This represents the decision whether the DTCSettingControlOptionRecord (see ISO 14229-1) is in general supported in the
request message.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ControlDTCSetting::DiagnosticControlDTCSettingClass.
controlOptionRecordPresent
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00965]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspDDDIDcheckPerSourceDID ECUC-BOOLEAN-PARAM-DEF
BSW Description
Defines the check for session, security and mode dependencies per source DIDs with a ReadDataByIdentifier (0x22).
true: Dcm module shall check the session, security and mode dependencies per source DIDs with a ReadDataByIdentifier
(0x22) with DID in the range 0xF200 to 0xF3FF
false: Dcm module shall not check the session, security and mode dependencies per source DIDs with a ReadDataBy
Identifier (0x22) with DID in the range 0xF200 to 0xF3FF
Template Description
If set to TRUE, the Dcm module shall check the session, security and mode dependencies per source DIDs with a ReadData
ByIdentifier (0x22) with DID in the range 0xF200 to 0xF3FF.
If set to FALSE. the Dcm module shall not check the session, security and mode dependencies per source DIDs with a Read
DataByIdentifier (0x22) with DID in the range 0xF200 to 0xF3FF.
5

332 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineDataIdentifier::DiagnosticDynamicallyDefineDataIdentifier
Class.checkPerSourceId
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00966]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspData ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) of a Data belonging to a DID
Template Description
DiagnosticSecurityEventReportingModeMapping:
This meta-class represents the ability to associate a location in a DID with a security event. The purpose of this mapping is
that the location in the DID contains the setting of the reporting mode for the specific security event. This means that the
reporting mode of the security event can be set via the diagnostic service WriteDataByIdentifier.
DiagnosticSecurityEventReportingModeMapping.securityEvent:
This reference identifies the mapped security event.
DiagnosticSecurityEventReportingModeMapping.dataElement:
This reference identifies the data element that carries the information about the reporting mode.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticSecurityEventReportingModeMapping, DiagnosticExtract::Service
Mapping::DiagnosticSecurityEventReportingModeMapping.securityEvent, DiagnosticExtract::Service
Mapping::DiagnosticSecurityEventReportingModeMapping.dataElement
Mapping Rule Mapping Type
If a DiagnosticSecurityEventReportingModeMapping exists then: * DcmDspDataType shall be set full
to UINT8_N * DcmDspDataByteSize shall be set to the number of bytes in the DiagnosticData
Identifier * DcmDspDataUsePort shall be set to USE_DATA_SYNCH_FNC *DcmDspDataReadFnc
shall be set to the name of the read API for reporting mode at the IdsM * DcmDspDataWriteFnc
shall be set to the name of the write API for reporting mode at the IdsM
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00869]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataByteSize ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the array length in bytes or the the maximum array length for variable datalengths.
Template Description
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
5

333 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, AsamHdo::BaseTypes::Base
TypeDirectDefinition.baseTypeSize
Mapping Rule Mapping Type
S/R via array: DcmDspDataByteSize= maxNumberOfElements * (baseTypeSize / 8) C/S of FNC full
callback: DcmDspDataByteSize= maxNumberOfElements Note: 8 is the baseTypeSize of UINT8
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01106]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataConditionCheckReadFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to demand application if the conditions (e.g. System state) to read the DID are correct. (ConditionCheck
Read-function).
Multiplicity shall be equal to parameter DcmDspDataReadFnc. This parameter is related to the interface Xxx_ConditionCheck
Read.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00677]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a DID in a diagnostic request or response message.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnosticDataIdentifier.dataElement
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00986]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
5

334 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspDataFreezeCurrentStateFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request to application to freeze the current state of an IOControl. (FreezeCurrentState-function).
This parameter is related to the interface Xxx_FreezeCurrentState.
Template Description
DiagnosticServiceSwMapping.mappedBswServiceDependency:
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
DiagnosticIoControlNeeds.freezeCurrentStateSupported:
This attribute determines, if the referenced port supports temporary freezing of I/O value.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency, Common
Structure::ServiceNeeds::DiagnosticIoControlNeeds.freezeCurrentStateSupported
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00674]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataReadDataLengthFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request from application the data length of a DID. (ReadDataLength-function). This parameter is related to
the interface Xxx_ReadDataLength.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00671]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataReadFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request from application the data value of a DID. (ReadData-function). This parameter is related to the
interface Xxx_ReadData.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
5

335 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00669]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataResetToDefaultFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request to application to reset an IOControl to default value. (ResetToDefault-function). This parameter is
related to the interface Xxx_ResetToDefault.
Template Description
DiagnosticServiceSwMapping.mappedBswServiceDependency:
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
DiagnosticIoControlNeeds.resetToDefaultSupported:
This represents a flag for the existence of the ResetToDefault operation in the service interface.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency, Common
Structure::ServiceNeeds::DiagnosticIoControlNeeds.resetToDefaultSupported
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00673]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataReturnControlToEcuFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request to application to return control to ECU of an IOControl. (ReturnControlToECU-function). This
parameter is related to the interface Xxx_ReturnControlToECU.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00672]

336 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataShortTermAdjustmentFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request to application to adjust the IO signal. (ShortTermAdjustment-function).
This parameter is related to the interface Xxx_ShortTermAdjustment.
Template Description
DiagnosticServiceSwMapping.mappedBswServiceDependency:
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
DiagnosticIoControlNeeds.shortTermAdjustmentSupported:
This attribute determines, if the referenced port supports temporarily setting of I/O value to a specific value provided by the
diagnostic tester.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency, Common
Structure::ServiceNeeds::DiagnosticIoControlNeeds.shortTermAdjustmentSupported
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00675]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = BOOLEAN baseTypeSize = 1 maxNumberOfElements shall not exist array full
SizeSemantics shall not exist Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
5

337 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

338 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Type of the data is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements shall not exist arraySize full
Semantics shall not exist Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements exists and value is greater full
than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is set to
ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001) Derivation from DiagnosticValue
Needs.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

339 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements shall not exist arraySize full
Semantics shall not exist Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements exists and value is greater full
than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is set to
ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001) Derivation from DiagnosticValue
Needs.fixedLength=1 possible.
5

340 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements shall not exist arraySize full
Semantics shall not exist Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
5

341 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements exists and value is greater full
than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is set to
ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001) Derivation from DiagnosticValue
Needs.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOfElements shall not exist full
arraySizeSemantics shall not exist Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
5

342 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOfElements exists and value full
is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is
set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001) Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 maxNumberOfElements shall not exist full
arraySizeSemantics shall not exist Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
5
5

343 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
4
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 maxNumberOfElements exists and value full
is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is
set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001) Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT8_DYN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint8 array with dynamic length.
Template Description
5

344 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002) arraySizeSemantics
exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_DEXT_01002) Derivation from
DiagnosticValueNeeds.fixedLength=0 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, CommonStructure::Service
Needs::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics
either does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_
DEXT_01001) Derivation from DiagnosticValueNeeds.fixedLength=1 possible.
5

345 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataUsePort ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines which interface shall be used to access the data.
Template Description
This attribute controls whether interaction requires the software-component to react synchronously on a request or whether it
processes the request in background but still the DCM has to issue the call again to eventually obtain the result of the request.
M2 Parameter
CommonStructure::ServiceNeeds::DiagnosticValueNeeds.processingStyle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00713]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort
BSW Parameter BSW Type
USE_DATA_ASYNCH_CLIENT_SERVER ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The DCM will access the Data using an R-Port requiring a asynchronous ClientServertInterface DataServices_{Data}. The
R-Port is named DataServices_{Data} where {Data} is the name of the container DcmDspData.
Template Description
The software-component processes the request in background but still the Dcm has to issue the call again to eventually
obtain the result of the request.
M2 Parameter
CommonStructure::ServiceNeeds::DiagnosticProcessingStyleEnum.processingStyleAsynchronous
Mapping Rule Mapping Type
DiagnosticServiceSwMapping is having a SwcServiceDependency and ServiceNeeds::Diagnostic full
ProcessingStyleEnum is equal to processingStyleAsynchronous
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort
BSW Parameter BSW Type
USE_DATA_ASYNCH_CLIENT_SERVER_ERROR ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The Dcm will access the Data using an R-Port requiring a asynchronous ClientServertInterface DataServices_{Data}. The
parameter ErrorCode can be returned to allow the application to trigger a negative response during the operation. The R-Port
is named DataServices_{Data} where {Data} is the name of the container DcmDspData.
Template Description
5

346 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
The software-component processes the request in background but still the Dcm has to issue the call again to eventually
obtain the result of the request or handle error code.
M2 Parameter
CommonStructure::ServiceNeeds::DiagnosticProcessingStyleEnum.processingStyleAsynchronousWithError
Mapping Rule Mapping Type
DiagnosticServiceSwMapping is having a SwcServiceDependency and ServiceNeeds::Diagnostic full
ProcessingStyleEnum is equal to processingStyleAsynchronousWithError
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort
BSW Parameter BSW Type
USE_DATA_ASYNCH_FNC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The DCM will access the Data using the functions that are defined in parameters of type EcucFunctionNameDef (but without
DcmDspDataReadDataLengthFnc) in the DcmDspData container. DCM_E_PENDING return is allowed. OpStatus is existing
as IN parameter.
Template Description
The software-component processes the request in background but still the Dcm has to issue the call again to eventually
obtain the result of the request.
M2 Parameter
CommonStructure::ServiceNeeds::DiagnosticProcessingStyleEnum.processingStyleAsynchronous
Mapping Rule Mapping Type
DiagnosticServiceSwMapping is having a BswServiceDependency and ServiceNeeds::Diagnostic full
ProcessingStyleEnum is equal to processingStyleAsynchronous
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort
BSW Parameter BSW Type
USE_DATA_SENDER_RECEIVER ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The DCM will access the Data using an Port requiring a SenderReceiverInteface (with isService=false) DataServices_{Data}.
The Port is namedDataServices_{Data} where {Data} is the name of the container DcmDspData.
Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component.
This kind of service mapping is applicable for the usage of SenderReceiverInterfaces or event/notifier semantics in Service
Interfaces on the adaptive platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

347 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort
BSW Parameter BSW Type
USE_DATA_SENDER_RECEIVER_AS_SERVICE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The DCM will access the Data using an service Port requiring a SenderReceiverInteface (with isService=true) Data
Services_{Data} . The Port is namedDataServices_{Data} where {Data} is the name of the container DcmDspData.
Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component.
This kind of service mapping is applicable for the usage of SenderReceiverInterfaces or event/notifier semantics in Service
Interfaces on the adaptive platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDataWriteFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request application to write the data value of a DID. (WriteData-function). This parameter is related to the
interface Xxx_WriteData.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00670]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDiagnosisScaling/DcmDspAlternativeData
Type
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
5

348 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDiagnosisScaling/DcmDspAlternativeData
Type/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDiagnosisScaling/DcmDspAlternativeData
Type/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

349 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspDidDataSupportInfo ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container defines the supported information.
Template Description
DiagnosticParameter.supportInfo:
This attribute represents the ability to define which bit of the support info byte is representing this part of the PID.
DiagnosticDataIdentifier.supportInfoByte:
This attribute represents the supported information associated with the DiagnosticDataIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.supportInfo, DiagnosticExtract::Common
Diagnostics::DiagnosticDataIdentifier.supportInfoByte
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01104]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspExternalSRDataElementClass/DcmData
ElementInstance
BSW Parameter BSW Type
DcmDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitive or array data which shall be read or written. Supported are VariableDataPrototypes in
SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in ParameterInterfaces (read only). This
reference is applicable if the AutosarDataPrototype is typed with a ApplicationPrimitiveDataType of category VALUE or
BOOLEAN or ApplicationArrayDataType or if the AutosarDataPrototype is typed with a ImplementationDataType of category
VALUE, ARRAY or TYPE_REFERENCE that in turn boils down to VALUE or ARRAY
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive data. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00991]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspExternalSRDataElementClass/DcmSub
ElementInDataElementInstance
BSW Parameter BSW Type
DcmSubElementInDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
5

350 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Instance Reference to the primitve sub-element (at any level) of composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in Parameter
Interfaces (read only). This reference is applicable if the AutosarDataPrototype is typed with a ApplicationCompositeData
Type.
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive element within a composite data, where the full
AutosarDataPrototype is typed with a ApplicationCompositeDataType.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00990]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspExternalSRDataElementClass/DcmSub
ElementInImplDataElementInstance
BSW Parameter BSW Type
DcmSubElementInImplDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitve sub-element (at any level) of composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in Parameter
Interfaces (read only). This reference is applicable if the AutosarDataPrototype is typed with a ImplementationDataType of
category STRUCTURE or ARRAY. Please note that in case of ARRAY the index attribute in the target reference has to be set
to select a single array element.
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive element within a composite data, where the full
AutosarDataPrototype is typed with a ApplicationCompositeDataType ImplementationDataType of
category STRUCTURE or ARRAY.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00992]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspData
BSW Parameter BSW Type
DcmDspOdxDataDescription ECUC-ADD-INFO-PARAM-DEF
BSW Description
Defines additional description for ODX documentation
Template Description
This specifies the long name of the object. Long name is targeted to human readers and acts like a headline.
M2 Parameter
GenericStructure::GeneralTemplateClasses::Identifiable::MultilanguageReferrable.longName
5

351 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
Textual description that characterizes the DID element with respect to the ODX long name can be full
provided by means of the attribute long-Name.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00988]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspDataDefaultEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the default endianness belonging to a DID, RID or PID if the corresponding data does not define an endianness.
Template Description
Defines the default endianness of the data belonging to a DID or RID which is applicable if the DiagnosticDataElement does
not define the endianness via the swDataDefProps.baseType attribute.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.defaultEndianness
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00987]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspDid ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) of the DID.
Template Description
DiagnosticDataIdentifier:
This meta-class represents the ability to model a diagnostic data identifier (DID) that is fully specified regarding the payload at
configuration-time.
DiagnosticDynamicDataIdentifier:
This meta-class represents the ability to define a diagnostic data identifier (DID) at run-time.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataIdentifier, DiagnosticExtract::CommonDiagnostics::
DiagnosticDynamicDataIdentifier
Mapping Rule Mapping Type
If the DiagnosticDataIdentifier is referenced by DiagnosticDataByIdentifier, DiagnosticIOControl, or full
DiagnosticReadDataByPeriodicID,DiagnosticDataChangeTrigger
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00601]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDid
BSW Parameter BSW Type
5

352 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspDidIdentifier ECUC-INTEGER-PARAM-DEF
BSW Description
2 byte Identifier of the DID
Within each DcmConfigSet all DcmDspDidIdentifier values shall be unique.
Template Description
DiagnosticAbstractDataIdentifier.id:
This is the numerical identifier used to identify the DiagnosticAbstractDataIdentifier in the scope of diagnostic workflow
DiagnosticValueNeeds.didNumber:
This represents a Data identifier for the diagnostic value. This allows to predefine the DID number if the responsible function
developer has received a particular requirement from the OEM or from a standardization body.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticAbstractDataIdentifier.id, CommonStructure::ServiceNeeds::Diagnostic
ValueNeeds.didNumber
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00602]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidSignal
BSW Parameter BSW Type
DcmDspDidByteOffset ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the absolute byte offset of the data defined by DcmDspDidDataRef reference to DcmDspData container in the DID.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
bitOffset / 8 full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01105]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDid
BSW Parameter BSW Type
DcmDspDidSize ECUC-INTEGER-PARAM-DEF
BSW Description
Length of a DID in byte(s).
Template Description
This attribute indicates the size in bytes of the DiagnosticDataIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataIdentifier.didSize
Mapping Rule Mapping Type
1:1 mapping full
5

353 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01099]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDid
BSW Parameter BSW Type
DcmDspDidSupportInfo ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container defines the support information to declare the usability of the data bytes within the DIDs
Template Description
This attribute represents the supported information associated with the DiagnosticDataIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataIdentifier.supportInfoByte
Mapping Rule Mapping Type
full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01102]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo
BSW Parameter BSW Type
DcmDspDDDIDMaxElements ECUC-INTEGER-PARAM-DEF
BSW Description
Maximum number of source elements of a DDDID.
Template Description
This represents the maximum number of source elements of the dynamically created DID.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineDataIdentifier::DiagnosticDynamicallyDefineDataIdentifier.
maxSourceElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00970]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl
BSW Parameter BSW Type
DcmDspDidControlSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspSecurityRow Security levels allowed to control this DID. If there is no reference, no check of security
level shall be done.
Template Description
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
5

354 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00620]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl
BSW Parameter BSW Type
DcmDspDidControlSessionRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspSessionRow Sessions allowed to control this DID. If there is no reference, no check of session level
shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00621]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl
BSW Parameter BSW Type
DcmDspDidFreezeCurrentState ECUC-BOOLEAN-PARAM-DEF
BSW Description
This indicates the presence of "FreezeCurrentState".
Template Description
DiagnosticIOControl.freezeCurrentState:
Setting this attribute to true represents the ability of the Dcm to execute a freezeCurrentState.
DiagnosticIoControlNeeds.freezeCurrentStateSupported:
This attribute determines, if the referenced port supports temporary freezing of I/O value.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::IOControl::DiagnosticIOControl.freezeCurrentState, Common
Structure::ServiceNeeds::DiagnosticIoControlNeeds.freezeCurrentStateSupported
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00624]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl
BSW Parameter BSW Type
DcmDspDidResetToDefault ECUC-BOOLEAN-PARAM-DEF
BSW Description
5

355 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This indicates the presence of "ResetToDefault".
Template Description
DiagnosticIOControl.resetToDefault:
Setting this attribute to true represents the ability of the Dcm to execute a resetToDefault.
DiagnosticIoControlNeeds.resetToDefaultSupported:
This represents a flag for the existence of the ResetToDefault operation in the service interface.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::IOControl::DiagnosticIOControl.resetToDefault, CommonStructure::Service
Needs::DiagnosticIoControlNeeds.resetToDefaultSupported
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00623]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl
BSW Parameter BSW Type
DcmDspDidShortTermAdjustment ECUC-BOOLEAN-PARAM-DEF
BSW Description
This indicates the presence of "ShortTermAdjustment".
Template Description
DiagnosticIOControl.shortTermAdjustment:
Setting this attribute to true represents the ability of the Dcm to execute a shortTermAdjustment.
DiagnosticIoControlNeeds.shortTermAdjustmentSupported:
This attribute determines, if the referenced port supports temporarily setting of I/O value to a specific value provided by the
diagnostic tester.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::IOControl::DiagnosticIOControl.shortTermAdjustment, Common
Structure::ServiceNeeds::DiagnosticIoControlNeeds.shortTermAdjustmentSupported
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00625]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo
BSW Parameter BSW Type
DcmDspDidDynamicallyDefined ECUC-BOOLEAN-PARAM-DEF
BSW Description
Indicates if this DID can be dynamically defined
true = DID can be dynamically defined false = DID can not be dynamically defined
Template Description
DiagnosticDataIdentifier:
This meta-class represents the ability to model a diagnostic data identifier (DID) that is fully specified regarding the payload at
configuration-time.
DiagnosticDynamicDataIdentifier:
This meta-class represents the ability to define a diagnostic data identifier (DID) at run-time.
5

356 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataIdentifier, DiagnosticExtract::CommonDiagnostics::
DiagnosticDynamicDataIdentifier
Mapping Rule Mapping Type
true: in case the DiagnosticAbstractDataIdentifier for the DID value is aggregated by Diagnostic full
DynamicDataIdentifier false: in case the DiagnosticAbstractDataIdentifier for the DID value is
aggregated by DiagnosticDataIdentifier
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00612]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidRead
BSW Parameter BSW Type
DcmDspDidReadSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspSecurityRow Referenced security levels are allowed to read this DID.
If there is no reference, no check of security level shall be done.
Template Description
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00614]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidRead
BSW Parameter BSW Type
DcmDspDidReadSessionRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspSessionRow Referenced sessions are allowed to read this DID.
If there is no reference, no check of session level shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00615]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidWrite
BSW Parameter BSW Type
5

357 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspDidWriteSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspSecurityRow Referenced security levels are allowed to wirte this DID.
If there is no reference, no check of security level shall be done.
Template Description
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00617]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidWrite
BSW Parameter BSW Type
DcmDspDidWriteSessionRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspSessionRow Referenced sessions are allowed to write this DID.
If there is no reference, no check of session level shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00618]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspEcuReset/DcmDspEcuResetRow
BSW Parameter BSW Type
DcmDspEcuResetId ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the subfunction ID
Template Description
This represents the maximum number of source elements of the dynamically created DID.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineDataIdentifier::DiagnosticDynamicallyDefineDataIdentifier.
maxSourceElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01113]

358 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspEcuReset/DcmDspEcuResetRow
BSW Parameter BSW Type
DcmResponseToEcuReset ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the answer to EcuReset service should come: Before or after the reset.
Template Description
This attribute defines whether the response to the EcuReset service shall be transmitted before or after the actual reset.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EcuReset::DiagnosticEcuResetClass.respondToReset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01039]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspEcuReset/DcmDspEcuResetRow/DcmResponseToEcu
Reset
BSW Parameter BSW Type
AFTER_RESET ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Answer to EcuReset service should come after the reset.
Template Description
Answer to EcuReset service should come after the reset.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EcuReset::DiagnosticResponseToEcuResetEnum.respondAfterReset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspEcuReset/DcmDspEcuResetRow/DcmResponseToEcu
Reset
BSW Parameter BSW Type
BEFORE_RESET ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Answer to EcuReset service should come before the reset.
Template Description
Answer to EcuReset service should come before the reset.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EcuReset::DiagnosticResponseToEcuResetEnum.respondBeforeReset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

359 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspMaxDidToRead ECUC-INTEGER-PARAM-DEF
BSW Description
Indicates the maximum allowed DIDs in a single "ReadDataByIdentifier" request.
Template Description
This attribute represents the maximum number of allowed DIDs in a single instance of DiagnosticReadDataByIdentifier.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::DataByIdentifier::DiagnosticReadDataByIdentifierClass.maxDidToRead
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00638]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspMaxPeriodicDidToRead ECUC-INTEGER-PARAM-DEF
BSW Description
Indicates the maximum allowed periodicDIDs which can be read in a single "ReadDataByPeriodicIdentifier" request.
Template Description
This represents the maximum number of data identifiers that can be included in one request.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticReadDataByPeriodicIDClass.
maxPeriodicDidToRead
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00956]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo
BSW Parameter BSW Type
DcmDspMemoryIdValue ECUC-INTEGER-PARAM-DEF
BSW Description
Value of the memory device identifier used.
Each DcmDspMemoryIdInfo should have a unique ID.
The MemoryIdValue is retrieved from the request messages (RMBA,WMBA,RD,RU,DDDI) according to ISO-14229-1 with the
most significant byte of the request parameter memoryAddress.
Template Description
This represents the identification of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.id
Mapping Rule Mapping Type
5

360 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00913]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeByLabelHigh ECUC-STRING-PARAM-DEF
BSW Description
High memory address as label (string) of a range allowed for reading.
Template Description
This represents a symbolic label for the upper bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryHighAddressLabel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01070]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeByLabelLow ECUC-STRING-PARAM-DEF
BSW Description
Low memory address as label (string) of a range allowed for reading.
Template Description
This represents a symbolic label for the lower bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryLowAddressLabel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01069]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the Security Access Levels needed for read access on this memory address. If there is no reference, no check of
security level shall be done.
Template Description
5

361 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
DiagnosticMemoryIdentifier referenced in the role memoryRange is referenced by a Diagnostic full
ReadMemoryByAddress The accessPermission holds the security level information.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01071]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeSessionLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01088]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeHigh ECUC-INTEGER-PARAM-DEF
BSW Description
High memory address of a range allowed for reading
Template Description
This represents the upper bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryHighAddress
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00787]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeInfo
5

362 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Parameter BSW Type
DcmDspReadMemoryRangeLow ECUC-INTEGER-PARAM-DEF
BSW Description
Low memory address of a range allowed for reading
Template Description
This represents the lower bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryLowAddress
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00786]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the Security Access Levels needed for read access on this memory address. If there is no reference, no check of
security level shall be done.
Template Description
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
DiagnosticMemoryIdentifier referenced in the role memoryRange is referenced by a Diagnostic full
ReadMemoryByAddress The accessPermission holds the security level information.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00788]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspReadMemory
RangeInfo
BSW Parameter BSW Type
DcmDspReadMemoryRangeSessionLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
5

363 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01086]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeByLabelHigh ECUC-STRING-PARAM-DEF
BSW Description
High memory address as label (string) of a range allowed for writing.
Template Description
This represents a symbolic label for the upper bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryHighAddressLabel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01075]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeByLabelLow ECUC-STRING-PARAM-DEF
BSW Description
Low memory address as label (string) of a range allowed for writing.
Template Description
This represents a symbolic label for the lower bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryLowAddressLabel
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01074]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the Security Access Levels needed for write access on this memory address. If there is no reference, no check of
security level shall be done.
Template Description
This represents the associated DiagnosticSecurityLevels
5

364 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
DiagnosticMemoryIdentifier referenced in the role memoryRange is referenced by a Diagnostic full
WriteMemoryByAddress The accessPermission holds the security level information.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01076]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeByLabelInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeSessionLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01089]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeHigh ECUC-INTEGER-PARAM-DEF
BSW Description
High memory address of a range allowed for writing.
Template Description
This represents the upper bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryHighAddress
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00791]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeInfo
BSW Parameter BSW Type
5

365 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspWriteMemoryRangeLow ECUC-INTEGER-PARAM-DEF
BSW Description
Low memory address of a range allowed for writing
Template Description
This represents the lower bound for addresses of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.memoryLowAddress
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00790]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeSecurityLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the Security Access Levels needed for write access on this memory address. If there is no reference, no check of
security level shall be done.
Template Description
This represents the associated DiagnosticSecurityLevels
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.securityLevel
Mapping Rule Mapping Type
DiagnosticMemoryIdentifier referenced in the role memoryRange is referenced by a Diagnostic full
WriteMemoryByAddress The accessPermission holds the security level information.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00793]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemory/DcmDspMemoryIdInfo/DcmDspWriteMemory
RangeInfo
BSW Parameter BSW Type
DcmDspWriteMemoryRangeSessionLevelRef ECUC-REFERENCE-DEF
BSW Description
Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Template Description
This represents the associated DiagnosticSessions
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticAccessPermission.diagnosticSession
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

366 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dcm_01087]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer/DcmDspMemoryTransferIdInfo
BSW Parameter BSW Type
DcmDspMemoryIdValue ECUC-INTEGER-PARAM-DEF
BSW Description
Value of the memory device identifier used.
Each DcmDspMemoryIdInfo should have a unique ID.
The MemoryIdValue is retrieved from the request messages (RMBA,WMBA,RD,RU,DDDI) according to ISO-14229-1 with the
most significant byte of the request parameter memoryAddress.
Template Description
This represents the identification of the memory segment.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::MemoryByAddress::DiagnosticMemoryIdentifier.id
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01138]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPeriodicTransmission
BSW Parameter BSW Type
DcmDspMaxPeriodicDidScheduler ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the maximum number of periodicDataIdentifiers that can be scheduled concurrently.
Template Description
This represents the maximum number of periodic data identifiers that can be scheduled in parallel.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticReadDataByPeriodicIDClass.
schedulerMaxNumber
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00962]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPeriodicTransmission
BSW Parameter BSW Type
DcmDspPeriodicTransmissionFastRate ECUC-FLOAT-PARAM-DEF
BSW Description
This parameter give the transmission rate of the requested periodicDataIdentifiers to be used if the parameter transmission
Mode given in the ReadDataByPeriodicID request is equal to 0x03 ("sendAtFastRate"). This parameter value in seconds
have to be configured as a multiple of DcmTaskTime.
min: A negative value and zero is not allowed.
5

367 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
DiagnosticPeriodicRate.period:
This represents the period of the DiagnosticPeriodicRate in seconds.
DiagnosticPeriodicRate.periodicRateCategory:
This attribute represents the category of the periodic rate.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticPeriodicRate.period, Diagnostic
Extract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticPeriodicRate.periodicRateCategory
Mapping Rule Mapping Type
The parameter shall exist if DiagnosticPeriodicRate.periodicRateCategory is set to Diagnostic full
PeriodicRateCategoryEnum.periodicRateFast.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00960]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPeriodicTransmission
BSW Parameter BSW Type
DcmDspPeriodicTransmissionMediumRate ECUC-FLOAT-PARAM-DEF
BSW Description
This parameter give the transmission rate of the requested periodicDataIdentifiers to be used if the parameter transmission
Mode given in the ReadDataByPeriodicID request is equal to 0x02 ("sendAtMediumRate"). This parameter value in seconds
have to be configured as a multiple of DcmTaskTime.
min: A negative value and zero is not allowed.
Template Description
DiagnosticPeriodicRate.period:
This represents the period of the DiagnosticPeriodicRate in seconds.
DiagnosticPeriodicRate.periodicRateCategory:
This attribute represents the category of the periodic rate.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticPeriodicRate.period, Diagnostic
Extract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticPeriodicRate.periodicRateCategory
Mapping Rule Mapping Type
The parameter shall exist if DiagnosticPeriodicRate.periodicRateCategory is set to Diagnostic full
PeriodicRateCategoryEnum.periodicRateMedium.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00959]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPeriodicTransmission
BSW Parameter BSW Type
DcmDspPeriodicTransmissionSlowRate ECUC-FLOAT-PARAM-DEF
BSW Description
This parameter give the transmission rate of the requested periodicDataIdentifiers to be used if the parameter transmission
Mode given in the ReadDataByPeriodicID request is equal to 0x01 ("sendAtSlowRate"). This parameter value in seconds
have to be configured as a multiple of DcmTaskTime.
min: A negative value and zero is not allowed.
Template Description
5

368 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticPeriodicRate.period:
This represents the period of the DiagnosticPeriodicRate in seconds.
DiagnosticPeriodicRate.periodicRateCategory:
This attribute represents the category of the periodic rate.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticPeriodicRate.period, Diagnostic
Extract::Dcm::DiagnosticService::ReadDataByPeriodicID::DiagnosticPeriodicRate.periodicRateCategory
Mapping Rule Mapping Type
The parameter shall exist if DiagnosticPeriodicRate.periodicRateCategory is set to Diagnostic full
PeriodicRateCategoryEnum.periodicRateSlow.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00958]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspPid ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container defines the availability of a PID to the DCM.
Template Description
This meta-class represents the ability to model a diagnostic parameter identifier (PID) for the purpose of executing on-board
diagnostics (OBD).
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00626]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid
BSW Parameter BSW Type
DcmDspPidData ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container defines the parameter for a Signal in the PID.
Template Description
This represents the data carried by the DiagnosticParameterIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00865]

369 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData
BSW Parameter BSW Type
DcmDspPidByteOffset ECUC-INTEGER-PARAM-DEF
BSW Description
This is the position in bytes of the PID structure and will not start at position 0 in case a support information is available (for
packeted PIDs).
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
bitOffset / 8 full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01107]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData
BSW Parameter BSW Type
DcmDspPidDataByteSize ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the array length in bytes or the the maximum array length for variable datalengths.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticData
Element.maxNumberOfElements
Mapping Rule Mapping Type
S/R via array: DcmDspPidDataByteSize= maxNumberOfElements * (baseTypeSize / 8) C/S of full
FNC callback: DcmDspPidDataByteSize= maxNumberOfElements Note: 8 is the baseTypeSize of
UINT8
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01108]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData
BSW Parameter BSW Type
DcmDspPidDataSupportInfo ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container defines the supported information.
Template Description
This attribute represents the ability to define which bit of the support info byte is representing this part of the PID.
M2 Parameter
5

370 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.supportInfo
Mapping Rule Mapping Type
Applicable if the DiagnosticParameter is owned by a DiagnosticParameterIdentifier full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00874]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidDataSupportInfo
BSW Parameter BSW Type
DcmDspPidDataSupportInfoBit ECUC-INTEGER-PARAM-DEF
BSW Description
Referenced Bit of the SupportInfo
Template Description
defines the bit in the SupportInfo byte, which represents the PID DataElement pidSize / position / size. Unit: byte.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterSupportInfo.supportInfoBit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00876]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidDataSupportInfo
BSW Parameter BSW Type
DcmDspPidDataSupportInfoRef ECUC-REFERENCE-DEF
BSW Description
Reference to DcmDspPidSupportInfo
Template Description
This represents the supported information associated with the DiagnosticParameterIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier.supportInfoByte
Mapping Rule Mapping Type
Shall refer to the DiagnosticParameterIdentifier.supportInfoByte of the enclosing Diagnostic full
ParameterIdentifier
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00875]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDsp
DiagnosisScaling/DcmDspAlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
5

371 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDsp
DiagnosisScaling/DcmDspAlternativeDataType/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDsp
DiagnosisScaling/DcmDspAlternativeDataType/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
5

372 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataEndianness
BSW Parameter BSW Type
BIG_ENDIAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Most significant byte shall be stored at the lowest address.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
BaseTypeDirectDefinition.byteOrder == ByteOrderEnum.mostSignificantByteFirst full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataEndianness
BSW Parameter BSW Type
LITTLE_ENDIAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Most significant byte shall be stored at the highest address
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
BaseTypeDirectDefinition.byteOrder ==ByteOrderEnum.mostSignificantByteLast full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataEndianness
BSW Parameter BSW Type
OPAQUE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Opaque data endianness
5

373 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
BaseTypeDirectDefinition.byteOrder == ByteOrderEnum.opaque full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01
BSW Parameter BSW Type
DcmDspPidDataReadFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name for reading PID data value. This is only relevant if DcmDspPidDataUsePort==USE_DATA_SYNCH_FNC.
This parameter is related to the interface Xxx_ReadData.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
The BswServiceDependency should have aRoleBasedBswModuleEntryAssignment that in turn full
has attribute role set to xxx_ReadData and points to a BswModuleEntry.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00629]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
5

374 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements exists and value is greater full
than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is set to
ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

375 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements exists and value is greater full
than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is set to
ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

376 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeSize, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeEncoding, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements exists and value is greater full
than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is set to
ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

377 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOfElements exists and value full
is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is
set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

378 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 maxNumberOfElements exists and value full
is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is
set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

379 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticParameter full
Identifier.dataElement baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP
baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics
either does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_
DEXT_01001)
5

380 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataUsePort
BSW Parameter BSW Type
USE_DATA_SENDER_RECEIVER ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component.
This kind of service mapping is applicable for the usage of SenderReceiverInterfaces or event/notifier semantics in Service
Interfaces on the adaptive platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping
Mapping Rule Mapping Type
DiagnosticServiceDataMapping.diagnosticDataElement refers to a DiagnosticDataElement that in full
turn is aggregated in the PID definition where the PortPrototype referenced in the role mapped
DataElement.contextPort refers to a DataInterface where attribute isService is set to false.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataUsePort
BSW Parameter BSW Type
USE_DATA_SENDER_RECEIVER_AS_SERVICE ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component.
This kind of service mapping is applicable for the usage of SenderReceiverInterfaces or event/notifier semantics in Service
Interfaces on the adaptive platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping
Mapping Rule Mapping Type
DiagnosticServiceDataMapping.diagnosticDataElement refers to a DiagnosticDataElement that in full
turn is aggregated in the PID definition where the PortPrototype referenced in the role mapped
DataElement.contextPort refers to a DataInterface where attribute isService is set to true.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataUsePort
BSW Parameter BSW Type
USE_DATA_SYNCH_CLIENT_SERVER ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

381 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component or a basic-software module. If
the former is used then this kind of service mapping is applicable for the usage of ClientServerInterfaces.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping
Mapping Rule Mapping Type
DiagnosticServiceSwMapping.diagnosticDataElement refers to a DiagnosticDataElement that in full
turn is aggregated in the PID definition. DiagnosticServiceSwMapping.mappedSwcService
Dependency shall exist.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
DataUsePort
BSW Parameter BSW Type
USE_DATA_SYNCH_FNC ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component or a basic-software module. If
the former is used then this kind of service mapping is applicable for the usage of ClientServerInterfaces.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping
Mapping Rule Mapping Type
DiagnosticServiceSwMapping.diagnosticDataElement refers to a DiagnosticDataElement that in full
turn is aggregated in the PID definition and that also defines the role mappedBswService
Dependency.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
Service01ExternalSRDataElementClass/DcmDataElementInstance
BSW Parameter BSW Type
DcmDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitive or array data which shall be read or written. Supported are VariableDataPrototypes in
SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in ParameterInterfaces (read only). This
reference is applicable if the AutosarDataPrototype is typed with a ApplicationPrimitiveDataType of category VALUE or
BOOLEAN or ApplicationArrayDataType or if the AutosarDataPrototype is typed with a ImplementationDataType of category
VALUE, ARRAY or TYPE_REFERENCE that in turn boils down to VALUE or ARRAY
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive data. full
5

382 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00991]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
Service01ExternalSRDataElementClass/DcmSubElementInDataElementInstance
BSW Parameter BSW Type
DcmSubElementInDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitve sub-element (at any level) of composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in Parameter
Interfaces (read only). This reference is applicable if the AutosarDataPrototype is typed with a ApplicationCompositeData
Type.
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive element within a composite data, where the full
AutosarDataPrototype is typed with a ApplicationCompositeDataType.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00990]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPid
Service01ExternalSRDataElementClass/DcmSubElementInImplDataElementInstance
BSW Parameter BSW Type
DcmSubElementInImplDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitve sub-element (at any level) of composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in Parameter
Interfaces (read only). This reference is applicable if the AutosarDataPrototype is typed with a ImplementationDataType of
category STRUCTURE or ARRAY. Please note that in case of ARRAY the index attribute in the target reference has to be set
to select a single array element.
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive element within a composite data, where the full
AutosarDataPrototype is typed with a ApplicationCompositeDataType ImplementationDataType of
category STRUCTURE or ARRAY.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00992]

383 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService02
BSW Parameter BSW Type
DcmDspPidDataDemRef ECUC-REFERENCE-DEF
BSW Description
Reference to DemPidDataElement in DEM configuration. Allows to link the DCM PID and DEM PID configuration for Mode
$02.
Template Description
This represents the PID associated with this instance of the OBD mode 0x02 service.
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x02_RequestPowertrainFreezeFrameData::DiagnosticPowertrainFreezeFrame.
pid
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00887]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid
BSW Parameter BSW Type
DcmDspPidIdentifier ECUC-INTEGER-PARAM-DEF
BSW Description
1 byte Identifier of the PID
Within each DcmConfigSet all DcmDspPidIdentifier values shall be unique.
Template Description
ObdPidServiceNeeds.parameterId:
Standardized parameter identifier (PID) according to the OBD standard specified in attribute "standard".
DiagnosticParameterIdentifier.id:
This is the numerical identifier used to identify the DiagnosticParameterIdentifier in the scope of diagnostic workflow (see
SAE J1979-DA).
M2 Parameter
CommonStructure::ServiceNeeds::ObdPidServiceNeeds.parameterId, DiagnosticExtract::CommonDiagnostics::Diagnostic
ParameterIdentifier.id
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00627]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidService
BSW Parameter BSW Type
DCM_SERVICE_01 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
A PID is used with service $01 only.
Template Description
This represents the PID associated with this instance of the OBD mode 0x01 service.
5

384 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x01_RequestCurrentPowertrainDiagnosticData::DiagnosticRequestCurrent
PowertrainData.pid
Mapping Rule Mapping Type
Applicable if the DiagnosticParameterIdentifier is only referenced by a DiagnosticRequestCurrent full
PowertrainData
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidService
BSW Parameter BSW Type
DCM_SERVICE_01_02 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
A PID is used with service $01 and $02. Allowed with a PID configuration containing data elements on byte basis.
Template Description
DiagnosticRequestCurrentPowertrainData.pid:
This represents the PID associated with this instance of the OBD mode 0x01 service.
DiagnosticPowertrainFreezeFrame.pid:
This represents the PID associated with this instance of the OBD mode 0x02 service.
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x01_RequestCurrentPowertrainDiagnosticData::DiagnosticRequestCurrent
PowertrainData.pid, DiagnosticExtract::Dcm::ObdService::Mode_0x02_RequestPowertrainFreezeFrameData::Diagnostic
PowertrainFreezeFrame.pid
Mapping Rule Mapping Type
Applicable if the DiagnosticParameterIdentifier is referenced by both a DiagnosticRequestCurrent full
PowertrainData and a DiagnosticPowertrainFreezeFrame
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidService
BSW Parameter BSW Type
DCM_SERVICE_02 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
A PID is used with service $02 only. Allowed with a PID configuration containing data elements on byte basis.
Template Description
This represents the PID associated with this instance of the OBD mode 0x02 service.
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x02_RequestPowertrainFreezeFrameData::DiagnosticPowertrainFreezeFrame.
pid
Mapping Rule Mapping Type
Applicable if the DiagnosticParameterIdentifier is only referenced by a DiagnosticPowertrainFreeze full
Frame
Mapping Status ECUC Parameter ID
valid

385 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid
BSW Parameter BSW Type
DcmDspPidSize ECUC-INTEGER-PARAM-DEF
BSW Description
Length of a PID in byte(s).
Template Description
The size of the entire PID can be greater than the sum of the data elements because padding might be applied. Unit: byte.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier.pidSize
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00870]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid
BSW Parameter BSW Type
DcmDspPidSupportInfo ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container defines the support information (typically byte A) to declare the usability of the data bytes within the so-called
packeted PIDs (e.g. PID$68).
Template Description
This represents the supported information associated with the DiagnosticParameterIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier.supportInfoByte
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00871]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidSupportInfo
BSW Parameter BSW Type
DcmDspPidSupportInfoLen ECUC-INTEGER-PARAM-DEF
BSW Description
Length of the support information in bytes.
Template Description
This represents the size of the supportInfo within the PID. Unit: byte.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticSupportInfoByte.size
Mapping Rule Mapping Type
full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00873]

386 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidSupportInfo
BSW Parameter BSW Type
DcmDspPidSupportInfoPos ECUC-INTEGER-PARAM-DEF
BSW Description
Position of the support information in bytes.
Template Description
This represents the position of the supportInfo in the PID. Unit: byte.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticSupportInfoByte.position
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00872]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspRequestControl ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) of the "Request control of on-board system, test or component" service
(Service $08). The DCM will request the control using an R-Port requiring a PortInteface RequestControlServices_{Tid}. The
R-Port is named RequestControlServices_{Tid} where {Tid} is the name of the container DcmDspRequestControl.
Template Description
This meta-class represents the ability to model an instance of the OBD mode 0x08 service.
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x08_RequestControlOfOnBoardDevice::
DiagnosticRequestControlOfOnBoardDevice
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00637]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl
BSW Parameter BSW Type
DcmDspRequestControlInBufferSize ECUC-INTEGER-PARAM-DEF
BSW Description
Number of bytes to be provided in the input buffer of the interface RequestControlServices_{Tid} for OBD Service $08
Template Description
This represents the specified data size for the request message. Unit: byte.
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x08_RequestControlOfOnBoardDevice::DiagnosticTestRoutineIdentifier.
requestDataSize
Mapping Rule Mapping Type
1:1 mapping full
5

387 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00722]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl
BSW Parameter BSW Type
DcmDspRequestControlOutBufferSize ECUC-INTEGER-PARAM-DEF
BSW Description
Number of bytes to be provided in the output buffer of the interface RequestControlServices_{Tid} for OBD Service $08
Template Description
This represents the specified data size for the response message. Unit:byte.
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x08_RequestControlOfOnBoardDevice::DiagnosticTestRoutineIdentifier.
responseDataSize
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00723]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl
BSW Parameter BSW Type
DcmDspRequestControlTestId ECUC-INTEGER-PARAM-DEF
BSW Description
Test Id for Service $08
Template Description
ObdControlServiceNeeds.testId:
Test Identifier (TID) according to ISO 15031-5.
DiagnosticTestRoutineIdentifier.id:
This represents the numerical id of the DiagnosticTestIdentifier (see SAE J1979-DA).
M2 Parameter
CommonStructure::ServiceNeeds::ObdControlServiceNeeds.testId, DiagnosticExtract::Dcm::ObdService::Mode_0x08_
RequestControlOfOnBoardDevice::DiagnosticTestRoutineIdentifier.id
Mapping Rule Mapping Type
The value shall be taken from DiagnosticRequestControlOfOnBoardDevice.testId.id if available. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00656]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspRequestFileTransfer ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration for RequestFileTransfer. This container only exists if RequestFileTransfer is
configured.
Template Description
5

388 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This diagnostic service instance implements the UDS service 0x38.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::RequestFileTransfer::DiagnosticRequestFileTransfer
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01034]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent/DcmDspRoeEventProperties/Dcm
DspRoeOnChangeOfDataIdentifier
BSW Parameter BSW Type
DcmDspRoeDidRef ECUC-REFERENCE-DEF
BSW Description
Reference to a Did which is watched.
Template Description
This represents the corresponding DiagnosticDataIdentifier.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticDataChangeTrigger.dataIdentifier
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00979]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent/DcmDspRoeEventProperties/Dcm
DspRoeOnDTCStatusChange
BSW Parameter BSW Type
DcmDspRoeDTCStatusMask ECUC-INTEGER-PARAM-DEF
BSW Description
Value of the relevant DTCStatusMask
Template Description
This attribute represents the ability to define a status mask for the triggering of an ROE response on the change of a DTC.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticDtcChangeTrigger.dtcStatusMask
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01109]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent
BSW Parameter BSW Type
DcmDspRoeInitialEventStatus ECUC-ENUMERATION-PARAM-DEF
BSW Description
5

389 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Initial Roe status of this RoeEvent
Template Description
This represents the initial status of the enclosing DiagnosticResponseOnEventTrigger.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticResponseOnEventTrigger.
initialEventStatus
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00980]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent/DcmDspRoeInitialEventStatus
BSW Parameter BSW Type
DCM_ROE_CLEARED ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This means that the ResponseOnEvent is initially cleared.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticInitialEventStatusEnum.
returnOnEventCleared
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEvent/DcmDspRoeInitialEventStatus
BSW Parameter BSW Type
DCM_ROE_STOPPED ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This means that the ResponseOnEvent is initially stopped.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticInitialEventStatusEnum.
returnOnEventStopped
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe
BSW Parameter BSW Type
DcmDspRoeEventWindowTime ECUC-PARAM-CONF-CONTAINER-DEF
5

390 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
This container configures the available EventWindowTime in this Ecu.
This container contains a sub-set of EventWindowTimes supported by the Dcm, to limit the Ecu resources.
Template Description
This attribute clarifies the validity of the eventWindow
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticEventWindow.eventWindowTime
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00981]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEventWindowTime/DcmDspRoeEvent
WindowTime
BSW Parameter BSW Type
DCM_ROE_EVENT_WINDOW_CURRENT_AND_ ECUC-ENUMERATION-LITERAL-DEF
FOLLOWING_CYCLE
BSW Description

Template Description
This means that the window extends to this and the following cycle.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticEventWindowTimeEnum.
eventWindowCurrentAndFollowingCycle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEventWindowTime/DcmDspRoeEvent
WindowTime
BSW Parameter BSW Type
DCM_ROE_EVENT_WINDOW_CURRENT_CYCLE ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This means that the window is limited to the current cycle.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticEventWindowTimeEnum.
eventWindowCurrentCycle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

391 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe/DcmDspRoeEventWindowTime/DcmDspRoeEvent
WindowTime
BSW Parameter BSW Type
DCM_ROE_EVENT_WINDOW_INFINITE ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
This means that the window extents without a border.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticEventWindowTimeEnum.
eventWindowInfinite
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoe
BSW Parameter BSW Type
DcmDspRoeInterMessageTime ECUC-FLOAT-PARAM-DEF
BSW Description
Provide the minimum time in seconds between two transmissions of ROE event. It is used for the delay between two different
consecutive Roe transmissions.
Template Description
Provide the minimum time in seconds between two consecutive transmissions of an ROE event.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::ResponseOnEvent::DiagnosticResponseOnEventClass.interMessageTime
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00856]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspRoutine ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for Routines
Template Description
This meta-class represents the ability to define a diagnostic routine.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRoutine
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00640]

392 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine
BSW Parameter BSW Type
DcmDspRequestRoutineResults ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provides the configuration of RequestResult subservice for RoutineControl service. Existence indicates that the Request
RoutineResults in the RoutineControl is supported.
Template Description
DiagnosticRoutine.requestResult:
This represents the ability to request the result of a running routine.
DiagnosticRoutineNeeds.diagRoutineType:
This denotes the type of diagnostic routine which is implemented by the referenced server port.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRoutine.requestResult, CommonStructure::ServiceNeeds::Diagnostic
RoutineNeeds.diagRoutineType
Mapping Rule Mapping Type
1:1 mapping for DiagnosticRoutine.requestResult OR DiagnosticRoutineNeeds.diagRoutineTyoe full
== asynchronous
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01023]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults
BSW Parameter BSW Type
DcmDspRequestRoutineResultsFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name for request to application the results of a routine. (Routine_RequestResults-function)
This parameter is related to the interface Xxx_RequestResults.
Template Description
Specialization of ServiceDependency in the context of an BswInternalBehavior. It allows to associate BswModuleEntries and
data defined for a BSW module or cluster to a given ServiceNeeds element.
M2 Parameter
BswModuleTemplate::BswBehavior::BswServiceDependency
Mapping Rule Mapping Type
It could be possible to get the FNC name via BswServiceDependency full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00753]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults
BSW Parameter BSW Type
DcmDspRequestRoutineResultsIn ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of input parameter of RequestResult subservice for RoutineControl service.
Template Description
This represents the request parameters.
5

393 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRequestRoutineResults.request
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01116]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn
BSW Parameter BSW Type
DcmDspRequestRoutineResultsInSignal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provides description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents the order of the dataIn_n elements in
the XXX_RequestResult function call.
Template Description
This represents the related dataElement of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01117]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspArgumentScaling/DcmDsp
AlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
5

394 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspArgumentScaling/DcmDsp
AlternativeDataType/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspArgumentScaling/DcmDsp
AlternativeDataType/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal
BSW Parameter BSW Type
DcmDspRoutineParameterSize ECUC-INTEGER-PARAM-DEF
5

395 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
Provide the size of a RoutineControl parameter in bytes
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
Only in case of variable length required (according to constr_6008). Calculation: DcmDspRoutine full
SignalLength = maxNumberOfElements * 8
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01119]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal
BSW Parameter BSW Type
DcmDspRoutineSignalEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a Routine In Signal for RequestResult subfunction.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnostictRequestRoutineResult.response
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01121]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal
BSW Parameter BSW Type
DcmDspRoutineSignalPos ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the position of the signal in the RoutineControl request/response. The position is defined in bits.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01118]

396 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
5

397 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16 array.
5

398 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

399 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Type of the signal is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
5

400 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
Type of the signal is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
5

401 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOf
Elements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either
does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

402 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-32, UTF-32 baseTypeSize = 32 max
NumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics
either does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_
DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP
baseTypeSize = 8
Mapping Status ECUC Parameter ID
5

403 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP
baseTypeSize = 8 maxNumberOfElements exists and value is greater than 0 (cf.TPS_
DEXT_01001) arraySizeSemantics either does not exist or exists and is set to ArraySizeSemantics
Enum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsIn/DcmDspRequestRoutineResultsInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
VARIABLE_LENGTH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8[DcmDspRoutineParameterSize].
This is only valid for the last signal and when DcmDspRoutineSignalType is set to VARIABLE_LENGTH.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
5

404 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE baseTypeSize = 8 arraySizeSemantics =
variableSize maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002)
arraySizeSemantics exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_
DEXT_01002)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults
BSW Parameter BSW Type
DcmDspRequestRoutineResultsOut ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of output parameter of RequestResult subservice for RoutineControl service.
Template Description
This represents the response parameters.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRequestRoutineResults.response
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00831]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut
BSW Parameter BSW Type
DcmDspRequestRoutineResultsOutSignal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provides description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents the order of the dataOutN elements in
the XXX_RequestResult function call.
Template Description
This represents the related dataElement of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00836]

405 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspArgumentScaling/DcmDsp
AlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspArgumentScaling/DcmDsp
AlternativeDataType/DcmDspTextTableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspArgumentScaling/DcmDsp
AlternativeDataType/DcmDspTextTableMapping
BSW Parameter BSW Type
5

406 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal
BSW Parameter BSW Type
DcmDspRoutineParameterSize ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the size of a RoutineControl parameter in bytes
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
Only in case of variable length required (according to constr_6008). Calculation: DcmDspRoutine full
SignalLength = maxNumberOfElements * 8
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00838]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal
BSW Parameter BSW Type
DcmDspRoutineSignalEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a Routine Out Signal for RequestResult subfunction.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnostictRequestRoutineResult.response
5

407 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01013]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal
BSW Parameter BSW Type
DcmDspRoutineSignalPos ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the position of the signal in the RoutineControl request/response. The position is defined in bits.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00837]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

408 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

409 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Type of the signal is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
5

410 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
Type of the signal is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
5

411 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

412 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOf
Elements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either
does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

413 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, UTF-32, UTF-32 baseTypeSize = 32 max
NumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics
either does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_
DEXT_01001)
Mapping Status ECUC Parameter ID
valid

414 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP
baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP
baseTypeSize = 8 maxNumberOfElements exists and value is greater than 0 (cf.TPS_
DEXT_01001) arraySizeSemantics either does not exist or exists and is set to ArraySizeSemantics
Enum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

415 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDspRequest
RoutineResultsOut/DcmDspRequestRoutineResultsOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
VARIABLE_LENGTH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8[DcmDspRoutineParameterSize].
This is only valid for the last signal and when DcmDspRoutineSignalType is set to VARIABLE_LENGTH.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticRequest full
RoutineResults.response baseTypeEncoding = NONE baseTypeSize = 8 arraySizeSemantics =
variableSize maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002)
arraySizeSemantics exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_
DEXT_01002)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine
BSW Parameter BSW Type
DcmDspRoutineIdentifier ECUC-INTEGER-PARAM-DEF
BSW Description
2 bytes Identifier of the RID
Within each DcmConfigSet all DcmDspRoutineIdentifier values shall be unique.
Template Description
DiagnosticRoutine.id:
This is the numerical identifier used to identify the DiagnosticRoutine in the scope of diagnostic workflow
DiagnosticRoutineNeeds.ridNumber:
This represents a routine identifier for the diagnostic routine. This allows to predefine the RID number if the a function
developer has received a particular requirement from the OEM or from a standardization body.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRoutine.id, CommonStructure::ServiceNeeds::DiagnosticRoutineNeeds.
ridNumber
5

416 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00641]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine
BSW Parameter BSW Type
DcmDspRoutineUsePort ECUC-BOOLEAN-PARAM-DEF
BSW Description
If this parameter is set to true, the DCM uses a port requiring a PortInterface RoutineServices_{RoutineName}.
The R-Port is named RoutineServices_{RoutineName} where {RoutineName} is the name of the container DcmDspRoutine
In that case, the configuration must not provide function names in DcmDspStartRoutineFnc, DcmDspStopRoutineFnc or Dcm
DspRequestResultsRoutineFnc. If this is false, the DCM expects to find the names of the functions to be used in DcmDsp
StartRoutineFnc, DcmDspStopRoutineFnc or DcmDspRequestResultsRoutineFnc.
Template Description
This represents the ability to define a mapping of a diagnostic service to a software-component or a basic-software module. If
the former is used then this kind of service mapping is applicable for the usage of ClientServerInterfaces.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping
Mapping Rule Mapping Type
TRUE: DiagnosticServiceSwMapping is having a SwcServiceDependency FALSE: Diagnostic full
ServiceSwMapping is having a BswServiceDependency
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00724]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine
BSW Parameter BSW Type
DcmDspStartRoutine ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provides the configuration of Start subservice for RoutineControl service.
Template Description
DiagnosticRoutine.start:
This represents the ability to start a routine
DiagnosticRoutineNeeds:
Specifies the general needs on the configuration of the Diagnostic Communication Manager (Dcm) which are not related to a
particular item (e.g. a PID). The main use case is the mapping of service ports to the Dcm which are not related to a
particular item.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRoutine.start, CommonStructure::ServiceNeeds::
DiagnosticRoutineNeeds
Mapping Rule Mapping Type
A routine always comes with a start routine, independently of whether the execution is done full
synchronously or asynchronously.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01021]

417 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine
BSW Parameter BSW Type
DcmDspStartRoutineFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name for request to application to start a routine. (Routine_Start-function)
This parameter is related to the interface Xxx_Start.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00664]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine
BSW Parameter BSW Type
DcmDspStartRoutineIn ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of input parameter of Start subservice for RoutineControl service
Template Description
This represents the request parameters.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticStartRoutine.request
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00834]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn
BSW Parameter BSW Type
DcmDspStartRoutineInSignal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents the order of the dataInN elements in
the XXX_Start function call.
Template Description
This represents the related dataElement of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.dataElement
Mapping Rule Mapping Type
5

418 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00845]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDspText
TableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

419 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDspText
TableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal
BSW Parameter BSW Type
DcmDspRoutineParameterSize ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the size of a RoutineControl parameter in bytes
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
"Only in case of variable length required (according to constr_6008). Calculation: DcmDspRoutine full
SignalLength = maxNumberOfElements * 8.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00847]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal
BSW Parameter BSW Type
DcmDspRoutineSignalEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a Routine In Signal for Start subfunction.
Template Description
This attribute specifies the byte order of the base type.
5

420 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnosticStartRoutine.request.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01016]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal
BSW Parameter BSW Type
DcmDspRoutineSignalPos ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the position of the signal in the RoutineControl request/response. The position is defined in bits.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00846]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
valid

421 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

422 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

423 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

424 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either doesnot exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

425 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

426 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE, UTF-32 maxNumberOfElements exists and value is
greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is
set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

427 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8 maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001)
arraySizeSemantics either does not exist or exists and is set to ArraySizeSemanticsEnum.fixed
Size (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

428 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineIn/Dcm
DspStartRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
VARIABLE_LENGTH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8[DcmDspRoutineParameterSize].
This is only valid for the last signal and when DcmDspRoutineSignalType is set to VARIABLE_LENGTH.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.request baseTypeEncoding = NONE baseTypeSize = 8 arraySizeSemantics = variableSize
maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002) arraySize
Semantics exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_DEXT_01002)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine
BSW Parameter BSW Type
DcmDspStartRoutineOut ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of output parameter of Start subservice for RoutineControl service.
Template Description
This represents the response parameters.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticStartRoutine.response
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00835]

429 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut
BSW Parameter BSW Type
DcmDspStartRoutineOutSignal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents the order of the dataOutN elements in
the XXX_Start function call.
Template Description
This represents the related dataElement of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00848]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDsp
TextTableMapping
BSW Parameter BSW Type
5

430 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDsp
TextTableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal
BSW Parameter BSW Type
DcmDspRoutineParameterSize ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the size of a RoutineControl parameter in bytes
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
Only in case of variable length required (according to constr_6008). Calculation: DcmDspRoutine full
SignalLength = maxNumberOfElements * 8.
5

431 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00850]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal
BSW Parameter BSW Type
DcmDspRoutineSignalEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a Routine Out Signal for Start subfunction.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnosticStartRoutine.response
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01017]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal
BSW Parameter BSW Type
DcmDspRoutineSignalPos ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the position of the signal in the RoutineControl request/response. The position is defined in bits.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00867]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is boolean.
Template Description
5

432 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
5

433 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16 array.
Template Description
5

434 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32 array.
5

435 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

436 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Type of the signal is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
5

437 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
Type of the signal is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOf
Elements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemanticseither
does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
5

438 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 maxNumberOf
Elements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemanticseither
does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8
Mapping Status ECUC Parameter ID
valid

439 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8 maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001)
arraySizeSemantics either does not exist or exists and is set to ArraySizeSemanticsEnum.fixed
Size (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutineOut/
DcmDspStartRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
VARIABLE_LENGTH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8[DcmDspRoutineParameterSize].
This is only valid for the last signal and when DcmDspRoutineSignalType is set to VARIABLE_LENGTH.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
5

440 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStart full
Routine.response baseTypeEncoding = NONE baseTypeSize = 8 arraySizeSemantics = variable
Size maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002) arraySize
Semantics exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_DEXT_01002)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine
BSW Parameter BSW Type
DcmDspStopRoutine ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provides the configuration of Stop subservice for RoutineControl service. Existence indicates that the StopRoutine in the
RoutineControl is supported.
Template Description
DiagnosticRoutine.stop:
This represents the ability to stop a running routine.
DiagnosticRoutineNeeds.diagRoutineType:
This denotes the type of diagnostic routine which is implemented by the referenced server port.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticRoutine.stop, CommonStructure::ServiceNeeds::DiagnosticRoutine
Needs.diagRoutineType
Mapping Rule Mapping Type
1:1 mapping for DiagnosticRoutine.stop OR DiagnosticRoutineNeeds.diagRoutineType == full
asynchronous
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01022]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine
BSW Parameter BSW Type
DcmDspStopRoutineFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name for request to application to stop a routine. (Routine_Stop-function)
This parameter is related to the interface Xxx_Stop.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00752]

441 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine
BSW Parameter BSW Type
DcmDspStopRoutineIn ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of input parameter of Stop subservice for RoutineControl service.
Template Description
This represents the request parameters.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticStopRoutine.request
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00832]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn
BSW Parameter BSW Type
DcmDspStopRoutineInSignal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents the order of the dataInN elements in
the XXX_Stop function call.
Template Description
This represents the related dataElement of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00839]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
5

442 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDspText
TableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDspText
TableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

443 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal
BSW Parameter BSW Type
DcmDspRoutineParameterSize ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the size of a RoutineControl parameter in bytes
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
Only in case of variable length required (according to constr_6008). Calculation: DcmDspRoutine full
SignalLength = maxNumberOfElements * 8
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00841]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal
BSW Parameter BSW Type
DcmDspRoutineSignalEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a Routine In Signal for Stop subfunction.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnosticStopRoutine.request
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01014]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal
BSW Parameter BSW Type
DcmDspRoutineSignalPos ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the position of the signal in the RoutineControl request/response. The position is defined in bits.
Template Description
This represents the bitOffset of the DiagnosticParameter
5

444 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00840]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
5

445 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

446 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either doesnot exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

447 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either doesnot exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

448 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

449 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOfElements
exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not
exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 full
Mapping Status ECUC Parameter ID
valid

450 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 maxNumberOfElements exists and value full
is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists and is
set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8
Mapping Status ECUC Parameter ID
valid

451 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8 maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001)
arraySizeSemantics either does not exist or exists and is set to ArraySizeSemanticsEnum.fixed
Size (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineIn/Dcm
DspStopRoutineInSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
VARIABLE_LENGTH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8[DcmDspRoutineParameterSize].
This is only valid for the last signal and when DcmDspRoutineSignalType is set to VARIABLE_LENGTH.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
5

452 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.request baseTypeEncoding = NONE baseTypeSize = 8 arraySizeSemantics = variableSize
maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002) arraySize
Semantics exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_DEXT_01002)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine
BSW Parameter BSW Type
DcmDspStopRoutineOut ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of output parameter of Stop subservice for RoutineControl service.
Template Description
This represents the response parameters.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticStopRoutine.response
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00833]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut
BSW Parameter BSW Type
DcmDspStopRoutineOutSignal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents the order of the dataOutN elements in
the XXX_Stop function call.
Template Description
This represents the related dataElement of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00842]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType
BSW Parameter BSW Type
DcmDspTextTableMapping ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
5

453 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
The purpose of the DcmDspTextTableMapping is to associate a texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Template Description
This meta-class represents the ability to express the relationship between a physical value and the mathematical
representation.
Note that this is still independent of the technical implementation in data types. It only specifies the formula how the internal
value corresponds to its physical pendant.
M2 Parameter
AsamHdo::ComputationMethod::CompuMethod
Mapping Rule Mapping Type
This mapping applies if the CompuMethod.category is set to values TEXTTABLE or SCALE_ full
LINEAR_AND_TEXTTABLE.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00999]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDsp
TextTableMapping
BSW Parameter BSW Type
DcmDspDiagnosisRepresentationDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The data value in the diagnosis representation.
Template Description
This represents a textual constant in the computation method.
M2 Parameter
AsamHdo::ComputationMethod::CompuConstTextContent.vt
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01001]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspArgumentScaling/DcmDspAlternativeDataType/DcmDsp
TextTableMapping
BSW Parameter BSW Type
DcmDspInternalDataValue ECUC-INTEGER-PARAM-DEF
BSW Description
The ECU internal data value.
Template Description
5

454 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
CompuScale.lowerLimit:
This specifies the lower limit of the scale.
CompuScale.upperLimit:
This specifies the upper limit of a of the scale.
M2 Parameter
AsamHdo::ComputationMethod::CompuScale.lowerLimit, AsamHdo::ComputationMethod::CompuScale.upperLimit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01000]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal
BSW Parameter BSW Type
DcmDspRoutineParameterSize ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the size of a RoutineControl parameter in bytes
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
"Only in case of variable length required (according to constr_6008). Calculation: DcmDspRoutine full
SignalLength = maxNumberOfElements * 8
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00844]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal
BSW Parameter BSW Type
DcmDspRoutineSignalEndianness ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the endianness of the data belonging to a Routine Out Signal for Stop subfunction.
Template Description
This attribute specifies the byte order of the base type.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.byteOrder
Mapping Rule Mapping Type
baseType.baseTypeDefinition.byteOrder referenced by swDataDefProps of the Diagnostic full
Parameter with the role DiagnosticStopRoutine.response
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01015]

455 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal
BSW Parameter BSW Type
DcmDspRoutineSignalPos ECUC-INTEGER-PARAM-DEF
BSW Description
Provide the position of the signal in the RoutineControl request/response. The position is defined in bits.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00843]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
BOOLEAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is boolean.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = BOOLEAN baseTypeSize = 1
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
5

456 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16.
Template Description
5

457 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = 2C baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = 2C baseTypeSize = 16 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32.
5

458 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = 2C baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = 2C baseTypeSize = 32 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either does not exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

459 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Type of the signal is sint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = 2C baseTypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
SINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is sint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = 2C baseTypeSize = 8 maxNumberOfElements exists and
value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either doesnot exist or exists
and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16 ECUC-ENUMERATION-LITERAL-DEF
5

460 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
Type of the signal is uint16.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT16_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint16 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE, UTF-16 baseTypeSize = 16 maxNumberOf
Elements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either
does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
5

461 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
UINT32 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT32_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint32 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE, UTF-32 baseTypeSize = 32 maxNumberOf
Elements exists and value is greater than 0 (cf. TPS_DEXT_01001) arraySizeSemantics either
does not exist or exists and is set to ArraySizeSemanticsEnum.fixedSize (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
valid

462 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
UINT8_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8 array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP base
TypeSize = 8 maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01001)
arraySizeSemantics either does not exist or exists and is set to ArraySizeSemanticsEnum.fixed
Size (cf. TPS_DEXT_01001)
Mapping Status ECUC Parameter ID
5

463 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutineOut/
DcmDspStopRoutineOutSignal/DcmDspRoutineSignalType
BSW Parameter BSW Type
VARIABLE_LENGTH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the signal is uint8[DcmDspRoutineParameterSize].
This is only valid for the last signal and when DcmDspRoutineSignalType is set to VARIABLE_LENGTH.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticDataElement.maxNumberOfElements:
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
DiagnosticDataElement.arraySizeSemantics:
This attribute controls the meaning of the value of the array size.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements, Diagnostic
Extract::CommonDiagnostics::DiagnosticDataElement.arraySizeSemantics
Mapping Rule Mapping Type
referenced by swDataDefProps of the DiagnosticParameter with the role DiagnosticStop full
Routine.response baseTypeEncoding = NONE baseTypeSize = 8 arraySizeSemantics = variable
Size maxNumberOfElements exists and value is greater than 0 (cf. TPS_DEXT_01002) arraySize
Semantics exists and is set to ArraySizeSemanticsEnum.variableSize (cf. TPS_DEXT_01002)
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityADRSize ECUC-INTEGER-PARAM-DEF
BSW Description
Size in bytes of the AccessDataRecord used in GetSeed
Template Description
This represents the size of the AccessDataRecord used in GetSeed. Unit:byte.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSecurityLevel.accessDataRecordSize
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00725]

464 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityAttemptCounterEnabled ECUC-BOOLEAN-PARAM-DEF
BSW Description
This configuration parameter controls the existence of the APIs to set / get the attempt counter values towards application
(Xxx_SetSecurityAttemptCounter() / Xxx_GetSecurityAttemptCounter()). In case of enabled, the security attempt counter
values are passed to application, whenever there is a change in the value. This allows storing the values in nonvolatile RAM
and restoring them at ECU startup.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01050]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityCompareKeyFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request the result of a key comparison.
Parameter is only relevant if DcmDspSecurityUsePort=="USE_ ASYNCH_FNC". This parameter is related to the interface
Xxx_CompareKey.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00969]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityDelayTime ECUC-FLOAT-PARAM-DEF
BSW Description
Delay time after failed security access in seconds.
This is started after DcmDspSecurityNumAttDelay number of failed security accesses.
min: A negative value is not allowed.
Template Description
5

465 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This represents the delay time after a failed security access. Unit: second.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSecurityLevel.securityDelayTime
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00757]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityDelayTimeOnBoot ECUC-FLOAT-PARAM-DEF
BSW Description
Value of the delay timer in case of ’power on’ in seconds. This delay indicates the time at ECU boot power-on time during
which the Dcm does not accept a security access.
min: A negative value is not allowed.
Template Description
Start delay timer on power on in seconds.
This delay indicates the time at ECU boot power-on time where the Dcm remains in the default session and does not accept
a security access.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.securityDelayTimeOnBoot
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00726]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityGetAttemptCounterFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to request the value of an attempt counter. This parameter is related to the interface Xxx_ GetSecurityAttempt
Counter.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01048]

466 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityGetSeedFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Callout function name used to request a seed. This parameter is related to the interface Xxx_GetSeed.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00968]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityKeySize ECUC-INTEGER-PARAM-DEF
BSW Description
size of the security key (in Bytes).
Template Description
This represents the size of the security key. Unit: byte.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSecurityLevel.keySize
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00760]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityLevel ECUC-INTEGER-PARAM-DEF
BSW Description
Value of Security level. The locked state cannot be configured explicitly.
1,2,3...63: configuration dependent - Conversion formula to calculate SecurityLevel out of tester requested
SecurityAccessType parameter: SecurityLevel = (SecurityAccessType (requestSeed) + 1) / 2
Type: Dcm_SecLevelType
Template Description
This would be 0x01, 0x03, 0x05, ...
The sendKey id can be computed by adding 1 to the requestSeedId
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::SecurityAccess::DiagnosticSecurityAccess.requestSeedId
5

467 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
DcmDspSecurityLevel=(requestSeedId+1)/2 full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00754]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecurityNumAttDelay ECUC-INTEGER-PARAM-DEF
BSW Description
Number of failed security accesses after which the delay time is activated
Template Description
This represents the number of failed security accesses after which the delay time is activated.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSecurityLevel.numFailedSecurityAccess
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00762]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecuritySeedSize ECUC-INTEGER-PARAM-DEF
BSW Description
size of the security seed (in Bytes).
Template Description
This represents the size of the security seed. Unit: byte.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSecurityLevel.seedSize
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00755]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow
BSW Parameter BSW Type
DcmDspSecuritySetAttemptCounterFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name to set the value of an attempt counter. This parameter is related to the interface Xxx_ SetSecurityAttempt
Counter.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
5

468 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01049]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow/DcmDspSecurityUsePort
BSW Parameter BSW Type
USE_ASYNCH_CLIENT_SERVER ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The DCM will access the data using an R-Port requiring a asynchronous ClientServertInterface SecurityAccess_{Security
Level}.
The R-Port is described in DcmDspSecurityRow description.
Template Description
This represents the ability to point into the component hiearchy (under possible consideration of the rootSoftware
Composition)
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedSwcServiceDependencyInSystem
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow/DcmDspSecurityUsePort
BSW Parameter BSW Type
USE_ASYNCH_FNC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The DCM will access the data using the functions that are defined in the parameters DcmDspSecurityGetSeedFnc and Dcm
DspSecurityCompareKeyFnc as well as the functions defined in DcmDspSecurityGetAttemptCounterFnc and DcmDsp
SecuritySetAttemptCounterFnc, if enabled by the parameter DcmDspSecurityAttemptCounterEnabled.
DCM_E_PENDING return is allowed and OpStatus is existing as IN parameter.
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

469 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow/DcmDspSessionForBoot
BSW Parameter BSW Type
DCM_NO_BOOT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
This diagnostic session doesn’t allow to jump to Bootloader.
Template Description
This diagnostic session doesn’t allow to jump to Bootloader.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticJumpToBootLoaderEnum.noBoot
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow/DcmDspSessionForBoot
BSW Parameter BSW Type
DCM_OEM_BOOT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
This diagnostic session allows to jump to OEM Bootloader and bootloader sends final response.
Template Description
This diagnostic session allows to jump to OEM Bootloader. In this case the bootloader send the final response.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticJumpToBootLoaderEnum.oemBoot
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow/DcmDspSessionForBoot
BSW Parameter BSW Type
DCM_OEM_BOOT_RESPAPP ECUC-ENUMERATION-LITERAL-DEF
BSW Description
This diagnostic session allows to jump to OEM Bootloader and application sends final response.
Template Description
This diagnostic session allows to jump to OEM Bootloader and application sends final response.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticJumpToBootLoaderEnum.oemBootRespApp
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

470 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow/DcmDspSessionForBoot
BSW Parameter BSW Type
DCM_SYS_BOOT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
This diagnostic session allows to jump to System Supplier Bootloader and bootloader sends final response.
Template Description
This diagnostic session allows to jump to System Supplier Bootloader. In this case the bootloader send the final response.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticJumpToBootLoaderEnum.systemSupplierBoot
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow/DcmDspSessionForBoot
BSW Parameter BSW Type
DCM_SYS_BOOT_RESPAPP ECUC-ENUMERATION-LITERAL-DEF
BSW Description
This diagnostic session allows to jump to System Supplier Bootloader and application sends final response.
Template Description
This diagnostic session allows to jump to System Supplier Bootloader and application sends final response.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticJumpToBootLoaderEnum.systemSupplierBootRespApp
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow
BSW Parameter BSW Type
DcmDspSessionLevel ECUC-INTEGER-PARAM-DEF
BSW Description
subFunction value of the DiagnosticSession.
0, 127 and all values above 127 are reserved by ISO
Template Description
This is the numerical identifier used to identify the DiagnosticSession in the scope of diagnostic workflow
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSession.id
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00765]

471 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow
BSW Parameter BSW Type
DcmDspSessionP2ServerMax ECUC-FLOAT-PARAM-DEF
BSW Description
This is the session value for P2ServerMax in seconds (per Session). The AUTOSAR configuration standard is to use SI units,
so this parameter is defined as a float value in seconds. DCM configuration tools must convert this float value to the
appropriate value format for the use in the software implementation of DCM. This value is reported to the tester within the
response to the ’Session Control’ service.
Template Description
This is the session value for P2ServerMax in seconds (per Session Control).
The AUTOSAR configuration standard is to use SI units, so this parameter is defined as a float value in seconds.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSession.p2ServerMax
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00766]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow
BSW Parameter BSW Type
DcmDspSessionP2StarServerMax ECUC-FLOAT-PARAM-DEF
BSW Description
This is the session value for P2*ServerMax in seconds (per Session). The AUTOSAR configuration standard is to use SI
units, so this parameter is defined as a float value in seconds. DCM configuration tools must convert this float value to the
appropriate value format for the use in the software implementation of DCM. This value is reported to the tester within the
response to the ’Session Control’ service.
Template Description
This is the session value for P2*ServerMax in seconds (per Session Control).
The AUTOSAR configuration standard is to use SI units, so this parameter is defined as a float value in seconds.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticSession.p2StarServerMax
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00768]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp
BSW Parameter BSW Type
DcmDspVehInfo ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for one single VehicleInfoType of service $09
Template Description
This meta-class represents the ability to model an instance of the OBD mode 0x09 service.
5

472 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::ObdService::Mode_0x09_RequestVehicleInformation::DiagnosticRequestVehicleInfo
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00630]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo
BSW Parameter BSW Type
DcmDspVehInfoData ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Data Item of an InfoType; ShortName is post-fix of the port interface name.
Template Description
This meta-class represents the ability to describe a concrete piece of data to be taken into account for diagnostic purposes.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement
Mapping Rule Mapping Type
The value shall be taken from DiagnosticRequestVehicleInfo.infoType.dataElement.dataElement. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00888]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData
BSW Parameter BSW Type
DcmDspVehInfoDataOrder ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the order of the data item in the InfoType; values: 0..255; first data item having the order number 0; the next 1 and so
on. The configuration of order needs to be unique per InfoType.
Template Description
This represents the bitOffset of the DiagnosticParameter
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameter.bitOffset
Mapping Rule Mapping Type
Value shall be taken from DiagnosticRequestVehicleInfo.infoType.dataElement.bitOffset. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00891]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData
BSW Parameter BSW Type
DcmDspVehInfoDataReadFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Callout function name for reading InfoType data item. Only required in case parameter ’DcmDspVehInfoDataUsePort’ is set to
’false’
5

473 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency
Mapping Rule Mapping Type
The BswServiceDependency should have aRoleBasedBswModuleEntryAssignment that in turn full
has attribute role set to Xxx_GetInfotypeValueData and points to a BswModuleEntry.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00889]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData
BSW Parameter BSW Type
DcmDspVehInfoDataSize ECUC-INTEGER-PARAM-DEF
BSW Description
Size in bytes of the InfoType data item.
Template Description
The existence of this attribute turns the data instance into an array of data. The attribute determines the size of the array in
terms of how many elements the array can take.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement.maxNumberOfElements
Mapping Rule Mapping Type
Value shall be taken from DiagnosticRequestVehicleInfo.infoType.dataElement.dataElement.max full
NumberOfElements.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00890]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData
BSW Parameter BSW Type
DcmDspVehInfoDataUsePort ECUC-BOOLEAN-PARAM-DEF
BSW Description
When this parameter is set to true the DCM will access the Data using an R-Port requiring a PortInterface IInfotype
Services_{VehInfoData}. The R-Port is named InfotypeServices_{VehInfoData} where {VEHINFODATA} is the name of the
container DcmDspVehInfoData. In that case, the DcmDspVehInfoDataReadFnc is ignored and the RTE APIs are used.
When this parameter is set to false, the DCM calls the function defined in DcmDspVehInfoDataReadFnc.
Template Description
DiagnosticServiceSwMapping.mappedBswServiceDependency:
This is supposed to represent a reference to a BswServiceDependency. the latter is not derived from Referrable and
therefore this detour needs to be implemented to still let BswServiceDependency become the target of a reference.
DiagnosticServiceSwMapping.mappedSwcServiceDependencyInSystem:
This represents the ability to point into the component hiearchy (under possible consideration of the rootSoftware
Composition)
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceSwMapping.mappedBswServiceDependency, Diagnostic
Extract::ServiceMapping::DiagnosticServiceSwMapping.mappedSwcServiceDependencyInSystem
Mapping Rule Mapping Type
5

474 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Shall be set to TRUE if the reference DiagnosticServiceSwMapping.mappedSwcService full
Dependency exists. Shall be set to FALSE if the reference DiagnosticServiceSwMapping.mapped
BswServiceDependency exists.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00727]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo
BSW Parameter BSW Type
DcmDspVehInfoInfoType ECUC-INTEGER-PARAM-DEF
BSW Description
value of InfoType.
Within each DcmConfigSet all DcmDspVehInfoInfoType values shall be unique.
Template Description
ObdInfoServiceNeeds.infoType:
The InfoType according to ISO 15031-5
DiagnosticInfoType.id:
This attribute represents the value of InfoType (see SAE J1979-DA).
M2 Parameter
CommonStructure::ServiceNeeds::ObdInfoServiceNeeds.infoType, DiagnosticExtract::CommonDiagnostics::Diagnostic
InfoType.id
Mapping Rule Mapping Type
If DiagnosticRequestVehicleInfo, us DiagnosticRequestVehicleInfo.infoType.id. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00631]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions
BSW Parameter BSW Type
DcmModeCondition ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration of a mode condition or an environmental conditions which can be used as argument
in DcmModeRules.
One DcmModeCondition shall contain either one DcmSwcModeRef or one DcmBswModeRef or one DcmSwcSRData
ElementRef.
Please note that the Dcm acts as well as mode manager. Therefore the references DcmSwcModeRef or one DcmBswMode
Ref. might point to provided ModeDeclarationGroupPrototypes of the Dcm itself as well as to provided ModeDeclaration
GroupPrototypes of other Bsw Modules or software components.
In case of a configured DcmSwcModeRef or DcmBswModeRef only the DcmConditionType DCM_EQUALS or DCM_
EQUALS_NOT are applicable.
In case of DcmSwcSRDataElementRef all literals of DcmConditionType are possible.
Template Description
DiagnosticCompareConditions are atomic conditions. They are based on the idea of a comparison at runtime of some
variable data with something constant. The type of the comparison (==, !=, <, <=, ...) is specified in DiagnosticCompare
Condition.compareType.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvCompareCondition
Mapping Rule Mapping Type
5

475 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Depending on the reference a DcmModeCondition is mapped to a DiagnosticEnvModeCondition if full
only one reference is present and reference is a DcmSwcModeRef or a DcmBswModeRef. If two
references are present, a DcmSwcSRDataElementRef and a DcmSwcSRDataElementValueRef,
then DcmModeCondition is mapped to a DiagnosticEnvDataCondition.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00928]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition
BSW Parameter BSW Type
DcmBswModeRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
This parameter references a mode of a ModeDeclarationGroupPrototype provided by a Basic Software Module used for the
condition.
Please note that such ModeDeclarationGroupPrototype are owned by a Basic Software Module Description in the role
providedModeGroup.
Template Description
This reference represents both the ModeDeclarationGroupPrototype and the ModeDeclaration relevant for the mode
comparison.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvModeCondition.modeElement
Mapping Rule Mapping Type
For DcmModeRef a new DiagnosticEnvBswModeElement is used, pointing to the ModeDeclaration full
via ModeInModuleDescriptionInstanceRef. This new DiagnosticEnvModeElement shall be
aggregated by the same DiagnosticEnvironmentalConfition as the DiagnosticEnvModeCondition,
in which the target of the reference DiagnosticEnvModeCondition.modeElement points to the this
DiagnosticEnvModeElement.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00931]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmConditionType
BSW Parameter BSW Type
DCM_EQUALS ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isEqual:
equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isEqual
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

476 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmConditionType
BSW Parameter BSW Type
DCM_EQUALS_NOT ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isNotEqual:
not equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isNotEqual
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmConditionType
BSW Parameter BSW Type
DCM_GREATER_OR_EQUAL ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isGreaterOrEqual:
greater than or equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isGreaterOrEqual
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmConditionType
BSW Parameter BSW Type
DCM_GREATER_THAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isGreaterThan:
greater than
5

477 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isGreaterThan
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmConditionType
BSW Parameter BSW Type
DCM_LESS_OR_EQUAL ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isLessOrEqual:
less than or equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isLessOrEqual
Mapping Rule Mapping Type
full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmConditionType
BSW Parameter BSW Type
DCM_LESS_THAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isLessThan:
less than
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isLessThan
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

478 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmSwcDataElementValue/
DcmSwcDataElementArray/DcmSwcDataElementArrayElement
BSW Parameter BSW Type
DcmSwcDataElementArrayElementIndex ECUC-INTEGER-PARAM-DEF
BSW Description
Index to an element of the compare value array.
Template Description
This attribute represents a fixed compare value taken to evaluate the compare condition.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.compareValue
Mapping Rule Mapping Type
DiagnosticDataElement referenced by the DiagnosticEnvDataCondition is an array. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01127]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmSwcDataElementValue/
DcmSwcDataElementArray/DcmSwcDataElementArrayElement
BSW Parameter BSW Type
DcmSwcDataElementArrayElementValue ECUC-INTEGER-PARAM-DEF
BSW Description
Value of an array element compare value.
Template Description
This attribute represents a fixed compare value taken to evaluate the compare condition.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.compareValue
Mapping Rule Mapping Type
DiagnosticDataElement referenced by the DiagnosticEnvDataCondition is an array. full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_01128]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition/DcmSwcDataElementValue/
DcmSwcDataElementPrimitive
BSW Parameter BSW Type
DcmSwcDataElementPrimitiveValue ECUC-INTEGER-PARAM-DEF
BSW Description
Primitive compare value.
Template Description
This attribute represents a fixed compare value taken to evaluate the compare condition.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.compareValue
Mapping Rule Mapping Type
DiagnosticDataElement referenced by the DiagnosticEnvDataCondition is primitive. full
Mapping Status ECUC Parameter ID
5

479 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dcm_01126]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition
BSW Parameter BSW Type
DcmSwcModeRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
This parameter references a mode in a particular mode request port of a software component that is used for the condition.
Template Description
This reference represents both the ModeDeclarationGroupPrototype and the ModeDeclaration relevant for the mode
comparison.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvModeCondition.modeElement
Mapping Rule Mapping Type
For DcmModeRef a new DiagnosticEnvSwcModeElement is used, pointing to the ModeDeclaration full
via PModeInSystemInstanceRef. This new DiagnosticEnvModeElement shall be aggregated by the
same DiagnosticEnvironmentalConfition as the DiagnosticEnvModeCondition, in which the target
of the reference DiagnosticEnvModeCondition.modeElement points to the this DiagnosticEnvMode
Element.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00930]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeCondition
BSW Parameter BSW Type
DcmSwcSRDataElementRef ECUC-CHOICE-REFERENCE-DEF
BSW Description
Reference to environmental conditions. It is possible to reference a S/R Receiver-Port to read physical values and compare
(equal, greater, less,...) them with a configured value that is defined by DcmSwcDataElementValue.
Template Description
This reference represents the related diagnostic data element.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_001037]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions
BSW Parameter BSW Type
DcmModeRule ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration of a mode rule which represents a logical expression with DcmModeConditions or
other DcmModeRules as arguments.
All arguments are processed with the operator defined by DcmLogicalOperator, for instance: Argument_A AND Argument_B
AND Argument_C
5

480 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
A DiagnosticEnvConditionFormula embodies the computation instruction that is to be evaluated at runtime to determine if the
DiagnosticEnvironmentalCondition is currently present (i.e. the formula is evaluated to true) or not (otherwise). The formula
itself consists of parts which are combined by the logical operations specified by DiagnosticEnvConditionFormula.op.
If a diagnostic functionality cannot be executed because an environmental condition fails then the diagnostic stack shall send
a negative response code (NRC) back to the client. The value of the NRC is directly related to the specific formula and is
therefore formalized in the attribute DiagnosticEnvConditionFormula.nrcValue.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula
Mapping Rule Mapping Type
A DcmModeRule is mapped to a DiagnosticEnvConditionFormula, if this DcmModeRule is a full
subrule, i.e. it is referenced by a DcmArgumentRef. In addition, a new DiagnosticEnvironmental
Condition shall be created with DiagnosticEnvironmentalCondition.formula containing a Diagnostic
EnvConditionFormula. In both cases, if no DcmLogicalOperator is present in this DcmModeRule,
then DiagnosticEnvConditionFormula shall be set to DiagnosticLogicalOperatorEnum.logicalAnd.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00925]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeRule
BSW Parameter BSW Type
DcmArgumentRef ECUC-CHOICE-REFERENCE-DEF
BSW Description
This is a choice reference either to a mode condition or a an other mode rule serving as sub-expression.
Template Description
A DiagnosticEnvConditionFormulaPart can either be a atomic condition, e.g. a DiagnosticEnvCompareCondition, or a
DiagnosticEnvConditionFormula, again, which allows arbitrary nesting.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormulaPart
Mapping Rule Mapping Type
Depending on the destination, one DcmArgumentRef is mapped to a DiagnosticEnvCondition full
Formula if "destination" is a DcmModeRule, and to a DiagnosticEnvCompareCondition, if
"destination" is a DcmModeCondition. The order of the aggregation of the DiagnosticEnvCondition
FormulaParts shall correspond to the ordering of the index of the DcmArgumentRefs.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00927]

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeRule/DcmLogicalOperator
BSW Parameter BSW Type
DCM_AND ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticLogicalOperatorEnum.logicalAnd:
Logical AND
M2 Parameter
5

481 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticLogicalOperatorEnum.logicalAnd
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeRule/DcmLogicalOperator
BSW Parameter BSW Type
DCM_OR ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticLogicalOperatorEnum.logicalOr:
Logical OR
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticLogicalOperatorEnum.logicalOr
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dcm Dcm/DcmConfigSet/DcmProcessingConditions/DcmModeRule
BSW Parameter BSW Type
DcmModeRuleNrcValue ECUC-INTEGER-PARAM-DEF
BSW Description
Optional parameter which defines the NRC to be sent in case the mode rule condition is not valid.
Template Description
This attribute represents the concrete NRC value that shall be returned if the condition fails.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.nrcValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00949]

BSW Module BSW Context

Dcm Dcm/DcmGeneral
BSW Parameter BSW Type
DcmDDDIDStorage ECUC-BOOLEAN-PARAM-DEF
BSW Description
5

482 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This configuration switch defines, whether DDDID definition is stored non-volatile or not.
true: DDDID are stored non-volatile false: DDDID are only maintained volatile
Template Description
This configuration switch defines whether DDDID definition is handled as non-volatile information or not.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::DynamicallyDefineDataIdentifier::DiagnosticDynamicallyDefineDataIdentifier
Class.configurationHandling
Mapping Rule Mapping Type
volatile -> false, nonVolatile -> true full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00971]

BSW Module BSW Context

Dcm Dcm/DcmGeneral
BSW Parameter BSW Type
DcmRespondAllRequest ECUC-BOOLEAN-PARAM-DEF
BSW Description
If set to FALSE the Dcm will not respond to diagnostic request that contains a service ID which is in the range from 0x40 to
0x7F or in the range from 0xC0 to 0xFF (Response IDs).
Template Description
If set to FALSE the DCM will not respond to diagnostic request that contains a service ID which is in the range from 0x40 to
0x7F or in the range from 0xC0 to 0xFF (Response IDs).
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.responseOnAllRequestSids
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00600]

BSW Module BSW Context

Dcm Dcm/DcmGeneral
BSW Parameter BSW Type
DcmVinRef ECUC-REFERENCE-DEF
BSW Description
Reference to the Did containing the VIN Information.
This parameter is needed for function Dcm_GetVin
Template Description
This meta-class represents the ability to model a diagnostic data identifier (DID) that is fully specified regarding the payload at
configuration-time.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataIdentifier
Mapping Rule Mapping Type
This reference shall only apply to a DiagnosticDataIdentifier where the attribute representsVin is full
set to true.
Mapping Status ECUC Parameter ID
valid [ECUC_Dcm_00984]

483 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

E.3 Dem
BSW Module BSW Context
Dem Dem/DemConfigSet/DemDTC
BSW Parameter BSW Type
DemDTCFunctionalUnit ECUC-INTEGER-PARAM-DEF
BSW Description
DTCFuncitonalUnit is a 1-byte value which identifies the corresponding basic vehicle / system function which reports the
DTC. This parameter is necessary for the report of severity information.
If this parameter is configured for no DTC, the Dem provides no DTC functional unit information.
Template Description
This attribute specifies a 1-byte value which identifies the corresponding basic vehicle / system function which reports the
DTC. This parameter is necessary for the report of severity information.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeUds.functionalUnit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00643]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTC
BSW Parameter BSW Type
DemDTCSeverity ECUC-ENUMERATION-PARAM-DEF
BSW Description
DTC severity according to ISO 14229-1. This parameter depends on the automotive manufacturer.
If it is not configured, the value is counted as ’no severity’. If this parameter is configured for no DTC, the Dem provides no
DTC severity information.
Template Description
DTC severity according to ISO 14229-1.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeUds.severity
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00645]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTC
BSW Parameter BSW Type
DemWWHOBDDTCClass ECUC-ENUMERATION-PARAM-DEF
BSW Description
DTC Class according to ISO 14229-1 [2013 version]. This parameter depends on the automotive manufacturer. If it is not
configured, the value is marked as ’unclassified’. If this parameter is configured for no DTC, the Dem provides no DTC
WWHOBD class information.
Template Description
This attribute is used to identify (if applicable) the corresponding severity class of an WWH-OBD DTC.
5

484 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeUds.wwhObdDtcClass
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00912]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemAgingAllowed ECUC-BOOLEAN-PARAM-DEF
BSW Description
Defines if a DTC can be aged.
TRUE: aging allowed FALSE: aging not allowed
Template Description
Reference to an aging algorithm in case that an aging/unlearning of the event is allowed.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.aging
Mapping Rule Mapping Type
Shall be set to true if DiagnosticTroubleCodeProps.aging exists. Shall be set to false if Diagnostic full
TroubleCodeProps.aging does not exist.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00622]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemAgingCycleCounterThreshold ECUC-INTEGER-PARAM-DEF
BSW Description
Number of aging cycles needed to unlearn/delete the event.
Template Description
Number of aging cycles needed to unlearn/delete the event.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticAging::DiagnosticAging.threshold
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00623]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemAgingCycleRef ECUC-REFERENCE-DEF
BSW Description
5

485 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Reference to the cycle which is triggering the aging of the event.
Template Description
This represents the applicable aging cycle.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticAging::DiagnosticAging.agingCycle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00624]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemDTCPriority ECUC-INTEGER-PARAM-DEF
BSW Description
Priority of the event/dtc, in view of full event memory. A lower value means higher priority.
Template Description
Priority of the event, in view of full event buffer. A lower value means higher priority.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.priority
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00662]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemDTCSignificance ECUC-ENUMERATION-PARAM-DEF
BSW Description
Significance of the event, which indicates additional information concerning fault classification and resolution.
It can be mapped as Dem-internal data element. It shall be configured, if it is a part of event related data.
Template Description
Significance of the event, which indicates additional information concerning fault classification and resolution.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.significance
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00779]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes/DemDTCSignificance
BSW Parameter BSW Type
5

486 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DEM_EVENT_SIGNIFICANCE_OCCURRENCE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
issue, which indicates additional information concerning insufficient system behavior
Template Description
Issue, which indicates additional information concerning insufficient system behavior.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticSignificanceEnum.occurence
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemMaxNumberFreezeFrameRecords ECUC-INTEGER-PARAM-DEF
BSW Description
This parameter defines the number of according freeze frame records, which can maximal be stored for this event. Therefore
all these freeze frame records have the same freeze frame class.
This parameter is only required for calculated record numeration (refer to DemTypeOfFreezeFrameRecordNumeration).
Template Description
This attribute defines the number of according freeze frame records, which can maximal be stored for this event. Therefore all
these freeze frame records have the same freeze frame class.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.maxNumberFreezeFrameRecords
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00605]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDTCAttributes
BSW Parameter BSW Type
DemMemoryDestinationRef ECUC-CHOICE-REFERENCE-DEF
BSW Description
The memory destination assigns DTCs to one or two memory destinations. If more than one memory destination is assigned
to a specific DTC, the DTC can be present in the corresponding event memories. In this case one of the references has to be
DemMirrorMemory (SWS_Dem_CONSTR_6104).
Template Description
The event destination assigns events to none, one or multiple origins.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.memoryDestination
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00890]

487 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemCounterBasedFdcThresholdStorageValue ECUC-INTEGER-PARAM-DEF
BSW Description
Threshold to allocate an event memory entry and to capture the Freeze Frame.
Template Description
Threshold to allocate an event memory entry and to capture the Freeze Frame.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterBasedFdcThresholdStorageValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00914]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceBehavior ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines how the event debounce algorithm will behave, if a related enable condition is not fulfilled or Control
DTCSetting of the related event is disabled.
Template Description
This attribute defines how the event debounce algorithm will behave, if a related enable condition is not fulfilled or Control
DTCSetting of the related event is disabled.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceAlgorithmProps.debounceBehavior
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00786]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass/DemDebounceBehavior
BSW Parameter BSW Type
DEM_DEBOUNCE_FREEZE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The event debounce counter will be frozen with the current value and will not change while a related enable condition is not
fulfilled or ControlDTCSetting of the related event is disabled. After all related enable conditions are fulfilled and Control
DTCSetting of the related event is enabled again, the event qualification will continue with the next report of the event (i.e. Set
EventStatus).
Template Description
The event debounce counter will be frozen with the current value and will not change while a related enable condition is not
fulfilled or ControlDTCSetting of the related event is disabled. After all related enable conditions are fulfilled and Control
DTCSetting of the related event is enabled again, the event qualification will continue with the next report of the event (i.e. Set
EventStatus).
M2 Parameter
5

488 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceBehaviorEnum.freeze
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass/DemDebounceBehavior
BSW Parameter BSW Type
DEM_DEBOUNCE_RESET ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The event debounce counter will be reset to initial value if a related enable condition is not fulfilled or ControlDTCSetting of
the related event is disabled. The qualification of the event will be restarted with the next valid event report.
Template Description
The event debounce counter will be reset to initial value if a related enable condition is not fulfilled or ControlDTCSetting of
the related event is disabled. The qualification of the event will be restarted with the next valid event report.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceBehaviorEnum.reset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterDecrementStepSize ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the step size for decrementation of the internal debounce counter (PREPASSED).
Template Description
This value shall be taken to decrement the internal debounce counter.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterDecrementStepSize
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterDecrementStepSize. Applicable if DiagnosticExtract::Diagnostic
CommonProps.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00635]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterFailedThreshold ECUC-INTEGER-PARAM-DEF
BSW Description
5

489 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Defines the value of the internal debounce counter, which indicates the failed status.
Template Description
This value defines the event-specific limit that indicates the "failed" counter status.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterFailedThreshold
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterFailedThreshold. Applicable if DiagnosticExtract::Diagnostic
CommonProps.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00618]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterIncrementStepSize ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the step size for incrementation of the internal debounce counter (PREFAILED).
Template Description
This value shall be taken to increment the internal debounce counter.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterIncrementStepSize
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterIncrementStepSize. Applicable if DiagnosticExtract::Diagnostic
CommonProps.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00637]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterJumpDown ECUC-BOOLEAN-PARAM-DEF
BSW Description
Switch for the activation of Jump-Down.
true: Jump-Down activated false: Jump-Down deactivated
Template Description
This value activates or deactivates the counter jump-down behavior.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterJumpDown
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterJumpDown. Applicable if DiagnosticExtract::DiagnosticCommon
Props.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
5

490 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00685]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterJumpDownValue ECUC-INTEGER-PARAM-DEF
BSW Description
Jump-Down value of the internal debounce counter which is taken as initialization value for the counter when the respective
step-down occurs.
Template Description
This value represents the initial value of the internal debounce counter if the counting direction changes from incrementing to
decrementing.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterJumpDownValue
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterJumpDownValue. Applicable if DiagnosticExtract::Diagnostic
CommonProps.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00638]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterJumpUp ECUC-BOOLEAN-PARAM-DEF
BSW Description
Switch for the activation of Jump-Up.
true: Jump-Up activated false: Jump-Up deactivated
Template Description
This value activates or deactivates the counter jump-up behavior.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterJumpUp
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterJumpUp. Applicable if DiagnosticExtract::DiagnosticCommon
Props.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00686]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterJumpUpValue ECUC-INTEGER-PARAM-DEF
BSW Description
5

491 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Jump-Up value of the internal debounce counter which is taken as initialization value for the counter when the respective
step-up occurs.
Template Description
This value represents the initial value of the internal debounce counter if the counting direction changes from decrementing to
incrementing.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterJumpUpValue
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterJumpValue. Applicable if DiagnosticExtract::DiagnosticCommon
Props.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00639]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterPassedThreshold ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the value of the internal debounce counter, which indicates the passed status.
Template Description
This value defines the event-specific limit that indicates the "passed" counter status.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased.counterPassedThreshold
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::DiagnosticCommonProps.debounceAlgorithm full
Props.debounceAlgorithm.counterPassedThreshold. Applicable if DiagnosticExtract::Diagnostic
CommonProps.debounceAlgorithmProps.debounceAlgorithm is modeled by means of a DiagEvent
DebounceCounterBased.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00636]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceCounterBasedClass
BSW Parameter BSW Type
DemDebounceCounterStorage ECUC-BOOLEAN-PARAM-DEF
BSW Description
Switch to store the debounce counter value non-volatile or not.
true: debounce counter value shall be stored non-volatile false: debounce counter value is volatile
Template Description
Switch to store the debounce counter value non-volatile or not.
true: debounce counter value shall be stored non-volatile
false: debounce counter value is volatile
M2 Parameter
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceAlgorithmProps.
debounceCounterStorage
5

492 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00791]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceTimeBaseClass
BSW Parameter BSW Type
DemDebounceBehavior ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines how the event debounce algorithm will behave, if a related enable condition is not fulfilled or Control
DTCSetting of the related event is disabled.
Template Description
This attribute defines how the event debounce algorithm will behave, if a related enable condition is not fulfilled or Control
DTCSetting of the related event is disabled.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceAlgorithmProps.debounceBehavior
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00789]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceTimeBaseClass/DemDebounceBehavior
BSW Parameter BSW Type
DEM_DEBOUNCE_FREEZE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The event debounce timer will be frozen with the current value and will not change while a related enable condition is not
fulfilled or ControlDTCSetting of the related event is disabled. After all related enable conditions are fulfilled and Control
DTCSetting of the related event is enabled again, the event qualification will continue with the next report of the event (i.e. Set
EventStatus).
Template Description
The event debounce counter will be frozen with the current value and will not change while a related enable condition is not
fulfilled or ControlDTCSetting of the related event is disabled. After all related enable conditions are fulfilled and Control
DTCSetting of the related event is enabled again, the event qualification will continue with the next report of the event (i.e. Set
EventStatus).
M2 Parameter
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceBehaviorEnum.freeze
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceTimeBaseClass/DemDebounceBehavior
BSW Parameter BSW Type
DEM_DEBOUNCE_RESET ECUC-ENUMERATION-LITERAL-DEF
5

493 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
The event debounce timer will be reset to initial value if a related enable condition is not fulfilled or ControlDTCSetting of the
related event is disabled. The qualification of the event will be restarted with the next valid event report.
Template Description
The event debounce counter will be reset to initial value if a related enable condition is not fulfilled or ControlDTCSetting of
the related event is disabled. The qualification of the event will be restarted with the next valid event report.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticDebouncingAlgorithm::DiagnosticDebounceBehaviorEnum.reset
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceTimeBaseClass
BSW Parameter BSW Type
DemDebounceTimeFailedThreshold ECUC-FLOAT-PARAM-DEF
BSW Description
Defines the time out duration for "Event Failed" qualification.
The AUTOSAR configuration standard is to use SI units, so this parameter is defined as float value in seconds. Dem
configuration tools must convert this float value to the appropriate value format for the use in the software implementation of
Dem.
Template Description
This value represents the event-specific delay indicating the "failed" status.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceTimeBased.timeFailedThreshold
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00716]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceTimeBaseClass
BSW Parameter BSW Type
DemDebounceTimePassedThreshold ECUC-FLOAT-PARAM-DEF
BSW Description
Defines the time out duration for "Event Passed" qualification.
The AUTOSAR configuration standard is to use SI units, so this parameter is defined as float value in seconds. Dem
configuration tools must convert this float value to the appropriate value format for the use in the software implementation of
Dem.
Template Description
This value represents the event-specific delay indicating the "passed" status.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceTimeBased.timePassedThreshold
Mapping Rule Mapping Type
1:1 mapping full
5

494 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00717]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDebounceTimeBaseClass
BSW Parameter BSW Type
DemTimeBasedFdcThresholdStorageValue ECUC-FLOAT-PARAM-DEF
BSW Description
Threshold to allocate an event memory entry and to capture the Freeze Frame.
Template Description
Threshold to allocate an event memory entry and to capture the Freeze Frame.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceTimeBased.timeBasedFdcThresholdStorageValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00915]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr
BSW Parameter BSW Type
DemDtrEventRef ECUC-REFERENCE-DEF
BSW Description
Reference to the DemEventParameter this DTR is related to. If the related event is not configured, the Dem cannot ensure
consistency between the DTR and the event.
Template Description
DiagnosticTestResult:
This meta-class represents the ability to define diagnostic test results.
DiagnosticEvent:
This element is used to configure DiagnosticEvents.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticTestResult, DiagnosticExtract::Dem::DiagnosticEvent::
DiagnosticEvent
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00808]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr
BSW Parameter BSW Type
DemDtrId ECUC-INTEGER-PARAM-DEF
BSW Description
The index identifier value assigned to this DTR. The value is generated during the Dem configuration process.
Template Description
5

495 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter

Mapping Rule Mapping Type

local
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00807]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr
BSW Parameter BSW Type
DemDtrMid ECUC-INTEGER-PARAM-DEF
BSW Description
The OBDMID of the DTR.
The values 0x00, 0x20, 0x40, 0x60, 0x80, 0xA0, 0xC0, 0xE0 are reserved.
Template Description
This represents the numerical measurement Id
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticMeasurementIdentifier.obdMid
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00809]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr
BSW Parameter BSW Type
DemDtrTid ECUC-INTEGER-PARAM-DEF
BSW Description
The OBDTID of the DTR.
Template Description
This represents the numerical id associated with the diagnostic test identifier.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticTestIdentifier.id
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00810]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr
BSW Parameter BSW Type
DemDtrUasid ECUC-INTEGER-PARAM-DEF
BSW Description
The UaSId the DTR data shall be scaled to, and reported together with the rescaled DTR data.
Template Description
5

496 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This represents the unit and scaling Id of the diagnostic test result.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticTestIdentifier.uasId
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00811]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr
BSW Parameter BSW Type
DemDtrUpdateKind ECUC-ENUMERATION-PARAM-DEF
BSW Description
Update conditions applied by the Dem to reports of DTR values. Only supported if a related Event is configured
Template Description
This attribute controls the update behavior of the enclosing DiagnosticTestResult.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticTestResult.updateKind
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00812]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr/DemDtrUpdateKind
BSW Parameter BSW Type
DEM_DTR_UPDATE_ALWAYS ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Any DTR result reported by the monitor is used by the Dem.
Template Description
Any DTR result reported by the monitor is used by the Dem.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticTestResultUpdateEnum.always
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemDtrs/DemDtr/DemDtrUpdateKind
BSW Parameter BSW Type
DEM_DTR_UPDATE_STEADY ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The Dem accepts reported DTRs only when the configured debouncing mechanism is stable at the FAIL or PASS limit.
5

497 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
The Dem accepts reported DTRs only when the configured debouncing mechanism is stable at the FAIL or PASS limit.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTestResult::DiagnosticTestResultUpdateEnum.steady
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemCallbackClearEventAllowed ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The presence of this container indicates that the Dem has access to a "ClearEventAllowed" callback.
In case there is a DemCallbackClearEventAllowedFnc, this parameter defines the name of the function that the Dem will call.
In case there is no DemCallbackClearEventAllowedFnc, the Dem will have an R-Port requiring the interface CallbackClear
EventAllowed whose name is generated by using the unique callback-prefix followed by the event name.
Template Description
In case the clearing of a Diagnostic Event has to be allowed or prohibited through the SWC interface CallbackClearEvent
Allowed, the SWC has to indicate this by defining appropriate ServiceNeeds (i.e. DiagnosticEventNeeds).
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEventClearAllowedEnum.requiresCallbackExecution
Mapping Rule Mapping Type
Shall be taken from DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent::DiagnosticEvent full
ClearAllowedEnum.requiresCallbackExecution. If literal requiresCallbackExecution is set, the BSW
container DemCallbackClearEventAllowed will be present. Dem will call the funtion named by
configuration parameter DemCallbackClearEventAllowedFnc. If no such function name is
provided, Dem will require an R-Port with the interface name using the unique callback-prefix
followed by the event name.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00607]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemCallbackClearEventAllowed
BSW Parameter BSW Type
DemCallbackClearEventAllowedFnc ECUC-FUNCTION-NAME-DEF
BSW Description
Function name of prototype "ClearEventAllowed".
Template Description
This attribute defines whether the Dem has access to a "ClearEventAllowed" callback.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.eventClearAllowed
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00609]

498 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemCallbackClearEventAllowed
BSW Parameter BSW Type
DemClearEventAllowedBehavior ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the resulting UDS status byte for the related event, which must not be cleared according to the ClearEventAllowed
callback.
Template Description
This attribute defines the resulting UDS status byte for the related event, which shall not be cleared according to the Clear
EventAllowed callback
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.clearEventAllowedBehavior
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00788]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemCallbackClearEventAllowed/DemClearEvent
AllowedBehavior
BSW Parameter BSW Type
DEM_NO_STATUS_BYTE_CHANGE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The UDS status byte keeps unchanged.
Template Description
The event status byte keeps unchanged.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticClearEventAllowedBehaviorEnum.noStatusByteChange
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemCallbackClearEventAllowed/DemClearEvent
AllowedBehavior
BSW Parameter BSW Type
DEM_ONLY_THIS_CYCLE_AND_READINESS ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The <...>ThisOperationCycle and readiness bits of the UDS status byte are reset.
Template Description
The OperationCycle and readiness bits of the event status byte are reset.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticClearEventAllowedBehaviorEnum.onlyThisCycleAndReadiness
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

499 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemDebounceAlgorithmClass ECUC-CHOICE-CONTAINER-DEF
BSW Description
Debounce algorithm class: counter based, time based, or monitor internal.
Template Description
This class represents the ability to specify the pre-debounce algorithm which is selected and/or required by the particular
monitor.
This class inherits from Identifiable in order to allow further documentation of the expected or implemented debouncing and to
use the category for the identification of the expected / implemented debouncing.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceAlgorithm
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00604]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass
BSW Parameter BSW Type
DemDebounceCounterBased ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for counter based debouncing.
Template Description
This meta-class represents the ability to indicate that the counter-based debounce algorithm shall be used by the DEM for
this diagnostic monitor.
This is related to set the ECUC choice container DemDebounceAlgorithmClass to DemDebounceCounterBased.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceCounterBased
Mapping Rule Mapping Type
There are two ways to derive the existence of DemDebounceCounterBased: 1. DiagEvent full
Needs,diagEventDebounceAlgoritm exists and is modeled as a DiagEventDebounceCounter
Based. 2. DiagnosticContributionSet.commonProperties.debounceAlgorithmProps.debounce
Algorithm exists and is modeled as a DiagEventDebounceCounterBased If both alternatives exist
at the same time then the definition ot DiagnosticContributionSet.commonProperties.debounce
AlgorithmProps.debounceAlgorithm shall be handled with priority.
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00711]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass
BSW Parameter BSW Type
DemDebounceMonitorInternal ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
5

500 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This container contains the configuration (parameters) for monitor internal debouncing.
Template Description
"This meta-class represents the ability to indicate that no Dem pre-debounce algorithm shall be used for this diagnostic
monitor. The SWC might implement an internal debouncing algorithm and report qualified (debounced) results to the Dem/
DM.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceMonitorInternal
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00712]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass
BSW Parameter BSW Type
DemDebounceTimeBase ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for time based debouncing.
Template Description
This meta-class represents the ability to indicate that the time-based pre-debounce algorithm shall be used by the Dem for
this diagnostic monitor.
This is related to set the EcuC choice container DemDebounceAlgorithmClass to DemDebounceTimeBase.
M2 Parameter
CommonStructure::ServiceNeeds::DiagEventDebounceTimeBased
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00713]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemEnableConditionGroupRef ECUC-REFERENCE-DEF
BSW Description
References an enable condition group.
Template Description
Defines which EnableConditionGroup is applicable for a DiagnosticEvent.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticEventToEnableConditionGroupMapping
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00746]

501 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemEventAssociatedIdentification ECUC-INTEGER-PARAM-DEF
BSW Description
Event associated identifier that allows to identify an event. This value can be reported as internal data element in snapshot
records or extended data records.
Template Description
This attribute represents the identification number that is associated with the enclosing DiagnosticEvent and allows to identify
it when placed into a snapshot record or extended data record storage.
This value can be reported as internal data element in snapshot records or extended data records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.associatedEventIdentification
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00969]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemEventConfirmationThreshold ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the operation cycle threshold of the DTC confirmation status according "Confirmation Threshold" of ISO 14229-1.
Template Description
This attribute defines the number of operation cycles with a failed result before a confirmed DTC is set to 1. The semantic of
this attribute is a by "1" increased value compared to the confirmation threshold of the "trip counter" mentioned in ISO
14229-1 in figure D.4. A value of "1" defines the immediate confirmation of the DTC along with the first reported failed. This is
also sometimes called "zero trip DTC". A value of "2" defines a DTC confirmation in the operation cycle after the first occurred
failed. A value of "2" is typically used in the US for OBD DTC confirmation.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.confirmationThreshold
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00924]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemEventKind ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter is used to distinguish between SW-C and BSW events.
Template Description
This attribute is used to distinguish between SWC and BSW events.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.eventKind
5

502 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00660]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemEventKind
BSW Parameter BSW Type
DEM_EVENT_KIND_BSW ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The event is a assigned to a BSW module
Template Description
The event is assigned to a BSW module.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEventKindEnum.bsw
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemEventKind
BSW Parameter BSW Type
DEM_EVENT_KIND_SWC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The event is a assigned to a SW-C
Template Description
The event is assigned to a SWC.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEventKindEnum.swc
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemEventRecoverableInSameOperationCycle ECUC-BOOLEAN-PARAM-DEF
BSW Description
If parameter is configured to FALSE, reporting of PASSED will be ignored if the event is already "testfailed this operation
cycle".
Template Description
If the attribute is set to true then reporting PASSED will reset the indication of a failed test in the current operation cycle. If the
attribute is set to false then reporting PASSED will be ignored and not lead to a reset of the indication of a failed test.
5

503 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.recoverableInSameOperationCycle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00916]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemFFPrestorageSupported ECUC-BOOLEAN-PARAM-DEF
BSW Description
If this parameter is set to true, then the Prestorage of FreezeFrames is supported by the assigned event. This parameter is
useful to calculate the buffer size.
Template Description
This attribute describes whether the Prestorage of FreezeFrames is supported by the assigned event or not.
True: Prestorage of FreezeFrames is supported
False: Prestorage of FreezeFrames is not supported
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.prestorageFreezeFrame
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00671]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute
BSW Parameter BSW Type
DemIndicatorBehaviour ECUC-ENUMERATION-PARAM-DEF
BSW Description
Behaviour of the linked indicator
Template Description
Behavior of the linked indicator.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicator.behavior
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00682]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute/DemIndicatorBehaviour
BSW Parameter BSW Type
DEM_INDICATOR_BLINKING ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

504 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
The indicator blinks when the event has status FAILED Not relevant with J1939.
Template Description
The indicator blinks when the event has status FAILED.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicatorBehaviorEnum.blinkMode
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute/DemIndicatorBehaviour
BSW Parameter BSW Type
DEM_INDICATOR_BLINK_CONT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The indicator is active and blinks when the event has status FAILED Not relevant with J1939.
Template Description
The indicator is active and blinks when the event has status FAILED.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicatorBehaviorEnum.blinkOrContinuousOnMode
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute/DemIndicatorBehaviour
BSW Parameter BSW Type
DEM_INDICATOR_CONTINUOUS ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The indicator is active when the even has status FAILED
Template Description
The indicator is active when the event has status FAILED.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicatorBehaviorEnum.continuousOnMode
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute/DemIndicatorBehaviour
BSW Parameter BSW Type
DEM_INDICATOR_FAST_FLASH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
5

505 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Flash Indicator Lamp should be set to ’Fast Flash’
Template Description
Flash Indicator Lamp should be set to "Fast Flash".
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicatorBehaviorEnum.fastFlashingMode
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute/DemIndicatorBehaviour
BSW Parameter BSW Type
DEM_INDICATOR_SLOW_FLASH ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Flash Indicator Lamp should be set to ’Slow Flash’
Template Description
Flash Indicator Lamp should be set to "Slow Flash".
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicatorBehaviorEnum.slowFlashingMode
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter/DemIndicatorAttribute
BSW Parameter BSW Type
DemIndicatorHealingCycleCounterThreshold ECUC-INTEGER-PARAM-DEF
BSW Description
Defines the number of healing cycles for the WarningIndicatorOffCriteria.
Template Description
This attribute defines the number of healing cycles for the WarningIndicatorOffCriteria
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticConnectedIndicator.healingCycleCounterThreshold
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00748]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemEventParameter
BSW Parameter BSW Type
DemStorageConditionGroupRef ECUC-REFERENCE-DEF
5

506 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
References a storage condition group.
Template Description
Defines which StorageConditionGroup is applicable for a DiagnosticEvent.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticEventToStorageConditionGroupMapping
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00769]

BSW Module BSW Context

Dem Dem/DemConfigSet
BSW Parameter BSW Type
DemMultiEventTriggering ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
Configures an event that will trigger other events whenever the event is reported.
Template Description
This meta-class provides the ability to map a master diagnostic event with a slave diagnostic event such that reporting of the
master event with a given value also reports the slave event with the same value
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticMasterToSlaveEventMapping
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00944]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemMultiEventTriggering
BSW Parameter BSW Type
DemMultiEventTriggeringMasterEventRef ECUC-REFERENCE-DEF
BSW Description
Reference to the event that will trigger other events upon reception of this event.
Template Description
This represents the master diagnostic event.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticMasterToSlaveEventMapping.masterEvent
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00945]

507 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemConfigSet/DemMultiEventTriggering
BSW Parameter BSW Type
DemMultiEventTriggeringSlaveEventRef ECUC-REFERENCE-DEF
BSW Description
Reference to the event that is triggered upon triggering the master event.
Template Description
This represents the slave diagnostic event.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticMasterToSlaveEventMapping.slaveEvent
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00946]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemObdDTC
BSW Parameter BSW Type
DemConsiderPtoStatus ECUC-BOOLEAN-PARAM-DEF
BSW Description
This parameter is TRUE, when the event is affected by the Dem PTO handling.
Template Description
This attribute describes the affection of the event by the Dem PTO handling.
True: the event is affected by the Dem PTO handling.
False: the event is not affected by the Dem PTO handling.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeObd.considerPtoStatus
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00602]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemObdDTC
BSW Parameter BSW Type
DemDtcValue ECUC-INTEGER-PARAM-DEF
BSW Description
Unique Diagnostic Trouble Code value for OBD
Template Description
Unique Diagnostic Trouble Code value for OBD.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeObd.obdDTCValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

508 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dem_00885]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemObdDTC
BSW Parameter BSW Type
DemEventOBDReadinessGroup ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter specifies the Event OBD Readiness group for PID $01 and PID $41 computation. This parameter is only
applicable for emission-related ECUs.
Template Description
DiagnosticTroubleCodeObd.eventReadinessGroup:
This aggregation allows for the variant definition of the attribute eventObdReadinessGroup.
EventObdReadinessGroup.eventObdReadinessGroup:
This attribute specifies the Event OBD Readiness group for PID $01 and PID $41 computation. This attribute is only
applicable for emission-related ECUs.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeObd.eventReadinessGroup, Diagnostic
Extract::Dem::DiagnosticTroubleCode::EventObdReadinessGroup.eventObdReadinessGroup
Mapping Rule Mapping Type
Configuration is only possible if DemOBDSupport is set to DEM_OBD_MASTER_ECU (see up_ full
Dem_00131)
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00755]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemObdDTC
BSW Parameter BSW Type
DemJ1939DTCValue ECUC-INTEGER-PARAM-DEF
BSW Description
Unique Diagnostic Trouble Code value for J1939 (consisting of SPN and FMI). The SPN is encoded in the lower number
range (0x7FFFF) and the FMI is encoded in the higher range (0xF80000).
Template Description
DiagnosticTroubleCodeJ1939.spn:
This represents the releated SPN.
DiagnosticTroubleCodeJ1939.fmi:
This attribute represents the behavior of the Failure Mode Indicator.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeJ1939.spn, DiagnosticExtract::Dem::Diagnostic
TroubleCode::DiagnosticTroubleCodeJ1939.fmi
Mapping Rule Mapping Type
The value is created out of a combination of the two attribute fmi and spn. The details are full
explained in the J1939-73 document
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00892]

509 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemConfigSet/DemPidClass
BSW Parameter BSW Type
DemPidDataElement ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the different data elements contained in the specific PID.
Template Description
This represents the data carried by the DiagnosticParameterIdentifier.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00896]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemPidClass/DemPidDataElement
BSW Parameter BSW Type
DemPidDataElementClassRef ECUC-REFERENCE-DEF
BSW Description
This reference contains the link to a data element class.
Template Description
This meta-class represents the ability to describe a concrete piece of data to be taken into account for diagnostic purposes.
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticDataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00733]

BSW Module BSW Context

Dem Dem/DemConfigSet/DemPidClass
BSW Parameter BSW Type
DemPidIdentifier ECUC-INTEGER-PARAM-DEF
BSW Description
identifier of the PID
Template Description
This is the numerical identifier used to identify the DiagnosticParameterIdentifier in the scope of diagnostic workflow (see
SAE J1979-DA).
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticParameterIdentifier.id
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00705]

510 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemAgingRequiresTestedCycle ECUC-BOOLEAN-PARAM-DEF
BSW Description
Defines if the aging cycle counter is processed every aging cycles or if only tested aging cycle are considered.
true: only tested aging cycle are considered for aging cycle counter
false: aging cycle counter is processed every aging cycle
Template Description
Defines whether the aging cycle counter is processed every aging cycles or else only tested aging cycle are considered.
If the attribute is set to TRUE: only tested aging cycle are considered for aging cycle counter.
If the attribute is set to FALSE: aging cycle counter is processed every aging cycle.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.agingRequiresTestedCycle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00877]

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemClearDTCLimitation ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the supported Dem_<...>ClearDTC API scope.
Template Description
Defines the scope of the DEM_ClearDTC Api.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.clearDtcLimitation
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00790]

BSW Module BSW Context

Dem Dem/DemGeneral/DemClearDTCLimitation
BSW Parameter BSW Type
DEM_ALL_SUPPORTED_DTCS ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Dem_<...>ClearDTC accepts all supported DTC values, as well as all DTC values which are configured in DemGroupDTCs
and DEM_DTC_GROUP_ALL_DTCS.
Template Description
DEM_ClearDtc API accepts all supported DTC values.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticClearDtcLimitationEnum.allSupportedDtcs
5

511 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemClearDTCLimitation
BSW Parameter BSW Type
DEM_ONLY_CLEAR_ALL_DTCS ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Dem_<...>ClearDTC accepts ClearAllDTCs only.
Template Description
DEM_ClearDtc API accepts ClearAllDTCs only.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticClearDtcLimitationEnum.clearAllDtcs
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemDataElementClass/DemExternalCSDataElementClass/DemDataElement
DataType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

512 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemDataElementClass/DemExternalCSDataElementClass/DemDataElement
DataType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemDataElementClass/DemExternalSRDataElementClass/DemDataElement
DataType
BSW Parameter BSW Type
FLOAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

513 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemDataElementClass/DemExternalSRDataElementClass/DemDataElement
DataType
BSW Parameter BSW Type
FLOAT_N ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Type of the data is float array.
Template Description
BaseTypeDirectDefinition.baseTypeEncoding:
This specifies, how an object of the current BaseType is encoded, e.g. in an ECU within a message sequence.
BaseTypeDirectDefinition.baseTypeSize:
Describes the length of the data type specified in the container in bits.
DiagnosticValueNeeds.fixedLength:
This attribute controls whether the data length of the data is fixed.
M2 Parameter
AsamHdo::BaseTypes::BaseTypeDirectDefinition.baseTypeEncoding, AsamHdo::BaseTypes::BaseTypeDirectDefinition.
baseTypeSize, CommonStructure::ServiceNeeds::DiagnosticValueNeeds.fixedLength
Mapping Rule Mapping Type
baseTypeEncoding = NONE, WINDOWS-1252, UTF-8, BCD-P, BCD-UP baseTypeSize = 8 max full
NumberOfElements shall not exist arraySizeSemantics shall not exist Derivation from Diagnostic
ValueNeeds.fixedLength=1 possible.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemDataElementClass/DemInternalDataElementClass
BSW Parameter BSW Type
DemInternalDataElement ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines the Dem-internal data value, which is mapped to the data element.
Template Description
This represents the ability to further specify the access within the Dem.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticDemProvidedDataMapping.dataProvider
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00616]

BSW Module BSW Context

Dem Dem/DemGeneral/DemDataElementClass/DemInternalDataElementClass/DemInternalData
Element
BSW Parameter BSW Type
DEM_EVENT_ASSOCIATED_IDENTIFICATION ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Represents the static value associated to an event by DemEventAssociatedIdentification.
Template Description
5

514 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This attribute represents the identification number that is associated with the enclosing DiagnosticEvent and allows to identify
it when placed into a snapshot record or extended data record storage.
This value can be reported as internal data element in snapshot records or extended data records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticEvent.associatedEventIdentification
Mapping Rule Mapping Type
If attribute DiagnosticEvent.associatedEventIdentification exists then the corresponding Dem full
InternalDataElement shall be set to DEM_EVENT_ASSOCIATED_IDENTIFICATION.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemDidClass ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for a data Id class. It is assembled out of one or several data elements.
Template Description
This is the numerical identifier used to identify the DiagnosticAbstractDataIdentifier in the scope of diagnostic workflow
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticAbstractDataIdentifier.id
Mapping Rule Mapping Type
If the subclass of DiagnosticAbstractDataIdentifier is referenced as DiagnosticTroubleCode full
Props.freezeFrameContent.dataIdentifier
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00706]

BSW Module BSW Context

Dem Dem/DemGeneral/DemDidClass
BSW Parameter BSW Type
DemDidIdentifier ECUC-INTEGER-PARAM-DEF
BSW Description
Identifier of the Data ID.
Template Description
This is the numerical identifier used to identify the DiagnosticAbstractDataIdentifier in the scope of diagnostic workflow
M2 Parameter
DiagnosticExtract::CommonDiagnostics::DiagnosticAbstractDataIdentifier.id
Mapping Rule Mapping Type
If the DiagnosticDataIdentifier is referenced as DiagnosticTroubleCodeProps.freezeFrame full
Content.dataIdentifier
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00650]

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
5

515 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DemEnableCondition ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for enable conditions.
Template Description
Specification of an enable condition.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticCondition::DiagnosticEnableCondition
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00653]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEnableCondition
BSW Parameter BSW Type
DemEnableConditionId ECUC-INTEGER-PARAM-DEF
BSW Description
Defines a unique enable condition Id.
This parameter should not be changeable by user, because the Id should be generated by Dem itself to prevent gaps and
multiple use of an Id. The enable conditions should be sequentially ordered beginning with 0 and no gaps in between.
Template Description

M2 Parameter

Mapping Rule Mapping Type

local
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00654]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEnableCondition
BSW Parameter BSW Type
DemEnableConditionStatus ECUC-BOOLEAN-PARAM-DEF
BSW Description
Defines the initial status for enable or disable of acceptance of event reports of a diagnostic event.
The value is the initialization after power up (before this condition is reported the first time). true: acceptance of a diagnostic
event enabled false: acceptance of a diagnostic event disabled
Template Description
Defines the initial status for enable or disable of acceptance/storage of event reports of a diagnostic event. The value is the
initialization after power up (before this condition is reported the first time).
true: acceptance/storage of a diagnostic event enabled
false: acceptance/storage of a diagnostic event disabled
M2 Parameter
DiagnosticExtract::Dem::DiagnosticCondition::DiagnosticCondition.initValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

516 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dem_00656]

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemEnableConditionGroup ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for enable condition groups.
Template Description
Enable condition group which includes one or several enable conditions.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticConditionGroup::DiagnosticEnableConditionGroup
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00745]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEnableConditionGroup
BSW Parameter BSW Type
DemEnableConditionRef ECUC-REFERENCE-DEF
BSW Description
References an enable condition.
Template Description
Reference to enableConditions that are part of the EnableConditionGroup.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticConditionGroup::DiagnosticEnableConditionGroup.enableCondition
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00655]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet
BSW Parameter BSW Type
DemIndicator ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for Indicators.
Template Description
Definition of an indicator.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticIndicator::DiagnosticIndicator
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

517 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dem_00680]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet
BSW Parameter BSW Type
DemMILIndicatorRef ECUC-REFERENCE-DEF
BSW Description
This parameter defines the indicator representing the MIL.
This parameter is mandatory for ECUs supporting OBD (refer to DemOBDSupport).
Template Description
Defines the type of the indicator.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticIndicator::DiagnosticIndicator.type
Mapping Rule Mapping Type
DignosticIndicator.type == DiagnosticIndicatorTypeEnum.malfunction full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00723]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet
BSW Parameter BSW Type
DemMirrorMemory ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the mirror event memory specific parameters of the Dem module.
Template Description
This represents a mirror memory for a diagnostic event.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestinationMirror
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00902]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemMirrorMemory
BSW Parameter BSW Type
DemMaxNumberEventEntryMirror ECUC-INTEGER-PARAM-DEF
BSW Description
Maximum number of events which can be stored in the mirror memory
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.maxNumberOfEventEntries
Mapping Rule Mapping Type
1:1 mapping full
5

518 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00688]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet
BSW Parameter BSW Type
DemPrimaryMemory ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the primary event memory specific parameters of the Dem module.
Template Description
This represents a primary memory for a diagnostic event.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestinationPrimary
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00901]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemDtcStatusAvailabilityMask ECUC-INTEGER-PARAM-DEF
BSW Description
Mask for the supported DTC status bits by the Dem. This mask is used in the positive response of UDS service 0x19.
Template Description
Mask for the supported DTC status bits by the Dem.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.dtcStatusAvailabilityMask
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00652]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemEnvironmentDataCapture ECUC-ENUMERATION-PARAM-DEF
BSW Description
DemEnvironmentDataCapture defines the point in time, when the data actually is captured.
Template Description
This attribute determines the point in time, when the data actually is captured.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.environmentCaptureToReporting
Mapping Rule Mapping Type
5

519 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00895]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemEnvironmentDataCapture
BSW Parameter BSW Type
DEM_CAPTURE_ASYNCHRONOUS_TO_REPORTING ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The data capturing is postponed to the next cycle of the Dem_Mainfunction. (This means that there is a minimum delay
between report of the failure and capturing the data).
Template Description
The data capturing is postponed to the next cycle of the Dem_Mainfunction. (This means that there is a minimum delay
between report of the failure and capturing the data.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::EnvironmentCaptureToReportingEnum.
captureAsynchronousToReporting
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemEnvironmentDataCapture
BSW Parameter BSW Type
DEM_CAPTURE_SYNCHRONOUS_TO_REPORTING ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The data is captured immediately within the context of Dem_SetEventStatus.
Template Description
The data is captured immediately within the reporting function (i.e. in the context of the setEventStatus/reportErrorStatus
function).
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::EnvironmentCaptureToReportingEnum.
captureSynchronousToReporting
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemEventDisplacementStrategy ECUC-ENUMERATION-PARAM-DEF
BSW Description
This configuration switch defines, whether support for event displacement is enabled or not, and which displacement strategy
is followed.
5

520 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.eventDisplacementStrategy
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00742]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemEventDisplacementStrategy
BSW Parameter BSW Type
DEM_DISPLACEMENT_FULL ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Event memory entry displacement is enabled, by consideration of priority active/passive status, and occurrence.
Template Description
Event memory entry displacement is enabled, by consideration of priority active/passive status, and occurrence.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticEventDisplacementStrategyEnum.full
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemEventDisplacementStrategy
BSW Parameter BSW Type
DEM_DISPLACEMENT_NONE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Event memory entry displacement is disabled.
Template Description
Event memory entry displacement is disabled.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticEventDisplacementStrategyEnum.none
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemEventDisplacementStrategy
BSW Parameter BSW Type
DEM_DISPLACEMENT_PRIO_OCC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Event memory entry displacement is enabled, by consideration of priority and occurrence (but without active/passive status).
5

521 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
Event memory entry displacement is enabled, by consideration of priority and occurrence (but without active/passive status).
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticEventDisplacementStrategyEnum.prioOcc
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemEventMemoryEntryStorageTrigger ECUC-ENUMERATION-PARAM-DEF
BSW Description
Configures the primary trigger to allocate an event memory entry.
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.memoryEntryStorageTrigger
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00797]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemMaxNumberEventEntryPrimary ECUC-INTEGER-PARAM-DEF
BSW Description
Maximum number of events which can be stored in the primary memory
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.maxNumberOfEventEntries
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00690]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemOccurrenceCounterProcessing ECUC-ENUMERATION-PARAM-DEF
BSW Description
5

522 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This configuration switch defines the consideration of the fault confirmation process for the occurrence counter. For OBD and
mixed systems (OBD/non OBD, refer to DemOBDSupport) configuration switch shall always set to DEM_PROCESS_
OCCCTR_TF.
Template Description
This attribute defines the consideration of the fault confirmation process for the occurrence counter.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.occurrenceCounterProcessing
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00767]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemOccurrenceCounter
Processing
BSW Parameter BSW Type
DEM_PROCESS_OCCCTR_CDTC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
the occurrence counter is triggered by the TestFailed bit if the fault confirmation was successful (ConfirmedDTC bit is set)
Template Description
The occurrence counter is triggered by the TestFailed bit if the fault confirmation was successful (ConfirmedDTC bit is set).
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticOccurrenceCounterProcessingEnum.confirmedDtcBit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemOccurrenceCounter
Processing
BSW Parameter BSW Type
DEM_PROCESS_OCCCTR_TF ECUC-ENUMERATION-LITERAL-DEF
BSW Description
the occurrence counter is only triggered by the TestFailed bit (and the fault confirmation is not considered) This parameter is
mandatory in case of J1939.
Template Description
The occurrence counter is only triggered by the TestFailed bit (and the fault confirmation is not considered).
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticOccurrenceCounterProcessingEnum.testFailedBit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

523 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory
BSW Parameter BSW Type
DemTypeOfFreezeFrameRecordNumeration ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
Template Description
This attribute defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00778]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemTypeOfFreezeFrameRecord
Numeration
BSW Parameter BSW Type
DEM_FF_RECNUM_CALCULATED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
freeze frame records will be numbered consecutive starting by 1 in their chronological order
Template Description
This attribute defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration
Mapping Rule Mapping Type
If DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration is set to DiagnosticTypeOf full
FreezeFrameRecordNumerationEnum.calculated
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemPrimaryMemory/DemTypeOfFreezeFrameRecord
Numeration
BSW Parameter BSW Type
DEM_FF_RECNUM_CONFIGURED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
freeze frame records will be numbered based on the given configuration in their chronological order
Template Description
This attribute defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration
Mapping Rule Mapping Type
If DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration is set to DiagnosticTypeOf full
FreezeFrameRecordNumerationEnum.configured.
5

524 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet
BSW Parameter BSW Type
DemTypeOfDTCSupported ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines the format returned by Dem_GetTranslationType and does not relate to/influence the supported Dem
functionality.
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.typeOfDtcSupported
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00720]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemTypeOfDTCSupported
BSW Parameter BSW Type
DEM_DTC_TRANSLATION_ISO11992_4 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
ISO11992-4 DTC format
Template Description
ISO11992-4 DTC format
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTypeOfDtcSupportedEnum.iso11992_4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemTypeOfDTCSupported
BSW Parameter BSW Type
DEM_DTC_TRANSLATION_ISO14229_1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
ISO14229-1 DTC format (3 byte format)
Template Description
ISO14229-1 DTC format (3 byte format)
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTypeOfDtcSupportedEnum.iso14229_1
Mapping Rule Mapping Type
1:1 mapping full
5

525 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemTypeOfDTCSupported
BSW Parameter BSW Type
DEM_DTC_TRANSLATION_SAEJ1939_73 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
SAEJ1939-73 DTC format
Template Description
SAEJ1939-73 DTC format
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTypeOfDtcSupportedEnum.saeJ1939_73
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemTypeOfDTCSupported
BSW Parameter BSW Type
DEM_DTC_TRANSLATION_SAE_J2012_DA_ ECUC-ENUMERATION-LITERAL-DEF
DTCFORMAT_04
BSW Description
SAE_J2012-DA_DTCFormat_00 (3 byte format)
Template Description
SAE_J2012-DA_DTCFormat_00 (3 byte format)
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTypeOfDtcSupportedEnum.saeJ2012_da
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet
BSW Parameter BSW Type
DemUserDefinedMemory ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the user defined event memory specific parameters of the Dem module.
Template Description
This represents a user-defined memory for a diagnostic event.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestinationUserDefined
Mapping Rule Mapping Type
5

526 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00910]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemDtcStatusAvailabilityMask ECUC-INTEGER-PARAM-DEF
BSW Description
Mask for the supported DTC status bits by the Dem. This mask is used in the positive response of UDS service 0x19.
Template Description
Mask for the supported DTC status bits by the Dem.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.dtcStatusAvailabilityMask
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00652]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemEnvironmentDataCapture ECUC-ENUMERATION-PARAM-DEF
BSW Description
DemEnvironmentDataCapture defines the point in time, when the data actually is captured.
Template Description
This attribute determines the point in time, when the data actually is captured.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.environmentCaptureToReporting
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00895]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemEnvironmentDataCapture
BSW Parameter BSW Type
DEM_CAPTURE_ASYNCHRONOUS_TO_REPORTING ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The data capturing is postponed to the next cycle of the Dem_Mainfunction. (This means that there is a minimum delay
between report of the failure and capturing the data).
Template Description
The data capturing is postponed to the next cycle of the Dem_Mainfunction. (This means that there is a minimum delay
between report of the failure and capturing the data.
M2 Parameter
5

527 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::Dem::DiagnosticTroubleCode::EnvironmentCaptureToReportingEnum.
captureAsynchronousToReporting
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemEnvironmentDataCapture
BSW Parameter BSW Type
DEM_CAPTURE_SYNCHRONOUS_TO_REPORTING ECUC-ENUMERATION-LITERAL-DEF
BSW Description
The data is captured immediately within the context of Dem_SetEventStatus.
Template Description
The data is captured immediately within the reporting function (i.e. in the context of the setEventStatus/reportErrorStatus
function).
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::EnvironmentCaptureToReportingEnum.
captureSynchronousToReporting
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemEventDisplacementStrategy ECUC-ENUMERATION-PARAM-DEF
BSW Description
This configuration switch defines, whether support for event displacement is enabled or not, and which displacement strategy
is followed.
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.eventDisplacementStrategy
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00742]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemEventDisplacement
Strategy
BSW Parameter BSW Type
DEM_DISPLACEMENT_FULL ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Event memory entry displacement is enabled, by consideration of priority active/passive status, and occurrence.
5

528 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
Event memory entry displacement is enabled, by consideration of priority active/passive status, and occurrence.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticEventDisplacementStrategyEnum.full
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemEventDisplacement
Strategy
BSW Parameter BSW Type
DEM_DISPLACEMENT_NONE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Event memory entry displacement is disabled.
Template Description
Event memory entry displacement is disabled.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticEventDisplacementStrategyEnum.none
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemEventDisplacement
Strategy
BSW Parameter BSW Type
DEM_DISPLACEMENT_PRIO_OCC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Event memory entry displacement is enabled, by consideration of priority and occurrence (but without active/passive status).
Template Description
Event memory entry displacement is enabled, by consideration of priority and occurrence (but without active/passive status).
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticEventDisplacementStrategyEnum.prioOcc
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemEventMemoryEntryStorageTrigger ECUC-ENUMERATION-PARAM-DEF
5

529 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Description
Configures the primary trigger to allocate an event memory entry.
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.memoryEntryStorageTrigger
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00797]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemMaxNumberEventEntryUserDefined ECUC-INTEGER-PARAM-DEF
BSW Description
Maximum number of events which can be stored in the user defined memory.
Template Description

M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.maxNumberOfEventEntries
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00691]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemOccurrenceCounterProcessing ECUC-ENUMERATION-PARAM-DEF
BSW Description
This configuration switch defines the consideration of the fault confirmation process for the occurrence counter. For OBD and
mixed systems (OBD/non OBD, refer to DemOBDSupport) configuration switch shall always set to DEM_PROCESS_
OCCCTR_TF.
Template Description
This attribute defines the consideration of the fault confirmation process for the occurrence counter.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.occurrenceCounterProcessing
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00767]

530 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemOccurrenceCounter
Processing
BSW Parameter BSW Type
DEM_PROCESS_OCCCTR_CDTC ECUC-ENUMERATION-LITERAL-DEF
BSW Description
the occurrence counter is triggered by the TestFailed bit if the fault confirmation was successful (ConfirmedDTC bit is set)
Template Description
The occurrence counter is triggered by the TestFailed bit if the fault confirmation was successful (ConfirmedDTC bit is set).
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticOccurrenceCounterProcessingEnum.confirmedDtcBit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemOccurrenceCounter
Processing
BSW Parameter BSW Type
DEM_PROCESS_OCCCTR_TF ECUC-ENUMERATION-LITERAL-DEF
BSW Description
the occurrence counter is only triggered by the TestFailed bit (and the fault confirmation is not considered) This parameter is
mandatory in case of J1939.
Template Description
The occurrence counter is only triggered by the TestFailed bit (and the fault confirmation is not considered).
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticOccurrenceCounterProcessingEnum.testFailedBit
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemTypeOfFreezeFrameRecordNumeration ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
Template Description
This attribute defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
5

531 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
valid [ECUC_Dem_00778]

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemTypeOfFreezeFrame
RecordNumeration
BSW Parameter BSW Type
DEM_FF_RECNUM_CALCULATED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
freeze frame records will be numbered consecutive starting by 1 in their chronological order
Template Description
This attribute defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration
Mapping Rule Mapping Type
If DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration is set to DiagnosticTypeOf full
FreezeFrameRecordNumerationEnum.calculated
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/DemTypeOfFreezeFrame
RecordNumeration
BSW Parameter BSW Type
DEM_FF_RECNUM_CONFIGURED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
freeze frame records will be numbered based on the given configuration in their chronological order
Template Description
This attribute defines the type of assigning freeze frame record numbers for event-specific freeze frame records.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration
Mapping Rule Mapping Type
If DiagnosticMemoryDestination.typeOfFreezeFrameRecordNumeration is set to DiagnosticTypeOf full
FreezeFrameRecordNumerationEnum.configured.
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory
BSW Parameter BSW Type
DemUserDefinedMemoryIdentifier ECUC-INTEGER-PARAM-DEF
BSW Description
Identifier used by external tester to identify the User defined event memory.
Template Description
This represents the identifier of the user-defined memory.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticMemoryDestinationUserDefined.memoryId
5

532 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00903]

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass
BSW Parameter BSW Type
DemExtendedDataRecordNumber ECUC-INTEGER-PARAM-DEF
BSW Description
This configuration parameter specifies an unique identifier for an extended data record.
One or more extended data records can be assigned to one diagnostic event/DTC.
0x00 is reserved by ISO (therefore the minimal value equals 1)
0xF0 to 0xFF are reserved by ISO (therefore the maximal value equals 239)
Template Description
This attribute specifies an unique identifier for an extended data record.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticExtendedDataRecord::DiagnosticExtendedDataRecord.recordNumber
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00666]

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass
BSW Parameter BSW Type
DemExtendedDataRecordTrigger ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the trigger to store the ExtendedDataRecord.
Template Description
This attribute specifies the primary trigger to allocate an event memory entry.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticExtendedDataRecord::DiagnosticExtendedDataRecord.trigger
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00804]

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass/DemExtendedDataRecordTrigger
BSW Parameter BSW Type
DEM_TRIGGER_ON_CONFIRMED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
ExtendedDataRecord will be stored when the UDS status confirmed bit changes from 0 to 1.
5

533 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
capture on "Confirmed"
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticRecordTriggerEnum.confirmed
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass/DemExtendedDataRecordTrigger
BSW Parameter BSW Type
DEM_TRIGGER_ON_FDC_THRESHOLD ECUC-ENUMERATION-LITERAL-DEF
BSW Description
ExtendedDataRecord will be stored when the FDC reaches its threshold.
Template Description
capture on "FDC Threshold"
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticRecordTriggerEnum.fdcThreshold
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass/DemExtendedDataRecordTrigger
BSW Parameter BSW Type
DEM_TRIGGER_ON_PENDING ECUC-ENUMERATION-LITERAL-DEF
BSW Description
ExtendedDataRecord will be stored when the UDS status pending bit changes from 0 to 1.
Template Description
capture on "Pending"
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticRecordTriggerEnum.pending
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass/DemExtendedDataRecordTrigger
BSW Parameter BSW Type
DEM_TRIGGER_ON_TEST_FAILED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
ExtendedDataRecord will be stored when the UDS status test failed bit changes from 0 to 1.
5

534 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
capture on "Test Failed"
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticRecordTriggerEnum.testFailed
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemExtendedDataRecordClass
BSW Parameter BSW Type
DemExtendedDataRecordUpdate ECUC-ENUMERATION-PARAM-DEF
BSW Description
This extended data record is captured if the configured trigger condition in "DemExtendedDataRecordTrigger" is fulfilled.
Template Description
This attribute defines when an extended data record is captured.
True: This extended data record is captured every time.
False: This extended data record is only captured for new event memory entries.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticExtendedDataRecord::DiagnosticExtendedDataRecord.update
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00621]

BSW Module BSW Context

Dem Dem/DemGeneral/DemFreezeFrameRecordClass
BSW Parameter BSW Type
DemFreezeFrameRecordNumber ECUC-INTEGER-PARAM-DEF
BSW Description
This parameter defines a record number for a freeze frame record. This record number is unique per freeze frame record
number class.
Template Description
This attribute defines a record number for a freeze frame record.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticFreezeFrame.recordNumber
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00777]

BSW Module BSW Context

Dem Dem/DemGeneral/DemFreezeFrameRecordClass
BSW Parameter BSW Type
5

535 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DemFreezeFrameRecordTrigger ECUC-ENUMERATION-PARAM-DEF
BSW Description
Defines the trigger to store the FreezeFrameRecord.
Template Description
This attribute defines the primary trigger to allocate an event memory entry.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticFreezeFrame.trigger
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00803]

BSW Module BSW Context

Dem Dem/DemGeneral/DemFreezeFrameRecordClass/DemFreezeFrameRecordTrigger
BSW Parameter BSW Type
DEM_TRIGGER_ON_TEST_FAILED_THIS_OPERATION_ ECUC-ENUMERATION-LITERAL-DEF
CYCLE
BSW Description
Event Memory entries are triggered if the UDS status bit 1 (testFailedThisOperationCycle) changes from 0 to 1.
Template Description
Test Failed This Operation Cycle.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticRecordTriggerEnum.testFailedThisOperationCycle
Mapping Rule Mapping Type
full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemFreezeFrameRecordClass
BSW Parameter BSW Type
DemFreezeFrameRecordUpdate ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter defines the case, when the freeze frame record is stored/updated.
Template Description
This attribute defines the approach when the freeze frame record is stored/updated.
True: FreezeFrame record is captured every time.
False: FreezeFrame record is only captured for new event memory entries.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticFreezeFrame::DiagnosticFreezeFrame.update
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00802]

536 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemOBDSupport ECUC-ENUMERATION-PARAM-DEF
BSW Description
This configuration switch defines OBD support and kind of OBD ECU.
Template Description
This attribute is used to specify the role (if applicable) in which the DiagnosticEcuInstance supports OBD.
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticEcuInstanceProps.obdSupport
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00698]

BSW Module BSW Context

Dem Dem/DemGeneral/DemOBDSupport
BSW Parameter BSW Type
DEM_OBD_DEP_SEC_ECU ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Kind of OBD ECU: OBD Dependend / Secondary ECU
Template Description
This represents the role "secondary ECU".
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticObdSupportEnum.secondaryEcu
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemOBDSupport
BSW Parameter BSW Type
DEM_OBD_MASTER_ECU ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Kind of OBD ECU: Master ECU
Template Description
This represent the role "master ECU".
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticObdSupportEnum.masterEcu
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

537 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemOBDSupport
BSW Parameter BSW Type
DEM_OBD_NO_OBD_SUPPORT ECUC-ENUMERATION-LITERAL-DEF
BSW Description
OBD is not supported within this ECU
Template Description
This represents the ability to explicitly specify that no participation in OBD is foreseen.
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticObdSupportEnum.noObdSupport
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemOBDSupport
BSW Parameter BSW Type
DEM_OBD_PRIMARY_ECU ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Kind of OBD ECU: Pimary ECU
Template Description
This represents the role "primary ECU".
M2 Parameter
DiagnosticExtract::DiagnosticContribution::DiagnosticObdSupportEnum.primaryEcu
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemOperationCycle ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container holds all parameters that are relevant to configure an operation cycle.
Template Description
Definition of an operation cycle that is the base of the event qualifying and for Dem scheduling.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticOperationCycle::DiagnosticOperationCycle
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00701]

538 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemRatio ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the OBD-specific in-use-monitor performance ratio configuration. It is related to a specific event, a
FID, and an IUMPR group.
Template Description
ObdRatioServiceNeeds:
Specifies the abstract needs of a component or module on the configuration of OBD Services in relation to a particular "ratio
monitoring" which is supported by this component or module.
DiagnosticIumprGroup:
This meta-class represents the ability to model a IUMPR groups.
M2 Parameter
CommonStructure::ServiceNeeds::ObdRatioServiceNeeds, DiagnosticExtract::Dem::DiagnosticEvent::
DiagnosticIumprGroup
Mapping Rule Mapping Type
In case the owner of the ObdRatioServiceNeeds is a BSW module then the DemRatio.shortName full
= {capitalizedMip}_{ServiceDependency.symbolicNameProps.symbol}. For the DiagnosticIumpr
Group the mapping rule is 1:1
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00734]

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio
BSW Parameter BSW Type
DemDiagnosticEventRef ECUC-REFERENCE-DEF
BSW Description
This reference contains the link to a diagnostic event.
Template Description
DiagnosticIumprGroup.iumpr:
This reference collects DiagnosticIumpr to a DiagnosticIumprGroup.
DiagnosticIumpr.event:
This reference represents the DiagnosticEvent that corresoponds to the IUMPR computation.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.iumpr, DiagnosticExtract::Dem::Diagnostic
Event::DiagnosticIumpr.event
Mapping Rule Mapping Type
foreach DiagnosticIumprGroup, follow the iumpr reference and then pick the target of the event full
reference
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00735]

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio
BSW Parameter BSW Type
DemIUMPRDenGroup ECUC-ENUMERATION-PARAM-DEF
BSW Description
5

539 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This parameter specifies the assigned denominator type which is applied in addition to the DEM_IUMPR_GENERAL_
INDIVIDUAL_DENOMINATOR conditions.
Template Description
This meta-class represents the ability to model a IUMPR denominator groups.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprDenominatorGroup
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00838]

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRDenGroup
BSW Parameter BSW Type
DEM_IUMPR_DEN_500MILL ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Additional condition based on definition of 500miles conditions as defined for OBD2.
Template Description
DiagnosticIumprDenominatorGroup.iumpr:
This reference collects DiagnosticIumpr to a DiagnosticIumprDenominatorGroup.
Identifiable.category:
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprDenominatorGroup.iumpr, GenericStructure::GeneralTemplate
Classes::Identifiable::Identifiable.category
Mapping Rule Mapping Type
DiagnosticIumprDenominatorGroup.category ==IUMPR_DENOMINATOR_500_MILES full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRDenGroup
BSW Parameter BSW Type
DEM_IUMPR_DEN_COLDSTART ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Additional condition based on definition of "cold start" as defined for EU5+
Template Description
DiagnosticIumprDenominatorGroup.iumpr:
This reference collects DiagnosticIumpr to a DiagnosticIumprDenominatorGroup.
Identifiable.category:
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprDenominatorGroup.iumpr, GenericStructure::GeneralTemplate
Classes::Identifiable::Identifiable.category
Mapping Rule Mapping Type
5

540 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticIumprDenominatorGroup == IUMPR_DENOMINATOR_COLDSTART full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRDenGroup
BSW Parameter BSW Type
DEM_IUMPR_DEN_EVAP ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Additional condition based on definition of "EVAP" conditions as defined for OBD2.
Template Description
DiagnosticIumprDenominatorGroup.iumpr:
This reference collects DiagnosticIumpr to a DiagnosticIumprDenominatorGroup.
Identifiable.category:
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprDenominatorGroup.iumpr, GenericStructure::GeneralTemplate
Classes::Identifiable::Identifiable.category
Mapping Rule Mapping Type
DiagnosticIumprDenominatorGroup.category == IUMPR_DENOMINATOR_EVAP full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRDenGroup
BSW Parameter BSW Type
DEM_IUMPR_DEN_NONE ECUC-ENUMERATION-LITERAL-DEF
BSW Description
No further condition. Denominator increments based on GENERAL_INDIVIDUAL_DENOMINATOR only.
Template Description
DiagnosticIumprDenominatorGroup.iumpr:
This reference collects DiagnosticIumpr to a DiagnosticIumprDenominatorGroup.
Identifiable.category:
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprDenominatorGroup.iumpr, GenericStructure::GeneralTemplate
Classes::Identifiable::Identifiable.category
Mapping Rule Mapping Type
DiagnosticIumprDenominatorGroup.category == IUMPR_DENOMINATOR_NONE full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRDenGroup
BSW Parameter BSW Type
5

541 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DEM_IUMPR_DEN_PHYS_API ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Additional physical condition (component activity) computed within the SW-C and reported via Dem_RepIUMPRDenRelease.
Template Description
DiagnosticIumprDenominatorGroup.iumpr:
This reference collects DiagnosticIumpr to a DiagnosticIumprDenominatorGroup.
Identifiable.category:
The category is a keyword that specializes the semantics of the Identifiable. It affects the expected existence of attributes and
the applicability of constraints.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprDenominatorGroup.iumpr, GenericStructure::GeneralTemplate
Classes::Identifiable::Identifiable.category
Mapping Rule Mapping Type
DiagnosticIumprDenominatorGroup.category == IUMPR_DENOMINATOR_PHYSICAL_API full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio
BSW Parameter BSW Type
DemIUMPRGroup ECUC-ENUMERATION-PARAM-DEF
BSW Description
This parameter specifies the assigned IUMPR group of the ratio Id.
Template Description
DiagnosticIumprGroup.iumprGroupIdentifier:
This aggregation allows for the variant modeling of the groupIdentifier.
DiagnosticIumprGroupIdentifier.groupId:
This attribute shall be taken to define an identifier for the IUMPR group. Please note that the value of this identifier is driven by
regulations outside the scope of AUTOSAR and can therefore not be limited to the set of characters suitable for a shortName.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.iumprGroupIdentifier, Diagnostic
Extract::Dem::DiagnosticEvent::DiagnosticIumprGroupIdentifier.groupId
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00737]

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_AFRI1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Air Fuel Ratio Imbalance Monitor Bank 1
Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
5

542 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
If groupIdentifier is set to DEM_IUMPR_AFRI1 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_AFRI2 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Air Fuel Ratio Imbalance Monitor Bank 2
Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_AFRI2 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_BOOSTPRS ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_BOOSTPRS full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_CAT1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_CAT1 full
Mapping Status ECUC Parameter ID
valid

543 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_CAT2 ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_CAT2 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_EGR ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
if groupIdentifier is set to DEM_IUMPR_EGR full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_EGSENSOR ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_EGSENSOR. full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
5

544 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DEM_IUMPR_EVAP ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_EVAP full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_FLSYS ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_FLSYS full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_NMHCCAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_NMHCCAT full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_NOXADSORB ECUC-ENUMERATION-LITERAL-DEF
BSW Description

545 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_NOXADSORB full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_NOXCAT ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_NOXCAT full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_OXS1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier ist set to DEM_IUMPR_OXS1 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_OXS2 ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
5

546 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_OSX2 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_PF1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Particulate Filter Monitor Bank 1
Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_PF1 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_PF2 ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Particulate Filter Monitor Bank 2
Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_PF2 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_PMFILTER ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_PMFILTER full
5

547 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_PRIVATE ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_PRIVATE full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_SAIR ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_SAIR full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_SECOXS1 ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_SECOXS1 full
Mapping Status ECUC Parameter ID
valid

548 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral/DemRatio/DemIUMPRGroup
BSW Parameter BSW Type
DEM_IUMPR_SECOXS2 ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description

M2 Parameter
DiagnosticExtract::Dem::DiagnosticEvent::DiagnosticIumprGroup.groupIdentifier
Mapping Rule Mapping Type
If groupIdentifier is set to DEM_IUMPR_SECOXS2 full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemResetConfirmedBitOnOverflow ECUC-BOOLEAN-PARAM-DEF
BSW Description
This configuration switch defines, whether the confirmed bit is reset or not while an event memory entry will be displaced.
Template Description
This attribute defines, whether the confirmed bit is reset or not while an event memory entry will be displaced.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.resetConfirmedBitOnOverflow
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00799]

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemStatusBitHandlingTestFailedSinceLastClear ECUC-ENUMERATION-PARAM-DEF
BSW Description
This configuration switch defines, whether the aging and displacement mechanism shall be applied to the "TestFailedSince
LastClear" status bits.
Template Description
This attribute defines, whether the aging and displacement mechanism shall be applied to the "TestFailedSinceLastClear"
status bits.
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.
statusBitHandlingTestFailedSinceLastClear
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00784]

549 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemStatusBitStorageTestFailed ECUC-BOOLEAN-PARAM-DEF
BSW Description
Activate/Deactivate the permanent storage of the "TestFailed" status bits.
true: storage activated false: storage deactivated
Template Description
This parameter is used to activate/deactivate the permanent storage of the "TestFailed" status bits.
true: storage activated
false: storage deactivated
M2 Parameter
DiagnosticExtract::DiagnosticCommonProps::DiagnosticCommonProps.statusBitStorageTestFailed
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00714]

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemStorageCondition ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for storage conditions.
Template Description
Specification of a storage condition.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticCondition::DiagnosticStorageCondition
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00728]

BSW Module BSW Context

Dem Dem/DemGeneral/DemStorageCondition
BSW Parameter BSW Type
DemStorageConditionId ECUC-INTEGER-PARAM-DEF
BSW Description
Defines a unique storage condition Id. This parameter should not be changeable by user, because the Id should be
generated by Dem itself to prevent gaps and multiple use of an Id. The storage conditions should be sequentially ordered
beginning with 0 and no gaps in between.
Template Description

M2 Parameter

Mapping Rule Mapping Type

5

550 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
local
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00730]

BSW Module BSW Context

Dem Dem/DemGeneral/DemStorageCondition
BSW Parameter BSW Type
DemStorageConditionReplacementEventRef ECUC-REFERENCE-DEF
BSW Description
Specifies the reference to an event which is stored to event memory and supports failure analysis.
Template Description
Reference to a DiagnosticEvent to which a StorageConditionGroup is assigned.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticEventToStorageConditionGroupMapping.diagnosticEvent
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00893]

BSW Module BSW Context

Dem Dem/DemGeneral/DemStorageCondition
BSW Parameter BSW Type
DemStorageConditionStatus ECUC-BOOLEAN-PARAM-DEF
BSW Description
Defines the initial status for enable or disable of storage of a diagnostic event.
The value is the initialization after power up (before this condition is reported the first time). true: storage of a diagnostic event
enabled false: storage of a diagnostic event disabled
Template Description
Defines the initial status for enable or disable of acceptance/storage of event reports of a diagnostic event. The value is the
initialization after power up (before this condition is reported the first time).
true: acceptance/storage of a diagnostic event enabled
false: acceptance/storage of a diagnostic event disabled
M2 Parameter
DiagnosticExtract::Dem::DiagnosticCondition::DiagnosticCondition.initValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00731]

BSW Module BSW Context

Dem Dem/DemGeneral
BSW Parameter BSW Type
DemStorageConditionGroup ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration (parameters) for storage condition groups.
5

551 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Template Description
Storage condition group which includes one or several storage conditions.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticConditionGroup::DiagnosticStorageConditionGroup
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00773]

BSW Module BSW Context

Dem Dem/DemGeneral/DemStorageConditionGroup
BSW Parameter BSW Type
DemStorageConditionRef ECUC-REFERENCE-DEF
BSW Description
References an enable condition.
Template Description
Reference to storageConditions that are part of the StorageConditionGroup.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticConditionGroup::DiagnosticStorageConditionGroup.storageCondition
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_Dem_00768]

E.4 Fim
BSW Module BSW Context
FiM FiM/FiMConfigSet
BSW Parameter BSW Type
FiMFID ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container includes symbolic names of all FIDs.
Template Description
FunctionInhibitionNeeds:
Specifies the abstract needs on the configuration of the Function Inhibition Manager for one Function Identifier (FID). This
class currently contains no attributes. Its name can be regarded as a symbol identifying the FID from the viewpoint of the
component or module which owns this class.
DiagnosticFunctionIdentifier:
This meta-class represents a diagnostic function identifier (a.k.a. FID).
M2 Parameter
CommonStructure::ServiceNeeds::FunctionInhibitionNeeds, DiagnosticExtract::Fim::
DiagnosticFunctionIdentifier
Mapping Rule Mapping Type
In case the owner of the FunctionInhibitionNeeds is a BSW module then the FiMFID.shortName= full
{capitalizedMip}_{ServiceDependency.symbolicNameProps.symbol}.
5

552 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid [ECUC_FiM_00039]

BSW Module BSW Context

FiM FiM/FiMConfigSet
BSW Parameter BSW Type
FiMInhibitionConfiguration ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container includes all configuration parameters concerning the relationship between event and FID.
Template Description
This meta-class represents the ability to define the inhibition of a specific function identifier within the Fim configuration.
M2 Parameter
DiagnosticExtract::Fim::DiagnosticFunctionIdentifierInhibit
Mapping Rule Mapping Type
full
Mapping Status ECUC Parameter ID
valid [ECUC_FiM_00038]

BSW Module BSW Context

FiM FiM/FiMConfigSet/FiMInhibitionConfiguration
BSW Parameter BSW Type
FiMInhEventRef ECUC-REFERENCE-DEF
BSW Description
Selection of an single DEM Event.
Template Description
This represents the alias event appllicable for the referencing inhibition source.
M2 Parameter
DiagnosticExtract::Fim::DiagnosticFunctionInhibitSource.event
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_FiM_00100]

BSW Module BSW Context

FiM FiM/FiMConfigSet/FiMInhibitionConfiguration
BSW Parameter BSW Type
FiMInhInhibitionMask ECUC-ENUMERATION-PARAM-DEF
BSW Description
The configuration parameter is used to specify the inhibition mask for an event - FID relation.
Template Description
This represents the value of the inhibition mask behavior.
M2 Parameter
DiagnosticExtract::Fim::DiagnosticFunctionIdentifierInhibit.inhibitionMask
Mapping Rule Mapping Type
5

553 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
full
Mapping Status ECUC Parameter ID
valid [ECUC_FiM_00096]

BSW Module BSW Context

FiM FiM/FiMConfigSet/FiMInhibitionConfiguration/FiMInhInhibitionMask
BSW Parameter BSW Type
FIM_LAST_FAILED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Last Failed - DEM_UDS_STATUS_TF flag of Dem Eventstatus is set Use case: Re-configuration, avoiding follow-up errors
Template Description
This represents the inhibition mask behavior "last failed".
M2 Parameter
DiagnosticExtract::Fim::DiagnosticInhibitionMaskEnum.lastFailed
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

FiM FiM/FiMConfigSet/FiMInhibitionConfiguration/FiMInhInhibitionMask
BSW Parameter BSW Type
FIM_NOT_TESTED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Not Tested this cycle - DEM_UDS_STATUS_TNCTOC flag of Dem Eventstatus is set. Use case: Scheduling of monitors.
Template Description
This represents the inhibition mask behavior "not tested".
M2 Parameter
DiagnosticExtract::Fim::DiagnosticInhibitionMaskEnum.notTested
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

FiM FiM/FiMConfigSet/FiMInhibitionConfiguration/FiMInhInhibitionMask
BSW Parameter BSW Type
FIM_TESTED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Tested - DEM_UDS_STATUS_TNCTOC flag of Dem Eventstatus is not set. Use case: Self deactivation, check during driving
cycle.
Template Description
This represents the inhibition mask behavior "tested".
M2 Parameter
DiagnosticExtract::Fim::DiagnosticInhibitionMaskEnum.tested
5

554 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

FiM FiM/FiMConfigSet/FiMInhibitionConfiguration/FiMInhInhibitionMask
BSW Parameter BSW Type
FIM_TESTED_AND_FAILED ECUC-ENUMERATION-LITERAL-DEF
BSW Description
Tested and Failed - DEM_UDS_STATUS_TF flag of Dem Eventstatus is set and DEM_UDS_STATUS_TNCTOC flag is not set
Use case: Avoiding deadlocks, repeated monitoring.
Template Description
This represents the inhibition mask behavior "tested and failed".
M2 Parameter
DiagnosticExtract::Fim::DiagnosticInhibitionMaskEnum.testedAndFailed
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

FiM FiM/FiMConfigSet
BSW Parameter BSW Type
FiMSummaryEvent ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
The summarized EventId definition record consists of a summarized event ID and specific Dem Events.
This record means that a particular FID that has to be disabled in case of summarized event (defined above) is to be disabled
in any of the specific events. A possible solution could be assigning events as summarized events along with a list of specific
events. During the configuration process the summarized event substitutes the referenced single events.
However, it is not outlined how this requirement is solved - whether by configuration process or by implementation within the
FiM. The FiM configuration tool could also build up a suitable data structure for summarized events and deal with it in the FiM
implementation.
Template Description
This meta-class represents the ability to model a Fim event group, also known as a summary event in Fim terminology. This
represents a group of single diagnostic events.
M2 Parameter
DiagnosticExtract::Fim::DiagnosticFimEventGroup
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_FiM_00603]

555 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

E.5 J1939 Dcm

BSW Module BSW Context
J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmChannel
BSW Parameter BSW Type
J1939DcmBusType ECUC-ENUMERATION-PARAM-DEF
BSW Description
Identifies the communication port
Template Description
This represents the network ID for the J1939 cluster.
M2 Parameter
SystemTemplate::Fibex::Fibex4Can::CanTopology::J1939Cluster.networkId
Mapping Rule Mapping Type
value 1 maps to J1939DCM_J1939_NETWORK_1 value 2 maps to J1939DCM_J1939_ full
NETWORK_2 value 3 maps to J1939DCM_J1939_NETWORK_3 value 4 maps to J1939DCM_
J1939_NETWORK_4
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00039]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmDspExternalSRDataElementClass/J1939DcmData
ElementInstance
BSW Parameter BSW Type
J1939DcmDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitive data which shall be read or written. Supported are VariableDataPrototypes in Sender
ReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in ParameterInterfaces (read only). This reference
is applicable if the AutosarDataPrototype is typed with a ApplicationPrimitiveDataType of category VALUE or BOOLEAN or if
the AutosarDataPrototype is typed with a ImplementationDataType of category VALUE or TYPE_REFERENCE that in turn
boils down to VALUE
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive data. full
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00067]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmDspExternalSRDataElementClass/J1939DcmSub
ElementInDataElementInstance
BSW Parameter BSW Type
J1939DcmSubElementInDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
5

556 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Instance Reference to the primitve sub-element (at any level) of composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in Parameter
Interfaces (read only). This reference is applicable if the AutosarDataPrototype is typed with a ApplicationCompositeData
Type.
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive element within a composite data, where the full
AutosarDataPrototype is typed with a ApplicationCompositeDataType.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00066]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmDspExternalSRDataElementClass/J1939DcmSub
ElementInImplDataElementInstance
BSW Parameter BSW Type
J1939DcmSubElementInImplDataElementInstanceRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
Instance Reference to the primitve sub-element (at any level) of composite data in a port which shall be read. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and NvDataInterfaces and ParameterDataPrototypes in Parameter
Interfaces (read only). This reference is applicable if the AutosarDataPrototype is typed with a ImplementationDataType of
category STRUCTURE or ARRAY. Please note that in case of ARRAY the index attribute in the target reference has to be set
to select a single array element.
Template Description
This represents the dataElement in the application software that is accessed for diagnostic purpose. This role is applicable on
the classic platform.
M2 Parameter
DiagnosticExtract::ServiceMapping::DiagnosticServiceDataMapping.mappedDataElement
Mapping Rule Mapping Type
DiagnosticServiceDataMapping maps to a primitive element within a composite data, where the full
AutosarDataPrototype is typed with a ApplicationCompositeDataType ImplementationDataType of
category STRUCTURE or ARRAY.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00068]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmNode
BSW Parameter BSW Type
J1939DcmServiceOnlyDTCsMemoryDestinationRef ECUC-REFERENCE-DEF
BSW Description
Reference to the user defined memory used for the Service Only DTCs handled by DM53, DM54, and DM55.
Template Description
The event destination assigns events to none, one or multiple origins.
M2 Parameter
5

557 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
DiagnosticExtract::Dem::DiagnosticTroubleCode::DiagnosticTroubleCodeProps.memoryDestination
Mapping Rule Mapping Type
This upstream mapping shall only exist for a DiagnosticTroubleCodeJ1939 with attribute kind set to full
serviceOnly that references the DiagnosticTroubleCodeProps that owns the memoryDestination.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00051]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions
BSW Parameter BSW Type
J1939DcmModeCondition ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration of a mode condition or an environmental conditions which can be used as argument
in J1939DcmModeRules.
One J1939DcmModeCondition shall contain either one J1939DcmSwcModeRef or one J1939DcmBswModeRef or one
J1939DcmSwcSRDataElementRef.
Please note that the J1939Dcm acts as well as mode manager. Therefore the references J1939DcmSwcModeRef or one
J1939DcmBswModeRef might point to provided ModeDeclarationGroupPrototypes of the J1939Dcm itself as well as to
provided ModeDeclarationGroupPrototypes of other Bsw Modules or software components.
In case of a configured J1939DcmSwcModeRef or J1939DcmBswModeRef only the J1939DcmConditionType J1939DCM_
EQUALS or J1939DCM_EQUALS_NOT are applicable.
In case of J1939DcmSwcSRDataElementRef all literals of J1939DcmConditionType are possible.
Template Description
DiagnosticCompareConditions are atomic conditions. They are based on the idea of a comparison at runtime of some
variable data with something constant. The type of the comparison (==, !=, <, <=, ...) is specified in DiagnosticCompare
Condition.compareType.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvCompareCondition
Mapping Rule Mapping Type
Depending on the reference a DcmModeCondition is mapped to a DiagnosticEnvModeCondition if full
only one reference is present and reference is a DcmSwcModeRef or a DcmBswModeRef. If two
references are present, a DcmSwcSRDataElementRef and a DcmSwcSRDataElementValueRef,
then DcmModeCondition is mapped to a DiagnosticEnvDataCondition.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00071]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition
BSW Parameter BSW Type
J1939DcmBswModeRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
This parameter references a mode of a ModeDeclarationGroupPrototype provided by a Basic Software Module used for the
condition.
Please note that such ModeDeclarationGroupPrototype are owned by a Basic Software Module Description in the role
providedModeGroup.
Template Description
5

558 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
This reference represents both the ModeDeclarationGroupPrototype and the ModeDeclaration relevant for the mode
comparison.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvModeCondition.modeElement
Mapping Rule Mapping Type
For DcmModeRef a new DiagnosticEnvBswModeElement is used, pointing to the ModeDeclaration full
via ModeInModuleDescriptionInstanceRef. This new DiagnosticEnvModeElement shall be
aggregated by the same DiagnosticEnvironmentalConfition as the DiagnosticEnvModeCondition,
in which the target of the reference DiagnosticEnvModeCondition.modeElement points to the this
DiagnosticEnvModeElement.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00059]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmConditionType
BSW Parameter BSW Type
J1939DCM_EQUALS ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isEqual:
equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isEqual
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmConditionType
BSW Parameter BSW Type
J1939DCM_EQUALS_NOT ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isNotEqual:
not equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isNotEqual
Mapping Rule Mapping Type
5

559 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmConditionType
BSW Parameter BSW Type
J1939DCM_GREATER_OR_EQUAL ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isGreaterOrEqual:
greater than or equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isGreaterOrEqual
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmConditionType
BSW Parameter BSW Type
J1939DCM_GREATER_THAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isGreaterThan:
greater than
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isGreaterThan
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmConditionType
BSW Parameter BSW Type
5

560 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
J1939DCM_LESS_OR_EQUAL ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isLessOrEqual:
less than or equal
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isLessOrEqual
Mapping Rule Mapping Type
full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmConditionType
BSW Parameter BSW Type
J1939DCM_LESS_THAN ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticCompareTypeEnum.isLessThan:
less than
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticCompareTypeEnum.isLessThan
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition
BSW Parameter BSW Type
J1939DcmSwcModeRef ECUC-INSTANCE-REFERENCE-DEF
BSW Description
This parameter references a mode in a particular mode request port of a software component that is used for the condition.
Template Description
This reference represents both the ModeDeclarationGroupPrototype and the ModeDeclaration relevant for the mode
comparison.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvModeCondition.modeElement
Mapping Rule Mapping Type
5

561 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
For DcmModeRef a new DiagnosticEnvSwcModeElement is used, pointing to the ModeDeclaration full
via PModeInSystemInstanceRef. This new DiagnosticEnvModeElement shall be aggregated by the
same DiagnosticEnvironmentalConfition as the DiagnosticEnvModeCondition, in which the target
of the reference DiagnosticEnvModeCondition.modeElement points to the this DiagnosticEnvMode
Element.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00058]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition
BSW Parameter BSW Type
J1939DcmSwcSRDataElementRef ECUC-REFERENCE-DEF
BSW Description
Reference to environmental conditions. It is possible to reference a S/R Receiver-Port to read physical values and compare
(equal, greater, less,...) them with a configured value that is defined by J1939DcmSwcSRDataElementValue.
Template Description
This reference represents the related diagnostic data element.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.dataElement
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00060]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmSwcSRDataElementValue/J1939DcmSwcSRDataElementArray/J1939DcmSwcSRData
ElementArrayElement
BSW Parameter BSW Type
J1939DcmSwcSRDataElementArrayElementIndex ECUC-INTEGER-PARAM-DEF
BSW Description
Index to an array SR data element.
Template Description
This attribute represents a fixed compare value taken to evaluate the compare condition.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.compareValue
Mapping Rule Mapping Type
DiagnosticDataElement referenced by the DiagnosticEnvDataCondition is an array. full
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00078]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmSwcSRDataElementValue/J1939DcmSwcSRDataElementArray/J1939DcmSwcSRData
ElementArrayElement
5

562 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
BSW Parameter BSW Type
J1939DcmSwcSRDataElementArrayElementValue ECUC-INTEGER-PARAM-DEF
BSW Description
Value of an array SR data element compare value.
Template Description
This attribute represents a fixed compare value taken to evaluate the compare condition.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.compareValue
Mapping Rule Mapping Type
DiagnosticDataElement referenced by the DiagnosticEnvDataCondition is an array. full
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00079]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeCondition/
J1939DcmSwcSRDataElementValue/J1939DcmSwcSRDataElementPrimitive
BSW Parameter BSW Type
J1939DcmSwcSRDataElementPrimitiveValue ECUC-INTEGER-PARAM-DEF
BSW Description
Reference to a primitive SR data element compare value.
Template Description
This attribute represents a fixed compare value taken to evaluate the compare condition.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvDataCondition.compareValue
Mapping Rule Mapping Type
DiagnosticDataElement referenced by the DiagnosticEnvDataCondition is primitive. full
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00077]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions
BSW Parameter BSW Type
J1939DcmModeRule ECUC-PARAM-CONF-CONTAINER-DEF
BSW Description
This container contains the configuration of a mode rule which represents a logical expression with J1939DcmMode
Conditions or other J1939DcmModeRules as arguments.
All arguments are processed with the operator defined by DcmLogicalOperator, for instance: Argument_A AND Argument_B
AND Argument_C
Template Description
A DiagnosticEnvConditionFormula embodies the computation instruction that is to be evaluated at runtime to determine if the
DiagnosticEnvironmentalCondition is currently present (i.e. the formula is evaluated to true) or not (otherwise). The formula
itself consists of parts which are combined by the logical operations specified by DiagnosticEnvConditionFormula.op.
If a diagnostic functionality cannot be executed because an environmental condition fails then the diagnostic stack shall send
a negative response code (NRC) back to the client. The value of the NRC is directly related to the specific formula and is
therefore formalized in the attribute DiagnosticEnvConditionFormula.nrcValue.
5

563 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula
Mapping Rule Mapping Type
A DcmModeRule is mapped to a DiagnosticEnvConditionFormula, if this DcmModeRule is a full
subrule, i.e. it is referenced by a DcmArgumentRef. In addition, a new DiagnosticEnvironmental
Condition shall be created with DiagnosticEnvironmentalCondition.formula containing a Diagnostic
EnvConditionFormula. In both cases, if no DcmLogicalOperator is present in this DcmModeRule,
then DiagnosticEnvConditionFormula shall be set to DiagnosticLogicalOperatorEnum.logicalAnd.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00053]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeRule
BSW Parameter BSW Type
J1939DcmArgumentRef ECUC-CHOICE-REFERENCE-DEF
BSW Description
This is a choice reference either to a mode condition or a an other mode rule serving as sub-expression.
Template Description
A DiagnosticEnvConditionFormulaPart can either be a atomic condition, e.g. a DiagnosticEnvCompareCondition, or a
DiagnosticEnvConditionFormula, again, which allows arbitrary nesting.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormulaPart
Mapping Rule Mapping Type
Depending on the destination, one DcmArgumentRef is mapped to a DiagnosticEnvCondition full
Formula if "destination" is a DcmModeRule, and to a DiagnosticEnvCompareCondition, if
"destination" is a DcmModeCondition. The order of the aggregation of the DiagnosticEnvCondition
FormulaParts shall correspond to the ordering of the index of the DcmArgumentRefs.
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00055]

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeRule/
J1939DcmLogicalOperator
BSW Parameter BSW Type
J1939DCM_AND ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticLogicalOperatorEnum.logicalAnd:
Logical AND
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticLogicalOperatorEnum.logicalAnd
Mapping Rule Mapping Type
1:1 mapping full
5

564 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeRule/
J1939DcmLogicalOperator
BSW Parameter BSW Type
J1939DCM_OR ECUC-ENUMERATION-LITERAL-DEF
BSW Description

Template Description
DiagnosticEnvConditionFormula.op:
This attribute represents the concrete operator (supported operators: and, or) of the condition formula.
DiagnosticLogicalOperatorEnum.logicalOr:
Logical OR
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.op, Diagnostic
Extract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticLogicalOperatorEnum.logicalOr
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid

BSW Module BSW Context

J1939Dcm J1939Dcm/J1939DcmConfigSet/J1939DcmProcessingConditions/J1939DcmModeRule
BSW Parameter BSW Type
J1939DcmModeRuleNrcValue ECUC-INTEGER-PARAM-DEF
BSW Description
Optional parameter which defines the NRC to be sent in case the mode rule condition is not valid.
Template Description
This attribute represents the concrete NRC value that shall be returned if the condition fails.
M2 Parameter
DiagnosticExtract::Dcm::DiagnosticService::EnvironmentalCondition::DiagnosticEnvConditionFormula.nrcValue
Mapping Rule Mapping Type
1:1 mapping full
Mapping Status ECUC Parameter ID
valid [ECUC_J1939Dcm_-
00056]

E.6 IdsM
BSW Module BSW Context
IdsM IdsM/IdsMConfiguration/IdsMEvent
BSW Parameter BSW Type
IdsMSinkDem ECUC-BOOLEAN-PARAM-DEF
BSW Description
5

565 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
The QSEv will be sent to the Dem Module into a Security Event Memory (Sem) to persist it on the local ECU.
Template Description
This meta-class represents the ability to map a security event that is defined in the context of the Security Extract to a
diagnostic event defined on the context of the DiagnosticExtract.
M2 Parameter
DiagnosticExtract::Dem::DiagnosticMapping::DiagnosticEventToSecurityEventMapping
Mapping Rule Mapping Type
If the (M2) DiagnosticEventToSecurityEventMapping of the DEXT defines a mapping between the full
(M2) SecurityEventDefinition corresponding to the enclosing IdsMEvent and a (M2) Diagnostic
Event, then IdsMSinkDem = TRUE. Otherwise, IdsMSinkDem = FALSE.
Mapping Status ECUC Parameter ID
valid [ECUC_IdsM_00035]

566 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

F Splitable Elements in the Scope of this Document

This chapter contains a table of all model elements stereotyped atpSplitable
in the scope of this document.
Each entry in the table consists of the identification of the specific model element itself
and the applicable value of the tagged value atp.Splitkey.
For more information about the concept of splitable model elements and how these
shall be treated please refer to [24].
Name of splitable element Splitkey
DiagnosticAging.agingCycle agingCycle.diagnosticOperationCycle, aging
Cycle.variationPoint.shortLabel
DiagnosticContributionSet.commonProperties commonProperties
DiagnosticContributionSet.element element.diagnosticCommonElement,
element.variationPoint.shortLabel
DiagnosticContributionSet.serviceTable serviceTable.diagnosticServiceTable, service
Table.variationPoint.shortLabel
DiagnosticDataIdentifier.dataElement dataElement.bitOffset, dataElement.variation
Point.shortLabel
DiagnosticEcuInstanceProps.ecuInstance ecuInstance
DiagnosticEnableConditionGroup.enableCondition enableCondition.diagnosticEnableCondition, enable
Condition.variationPoint.shortLabel
DiagnosticEvent.connectedIndicator connectedIndicator.shortName, connected
Indicator.variationPoint.shortLabel
DiagnosticInfoType.dataElement dataElement.bitOffset, dataElement.variation
Point.shortLabel
DiagnosticIumprGroup.iumprGroupIdentifier iumprGroupIdentifier, iumprGroupIdentifier.variation
Point.shortLabel
DiagnosticParameter.dataElement dataElement.shortName, dataElement.variation
Point.shortLabel
DiagnosticParameterIdentifier.dataElement dataElement.bitOffset, dataElement.variation
Point.shortLabel
DiagnosticProtocol.diagnosticConnection diagnosticConnection.diagnosticConnection,
diagnosticConnection.variationPoint.shortLabel
DiagnosticProtocol.serviceTable serviceTable.diagnosticServiceTable, service
Table.variationPoint.shortLabel
DiagnosticSecurityAccess.securityLevel securityLevel
DiagnosticServiceTable.diagnosticConnection diagnosticConnection.diagnosticConnection,
diagnosticConnection.variationPoint.shortLabel
DiagnosticStorageConditionGroup.storageCondition storageCondition.diagnosticStorageCondition,
storageCondition.variationPoint.shortLabel
DiagnosticTroubleCodeGroup.dtc dtc.diagnosticTroubleCode, dtc.variationPoint.short
Label
DiagnosticTroubleCodeObd.eventReadinessGroup eventReadinessGroup, eventReadiness
Group.variationPoint.shortLabel
DiagnosticTroubleCodeProps.extendedDataRecord extendedDataRecord.diagnosticExtendedData
Record, extendedDataRecord.variationPoint.short
Label
DiagnosticTroubleCodeProps.freezeFrame freezeFrame.diagnosticFreezeFrame, freeze
Frame.variationPoint.shortLabel
Table F.1: Usage of splitable elements

567 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

G Variation Points in the Scope of this Document

This chapter contains a table of all model elements stereotyped atpVariation
in the scope of this document.
Each entry in the table consists of the identification of the model element itself and the
applicable value of the tagged value vh.latestBindingTime.
For more information about the concept of variation points and how model elements
that contain variation points shall be treated please refer to [24].
Variation Point Latest Binding Time
DiagnosticAbstractDataIdentifier.id preCompileTime
DiagnosticAging.agingCycle preCompileTime
DiagnosticAging.threshold preCompileTime
DiagnosticCommonProps codeGenerationTime
DiagnosticConnectedIndicator.healingCycleCounterThreshold preCompileTime
DiagnosticContributionSet.element postBuild
DiagnosticContributionSet.serviceTable postBuild
DiagnosticDataIdentifier.dataElement postBuild
DiagnosticDebounceAlgorithmProps.debounceBehavior preCompileTime
DiagnosticEnableConditionGroup.enableCondition postBuild
DiagnosticEvent.confirmationThreshold preCompileTime
DiagnosticEvent.connectedIndicator postBuild
DiagnosticFreezeFrame.recordNumber preCompileTime
DiagnosticIndicator.type preCompileTime
DiagnosticIumprGroup.iumprGroupIdentifier postBuild
DiagnosticMeasurementIdentifier.obdMid preCompileTime
DiagnosticParameter.dataElement postBuild
DiagnosticParameterIdentifier.dataElement postBuild
DiagnosticProtocol.diagnosticConnection postBuild
DiagnosticProtocol.priority preCompileTime
DiagnosticProtocol.sendRespPendOnTransToBoot preCompileTime
DiagnosticProtocol.serviceTable postBuild
DiagnosticRoutine.id preCompileTime
DiagnosticServiceTable.diagnosticConnection postBuild
DiagnosticStorageConditionGroup.storageCondition postBuild
DiagnosticTestIdentifier.id preCompileTime
DiagnosticTestIdentifier.uasId preCompileTime
DiagnosticTestResult.diagnosticEvent preCompileTime
DiagnosticTestResult.updateKind preCompileTime
DiagnosticTroubleCodeGroup.dtc postBuild
DiagnosticTroubleCodeGroup.groupNumber preCompileTime
DiagnosticTroubleCodeObd.considerPtoStatus preCompileTime
DiagnosticTroubleCodeObd.eventReadinessGroup postBuild
5

568 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate

 Diagnostic Extract Template
AUTOSAR CP R20-11

4
Variation Point Latest Binding Time
DiagnosticTroubleCodeObd.obdDTCValue preCompileTime
DiagnosticTroubleCodeProps.extendedDataRecord preCompileTime
DiagnosticTroubleCodeProps.freezeFrame preCompileTime
DiagnosticTroubleCodeProps.legislatedFreezeFrameContentWwhObd preCompileTime
DiagnosticTroubleCodeProps.priority preCompileTime
DiagnosticTroubleCodeProps.snapshotRecordContent preCompileTime
DiagnosticTroubleCodeUds.udsDtcValue preCompileTime
DiagnosticTroubleCodeUds.wwhObdDtcClass preCompileTime

Table G.1: Usage of variation points

569 of 569 Document ID 673: AUTOSAR_TPS_DiagnosticExtractTemplate