JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
Page History
...
| Project | Person reporting | Updates |
|---|---|---|
| Sebastian (Bosch) | Refactor Subscription Manager and fixes race condition in Websocket interface: |
| Ulf | See last update |
| Ulf | See last update |
Daniel Wilms (BMW) | No update | |
| Daniel W Ted | See last update |
| VSC team members | No call this week due to national holidays |
| Ulf | No update |
| Artem (EPAM) | See update in minutes for last week |
| ||
| Alexander Domin (BMW) | No update | (proposed. worth tracking in CVII call?) | (Thomas S) | Presentation from Kanto introduction posted in "2022-03-28" heading below.
| Steve (Renesas) | No update |
Minutes:
| Added wiki page to gather issues/opportunities for Minutes: | |
| Alexander Domin (BMW) | No update |
| (proposed. worth tracking in CVII call?) | (Thomas S) | Presentation from Kanto introduction posted in "2022-03-28" heading below. |
| Steve (Renesas) | No update |
Minutes:
- AMM workshop Thursday afternoon: 2-3 hours (Updated working list from last week)
- Discussion of what the group wants to work on and discuss in near-term
- Currently the sessions are split into the two related topics VSS Data Storage, including feeders and VSS Data Servers
- Topic brainstorming:
- VSS Data Storage (including VSS Data Feeders) (Southbound)
- Data Storage implementations:
- DBs: redis, timeseries etc
- Architecture: Single central vs distributed vs direct sensor connect (bypass store)
- Feeders: CAN (kuksa.val have closed some gaps), some/ip,
- Timeseries vs last/single value
- Interfacing into data servers
- Data Storage implementations:
- VSS Data Servers (Northbound)
- VISS v3? (Duplicate: Will be brought up in prior VISS session so likely handled there)
- Are VISS backend abstractions possible: storage, feeders?
- GraphQL - in-vehicle?
- BMW VISS→Android abstraction/interface/data server
- VSS Data Servers to cloud
- Data processing
- Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
- In-vehicle vs cloud
- In-memory vs storage
- Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
- VSS Data Storage (including VSS Data Feeders) (Southbound)
2022-04-13
Agenda:
- Project Status
- AMM Sessions
...
- Project status roundup abbreviated to allow more AMM prep. Any
- VISS
- Ted: BMW hope to OSS the VISS→Android adapter they will discuss at the VISS session at the AMM by June
- Ulf is refactoring WAII so the architecture has a much lower number of standalone processes. Work should be complete in 2-3 weeks.
- Kanto
- Steve: Tom could you chase Tina for the Kanto presentation please.
- Aos
- Steve reports that the public documentation for Aos is now online https://docs.aoscloud.io
- Work is starting on the previously reported goal of replacing the current VISS v1 server with an OSS replacement to adopt and extend. WAII and Kuksa.val in focus.
- Work is also starting on some of the VSS related topics mentioned in Artem's presentation last year such as user service migration between cars.
- VISS
- AMM workshop Thursday afternoon: 2-3 hours
- Discussion of what the group wants to work on and discuss in near-term
- Currently the sessions are split into the two related topics VSS Data Storage, including feeders and VSS Data Servers
- Topic brainstorming:
- VSS Data Storage (including VSS Data Feeders) (Southbound)
- Data Storage implementations:
- DBs: redis, timeseries etc
- Architecture: Single central vs distributed vs direct sensor connect (bypass store)
- Feeders: CAN (kuksa.val have closed some gaps), some/ip,
- Timeseries vs last/single value
- Interfacing into data servers
- Data Storage implementations:
- VSS Data Servers (Northbound)
- VISS v3? (Duplicate: Will be brought up in prior VISS session so likely handled there)
- Are VISS backend abstractions possible: storage, feeders?
- GraphQL - in-vehicle?
- BMW VISS→Android abstraction/interface/data server
- VSS Data Servers to cloud
- Data processing
- Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
- In-vehicle vs cloud
- In-memory vs storage
- Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
- VSS Data Storage (including VSS Data Feeders) (Southbound)
...
Overview
Content Tools