...
# | Item | User | |||
---|---|---|---|---|---|
1 | A user opens the Door and rides in the car. And the user presses the start button for ACC-ON.Then the car and the IVI turns on. | Driver | |||
2 | A user shuts down IVI by the ACC off. Then IVI turns off. | Driver | 3 | After arrival at the destination, when a user wants to continue a handsfree call after ACC off-OFF, the user can continue it although the display is off. When the user finishes the call, the hands-free function will end. Then IVI turns off. | Driver |
3 | When a user wants to get the car out of the garage, the user can use the smartphone-linked function to control outside and after that get into the car. (There are other use cases, for example, when no one is in the car, the multimedia system will be updated through OTA. ) | Driver | |||
4 | A user presses the button for ACC-OFF, gets out of the car and gets into the car soon. | Driver | |||
5 | A user presses the button for ACC off, gets out of the car and does not get into the car for a long time. | Driver |
This is a simplified use case diagram of the above use case.
Figure2 Figure2
In Production Readiness, to realize the use cases, power state transition of IVI in general is defined as follows.
...
The following shows the IVI state transition diagram of the above table. The conditions for each transition are also described.
Figure3) State transition diagram
Use cases diagram | State transition diagram | The condition of transition |
---|---|---|
#1 | (1), (2) | (1)The transition request to change the selected services states to “Ready” is sent from the Hardware side. (2)The transition request to change the IVI state to “Running” is sent from the Hardware side. |
#2 | (3) | (3)The transition request to change the IVI state to “Power-off” is sent from the Hardware side. |
#3 | (41), (5)(46) | (1)The transition request to change the selected services states to “Ready” is sent from the Hardware side. (6)The transition request to change the selected services states to “Partially running” Running” is requested from applications or services which need to be used at the state against the shutdown request from the hardware side.(5sent from the Hardware side. |
#4 | (3), (4) | (3)The transition request to change the IVI state to “Power-off” is sent from the Hardware side. (4)The transition request to change the IVI state to Running is sent from the Hardware side. |
#5 | (3), (5) | (3)The transition request to change the IVI state to “Power-off” is requested from applications or services which don’t need the state and IVI system terminatessent from the Hardware side. (5)No transition request to change the IVI state is sent. |
Functional Requirements
This table includes the functional requirements of Power State Management module. Figure1 will be used to explain this requirement.
...
To have Power State Management for the use cases above, we provided the following functions as part of the power management function. Refer to the software configuration diagram(2. The scope).
- Power Service
- System Manager
...