JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
...
Jira | ||||||
---|---|---|---|---|---|---|
|
Review of TODOs
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Kevin Valdek presents this slide that presents the big picture of the Cloud2Vehicle Communication Framework
Jira | ||||||
---|---|---|---|---|---|---|
|
Next steps
...
/TODO/ Glenn to provide the link to the YouTube video presenting an example of data processing / compression on the vehicle side
Jira | ||||||
---|---|---|---|---|---|---|
|
/TODO/ KevinV to draw a rough sketch of of the end-to-end architecture and provide a big picture of the Vehicle2Cloud Communication Framework DONE
/TODO/ Gunnar to provide the link to the 5GAA paper describing the data foreseen in V2V/V2X data exchanges
Jira | ||||||
---|---|---|---|---|---|---|
|
/TODO/ Glenn to provide the links to NHTSA paper on V2V/V2X data exchanges
Jira | ||||||
---|---|---|---|---|---|---|
|
...
...
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Gunnar: on the protocol for Vehicle => 3rd Party Servers, we need to go out and survey who are the players in the industry and which models of data capturing are acceptable
Kevin: : it's a bit of a different case, it could be brought out separately from the in-vehicle infotainment system to third-party servers, because that's the route the data would take.
Gunnar: presumably, yes, it is like an app getting a direct connection and maybe we leave that out the scope and say that's not part of our infrastructure. But at the same time in order to cover all cases, we should consider these points, see what they mean for us and see if we can relate to them in some way in our specifications because otherwise companies tend to work around it anyway, and they end up doing ad hoc things that we might be able to avoid if we actually cover it in our discussions
Kevin: actually vehicle to third-party servers connection comes down to connecting to devices or devices in general like a smartphone, this is the obvious example of having a direct access from my mobile device or an application in a mobile device to the onboard systems, that's more of the typical MirrorLink type of solutions, but it is true there is a lack of data protocols there and if this is VSS that the Vehicle Gateway is using and if these are VSS data that are being uploaded to the cloud, then of course if there is a direct connection with Wi-Fi or Bluetooth from smartphone and the vehicle, it makes sense that the VSS model or a certain data model is used there as well.
Kevin: One more comment in the OEM server to neutral server part, we should add a connection from OEM server to third-party servers or developers as in general the OEMs will provide an API both for neutral servers who serve as intermediaries and directly to third parties, that's already starting to become a common practice and should be considered.
Kevin: I have another comment that relates to the question Gerald mentioned with big data earlier, in my opinion there are certain (or maybe even larger) design impacts of the system considering personalized data, which are more like small data chunks with high frequency and high velocity rather than big data type of sharing between two different services. Probably the system block-diagrams are to look quite different at some components level.
Kevin: in my second set of comments, I added some thoughts about the third-party expectations. This is nothing groundbreaking but more practical things. The callback feature is one thing that third parties expect. Third parties rely a lot on quite up-to-date data. That means that sometimes even one minute old data is not that good because of a business case where you need to act fast on certain data or because of the user experience for instance in electric car charging where you want to get an event as soon as charging is complete.
Kevin: with the VSS and the W3C, I've seen websocket protocols are considered, and the system design should have (when we have a Rest API or an SDK) a callback system with web hooks, this was mentioned also in the OCF presentation. Today a lot of these OEM systems that do provide data don't provide callback systems in general and it is a bit of a headache for third parties. Typically there are different request limits that can be hard to meet at the same time, if there are no webhooks, it creates a problem because third parties want to get the latest data at the same time and the OEMs might limit them with their request limits because otherwise they get too much traffic to the servers. This kind of problem needs to be solved with technology and should be part of the system design we are considering
Kevin: in the last two steps of my second set of comments, I added a few things about the fleets. In general with data sharing, there is a general consent from the owners of the car, this is more for personal vehicles, when it comes to fleets, there are different considerations. If a fleet owner has 1,000 vehicles for instance, the third party application and the fleet owner are the same entity, in that case how that is handled and how the data querying is handled probably should be also part of the overall system design.
Gunnar: I agree with your views, IMHO we should have a list of typical applications / use cases, i.e. something to drive where we need to do different solutions. As you said, the solutions might be different for fleet management applications and user oriented applications. Also what you said about the Big Data statistics being a different one from user-centric data.
Kevin: agreed, I could add a list of use cases in the wiki page trying to cover some different verticals.
Philippe: we need to ask again Cloudera about their inputs of the system design for gathering vehicle big data
/TODO/ Gunnar set up a call with Cloudera to get their inputs of the system design for gathering vehicle big data
...
the list of presentations (and slide decks) is at: https://www.w3.org/auto/events/data-ws-2019/schedule.html
2 presentations need to be highlighted
Towards A Common Data Model Kenneth Vaughn, Trevilon
https://www.w3.org/2019/09/trans-data-ws/ITS_Data_Model-W3C-2019-09.pptx
Gunnar: introduces the slide deck, we should review with the comprehensive web site, the work seems to be fairly USA centric and ITS-related and related to fleet operation, we might be willing to take this into account in our work
Steve (who attended the workshop): it was an interesting presentation, consolidation of info from various specs, navigable on-line site with connection through various data models
slide 10: shows all data models in scope of this work
/TODO/ Bosch review the slide deck and possibly report on findings for next week
jira ticket created
Towards a SAREF extension for Automotive Michelle Wetterwald, Netellany
this work was pointed out by one of the AutoMat project participants interviewed by Philippe late July
Philippe: it refers to the work on data ontologies pushed by EU whose motivation is to define and promote an European standard
/TODO/ Benjamin review the slide deck on SAREF (TBC), Philippe will ask him about it
jira ticket created
Don: was VSS discussed there ?
Steve not in the workshop because VSS was discussed in a W3C auto WG scheduled the days before
Don: what about VSSo work ?
Gunnar: VSSowork is led by Benjamin and Daniel Wilms (BMW)
OCF Automotive update
Don: the OCF SC is still considering doing a demo at CES, there is an OCF interop event planned later this year, theme of the possible CES demo will be ratherabout electrification / charging status in the home
Gap analysis deliverable - review of drafts
Gunnar: we should also dig a little bit into vehicle fleet data management and impact on the "design concerns" content
Gerald: this is what Sensoris has looked into
Sprint & backlog review
CCS-59 to be checked with cloudera and engineers there
CCS-35 Philippe will ping daniel wilms
CCS-6 we should start populating it with work items related to Gunnar's thoughts on software designs, Gunnar: will do that, a link to Big Picture & Design concerns pzge added to the Jira ticket
CCS-38 /TODO/ @Kevin can you close it ?
CCS-39 Philippe will ping Sebastien about the status of the Kuksa project
AOB
notification scheme in Jira to be checked, Philippe will create a test jira ticket, reminders listed above will be sent by email
login Don credentials are working now
...
Philippe asks participants to review the project charter and provide comments by next week
link: https://www.neutralvehicle.com/ (yet another start-up company)
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
...