User Tools

Site Tools


agl-roadmap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
agl-roadmap [2019/07/25 13:18]
waltminer
agl-roadmap [2020/02/20 00:18] (current)
khosokawa [From Graphics EG]
Line 3: Line 3:
 The official AGL Roadmap is maintained in Jira. [[https://​jira.automotivelinux.org/​issues/?​filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:​using-jira|here]]. ​ The official AGL Roadmap is maintained in Jira. [[https://​jira.automotivelinux.org/​issues/?​filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:​using-jira|here]]. ​
  
-===== 2019 Roadmap/ Workplan from SAT =====+===== 2020 Roadmap/ Workplan from SAT ===== 
 +  
 +Updated 13 Feb 2020
  
     * **Happy Halibut and Itchy Icefish on Yocto 2.6 (thud)**     * **Happy Halibut and Itchy Icefish on Yocto 2.6 (thud)**
-    * Components to move from agl-devel to agl-extras +    * **Jumping Jellyfish and Kooky Koi on Yocto 3,0 (zeus)**  
-      * 4a+    *  
 +    * Candidate ​Components to move from meta-agl-devel to meta-agl 
 +      * Voice core components  
 +      * PipeWire  
 +      * meta-agl-profile-graphical-html5 ​
      * Review Reference Hardware System Architecture document and consider its implications for the software architecture. ​      * Review Reference Hardware System Architecture document and consider its implications for the software architecture. ​
      * Move RHSA to doc site.       * Move RHSA to doc site. 
      * Finish the documentation site improvements and increase the amount of documentation by 100%      * Finish the documentation site improvements and increase the amount of documentation by 100%
-     * Move to groups.io ​ 
      * **Add video support to mediaplayer binding.**      * **Add video support to mediaplayer binding.**
      * Video player and in-vehicle video architecture that allow third-party plug-ins, rear view camera, Autonomous vehicles, encrypted data such as widevine (from Google) for Netflix, Hulu, Android, etc.      * Video player and in-vehicle video architecture that allow third-party plug-ins, rear view camera, Autonomous vehicles, encrypted data such as widevine (from Google) for Netflix, Hulu, Android, etc.
      * Finish AGL spec 2.0      * Finish AGL spec 2.0
-     * Web App Manager maturity ​ 
      * Speech API maturity      * Speech API maturity
-     * Home Screen ​and Window Manager re-architecture ​+     ​* ​Completion of Home ScreenWindow Manager, and Compositor ​re-architecture ​
      * Instrument Cluster reference device improvements and maturity      * Instrument Cluster reference device improvements and maturity
-     * Create Telematics reference device +     * New reference board for 2020Switch ​to RHSA board.
-     * New reference board for 2019CES 2020 board should be M3 again or move to H3?  Need information from RHSA.+
      * Smartphone connectivity - no OS solution that allows integration of proprietary solutions such as CarPlay or Android Auto.  We do not have all of the components (video and audio especially) that are required for these integrations. What do we need to add?      * Smartphone connectivity - no OS solution that allows integration of proprietary solutions such as CarPlay or Android Auto.  We do not have all of the components (video and audio especially) that are required for these integrations. What do we need to add?
 +     * Long-Term Stable updates, proposal and agreement on a roadmap ot make each UCB components LTS
 +     * Improve collaboration with other projects to resolve many issues.ELISA,​ Yocto, OE, CIP
 +     * Increase production readiness based on OEM and Tier One gap analysis of missing features in UCB. 
 +       * Toyota code drop and other contributions from Tier One and OEM members
 +     * Increase QA and testing by increasing code coverage of our existing automated and manual tests
 +     * Apis
 +       * Define an AGL APIs description format and implement command line tools to generates C/C++ code skeleton and JSON marshaling/​un-marshaling and API documentation (SPEC-1903)
 +     * Signaling
 +       * Implement a per-signal (or per-class) permission model
 +       * Define & agree on Key Performance Indicator to ensure QA validation
 +     * Vehicle to Cloud
 +       * Propose an identity model to manage local/​remote identity to enable smartphone cooperation etc
 +       * Add MQTT as native transport for AGL
 +     * Security / Application Framework
 +       * Finalize and improve token logic in order to support smartphone replication ​
 +       * Set-up Firewall (in relation with the App. Framework)
 +       * Implement Security Manager hosted and maintained by AGL
 +       * Turn on widget signing and security enforcement
 +       * App. Framework: allow customers extensions (plugable transport / security / protocol) and make sustainable LTS source code
 +       * add support for legacy applications (for example support AGL Java client) and add LXC/systemd container to run 3rd party or legacy apps. 
 +       * Implement a secured single port reverse proxy
 +       * Better handling of reconnections (add connection session persistence,​ keep alive, ...)
 +       * Move from widget (now deprecated by W3C) to RPM package format for AGL services and applications
 +       * Add support for Javascript and Python bindings
 +     * Power resource & boot management
 +       * Integrate a boot configuration manager to reduce boot time, monitor, select boot mode, ...
 +       * Leverage TPM, trusted apps to secure key AGL services (App Framework, Identity, ...)
 +       * Support sleep on RAM and cryogenics for apps
 +     * System
 +       * minimize AGL footprint to support small systems (eg. small ECUs running cluster or telematic AGL profile)
 +       * Add real time capabilities on APIs (priorities,​ predictable execution) to guarantee QoS
 +
  
  
Line 32: Line 67:
  
      * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications,​ load them.      * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications,​ load them.
-     * Define the list of privileges we are going to enforce in the security model. ​   
-     * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} **Running apps not as root/ multi-user** 
-     * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) ​ 
      * Changes necessary at binder level for V2C (SSL transport)      * Changes necessary at binder level for V2C (SSL transport)
      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Application signing and installation mechanism      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Application signing and installation mechanism
Line 42: Line 74:
        * Development mode and Production mode for app management ​        * Development mode and Production mode for app management ​
      * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.      * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.
-     * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Binder APIv3 (enable dynamic APIs) 
      * Improved Developer workflow for debugging apps including ​      * Improved Developer workflow for debugging apps including ​
        * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Round trip download/​debug/​fix/​download apps.         * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Round trip download/​debug/​fix/​download apps. 
-       * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} **Supervision daemon for apps and services for development mode.** Allows a developers to have a central place monitor IPC in real time. Builds on the current monitor service that is available for binders. Extends its availability to startup and allows more general monitoring without requiring detailed knowledge of what is available in a specific binder. 
  
-     * **Task manager app** to allow developers to see what tasks/​process are running in an app. Allow for killing apps.  ​ 
-       * Review AGL spec 1.0 to determine what requirements are there for managing home screen and apps. Something like iphone where a double-tap on home button allows swiping up of apps to kill them.  
      * Terminal app on home screen      * Terminal app on home screen
  
-     * Introduce resource widgets to share content/ resources across multiple apps.  
      * App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5      * App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5
      * App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? ​      * App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? ​
      * App Framework binder communications shall be able to manage return from sleep mode.       * App Framework binder communications shall be able to manage return from sleep mode. 
-     * Connection glitches in multi-ECU system shall be properly handled. ​+     ​* ​[HH - partial support] ​Connection glitches in multi-ECU system shall be properly handled. ​
      * **XDS features**      * **XDS features**
        * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th)        * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th)
Line 85: Line 112:
  
 ==== From Graphics EG ==== ==== From Graphics EG ====
 +Updated 20 Feb 2020
 +
 +Our responsibilities have been almost completed in 2019. Our individual activities are not planned for next year.
 +The remaining activities will be addressed in IC-EG.
 +
      * Graphic      * Graphic
        * **Finish Window Manager and Homescreen work**        * **Finish Window Manager and Homescreen work**
Line 130: Line 162:
  
 ==== From Connectivity EG ==== ==== From Connectivity EG ====
 +
 +Updated 06 Feb 2020
 +
      * Vehicle Signaling ​      * Vehicle Signaling ​
-       * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} **Signal composer stabilization an improvements** 
-       * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} API to define new virtual messages at run-time 
-       * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Extend low level binding to hardware other than CAN. Need to determine what the next target hardware should be.  
        * Factory programming of CAN message set based on final vehicle configuration. Requires multiple vehicle message dictionaries to be present in the code.         * Factory programming of CAN message set based on final vehicle configuration. Requires multiple vehicle message dictionaries to be present in the code. 
-       * Done - **Add GPS data to virtual signal composer** 
-       * Done - **Sensor data collection and include in signal composer** 
-       * Done - **Improved performance using Denso Ten baseline as presented at ALS 2018** 
        * Content encryption within vehicle for streaming services or Blue Ray content. ​        * Content encryption within vehicle for streaming services or Blue Ray content. ​
-       ​* ​Done - Telematics reference device profile with built in modem+       ​* ​Better support for translation from CANoe to AGL message sets. 
 +       * Any other standard message set tools that we should support?
  
      * Bluetooth improvements      * Bluetooth improvements
-       ​* ​{{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} **Bluetooth ​binding rewrite** for stability and robustness ​ +       ​* ​Add support for proprietary chip stacks based on work done on other projects in support of AGL. Supports production readiness 
-       ​* ​{{:ff-ready-brightgreen.png?​nolink&​75|FF-READY}} **PBAP/​Contacts binding** +       * Bluetooth ​Low Energy (BLE) support 
-       * BLE binding ​+ 
 +     Tuner  
 +       ​* ​Update tuner API based on Denso-Ten gap analysis.  
      * WiFi improvements      * WiFi improvements
-       * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} **WiFi binding rewrite** for stability and robustness +       * AP Mode 
-       * **AP mode** +
-       * **Additional Wifi dongle support** +
-       * 802.11p support +
-       * Investigate LPWAN support for automotive +
-     * WWAN binding +
-       * Support current QMI  modems via either modemmanager or ofono+
      * Telephony app improvements      * Telephony app improvements
-       ​* ​Show missed call, last outgoing, last incoming call log info +       ​* ​Need to do more extensive testing of the Telephony app now that audio is working better. 
-       * Contacts integrated into dialing, caller ID, and call log info +
-     * NFC binder and NFC for user identification +
-     * Hardwired connection to telephone for **Telematics use cases**+
      * Network management binding      * Network management binding
-       ​* ​GG priorities ​in bold +       ​* ​Conman is probably not appropriate for production use cases, but we need requirements from Tier Ones and OEMS.  Do we switch to network manager or wait for someone to push code to us that already works in a production environment?​ 
-       ​* ​General network connectivity above connman ​to manage connectivity including ​**IPv4/v6 configuration**, bridging, tethering, network QOS and switching +       ​* ​Hardwired connection ​to telephone for **Telematics use cases** 
-       ​* ​**Add configuration ​support for networking into settings app**+       ​* ​Multiple simultaneous telephone ​support ​(wired + BT) for telematics use cases
        * User profiles to allow authorized users to configure interfacing        * User profiles to allow authorized users to configure interfacing
-       * Support multiple low-level interface binding backends including **Ethernet, WiFi**, BT PAN, and WWAN 
- 
-     * For 2018 - evaluate usage of connman versus network manager/​modem manager for long-term especially for 4G and complex use cases. 
  
  
Line 193: Line 216:
  
 ==== From CIAT EG ==== ==== From CIAT EG ====
-     * Lab in a box 
-       * Board management 
-       * Board on developer'​s desk 
-     * Improved publishing of test results 
-     * Additional tests 
-       * Applications 
-       * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} App Services 
-       * Platform 
-       * BSPs 
-     * Fuego integration 
  
 +Updated 06 February 2020
 +
 +  * Improved publishing of test results
 +    * Email Reports
 +      * improve format and feedback to gerrit
 +  * Additional tests
 +    * Applications
 +      * build and test different wgt types (normal, debug, test, coverage)
 +  * Fuego integration
 +    * Support to run tests as lava jobs (from within Fuego)
 +  * Images in build matrix
 +    * more variants! (plan is to use qemux86-64 for this)
 +      * e.g. sota enabled
 +      * agl-demo-platform-html5 (html5-only UI)
 +      * cluster profile/​image
 +      * telematic profile/​image
 +  * move from jenkins-job-builder to a .jenkinsci or yaml based job description
 ==== From Navi EG ==== ==== From Navi EG ====
      * AGL Navigation API      * AGL Navigation API
agl-roadmap.1564060712.txt.gz · Last modified: 2019/07/25 13:18 by waltminer