User Tools
agl-roadmap
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
agl-roadmap [2018/07/04 18:02] sdesneux |
agl-roadmap [2018/07/18 13:46] waltminer [From App FW and Security EG] |
||
|---|---|---|---|
| Line 28: | Line 28: | ||
| * {{: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) | * {{: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) | ||
| - | * Application signing and installation mechanism | + | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Application signing and installation mechanism |
| + | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} Mechanism for checking signature is in place. | ||
| + | * Require all apps to be signed in GG | ||
| + | * Developer workflow is needed for managing keys | ||
| + | * 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) | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} Binder APIv3 (enable dynamic APIs) | ||
| Line 53: | Line 57: | ||
| * Improved development cycle (based on partial Widget installation) | * Improved development cycle (based on partial Widget installation) | ||
| * First step to support package manager for SDKs (Yomo) | * First step to support package manager for SDKs (Yomo) | ||
| + | |||
| + | * **GG Priorities for App FW** | ||
| + | * Multi-user use case | ||
| + | * API for abstraction of hardware mechanism for signing apps, packages, etc. | ||
| + | * Headless/ Telematics use case | ||
| + | * Unit testing for app framework | ||
| + | * Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms. | ||
| + | * Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]] | ||
| + | * Allow keys to be changed by the device developers - git repo and recipe for keys | ||
| + | * Library (or binding) to plug in key management to the app FW. | ||
| + | * Reference implementation will use the file system as the key store. Can be swapped for a trusted environment by a device creator at a later time. | ||
| + | * Sign at build time in AGL CI system with a check at run time | ||
| ==== From Graphics EG ==== | ==== From Graphics EG ==== | ||
| Line 93: | Line 109: | ||
| * {{: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. | * {{: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. | ||
| + | * **Add GPS data to virtual signal composer** | ||
| + | * **Sensor data collection and include in signal composer** | ||
| + | * **V2C interface** | ||
| + | * **Improved performance using Denso Ten baseline as presented at ALS 2018** | ||
| + | |||
| * Bluetooth improvements | * Bluetooth improvements | ||
| * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **Bluetooth binding rewrite** for stability and robustness | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **Bluetooth binding rewrite** for stability and robustness | ||
| * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **PBAP/Contacts binding** | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **PBAP/Contacts binding** | ||
| - | * BT PAN binding | ||
| * BLE binding | * BLE binding | ||
| * WiFi improvements | * WiFi improvements | ||
| Line 112: | Line 132: | ||
| * Hardwired connection to telephone for **Telematics use cases** | * Hardwired connection to telephone for **Telematics use cases** | ||
| * Network management binding | * Network management binding | ||
| - | * General network connectivity above connman to manage connectivity including IPv4/v6 configuration, bridging, tethering, network QOS and switching | + | * GG priorities in bold |
| + | * General network connectivity above connman to manage connectivity including **IPv4/v6 configuration**, bridging, tethering, network QOS and switching | ||
| + | * **Add configuration support for networking into settings app** | ||
| * 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 | + | * 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. | * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases. | ||
| - | * Port Comtech's OSS nav app to demo HMI | + | |
| ==== From V2X EG ==== | ==== From V2X EG ==== | ||
agl-roadmap.txt · Last modified: 2021/03/11 12:21 by YAMAGUCHINaoto
Page Tools
