Describe the use cases of functions which are common in each OEM's products and functional requirements on implementation.
Supplement)
#d:What the Basesystem functions responsible for Power state management are.
Abstraction
This chapter provides requirements for the function of the Power State Management.
By vehicle power state transition(like ACC On/Off) or other use cases, IVI receives the power state transition requests from Power State Notification Device.
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.
This figure shows the data flow diagram with the Power State Notification Device as a center.
Figure2
Use cases
The following use cases can be assumed when using the Power State Management function.
# | Item |
1 | A user searches the destination on the navigation display after starting the engine. |
2 | When a user wants to go to the destination quickly after starting the engine, he or she can quickly search the destination because of quick startup of IVI. |
3 | A user shutdown IVI by the ACC off. |
4 | When a user wants to continue a handsfree call after ACC off, he or she can continue it although the display is off as partially running state.
|
This is a simplified use case diagram of the above use case.
Figure 3
In Production Readiness, to realize the use cases, power state transition of IVI in general is defined as follows.
- The state of IVI power-off
- The state which is ready to boot IVI(Ready)
- The state that the part of IVI features can be used(Partially running)
- The state which IVI has started(Running).
To realize various use cases, the above four transition states are considered necessary. However, the B and C states depend on the requirements of each OEM.
The following diagram is a description of the above 4 states.
# | IVI power state | Description of each state |
1 | Power-off | The IVI system is turned off. |
2 | Ready | The IVI system is turned on. |
3 | Partially running | The IVI system is turned on. |
4 | Running | The IVI is turned on. |
The following shows the IVI state transition diagram of the above diagram. The conditions for each transition are also described.
Figure 4
Use cases diagram | State transition diagram | The condition of transition |
#1 | (1) | (1)Power State Notification Device sends the transition request to change the IVI state to “Running”. |
#2 | (3), (4) | (3)Power State Notification Device sends the transition request to change the selected services states to “Ready”. (4)Power State Notification Device sends the transition request to change the IVI state to “Running”. |
#3 | (2) | (2)Power State Notification Device sends the transition request to change the IVI state to “Power-off”. |
#4 | (5), (6) | (5)Power State Notification Device sends the transition request to change the selected services states to “Partially running”. (6)Power State Notification Device sends the transition request to change the IVI state to “Power-off” and terminate IVI system. |
Functional Requirements
This table includes the functional requirements of Power State Management module. Figure2 will be used to explain this requirement.
# | Description |
1 | Power State Management should receive state transition requests from Power state notification device. |
2 | When Power State Management receives the state transition requests from Power State notification device to change to the each 4 power state, Power State Management should have the list that configures the target services to be notified of the request. |
3 | Power State Management should notify each Service of the transition request based on the configuration list in #2 above. |
4 | Power State Management should receive completion notification when the Service that received the request notification completes the state transition.(Finally the information will be notified to the Power State Notification Device.) |
5 | Power State Management notifies the state transition completion information to the Power State Notification Device. |
6 | Power State Management should not notify the Power State Notification Device every time the state transition completion information is sent from the Service, but rather notifies the device of a certain amount of information at once. |
Power state management in Basesystem
Functional Requirements to implement in Basesystem
To have Power State Management for the use cases above, we provided the following functions as the part of the power management function. Refer to the software configuration diagram(Figure1).
- Power service
- System manager
- (NS frameworkunified)
Figure5
Power service
Power service provides functions such as notifying the system manager unit of power state transition requests by getting the notification from the power state notification device side, or receiving requests and notifying the power state notification device side of it.
System manager
In order to control the system according to the power state transition request, System manager notifies the services on the service list of a power state transition received from Power service.
NS frameworkunified
NS frameworkunified provides mechanism for communicating with any process in Basesystem.
Reference to source code
- System manager
https://gerrit.automotivelinux.org/gerrit/gitweb?p=staging/basesystem.git;a=tree;f=service/system/system_manager;hb=refs/heads/master - Power service
https://gerrit.automotivelinux.org/gerrit/gitweb?p=staging/basesystem.git;a=tree;f=service/system/power_service;h=fabcbf6aabbf0b7dd8a1df2fb35491029a2d1fdd;hb=refs/heads/master