BS ISO 26021-2:2008

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviated terms
5 Conventions
6 Pyrotechnic device deployment via on-board diagnostic
  architecture
  6.1 Vehicle system description
  6.2 Example of in-vehicle hardware and software required
  6.3 Additional communication line (optional)
  6.4 Requirements for the PDT
7 Relationship to existing standards
  7.1 General
  7.2 Application layer
  7.3 Session layer
  7.4 Application layer and diagnostic session management
      timing
  7.5 Network layer
  7.6 Data link layer
  7.7 Data link layer
  7.8 Physical layer
8 Deployment process
  8.1 General information
  8.2 System preconditions
  8.3 Initiation of the communication between PDT and PCU
  8.4 Deployment process description
  8.5 Software provisions
  8.6 Error handling and reaction
9 Communication with diagnostic services
  9.1 Unified diagnostic services overview
  9.2 Diagnostic session control (10 hex) service
  9.3 EcuReset (11 hex) service
  9.4 Read data by identifier (22 hex) service
  9.5 Write data by identifier (2E hex) service
  9.6 Security access (27 hex) service
  9.7 RoutineControl (31 hex) service
  9.8 TesterPresent (3E hex) service
Annex A (normative) - Specification of the data identifier
                      used
Annex B (normative) - Deployment loop parameter definitions
Annex C (normative) - Routine control parameter definitions
Bibliography

Specifies the deployment process, the system architecture, CAN-based communication methods and system preconditions which have to be implemented to fulfil the use cases defined in ISO 26021-1.