W3C

– DRAFT –
RPC

01 February 2021

Attendees

Present
Glenn, Gunnar, MagnusF, Rudi, Ted, Ulf
Regrets
-
Chair
-
Scribe
ted

Meeting minutes

[Magnus discusses presentation for upcoming webinar 18 February but cannot share until approved by Toyota]

[Ted mentions he is encouraging Autonomic to provide service candidates for catalog]

MagnusF: back to use cases then. assume these to be external interaction only or include internal eg hvac, seating etc?

Ted: don't see reason to exclude internal

Gunnar: question exists on whether to use VISS/VSS internal to vehicle as well
… seems contrary to SOME/IP but some moving more towards regular network in-vehicle

Rudi: having a unified method in and outside the vehicle has clear benefits
… people are familiar with existing use cases and advantages it could bring

Gunnar: back to original point, Magnus you're looking for clear scope

MagnusF: correct

Gunnar: CVII tech stack conversation it in and outside the vehicle
… cloud to vehicle can use this protocol (VISS) but how do you invoke AutoSAR services...

MagnusF: we may want to explore bring your own device. a generic interface service for a properly authenticated and authorized device
… and can give paired down functionality to the kids in the back seat

Rudi: another question is there is overlap with VSS/VISS for signals and keep VSC for functions

MagnusF: I can support multiple protocols and could easily intergrate others if sufficient libraries exist such as SOME/IP

Gunnar: we have a large number of areas under CVII, where we can provide some concrete work items helps

MagnusF: let's go back to the domains themselves
… are we coming up with explicit, complete functions or smaller functions for exposure to developers

Gunnar: do we go with specific definitions for infotainment services?

MagnusF: good question, some seem appropriate while others not

Glenn: there are financial interests, eg on vehicle loan related use cases

MagnusF: such as remotely disable ignition, makes sense. if you know anyone that can provide details for such would be helpful
… this would be handled with PKI and need regular certificate renewals

Glenn: ideal would be capability at manufacturer and allow enabling per fleet

MagnusF: any discussion with truck guys?

Ted: ongoing with Daimler, Volvo trucking - could also reach out to NMFTA

MagnusF: difference is heavy trucks are invariably in managed fleets

Glenn: they also produced an API for heavy vehicles
… there are regulations on telematics for vehicles

[Discussion of presentation at webinar]

https://github.com/nmfta-repo/nmfta-opentelematics-api

Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

Diagnostics