0. Change History

• Glossary is cleated.
• Power State Management SPEC
  • The diagram of abstraction(Figure1) is improved.
    • Described as a request comes from the Vehicle.
    • Added the description of a device that sends CAN data to Hardware.
  • The use cases are corrected.
    • Starting up IVI quickly is considered at the default way of start-up, so the use case of IVI (normaly) start-up is removed.
  • The power state of suspend is omitted.
    • The reason why the state is not needed is that the state is not must in actual product in general
  • The conditions of transition are improved
    • From Running to Partially Running, the request of state change is from applications or services.
    • From Partially Running to Power-off, the request of state change is from applications or services.
  • Functional requirements are improved .
    • Some services are defined as connected at Ready state

• 4.2 System Anomaly Detection

The following are added.

• 4.1 Services Launch / Termination

• 4.3 System Logging Support
• 4.0 Abstraction for each function

Use cases are improved. The column for clarifying the user is added.

• 4.1 Services Launch / Termination

• 4.2 System Anomaly Detection
• 4.3 System Logging Support
• 4.4 Power state management

The following are added.

4.4 Power state management

• The outline of the above requirements document has been revised (background has been added).
• In addition, we have added the use cases that were pointed out in the Virtual Workshop.

The titles of each chapter are changed.

• 4.1 Power state management

• 4.2 Services Launch / Termination

• 4.3 System Failure Detection and Procedure

4.2 Services Launch / Termination

The following are added.

• 4.5 Persistent data management
• 4.6 Vehicle Parameter Configuration

The following are added.

4.7 CAN Communication