ISO INTERNATIONAL STANDARD. Road vehicles Unified diagnostic services (UDS) Part 2: Session layer services

Transcription

1 Dit document mag slechts op een stand-alone PC wden geinstalleerd. Gebruik op een netwerk is alleen. toestaan als een aanvullende licentieovereenkomst vo netwerkgebruik met NEN is afgesloten. This document may only used on a stand-alone PC. Use in a netwk is only permitted when a supplementary license agreement f us in a netwk with NEN has en concluded. INTERNATIONAL STANDARD First edition Road vehicles Unified diagnostic services (UDS) Part 2: Session layer services Véhicules routiers Services de diagnostic unifiés (SDU) Partie 2: Séquence des couches de services Reference numr :2013(E) 2013

2 :2013(E) COPYRIGHT PROTECTED DOCUMENT 2013 All rights reserved. Unless otherwise specified, no part of this publication may reproduced utilized in any fm by any means, electronic mechanical, including photocopying and microfilm, without permission in writing from either at the address low 's memr body in the country of the requester. copyright office Case postale 56 CH-1211 Gena 20 Tel Fax copyright@iso.g Web Published in Switzerland ii 2013 All rights reserved

3 :2013(E) Contents Page Scope Nmative references Terms, definitions and abbriated terms... 1 Terms and definitions... 1 Abbriated terms Conventions Document overv Session layer services... 4 General... 4 Specification of session layer service primitives... 6 Session data unit specification Timing parameter definition... 9 General application timing considerations... 9 Application timing parameter definitions defaultsession Example f P4Server without enhanced response timing Example f P4Server with enhanced response timing Session timing parameter definitions f the non-default session Client and server timer resource requirements Err handling Timing handling during communication Physical communication Functional communication Minimum time tween client request messages Annex A (nmative) T_PDU interface Annex B (infmative) Vehicle diagnostic OSI layer architecture examples B.1 Vehicle diagnostic OSI layer gateway example B.2 Vehicle diagnostic OSI layer CAN router example B.3 Vehicle diagnostic OSI layer CAN switch example Bibliography All rights reserved iii

4 :2013(E) Fewd (the International Organization f Standardization) is a wldwide federation of national standards bodies ( memr bodies). The wk of preparing International Standards is nmally carried out through technical committees. Each memr body interested in a subject f which a technical committee has en established has the right to represented on that committee. International ganizations, governmental and non-governmental, in liaison with, also take part in the wk. collabates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accdance with the rules given in the /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 memr bodies f voting. Publication as an International Standard requires approval by at least 75 % of the memr bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may the subject of patent rights. shall not h responsible f identifying any all such patent rights was prepared by Technical Committee /TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment 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 otocol implementation (UDSonIP) Part 6: Unified diagnostic services on K-Line implementation (UDSonK-Line) Part 7: Unified diagnostic services on Local Interconnect Netwk implementation (UDSonLIN) The titles of future parts will drafted as follows: iv The following part is under preparation: Part n: Unified diagnostic services on implementation (UDSon ) 2013 All rights reserved

5 :2013(E) Introduction has en established in der to define common requirements f diagnostic systems that are independent of the underlying serial data link. To achie this, is based on the Open Systems Interconnection (OSI) Basic Reference Model in accdance with and /IEC 10731, which structures communication systems into sen layers. When mapped on this model, the services used by a diagnostic tester (client) and an Electronic Control Unit (ECU, server) are broken into the following layers in accdance with Table 1: Application layer (layer 7), unified diagnostic services specified in , UDSonCAN, UDSonFR, UDSonIP, UDSonK-Line, UDSonLIN, further standards and WWH-OBD. esentation layer (layer 6), vehicle manufacturer specific, WWH-OBD. Session layer services (layer 5) specified in this part of Transpt layer services (layer 4), specified in DoCAN, Communication on FlexRay, DoIP, WWH-OBD. Netwk layer services (layer 3), specified in DoCAN, Communication on FlexRay, DoIP, WWH-OBD. Data link layer (layer 2), specified in , , , , IEEE 802.3, and further standards, WWH-OBD. Physical layer (layer 1), specified in , , , , IEEE 802.3, , further standards, WWH-OBD. Table 1 Example of diagnostic/programming specifications applicable to the OSI layers Applicability WWH-OBD Enhanced diagnostics services Sen layer accding to /IEC and /IEC OSI sen layer Application (layer 7) , UDSonCAN, UDSonFR, UDSonIP, UDSonK-Line, UDSonLIN, further standards esentation (layer 6) vehicle manufacturer specific Session (layer 5) Transpt (layer 4) Netwk (layer 3) Data link (layer 2) Physical (layer 1) , , IEEE Not applicable further standards further standards further standards further standards 2013 All rights reserved v

6 :2013(E) vi 2013 All rights reserved

7 INTERNATIONAL STANDARD :2013(E) Road vehicles Unified diagnostic services (UDS) Part 2: Session layer services 1 Scope This part of specifies data link independent requirements of session layer services. This part of specifies common session layer services to provide independence tween unified diagnostic services ( ) and all transpt protocols and netwk layer services (e.g DoCAN, Communication on FlexRay, DoIP, DoK-Line, etc.) This part of specifies a common service primitive interface tween OSI layer 4 (Transpt) and layer 5 (Session) via so-called service request/confirmation/indication primitives. This interface allows seamless implementation of Unified diagnostic services (UDS) with any communication protocol titled "DoXYZ / CoXYZ" like DoCAN Diagnostic communication over Controller Area Netwk, DoIP, Communication over FlexRay, DoK-Line (emissions-related OBD) and (WWH-OBD) suppt the standardized service primitive interface. Nmative references 2 The following referenced documents are indispensable f the application of this document. F dated references, only the edition cited applies. F undated references, the latest edition of the referenced document (including any amendments) applies , Road vehicles Unified diagnostic services (UDS) Part 1: Specification and requirements 3.1 Terms, definitions and abbriated terms Terms and definitions 3 F the purposes of this document, the following terms and definitions apply gateway netwking dice that transfers the PDU on different OSI layers EXAMPLE A netwk dice that enables communication tween control module netwks that use different communication protocols, different communication rates, etc. That includes, but is not limited to, gateway functionalities like bridge, switch, router application layer routing All rights reserved 1

8 :2013(E) router netwking dice that transfers the PDU on OSI layers 3 and switch netwking dice that transfers the PDU on OSI layer Abbriated terms CDD CMD DSC ECU OSI S_AE S_SA S_Data SI SOM S_Mtype S_PDU S_TA S_TAtype common data dictionary common message dictionary diagnostic session control electronic control unit open systems interconnection session layer address extension session layer source address session layer data transfer service name service identifier start of message session layer message type session layer protocol data unit session layer target address session layer target address type 4 Conventions This part of is guided by the conventions discussed in the OSI Service Conventions ( 10731:1994) as they apply to the diagnostic services. These conventions specify the interactions tween the service user and the service provider. Infmation is passed tween the service user and the service provider by service primitives, which may convey parameters All rights reserved

9 :2013(E) 5 Document overv Figure 1 illustrates implementations of onto various protocols. Figure 1 Implementation of UDS document reference accding to OSI model 2013 All rights reserved 3

10 :2013(E) Session layer services General The service interface defines a set of services that are needed to access the functions offered by the session layer, i.e. transmission/reception of data and setting of protocol parameters. All session layer services have the same general structure. The service primitives define how a service user (e.g. diagnostic application) cooperates with a service provider (e.g. session layer). To define the services, three types of service primitives are specified: a service request primitive S_Data.request, used by the higher application layer to pass control infmation data required to transmitted to the session layer (i.e. the service provider is ing requested by the service user to process control infmation to transmit data); a service indication primitive S_Data.indication, used by the session layer to pass status infmation and received data to the higher application layer (i.e. the service user is ing infmed by the service provider about an internal ent of the session layer the service request of a peer protocol layer entity service user); a service confirmation primitive S_Data.confirm used by the session layer to pass status infmation to the application layer (i.e. the service user is ing infmed by service provider about the result of a preceding service request of the service user); All session layer services have the same general fmat. Service primitives are written in the fm: service_name.type ( Where: parameter A, parameter B, parameter C [, parameter X,...] ) "service_name" is the name of the service (e.g. S_Data), "type" indicates the type of the service primitive (e.g. request, indication, confirm), "parameter A,..." is the S_PDU (Session layer otocol Data Unit) as a list of values passed by the service primitive (e.g. addressing infmation, Data, Length, Result), "parameter A, parameter B, parameter C" are mandaty parameters that shall included in all service calls, "[parameter X]" is an optional parameter that is included if specific conditions are fulfilled All rights reserved

11 :2013(E) Figure 2 shows the session layer service primitives f a single frame message. Figure 2 Session layer service primitives Single frame message Figure 3 shows the session layer service primitives f a multiple frame message, if the transpt/netwk layer suppts the T_DataSOM.ind interfaces. time Sender Application Layer Sender Session Layer 1 Receiver Session Layer Receiver Application Layer S_Data.req T_Data.req T_DataSOM.ind Message S_Data.con T_Data.con T_Data.ind S_Data.ind Key 1 optional, i.e. the transpt/netwk layer suppts the T_DataSOM.ind interfaces Figure 3 Session layer service primitives Multiple frame message The following communication scenarios shall distinguished: a) physical communication during 1) default session, and 2) non-default session session handling required; b) functional communication during 1) default session, and 2) non-default session session handling required All rights reserved 5

12 :2013(E) F all cases, the possibility of requesting an enhanced response-timing window by the server via a negative response message, including a negative response code 0x78, shall considered. The transpt/netwk layer services as defined in different standards (e.g DoCAN CoFR) are used to perfm the diagnostic session management timing in the client and the server Specification of session layer service primitives General In der to descri the function of the session layer, services provided to higher layers and the internal operations of the session layer have to considered S_Data.request The service primitive requests transmission of S_Data with S_Length numr of bytes from the sender to the receiver peer entities identified by the address infmation in S_SA, S_TA, S_TAtype, and S_AE. Each time the S_Data.request service is called, the session layer shall signal the completion ( failure) of the message transmission to the service user by means of the issuing of an S_Data.confirm service call. S_Data.request ( S_Data.confirm ) S_Mtype, S_SA, S_TA, S_TAtype, [S_AE], S_Data [Data#1, Data#2,, Data#n ], S_Length The S_Data.confirm service is issued by the session layer. The service primitive confirms the completion of an S_Data.request service identified by the address infmation in S_SA, S_TA, S_TAtype, and S_AE. The parameter S_Result provides the status of the service request. S_Data.confirm ( S_Data.indication ) S_Mtype, S_SA, S_TA, S_TAtype, [S_AE], S_Result The S_Data.indication service is issued by the session layer. The service primitive indicates S_Result ents and delivers S_Data with S_Length bytes received from a peer protocol entity identified by the address infmation in S_SA, S_TA, S_TAtype to the adjacent upper layer All rights reserved

13 Bestelfmulier Stuur naar: NEN Standards oducts & Services t.a.v. afdeling Klantenservice Antwodnummer WB Delft NEN Standards oducts & Services Postbus GB Delft Vlinderweg AX Delft Ja, ik stel ex :2013 en Wegvoertuigen - Unifme diagnostische diensten (UDS) - Deel 2: Session-layer-diensten T (015) F (015) Wilt u deze nm in PDF-fmaat? Deze stelt u eenvoudig via Gratis nieuwsbrien Wilt u op de hoogte blijven van de laatste ontwikkelingen op het gebied van nmen, nmalisatie en regelging? Neem dan een gratis abonnement op een van onze nieuwsbrien. Gegens Bedrijf / Instelling T.a.v. O M O V Klantnummer NEN Uw dernummer BTW nummer Postbus / Adres Postcode Plaats Telefoon Fax Factuuradres (indien dit afwijkt van bovenstaand adres) Postbus / Adres Postcode Plaats Datum Handtekening Retourneren Fax: klantenservice@nen.nl Post: NEN Standards oducts & Services, t.a.v. afdeling Klantenservice Antwodnummer 10214, 2600 WB Delft (geen postzegel nodig). waarden De prijzen zijn gig tot 31 decemr 2018, tenzij anders aangegen. Alle prijzen zijn excl. btw, verzend- en handelingskosten en onder vohoud bij o.m. - en IEC-nmen. Bestelt u via de nmshop een pdf, dan taalt u geen handeling en verzendkosten. Meer infmatie: telefoon , dagelijks van 8.30 tot uur. Wijzigingen en typefouten in teksten en prijsinfmatie vohouden. U kunt onze algemene vowaarden terugvinden op: LEREN, WERKEN EN GROEIEN MET NEN pr