Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications. Although the initial target for AGL is In-Vehicle-Infotainment (IVI) systems, additional use cases such as instrument clusters and and telematics systems will eventually be supported. AGL has participants from the Automotive, Communications, and Semiconductor Industries and welcomes contributions from individual developers.

By leveraging the over $10B of investment made in the Linux kernel and other open source software projects, the AGL Workgroup:

• Enables rapid software innovation for automotive suppliers to keep up with the demand from consumers for better IVI experiences
• Utilizes the talents of thousands of open source software developers dedicated to maintaining the core software in areas like the Linux kernel, networking, and connectivity, used in systems across numerous industries

The goals of the Automotive Grade Linux Workgroup are to provide:

• An automotive-focused core Linux operating system stack that meets common and shared requirements of the automotive ecosystem with a broad community of support that includes individual developers, academic organizations and companies.
• A transparent, collaborative, and open environment for Automotive OEMs, Tier One suppliers, and their semiconductor and software vendors to create amazing in-vehicle software.
• A collective voice for working with other open source projects and developing new open source solutions.
• An embedded Linux distribution that enables rapid prototyping for developers new to Linux or teams with prior open source experience

This results in faster time to market by jump-starting product teams with reference applications running on multiple hardware platforms.

The scope of this document is to define the architecture of the Automotive Grade Linux software platform. The requirements are broken up into an overview of the Architecture and a description of each of the layers in the architecture followed by the requirements for each module in the various layers. The Architecture Diagram and the layout of the specification take into consideration all of the components that would be needed for an IVI system; however the are missing requirements for individual modules. As the spec continues to evolve those sections will continue to be filled in.

The main goal of this document is to define the core software platform from which applications can be built. As such, this document does not define application requirements except in a single case (Home Screen). Application requirements will be developed by various projects that use the AGL platform. Those application requirements can be used to drive new or revised requirements into the platform. 

At this time there is no plan to use this specification to create a compliance or certification program. The specification is used as blueprint to guide the overall work of AGL and to derive work packages for companies and individuals to complete in order to attain the goals of the AGL Workgroup. 

The Automotive Grade Linux Software Architecture diagram is below. The architecture consists of five layers. The App/HMI layer contains applications with their associated business logic and HMI. Generally applications are out of scope for this document since they are product specific for the OEM that is developing a system based on AGL.

The Application Framework layer provides the APIs for creating both managing and running applications on an AGL system. The Services layer contains user space services that all applications can access. The Operating System (OS) layer provides the Linux kernel and device drivers along with standard OS utilities.

Applications may use a web based framework or a native framework. A system may include applications that use different frameworks. Coordination of applications between frameworks is performed by the AGL App Framework. The diagram represents possible applications that could appear in a given system, but is not all inclusive. Reference applications may be provided by AGL to demonstrate the capabilities of the platform.

Home Screen provides the Home User Interface (Home UI) of the system which meets the following requirements:

• Rich User Experience (Rich UX)
• Driver Distraction mitigation
• Variations support

Rich UX covers requirements such as usability and user satisfaction. Driver Distraction mitigation covers requirements on display control and user operation behavior while vehicle is in motion to minimize driver distraction. Variations support covers requirements to support customization of design and behavior of the system to meet the different needs of vehicle type, destination and grade.

The following use cases are considered for Layout.

• Home Screen developer changes the Home UI by using a customizable layout definition.

The use case assumed about System UI Parts is as follows.

• An application or System uses status bar and on-screen in order to notify information to a user.
• User uses the system setting UI in order to change settings.
• User uses software keyboard in order to input characters.

The use case assumed about Application Management is as follows.

• A user downloads and installs or updates the delivery application from application store.
• A user uninstalls the delivery application.
• A user launches the installed delivery application or the pre-installed application.
• Also a user terminates those applications.

The use case assumed about Application Switch is as follows.

• User switches application via application history or application stack.
• The system switches application according to Driving Mode status.

Application switching by application history is assumed as follows.

• The system records the order of the applications in the order in which the application is displayed.
• The order of application that is recorded is updated each time the display of the application is switched.
• Screen of the application is displayed in the order in which they are recorded in the history at the time of switching applications.

・ Specification of operation

- User runs a swipe from the edge of the application screen area.

・ Specification of action

- The order of the screen is managed order management list (application history).

- List order update opportunity(Update has determined a display of the application)

- Application starts or stops.

- Allowed to stand between the screen N seconds after the swipe.

※"N seconds"：User defines the value of any.

- User to operate the screen after you swipe.

※"operation"：Screen tap. Menu display. Other.

Figure 5‑2 represents a sample Home Screen depicting the above mentioned use cases.

Application switching by application stack is assumed as follows.

• The user specifies the type of any order. The system records the order of the application to the rule as of the specified type.
• Examples of the types of any order
• Application start-up order
• Screen of the application is displayed in the order in which they are recorded in the stack when switching applications.

・ Specification of operation

• User runs a swipe from the edge of the application screen area.

・ Specification of action

• The order of the screen is managed order management list (application stack).
• List order update opportunity.(Application start-up order as an example)
• Application that started at the end of the list when the application is started is added.
• Application that has stopped from the list when the application is stopped will be deleted.

Figure 5-3 represents the switching example depicting the application of the above switching.

Table 5-1 describes the role of the Home Screen to satisfy the purpose and use cases mentioned above.

Table 5-2:  Relevance of the Role and Purpose

Home Screen must provide a mechanism for customizable GUI layout definition by each vehicle type, each destination and each grade.

Home Screen must provide a mechanism for a customizable GUI layout definition for different vehicle type, destination and grade.

GUI layout definitioncan be definedsuch as the following items:

(In addition, items that can be defined is not limited to the following.)

• screen resource (Display, Layer Type, Area)
• sound resource (Zone, Sound Type)
• input resource (Device, Event Type)
• UI Component to be used in the entire system
• transition effect (Animation effect)
• Background image

Home Screen must provide a mechanism to apply customized GUI layout definition.

Home Screen must provide a mechanism to display two or more information simultaneously to the status notification area.

Home Screen must provide a mechanism to displaying status to status notification area.

• Current Time: Displaying clock capability
• Icons of Status: Displaying icons for notify information from applications
• Status Message: Displaying text for notify information from applications
• Communication Status: Status of mobile communication and wireless communications (Wi-Fi, Bluetooth, etc.)

Home screen must provide an interface to retrieve information from application for notification.

Home Screen must provide a mechanism to show popup window into on-screen window.

Home Screen must provide GUI method to hide on-screen window by user operation.

Home Screen must provide a mechanism to hide on-screen window within a specified duration.

Home Screen must provide an interface for applications to request to show popups.

Home Screen must provide an interface for applications to cancel the previously requested popup.

Home Screen must provide a mechanism to show text information, draw images and show software switch like button in the on-screen window.

Home Screen must provide a mechanism to specify attributes such as position and size of On-screen window.

Home Screen must support a mechanism to specify other window display effect when the On-screen window is displayed. (e.g. tone down)

Home Screen must provide system setting menu regarding GUI, such as locale and network.

Home Screen must provide a mechanism to change current date and time setting.

Home Screen must provide a mechanism to change timezone setting.

• The platform must set up the date, time and timezone according to a current position automatically.
• Home Screen must provide a mechanism to set up turning on and off of the automatic date/time/timezone setup.

Home Screen must provide a mechanism to change language setting.

Home Screen must provide a mechanism to change wireless communications (Wi-Fi, Bluetooth, etc.) setting.

• Enable/Disable
• Connect/Disconnect
• Search the devices
• Display the list of available and/or registered devices

Home Screen must provide a mechanism to change mobile communication setting.

• Enable/Disable
• A setup and change of various attributes
• Display the list of registered devices and select device

HomeScreen must support to change the appearance of a screen to a user's liking.

These are as follows.

• Tone of a screen.
• Appearance of a window frame.
• Animation effect when screen transition was occurred.

Home Screen must support a mechanism to set or change master audio volume.

Home Screen must support a mechanism to set or change display brightness.

Home Screen must provide a mechanism to show software keyboard.

Home Screen must provide a mechanism to apply default settings (e.g. theme, local, wallpaper) to a new user, when a user is added by the User Manager.

Home Screen must provide a mechanism to manage downloaded application package.

• Display downloaded application list from application store.
• Download the application
• Install the downloaded application
• Uninstall the downloaded application
• Update the downloaded application

Home Screen must provide a mechanism to launch the application.

Home Screen must provide a mechanism to terminate the application.

Home Screen must provide a mechanism to show the list of installed applications.

Examples of assumed application list

• list of application name
• list of application’s icon
• list of live thumbnail for all the running applications

Home Screen must provide a mechanism for switching display application in order by application history.

Home Screen must provide a mechanism for the application stack in any order. For example, such as launch order or display order.

Home Screen must provide a mechanism for the system to switch applications.

For example, when Driving Mode changes, system must be able to switch application based on policy.

The Application Framework layer provides the methods needed to create software applications and their user interfaces. The platform can support multiple application frameworks any of which may be built into an SDK or product build. The application framework contains any code specifically written for that framework as well the bindings to the Services and Operating Systems layers that the application framework provides for its applications.

The AGL Application Framework provides basic services to all applications regardless of the framework they are implemented in so that there is a standard method providing the services.

Application Manager describes requirements for AGL application lifecycle function. Application lifecycle contains application installation/removal and launch/hide/resume/kill.

AGL System must support application lifecycle (install/uninstall, launch/kill, suspend/resume) based on appid/pid via launcher.

AGL System must support a database to store application metadata (appid, exec path etc.).

AGL System must provide an interface to get a list of installed applications.

AGL System must provide an interface to get the state of an application. 

AGL System must provide application privilege control. 

A window system is a software component that facilitates an implementation of graphical user interface. A window system is responsible for managing display devices, Graphics Processing Units (GPUs), input devices, and graphics memory. A window system works with the software component named window manager that is responsible for a layout management of windows, and a routing of user interactions.

A window manager is as software component that is responsible for a layout management of windows.

Window manager of automotive middleware layer makes up for traditional window management system to be satisfied IVI’s complex requirements, typically requested from Policy Manager. Also, AGL aims to provide well-portability among various hardware platforms. 

Please refer “screen resource control” of Policy Manger section.

Table 7-148 describes the role of window manager to be satisfied above purpose and use cases.

Table 7-16 : Role of Resource Control

System must provide a mechanism to manage surfaces, such as create, delete, make visible and make invisible.

System must provide a mechanism to create and delete surface.

When surface is created or deleted, system must notify status change to GUI resource.

This notification mechanism makes possible to assign surface to proper area by GUI resource.

System must provide a mechanism to change visibility per each surface.

And, provide an interface to change visibility.

All the surfaces must be set to invisible for initial state.

Surface will be visible only if GUI resource issues to change visibility.

System must provide a mechanism to move surface’s area. If area size was different between previous area and new one, then system must support to fit into new area by VIC.4.1.4.

System must provide a mechanism to fit surface into area. Because, size of area may different from size of surface.

If resize was happened, system must notify to surface’s owner application.

If size of surface and size of area was different, system must provide a mechanism to fit surface into area by squeeze.

If size of surface and size of area was different, system must provide a mechanism to fit surface into area by using combination of scaling and trimming function.

That means, system must provide a mechanism to fit surface into area keeping original aspect ratio. This makes it possible to fit by “pan & scan”.

If size of surface and size of area was different, system must provide a mechanism to fit surface into area by using combination of scaling and background color.

That means, system must provide a mechanism to fit surface into area keeping original aspect ratio. System also provides a mechanism to fill background color into redundant pixels. This mechanism makes it possible to do “letterbox” method.

System must provide a mechanism to create and delete a layer.

Layer must have a concept of z-order. That means, display order for each layer is decided by their z-order attribute.

Z-order attribute is fixed value. So, if application wants to change display order of surfaces, then, attached layer must be changed.

System must provide a mechanism to create and delete “area” to display surface.

Area is a concept which defines where to display in specific layer.

System must provide a mechanism to attach surface to any layer.

Also, system must be able to change attached layer.

And, provide an interface to attach and change.

System must provide a mechanism to assign surface to any area in a layer.

And, provide an interface to assign surface to any area.

System must provide a mechanism to change visibility per each layer.

That means all the surfaces belonging to same layer will be changed visible or invisible at the same time.

And, provide an interface to change visibility per layer.

Initial state must be set to invisible.

System must provide a mechanism to enable superimposed display based on z-order of each layer, and disposition of surfaces.

System must provide a mechanism to apply animation effect when visibility change was happened.

Per each animation, system must provide a mechanism to apply below attributes.

-       Duration

Animation type

System must provide typical animation effects, such as slide-in, slide-out, zoom-in and zoom-out.

Also, system must provide a mechanism to add, delete and change animation effect easily by plug-in architecture.

System must provide a mechanism to apply animation effect when move surface was happened.

Per each animation, system must provide a mechanism to apply below attributes.

• Duration

Animation type

System must provide typical animation effects, such as slide-in, slide-out, zoom-in and zoom-out.

Also, system must provide a mechanism to add, delete and change animation effect easily by plug-in architecture.

System must provide a mechanism to make effect to surface.

And, provide an interface to set effect type from application and other software components.

System must provide a mechanism to make specific surface to gray-out.

System must provide a mechanism to make specific surface to low brightness

System must provide a mechanism to add, delete and change effect for surface easily by plug-in architecture.

System must provide a mechanism to reduce frame rate independent from refresh interval of application.

System also provides a mechanism to set frame rate as 0fps, independent from refresh interval of application.

This function is useful to keep whole system quality even if high load status, such as live thumbnail and moving surface.

If hardware supports two or more hardware layers, system must provide a mechanism to use hardware layers efficiently.

• Never use software overlay when superimposing two or more hardware layers

Assign hardware layer for graphical high load function, such as video playback

Window Manager must be able to retrieve system structure regarding displays and layers of each display. And system must provide a mechanism to adapt any structure without re-build, such as by using re-configuration.

AGL specifies that automotive grade Linux shall manage multiple windows owned by multiple processes on a display.

AGL specifies that automotive grade Linux shall support multi-headed display.

AGL specifies that automotive grade Linux shall have a window manager that uses only public APIs provided by Window System and OpenGL/ES 2.0 for rendering and user interaction.

AGL specifies that automotive grade Linux shall have a window manager that relies on a standard rendering API such as OpenGL/ES 2.0 only. The window manager shall not rely on any hardware specific API.

A window system and OpenGL/ES 2.0 API are responsible for a hardware abstraction.

Policy Manager collects information and makes decisions based on them. To do that, Policy Manager collects lots of status, such as user operation and application status, then issue Vehicle Info Control or Resource Control to provide information. Policy Manager controls two types of resource, one is called “GUI resources” such as screen and sound, and other one is called “System resources” such as CPU and memory.

(1)  Definition

·  About Control of GUI Resources

AGL is supposed the following devices in this feature. For example, display with touch panel, speaker, and microphone. And AGL defines that “GUI resources” are resources that provide user or is provided by user on those devices, such as windows, sound streams and input events.

Figure 7-1:  GUI resources

Policy Manager controls GUI resources according to external conditions. For example, Policy Manager limits the information of GUI resources while the vehicle is driving, because, the too much information distracts the attention of driver from driving operations.

·  Associated Software Architecture

The software architecture of Policy Manager and related components regarding GUI resources control is as below.

Figure 7-2:  Associated Software Expected Use Case

Policy Manager is related with the below components.

Table 7-1: Related Components

(2)  Role

Policy Manager has the below role.

Table 7-2:  Role of Policy Manager

Figure 7-3:  Definition of Role

GUI resource classifies screen resource, sound resource and input resource. Details of each resource type are as follows:

a.  Screen Resource

a-1.  External Condition Collection

Policy Manager collects the below definition that is related with screen resource.

Figure 7-4:  Definition of screen resource

• Concept of Display, Layer, Layout and Area

AGL supports not only one physical display but also two or more displays. Each display has one or more layer. And each layer must be connected to one layout defined by Homescreen. Layout consists of one or more areas. “Area” is graphics composed area to display specific graphics window.

The z-order of layers is flexible. Policy Manager decides the z-order of each layer depending on objectives of them. For example, layer-1 was used as “phone call notification”, and layer-2 was used as displaying “map”, then Policy Manager will decide that layer-1 should be upper than layer-2.

Layer is created by application including Homescreen. When application creates layer, application specifies layer type. Layer type is roughly categorized as “Basic” and “Interrupt”. “Basic” layers are used to display application itself such as media playback, map drawing and setting menu. “Interrupt” layers are used to display overlay windows such as information alert and enlarged view.

When application creates layer with ”Basic” type, application must specify layout type for it. On the other hand, the case layer with “Interrupt”, application must specify corresponding “Basic” layer. The layout of “Interrupt” layer is followed by “Basic” layer’s layout.

From the capability of Policy Manager point of view, the main purpose of layer is to decide z-order. In other words, if there is a scenario to change z-order of two or more windows triggered by system status change and/or user operation, then such kind of window must assign to individual layer.

• Concept of Layer Owner, Role and Surface

“Layer owner” is application which created that layer. “Layer owner” can request each area of that layer. When “Layer owner” requests specific area, “Layer owner” also specify “Role” of area. “Role” represents how to be used that area, and used to define z-order of layers by Policy Manager.

“Layer owner” also can request to change “Role” for specific area, however, whether “Role” change is acceptable or not is decided by Policy Manager by using policy rule.

One area should connect to one graphics window. AGL defines the term “Surface” as graphics window to display into one area.

Surface is a canvas to draw graphical image by application. To show via physical display, surface drawn by application must be assigned to specific area. Figure 7-16 describes simplest example to assign one surface to full screen with one layer. If layer has two or more areas, then corresponding surfaces are mapped to each area. According to example of Figure 7-16, surface is fit to area size as “squeeze”, however AGL also provide a way to fit as “letterbox” and “pan & scan”.

Figure 7-5:  Definition of Surface

• Subdivision of “Interrupt” Layer

Basically, “Basic” layer corresponding to “Interrupt” layer is used to display application’s main surface. However there are some exceptions. For example virtual keyboard is not needed main surface. However, to follow this layer type rule, virtual keyboard must have corresponding “Basic” layer. But this “Basic” layer never used to display. Also on-screen, such as alert message is not needed main surface too. But it must have corresponding “Basic” layer from same reason.

According to above concept and some exceptions, AGL defines four layer types described as Table 7-3.

Table 7-3:  Definition of Layer Type

a-2. Judgment of Priority of GUI Resource

Policy Manager receives the request with “Role” that is related with each screen resource. Role is the category name of screen resource priority. Role is used to judgment of priority by Policy Manager. Table 7-4 and Figure 7-6 describes the definition of role and sub role.

Table 7-4: Definition of Role

Role consists of role and sub role. Role is screen owner role such as “Navigation” and “Software keyboard”. Sub role defines when layer type of the screen resource is not “Basic”. Sub role is popup screen role such as “Enlarged view” (of Navigation).

Figure 7-6:  Definition of Role and Sub role

The screen resources are sorted of priority that is related to role by Policy Manager. If display has two or more layers, then all layers will be superimposed by z-order.

In addition, Policy Manager decides the area of "Interrupt" layer using role. Area of "Interrupt" layer must be same area of the related "Basic" layer. "related" means that "Role" (is not "Sub role") of "Basic" and "Interrupt" is same. For examples, if "Interrupt" layer is set “Navigation” role and “Lane guidance” sub role, this is set in same area of "Navigation" role.

a-3. GUI resource control

Policy Manager controls the screen resources using Vehicle Info Control. Policy Manager only issues to control the screen resources but it is actually controlled by Vehicle Info Control directly.

There are three types of screen resource control:

One is allocation of each surface such as position, size and size-fitting method.

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

b.  Sound Resource

b-1.  External Condition Collection

Policy Manager receives the below definition that is related with sound resource.

Figure 7-7:  Definition of Sound Resource

• Zone

Zone is a place in the car, such as driver zone, passenger zone, rear seat zone. Each zone can play at the same time.

• Sound type

Sound type is the category of sound resource. Sound type must be set by each sound resource owner such as application. If application wants to play sound, it must be assigned to proper sound type of proper zone. Only one sound stream can occupy specific sound type of specific zone. In other words, if two or more sound streams should be mixed in same zone, then each sound stream must assign to individual sound type.

AGL supports the following sound type, however it’s just sample and should be configurable.

Table 7-5:  Definition of sound type

• Stream

Stream is connection of sound resource that is made in applications. Sound is transferred in stream.

b-2. Judgment of Priority of GUI resource

Policy Manager receives the request with “Role” that is related with each sound resource. Role is the category name of sound resource. Role is used to judgment of priority by Policy Manager. Figure 7-8 describes the definition of role.

Figure 7-8:  Sample Role 

The sound resources in the same zone and same sound type are switched along the priority that is related to role by Policy Manager. In other words, the sound resources of different zones or different sound type are not switched. They are mixed.

b-3. GUI Resource Control

Policy Manager controls the sound resources using Vehicle Info Control. Policy Manager only issues to control the sound resources but it is actually controlled by Vehicle Info Control directly.

There are two types of sound resource control:

One is playback control such as play, pause and stop. Policy Manger 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. In this case, Policy Manager specifies volume parameter for each sound stream. For example, if route guidance and music playback are mixed, assign higher volume to route guidance and volume down for music playback.

c.  Input Resource

c-1. External Condition Collection

Policy Manager receives the below definition that is related with input resource.

Figure 7-9:  Definition of Input Resource

• Device Name

Device name is identity of input device such as steering SW and microphone.

• Event Type

Event type is logical group of input event from each input device such as volumes and temperatures.

c-2. Judgment of Priority of GUI resource

If application wants to be notified input event, it must request input event notice with device name and event type. The request is judged whether to notify by Policy Manager using policy DB. And Vehicle Info Control notifies input event to applications along the result of the judgment as below.

Figure 7-10:  Definition of routing rule

OEM special switch means product variant configuration in Figure 7-10.

c-3. GUI Resource Control

Policy Manager controls the input resources using Vehicle Info Control. Policy Manager only issues to control the input resources but it is actually controlled by Vehicle Info Control directly.

Input resource control is to specify event target to Vehicle Info Control.

(1)  Definition

Policy Manager controls System resources according to external conditions. For example, Policy Manager limits memory usage of background applications when memory shortage was occurred.

Policy Manager controls System resources by using “Resource Control” of kernel layer. So, target resources are CPU, memory, storage bandwidth and network bandwidth.

a.  Role

(1)  External Condition Collection

System must provide a mechanism to receive the definition that is used judgment of resource owner.

System must provide a mechanism to receive the physical display information. Because system uses physical display information with to control surface to other system. The receive information must include as follows.

a. ID

 b. Display resolution (Vertical and horizontal number of pixels)

 c. DPI

d. Connected ECU

System must provide a mechanism to receive the layout definition. Layout definition must be able to identify the all areas of display. As a result, system recognizes the available area list according to current layout of each display.

The receive definition must include the follows.

a. ID

 b. Area list

System must provide a mechanism to receive the area definition. Area is set application surface by system if the request is accepted by system. As a result, application surface displays on the device.

The receive request must include the follows.

a. Layout ID

b. ID

 c. Area position (Coordinate of the upper-left)

 d. Area size (Length * Width)

System must provide a mechanism to receive the layout type of each display. System can specify the available areas if layout type is defined. The receive information must include the follows.

a. Display ID

 b. Layout ID

System must provide a mechanism to receive the priority rule. Because system must judge the providing resource using it when the request is collision.

The receive information must include the follows.

a. Role

 b. Priority

System must provide a mechanism to receive the vehicle status. Because system must judge driving mode.

The receive information must include the follows.

a. Velocity

 b. Brake status

System should provide a mechanism to receive the vehicle status. Because system should judge day night mode.

The receive information should include the follows.

a. The brightness of the interior

System should provide a mechanism to receive the user status. Because system should judge the providing resource using it.

System should provide a mechanism to receive the infrastructure status. Because system should judge the providing resource using it.

(2)  Judgment of Priority of GUI Resource

System must provide a mechanism to assign resource owner to the requested resource according to external condition. This means that system judges the providing resource.

System must provide a mechanism to receive the layer request. System allocates the physical resource. Application must request the area on this layer if application needs to display the resource.

The receive request must include as follows.

a. Role

 b. Layer type

The receive request should include as follows.

c. Display ID

System must provide a mechanism to receive the area request. System sorts layers in order by priority that is related with the specified role. Then system displays the application surface on the specified area on the specified layer. 

The receive request must include as follows.

a. Role

b. Layer ID

The receive request must include as follows when layer type of the specified layer is “Basic”. Because there is a specification that the area on layer except basic type must be located on the related basic type area.

c. Area ID

Figure 7-11:  Sequence to display

System should provide an interface to request both screen and sound resource simultaneously. In this request, requester should choose below options.

• Requester needs both screen and sound. For example, if screen resource was available, but sound resource was occupied by other owner of higher priority, then, request should be refused.
• Requester wants screen and sound resource as much as possible. For example, if screen resource was available, but sound resource was occupied by other owner of higher priority, then, only screen resource should be assigned to requester.

System should provide a mechanism to receive the request of forcibly acquire and forcibly release. System should be able to forcibly acquire and forcibly release request during system running. System should raise the requested surface to the top of the display.

The receive request should include the follows in addition to the information of the normal request.

a. Effective period (Can set unlimited)

System should not raise the other surface above its during effective period. 

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

a. The effect at the transition

 b. The effect of display surface

System must provide a mechanism to judge priority of resources. The screen resources are sorted of priority that is related to role by system. If display has two or more layers, then all layers will be superimposed by z-order.

System must provide a mechanism to judge visible surfaces according to vehicle running state. System must hide the surface that has too much information.

(3)  GUI Resource Control

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

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

 a. Visible / Invisible

 b. Change position

 c. Raise

The receive request must include as follows.

i. Surface ID *Only case of visible.

ii. Display ID *Only case of visible.

iii. Layer ID *Only case of visible.

 iv. Position (Coordinate of the upper-left) *Only case of visible and change position.

 v. Size (Length * Width) *Only case of visible.

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

 a. The effect at the transition

 b. The effect of display surface

(1)  External Condition Collection

System must provide a mechanism to receive the definition that is used judgment of resource owner.

System must provide a mechanism to receive the zone definition. Because system uses zone information with to control stream to other system. The receive information must include as follows.

a. ID

 b. Sound device ID

System must provide a mechanism to receive the sound type definition. Because system uses sound type information with to control stream to other system. The receive information must include as follows.

a. ID

(2)  Judgment of Priority of GUI resource

System must provide a mechanism to assign resource owner to the requested resource according to external condition. This means that system judges the providing resource.

System must provide a mechanism to receive the owner request. System must be able to receive request during system running.

The receive request must include as follows.

a. Role

b. Zone ID

c. Sound type ID

System should provide a mechanism to receive the request of forcibly acquire and forcibly release. System should be able to forcibly acquire and forcibly release receive request during system running.

The receive request should include as follows in addition to the information of the normal request.

a. Effective period (Can set unlimited)

System must assign resource owner as requested. And system must not assign resource owner by other request on same area during effective period.

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

a. The effect at the transition 

 b. The effect of output sound

System must provide a mechanism to judge priority of resources when there are two or more resources on same sound type on same zone. System judges the providing resource by priority of resources that is related to role.

* Boundary of the role between Policy Manager and application.

Figure 7-12:  Boundary of role (Case of reverse)

System should provide a mechanism to manage order of the owner request. Because system should provide a mechanism to hold the request until the request is approved.

For example, if current playing interrupt sound completed, select the next play interrupt sound from request history based on the priority.

(3)  GUI Resource Control

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

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

 a. Mute / Unmute

 b. Change zone

The receive request must include as follows.

i. Stream ID

ii. Device

In the case of multi-channel speaker, the receive request should include as follows.

iii. Channel ID

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

 a. The effect at the transition 

b. The effect of output sound 

(1)  External Condition Collection

System must provide a mechanism to receive the definition that is used judgment of resource owner.

System must provide a mechanism to receive the input device information. Because system uses input device information with to control input event to other system. The receive information must include as follows.

a. ID

System must provide a mechanism to receive the event type definition. Because system uses input device definition with to control input event to other system. The receive definition must include as follows.

a. ID

b. Related event IDs

(2)  Judgment of Priority of GUI resource

System must provide a mechanism to assign resource owner to the requested resource according to external condition. This means that system judges the providing resource.

System must provide a mechanism to receive the owner request. System must be able to receive request during system running.

The receive request must include as follows.

a. Input device ID

b. Event type ID

System should provide a mechanism to judge whether to accept request according to the limitation routing rule of policy DB.

(3)  GUI Resource Control

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

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

 a. Set the routing rule

The receive request must include as follows.

i. Input device ID

ii. Event type ID

The receive request must include either as follows.

iii. The allowed application

iv. The denied application

System should provide a mechanism to set the following information.

 a. Application that has active surface

System should notify the touch event from touch panel to user operating application. This feature is needed because there may be case that privilege application such as Homescreen changes the active surface.

(1)  External Condition Collection

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

Policy Manager must detect creation and deletion of process.

To detect creation of process, Policy Manager can assign proper system resource to created process.

Also, to detect deletion of process, Policy Manager can assign resources of deleted process to other active processes.

To assign proper system resource to specific process, system must provide a mechanism to identify process’s role. In other words, Policy Manager must recognize the purpose of each active process.

Policy Manager must detect current memory consumption periodically.

To detect current memory consumption, Policy Manager can control maximum memory to each process to prevent memory shortage. Also, Policy Manager may kill processes which were thought as not so important process.

Policy Manager must detect current CPU consumption periodically.

To detect current CPU consumption, Policy Manager can control priority to each process to keep system performance. Also, Policy Manager may kill processes which seem to be in unexpected busy state.

System must provide a mechanism to notify application status change to Policy Manager. Application status includes as below.

• GUI resource status, such as foreground or background.
• Resuming last status or not. When system starts up or log-in user changes, system must resume last status. In this case, Policy Manager should assign much resource to last application to resume quickly as much as possible.

(2)  System Resource Control

System must provide a mechanism to change assigned system resource per process or process group according to external conditions.

According to policy based decision, Policy Manager must assign proper system resource to target process or process group by using “Resource Control” of kernel layer. (typically cgroups will be used)

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

Resource Management shall consist of three functional components - Resource Manager, Policy Manager, Connection Manager.

Resource Management shall provide CORBA interfaces to rest of the components in the system.

Each resource request shall be in form a:

AppID,

SourceID,

RequestorZoneID,

NeedAll Flag (to specify if all the resources need to be allocated ),

Required Resource List.

Resource Management shall be able to handle resource requests for Audio Sinks (eg: Cabin Speakers, HeadPhones)

Resource Management shall be able to handle resource requests for Video Sinks (eg: Display)

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

Resource Management shall be able to validate all the input parameters for a resource request from resource requestors.

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

Use CCF data to identify all the resources that are possible in the system. (static identification)

Use dynamic registration by the resource owners to identify what resources out of the above list are available at a point of time in the system. (dynamic identification)

Resource Management shall inform about resource availability and unavailability in the system through status update.

Resource Management shall support stacking/queuing of resource requests.

> Receive the requests from the resource requestors.

> Handle each request in chronological order and check for policy validation through Policy Manager.

> Add the validated requests into a priority queue.

> Process each request from the top of the queue for establishing the connection.

> If a request is still in the pending queue and the requestor requests to withdraw the request, it shall be removed from the queue.

Each request for resource shall be handled as an independent request irrespective of any earlier request by the same requestor. In case of multiple resources requested in a single request, it shall be treated as a single request and will be processed based on the request parameters.

If the NeedAll flag is set by the requestor, it shall either grant all the requested resources to the requestor or none of them shall be granted. There shall be no partial allocation of resources.

If the NeedAll flag is not set, it shall be able to do partial allocation of resources i.e. grant some/all of the resources requested by the requestor.

Resource Management shall provide an interface to a request owner to remove/withdraw an existing resource request.

Resource Management shall check for every requested resource against a pre-defined set of policies if the request can be served at this point of time or not. Below is a list of possible inputs for the policy decision:

> Currently Free or InUse Sink status

> Who is the resource owner of the currently used sink resource (if it is in use)

> Priority of the new requestor compared to the currently using requestor.

Resource Management shall use the system state as an additional input to make a decision if a request can currently be serviced or not. Below system states can be taken as input to the policy decision:

> Based on the speed restriction setting for a specific region, a request can be granted/kept pending.

> Low Power Mode, Eco Mode, System errors shall also be used to make policy decisions.

At any point of time it shall maintain the following information for each ZONE for use by resource requestor:

> Zone ID

> Allocated Source Instance

> Allocated Sink Instance

> Mute status

Resource Management shall not consider requirements to achieve a specific feature functionality (e.g. : Lowering audio volume of rest of the sinks when a phone call is in progress) as an input to the resource management policy.

Resource Management shall not provide support for requirements to achieve a specific feature functionality (e.g.: Pausing a pausable source when phone call is in progress).

Resource Management shall maintain priorities for all non-entertainment sources (eg: AMFM_TA, PHONE_NORMAL, NAV_VG, etc. shall all have priorities). In case two sources have same priority, the first requestor shall be granted a resource. In case of difference in priorities, the highest priority resource request shall be the one that is granted the resource.

Resource Management shall maintain same priority for all entertainment sources (eg: MP, DVD, AMFM_NORMAL, etc. shall all have the same priority). The last received Entertainment resource request will be the one that is granted the resource.

A valid (parameter and policy validated) resource request shall never be denied to the requestor. It shall either be granted or kept as a pending request in the priority queue.

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

It shall be the responsibility of the resource requestor to remove the request from Resource Manager if the resource is no longer needed.

Resource Management shall assign a sink instance (the specific instance allocated out of all available instances of the requested sink type for a particular zone) to a resource request, once the request is granted against the set policy.

Resource Management shall maintain connection state of an already granted connection. Possible connection states are Active or Passive.

> When a source has the primary (master) control over a sink, the connection state will be active.

Ex: In normal mode, a driver requesting for AMFM source to Driver HeadPhone Sink connection.

> When a source has the secondary (slave) control over a sink, the connection state will be passive.

Ex: Driver using the AMFM source, at the same time the rear passenger requesting for same AMFM source on Rear headphone sink.

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

Resource Management shall be responsible for removing/releasing an existing source-sink connection using the underlying platform support.

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

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.

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

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

Resource requestor needs to inform the Resource Manager when they are ready to start audio routing. This information shall be used to unmute the allocated sink.

Resource Management shall maintain the system connection table at any point of time. Connection table contains information regarding which sink is currently allocated to which source instance.

Resource Management shall support handling of change in behaviour based on Limo setting:

> Share the source between the Rear Seat headphone (Limo mode owner) and Cabin Speakers.

System shall support 4 ForegroundBeep sinks and 2 ForegroundSpeech sinks. 2 additional sinks are reserved for Engine noise synthesis which is outside the scope of this document. Additionally 1 FG speech sink and 1 FG beep sink is reserved for future use by ISC.

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

Headphones shall not be required to support any foreground sinks.

In case of Foreground sources and Tuner interrupt sources, any sink that is taken away from a source because of a high-priority interruption, need to be returned back to the previous source (if the request from the previous source is still valid and it's the next highest priority request).

As part of requirement to improve connection handling efficiency, it shall have exceptions to not disconnect the active connection while switching between any Tuner Source-Sink Background connection to another Tuner Interrupt Source with same sink connection.

It shall inform Resource Manager about a errors/failure in any of the existing sinks.

It shall inform Resource Manager about a errors/failure in any of the existing sources.

It shall provide the error state information about all resources to the Platform Error State Manager.

It shall inform the resource requestors in case the request is for an erroneous or faulty sink.

It shall wait for the application manager to notify it to prepare for shutdown.

It shall interact with the data storage manager to access (read and write) persistence data.

It shall interact with the data storage manager to access CCF data.

It shall support rules/exceptions (Blacklist) that define resource allocation strategy based on current system scenario.

E.g.: If there is a blacklist rule that says a Speech session shall not be allowed while phone call is in progress, then even if a FG sink is available, Speech shall be denied resources and kept as a pending request.

It shall provide an interface to receive Limo mode setting status.

It shall provide an interface to receive status when a rear-user selects to take Cabin control.

It shall use interfaces of early app to receive information if it's already using Audio/Video resources and update its internal status accordingly.

On any change in input to the Policy Manager (system state) it shall reevaluate all active connections and reconnect or disconnect if required.

E.g. An Amp gets disconnected, then all active connects have to be disconnected.

Once the Amp gets reconnected, the connection info shall be reevaluated and final set of connections shall be rebuilt with Amp.

It shall provide CORBA interfaces to the Resource Manager.

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

It shall be responsible for removing/releasing an existing source-sink connection using the underlying platform support.

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

It shall provide an interface to unmute an audio sink.

System shall support 4 ForegroundBeep sinks and 2 ForegroundSpeech sinks. 2 additional sinks are reserved for Engine noise synthesis which is outside the scope of this document. Additionally 1 FG speech sink and 1 FG beep sink is reserved for future use by ISC.

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

It shall inform Resource Manager about a errors/failure in any of the existing sinks.

Headphones shall not be required to support any foreground sinks.

It shall wait for the application manager to notify it to prepare for shutdown.

It shall interact with the data storage manager to access (read and write) persistence data.

It shall interact with the data storage manager to access CCF data.

A sound manager is a mechanism in which a sound output demand in two or more zones from two or more applications is arbitrated, an audio server manages control of a sound output and a policy manager manages a mediation rule.

A zone is a place in the car divided by the purpose of output power of sound like a driver zone, a passenger zone, and a rear seat zone. Each zone can play at the same time. Refer to "Sound resource" of "7.1.1.2 (2) Role" of "7.1 Policy Manager" for the details of a zone.

Applications that play and capture audio via the audio server, applications that control things like volume and routing via the audio server, and a policy manager that works with the audio server to implement automatic audio policies.

Please refer “sound resource control” of Policy Manger section.

Table 7-14 describes the role of sound manager to be satisfied above purpose and use cases.

Table 7-15 : Role of Resource Control

System must provide a mechanism to manage sound “zone”.

Refer to "(2) Sound resource" of "7.3.1.2.2 Role" of "7.3 Policy Manager" for the details of a zone and how to manage zone.

System must provide a mechanism to manage one or more connected sound devices, and each channels of each sound device.

One or more sound devices are usually connected to a system, and each sound device consists of one or more channels. And each channel outputs the sound of a monophonic recording.

For example, as for a stereo sound, a speaker is connected to each of two channels, and it is arranged at the driver side of a car, and the passenger seat side. If a telephone call is got when outputting stereo music from both of speakers, only the channel of a driver side needs to lower musical volume, and needs to mix and output the sound of a telephone (to louder sound than music). For this reason, the system needs to recognize and control each channel of each sound device.

The system must determine the route which outputs two or more sound streams to two or more zones.

Although the output place zone of a sound stream may change dynamically according to the present state of vehicles and a policy manager makes the decision, sound manager requires the mechanism in which a route is smoothly changed based on the determination of policy manager.

System must provide a mechanism to manage two or more sound zone as grouped zone.

System must provide a mechanism to do volume control for specific zone.

All the sound outputted to a certain zone is adjusted by the volume of the zone.

System must provide a mechanism to control sound stream.

Control of a sound stream is as follows.

• Mute/unmute: System must provide a mechanism to do mute or unmute to any sound stream.
• Suspend/resume: System must provide a mechanism to suspend or resume to any sound stream.

Volume control: System must provide a mechanism to change volume to any sound stream.

The system must offer the mechanism for arbitrating two or more sound streams outputted to the same zone according to a policy manager's arbitration.

System must provide a mechanism to do mixing after volume control of each sound streams.

System must provide a mechanism to attenuate sound volume when other sound stream requested to play into same sound zone.

In this case, system must also provide a mechanism to return to the volume before attenuating the volume of a sound stream when interrupted sound stream was ended.

System must provide a mechanism to mute sound volume when other sound stream requested to play into same sound zone.

In this case, system must also provide a mechanism to unmute sound volume when interrupted sound stream was ended.

System must provide a mechanism to suspend sound stream playback when other sound stream requested to play into same sound zone.

In this case, system must also provide a mechanism to resume playback when interrupted sound stream was ended.

When sound stream was changed, system must provide a mechanism to do sound effect.

System must provide typical sound effect such as fade in and fade out.

System must provide a mechanism to add, replace and delete sound effect easily by using plugin architecture.

Sound Manager must be able to retrieve system structure regarding sound device and channels of each device. And the system must enable addition/deletion of a sound device by the means which does not need rebuild of systems, such as a configuration.

The Input Manager provides a capability to deliver input events to the proper application depending on request from Policy Manager. Policy Manager will decide event target per each input area. Also, the IVI system may use various car-oriented input devices such as steering switch. Input manager provides a capability to abstract such kind of input event.

Please refer “input resource control” of Policy Manger section.

By the way, associated input devices are listed below.

Table 7-14 describes the role of input manager to be satisfied above purpose and use cases.

Table 7-14 : Role of Resource Control

System must provide a mechanism to re-configuration regarding input devices without re-build.

Because, connected input devices may different by car grade, car type, destination and optional equipment.

System must provide a mechanism to deliver any input event to any application.

System must provide an interface to apply event delivery rule by using attribute pair “device id” and “destination application id”.

Device id specifies a logical device name. Logical device name will link to physical device by UIM.2.1.2.

Also, system must provide a mechanism to change event delivery rule dynamically.

System must provide a mechanism to link between logical device name and physical device.

System must provide a mechanism to deliver any input event to any application depending on delivery rule defined in UIM.2.1.1.

System must provide a mechanism to inhibit any event delivery.

This function makes it possible to restrict input event during driving mode.

User manager provides multi-user environment. A car may be used by two or more people, and a person may use two or more cars, by using rent-a-car, for example.

Multi-user environment provides same user experience for each user.

Also, multi-user aims seamless personal data sharing not only between cars but also including other devices such as smartphones and smart TVs. Furthermore, it will include seamless data sharing from your home and your office.

Identify the person, and log-in to the IVI system as a specified user. Personal identify may be provided by traditional user name and password pair, smart key or biometrics.

Once a user has logged-in to IVI system, IVI system should provide personalized user experience. For example, Bob uses English, but Alice uses French. Also, Bob likes rock-music, but Alice likes classic-music. In this case, English and rock-music should be selected when Bob is logged-in, and Japanese and classic-music should be selected when Alice is logged-in.

Figure 7-24 : Provide Logged-in User’s UE (User Experience)

When Bob uses a rent-a-car, same preference should be adapted as if he rode his own car. If Bob’s preference was stored in a cloud, then this can be supported. However, security is important in this scenario. For example, Bob must not be able to access to other user’s preference.

Figure 7-25 : User data sharing between cars

Cloud-based user data syncing will enable seamless data sharing between IVI systems and smart-phones, home networks and accessing from your offices.

Figure 7-26 : User data sharing over the cars

Error! Reference source not found. describes the role of the User Manager to satisfy the above purpose and use cases.

Table 7-17 : Role of User Manager

System must provide a mechanism to identify logged-in user.

System must provide a mechanism to enter user name and password, and verify password to identify logged-in user.

System should provide a mechanism to read smart key attribute to identify logged-in user. For example, using NFC.

System should provide a mechanism to identify logged-in user by using biometrics.

When a logged-in user is identified, system must apply user preference depending on the currently logged-in user.

System must provide a mechanism to apply personalized user experience as follows.

-       Locale settings

-       UX theme

Wall paper

System must provide an easy mechanism to add plugin function and/or attribute of personalized user experience.

System must provide a mechanism to switch application data per user, and apply logged-in user’s application data automatically.

When user is identified and logged-in, the system must apply last status of logged-in user. Last status refers to the status of the system as the current logged-in user has last logged-out of the system. Specifically, last status includes the following.

-       Foreground applications. That means displayed applications.

Background applications.

When user logs in for the first time, the system must apply user preference for new log-in user.

System must provide a mechanism to apply default preference attributes for new log-in user.

System must provide default preference attributes and HMI to apply for first time log-in user.

System must provide a mechanism to manage user data.

AGL defines “user data” as a general term which includes all the data necessary to realize user preference.

User data shall be stored in the cloud. The cloud provides user data not only to IVI systems but also other systems and/or devices such as smartphones, Home-PCs, business-PCs, HEMS and home electronics.

System must provide a mechanism to apply user preference and to supply user data to application by using cloud based user data.

System must provide a mechanism to download cloud based user data and apply it as user data of the IVI system.

When user data is updated in the IVI system, then the system must upload updated user data to the cloud.

Also, since other device or system may update shared user data elsewhere, system must provide a mechanism to sync with the cloud periodically to keep user data in the IVI system up-to-date.

Because the IVI system is not necessarily connected to a network, the system must provide a mechanism to cache downloaded user data.

If the IVI system re-connected to a network, system must sync with the cloud as soon as possible.

Because user data may include personal information, system must provide a mechanism to protect user data from risks including but not limited to leakage, tampering and theft.

System must provide a mechanism to protect user data when accessing to the cloud.

-       System must authenticate communication entity. In other words, IVI system must authenticate cloud server, and cloud server must authenticate client such as IVI system, smartphone or PC.

-       System must provide a mechanism to encrypt transported data via a network.

-       System must provide a mechanism to transport data via a network with protection against falsification of data from unauthorized access or illegal access.

-       Cloud server must provide a mechanism to authenticate individual user, and provide user data only to the authorized user.

Because, two or more user’s user data may be stored in IVI system as a cache, system must provide a mechanism to protect cache data from other users. The protection of cached data to include not only the current multi-user environment risk, but also the risk of attacks against cached data. In other words, only logged-in user’s cache data can be accessed.

Web based HMI. Contains applications, web runtime environment, and web-based home screen.

It is discussed that HMI parts of IVI system will be developed using HTML5. APIs to use service function in IVI system from web applications is needed. Audio Visual API provides APIs for audio visual equipment control to web applications. (e.g. Media files on storage, CD, DVD, BT-Audio, Photo, etc.)

Web applications use Audio Visual API to play audio visual contents on IVI system. Use case of Audio Visual API is shown in Figure 6-1.

Figure 6-1:  Use case of Audio Visual API

Audio Visual API must provide API to select Audio Visual contents.

• Select content using URL
• Select content using contents list provided by multimedia subsystem

Audio Visual API must provide API to playback Audio Visual contents. (Media file on storage, CD, DVD, BT-Audio, Photo, etc.)

• Play
• Pause
• Fast-forward
• Rewind
• Track up
• Track down
• Select playmode (Repeat/Random)

Audio Visual API must provide API to control a volume.

• Volume up
• Volume down
• Mute

Audio Visual API must provide API for metadata access about Audio Visual contents.

Audio Visual API must provide API for notifications.

• The case that playback state is changed
• The case that Audio Visual contents is add / removed

Audio Visual API must provide API to play AM/FM radio.

• Change the frequency.
• Change the broadcasting stations.
• Receive the list of broadcasting stations.
• Select the preset channel.
• Get the information of the broadcasting station.

Audio Visual API must provide API to play digital radio.

• Store the broadcast program information.
• Get the broadcast program information.
• Get the play time.
• Play the radio broadcast cached.

AGL System must support a web API to access Vehicle information.

AGL System must support web API to control STT/TTS daemon.

AGL System must support web API to control navi engine.

AGL System needs to provide a Web API to allow peer to peer communication between two web apps.

AGL System needs to provide an API to allow peer to peer communication between a web app and a native app.

AGL System must support access control over app to app communications. Service provider should be able to restrict subscriber.

AGL System must support W3C/HTML5 DOM, Forms and Styles.

AGL System must support W3C/HTML5 Device APIs: Touch Events, Device Orientation, Network Information

AGL System must support W3C/HTML5 Graphics APIs: canvas, canvas 2D context, and SVG

AGL System must support W3C/HTML5 Media: audio and video tags, user media and  web audio

AGL System must support W3C/HTML5 Communication APIs: websocket, web messaging, server sent events, session history of browsing context

AGL System must support W3C/HTML5 Storage APIs: Web storage, File, Database, Web SQL

AGL System must support W3C/HTML5 Security APIs: Cross-Origin Resource Sharing, HTML5 The iframe element, Content Security Policy 1.0.

AGL System must support W3C/HTML5 UI APIs: Clipboard, DnD, Web Notifications

AGL System must support W3C/HTML5 Performance APIs: Web workers, Page Visibility, Timing control, Navigation timing

AGL System must support W3C/HTML5 Location API: Geolocation

AGL System must support W3C/HTML5 Widget: Widget Packaging and XML Configuration, Widget Interface, XML Digital Signatures for Widgets, Widget Access Request Policy

AGL System must support Khronos WebGL API.

The Web Runtime module contains the bindings for the Web Application Framework to access the AGL Application Framework and Services.

AGL system Web Runtime shall provide full web application lifecycle management (e.g., installation/removal).

AGL System Web Runtime shall provide full execution environment for web apps (i.e., launch, view generation, rendering, etc.)

AGL system Web Runtime shall provide a mechanism to implement plugins/extensions to add better device/platform integration.

AGL system Web Runtime shall provide a mechanism to manage apps' access control and also to categorize apps with different privileges.

System must provide high level GUI components for Web application.

At least, below components are required.

• Text labels
• Button
• Radio button
• Check box
• Tab panel
• Animation (e.g. MNG, GIF animation)
• Slider
• Accordion list
• Anchor
• Text input form
• Dropdown list box
• Date picker

The Native HMI provides an application framework for those applications that are not written using Javascript or other web  technologies.

The Native Runtime module contains the bindings for the Native Application Framework to access the AGL Application Framework and Services.

System must provide high level GUI components for native application.

At least, below components are required.

• Text labels
• Button
• Radio button
• Check box
• Tab panel
• Animation (e.g. MNG, GIF animation)
• Slider
• Accordion list
• Anchor
• Text input form
• Dropdown list box
• Date picker

The platform can support multiple application frameworks any of which may be built into an SDK or product build. The application framework contains any code specifically written for that framework as well the bindings to the Services and Operating Systems layers that the application framework provides for its applications.  

The Services Layer contains user space services that all applications can access. Generally the services provide either an IPC type interface or a subroutine/ function API. These interfaces remain the same for a given implementation and it is up to the Application Framework Runtime modules to provide access to these interfaces to the applications. Since we are trying to avoid unnecessary interface shims, it is not necessary for AGL to define standard service layer interfaces for a given module. Unless otherwise specified the API depends upon the interfaces provided by the open source packages chosen for a module. Different implementations may choose different packages for a given function and it is left to the Application Framework runtime to adjust to any new interfaces,

Platform Services Layer. Conventional Linux platform services

This document describes requirements regarding registration, (dis)connection and device information management between Bluetooth device and infotainment system. Necessary Bluetooth profiles in automotive use case are defined here.

The Telephony system shall be designed to

support a minimum of BT3.0+EDR, but shall be possible to upgrade to Bluetooth 4.0+EDR without hardware upgrade.

A Bluetooth hands-free system shall provide the following BT profiles:

• Core 2.0 + EDR inc. GAP (Generic Access Profile)
• HFP (Hands Free Profile)
• OBEX (Object Exchange)
• OPP (Object Push Profile)
• PBAP (Phonebook Access Profile)
• SPP (Serial Port Profile)
• SDAP (Service Discovery Access Profile)

If the BT system is designed to operate with BT Media Players (E.g. control and stream music from), the system shall also support the following incremental BT profiles:

• A2DP (Advanced Audio Distribution Profile)
• AVRCP (Audio Visual Remote Control Profile)

The link key shall be minimum 128 bits. The encryption key is negotiated and shall be set at the highest supported value by the remote device. The Telephony system shall be capable of generating up to 128-bit encryption key. The Telephony system will not be the limiting device in encryption key length negotiation.

When implemented by the remote device Simple Secure Pairing 'Numeric comparison' method as default pairing mechanism. However when remote device is limited a configurable priority scheme will be adopted where the order of mechanisms will be determined at configuration time.

The Telephony system shall provide Bluetooth Power Class 2. The operating range of Class 2 is 10 meters and maximum power is 2.5 mW (4 dBm).

The Telephony system shall have provision for 1, 3 and 5-slot packet transmission. It shall allow using five-slot packet transmission for faster data rate.

The Telephony system shall use IrMC standards as directed by the BT specification. It is a standard from IrDA, including IrOBEX for object exchange including vCards, vCalendars, etc.

vCard is the electronic business card. It is used for Personal Data Interchange (PDI). vCards are often attached to e-mail messages, and can be exchanged on Instant Messaging. vCard contain name and address information, phone numbers, and e-mail addresses.

vCard version 2.1 is widely adopted by e-mail clients. It contains FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ, GEO, TITLE, ROLE, Logo, Agent, ORG, NOTE, REV, SOUND, URL, UID, Version, and KEY properties.

vCard version 3.0 is IETF standards format. It is defined in following two parts:

MIME Content-Type for Directory Information

vCard MIME Directory Profile

It contains NICKNAME, CATEGORIES, PRODID, SORTSTRING and CLASS properties along with the vCard version 2.1 properties.

The touch-screen or head unit HMI must have the ability to delete a Bluetooth device and any associated data (E.g. phonebook, voicemail number) when required, even if the BT device list is not full.

The Telephony system shall use SCO link for voice data if eSCO link is not supported else eSCO shall be used.

The Telephony system shall implement Hands-Free Profile (HFP) as per the hands-free Profile specification version 1.6 or later.

The Telephony system shall enable a headset, or an embedded Hands-Free unit to connect, wirelessly, to a cellular phone for the purposes of acting as the cellular phone's audio input and output mechanism and allowing typical Telephony functions to be performed without access to the actual phone.

It shall provide following roles:

Hands-Free unit (HF)

Table 19 : List of HFP supporting functions