ISO 22900-3-2012 PDF

Full title and description

Road vehicles — Modular vehicle communication interface (MVCI) — Part 3: Diagnostic server application programming interface (D-Server API). Defines an object‑oriented application programming interface for diagnostic server applications that provide access to on‑board control units (ECUs) via a communication server and VCI module; intended to enable compatible, exchangeable server implementations used during design, production and maintenance of vehicle communication systems.

Abstract

This part of ISO 22900 specifies the Diagnostic Server (D‑Server) API: an object‑oriented interface describing server function blocks (measurement, calibration, diagnostics) and the methods, data types and error handling required to implement diagnostic server applications that interoperate with MVCI protocol modules and VCIs for ECU access and diagnostic services. It focuses on enabling interchangeable, vendor‑neutral server implementations for diagnostic and calibration tasks.

General information

• Status: Published (confirmed).
• Publication date: December 2012 (Edition 2).
• Publisher: International Organization for Standardization (ISO).
• ICS / categories: 43.040.15 (Car informatics; on‑board computer systems).
• Edition / version: Edition 2 (2012).
• Number of pages: 281.

Key bibliographic and lifecycle details above are taken from the ISO bibliographic record for ISO 22900‑3:2012. The 2012 edition superseded the 2009 edition.

Scope

Specifies the Diagnostic Server application programming interface (D‑Server API) for a Modular Vehicle Communication Interface (MVCI) environment. The scope includes definitions of server architecture and function blocks (M: measurement, C: calibration, D: diagnostics), API classes and methods, data types, conventions, session and error handling, and optional/annex functionality such as flash programming and value read/set mechanisms. The aim is to allow diagnostic server applications from different vendors to be compatible and exchangeable when used with MVCI protocol modules and VCIs.

Key topics and requirements

• Object‑oriented Diagnostic Server API specifying classes, methods and data structures for diagnostics, measurement and calibration.
• Definition of server function blocks (M, C, D) and their responsibilities in MVCI systems.
• Session management, PDU/PDUs handling and abstraction of transport/protocol details to support multiple diagnostic protocols (UDS, KWP, CAN, DoIP through protocol modules).
• Error codes, status reporting and standardized exception/diagnostic information handling.
• Annexes and optional features: flash programming examples (KWP/ISO 14230), value reading/setting by string, system parameters, deprecated methods and overview of optional functionality.
• Interoperability requirements with MVCI protocol modules (D‑PDU API) and diagnostic data formats (e.g., ODX) to enable tool and VCI vendor independence.

Typical use and users

Used by automotive OEM software teams, diagnostic tool and VCI manufacturers, aftermarket tool vendors, calibration and test‑system integrators, and software developers implementing diagnostic servers or integrating diagnostics into production/test systems. Typical applications include ECU diagnostics, calibration, flashing/reprogramming support and production line test software that must interoperate across different VCIs and protocol modules.

Related standards

Closely related documents and interoperable standards include: ISO 22900‑1 (MVCI — Part 1: hardware design requirements), ISO 22900‑2 (MVCI — D‑PDU API; newer editions published since 2009 and updated in 2022), ISO 22901 (ODX — Open Diagnostic Data Exchange), and relevant diagnostic protocol standards such as ISO 14229 (UDS) and ISO 14230 (KWP). The standard also references migration/compatibility concerns with vehicle programming APIs (for example SAE J2534 / RP1210 in related contexts).

Keywords

MVCI; D‑Server API; diagnostic server; ECU access; VCI; D‑PDU; ODX; UDS; KWP; flash programming; measurement; calibration; diagnostic trouble codes (DTC); object‑oriented API.

FAQ

Q: What is this standard?

A: ISO 22900‑3:2012 is Part 3 of the MVCI series and defines the Diagnostic Server application programming interface (D‑Server API) used to implement diagnostic server applications that access and manage ECUs via MVCI communication stacks and VCIs.

Q: What does it cover?

A: It covers the object‑oriented API structure, server function blocks (measurement, calibration, diagnostics), API methods, data types, error handling, session management and several informative/normative annexes including examples for flash programming and value read/set methods.

Q: Who typically uses it?

A: OEM software teams, diagnostic application developers, VCI and protocol‑module vendors, aftermarket diagnostic tool makers, calibration engineers and production/test system integrators who need interoperable server APIs for ECU diagnostics, calibration and flashing.

Q: Is it current or superseded?

A: The 2012 publication is Edition 2 and supersedes the 2009 edition; ISO’s bibliographic record lists ISO 22900‑3:2012 as the published/confirmed edition. Users should check ISO or national standards bodies for any later revisions or withdrawal notices before use in new projects.

Q: Is it part of a series?

A: Yes — ISO 22900 is a multi‑part series (for example Part 1: hardware design requirements, Part 2: D‑PDU API, Part 3: D‑Server API) that together define the MVCI architecture and interfaces used for vehicle diagnostics and reprogramming.

Q: What are the key keywords?

A: MVCI, D‑Server API, diagnostic server, ECU, VCI, D‑PDU, ODX, UDS, KWP, flash programming, measurement, calibration.