Versions Compared

Old Version 35

changes.mady.by.user Riku Nomoto

Saved on

compared with

New Version 36

changes.mady.by.user Riku Nomoto

Saved on

Key

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

...

This chapter provides requirements for the function of the Power State Management.

From the user's perspective, the system appears to be in ACC-ON/OFF state, but there are various power states inside the vehicle that need to be managed.
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 to each services from Power State Management module.

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 In the following table, use cases which need the Power State Management function are described. Each user is a driver.

#

Item

User

1

A user

searches the destination on the navigation display after starting the car.

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

shutdown

shuts down IVI by the ACC off. Then IVI turns off.

Driver

3

When

After arrival at the destination, when a user wants to continue a handsfree call after ACC off,

he or she

the user can continue it although the display is

off as partially running state

off. When the user finishes the call, the hands-free function will end. Then IVI turns off.
(There are other use cases, for example, 

  • When
an
  • a user wants to get the car out,
he or she
  • the user can use the smartphone-linked function to control outside and after that get into the car.
  • When no one is in the car, the multimedia system will be updated through OTA. )
User opens the door

Driver

4

A user gets out of the car and gets into the car soon.

Driver

5

A user 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.


　　　

...

#

IVI power state

Description of each state

1

Power-off

The IVI system is turned off.
The IVI display is turned off.

2

Ready

The IVI system is turned on.
The IVI display is turned off.
The IVI system prepares selected services so that the IVI system can provide user functions quickly when the IVI becomes on.
BT and Wifi services should be prepared at Ready state as standard..

※When starting a car with unprepared IVI, it takes a lot of time.So the state “Ready” is necessary.

3

Partially running

The IVI system is turned on.
The IVI display is turned off.
The IVI system keeps selected services so that the services can be used for some time after the ACC off.

4

Running

The IVI is turned on.
Also the IVI display is turned on.
All of the user functions are available.

...

#

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 4 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.

...