Requirements on Diagnostic Extract Template

AUTOSAR CP R23-11

Requirements on Diagnostic
Document Title Extract Template
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 681

Document Status published

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

Document Change History

Date Release Changed by Description
AUTOSAR
2023-11-23 R23-11 Release • No content changes
Management
AUTOSAR • Support for nested data structures
2022-11-24 R22-11 Release
Management • Remove superfluous requirement
AUTOSAR
2021-11-25 R21-11 Release • No content changes
Management
AUTOSAR
• Add requirements for security event
2020-11-30 R20-11 Release
reporting
Management
AUTOSAR • No content changes
2019-11-28 R19-11 Release • Changed Document Status from Final to
Management published
AUTOSAR
2018-10-31 4.4.0 Release • Editorial changes
Management
AUTOSAR
2017-12-08 4.3.1 Release • Editorial changes
Management
5

1 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
• Add requirements for OBD

• Add requirements for the support of Fim

AUTOSAR • Add requirements for the support of
2016-11-30 4.3.0 Release J1939
Management
• Minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
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 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-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 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

Contents
1 Introduction 9
1.1 Scope of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4 Requirements Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Requirements 13
2.1 Relation to AUTOSAR Features . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
[RS_DEXT_00001] Diagnostic data exchange . . . . . . . . . . . . . . . . 13
[RS_DEXT_00044] Derivation of related ECU-C parameter . . . . . . . . 14
[RS_DEXT_00048] Diagnostic Properties that are specific for one ECU . 14
[RS_DEXT_00058] Indicate that an ECU supports ODB . . . . . . . . . . 15
[RS_DEXT_00059] Support for different protocols . . . . . . . . . . . . . 15
2.3 Requirements against the Support for UDS Diagnostic Services . . . . . 15
[RS_DEXT_00003] SessionControl . . . . . . . . . . . . . . . . . . . . . . 16
[RS_DEXT_00004] ECUReset . . . . . . . . . . . . . . . . . . . . . . . . 16
[RS_DEXT_00005] ClearDiagnosticInformation . . . . . . . . . . . . . . . 16
[RS_DEXT_00006] ReadDTCInformation . . . . . . . . . . . . . . . . . . 16
[RS_DEXT_00007] ReadDataByIdentifier . . . . . . . . . . . . . . . . . . 17
[RS_DEXT_00008] ReadMemoryByAddress . . . . . . . . . . . . . . . . 17
[RS_DEXT_00009] SecurityAccess . . . . . . . . . . . . . . . . . . . . . . 17
[RS_DEXT_00010] CommunicationControl . . . . . . . . . . . . . . . . . 18
[RS_DEXT_00011] ReadDataByPeriodicIdentifier . . . . . . . . . . . . . . 18
[RS_DEXT_00012] DynamicallyDefineDataIdentifier . . . . . . . . . . . . 18
[RS_DEXT_00013] WriteDataByIdentifier . . . . . . . . . . . . . . . . . . 19
[RS_DEXT_00014] IOControl . . . . . . . . . . . . . . . . . . . . . . . . . 19
[RS_DEXT_00015] RoutineControl . . . . . . . . . . . . . . . . . . . . . . 19
[RS_DEXT_00016] RequestDownload . . . . . . . . . . . . . . . . . . . . 20
[RS_DEXT_00017] RequestUpload . . . . . . . . . . . . . . . . . . . . . 20
[RS_DEXT_00018] TransferData . . . . . . . . . . . . . . . . . . . . . . . 20
[RS_DEXT_00019] RequestTransferExit . . . . . . . . . . . . . . . . . . . 21
[RS_DEXT_00020] WriteMemoryByAddress . . . . . . . . . . . . . . . . 21
[RS_DEXT_00021] ControlDTCSetting . . . . . . . . . . . . . . . . . . . . 21
[RS_DEXT_00022] ResponseOnEvent . . . . . . . . . . . . . . . . . . . . 21
[RS_DEXT_00057] RequestFileTransfer . . . . . . . . . . . . . . . . . . . 22
[RS_DEXT_00047] Custom Diagnostic Service . . . . . . . . . . . . . . . 22
[RS_DEXT_00049] Properties of individual diagnostic services . . . . . . 22
[RS_DEXT_00050] Properties of all diagnostic services of a given kind . 23
[RS_DEXT_00051] Subfunctions of Diagnostic Services . . . . . . . . . . 23
[RS_DEXT_00043] Description of data elements . . . . . . . . . . . . . . 23
[RS_DEXT_00038] Description of nested elements of DIDs and RIDs . . 24
[RS_DEXT_00039] Diagnostic Service Table . . . . . . . . . . . . . . . . 24
2.4 Requirements against Event Handling . . . . . . . . . . . . . . . . . . . 24

4 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00023] Configuration of events . . . . . . . . . . . . . . . . . 25

[RS_DEXT_00024] Configuration of DTCs . . . . . . . . . . . . . . . . . . 25
[RS_DEXT_00026] Enable Conditions . . . . . . . . . . . . . . . . . . . . 25
[RS_DEXT_00027] Storage Conditions . . . . . . . . . . . . . . . . . . . 26
[RS_DEXT_00028] Enable Condition Groups . . . . . . . . . . . . . . . . 26
[RS_DEXT_00029] Storage Condition Groups . . . . . . . . . . . . . . . 26
[RS_DEXT_00030] Assignment of Enable Condition Groups . . . . . . . 27
[RS_DEXT_00031] Assignment of Storage Condition Group . . . . . . . . 27
[RS_DEXT_00032] Configuration of Extended Data Records . . . . . . . 27
[RS_DEXT_00033] Configuration of Snapshot Records . . . . . . . . . . 28
[RS_DEXT_00034] Description of Data Identifiers . . . . . . . . . . . . . 28
[RS_DEXT_00035] Description of Dynamic Data Identifiers . . . . . . . . 28
[RS_DEXT_00036] Description of Routine Identifiers . . . . . . . . . . . . 29
[RS_DEXT_00037] Description of I/O Identifiers . . . . . . . . . . . . . . 29
[RS_DEXT_00053] Debouncing of diagnostic events . . . . . . . . . . . . 29
[RS_DEXT_00054] Operation cycles . . . . . . . . . . . . . . . . . . . . . 29
[RS_DEXT_00055] Aging . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
[RS_DEXT_00056] Indicator . . . . . . . . . . . . . . . . . . . . . . . . . 30
[RS_DEXT_00045] Textual descriptions . . . . . . . . . . . . . . . . . . . 30
[RS_DEXT_00078] Support for In Use Monitor Performance Ratio . . . . 31
[RS_DEXT_00080] Support for persisting Security Events . . . . . . . . . 31
2.5 Requirements against Sessions and Security . . . . . . . . . . . . . . . 31
[RS_DEXT_00040] Diagnostic Sessions . . . . . . . . . . . . . . . . . . . 31
[RS_DEXT_00041] Access Permissions . . . . . . . . . . . . . . . . . . . 32
[RS_DEXT_00042] Security Levels . . . . . . . . . . . . . . . . . . . . . . 32
[RS_DEXT_00079] Support for environment conditions . . . . . . . . . . 32
2.6 Requirements against the Support for Function Inhibition . . . . . . . . . 33
[RS_DEXT_00060] Function . . . . . . . . . . . . . . . . . . . . . . . . . 33
[RS_DEXT_00061] Relationship between functions and diagnostic events 33
[RS_DEXT_00062] Pre-configuration of the Fim when the Dem configu-
ration is not yet available . . . . . . . . . . . . . . . . . . . . . 34
2.7 Requirements against the Support for diagnostics on J1939 . . . . . . . 34
[RS_DEXT_00064] Definition of an SPN . . . . . . . . . . . . . . . . . . . 34
[RS_DEXT_00065] Definition of freeze frames on J1939 . . . . . . . . . . 35
[RS_DEXT_00067] Definition of J1939 DTC . . . . . . . . . . . . . . . . . 35
2.8 Requirements against the Support for OBD Diagnostic Services . . . . . 35
[RS_DEXT_00068] Definition of a Diagnostic Parameter Identifier . . . . . 35
[RS_DEXT_00069] Support for OBD Mode 0x01 (RequestCurrentPow-
ertrainDiagnosticData) . . . . . . . . . . . . . . . . . . . . . . 36
[RS_DEXT_00070] Support for OBD Mode 0x02 (RequestPowertrain-
FreezeFrameData) . . . . . . . . . . . . . . . . . . . . . . . . . 36
[RS_DEXT_00071] Support for OBD ModeModes 0x03 / 0x07 / 0x0A
(RequestEmissionRelatedDiagnosticTroubleCodes) . . . . . . 36
[RS_DEXT_00072] Support for OBD Mode 0x04 (ClearResetEmission-
RelatedDiagnosticInformation) . . . . . . . . . . . . . . . . . . 37

5 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00073] Support for OBD Mode 0x06 (RequestOnBoard-

MonitoringTestResults) . . . . . . . . . . . . . . . . . . . . . . 37
[RS_DEXT_00074] Support for OBD Mode 0x08 (RequestControlOfOn-
BoardDevice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
[RS_DEXT_00075] Support for OBD Mode 0x09 (RequestVehicleInfor-
mation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
[RS_DEXT_00076] Definition of Diagnostic Test Identifier . . . . . . . . . 38
[RS_DEXT_00077] Description of the utilization of UDS for supporting
WWH-OBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.9 Requirements against the Mapping of Diagnostic Resources . . . . . . . 39
[RS_DEXT_00052] Mapping of diagnostic services to the PortProto-
types of ApplicationSwComponentTypes . . . . . . . . . . . . 39
[RS_DEXT_00025] Combined Events . . . . . . . . . . . . . . . . . . . . 39
[RS_DEXT_00063] Relation between functions on Fim level and
software-components . . . . . . . . . . . . . . . . . . . . . . . 39
[RS_DEXT_00066] Mapping between a J1939 controller application and
a software-component . . . . . . . . . . . . . . . . . . . . . . . 40
2.10 Miscellaneous Requirements . . . . . . . . . . . . . . . . . . . . . . . . 40
[RS_DEXT_00081] Support for updating the Reporting Mode of Security
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
A Change history of AUTOSAR traceable items 41
A.1 Traceable item history of this document according to AUTOSAR Re-
lease R4.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
A.1.1 Added Requirements in R4.2.1 . . . . . . . . . . . . . . . . . . 41
A.1.2 Changed Requirements in 4.2.1 . . . . . . . . . . . . . . . . . 42
A.1.3 Deleted Requirements in 4.2.1 . . . . . . . . . . . . . . . . . . 42
A.2 Traceable item history of this document according to AUTOSAR Re-
lease R4.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
A.2.1 Added Requirements in 4.2.2 . . . . . . . . . . . . . . . . . . . 42
A.2.2 Changed Requirements in 4.2.2 . . . . . . . . . . . . . . . . . 42
A.2.3 Deleted Requirements in 4.2.2 . . . . . . . . . . . . . . . . . . 43
A.2.4 Added Constraints in 4.2.2 . . . . . . . . . . . . . . . . . . . . 43
A.2.5 Changed Constraints in 4.2.2 . . . . . . . . . . . . . . . . . . . 43
A.2.6 Deleted Constraints in 4.2.2 . . . . . . . . . . . . . . . . . . . 43
A.3 Traceable item history of this document according to AUTOSAR Re-
lease R4.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
A.3.1 Added Requirements in 4.3.0 . . . . . . . . . . . . . . . . . . . 43
A.3.2 Changed Requirements in 4.3.0 . . . . . . . . . . . . . . . . . 44
A.3.3 Deleted Requirements in 4.3.0 . . . . . . . . . . . . . . . . . . 45
A.3.4 Added Constraints in 4.3.0 . . . . . . . . . . . . . . . . . . . . 45
A.3.5 Changed Constraints in 4.3.0 . . . . . . . . . . . . . . . . . . . 45
A.3.6 Deleted Constraints in 4.3.0 . . . . . . . . . . . . . . . . . . . 45
A.4 Traceable item history of this document according to AUTOSAR Re-
lease R4.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
A.4.1 Added Requirements in R4.3.1 . . . . . . . . . . . . . . . . . . 45

6 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

A.4.2 Changed Requirements in R4.3.1 . . . . . . . . . . . . . . . . 45

A.4.3 Deleted Requirements in R4.3.1 . . . . . . . . . . . . . . . . . 46
A.5 Traceable item history of this document according to AUTOSAR Re-
lease R4.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
A.5.1 Added Requirements in R4.4.0 . . . . . . . . . . . . . . . . . . 46
A.5.2 Changed Requirements in R4.4.0 . . . . . . . . . . . . . . . . 46
A.5.3 Deleted Requirements in R4.4.0 . . . . . . . . . . . . . . . . . 46
A.6 Traceable item history of this document according to AUTOSAR Re-
lease R19-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
A.6.1 Added Requirements in R19-11 . . . . . . . . . . . . . . . . . 46
A.6.2 Changed Requirements in R19-11 . . . . . . . . . . . . . . . . 46
A.6.3 Deleted Requirements in R19-11 . . . . . . . . . . . . . . . . . 46
A.7 Traceable item history of this document according to AUTOSAR Re-
lease R20-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
A.7.1 Added Requirements in R20-11 . . . . . . . . . . . . . . . . . 47
A.7.2 Changed Requirements in R20-11 . . . . . . . . . . . . . . . . 47
A.7.3 Deleted Requirements in R20-11 . . . . . . . . . . . . . . . . . 47
A.8 Traceable item history of this document according to AUTOSAR Re-
lease R21-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
A.8.1 Added Requirements in R21-11 . . . . . . . . . . . . . . . . . 47
A.8.2 Changed Requirements in R21-11 . . . . . . . . . . . . . . . . 47
A.8.3 Deleted Requirements in R21-11 . . . . . . . . . . . . . . . . . 47
A.9 Traceable item history of this document according to AUTOSAR Re-
lease R22-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
A.9.1 Added Requirements in R22-11 . . . . . . . . . . . . . . . . . 48
A.9.2 Changed Requirements in R22-11 . . . . . . . . . . . . . . . . 48
A.9.3 Deleted Requirements in R22-11 . . . . . . . . . . . . . . . . . 48
A.10 Traceable item history of this document according to AUTOSAR Re-
lease R23-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
A.10.1 Added Requirements in R23-11 . . . . . . . . . . . . . . . . . 48
A.10.2 Changed Requirements in R23-11 . . . . . . . . . . . . . . . . 48
A.10.3 Deleted Requirements in R23-11 . . . . . . . . . . . . . . . . . 48

7 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

References
[1] Standardization Template
AUTOSAR_FO_TPS_StandardizationTemplate
[2] Unified diagnostic services (UDS) – Part 1:Specification and requirements (Re-
lease 2006-12)
https://www.iso.org
[3] Specification of Diagnostic Communication Manager
AUTOSAR_CP_SWS_DiagnosticCommunicationManager
[4] Specification of Diagnostic Event Manager
AUTOSAR_CP_SWS_DiagnosticEventManager
[5] Motor Vehicle Pollution Control Devices
https://www.iso.org
[6] Specification of Function Inhibition Manager
AUTOSAR_CP_SWS_FunctionInhibitionManager
[7] Road vehicles – Communication between vehicle and external equipment for
emission-related diagnostic – Part 5:Emission-related diagnostic services.
https://www.iso.org

8 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

1 Introduction

1.1 Scope of this document

This document collects the requirements on the Diagnostic Extract.
The main goal of the Diagnostic Extract is to exchange diagnostic data between the dif-
ferent parties involved in the diagnostic development process to support the automatic
code generation process for diagnostic modules DCM and DEM.
Further, the Diagnostic Extract is used to support the distributed development process
for diagnostic functionality.
Below, the key aspects for the usage of the Diagnostic Extract are mentioned again:
• Exchange of diagnostic data for DCM and DEM
• Support of distributed development for diagnostic functionality

9 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

1.2 Document Conventions

The representation of requirements in AUTOSAR documents follows the table specified
in [TPS_STDT_00078], see Standardization Template, chapter Support for Traceability
([1]).
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 ([1]).

10 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

1.3 Guidelines
Existing specifications shall be referenced (in form of a single requirement). Differ-
ences to these specifications are specified as additional requirements. All Require-
ments shall have the following properties:
• Redundancy
Requirements shall not be repeated within one requirement or in other require-
ments.
• Clearness
All requirements shall allow one possibility of interpretation only. Used technical
terms that are not in the glossary must be defined.
• Atomicity
Each Requirement shall only contain one requirement. A Requirement is atomic
if it cannot be split up in further requirements.
• Testability
Requirements shall be testable by analysis, review or test.
• Traceability
The source and status of a requirement shall be visible at all times.

11 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

1.4 Requirements Tracing

Currently no requirements tracing is provided for this document. Requirement tracing
will be included in later revision.

12 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

2 Requirements

2.1 Relation to AUTOSAR Features

The section describes a list of features that should be addressed by the requirements:
• [RS_Main_00300] AUTOSAR shall provide data exchange formats to support
work-share in large inter and intra-company development groups
• [RS_BRF_01112] AUTOSAR shall offer interfaces to boot loaders.
• [RS_BRF_01440] AUTOSAR services shall support system diagnostic function-
ality.
This is a short selection of features and main requirements which need to be fulfilled
by the requirements on the Diagnostic Extract.

2.2 General Requirements

This chapter contains a collection of general requirements that apply for all aspects of
the Diagnostic Extract.
[RS_DEXT_00001] Diagnostic data exchange d

Description: The diagnostic extract shall support the exchange of diagnostics-related

information.
The configuration of the AUTOSAR diagnostics stack, in the vast majority of
cases, is a joint effort with contributions from the OEM and the respective ECU
supplier.

Rationale: For this purpose, the OEM and the supplier need to be able to exchange
configuration information with as little friction as possible. In general, arbitrary
combinations of particular OEMs and specific suppliers are possible. To make
this work it is necessary to standardize the data exchanged between the
affected parties to the necessary extent.
1. OEM delivers a partial configuration to a supplier that in turn is expected to
fill in the missing pieces and/or review and (where applicable) overwrite
configuration done by the OEM.
2. Supplier feeds back reviewed diagnostics configuration to the OEM.
Use Case: 3. Supplier delivers the final configuration of the diagnostics stack back to the
OEM such that the latter is able to derive a tester configuration from this data.
4. Suppliers or OEMs use the Diagnostic Extract to exchange the information
within the company between related responsible organization parts. By this
means a distributed software development is supported within the company.
Dependencies: –
5

13 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting –
Material:

c()
[RS_DEXT_00044] Derivation of related ECU-C parameter d

The Diagnostic Extract shall support the derivation of related ECU-C

Description:
parameters for Dcm, Fim and Dem.
A concrete configuration of an AUTOSAR diagnostic stack on the level of
ECUC is, by definition, not portable. It is very much focused on specific details
that reflect the specific implementation of the particular diagnostic stack. This
approach is reasonable because it allows for a deeper optimization of the
software stack than a general and more abstract approach would support.
Rationale: However, the more abstract approach has other benefits in terms of being
exchangeable across different organizations and, to some extent, even
projects.
Therefore, it is reasonable to define a general and more abstract way of
configuring the diagnostic stack for which the ultimate goal is to derive the
concrete and non-portable specific configuration to a large extent.
A user wants the specify configuration of the diagnostic stack in a general way
that can be exchanged with project partners in the same way that e.g. a system
description can be exchanged.
The user wants to specify the diagnostic information on the same conceptual
Use Case: level as the system extract and the user wants to relate from the diagnostic
configuration to elements of a system extract where applicable. Finally,
someone wants to take this information that is described on a higher
conceptual level and use if for the derivation of configuration information on the
much more specific (and, consequently, less portable) level that is ECUC.
Dependencies: –
Supporting –
Material:

c()
[RS_DEXT_00048] Diagnostic Properties that are specific for one ECU d

The Diagnostic Extract shall support the definition of diagnostic properties that
Description:
are specific for a given ECU.
Some properties differ from ECU to ECU. In case the diagnostic extract covers
Rationale: multiple ECUs at the same time it is necessary to express their diagnostic
properties individually.
The user wants to specify a diagnostic extract consisting of several ECUs and
Use Case: the user wants to define certain properties individually for each of the included
ECUs.
Dependencies: –
5

14 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting –
Material:

c()
[RS_DEXT_00058] Indicate that an ECU supports ODB d

The diagnostic extract shall allow for the definition of whether (and how) a given
Description:
ECU supports OBD
There are certain switches to be set in the downstream configuration that
Rationale: depend on the information about the OBD capabilities of a given ECU.
Use Case: The user wants to specify the applicability of OBD for a given ECU
Dependencies: –
Supporting
Material:

c()
[RS_DEXT_00059] Support for different protocols d

The diagnostic extract shall support the definition of different diagnostic

Description:
protocols (e.g. UDS, OBD, etc.) and their priority in relation to each other.
Different protocols shall be handled with different priorities. This requires a
Rationale: formal definition of a diagnostic protocol and its relation to further model
elements that are already part of the diagnostic extract.
The user wants to define a diagnostic extract that supports different diagnostic
Use Case:
protocols.
Dependencies: –
Supporting
Material:

c()

2.3 Requirements against the Support for UDS Diagnostic Ser-

vices
This chapter contains a collection of requirements against the context of UDS diagnos-
tic services according to [2].

15 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00003] SessionControl d

The Diagnostic Extract shall support the configuration of UDS service 0x10
Description:
(SessionControl).
The usage of different diagnostic sessions is very common and therefore
Rationale: needs to be supported by the Diagnostic Extract Template.
Use Case: Support the switching from one diagnostic session to another.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00004] ECUReset d

The Diagnostic Extract shall support the configuration of UDS service 0x11
Description:
(ECUReset).
Rationale: The ability to reset the server is crucial for conducing a diagnostic session.
Use Case: The user wants to reset the connected server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00005] ClearDiagnosticInformation d

The Diagnostic Extract shall support the configuration of UDS service 0x14
Description:
(ClearDiagnosticInformation).
The service allows for clearing the diagnostic memory of a server. This is a
Rationale:
frequently used functionality.
Use Case: The user wants to clear diagnostic memory on the connected server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00006] ReadDTCInformation d

The Diagnostic Extract shall support the configuration of UDS service 0x19
Description:
(ReadDTCInformation).
The service allows for accessing the status of a diagnostic trouble code on the
Rationale:
server. This is a frequently used functionality.
Use Case: The user wants to access DTC information via a tester on the server.
Dependencies: –
5

16 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00007] ReadDataByIdentifier d

The Diagnostic Extract shall support the configuration of UDS service 0x22
Description:
(ReadDataByIdentifier).
The service allows for reading values on the server according to the definition
Rationale: of a given data identifier. This is a frequently used functionality.
The user wants to read the values associated with a given data identifier from
Use Case:
the server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00008] ReadMemoryByAddress d

The Diagnostic Extract shall support the configuration of UDS service 0x23
Description:
(ReadMemoryByAddress).
The service allows for accessing the content of a piece of memory on the
Rationale:
server. This is a frequently used functionality.
Use Case: The user wants to read memory content from the diagnostic server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00009] SecurityAccess d

The Diagnostic Extract shall support the configuration of UDS service 0x27
Description:
(SecurityAccess).
This service allows for data and diagnostic services for which specific security
Rationale:
restrictions apply.
The application of security restrictions limits the access to data and diagnostic
Use Case: services to authorized personnel. The restriction may be applied for safety
and/or security reasons.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()

17 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00010] CommunicationControl d

The Diagnostic Extract shall support the configuration of UDS service 0x28
Description:
(CommunicationControl).
This service allows for switching on and off the communication of certain
Rationale: messages (e.g. application-related communication).
Use Case: The user wants to switch off normal communication messages.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00011] ReadDataByPeriodicIdentifier d

The Diagnostic Extract shall support the configuration of UDS service 0x2A
Description:
(ReadDataByPeriodicIdentifier).
The service allows for requesting the periodic transmission of diagnostic data
Rationale: by the server according to the definition of a periodic data identifier.
The user wants to get access to diagnostic data that is transmitted periodically
Use Case: without the necessity to request each transmission individually.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00012] DynamicallyDefineDataIdentifier d

The Diagnostic Extract shall support the configuration of UDS service 0x2C
Description:
(DynamicallyDefineDataIdentifier).
The service allows for the ad-hoc definition of a data identifier that can then be
Rationale: accessed by the respective diagnostic services.
In contrast to the case where data identifiers are defined in advance of a
Use Case: diagnostic session, this service allows for defining data identifiers while a
diagnostic session is ongoing.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()

18 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00013] WriteDataByIdentifier d

The Diagnostic Extract shall support the configuration of UDS service 0x2E
Description:
(WriteDataByIdentifier).
The service allows for transmitting diagnostic data identified by the association
Rationale: with a diagnostic data identifier to a diagnostic server. This is a frequently used
functionality.
The user wants to transmit data associated with a given data identifier to the
Use Case: diagnostic server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00014] IOControl d

The Diagnostic Extract shall support the configuration of UDS service 0x2F
Description:
(IOControl).
The service allows for substituting values of the I/O layer with values provided
Rationale: by the diagnostic tester.
The user wants to bypass a sensor and feeds substitution values instead. The
Use Case: user wants to substitute values provided to a given actuator.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00015] RoutineControl d

The Diagnostic Extract shall support the configuration of UDS service 0x31
Description:
(RoutineControl).
Rationale: The service can be used to execute specific code on the server according.
The user wants to execute code on the remote server in order to achieve a
Use Case: given functionality that goes beyond the capabilities provided by any of the
“simple” data exchange services.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()

19 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00016] RequestDownload d

The Diagnostic Extract shall support the configuration of UDS service 0x34
Description:
(RequestDownload).
This service has the ability to request the server to accept the transfer of a
Rationale: piece of data from the client (e.g. tester) to the server. Support for this service
is the prerequisite for a support of the service described in [RS_DEXT_00018].
The user wants to transmit a piece of (mostly complex) data from the client to
Use Case:
the server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00017] RequestUpload d

The Diagnostic Extract shall support the configuration of UDS service 0x35
Description:
(RequestUpload).
This service has the ability to request the server to accept the transfer of a
Rationale: piece of data from the server to a client (e.g. tester). Support for this service is
the prerequisite for a support of the service described in [RS_DEXT_00018].
The user wants to transmit a piece of (mostly complex) data from the server to
Use Case:
the client.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00018] TransferData d

The Diagnostic Extract shall support the configuration of UDS service 0x36
Description:
(TransferData).
This service is used to actually execute a data transfer between client and
Rationale:
server.
The user wants to transmit a piece of (mostly complex) data between client and
Use Case:
server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()

20 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00019] RequestTransferExit d

The Diagnostic Extract shall support the configuration of UDS service 0x37
Description:
(RequestTransferExit).
The service can be taken to request the termination of a data transmission
Rationale: between server and client (independent of the direction of the data
transmission).
Use Case: The user wants to actively end a data transmission between client and server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00020] WriteMemoryByAddress d

The Diagnostic Extract shall support the configuration of UDS service 0x3D
Description:
(WriteMemoryByAddress).
Rationale: The service can be used to write a piece of data to the server’s memory.
Use Case: The user wants to overwrite the values in a given piece of server memory.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00021] ControlDTCSetting d

The Diagnostic Extract shall support the configuration of UDS service 0x85
Description:
(ControlDTCSetting).
The service can be used to control the updating of status bits of diagnostic
Rationale:
trouble codes in the server.
The user wants to either stop or resume the updating of status bits of
Use Case: diagnostic trouble codes in the server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00022] ResponseOnEvent d

The Diagnostic Extract shall support the configuration of UDS service 0x86
Description:
(ResponseOnEvent).
The service can be used to control the behavior of the server with respect to
Rationale: the transmission of data in response to a given event.
The user wants to control the behavior of the server in terms of how the server
Use Case: sends response messages according to the existence of a given event.
5

21 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00057] RequestFileTransfer d

The Diagnostic Extract shall support the configuration of UDS service 0x38
Description:
(RequestFileTransfer).
The service RequestFileTransfer is part of the subset of UDS services
Rationale: supported by the Diagnostic Extract.
Use Case: The user wants to specify a file transfer to/from the server.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00047] Custom Diagnostic Service d

Description: The Diagnostic Extract shall support the definition of custom diagnostic
services.
In some cases diagnostic services beyond the set of services standardized in
Rationale:
ISO14229 are needed.
The user wants to execute a diagnostic functionality that is not part of the
Use Case:
specification of ISO 14229 [2]
Dependencies: –
Supporting –
Material:

c()
[RS_DEXT_00049] Properties of individual diagnostic services d

The Diagnostic Extract shall support the definition of properties that are specific
Description:
for a given diagnostic service.
Some properties of diagnostic services need to be individually fine-tuned for
Rationale: every instance of a given class of diagnostic service, e.g. ReadDataByIdentifier.
The user wants to define specific properties differently for all instances of a
Use Case: given diagnostic service.
Dependencies: –
Supporting –
Material:

c()

22 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00050] Properties of all diagnostic services of a given kind d

The Diagnostic Extract shall support the definition of properties that are
Description:
common for all instances of a kind of diagnostic service.
Some properties of diagnostic services are common for all instances of the
specific diagnostic service. If these were specifiable on an individual basis
Rationale: there would be potential for inconsistencies in the specification of different
instances of the diagnostic service.
The user wants to define specific properties that are shared among all
Use Case: instances of a given diagnostic service.
Dependencies: –
Supporting –
Material:

c()
[RS_DEXT_00051] Subfunctions of Diagnostic Services d

Description: The Diagnostic Extract shall support the definition of subfunctions of diagnostic
services.
The definition of subfunctions is an important part of the definition of diagnostic
Rationale: services. Also, the existence of subfunctions for certain diagnostic services is
regulated by the applicable ISO 14229-1 [2].
Use Case: The user wants to specify subfunctions for given diagnostic services.
Dependencies: –
Supporting –
Material:

c()
[RS_DEXT_00043] Description of data elements d

The Diagnostic Extract shall support the description of data elements for
Description:
diagnostic services.
Data elements represent a formal specification of the content of diagnostic
messages exchanged between a client and a server. The formal definition of
the elements of the messages allows for a clearer idea of what is actually
Rationale: exchanged. Plus, it is possible to check the consistency of data elements
defined in the diagnostic extract to data elements in the application software to
which the diagnostic service is finally connected to.
The user wants to create a fine-grained model of the content of diagnostic
Use Case: messages exchanged between client and server.
Dependencies: –
Supporting –
Material:

c()

23 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00038] Description of nested elements of DIDs and RIDs d

The Diagnostic Extract shall support the usage of nested data elements for the
Description: DID sender/receiver and RID routine interaction between the Dcm and
application software.
Nested data types are a commonly used case in AUTOSAR application
software. Consequently, the AUTOSAR diagnostic stack and, by extension, the
Rationale:
Diagnostic Extract needs to support this case for the interaction between the
Dcm and application software.
The user wants to access a nested data type in a PortPrototype of the
Use Case: application to be used in the description of diagnostic content (e.g. the
definition of a Diagnostic Data Identifier)
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()
[RS_DEXT_00039] Diagnostic Service Table d

The Diagnostic Extract shall support the capability to specify a Diagnostic

Description:
Service Table.
The Diagnostic Service Table represents the amount of services necessary for
the applicable Diagnostic Protocol. The service table is a central aspect of the
Rationale: configuration of the diagnostic stack and shall therefore be supported by the
Diagnostic Extract.
The user wants to define a specific Diagnostic protocol in the context of a
Use Case: project. As far as the Diagnostic Extract is concerned, this requires the
definition of a Diagnostic Service Table.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()

2.4 Requirements against Event Handling

This chapter contains a collection of requirements against the general context of diag-
nostic events and diagnostic trouble codes.

24 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00023] Configuration of events d

Description: The Diagnostic Extract shall support the configuration of diagnostic events.
The definition of diagnostic events is key for the configuration of the AUTOSAR
Dem. Diagnostic events are rich with additional information that needs to be
Rationale: provided as part of the definition of the diagnostic event. Furthermore,
diagnostic events have relations to other entities that also need to be expressed
as part of the diagnostic extract.
The user wants to formally define the result of a diagnostic monitor. This is a
Use Case:
typical task of (but not restricted to) the supplier’s workflow.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00024] Configuration of DTCs d

Description: The Diagnostic Extract shall support the configuration of DTCs.

The diagnostic stack foresees the existence of entities called diagnostic trouble
codes (DTC) that, from a simplified point of view, represent reportable incidents
Rationale: towards a diagnostic tester. In reality, a DTC has more complex features that
need to be supported by the diagnostic extract as well.
The user wants too define a unique identifier that represents a given fault
Use Case: situation, which in turn can be reported to a diagnostic tester.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00026] Enable Conditions d

Description: The Diagnostic Extract shall support the configuration of Enable Conditions.
AUTOSAR foresees the existence of conditions that govern the processing of a
diagnostic event. It shall be possible to define conditions that control how
Rationale: specific diagnostic events are enabled (i.e. will be processed) or disabled (i.e.
processing will be blocked).
The user wants to define a diagnostic enable condition that impacts the
Use Case: processing of diagnostic events.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()

25 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00027] Storage Conditions d

Description: The Diagnostic Extract shall support the configuration of Storage Conditions.
AUTOSAR foresees the existence of conditions that control whether or not a
diagnostic event is stored in event memory. These conditions are part of the
Rationale: configuration of the diagnostic stack. It is therefore necessary to also be able to
define storage conditions in the diagnostic extract.
The user wants to define storage conditions for a given event. These storage
Use Case: conditions shall later be taken to derive the configuration of the AUTOSAR
diagnostic stack.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00028] Enable Condition Groups d

The Diagnostic Extract shall support the collection of Enable Conditions by

Description:
means of Enable Condition Groups.
The definition of an Enable Condition Group facilitates the handling of Enable
Conditions in general. This applies in particular for Diagnostic Events that
depend on a shared collection of enable conditions. It is therefore required that
Rationale:
the Diagnostic Extract supports the definition of Enable Condition Groups that
can later be taken to contribute to the configuration of the AUTOSAR diagnostic
stack.
The user wants to group several Diagnostic Enable Conditions to a single
Use Case: Enable Condition Group that can then be used to express the relation of given
Diagnostic Events to the definition of Enable Conditions in a single step.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00029] Storage Condition Groups d

he Diagnostic Extract shall support the collection of Storage Conditions by

Description:
means of Storage Condition Groups.
The definition of an Storage Condition Group facilitates the handling of Storage
Conditions in general. This applies in particular for Diagnostic Events that
depend on a shared collection of Storage conditions. It is therefore required
Rationale: that the Diagnostic Extract supports the definition of Storage Condition Groups
that can later be taken to contribute to the configuration of the AUTOSAR
diagnostic stack.
The user wants to group several Diagnostic Storage Conditions to a single
Use Case: Storage Condition Group that can then be used to express the relation of given
Diagnostic Events to the definition of Storage Conditions in a single step.
Dependencies: –
5

26 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00030] Assignment of Enable Condition Groups d

The Diagnostic Extract shall support the assignment of Enable Condition

Description:
Groups to an event.
A consequence of the existence of Diagnostic Enable Condition and Enable
Rationale: Condition Groups is that it should be possible to establish a relation of one with
the other.
The user wants to collect several Diagnostic Enable Conditions in the context of
Use Case: one Enable Condition Group. This way, the configuration of the relation of
Diagnostic Events to Enable Conditions can be significantly facilitated.
Dependencies: [RS_DEXT_00028]
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00031] Assignment of Storage Condition Group d

The Diagnostic Extract shall support the assignment of Storage Condition

Description:
Groups to an event.
A consequence of the existence of Diagnostic Storage Condition and Storage
Rationale: Condition Groups is that it should be possible to establish a relation of one with
the other.
The user wants to collect several Diagnostic Storage Conditions in the context
Use Case: of one Storage Condition Group. This way, the configuration of the relation of
Diagnostic Events to Storage Conditions can be significantly facilitated.
Dependencies: [RS_DEXT_00029]
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00032] Configuration of Extended Data Records d

Description: The Diagnostic Extract shall support the configuration of Extended Data
Records.
Extended Data Records, like Freeze Frames, are used to store additional
Rationale: information related to a Diagnostic Event and shall therefore also be supported
by the Diagnostic Extract.
The user wants to define additional information to be stored along with a given
Use Case: Diagnostic Event in event memory.
Dependencies: –
5

27 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00033] Configuration of Snapshot Records d

The Diagnostic Extract shall support the configuration of Snapshot Records

Description:
(Freeze Frames).
Freeze Frames, like Extended Data Records, are used to store additional
Rationale: information related to a Diagnostic Event and shall therefore also be supported
by the Diagnostic Extract.
The user wants to define the content of a Freeze frame to be stored along with
Use Case: a given Diagnostic Event in event memory.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00034] Description of Data Identifiers d

The Diagnostic Extract shall support the description of Data Identifiers for
Description:
Diagnostic Services.
The definition of Data Identifiers is a central part of the configuration of the
Rationale: AUTOSAR diagnostic stack.
Use Case: The user wants to define a Diagnostic Data Identifier with a given content.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()
[RS_DEXT_00035] Description of Dynamic Data Identifiers d

The Diagnostic Extract shall support the description of Dynamic Data Identifiers
Description:
for Diagnostic Services.
The definition of Dynamic Data Identifiers is a central part of the configuration
Rationale: of the AUTOSAR diagnostic stack.
The user wants to specify that a Diagnostic Data Identifier can be used as a
Use Case: Diagnostic Dynamic Data Identifier.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()

28 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00036] Description of Routine Identifiers d

The Diagnostic Extract shall support the description of Routine Identifiers for
Description:
Diagnostic Services.
The definition of Routine Identifiers is a central part of the configuration of the
Rationale: AUTOSAR diagnostic stack.
The user wants to define a Routine Identifier associated with a given Diagnostic
Use Case: Routine. This typically extend to the modeling of the Diagnostic Routine itself.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()
[RS_DEXT_00037] Description of I/O Identifiers d

The Diagnostic Extract shall support the description of I/O Identifiers for
Description:
Diagnostic Services.
The definition of I/O Identifiers is a central part of the configuration of the
Rationale: AUTOSAR diagnostic stack.
The user wants to define an I/O Identifier. This typically extends to the
Use Case: modeling of the Diagnostic Data Identifier.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()
[RS_DEXT_00053] Debouncing of diagnostic events d

Description: The Diagnostic Extract shall support the specification of how Diagnostic Events
shall be debounced.
Typically, a debouncing algorithm (as defined by the SWS Dem) is applied to
Rationale: the occurrence of Diagnostic Events in order to avoid the existence of false
positives. This aspect shall be supported by the Diagnostic Extract as well.
The user wants to define how debouncing shall be applied to a given
Use Case: Diagnostic Event.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00054] Operation cycles d

Description: The Diagnostic Extract shall support the specification of operation cycles.
The AUTOSAR diagnostic stack supports the configuration of operation cycles.
Rationale: This aspect shall therefore be supported by the Diagnostic Extract.
5

29 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
The user wants to assign a specific operation cycle to a diagnostic event
Use Case: depending on the project needs.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00055] Aging d

Description: The Diagnostic Extract shall support the specification of aging.

It is common practice that events are removed from fault memory after a certain
Rationale: succession of “passed” reports for this event. This aspect shall be supported by
the Diagnostic Extract.
The user wants to specify the way in which specific Diagnostic Events shall be
Use Case: subject to aging.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00056] Indicator d

Description: The Diagnostic Extract shall support the specification of indicators.

The diagnostic stack is supposed to support the signaling of certain Diagnostic
Rationale: Events to the driver of a vehicle. The signaling shall be modeled as a
diagnostic indicator.
Use Case: The user wants to specify how Diagnostic Events are indicated to the driver.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00045] Textual descriptions d

The Diagnostic Extract shall support the capability to specify textual

Description:
descriptions for Diagnostic Events and DTC attributes.
The ability to attach textual descriptions to the definition of diagnostic model
Rationale: elements allows for a better transport of knowledge about the purpose and the
semantics of the respective model elements.
The user wants to provide a proper textual documentation of specific model
Use Case: elements related to the description of a Diagnostic Extract.
Dependencies: –
5

30 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting –
Material:

c()
[RS_DEXT_00078] Support for In Use Monitor Performance Ratio d

The diagnostic extract shall support the definition of In Use Monitor

Description:
Performance Ratio (IUMPR).
Rationale: The definition of IUMPR is an integral part of the application of OBD.
Use Case: The user wants to specify the IUMPR with respect to given diagnostic events.
Dependencies: –
Supporting More information about this aspect can be found in the respective law
Material: publication [5].

c()
[RS_DEXT_00080]{DRAFT} Support for persisting Security Events d

In some cases, security events need to be persisted such that they can later be
Description:
queried by a diagnostic tester.
The occurence of security events can be a very important part of a forensical
Rationale:
analysis of an intrusion.
The user wants to specify which security events shall be persisted in the
Use Case:
Security Event Memory that is part of the Dem
Dependencies: –
Supporting
Material:

c()

2.5 Requirements against Sessions and Security

This chapter contains a collection of requirements against the context of diagnostic
sessions and security.
[RS_DEXT_00040] Diagnostic Sessions d

The Diagnostic Extract shall support the capability to specify Diagnostic

Description:
Sessions.
The configuration of Diagnostic Sessions represents an important angle of the
Rationale: configuration of the AUTOSAR diagnostic stack. Therefore, the Diagnostic
Extract needs to support the modeling of this aspect.
Use Case: The user wants to define Diagnostic Sessions as part of a project.
Dependencies: –
5

31 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00041] Access Permissions d

Description: The Diagnostic Extract shall support the capability to specify Access
Permissions.
The configuration of Access Permissions represents an important angle of the
Rationale: configuration of the AUTOSAR diagnostic stack. Therefore, the Diagnostic
Extract needs to support the modeling of this aspect.
The user wants to define specific diagnostic functionality, e.g. DIDs or RIDs that
Use Case:
require Access Permissions as part of a project.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00042] Security Levels d

Description: The Diagnostic Extract shall support the capability to specify Security Levels.
The configuration of Security Levels represents an important angle of the
Rationale: configuration of the AUTOSAR diagnostic stack. Therefore, the Diagnostic
Extract needs to support the modeling of this aspect.
Use Case: The user wants to define Security Levels as part of a project.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [2].

c()
[RS_DEXT_00079] Support for environment conditions d

The Diagnostic Extract shall support the formulation of environment conditions

Description:
that enable the processing of diagnostic functionality.
Some diagnostic functionalities are only safe if the vehicle is in a certain state.
Rationale: Therefore, it should be possible to specify the conditions for executing
diagnostic functionalities on the level of the diagnostic extract.
The user wants to execute a diagnostic functionality that requires the vehicle to
Use Case:
be stopped (i.e. the condition is that vehicle speed == 0).
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Communication Manager [3].

c()

32 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

2.6 Requirements against the Support for Function Inhibition

This chapter contains a collection of requirements against the support for function in-
hibition in the diagnostic extract.
[RS_DEXT_00060] Function d

The Diagnostic Extract shall support the definition of a function for the purpose
Description: of function inhibition. The function shall have an identification by which it can be
identified further downstream the configuration.
In order to be able to define function inhibition, it is essential to have model
Rationale:
elements that represent a function.
The user wants to specify a function that can then be used in the scope of
Use Case:
function inhibition.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Function
Material: Inhibition Manager [6].

c()
[RS_DEXT_00061] Relationship between functions and diagnostic events d

The Diagnostic Extract shall support the relationship between a function and
the diagnostic events that are no longer reported if the respective function is
inhibited.
Description: It shall be possible to express the relationship between a function and the
corresponding events on different levels of granularity. This means that it shall
be possible to refer to single diagnostic events as well as to an entire collection
of diagnostic events.
The disabling of reporting of diagnostic events is a core functionality of the Fim.
Rationale: It shall be possible to describe this aspect in the diagnostic extract
The user wants to specify how a specific function inhibits the reporting of a
given collection of diagnostic events. Instead of having to refer to every single
Use Case: intended diagnostic event the user wants to have the ability to shortcut this
effort by referring to a group of events formalized by means of the diagnostic
extract.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Function
Material: Inhibition Manager [6].

c()

33 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00062] Pre-configuration of the Fim when the Dem configuration is

not yet available d

At the point in time when the configuration of the Fim in the diagnostic extract is
created it may be possible that the configuration of the Dem in the diagnostic
extract does not exist yet.
Therefore, there are no formalized representation of diagnostic events available
Description: that could be taken for the creation of the Fim’s pre-configuration.
Therefore, the diagnostic extract shall provide the ability to define placeholders
for diagnostic events that can be used in the pre-configuration of the Fim and
later be replaced by the real diagnostic events when the Dem configuration in
the diagnostic extract becomes available.
The concept of a decentralized configuration supports the idea the certain parts
Rationale: of the diagnostic extract shall be defined independently from each other and
then later merged to form the configuration of an entire diagnostic stack.
The user wants to model the relation between functions and diagnostic events
Use Case: before the definition of the actual diagnostic events is available.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Function
Material: Inhibition Manager [6].

c()

2.7 Requirements against the Support for diagnostics on J1939

This chapter contains a collection of requirements against the support for diagnostics
on J1939 in the diagnostic extract.
[RS_DEXT_00064] Definition of an SPN d

The diagnostic extract shall support the definition of an SPN as well as the
Description: representation of a communication item in the system description along with its
physical properties.
The so-called Suspect Parameter Number (SPN) is a prominent concept inside
Rationale: J1939 diagnostics. The SPN can also refer to physical properties.
The user wants to specify a J1939 SPN by means of the diagnostic extract.
The user wants to specify how the SPN is represented in the system
Use Case:
description. The user wants to make sure that the intended physical properties
are available in the system description.
Dependencies: –
Supporting –
Material:

c()

34 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00065] Definition of freeze frames on J1939 d

The diagnostic extract shall support the definition of freeze frames (both regular
Description:
and expanded) on J1939
The definition of freeze frames on J1939 is an important part of the
Rationale: configuration of a J1939 diagnostics stack.
Use Case: The user wants to define the content of J1939 freeze frames.
Dependencies: –
Supporting –
Material:

c()
[RS_DEXT_00067] Definition of J1939 DTC d

The diagnostic extract shall support the definition of a DTC in the domain of
Description:
J1939 with all its specific properties.
The definition of a DTC is an important part of a diagnostic stack. The DTCs in
Rationale: the J1939 domain have specific properties that are clearly separate from the
properties of e.g. UDS DTCs.
The user wants to specify a DTC within the configuration of the J1939
Use Case: diagnostic stack in the diagnostic extract.
Dependencies: –
Supporting –
Material:

c()

2.8 Requirements against the Support for OBD Diagnostic Ser-

vices
This chapter contains a collection of requirements against the context of OBD diagnos-
tic services according to [7].
[RS_DEXT_00068] Definition of a Diagnostic Parameter Identifier d

The diagnostic extract shall support the formal definition of diagnostic

Description: parameter identifiers (PID). The formal representation of the PID shall have a
numerical identifier that shall be used for downstream configuration.
A PID plays a central role in the modeling of OBD services. The definition of
Rationale:
PIDs is key for the support of OBD services.
Use Case: The user wants to define a PID in order to model OBD services.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()

35 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00069] Support for OBD Mode 0x01 (RequestCurrentPowertrainDiag-

nosticData) d

The diagnostic extract shall support the modeling of the OBD mode 0x01, a.k.a.
Description:
RequestCurrentPowertrainDiagnosticData.
The OBD mode 0x01 is a mandatory part of the OBD functionality and
Rationale: therefore a representation of this mode is required in the diagnostic extract.
Use Case: The user wants to model the OBD service 0x01 in the diagnostic extract.
Dependencies: [RS_DEXT_00068]
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()
[RS_DEXT_00070] Support for OBD Mode 0x02 (RequestPowertrainFreeze-
FrameData) d

The diagnostic extract shall support the modeling of the OBD mode 0x02, a.k.a.
Description:
RequestPowertrainFreezeFrameData.
The OBD mode 0x02 is a mandatory part of the OBD functionality and
Rationale: therefore a representation of this mode is required in the diagnostic extract.
Use Case: The user wants to model the OBD service 0x02 in the diagnostic extract.
Dependencies: [RS_DEXT_00068]
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()
[RS_DEXT_00071] Support for OBD ModeModes 0x03 / 0x07 / 0x0A (RequestE-
missionRelatedDiagnosticTroubleCodes) d

The diagnostic extract shall support the modeling of the OBD mode 0x03 / 0x07
Description:
/ 0x0A, a.k.a. RequestEmissionRelatedDiagnosticTroubleCodes.
The OBD modes 0x03 / 0x07 / 0x0A are mandatory parts of the OBD
Rationale: functionality and therefore a representation of this mode is required in the
diagnostic extract.
The user wants to model the OBD services 0x03 / 0x07 / 0x0A in the diagnostic
Use Case:
extract.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()

36 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00072] Support for OBD Mode 0x04 (ClearResetEmissionRelatedDi-

agnosticInformation) d

The diagnostic extract shall support the modeling of the OBD mode 0x04, a.k.a.
Description:
ClearResetEmissionRelatedDiagnosticInformation.
The OBD mode 0x04 is a mandatory part of the OBD functionality and
Rationale: therefore a representation of this mode is required in the diagnostic extract.
Use Case: The user wants to model the OBD service 0x04 in the diagnostic extract.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()
[RS_DEXT_00073] Support for OBD Mode 0x06 (RequestOnBoardMonitor-
ingTestResults) d

The diagnostic extract shall support the modeling of the OBD mode 0x06, a.k.a.
Description:
RequestOnBoardMonitoringTestResults.
The OBD mode 0x06 is a mandatory part of the OBD functionality and
Rationale: therefore a representation of this mode is required in the diagnostic extract.
Use Case: The user wants to model the OBD service 0x06 in the diagnostic extract.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()
[RS_DEXT_00074] Support for OBD Mode 0x08 (RequestControlOfOnBoardDe-
vice) d

The diagnostic extract shall support the modeling of the OBD mode 0x08, a.k.a.
Description:
RequestControlOfOnBoardDevice.
The OBD mode 0x08 is a mandatory part of the OBD functionality and
Rationale: therefore a representation of this mode is required in the diagnostic extract.
Use Case: The user wants to model the OBD service 0x08 in the diagnostic extract.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()

37 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00075] Support for OBD Mode 0x09 (RequestVehicleInformation) d

The diagnostic extract shall support the modeling of the OBD mode 0x09, a.k.a.
Description:
RequestVehicleInformation.
The OBD mode 0x09 is a mandatory part of the OBD functionality and
Rationale: therefore a representation of this mode is required in the diagnostic extract.
Use Case: The user wants to model the OBD service 0x09 in the diagnostic extract.
Dependencies: [RS_DEXT_00076]
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()
[RS_DEXT_00076] Definition of Diagnostic Test Identifier d

The diagnostic extract shall support the definition of a Diagnostic Test Identifier
Description:
(TID)
Rationale: The definition of a TID is required for the definition of the OBD model 0x09.
The user wants to define a TID that later shall be used in the definition of the
Use Case:
OBD service 0x09.
Dependencies: –
Supporting More information about this diagnostic service can be found in the respective
Material: ISO specification [7].

c()
[RS_DEXT_00077] Description of the utilization of UDS for supporting WWH-OBD
d

The diagnostic extract shall specify how the UDS diagnostic services shall be
Description:
utilized in order to implement WWH-OBD.
The implementation of WWH-OBD basically means to use UDS services to
emulate the behavior of OBD services. In order to harmonize the usage of UDS
Rationale: services for this purpose the diagnostic extract shall provide a specification that
eliminates ambiguous configuration variants as good as possible.
The user wants to utilize WWH-OBD on an ECU that in general supports the
UDS diagnostic services. The user wants to take advantage of specifications
Use Case:
that clarify how UDS services shall be configured in the diagnostic extract for
this purpose.
Dependencies: –
Supporting –
Material:

c()

38 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

2.9 Requirements against the Mapping of Diagnostic Resources

This chapter contains a collection of requirements against the mapping of diagnostic
resources onto other model elements.
[RS_DEXT_00052] Mapping of diagnostic services to the PortPrototypes of Ap-
plicationSwComponentTypes d

The Diagnostic Extract shall support the specification of how diagnostic

Description:
services are mapped to the PortPrototypes of ApplicationSwComponentTypes
The mapping of diagnostic services to the the PortPrototypes of
ApplicationSwComponentTypes connects the definition of diagnostic services
Rationale: with the actual application software that these services are about. Therefore,
this mapping is an important step in the workflow and also provides essential
information for the integration of the software on a given ECU.
The user wants to map diagnostic services to application software in order to
Use Case: express the conceptual connection between these two aspects of the ECU
configuration.
Dependencies: –
Supporting –
Material:

c()
[RS_DEXT_00025] Combined Events d

The Diagnostic Extract shall support the configuration of events mapping to a

Description:
single DTC.
There are cases where the results of several diagnostic monitors contribute to a
single diagnostic trouble code. For this purpose the diagnostic extract needs to
Rationale: be able to allow for an n:1 relationship between the model elements for
diagnostic events and diagnostic trouble codes.
The user wants to wire the results of several diagnostic monitors to a single
Use Case: diagnostic trouble code.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Diagnostic
Material: Event Manager [4].

c()
[RS_DEXT_00063] Relation between functions on Fim level and software-
components d

The diagnostic extract shall provide means to define the mapping of a function
Description:
to a software-component.
The concept of a function with in the Fim is quite abstract and needs further
Rationale: clarification as to which part of the application software on an AUTOSAR ECU
actually corresponds to it.
5

39 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

4
The user wants to specify which function in terms of the Fim is represented by
Use Case:
which part of the application software.
Dependencies: –
Supporting More information can be found in the specification of the AUTOSAR Function
Material: Inhibition Manager [6].

c()
[RS_DEXT_00066] Mapping between a J1939 controller application and a
software-component d

The diagnostic extract shall support the specification of the mapping between
Description: the concept of a J1939 controller application and a part of the AUTOSAR
application software represented by a single software-component.
The mapping between controller applications and software-component is an
important part of “bridging the gap” between the technical domains of
Rationale:
AUTOSAR and J1939. The different approaches to the definition of a functional
unit shall be mapped onto each other.
The user wants to specify the mapping between a controller application and a
Use Case:
part of the AUTOSAR application software.
Dependencies: –
Supporting –
Material:

c()

2.10 Miscellaneous Requirements

This chapter contains a collection of miscellaneous requirements.
[RS_DEXT_00081]{DRAFT} Support for updating the Reporting Mode of Security
Events d

In some cases, it is necessary to update the reporting mode of certain security

Description:
events via diagnostic services.
The reporting mode of security events can be a very important part of a
Rationale:
forensical analysis of an intrusion.
Use Case: The user wants to update the reporting mode of a given security event.
Dependencies: –
Supporting
Material:

c()

40 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

A Change history of AUTOSAR traceable items

A.1 Traceable item history of this document according to

AUTOSAR Release R4.2.1

A.1.1 Added Requirements in R4.2.1

Id Heading
[RS_DEXT_00001] Diagnostic Data Exchange
[RS_DEXT_00002] Distributed software development process
[RS_DEXT_00003] SessionControl
[RS_DEXT_00004] ECUReset
[RS_DEXT_00005] ClearDiagnosticInformation
[RS_DEXT_00006] ReadDTCInformation
[RS_DEXT_00007] ReadDataByIdentifier
[RS_DEXT_00008] ReadMemoryByAddress
[RS_DEXT_00009] SecurityAccess
[RS_DEXT_00010] CommunicationControl
[RS_DEXT_00011] ReadDataByPeriodicIdentifier
[RS_DEXT_00012] DynamicallyDefineDataIdentifier
[RS_DEXT_00013] WriteDataByIdentifier
[RS_DEXT_00014] IOControl
[RS_DEXT_00015] RoutineControl
[RS_DEXT_00016] RequestDownload
[RS_DEXT_00017] RequestUpload
[RS_DEXT_00018] TransferData
[RS_DEXT_00019] RequestTransferExit
[RS_DEXT_00020] WriteMemoryByAddress
[RS_DEXT_00021] ControlDTCSetting
[RS_DEXT_00022] ResponseOnEvent
[RS_DEXT_00023] Configuration of events
[RS_DEXT_00024] Configuration of DTCs
[RS_DEXT_00025] Combined Events
[RS_DEXT_00026] Enable Conditions
[RS_DEXT_00027] Storage Conditions
[RS_DEXT_00028] Enable Condition Groups
[RS_DEXT_00029] Storage Condition Groups
[RS_DEXT_00030] Assignment of Enable Condition Groups
[RS_DEXT_00031] Assignment of Storage Condition Group
[RS_DEXT_00032] Configuration of Extended Data Records
[RS_DEXT_00033] Configuration of Snapshot Records
[RS_DEXT_00034] Description of Data Identifiers
[RS_DEXT_00035] Description of Dynamic Data Identifiers
[RS_DEXT_00036] Description of Routine Identifiers
[RS_DEXT_00037] Description of I/O Identifiers
[RS_DEXT_00038] Description of array data types
[RS_DEXT_00039] Diagnostic Service Table
[RS_DEXT_00040] Diagnostic Sessions
[RS_DEXT_00041] Access Permissions
[RS_DEXT_00042] Security Levels
[RS_DEXT_00043] Description of data elements

41 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00044] Derivation of related ECU-C parameter

[RS_DEXT_00045] Textual descriptions
[RS_DEXT_00046] Variants
[RS_DEXT_00047] Custom Diagnostic Service
[RS_DEXT_00048] Diagnostic Properties that are specific for one ECU
[RS_DEXT_00049] Properties of individual diagnostic services
[RS_DEXT_00050] Properties of all diagnostic services of a given kind
[RS_DEXT_00051] Subfunctions of Diagnostic Services
[RS_DEXT_00052] Mapping of diagnostic services to the PortPrototypes of ApplicationSwCom-
ponentTypes
[RS_DEXT_00053] Debouncing of diagnostic events
[RS_DEXT_00054] Operation cycles
[RS_DEXT_00055] Aging
[RS_DEXT_00056] Indicator
[RS_DEXT_00057] RequestFileTransfer

Table A.1: Added Traceables in R4.2.1

A.1.2 Changed Requirements in 4.2.1

none

A.1.3 Deleted Requirements in 4.2.1

none

A.2 Traceable item history of this document according to

AUTOSAR Release R4.2.2

A.2.1 Added Requirements in 4.2.2

none

A.2.2 Changed Requirements in 4.2.2

Id Heading
[RS_DEXT_00003] SessionControl
[RS_DEXT_00004] ECUReset
[RS_DEXT_00005] ClearDiagnosticInformation
[RS_DEXT_00006] ReadDTCInformation
[RS_DEXT_00007] ReadDataByIdentifier
[RS_DEXT_00008] ReadMemoryByAddress
[RS_DEXT_00009] SecurityAccess
[RS_DEXT_00010] CommunicationControl
[RS_DEXT_00011] ReadDataByPeriodicIdentifier

42 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00012] DynamicallyDefineDataIdentifier
[RS_DEXT_00013] WriteDataByIdentifier
[RS_DEXT_00014] IOControl
[RS_DEXT_00015] RoutineControl
[RS_DEXT_00016] RequestDownload
[RS_DEXT_00017] RequestUpload
[RS_DEXT_00018] TransferData
[RS_DEXT_00019] RequestTransferExit
[RS_DEXT_00020] WriteMemoryByAddress
[RS_DEXT_00021] ControlDTCSetting
[RS_DEXT_00022] ResponseOnEvent

Table A.2: Changed Traceables in 4.2.2

A.2.3 Deleted Requirements in 4.2.2

none

A.2.4 Added Constraints in 4.2.2

none

A.2.5 Changed Constraints in 4.2.2

none

A.2.6 Deleted Constraints in 4.2.2

none

A.3 Traceable item history of this document according to

AUTOSAR Release R4.3.0

A.3.1 Added Requirements in 4.3.0

Id Heading
[RS_DEXT_00058] Indicate that an ECU supports ODB
[RS_DEXT_00059] Support for different protocols
[RS_DEXT_00060] Function
[RS_DEXT_00061] Relationship between functions and diagnostic events
[RS_DEXT_00062] Pre-configuration of the Fim when the Dem configuration is not yet available
[RS_DEXT_00063] Relation between functions on Fim level and software-components
[RS_DEXT_00064] Definition of an SPN

43 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00065] Definition of freeze frames on J1939

[RS_DEXT_00066] Mapping between a J1939 controller application and a software-component
[RS_DEXT_00067] Definition of J1939 DTC
[RS_DEXT_00068] Definition of a Diagnostic Parameter Identifier
[RS_DEXT_00069] Support for OBD Mode 0x01 (RequestCurrentPowertrainDiagnosticData)
[RS_DEXT_00070] Support for OBD Mode 0x02 (RequestPowertrainFreezeFrameData)
[RS_DEXT_00071] Support for OBD ModeModes 0x03 / 0x07 / 0x0A (RequestEmissionRelated-
DiagnosticTroubleCodes)
[RS_DEXT_00072] Support for OBD Mode 0x04 (ClearResetEmissionRelatedDiagnosticInforma-
tion)
[RS_DEXT_00073] Support for OBD Mode 0x06 (RequestOnBoardMonitoringTestResults)
[RS_DEXT_00074] Support for OBD Mode 0x08 (RequestControlOfOnBoardDevice)
[RS_DEXT_00075] Support for OBD Mode 0x09 (RequestVehicleInformation)
[RS_DEXT_00076] Definition of Diagnostic Test Identifier
[RS_DEXT_00077] Description of the utilization of UDS for supporting WWH-OBD
[RS_DEXT_00078] Support for In Use Monitor Performance Ratio
[RS_DEXT_00079] Support for environment conditions

Table A.3: Added Traceables in 4.3.0

A.3.2 Changed Requirements in 4.3.0

Id Heading
[RS_DEXT_00001] Diagnostic data exchange
[RS_DEXT_00023] Configuration of events
[RS_DEXT_00024] Configuration of DTCs
[RS_DEXT_00025] Combined Events
[RS_DEXT_00026] Enable Conditions
[RS_DEXT_00027] Storage Conditions
[RS_DEXT_00028] Enable Condition Groups
[RS_DEXT_00029] Storage Condition Groups
[RS_DEXT_00030] Assignment of Enable Condition Groups
[RS_DEXT_00031] Assignment of Storage Condition Group
[RS_DEXT_00032] Configuration of Extended Data Records
[RS_DEXT_00033] Configuration of Snapshot Records
[RS_DEXT_00034] Description of Data Identifiers
[RS_DEXT_00035] Description of Dynamic Data Identifiers
[RS_DEXT_00036] Description of Routine Identifiers
[RS_DEXT_00037] Description of I/O Identifiers
[RS_DEXT_00038] Description of array data types
[RS_DEXT_00039] Diagnostic Service Table
[RS_DEXT_00040] Diagnostic Sessions
[RS_DEXT_00041] Access Permissions
[RS_DEXT_00042] Security Levels
[RS_DEXT_00043] Description of data elements
[RS_DEXT_00044] Derivation of related ECU-C parameter
[RS_DEXT_00045] Textual descriptions
[RS_DEXT_00046] Variants
[RS_DEXT_00047] Custom Diagnostic Service
[RS_DEXT_00048] Diagnostic Properties that are specific for one ECU
[RS_DEXT_00049] Properties of individual diagnostic services
[RS_DEXT_00050] Properties of all diagnostic services of a given kind

44 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

[RS_DEXT_00051] Subfunctions of Diagnostic Services

[RS_DEXT_00052] Mapping of diagnostic services to the PortPrototypes of ApplicationSwCom-
ponentTypes
[RS_DEXT_00053] Debouncing of diagnostic events
[RS_DEXT_00054] Operation cycles
[RS_DEXT_00055] Aging
[RS_DEXT_00056] Indicator
[RS_DEXT_00057] RequestFileTransfer

Table A.4: Changed Traceables in 4.3.0

A.3.3 Deleted Requirements in 4.3.0

Id Heading
[RS_DEXT_00002] Distributed software development process

Table A.5: Deleted Traceables in 4.3.0

A.3.4 Added Constraints in 4.3.0

none

A.3.5 Changed Constraints in 4.3.0

none

A.3.6 Deleted Constraints in 4.3.0

none

A.4 Traceable item history of this document according to

AUTOSAR Release R4.3.1

A.4.1 Added Requirements in R4.3.1

none

A.4.2 Changed Requirements in R4.3.1

none

45 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

A.4.3 Deleted Requirements in R4.3.1

none

A.5 Traceable item history of this document according to

AUTOSAR Release R4.4.0

A.5.1 Added Requirements in R4.4.0

none

A.5.2 Changed Requirements in R4.4.0

none

A.5.3 Deleted Requirements in R4.4.0

none

A.6 Traceable item history of this document according to

AUTOSAR Release R19-11

A.6.1 Added Requirements in R19-11

none

A.6.2 Changed Requirements in R19-11

none

A.6.3 Deleted Requirements in R19-11

none

46 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

A.7 Traceable item history of this document according to

AUTOSAR Release R20-11

A.7.1 Added Requirements in R20-11

Number Heading
[RS_DEXT_00080] Support for persisting Security Events
[RS_DEXT_00081] Support for updating the Reporting Mode of Security Events
Table A.6: Added Requirements in R20-11

A.7.2 Changed Requirements in R20-11

none

A.7.3 Deleted Requirements in R20-11

none

A.8 Traceable item history of this document according to

AUTOSAR Release R21-11

A.8.1 Added Requirements in R21-11

none

A.8.2 Changed Requirements in R21-11

none

A.8.3 Deleted Requirements in R21-11

none

47 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate

 Requirements on Diagnostic Extract Template
AUTOSAR CP R23-11

A.9 Traceable item history of this document according to

AUTOSAR Release R22-11

A.9.1 Added Requirements in R22-11

none

A.9.2 Changed Requirements in R22-11

Number Heading
[RS_DEXT_00038] Description of nested elements of DIDs and RIDs
Table A.7: Changed Requirements in R22-11

A.9.3 Deleted Requirements in R22-11

Number Heading
[RS_DEXT_00046] Variants
Table A.8: Deleted Requirements in R22-11

A.10 Traceable item history of this document according to

AUTOSAR Release R23-11

A.10.1 Added Requirements in R23-11

none

A.10.2 Changed Requirements in R23-11

none

A.10.3 Deleted Requirements in R23-11

none

48 of 48 Document ID 681: AUTOSAR_CP_RS_DiagnosticExtractTemplate