The following is a list of features that are the topics for describing the functional requirements.
| # | Item | Description |
|---|---|---|
| 1 | Services Launch / Termination | When using IVI, it’s required that not only the system is launched at boot time, but also the services that will be used are launched. This is because the necessary services need to be launched for the user to use the application and for the system to work. Similarly, when the system terminates, the services that have been already launched should also be terminated. |
| 2 | System Anomaly Detection
| IVI system needs the ability to detect anomalies and maintain a normal state. For this purpose, the functional requirements to detect anomalies and to deal with anomalies are defined. In this section, we classify the functions for System Anomaly Detection into two categories. Service Anomaly" and "Resource Anomaly". "Service Anomaly" represents an abnormality at the time of service startup or service use and "Resource Anomaly" represents an abnormal state such as a resource state that exceeds a specified value. |
| 3 | System Logging Support | In the use of IVI products, it is necessary to collect and centrally manage logs created in multiple places in the system, which are records of various events and times that occurred in systems. The reasons to keep logs are for security measures or information gathering and decision making in the operation, management and countermeasure for anomalies of the product system. |
| 4 | Power State Management | On vehicle power state transitions(like ACC On/Off) or other use cases, IVI should receive the power state transition requests. In such cases of state transition, it is necessary to have a mechanism to manage the services running on IVI and notify the transition request. What is described here indicates some kind of notification from the Hardware side (e.g. Acc on, etc.). |
| 5 | Backup data management | Data needs to be secured in products to prevent data corruption due to failures. Backing up the necessary data on a regular basis will help maintain the reliability of the product. |
| 6 | Message notification and IPC | This section describes the functions that are necessary to interact with each function and process unit when using the product. For example, when an anomaly occurs in a system, there may be a case where the anomaly is messaged. The requirements for the function to notify messages for such cases are described. In addition, we will focus on and describe communication functions, such as functions to communicate between processes. |
| 7 | Common process of extended devices control | |
| 8 | CAN communication | |
| 9 | GPS or Sensor information | |
| 10 | RPC | |
| 11 | Getting vehicle parameter | |
| 12 | Supporting system call |