BS ISO 22900-3:2009
$215.11
Road vehicles. Modular vehicle communication interface (MVCI) – Diagnostic server application programming interface (D-Server API)
| Published By | Publication Date | Number of Pages |
| BSI | 2009 | 464 |
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 13 | Scope Normative references |
| 14 | Terms, definitions, symbols and abbreviated terms Terms and definitions |
| 15 | Abbreviated terms |
| 16 | Typographical conventions and mnemonics used in this part of |
| 17 | Legends for used graphics Hierarchical diagrams Sequence diagrams |
| 18 | Stereotypes General considerations Specification release version information |
| 19 | Structure of MCD systems |
| 22 | Function block common MCD MCD system object |
| 23 | Version information retrieval Description of Terms General Client-controlled object Location |
| 24 | Logical Link (LOGICAL-LINK) Project |
| 25 | Server-controlled mutable object Server-controlled object (shared object) States of the MCD system object |
| 27 | State changes |
| 28 | Project configuration |
| 30 | Interface structure of MCD-server API Separation in database and runtime side |
| 31 | Hierarchical model |
| 32 | Structure of the database Overview Associations of DbLocation for MCD |
| 34 | Database within the field Measurement and Calibration Database within the field Diagnostics Collections Types and methods |
| 36 | RunTime collections Overview |
| 37 | RunTime collections in MC RunTime collections in D |
| 38 | Database collections |
| 40 | Handling of collection of ASCIISTRING EventHandler Registering/deregistering of the EventHandlers |
| 42 | Methods of the EventHandlers |
| 47 | Eventfilter |
| 55 | Multi-Client capability Requirements |
| 58 | Design |
| 59 | Proxy in Multi Client Architecture |
| 62 | Cooperation Level |
| 64 | Symbolic Names of Clients Selection and de-selection of Project and VehicleInfo in a m |
| 65 | Notification |
| 66 | Remove shared objects |
| 67 | Locking |
| 69 | Client Controlled Objects |
| 70 | Resource Release Use cases |
| 71 | Requirements Solution Critical Section, Critical Groups of Methods |
| 73 | Result access |
| 74 | MCD value Value types |
| 75 | Method getValue Behaviour of MCDRequestParameter::getValue() Behaviour of MCDResponseParameter::getValue() Behaviour of MCDParameter::getValue() Method setValue |
| 76 | Method createValue |
| 80 | Use cases View Instantiation of projects |
| 83 | Database access |
| 85 | Destruction |
| 86 | Function block Common MD Collector ERD |
| 87 | Concept |
| 91 | Result access Object list configuration Structure of the collector sample list |
| 93 | Result structure |
| 96 | Collector usage in diagnostics |
| 97 | Use cases Measurement with a collector – activation |
| 99 | Measurement with a collector – result access |
| 102 | Measurement with a collector – polling for results |
| 103 | Function block Diagnostics Description of Terms General Access Key Functional Class (FUNCTIONAL-CLASS) Job (SINGLE-ECU-JOB, MULTIPLE-ECU-JOB) Physical Interface Link |
| 104 | Physical Link Physical Vehicle Link (PHYSICAL-VEHICLE-LINK) Structuring of the function block Diagnostics Separation in database and runtime side |
| 106 | Relation between Vehicle Connector Information Table and Log |
| 107 | Hierarchical model |
| 109 | Entity Relationship Diagrams ERD DbLocation |
| 110 | ERD Logical Link and associated MCD Objects |
| 112 | ERD Request and Response Parameter associations |
| 120 | ERD Jobs |
| 121 | System Properties Diagnostic DiagComPrimitives and Services Diagnostic DiagComPrimitives and States Diagnostic DiagComPrimitives |
| 123 | States of DiagComPrimitives |
| 125 | Service overview |
| 132 | Non cyclic single shot diag service |
| 134 | Cyclic diag service |
| 135 | Repeated diag service |
| 136 | Repeated send only diag service |
| 137 | Repeated receive only diag service Updating repetition parameters |
| 138 | Summary |
| 139 | Protocol parameters General |
| 140 | Introduction related to ODX |
| 145 | Inheritance of protocol parameters |
| 148 | Database part Runtime part |
| 152 | Suppress Positive Response |
| 155 | Diagnostic variables |
| 157 | eEND_OF_PDU as RequestParameter Database side |
| 159 | Runtime side |
| 160 | COMPUCODE |
| 161 | Variable length parameters |
| 163 | Layer inheritance of services Goal Layer inheritance of services |
| 168 | Service handling on functional and physical locations |
| 170 | Variant Identification and Selection (VI / VIS) Goal Variant Identification Algorithm Logical Link Basics |
| 172 | Principles of Variant Identification and Variant Identificat |
| 174 | Variant Patterns and Matching Parameters |
| 175 | Identification Algorithm |
| 178 | General VI/VIS handling considerations |
| 180 | Deselecting of selected variants Request and Response parameters of VI and VIS Goal |
| 181 | Request Parameter Structure of VI and VIS |
| 183 | Response Parameter Structure of VI and VIS |
| 184 | Switching Database Template Generation On and Off |
| 185 | Example Scenarios for VI and VIS |
| 195 | Base Variant Identification and Selection |
| 202 | Use Cases Creation of LogicalLink and usage of DiagComPrimitives |
| 204 | Removal of communication objects |
| 206 | Service Handling Non cyclic diag service execution |
| 207 | Cyclic diag service execution |
| 208 | Result access General |
| 209 | Result buffer |
| 211 | Error handling in results |
| 212 | Result matching for database templates |
| 237 | Filtering of results Principle |
| 241 | Handling rules |
| 242 | Read DTC |
| 246 | Logical Link General Connection overview |
| 247 | State diagram of Logical Link |
| 255 | Logical Link examples |
| 260 | Gateway handling |
| 262 | Examples and Relations between Logical Links, Locations and |
| 268 | Functional Addressing |
| 270 | Tables General |
| 272 | Usage of tables within DiagComPrimitives |
| 275 | Dynamically Defined Local Id / Table Parameters (DDLID) General DDLID principle and requirements |
| 276 | Lifecycle General Creation of Dynamically Defined Local Id |
| 278 | Reading by Dynamically Defined Local Id Deletion of Dynamically Defined Local Id |
| 279 | DB-Templates for Requests and Responses regarding DDLID |
| 280 | Procedure description |
| 284 | Internationalisation Multi language support Units Special Data Groups |
| 285 | ECU Flash programming Goal |
| 286 | Description of Terms for ECU-Reprogramming General ECU-MEM Description Flash Class Description Flash Job Description Flash Key Description Flash Session Description |
| 287 | Flash Session Desc Description Description of ‘Late-bound data files’ Mechanism Priority Description Structure of the function block flash programming Database part |
| 291 | Runtime part |
| 292 | Handling binary flash data |
| 294 | Identification mechanism |
| 297 | Segmenting Flash Data |
| 300 | Management of ECU-MEMs |
| 301 | Physical Memories |
| 303 | Executing flash sessions Flash session execution basics |
| 304 | Flash job basics |
| 308 | Uploading Flash Data from an ECU Downloading Flash Data to an ECU |
| 310 | Checksum calculation in Flash Jobs |
| 311 | Library |
| 312 | Java Jobs General General information Java Jobs |
| 313 | Types of Java Jobs General Single ECU Job Flash Job |
| 314 | Security access job |
| 315 | Multiple ECU Job |
| 316 | Handling of Java Jobs General Development of Java Jobs |
| 318 | Deployment of Java Jobs Job Execution Modes |
| 319 | Hash signatures for Jobs |
| 320 | Job Parameter handling |
| 322 | Job Communication Parameter handling Job Result handling Job Result Generation |
| 325 | Progress information |
| 326 | Job execution General Single execution of a Job |
| 332 | Repeated execution of Job |
| 333 | Cancellation of a Job |
| 334 | Job example |
| 344 | ECU configuration General ECU Configuration Database Part |
| 348 | ECU Configuration Runtime Part |
| 351 | Error Handling Initialising an MCDConfigurationRecord |
| 352 | Offline versus Online Configuration |
| 353 | Uploading and Downloading Configuration Strings Decomposing a Configuration String for Transfer |
| 354 | Downloading Configuration Records to an ECU |
| 356 | Uploading Configuration Records from an ECU |
| 357 | Management of CONFIG-DATAs |
| 358 | Audiences and Additional Audiences General |
| 360 | Audiences Additional Audiences |
| 361 | Function Dictionary and Sub-Components Terms and requirements General MCDDbFunctionDictionary MCDDbSubComponent Functions and function group in ODX |
| 363 | Function dictionary data model description |
| 365 | Function dictionary usage scenario |
| 367 | Sub-Component data model description |
| 368 | Sub-Component usage scenario |
| 369 | ECU States |
| 372 | Monitoring vehicle bus traffic |
| 374 | Support of VCI module selection and other VCI module feature General Definitions General behaviour of D-PDU API related D-server methods |
| 375 | Overview of VCI module related classes |
| 376 | VCI module selection MCDInterface |
| 377 | VCI module selection sequence |
| 378 | Interface status events |
| 379 | MCDInterfaceResource Selection of an interface resource |
| 380 | Send Break Signal |
| 381 | MCDDbInterfaceCable Accessing VCI module features |
| 382 | Adding Logical Links which are not found in the Vehicle Info |
| 383 | Behaviour of a MCD-server not supporting VCI Modules in acco |
| 384 | Mapping of D-PDU API methods General Initialization and Selection of VCI Modules Communication on a Logical Link |
| 386 | Handling of Communication Parameters Changing communication parameters from the client applicatio |
| 387 | Setting temporary communication parameters for a DiagComPrim Changing UNIQUE_ID Communication Parameters |
| 388 | MCDStartCommunication and MCDStopCommunication |
| 389 | Error Codes Principle |
| 391 | Description of the errors Error free behaviour Parameterisation errors Runtime / ProgramViolation errors Database errors System errors Communication errors Job error |
