ISO 14229-4:2012

INTERNATIONAL ISO
STANDARD 14229-4
First edition
2012-12-01
Road vehicles — Unified diagnostic
services (UDS) —
Part 4:
Unified diagnostic services on FlexRay
implementation (UDSonFR)
Véhicules routiers — Services de diagnostic unifiés (SDU) —
Partie 4: SDU sur l’implémentation FlexRay (SDUsurFR)
Reference number
ISO 14229-4:2012(E)
©
ISO 2012

---------------------- Page: 1 ----------------------
ISO 14229-4:2012(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any
means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the
address below or ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2012 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 14229-4:2012(E)

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 1
4 Conventions . 2
5 Document overview. 2
6 Unified diagnostic services implementation on FlexRay . 4
6.1 General . 4
6.2 UDS on FlexRay services overview . 4
6.3 CommunicationControl (0x28) service . 5
6.4 ResponseOnEvent (0x86) service . 5
6.5 LinkControl (0x87) service . 7
6.6 ReadDataByPeriodicIdentifier (0x2A) service . 8
7 Application layer requirements .14
7.1 Application layer services .14
7.2 Application layer protocol .14
7.3 Application layer timing.14
8 Presentation layer requirements .14
9 Session layer requirements .14
10 Transport/Network layer interface adaptation .14
10.1 General information .14
10.2 DoFR Transport/Network layer interface adaptation .14
11 Data Link layer diagnostic implementation requirements .15
Bibliography
.16
© ISO 2012 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 14229-4:2012(E)

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International
Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies
casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 14229-4 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
ISO 14229 consists of the following parts, under the general title Road vehicles — Unified diagnostic
services (UDS):
— Part 1: Specification and requirements
— Part 2: Session layer services
— Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)
— Part 4: Unified diagnostic services on FlexRay implementation (UDSonFR)
— Part 5: Unified diagnostic services on Internet Protocol implementation (UDSonIP)
— Part 6: Unified diagnostic services on K-Line implementation (UDSonK-Line)
The following parts are under preparation / are planned:
— Part 7: Unified diagnostic services on Local Interconnet Network implementation (UDSonLIN)
iv © ISO 2012 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 14229-4:2012(E)

Introduction
This part of ISO 14229 has been established in order to enable the implementation of unified diagnostic
services, as specified in ISO 14229-4, on FlexRay (UDSonFR).
To achieve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model specified in
ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers. When
mapped on this model, the services specified by ISO 14229 are divided into:
— Application layer (layer 7):
— Vehicle manufacturer enhanced diagnostics: ISO 14229-1, ISO 14229-4,
— Legislated OBD: ISO 15031-5,
— Legislated WWH-OBD: ISO 14229-1 / ISO 27145-3;
— Presentation layer (layer 6):
— Vehicle manufacturer enhanced diagnostics: vehicle manufacturer specific,
— Legislated OBD: SAE J1930-DA, SAE J1979-DA, SAE J2012-DA,
— Legislated WWH-OBD: ISO 27145-2 with reference to SAE J1930-DA, SAE J1939, Companion
Spreadsheet (SPNs), SAE J1939-73:2010, Appendix A (FMIs), SAE J1979-DA and SAE J2012-DA;
— Session layer services (layer 5):
— Vehicle manufacturer enhanced diagnostics: ISO 14229-2,
— Legislated OBD: ISO 14229-2,
— Legislated WWH-OBD: ISO 14229-2;
— Transport layer services (layer 4):
— Vehicle manufacturer enhanced diagnostics: ISO 10681-2,
— Legislated OBD: ISO 10681-2, ISO 15765-4
— Legislated WWH-OBD: ISO 27145-4;
— Network layer services (layer 3):
— Vehicle manufacturer enhanced diagnostics: ISO 10681-2,
— Legislated OBD: ISO 15765-2, ISO 15765-4
— Legislated WWH-OBD: ISO 27145-4;
— Data link layer (layer 2):
— Vehicle manufacturer enhanced diagnostics: ISO 17458-2,
— Legislated OBD: ISO 11898-1, ISO 11898-2, ISO 15765-4,
— Legislated WWH-OBD: ISO 27145-4;
— Physical layer (layer 3):
— Vehicle manufacturer enhanced diagnostics: ISO 17458-4,
— Legislated OBD: ISO 11898-1, ISO 11898-2, ISO 15765-4,
© ISO 2012 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 14229-4:2012(E)

— Legislated WWH-OBD: ISO 27145-4;
in accordance with Table 1.
Table 1 — DoFR enhanced diagnostics, legislated OBD and WWH-OBD specification reference
applicable to the OSI layers
Vehicle man- Legislated
ufacturer OBD Legislated WWH-OBD
Applicability OSI 7 layers
enhanced (On-Board (On-Board Diagnostics)
diagnostics Diagnostics)
Application ISO 14229-1/
ISO 15031-5 ISO 14229-1/ISO 27145-3
(layer 7) ISO 14229-4
ISO 27145-2
Presenta- Vehicle SAE J1930-DA, SAE J1930-DA, SAE J1939 Companion Spreadsheet
tion (layer manufacturer SAE J1979-DA, (SPNs),
6) specific SAE J2012-DA SAE J1939-73:2010, Appendix A (FMIs),
SAE J1979-DA, SAE J2012-DA
Seven layer
accord-
Session
ISO 14229-2
ing to ISO/
(layer 5)
IEC 7498-1
Transport
and ISO/
(layer 4)
ISO 15765-2, ISO 15765-2,
IEC 10731
ISO 10681-2 ISO 13400-2
ISO 15765-4 ISO 15765-4
Network
(layer 3)
ISO 27145-4
Data link
ISO 17458-2
ISO 11898-1, ISO 11898-1,
(layer 2)
ISO 13400-3,
ISO 11898-2, ISO 11898-2,
IEEE 802.3
Physical
ISO 15765-4 ISO 15765-4
ISO 17458-4
(layer 1)
vi © ISO 2012 – All rights reserved

---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 14229-4:2012(E)
Road vehicles — Unified diagnostic services (UDS) —
Part 4:
Unified diagnostic services on FlexRay implementation
(UDSonFR)
1 Scope
This part of ISO 14229 specifies the implementation of a common set of unified diagnostic services
(UDS) on FlexRay networks (FR) in road vehicles (UDSonFR).
UDSonFR references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the
diagnostic services to be used for diagnostic communication over FlexRay.
NOTE UDSonFR does not specify any requirements of the in-vehicle FlexRay architecture.
This part of ISO 14229 does not include any redundant information of the documents as listed in the
introduction. It focuses on
— additional requirements specific to the implementation of UDS on the FlexRay network, and
— specific restrictions in the implementation of UDS on the FlexRay network.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 10681-2, Road vehicles — Communication on FlexRay — Part 2: Communication layer services
ISO 17458-2, Road vehicles — FlexRay Communication Systems — Protocol specification
ISO 17458-4, FlexRay Communication Systems — Electrical physical layer specification
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 14229-1, ISO 14229-2, and
ISO 10681-2 apply.
3.2 Abbreviated terms
CF consecutive frame
DoFR diagnostic communication over FlexRay
© ISO 2012 – All rights reserved 1

---------------------- Page: 7 ----------------------
ISO 14229-4:2012(E)

FC flow control
FR FlexRay
ISO International Standardization Organization
LF last frame
OSI Open System Interconnection
Rx reception
SA source address
SID service identifier
SM subnet mask
SOM start of message
STF start frame
STRT serviceToRespondTo
TA target address
UDS unified diagnostic services
Tx transmission
UDSonFR Unified Diagnostic Services (UDS) on FlexRay
4 Conventions
This part of ISO 14229 is based on the conventions discussed in the OSI Service Conventions
(ISO/IEC 10731:1994) as they apply for diagnostic services.
5 Document overview
Figure 1 illustrates the document references from ISO 14229-1, ISO 14229-2 and ISO 10681-1 and
ISO 10681-2. ISO 14229-4 uses only a subset of the diagnostic services defined in ISO 14229-1 (see Table 2).
2 © ISO 2012 – All rights reserved

---------------------- Page: 8 ----------------------
ISO 14229-4:2012(E)

Uniied Diagnostic Services (UDS)
subset
ISO 14229-4
ISO 14229-1 UDS
UDS
OSI Layer 7 speciication and
Part 4:
Application requirements
UDSonFR
OSI Layer 6 vehicle manufacturer speciic
Presentation
OSI Layer 5 ISO 14229-2 UDS
Session session layer services
Standardized Service Primitive Interface
FlexRay
ISO 14229-4 UDS –
UDSonFlexRay
implementation
OSI Layer 4
ISO 10681-2 CoFlexRay
Transport
Part2:
Transport
and
network
layer services
OSI Layer 3
Network
ISO 17458-2
FlexRay communications
OSI Layer 2
system – Protocol
Data Link
speciication
ISO 17458-4
FlexRay communications
system
OSI Layer 1

– Electrical physical layer
Physical
speciication
Figure 1 — ISO 14229-4, UDSonFR document reference according to OSI model
© ISO 2012 – All rights reserved 3

---------------------- Page: 9 ----------------------
ISO 14229-4:2012(E)

6 Unified diagnostic services implementation on FlexRay
6.1 General
This clause defines how the diagnostic services as defined in ISO 14229-1 apply to FlexRay. For each
service, the applicable sub-function and data parameters are defined.
NOTE The sub-function parameter definitions take into account that the most significant bit is used for the
suppressPosRspMsgIndicationBit parameter as defined in ISO 14229-1.
6.2 UDS on FlexRay services overview
The purpose of Table 2 is to reference all ISO 14229-1 and ISO 14229-2 services as they are applicable for
an implementation in ISO 14229-4, UDSonFR. Table 2 contains the sum of all applicable services. Certain
applications using this part of ISO 14229 to implement UDSonFR may restrict the number of useable
services and may categorize them in certain application areas/diagnostic sessions (default session,
programming session, etc.).
Services in Table 2 that are marked “No FlexRay specific requirements” shall be implemented as defined
in ISO 14229-1 and ISO 14229-2 with no additional restrictions. Services that are marked “FlexRay
specific requirements” shall be implemented as defined by the subclause listed in the Table 2 entry.

Table 2 — Overview of applicable ISO 14229-1 unified diagnostic services and data ranges
Diagnostic service name
Comment Reference in this document
(ISO 14229-1)
Diagnostic and Communication Management Functional Unit
DiagnosticSessionControl No FlexRay specific requirements —
ECUReset No FlexRay specific requirements —
SecurityAccess No FlexRay specific requirements —
CommunicationControl FlexRay specific requirements see 6.3
TesterPresent No FlexRay specific requirements —
SecuredDataTransmission No FlexRay specific requirements —
ControlDTC-Setting No FlexRay specific requirements —
ResponseOnEvent FlexRay specific requirements see 6.4
LinkControl FlexRay specific requirements see 6.5
Data Transmission Functional Unit
ReadDataByIdentifier No FlexRay specific requirements —
ReadMemoryByAddress No FlexRay specific requirements —
ReadScalingDataByIdentifier No FlexRay specific requirements —
ReadDataByPeriodicIdentifier FlexRay specific requirements see 6.6
DynamicallyDefineDataIdentifier No FlexRay specific requirements —
WriteDataByIdentifier No FlexRay specific requirements —
WriteMemoryBy-Address No FlexRay specific requirements —
ReadDTCInformation No FlexRay specific requirements —
ClearDiagnosticInformation No FlexRay specific requirements —
Input/Output Control Functional Unit
InputOutputControlByIdentifier No FlexRay specific requirements —
4 © ISO 2012 – All rights reserved

---------------------- Page: 10 ----------------------
ISO 14229-4:2012(E)

Table 2 (continued)
Diagnostic service name
Comment Reference in this document
(ISO 14229-1)
Remote Activation Of Routine Functional Unit
RoutineControl No FlexRay specific requirements —
Upload/Download Functional Unit
Request-Download No FlexRay specific requirements —
RequestUpload No FlexRay specific requirements —
TransferData No FlexRay specific requirements —
RequestTransferExit No FlexRay specific requirements —
RequestFileTransfer No FlexRay specific requirements —
6.3 CommunicationControl (0x28) service
The following requirements as stated in Table 3 shall apply for this service when implemented on FlexRay.
Table 3 — Service 0x28 sub-function implementation definition on FlexRay
Hex
Description Cvt Mnemonic
(bit 6-0)
00 enableRxAndTx M ERXTX
—  FlexRay communication in the static segment is switched on;
—  FlexRay communication in the dynamic segment (if applicable) is switched
on;
01 enableRxAndDisableTx M ERXDTX
Enables the Rx – communication in the static and dynamic segment;
a
Disables the Tx - communication in the static and the dynamic segment :
—  In the static segment only null frames are sent in the individual slots.
—  In the dynamic segment (if applicable) communication is switched off
(results in minislots only).
02 disableRxAndEnableTx M DRXETX
—  Disables the Rx – communication in the static and dynamic segment;
—  Enables the Tx - communication in the static and the dynamic segment;
03 disableRxAndTx M DRXTX
Disables the communication (Rx and Tx) in the static and the dynamic seg-
ment. Impacts on Tx and Rx for the static and dynamic segment are the same as
described for sub-function 0x01 and 0x02.
a
It needs to be ensured that basic network functionality (e.g. synchronization) is not negatively influenced by disabling
Tx communication.
6.4 ResponseOnEvent (0x86) service
In addition to the generic implementation requirements stated in ISO 14229-1 the following additional
FlexRay specific implementation requirements shall apply:
While the ResponseOnEvent service is active, the server shall be able to process concurrent
diagnostic request and response messages accordingly. This should be accomplished with a different
serviceToRespondToFlexRay source address. If the same diagnostic FlexRay source and target
© ISO 2012 – All rights reserved 5

---------------------- Page: 11 ----------------------
ISO 14229-4:2012(E)

addresses are used for diagnostic communication and the serviceToRespondTo-responses, the following
restrictions shall apply.
a) The server shall ignore an incoming diagnostic request after an event has occurred and the
serviceToRespondTo-response is in progress, until the serviceToRespondTo-response is completed.
b) When the client receives any response after sending a diagnostic request, the response shall be
classified according to the possible serviceToRespondTo-responses and the expected diagnostic
responses to the previously sent request.
1) If the response is a serviceToRespondTo-response (one of the possible responses set up with
ResponseOnEvent-service), the client shall repeat the request after the serviceToRespondTo-
response has been received completely.
2) If the response is ambiguous (i.e. the response could originate from the serviceToRespondTo
initiated by an event or from the response to a diagnostic request), the client shall present
the response both as a serviceToRespondTo-response and as the response to the diagnostic
request. The client shall not repeat the request with the exception of NegativeResponseCode
busyRepeatRequest (0x21). (See the negative response code definitions in ISO 14229-1.)
client server
STF-Diag-Request STRT-ResponseSTF Event
a
server ignores request
STRT-FC
STRT-CF
STRT-LF
the STRT-response is completed
and the tester repeats the
diagnostic request, if the
response is a valid STRT-
STF-Diag-Request
response.
server responds to request
Response
a
In the example given it is assumed, that the STRT-Response STF caused by the event is sent in the same FR
cycle as the diagnostic request from the client.
Figure 2 — Concurrent request when the event occurs
c) When the specified event is detected, the server shall respond immediately with the appropriate
serviceToRespondTo-response message. The immediate serviceToRespondTo-response message
shall not disrupt any other diagnostic request or response transmission already in progress (i.e. the
serviceToRespondTo-response shall be delayed until the current message transmission has been
completed — see Figure 3).
6 © ISO 2012 – All rights reserved

---------------------- Page: 12 ----------------------
ISO 14229-4:2012(E)

NOTE In case the event occurs while the diagnostic request has not been indicated as being in progress to
the upper layers of the server, it would transmit the serviceToRespondTo-response and ignores the diagnostic
request (see Figure 2).
client server
STF Diag-Request
Diag-Resp. STF
FC
Event
STRT-Response
is delayed
Diag.-Response is
completed
STRT-Resp. STF
and the server sends the
STRT-response.
FC
STRT-CF
STRT-LF
Figure 3 — Event occurrence during a message in progress
6.5 LinkControl (0x87) service
LinkControl is utilized in FlexRay to adapt data link relevant parameters such, that diagnostic
communication bandwidth is maximized (e.g. programming event). This results in an adaptation of the
FlexRay cycle design (e.g. enhance dynamic segment, optimize frame length of diagnostic messages,
etc.). However, the detailed implementation is vehicle manufacturer specific and shall be described in
an individual implementation specification.
The following requirements shall apply for this service when implemented on FlexRay.
The communication strategy shall follow the requirements as stated in ISO 14229-1:
— Step #1: Shall follow the definition stated in ISO 14229-1.
— Step #2: The client requests the mode transition to adapt the FlexRay cycle design as specified
in the individual implementation specification. This step shall only be requested if step #1
has been performed successfully. In case of functional communication it is recommended
that there shall not be any response from a server when the mode transition is performed
(suppressPosRspMsgIndicationBit = TRUE), because one server might already have been transitioned
to the new mode while others are still in progress.
© ISO 2012 – All rights reserved 7

---------------------- Page: 13 ----------------------
ISO 14229-4:2012(E)

The individual FlexRay implementation shall follow the requirements as stated in Table 4.
Table 4 — Request message sub-function Parameter Definition
Hex
Description Cvt Mnemonic
(bit 6-0)
01 verifyModeTransitionWithFixedParameter M ERXTX
This parameter is used to verify if a transition with a pre-defined FlexRay
schedule design, which is specified by the linkControlModeIdentifier data
parameter can be performed.
02 verifyModeTransitionWithSpecificParameter M ERXDTX
Not applicable for FlexRay
03 transitionMode M TM
This sub-function parameter requests the server(s) to transition the FlexRay
to the schedule design which was requested in the preceding verification mes-
sage.
6.6 ReadDataByPeriodicIdentifier (0x2A) service
6.6.1 Periodic transmission response message
The ReadDataByPeriodicIdentifier service allows the client to request the periodic transmission of data record
values from the server identified by one or more periodicDataIdentifiers. For service 0x2A implementation
on FlexRay, the periodic transmission response message is supported according to ISO 14229-1.
The usage of the periodic transmission response message should consider a single data format being
supported for the whole vehicle which may consist of other data links than FlexRay. E.g. if CAN is part of
the electrical vehicle architecture in addition to FlexRay, the total DID data length shall not exceed the
length limitations of the CAN protocol to ensure a single data format.
Table 5 describes the requirements for periodic transmission response message.
Table 5 — Periodic transmission — Requirements for response message mapping
Client request Server response
Message type Further server restrictions
requirements requirements
The request for periodic transmission is
processed as a regular diagnostic request
and the response is sent via the communica-
tion layer (as a FlexRay message with service
identifier 0x6A)
On receiving the C_Data.confirm that indi-
Only single FlexRay frame
cates the completion of the transmission of
Periodic trans-
responses for periodic
the positive response, the application starts
mission response
transmission
an independent scheduler, which handles the
message uses a
Multi-frame responses
periodic transmission.
different FlexRay No restrictions
(non-periodic-transmission)
source address for
The scheduler in the server processes the
are possible in parallel
periodic message
periodic transmission as a single FlexRay
while periodic responses
transmissions
frame response message in a by-pass to the
are in progress
transport layer
There is neither a protocol control infor-
mation (PCI) nor a service identifier (SId)
included in the response message. Only the
periodic identifier and corresponding data
are included.
8 © ISO 2012 – All rights reserved

---------------------- Page: 14 ----------------------
ISO 14229-4:2012(E)

6.6.2 Periodic transmission response message handling
6.6.2.1 General
Due to the fact, that the periodic transmission response message neither supports protocol control
information nor the service identifier information (transport layer by-pass), the following service
primitives need to be taken into account. The service primitives as defined below make use of the
individual parameters as specified in ISO 10681-2:
6.6.2.2 C_UUData.request
The service primitive requests periodic transmission of < MessageData > with < Length > number
of bytes from the sender to the receiver peer entities identified by the address information in C_SA
and C_TA. Each time the C_UUData.request service is called, the communication layer shall signal the
completion (or failure) of the message transmission to the service user by means of the issuing of a
C_UUData.confirm service call.
C_UUData.request (
C_SA,
C_TA,
,

)
6.6.2.3 C_UUData.confirm
The C_UUData.confirm service is issued by the communication layer. The service primitive confirms the
completion of a C_UUData.request service identified by the address information in C_SA and C_TA. The
parameter < C_Result > provides the status of the service request (referring < C_Result > values defined
in ISO 10681-2.
C_UUData.confirm (
C_SA,
C_TA,

)
NOTE Not all result values as defined in ISO 10681-2 apply for the periodic transmission response message.
6.6.2.4 C_UUData.indication
The C_UUData.indication service is issued by the communication layer. The service primitive
delivers < MessageData > with < Length > bytes received from a peer protocol entity identified by the
address information in C_SA and C_TA to the upper layer (see definition in ISO 10681-2.
The parameters < MessageData > and < Length > are only valid when the service primitive is indicated. In
case of a reception error no indication will be generated. Therefore a < C_Result > parameter is not needed.
C_UUData.indication (
C_SA,
C_TA,
,

)
© ISO 2012 – All rights reserved 9

---------------------- Page: 15 ----------------------
ISO 14229-4:2012(E)

6.6.2.5 FlexRay frame format
6.6.2.5.1 General
Since the periodic transmission response message neither supports PCI information nor service
identification information the protocol data unit format (PDU) differs to what is defined in ISO 10681-2.
However the FlexRay periodic transmission PDU format also consists of three fields, as given
...