Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Abstraction


This chapter provides requirements for the function of the 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.).

This figure shows the data flow diagram with the Hardware side.
 

...

                                  Figure1
                 

Use cases


In the following table, use cases which need the Power State Management function are described.

...

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

(4), (5)

(4)The transition request to change the selected services states to “Partially running” is requested from applications or services which need to be used at the state against the shutdown request from the hardware side.

(5)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 terminates.


Functional Requirements


This table includes the functional requirements of Power State Management module.  Figure1 will be used to explain this requirement.

#

Description

1

Power State Management should receive state transition requests from the Hardware side.

2

When Power State Management receives the state transition requests from Hardware side to change to each 5 power state, the target service notified from Power State Management module should be configurable.

3

Power State Management should notify each service of the transition request based on the configuration in the case of requirements(#2).

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 Hardware side.)

5

At Ready state, some services should be defined as connected(which can start up quickly). For example, Bluetooth or Wifi services are considered to be such targets.

Power State Management in Basesystem

Reference implementation by Basesystem


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.

  • Power Service
  • System Manager

Image Modified

                                                                                                          Figure4


Power Service

Power service provides functions such as notifying the system manager unit of power state transition requests by getting the notification from the Hardware side, or receiving requests and notifying the Hardware 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.

Reference 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

...