BS ISO 15765-1 pdf download – Road vehicles -Diagnostic communication over ControllerArea Network (DoCAN) Part 1: General information and use case definition

BS ISO 15765-1 pdf download – Road vehicles -Diagnosticcommunication over ControllerArea Network (DoCAN) Part 1: General information and use case definition.
ISO 15765 is applicable to vehicle diagnostic systems implemented on a CAN communication network as specified en ISO 11898.
ISO 15765 has been established In order to define common requirements for vehicle diagnostic systems implemented on a CAN communication link as specified ii Iso 11898.
Although p1marify intended for diagnostic systems, ISO 15765 has been developed to also meet requwements from other CAN-based systems needing a network layer protocol.
5.2 Open Systems Interconnection (OSI) model
ISO 15765 is based on the Open Systems Interconnection (OSI) Basic Reference Model as specified in ISO1IEC 7498-1 which structLwes communication systems into seven layers.
All pails of ISO 15765 are guided by the OSI service conventions as specified in ISO/1EC 10731 to me exient that they are applicable to diagnostic services. These conventions define the interaction between the service user and the service provider through service primitives.
The aim of this subclause is to give an overview of the OSI model and show how it has been used as a guidebne for this part of ISO 15765. It also shows how the OSI service conventions have been applied to ISO 15765.
The OSI model structures data communication into seven layers called, from top down, apphcation layer
(layer 7), presentatIon layer (layer 6). sessIon layer (layer 5). transport protocol layer (layer 4), network layer
(layer 3). data link layer (layer 2) and physical layer (layer 1).
A subse of these layers is used in ISO 15765, which specifies the application, session, transport protocol, network, data link and physical layers for DoCAN.
The purpose of each layer is to provide services to the layer above The application layer provides services to the diagnostic application, The active parts of each layer, implemented in software, hardware or any combination of software and herdware. are called entities. In the OSI model, communication takes place between entities of the same layer in different nodes. Such communicating entities of the same layer are called peer entities,
The services provided by one layer are available at the Service Access Point (SAP) of that layer. The layer above can use them by exchanging data parameters.
ISO 15765 distinguishes between the services provided by a layer to the layer above it and the protocol used oy me layer to send a message between me peer entitles of that layer. The reason for this dstinctlon Is to make the services, especially the application layer services and the transport layer services, reusable for CAN and for other network types. In this way, the protocol is hidden from the service user and it is possible to change the protocol if special system requirements demand it.
Figure 1 illustrates the most applicable application implementations utilizing the DCCAN protocol.
A diagnostic gateway is a node in the network that is physically connected to two (or more) sub-networks andhas the ability to transfer diagnostic messages between the sub-networks.
Connecting individual sub-networks via diagnostic gateways creates larger diagnostic network architectures.
7 DoCAN use case overview and principles
7.1Overview
The individual use cases covered by the DoCAN protocol derive from the use of diagnostic communication inthe following areas:
-vehicle/EcU engineering (development);
vehicle/ECU manufacturing (production plant, assembly line);service (dealership, aftermarket repair shop);
-legislated inspections (emission-check, safety inspection).
NOTE IS0 15765 will only focus on communication protocol provisions which are necessary to support these usecases. lt will not specify data contents,signal update rate,signal availability, etc.
7.2DoCAN use case clusters
Table 2 provides an overview of the main DoCAN use case clusters which are applicable to systems whichsupport the DoCAN protocol. A main DoCAN use case cluster may have one or more use case definitions.