Proposal(Updated) for AGL HMI-Framework

Size: px

Start display at page:

Download "Proposal(Updated) for AGL HMI-Framework"

Derick Webb
5 years ago
Views:

1 Proposal(Updated) for AGL HMI-Framework AGL All-Member TOKYO February 2018 Toshikazu Oiwa toshikazu_ohiwa@mail.toyota.co.jp TOYOTA MOTOR CORPORATION 1

2 Who is Oiwa? Ø Software engineer, expert in in-vehicle infotainment. Ø Have been developing software for in-vehicle infotainment system such as apps, services since Ø In charge of HMI-Framework. 2

2017 AGL Development Plan of TOYOTA ALSJun AMMOct

3 2017 AGL Development Plan of TOYOTA ALSJun AMMOct CESJan HMI-FW Window Proto. Sound UI & Graphics EG Presentation with DEMO HMI-FW on EE DRESDENGERMANY Vehicle I/F ALS DEMO CAN SDK / Ethernet Navigation EG Vehicle I/F on EE Reference Reference Hardware System Architecture EG Requirement Spec 3

4 Table of Contents Ø Background of HMI-Framework Ø Proposal for HMI-Framework OEM can choose GUI OEM can choose HMI- HMI-Framework can arbitrate HMI Resources Ø Demonstration Ø Schedule Ø Conclusion 4

5 Background of HMI-Framework 5

6 Background for in-vehicle HMI #1 Ø Needs for HMI has increased dramatically Expectation to HMI is getting higher and higher because of better user experiences(ux) by smartphone, especially for richer graphics and easier interaction by using touch-panel. Users expect HMI at the same level as smartphone to other consumer products. Such expectation shall be the same for in-vehicle system. However, HMI of present in-vehicle systems is behind. 6

7 Background for in-vehicle HMI #2 Ø Apps compete to output information in in-vehicle system HMI Running at the same time in in-vehicle system. Compete for getting resources(screen,speaker) to output information. Wants to display map Wants to display control of HVAC Lack of proper management results in driver distraction. can t appropriately place on screen In addition, resources management would be different by system configuration such as low-end systems or high-end systems. 7

8 Requirements for HMI-Framework 1OEM can choose GUI 2OEM can choose HMI- 3HMI-FW can arbitrate HMI resources Why requirement1? Ø Comfortable GUI GUI for better UX (background #1) Intuitively easy to understand (3D) Animation (Graphic Effects) Wants to be able to use the most suitable GUI. Why requirement23? Ø Safe HMI(background #2) Manage resources(window-resources/sound-resources) Arbitration of Window-Resources/Sound-Resources Wants to be able to use the most suitable software to system. Wants to be able to arbitrate resources. 8

9 Proposal of HMI-Framework OEM can choose GUI OEM can choose HMI- HMI-FW can arbitrate HMI resources 9

PF. App Layer HMI Apps GUI-library proprietary software GUI HMI-FW App FW Layer GUI-lib PAL(*) For AGL PF *PF

10 Requirement1 OEM can choose GUI No change in API which Apps refer to Apps can use API of each GUI-lib. legend Proposal point Each GUI-lib has layer to adapt to PF Can have many different GUI-libs without change of PF. App Layer HMI Apps GUI-library proprietary software GUI HMI-FW App FW Layer GUI-lib PAL(*) For AGL PF *PF Adaptation Layer Service Layer HMI-(*) HMI-Server (e.g. Weston, OpenGL/EG, ALSA) * Generic name of component to manage HMI 10

11 Requirement2 OEM can choose HMI-(*) * Generic name of component to manage HMI * Decides the optimum layout and controls(e.g. screen), based request from apps.. No change in API which Apps and GUI-libs refer to Apps and GUI-libs are available to use unique API of HMI-.. Each HMI- has interface to adapt to service layer Can have different HMI- without change in PF. legend Proposal point App Layer HMI Apps GUI-lib GUI-lib PAL For AGL PF HMI-FW App FW Layer Window HMI- Sound Others Sound Service Layer HMI-Server (e.g. Weston, OpenGL/EG, ALSA) 11

12 legend Components for Requirement12 Proposal point App Layer HMI Apps Qt API EB-Guide API HTML API Proprietary GUI API App FW Layer GUI-lib CORE GUI-lib PAL For AGL PF GUI-lib CORE GUI-lib PAL For AGL PF GUI-lib CORE GUI-lib PAL For AGL PF proprietary GUI GUI-lib CORE GUI-lib PAL For AGL PF GUI-lib HMI-FW Window API(common) Sound API(Common) Window Sound Other Sound e.g. AAAA HMI- I/F For AGL PF I/F For AGL PF I/F For AGL PF Service Layer Weston OpenGL /EGL ALSA 12

Requirement3 HMI-FW can arbitrate HMI resources 1.

Policy decides which App can allocate resources.

HMI. Policy DB is described in a format such as XML.

13 Requirement3 HMI-FW can arbitrate HMI resources 1.Judges use of resources for request from Apps(Policy ) Upon request (Event) from Apps, Policy decides which App can allocate resources. Has a rule of arbitration as Policy DB OEM can easily change Policy DB without changing HMI. Policy DB is described in a format such as XML. HMI Apps Requirement HMI- Judgment result Designed by developer or generated using tool Policy Policy DB A 1 2 Policy DB B State transition table is made by HMI specific designer at the design process. 13

14 Structure of HMI- including Policy Decides the optimum screen layout or speaker layout and controls screen or speaker, based on request from Apps. Window /Sound in HMI manager are the same in structure. [Main components] Policy HMI- Client Message Signaling Server Resource Manages resource information such as display, speaker. Layout Manages layout according to judgment result by Policy. Resources Resource Layout Policy Message Signaling Client Policy DB Reference General Information HMI-Framework Architecture 14

15 Demonstration 15

16 Structure of demonstration Built software for AGL 5.0 on M3 Demonstration s Apps are based on Apps of CES2018 HMI-Framework supports AFB Choose Qt for Req.1 Choose Audio (Genivi) for Req.2, Window and Sound are updated Window Policy DB is ZIPC format, Sound Policy DB is Genivi format for Req.3 HomeScreen Navi *Native App assuming navi Media Player Phone SDL App Glympse 1 Qt (GUI-lib) Window Policy ZIPC Policy DB ZIPC HMI- Policy (Genivi) Sound Policy DB Genivi HMI-FW AGL for ver5.0 R-Car M3 16

17 Demo1 Changing the behavior of HMI Ø Use case: Changes the behavior of HMI according to destination or grade. Policy AScreen layout (1 App: 1 screen) Push HVAC button Push Media Player button Step1: screen changes according to Policy A. Policy BScreen layout (2 App: 1 screen) Push HVAC button Push Media Player button Step2: Changed from Policy A to Policy B. And restart the system. Step3: screen changes according to Policy B. In this demonstration, simple-egl is used instead of map of native app. 17

18 Demo1 Changing the behavior of HMI Ø Use case: Changes the behavior of HMI according to destination or grade. Policy AScreen layout (1 App: 1 screen) Push HVAC button Push Media Player button Step1: screen changes according to Policy A. Policy BScreen layout (2 App: 1 screen) Push HVAC button Push Media Player button Step2: Changed from Policy A to Policy B. And restart the system. Step3: screen changes according to Policy B. In this demonstration, simple-egl is used instead of map of native app. 18

Demo② Arbitration of HMI Resources Ø Use case When

display on running, split the display screen and

NEW Screen transitions mixed application s normal and

on-screen display Normal size display Half size

19 Demo② Arbitration of HMI Resources Ø Use case When executing another application during navigation map display on running, split the display screen and display multiple applications. NEW Screen transitions mixed application s normal and half size display Non-rectangular or rectangular on-screen display Normal size display Half size display On-Screen display Screen transition of half size app Screen transition to normal size app 19

20 Schedule 20

xxx-xxxx-xxxx Screen layout (2App: 1 screen) On-Screen Vehicle info.

21 Schedule for HMI-Framework development Release Patch Updates HMI-FW has already been released in UCB5.0(EE) Screen layout (1 App: 1 screen) Active source change Features Developed New features(add) Incoming xxx-xxxx-xxxx Screen layout (2App: 1 screen) On-Screen Vehicle info. Instrument cluster CAN Steering SW Center display Assumed system Stabilize Multi ECU/Display Policy (Update) Input Touchpad Features Developed Patch Updates Stabilize 21

22 Conclusion 22

23 Conclusion Proposed three requirements for HMI-Framework. Ø 1OEM can choose GUI Enables compelling application development. Ø 2OEM can choose HMI- Enables flexible development for OEM needs. Ø 3HMI-Framework can arbitrate HMI resources Each OEM can easily develop each OEM s specification. By our proposal, we hope that OEM will promote product development using AGL and that AGL will become more active. 23

24 Thank you once again for taking the time to join today s presentation. toshikazu_ohiwa@mail.toyota.co.jp 24

AGL Requirements Specification V2.0

AGL Requirements Specification V2.0 AGL All-Member Meeting @ DRESDEN October 2018 Toshikazu Oiwa toshikazu_ohiwa@mail.toyota.co.jp TOYOTA MOTOR CORPORATION 1 Who is Oiwa? Ø Software engineer, expert in