GUI resource control

(Screen Resources)

Second one is visibility control.

・Basically, visibility should be "ON" during area owner was assigned.

・However, visibility may set to "OFF" during driving mode due to driving mode due to driving restriction.

Last one is order control of each layer.

・Policy Manager decides the order of each layer, and issue z-order information for each layer.

GUI resource control

(Sound Resources)

One is playback control such as play, pause and stop.

・Policy Manager issues to play sound for sound area owner, and if area owner was changed, then issue to stop previous playing sound stream and to start play latest area owner.

Other one is volume control.

・Two or more sound streams of same zone may playback simultaneously if each sound streams are assigned to different sound type.

・Policy Manager specifies volume parameter for each sound streams.

・if route guidance and music playback are mixed, assign higher volume to route guidance and volume down for music playback.

GUI resource control

(Input Resources)

System resource

System resource

(External condition collection)

Policy manager must provide a mechanism to configure (or define) the priority rule.

Policy manager must provide a mechanism to configure the vehicle status for arbitration

System must provide a mechanism to assign resource owner to the requested resource according to external condition.

System must provide a mechanism to receive the layer request.

System must provide a mechanism to receive the area request.

System should provide an interface to request both screen and sound resource simultaneously.

System should provide a mechanism to receive the request of forcibly acquire and forcibly release.

System should provide a mechanism to receive the request that is specified the following effect

   ・the effect at the transition

   ・the effect of display surface

System must provide a mechanism to judge priority of resources.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to judge visible surfaces according to vehicle running state.

* 4 Need to change because the scope of requirements varies depending on the reader

System must hide the surface that has too much information.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to issue the resource control according to judgment.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to issue the following resource control.

   ・Visible/Invisible

   ・Change position

   ・Raise

* 4 Need to change because the scope of requirements varies depending on the reader

System should provide a mechanism to set the following effect of the surface to other system.

   ・the effect at the transition

・the effect of display surface

System must provide a mechanism to receive the zone definition.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to receive the sound type definition.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to receive the owner request.

* 4 Need to change because the scope of requirements varies depending on the reader

System should provide a mechanism to receive the request of forcibly acquire and forcibly release.

* 4 Need to change because the scope of requirements varies depending on the reader

System must assign resource owner as requested.

* 4 Need to change because the scope of requirements varies depending on the reader

System should provide a mechanism to receive the request that is specified the following effect

   ・the effect at the transition

   ・the effect of output sound

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to judge priority of resources when there are two or more resources on same sound type on same zone.

* 4 Need to change because the scope of requirements varies depending on the reader

System should provide a mechanism to manage order of the owner request.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to issue the following resource control.

   ・Mute/Unmute

   ・Change zone

* 4 Need to change because the scope of requirements varies depending on the reader

System should provide a mechanism to set the following effect of the sound  to other system.

   ・the effect at the transition

   ・the effect of output sound

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to receive the owner request.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to issue the following resource control.

   ・Set the routing rule

System should provide a mechanism to set the following information.

   ・Application that has active surface

* 4 Need to change because the scope of requirements varies depending on the reader

System should notify the touch event from touch panel to user operating application.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to collect external conditions to be used by Policy Manager to decide proper system resource.

* 4 Need to change because the scope of requirements varies depending on the reader

This should be listed up in previous section

System must provide a mechanism to identify process's role.

* 4 Need to change because the scope of requirements varies depending on the reader

Policy Manager must detect current memory consumption periodically.

→The Policy Manager must monitor the state of hardware (CPU, Memory, Storage, network, etc.) in order to periodically determine whether the application can be operated.

* 4 Need to change because the scope of requirements varies depending on the reader

Policy Manager must detect current CPU consumption periodically.

→Integrated into the above.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to notify application status change to Policy Manager.

* 4 Need to change because the scope of requirements varies depending on the reader

System must provide a mechanism to kill process or process group forcibly.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall be able to handle resource requests for Audio Sinks(e.g. Cabin Speakers, Headphones)

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall be able to handle Source arbitration(Mix, WavPlayer instances, Tuners etc.)

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall be able to keep track of all the available resources.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall support stacking/queuing of resource requests.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall check for every requested resource against a pre-defined set of policies.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall use the system state as an additional input to make a decision.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall maintain priorities for all non-entertainment sources.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall maintain same priority for all entertainment sources.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall be responsible for reporting a broken resource status.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall be responsible for connecting/building a new source-sink connection using the underlying platform support.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall be request to mute the audio sink before an existing connection is removed/released.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall provide an interface to unmute the audio sink when a connection is re-established and the active source is ready to use the sink for audio routing.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall provide an interface to unmute an audio sink.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall inform the resource requestor when the sink is connected and ready to be used for audio routing.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management needs to inform the Resource Manager when they are ready to start audio routing.

* 4 Need to change because the scope of requirements varies depending on the reader

Resource Management shall maintain the system connection table at any point of time.

* 4 Need to change because the scope of requirements varies depending on the reader

The number of sinks supported by the system shall be configurable through LCF parameter.

* 4 Need to change because the scope of requirements varies depending on the reader