Connectivity Expert Group Meeting Archive
December 28, 2017
Attendees: Upcoming Meeting
Cancel due to holidays.
December 14, 2017
Attendees: Walt, Michael, Christian, Stephane, Sebastien, Romain, Matt
Discuss on Dec 14 whether we need to have Dec 21 meeting.
CES Demo
Kingfisher Advanced board proposed to be used. Late October deliver expected from Shimafuji. IoT.bzh will start looking at their board to verify the in BSP and connectivity to the external modules.
11/2 - Kingfisher boards arrived in Yokohama. BSP in progress at IoT.bzh, but they are having issues because Cogent did a “proof of concept” BSP that is a fork of an older Renesas BSP and there is no easy way to port if to the current upstream Renesas BSP.
11/16 - Ongoing work in Yokohama
11/30 - BSP being sorted out. Kingfisher being merged to master in meta-renesas-rcar-gen3 but there are a quite a few (60+) patches to be merged. Konsulko does not have the board, except for Scott. Backup plan to use ULCB with a bunch of USB dongles would still be a problem with BT audio for telephony.
Vehicle Signaling
-
11/2 - Work delayed because Romain was pulled into Window Manager effort. Concern that there is not a set of reference CAN messages or an reference app to make available as part of the release. Walt would like to get the code into EE to encourage people to start using it and we can fix any defects as they are found.
11/16 - No progress. Romain still working on Window Manager, HMI, XDG, etc effort.
11/30 - Romain did some work on the signal composer. Need to create a list of features and test apps available for EE.
12/14 - agl-service-signal-composer repo created. Romain pushed his code there. Need to make a recipe for RC5 to make it available for EE. Documentation will be updated on the web site as well.
Telephony Updates
Initial implementation in DD with reference phone app.
EE improvements
Move to a standalone service binding
Build out feature set for telephony (multipart call, phone book, reliability)
Update 10.8.:
Update to v2 and aligning verbs used between bindings.
Work on moving to a standalone binding.
Looking into phone book profile
Update 8/24
Telephone binding now standalone.
Working on verb syntax for bindings. Will discuss at the F2F in Yokohama next week.
Phone book and contact database investigations ongoing. Matt P. looking at best practices in other spaces (Android, etc.)
9/7 - No update
9/20 - Looking at regressions introduced in the pyro update to master.
10/5 - Matt looking at asynchronous events to the telephone QML app. Having issues with the SCO voice connection for HFP so Matt is working with Vayu rather ULCB.
11/2 - Everything is in except the cleanup to make it standalone. Asynchronous event handing code is in progress. Talked about whether/ how to make it generic in such a way to make it work with
GUI toolkits other than Qt, but that is a much bigger job.
11/16 - Work completed on asynchronous event handling for telephony.
12/14 - SCO issues with KF persist. See SPEC-1175 for any updates.
Bluetooth profiles -
Phone book/contacts
10/5 - See above.
11/1 - On hold.
11/30 - On hold.
12/14 - On hold
Other:
New:
November 30, 2017
Attendees: Walt, Jan-Simon, Romain, Matt, Stephane, Sebastien, Michael, Chris
CES Demo
Kingfisher Advanced board proposed to be used. Late October deliver expected from Shimafuji. IoT.bzh will start looking at their board to verify the in BSP and connectivity to the external modules.
11/2 - Kingfisher boards arrived in Yokohama. BSP in progress at IoT.bzh, but they are having issues because Cogent did a “proof of concept” BSP that is a fork of an older Renesas BSP and there is no easy way to port if to the current upstream Renesas BSP.
11/16 - Ongoing work in Yokohama
11/30 - BSP being sorted out. Kingfisher being merged to master in meta-renesas-rcar-gen3 but there are a quite a few (60+) patches to be merged. Konsulko does not have the board, except for Scott. Backup plan to use ULCB with a bunch of USB dongles would still be a problem with BT audio for telephony.
Vehicle Signaling
-
11/2 - Work delayed because Romain was pulled into Window Manager effort. Concern that there is not a set of reference CAN messages or an reference app to make available as part of the release. Walt would like to get the code into EE to encourage people to start using it and we can fix any defects as they are found.
11/16 - No progress. Romain still working on Window Manager, HMI, XDG, etc effort.
11/30 - Romain did some work on the signal composer. Need to create a list of features and test apps available for EE.
Telephony Updates
Initial implementation in DD with reference phone app.
EE improvements
Move to a standalone service binding
Build out feature set for telephony (multipart call, phone book, reliability)
Update 10.8.:
Update to v2 and aligning verbs used between bindings.
Work on moving to a standalone binding.
Looking into phone book profile
Update 8/24
Telephone binding now standalone.
Working on verb syntax for bindings. Will discuss at the F2F in Yokohama next week.
Phone book and contact database investigations ongoing. Matt P. looking at best practices in other spaces (Android, etc.)
9/7 - No update
9/20 - Looking at regressions introduced in the pyro update to master.
10/5 - Matt looking at asynchronous events to the telephone QML app. Having issues with the SCO voice connection for HFP so Matt is working with Vayu rather ULCB.
11/2 - Everything is in except the cleanup to make it standalone. Asynchronous event handing code is in progress. Talked about whether/ how to make it generic in such a way to make it work with
GUI toolkits other than Qt, but that is a much bigger job.
11/16 - Work completed on asynchronous event handling for telephony.
Bluetooth profiles -
Phone book/contacts
10/5 - See above.
11/1 - On hold.
11/30 - On hold.
Other:
New:
November 16, 2017
Attendees: Walt, Christian, Michael, Romain, Sebastien, Matt
Agenda:
CES Demo
Kingfisher Advanced board proposed to be used. Late October deliver expected from Shimafuji. IoT.bzh will start looking at their board to verify the in BSP and connectivity to the external modules.
11/2 - Kingfisher boards arrived in Yokohama. BSP in progress at IoT.bzh, but they are having issues because Cogent did a “proof of concept” BSP that is a fork of an older Renesas BSP and there is no easy way to port if to the current upstream Renesas BSP.
11/16 - Ongoing work in Yokohama
Vehicle Signaling
-
Face to Face meeting to be held in Vannes on Sep 5 - 7 to work on vehicle signaling improvements for EE release.
-
8/24 - gerrit 10107 should be ready to merge. Vannes workshop on track for Sep 5 - 7. Romain organizing and will post the agenda on the wiki page.
9/7 - No update. The face to face meeting in Vannes is ongoing.
-
-
11/2 - Work delayed because Romain was pulled into Window Manager effort. Concern that there is not a set of reference CAN messages or an reference app to make available as part of the release. Walt would like to get the code into EE to encourage people to start using it and we can fix any defects as they are found.
11/16 - No progress. Romain still working on Window Manager, HMI, XDG, etc effort.
Telephony Updates
Initial implementation in DD with reference phone app.
EE improvements
Move to a standalone service binding
Build out feature set for telephony (multipart call, phone book, reliability)
Update 10.8.:
Update to v2 and aligning verbs used between bindings.
Work on moving to a standalone binding.
Looking into phone book profile
Update 8/24
Telephone binding now standalone.
Working on verb syntax for bindings. Will discuss at the F2F in Yokohama next week.
Phone book and contact database investigations ongoing. Matt P. looking at best practices in other spaces (Android, etc.)
9/7 - No update
9/20 - Looking at regressions introduced in the pyro update to master.
10/5 - Matt looking at asynchronous events to the telephone QML app. Having issues with the SCO voice connection for HFP so Matt is working with Vayu rather ULCB.
11/2 - Everything is in except the cleanup to make it standalone. Asynchronous event handing code is in progress. Talked about whether/ how to make it generic in such a way to make it work with
GUI toolkits other than Qt, but that is a much bigger job.
11/16 - Work completed on asynchronous event handling for telephony.
Bluetooth profiles -
Phone book/contacts
10/5 - See above.
11/1 - On hold.
Other:
New:
November 2, 2017
Attendees: Walt, Jan-Simon, Romain, Stephane, Sebastien, Matt
Agenda:
CES Demo
Kingfisher Advanced board proposed to be used. Late October deliver expected from Shimafuji. IoT.bzh will start looking at their board to verify the in BSP and connectivity to the external modules.
11/2 - Kingfisher boards arrived in Yokohama. BSP in progress at IoT.bzh, but they are having issues because Cogent did a “proof of concept” BSP that is a fork of an older Renesas BSP and there is no easy way to port if to the current upstream Renesas BSP.
Vehicle Signaling
-
Face to Face meeting to be held in Vannes on Sep 5 - 7 to work on vehicle signaling improvements for EE release.
-
8/24 - gerrit 10107 should be ready to merge. Vannes workshop on track for Sep 5 - 7. Romain organizing and will post the agenda on the wiki page.
9/7 - No update. The face to face meeting in Vannes is ongoing.
-
-
11/2 - Work delayed because Romain was pulled into Window Manager effort. Concern that there is not a set of reference CAN messages or an reference app to make available as part of the release. Walt would like to get the code into EE to encourage people to start using it and we can fix any defects as they are found.
Telephony Updates
Initial implementation in DD with reference phone app.
EE improvements
Move to a standalone service binding
Build out feature set for telephony (multipart call, phone book, reliability)
Update 10.8.:
Update to v2 and aligning verbs used between bindings.
Work on moving to a standalone binding.
Looking into phone book profile
Update 8/24
Telephone binding now standalone.
Working on verb syntax for bindings. Will discuss at the F2F in Yokohama next week.
Phone book and contact database investigations ongoing. Matt P. looking at best practices in other spaces (Android, etc.)
9/7 - No update
9/20 - Looking at regressions introduced in the pyro update to master.
10/5 - Matt looking at asynchronous events to the telephone QML app. Having issues with the SCO voice connection for HFP so Matt is working with Vayu rather ULCB.
11/2 - Everything is in except the cleanup to make it standalone. Asynchronous event handing code is in progress. Talked about whether/ how to make it generic in such a way to make it work with
GUI toolkits other than Qt, but that is a much bigger job.
Bluetooth profiles -
Phone book/contacts
10/5 - See above.
11/1 - On hold.
Other:
New:
October 19, 2017
Canceled due to Dresden AMM.
October 5, 2017
Attendees: Walt, Matt, Stephane, Sebastien, Romain, Fulup, Frederic, Kusakabe
Notes:
Vehicle Signaling
-
Face to Face meeting to be held in Vannes on Sep 5 - 7 to work on vehicle signaling improvements for EE release.
-
8/24 - gerrit 10107 should be ready to merge. Vannes workshop on track for Sep 5 - 7. Romain organizing and will post the agenda on the wiki page.
9/7 - No update. The face to face meeting in Vannes is ongoing.
-
-
Telephony Updates
Initial implementation in DD with reference phone app.
EE improvements
Move to a standalone service binding
Build out feature set for telephony (multipart call, phone book, reliability)
Update 10.8.:
Update to v2 and aligning verbs used between bindings.
Work on moving to a standalone binding.
Looking into phone book profile
Update 8/24
Telephone binding now standalone.
Working on verb syntax for bindings. Will discuss at the F2F in Yokohama next week.
Phone book and contact database investigations ongoing. Matt P. looking at best practices in other spaces (Android, etc.)
9/7 - No update
9/20 - Looking at regressions introduced in the pyro update to master.
10/5 - Matt looking at asynchronous events to the telephone QML app. Having issues with the SCO voice connection for HFP so Matt is working with Vayu rather ULCB.
Other:
New:
September 21, 2017
Attendees: Walt, Fulup, Michael, Milan, Stephane, Sebastien
Notes:
Vehicle Signaling
-
Face to Face meeting to be held in Vannes on Sep 5 - 7 to work on vehicle signaling improvements for EE release.
-
8/24 - gerrit 10107 should be ready to merge. Vannes workshop on track for Sep 5 - 7. Romain organizing and will post the agenda on the wiki page.
9/7 - No update. The face to face meeting in Vannes is ongoing.
-
Roadmap items
NFC - Use of NFC for user identification
V2X Connectivity
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Other:
New:
———
September 7, 2017
Attendees: Walt, Sebastien, Michael
Notes:
Vehicle Signaling
-
Face to Face meeting to be held in Vannes on Sep 5 - 7 to work on vehicle signaling improvements for EE release.
-
8/24 - gerrit 10107 should be ready to merge. Vannes workshop on track for Sep 5 - 7. Romain organizing and will post the agenda on the wiki page.
9/7 - No update. The face to face meeting in Vannes is ongoing.
Roadmap items
NFC - Use of NFC for user identification
V2X Connectivity
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Other:
New:
August 24, 2017
Attendees: Walt, Christian, Michael, Matt, Romain
Notes:
Vehicle Signaling
-
Face to Face meeting to be held in Vannes on Sep 5 - 7 to work on vehicle signaling improvements for EE release.
-
8/24 - gerrit 10107 should be ready to merge. Vannes workshop on track for Sep 5 - 7. Romain organizing and will post the agenda on the wiki page.
Roadmap items
NFC - Use of NFC for user identification
V2X Connectivity
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Other:
New:
August 10, 2017
Attendees: Jan-Simon, Romain, Christian, Michael
Notes:
Roadmap items
NFC - Use of NFC for user identification
V2X Connectivity
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Other:
New:
July 27, 2017
Attendees: Walt, Jan-Simon, Kusakabe, Dennis, Matt
Notes:
Roadmap items
NFC - Use of NFC for user identification
V2X Connectivity
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Other:
New:
July 13, 2017
June 29, 2017
Attendees: Upcoming Meeting
June 15, 2017
Attendees: Walt, Fulup, Kusakabe, Dennis
Notes:
Roadmap items
Complete lower level stack through service binder for vehicle signaling especially CAN
Telephony - need binder for ofono
NFC - Use of NFC for user identification
Update 4/20: no update
Update 5/4 - No update
V2X Connectivity (add BoF to AMM)
Update 4/20: no update
Update 5/4 - No update
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Documented networking and Bluetooth
API for AGL for DD Release
Improved wifi and Bluetooth settings and management
Event based instead of polling
For the following items (and more) we should define the user cases we want to enable
Multiuser for BT and Wifi and connections. For example allowing access to BT device when a specific user(s) is in the vehicle.
Multiple connection management (managing multiple remote devices and switching between them) for Wifi and BT.
Basic security definition concerning who can configure Wifi and BT
Support for additional wifi dongles and modes. Currently station mode only.
-
We need to make sure we capture video of the Wifi and BT settings applications at the AMM to add to our video collection.
New:
May 25, 2017
Attendees: Walt, Kurokawa, Matsuzawa
Notes:
May 4, 2017
Attendees: Walt, Jan-Simon, Stephane, Romain, Fulup
Notes:
Vehicle Signaling
SPEC-428 - CAN low level binding. End of March delivery
Michael contacted Tobias about CAN simulator for AGL. K2L has different solutions so Tobias will contact us to let us know what is possible.
Need CAN reference characterization from cockpit reference group
Update 3/23 - Had a review of the IoT.bzh design and code that
is in github. Based on the discussion we added some items to the F2F meeting agenda in Karlsruhe.
Update 4/20 - from F2F in KA
-
Fujitsu-Ten approach to CAN signaling (Kusakabe)(20170402_ften_can_kusakabe_v2.pdf)
Romain: Work on filtering capabilities (~ next week)
Romain: discussion on CAN interface naming
Inclusion of low-level can binder in platform for DD to be discussed in dev-call / SAT meeting (location? github or gerrit).
Update 5/4 - Romain filtering capabilities will be in DD. A prototype version of ViWi will be available in DD. Low level
API will be stable for DD. Question came up of how do we distribute the service to developers that want to use it or try it out. At this time we do not have “Store” so we discussed making it available to be built with the SDK for developers that want to use it. Should be kicked up to the SAT for further discussion on having a store available in EE.
Telephony Updates
Matt reports he is making some progress. Can connect a call, playing with echo cancellation.
Update 3/23 - Matt not on call. Nothing to report.
Update 4/20: - PoC working, w/o echo cancellation, postponed due to volume management
Roadmap items
Complete lower level stack through service binder for vehicle signaling especially CAN
Telephony - need binder for ofono
NFC - Use of NFC for user identification
Update 4/20: no update
Update 5/4 - No update
V2X Connectivity (add BoF to AMM)
Update 4/20: no update
Update 5/4 - No update
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Documented networking and Bluetooth
API for AGL for DD Release
Improved wifi and Bluetooth settings and management
Event based instead of polling
For the following items (and more) we should define the user cases we want to enable
Multiuser for BT and Wifi and connections. For example allowing access to BT device when a specific user(s) is in the vehicle.
Multiple connection management (managing multiple remote devices and switching between them) for Wifi and BT.
Basic security definition concerning who can configure Wifi and BT
Support for additional wifi dongles and modes. Currently station mode only.
-
We need to make sure we capture video of the Wifi and BT settings applications at the AMM to add to our video collection.
New:
April 20, 2017
Attendees: Jan-Simon, Matt, Stephane, Romain, Kusakabe-san, Chris, Michael
Notes:
Vehicle Signaling
SPEC-428 - CAN low level binding. End of March delivery
Michael contacted Tobias about CAN simulator for AGL. K2L has different solutions so Tobias will contact us to let us know what is possible.
Need CAN reference characterization from cockpit reference group
Update 3/23 - Had a review of the IoT.bzh design and code that
is in github. Based on the discussion we added some items to the F2F meeting agenda in Karlsruhe.
Update 4/20 - from F2F in KA
-
Fujitsu-Ten approach to CAN signaling (Kusakabe)(20170402_ften_can_kusakabe_v2.pdf)
Romain: Work on filtering capabilities (~ next week)
Romain: discussion on CAN interface naming
Inclusion of low-level can binder in platform for DD to be discussed in dev-call / SAT meeting (location? github or gerrit).
Telephony Updates
Matt reports he is making some progress. Can connect a call, playing with echo cancellation.
Update 3/23 - Matt not on call. Nothing to report.
Update 4/20: - PoC working, w/o echo cancellation, postponed due to volume management
Roadmap items
Complete lower level stack through service binder for vehicle signaling especially CAN
Telephony - need binder for ofono
NFC - Use of NFC for user identification
V2X Connectivity (add BoF to AMM)
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Documented networking and Bluetooth
API for AGL for DD Release
Improved wifi and Bluetooth settings and management
Event based instead of polling
For the following items (and more) we should define the user cases we want to enable
Multiuser for BT and Wifi and connections. For example allowing access to BT device when a specific user(s) is in the vehicle.
Multiple connection management (managing multiple remote devices and switching between them) for Wifi and BT.
Basic security definition concerning who can configure Wifi and BT
Support for additional wifi dongles and modes. Currently station mode only.
-
We need to make sure we capture video of the Wifi and BT settings applications at the AMM to add to our video collection.
New:
March 23, 2017
Attendees: Walt, Stephane, Michael, Kusakabe
Notes:
Vehicle Signaling
SPEC-428 - CAN low level binding. End of March delivery
Michael contacted Tobias about CAN simulator for AGL. K2L has different solutions so Tobias will contact us to let us know what is possible.
Need CAN reference characterization from cockpit reference group
Update 3/23 - Had a review of the IoT.bzh design and code that
is in github. Based on the discussion we added some items to the F2F meeting agenda in Karlsruhe.
Telephony Updates
Matt reports he is making some progress. Can connect a call, playing with echo cancellation.
Update 3/23 - Matt not on call. Nothing to report.
Roadmap items
Complete lower level stack through service binder for vehicle signaling especially CAN
Telephony - need binder for ophono
NFC - Use of NFC for user identification
V2X Connectivity (add BoF to AMM)
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Documented networking and Bluetooth
API for AGL for DD Release
Improved wifi and Bluetooth settings and management
Event based instead of polling
For the following items (and more) we should define the user cases we want to enable
Multiuser for BT and Wifi and connections. For example allowing access to BT device when a specific user(s) is in the vehicle.
Multiple connection management (managing multiple remote devices and switching between them) for Wifi and BT.
Basic security definition concerning who can configure Wifi and BT
Support for additional wifi dongles and modes. Currently station mode only.
We need to make sure we capture video of the Wifi and BT settings applications at the AMM to add to our video collection.
Add Connectivity EG meeting on Feb 10 at AMM
March 9, 2017
Attendees: Walt, Stephane, Matsuzawa, Jan-Simon, Jens, Matt, Michael, Soya
Notes:
Vehicle Signaling
SPEC-428 - CAN low level binding. End of March delivery
Michael contacted Tobias about CAN simulator for AGL. K2L has different solutions so Tobias will contact us to let us know what is possible.
Need CAN reference characterization from cockpit reference group
Roadmap items
Complete lower level stack through service binder for vehicle signaling especially CAN
Telephony - need binder for ophono
NFC - Use of NFC for user identification
V2X Connectivity (add BoF to AMM)
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Documented networking and Bluetooth
API for AGL for DD Release
Improved wifi and Bluetooth settings and management
Event based instead of polling
For the following items (and more) we should define the user cases we want to enable
Multiuser for BT and Wifi and connections. For example allowing access to BT device when a specific user(s) is in the vehicle.
Multiple connection management (managing multiple remote devices and switching between them) for Wifi and BT.
Basic security definition concerning who can configure Wifi and BT
Support for additional wifi dongles and modes. Currently station mode only.
We need to make sure we capture video of the Wifi and BT settings applications at the AMM to add to our video collection.
Add Connectivity EG meeting on Feb 10 at AMM
January 26, 2017
Attendees: Walt, Jan-Simon, Fulup, Soya, Stephane, Srimaldia, Milan, Dennis, Michael, Chris
Notes:
Roadmap items
Complete lower level stack through service binder for vehicle signaling especially CAN
Telephony - need binder for ophono
NFC - Use of NFC for user identification
V2X Connectivity (add BoF to AMM)
Bluetooth profiles -
General network connectivity above connman to manage connectivity including bridging, tethering, network QOS and switching
Documented networking and Bluetooth
API for AGL for DD Release
Improved wifi and Bluetooth settings and management
Event based instead of polling
For the following items (and more) we should define the user cases we want to enable
Multiuser for BT and Wifi and connections. For example allowing access to BT device when a specific user(s) is in the vehicle.
Multiple connection management (managing multiple remote devices and switching between them) for Wifi and BT.
Basic security definition concerning who can configure Wifi and BT
Support for additional wifi dongles and modes. Currently station mode only.
We need to make sure we capture video of the Wifi and BT settings applications at the AMM to add to our video collection.
Add Connectivity EG meeting on Feb 10 at AMM
January 12, 2017
Attendees: Walt, Jan-Simon, Michael, Soya, Stephane
Notes:
December 1, 2016
Upcoming Meeting
Attendees:
Agenda:
Agenda:
Vehicle messaging solution for AGL -
Microchip working on integrating their proposed solution with the App Framework so that it is seamless to the apps if the vehicle data or controls are on MOST, CAN, etc.
Update - IoT has posted their documentation for signalling to the wiki which will remove AMB as a component. Yury to review and then determine how to rework HVAC. Need to ask Tanikawa-san if the request for vehicle speed data from CAN is to use a software module on the AGL system or a real CAN device. Can follow up on dev call on Tuesday.
November 17, 2016
Canceled - Yokohama F2F meeting
November 3, 2016
Attendees: Walt, Jan-Simon, Matt, Denis, Michael, Chris, Yury, Tobias, Bai
Agenda:
ALPS BT/Wifi module - commercial availability and FCC Certification - switching to commercially available dongle. Ishikawa will ask Imamura about acquiring the listed dongles, Another option would be to have Nori purchase some of the recommended dongles prior to the F2F meeting in Yokohama so NTT Data MSE can try those out.
Vehicle messaging solution for AGL -
Microchip working on integrating their proposed solution with the App Framework so that it is seamless to the apps if the vehicle data or controls are on MOST, CAN, etc.
Update - IoT has posted their documentation for signalling to the wiki which will remove AMB as a component. Yury to review and then determine how to rework HVAC. Need to ask Tanikawa-san if the request for vehicle speed data from CAN is to use a software module on the AGL system or a real CAN device. Can follow up on dev call on Tuesday.
SDL - Walt needs to set up separate call with Vitus. Two different companies working on CES demos (Livio and Elektrobit)
Security topics and possible Microchip presentation. Sent Irdeto slides from AMM to Michael and they will be posted on the AMM event site.
Microchip asked about threat list for security blueprint. Still waiting
October 20, 2016
Attendees: Walt, Michael, Christian, Sri Maldia, Milan, Ishikawa
Agenda:
Bluez, Connman compatibility for Yocto 2.1 - not discussed. ALPS will focus on Wifi for now and Bluetooth maybe if time allows. Need to make sure we have someone looking at Bluetooth since a few apps proposed for CES require Bluetooth. ALPS agreed to work on Bluetooth integration which supports discovery and audio connections. Will use a USB dongle (TBD which one) for those platforms that do not have Bluetooth on board.
ALPS BT/Wifi module - commercial availability and FCC Certification - switching to commercially available dongle. Ishikawa will ask Imamura about acquiring the listed dongles, Another option would be to have Nori purchase some of the recommended dongles prior to the F2F meeting in Yokohama so NTT Data MSE can try those out.
Vehicle messaging solution for AGL -
Tobias is now working full-time on the audio solution. Looking for a PulseAudio GUI to demonstrate usage of audio in a optical way. Walt will ask Scott Murray about this.
Microchip working on integrating their proposed solution with the App Framework so that it is seamless to the apps if the vehicle data or controls are on MOST, CAN, etc.
Working on some seamless audio controls for MOST and audio in general for automotive
SDL - Walt needs to set up separate call with Vitus
Security topics and possible Microchip presentation. Sent Irdeto slides from AMM to Michael and they will be posted on the AMM event site.
Microchip asked about threat list for security blueprint. Still waiting
October 6, 2016
Attendees: Walt, Michael, Christian, Tobias, Sri Maldia, Milan, Imamura, Ishikawa
Agenda:
Bluez, Connman compatibility for Yocto 2.1 - not discussed. ALPS will focus on Wifi for now and Bluetooth maybe if time allows. Need to make sure we have someone looking at Bluetooth since a few apps proposed for CES require Bluetooth.
ALPS BT/Wifi module - commercial availability and FCC Certification - switching to commercially available dongle.
ALPS recommends using the Wifi dongles: TL-WN722N , RTL8192 , or CLS Ralink RT5572. All are commercially available and will simplify the process of getting ready for CES.
NTT Data MSE is using an NEC dongle for their Miracast demo. They will share the information on which one they are using and ALPS offered to use that one as well.
September 21, 2016
Attendees: Walt, Christian, Michael
Agenda:
Bluez, Connman compatibility for Yocto 2.1 - not discussed
ALPS BT/Wifi module - commercial availability and FCC Certification - not discussed
Vehicle messaging solution for AGL
Microchip working on integrating their proposed solution with the App Framework so that it is seamless to the apps if the vehicle data or controls are on MOST, CAN, etc.
Working on some seamless audio controls for MOST and audio in general for automotive
SDL - Walt needs to set up separate call with Vitus
Open discussion
September 7, 2016
Attendees: Walt, Michael, Fulup, Vitus, Sri Maldia, Milan, Ahmed, Hiroshi Miura, Hiroto, Keisuke
Agenda:
ALPS conman apps for next demo
Bluez 4 is compatible with connman. Bluez 5 is not.
Bluez 5 is current Yocto 2.1 solution
ALPS BT/Wifi module UGKZ7 is the one they have in mind.
Is there a commercial module we can use instead?
Did some updating of the demo
spec and showed some of the AGL requirements
spec.
Vehicle messaging solution for AGL (AMB or competing solution)
SDL Investigation - Vitus can make a presentation at a future meeting on his investigation. Walt will set up a meeting especially dedicated to SDL topics and invite the AGL community.
OpenXC for CAN
Discussion
August 25, 2016
Attendees: Walt, Stephane, Fulup, Sri Maldia, Milan
Notes:
Discussed ALPS proposal on Connman and interfacing to the application framework. Need to push the email conversation to the public list. One question is how do we document the APIs. Led to discussion on OpenAPI collab project within the LF.
Walt to arrange meeting with OpenAPI folks from LF. Meeting to determine where they are going with version 3 of OpenAPI and how we could work together. Team is very interested in the automatic testing capability of the tool, maybe less so with code generation until we see how well it works.
Investigation into GENIVI, Tizen IVI, SDL, and RVI connectivity APIs would be beneficial to see what we can reuse. RVI includes V2V APIs and vehicle to server. SDL includes phone to car communications. Fulup will write up a Jira issue.
OpenXC - Fulup asked if Walt or Dan have some contacts at Ford that we can work with.
August 18, 2016
Meeting Canceled - change to biweekly
August 11, 2016
Attendees: Walt, Chris, Michael, Bai
Notes:
August 4, 2016
Attendees: Walt, Michael, Sri Maldia
Notes:
Yury - iDrive patch going in this week.
Reviewed Michael's responses in SPEC-132 and SPEC-134. Moved those to the SAT team list for review.
Sri Maldia - need to assign SPEC-170 to her. Waiting for Stephane to return from his vacation.
July 28, 2016
Attendees: Walt, Chris, Sri Maldia - Alps Electronics
Notes:
Jul 7, 2016
Attendees: Walt, Stephane, Jan-Simon, Yury
Notes:
Yury - sent log file to Isogai-san to help debug the problem with iDrive commands not getting into Wayland. Since we have not heard anything further from the team in Japan, assume they will work this out during the integration session in Japan on Friday.
Need Michael to update SPEC-132 or wiki page with why AMB is no longer considered that appropriate solution for vehicle messaging and what the proposed solution will look like. On vacation this week.
June 30, 2016
Attendees:Walt, Christian, Michael
Notes:
Tomorrow morning code Microchip will start putting code into gerrit for the video server, keyboard driver , backported MOST driver, vehicle interface. Done - waiting on merge. Need to decide if the refactoring of the templates and adding meta-agl-extra layer to the build affects where we put this code.
Michael shipping hardware to Japan tomorrow including the rear seat displays since Walt has not heard from BD about a ship date for the parts to get to him. Done
Jira request for new subfolders will be entered today. Jan-Simon is back in the office tomorrow and should get those set up. Done
Need Michael to update SPEC-132 or wiki page with why AMB is no longer considered that appropriate solution for vehicle messaging and what the proposed solution will look like. (After ALS)
June 16, 2016
Attendees:Walt, Stephane, Christian, Michael
Notes:
Tomorrow morning code Microchip will start putting code into gerrit for the video server, keyboard driver , backported MOST driver, vehicle interface.
Michael shipping hardware to Japan tomorrow including the rear seat displays since Walt has not heard from BD about a ship date for the parts to get to him.
Jira request for new subfolders will be entered today. Jan-Simon is back in the office tomorrow and should get those set up.
Need Michael to update SPEC-132 or wiki page with why AMB is no longer considered that appropriate solution for vehicle messaging and what the proposed solution will look like.
Open Telematics - Imamura-san said that he will update the issue in Jira (SPEC-187) to provide the latest status. Done
June 2, 2016
Attendees: Walt, Stephane, Michael, Christian, Imamura
Notes:
At the meeting in Vannes two weeks ago (Microchip/IoT.bzh) they determined that AMB is not the ideal solution for connectivity to the vehicle busses. Tobias (MOST) and Yuri (CAN/LIN) will start working in the next two weeks on the signaling interface. Requested that Michael update SPEC-132 or wiki page with why AMB is no longer considered that appropriate solution for vehicle messaging and what the proposed solution will look like.
Network connectivity - moved the
GUI part of the project to the ALS demo. Still need to update the requirements
spec.
Open Telematics - Imamura-san said that he will update the issue in Jira to provide the latest status.
May 19, 2016
Attendees: Walt, Christian, Michael, Stephane
Notes:
May 5, 2016
Attendees: Walt
Meeting canceled after 5 minutes due to Golden Week in Japan and National Holiday in Germany and France.
April 21, 2016
Attendees: Walt,Stephane, Imamura, Tamura, Yamashita, Sosa Rimpei
Notes:
April 6, 2016
Attendees: Walt, Michael, Christian, Stephane, Fulup, Imamura, Tamura, Bai, Yamashita
Notes:
Discussed proceeding with implementation of a prototype between IoT.bzh and Microchip using an agent structure. The general parameters are for Microchip to provide a number of agents CAN bus properties (both read and write) and IoT.bzh will work on integration with their app framework. Michael will talk to Yuri about how to structure the agents and have a proposal.
Face to face meeting in Europe proposed for May (dates TBD)
March 10, 2016
February 24, 2016
Face to Face meeting at the AGL AMM.
Attendees:
Fulup Ar Foll (IoT.bzh)
Nobuyuki Uchida (Qualcomm)
Risto Avila (Qt)
Keisuke Nakano (NTT DATA)
Hiroto Imamura (NTT DATA)
Walt Miner (Linux Foundation)
Michael Fabry (Microchip)
Soya Saito (Microchip)
Christian Gromm (Microchip)
A) Automotive Message Broker (AMB) - Discussion started on how connectivity between Application layer and hardware resources should be established best. Current AMB solution comes at following Pros/Cons:
Pros:
Cons:
AMB most likely is not going to be accepted in mainstream (Fulup)
AMB seems over-engineered (Fulup)
Current implemention has issues and need rework especially in terms of security (Risto, Michael)
A bus like CAN, must not be allowed to be accessed by every application (Michael)
Two-level security approach (Cynara, privileged database at application and context level) (Fulup)
Common mistake when designing an
API is to define it as a map not as a protocol (Fulup)
Proposal is to use json protocol as common
API instead of dbus (Fulup)
However, the parser needed to decode the Json messages might be too much overhead to be implemented in a small micro (Christian)
Following tasks need to be addressed:
Let's take what is already there (take stuff from Tizen)
Take CES demo and put it in an application framework
Create a common report to find out what is needed to move DEMO applications to a framework (IoT.bzh and MCHP)
Question is cost of adaption, e.g. writing documentation
Timeframe:
Do we need this for next release? (Michael)
Security is not that important for the BB release (Walt)
Need “sexy” demo for July most likely 90% can be reused (Fulup)
Misc:
How big is implementation of security server? How fast is the http server starting up? Boot time is key! (Risto)
Didn't do any measurement on boot time yet (Fulup)
Secure boot is needed and this will slow down boot process (Fulup)
B) Cloud Connectivity- Discussion on how this is intended to work (NTT Data)
C) SDL (Smart Device Link):
SDL should not be the center of the AGL architecture (Fulup)
First applications where designed on windows, then QNX (Copyright by Ford)
