The following is a list of features that are the topics for describing the functional requirements.
| # | Item | Description | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 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. | ||||||||||||||||||||||
| 2 | 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. | ||||||||||||||||||||||
| 23 | Resource Anomaly System Anomaly Detection Failure Detection and Procedure | 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. | ||||||||||||||||||||||
| 34 | 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.5 | Backup data management | 6 | Message notification | 7 | IPC and related functions | 8 | Common process of extended devices control | 9 | Process management | 10 | CAN communication | 11 | GPS or Sensor information | 12 | RPC | 13 | Getting vehicle parameter | 14 | Supporting system call|
| 5 | Persistent 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 | Vehicle Parameter Configuration | IVI system requires software that is designed to meet a variety of needs and requirements. These needs and requirements vary depending on the country where it is used or OEMs. In order to prevent huge numbers of IVI system software branching, a configuration mechanism is needed to cover several options without changing the program. | ||||||||||||||||||||||
| 7 | CAN communication | CAN is the most major communication bus among ECUs in-vehicle systems. It is sufficient and reliable to obtain vehicle information such as speed data and HVAC control commands. CAN communication provides a communication function for handling CAN data. | ||||||||||||||||||||||
| 8 | GPS or Sensor information | For IVI system, Positioning information is a very essential one as it is moving. Positioning information includes a variety of information. IVI system needs to provide functions that can provide GPS and Sensor data to necessary applications. |