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 [2019/01/31 14:50] waltminer |
agl-roadmap [2020/02/06 14:40] waltminer [From Connectivity EG] Update Connectivity Roadmap during EG meeting |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| * 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 | * 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. | ||
| * Finish AGL spec 2.0 | * Finish AGL spec 2.0 | ||
| * Web App Manager maturity | * Web App Manager maturity | ||
| Line 19: | Line 20: | ||
| * Instrument Cluster reference device improvements and maturity | * Instrument Cluster reference device improvements and maturity | ||
| * Create Telematics reference device | * Create Telematics reference device | ||
| + | * New reference board for 2019? CES 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? | ||
| Line 127: | Line 130: | ||
| ==== 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. | ||
| - | * **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** | ||
| * Content encryption within vehicle for streaming services or Blue Ray content. | * Content encryption within vehicle for streaming services or Blue Ray content. | ||
| - | * 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. | ||
agl-roadmap.txt · Last modified: 2021/03/11 12:21 by YAMAGUCHINaoto
Page Tools
