...
Time | Day 1 |
---|
09.00 | Agenda Review and introduction |
09:30 | Security design - Vectors of attack
- Access control and permissions
- How to verify permissions
- Build connection VSS to Android permissions model
- External service approach
- = which authentication methods exist
- Adaptive AUTOSAR Identity and Access management has a general philosophy, defined names and concepts. It is a basis for discussion because it describes a model around interaction between (not details or protocols).
- → @alexander.domin (contact Giovanni Vergine)
- VSS Layers:
- concept could be used to put signals into access control groups (Gunnar Andersson - but after the basic ideas have been defined)
- Different users could have different permissions? Or is this only controlled based on application identity?
- For example audio zones... Some users should not be able to control the audio.
- But can this simply be built into the application?
- Use cases and general requirements
- E.g. How fine grained must the permissions model be?
|
12.3012.00 | Lunch, at WR BMW office |
13.00.30 | Technical proposals - further refinement - 1 External services e.g. VISS, REST
- 2 External services e.g. SOME/IP
- 3 Android internal service (Some signal-connecting library using VSS standard)
- VSS to standard Vehicle HAL - detailed design - can be done right away.
- Focus on: "Easiest way" to expose data to Android applications
- Compatibility Android and non-Android systems - common solutions
- Tool chains: VSS (or Franca) to Android IDLs translation?
- Decision point: Which design to use (develop), or at least prioritize
- ....Decide how the application layer should be fusing the connection - direct socket connection or bound through android service
|
17:30 | end of Day 1 |
| Backlog topics |
| - how to use SOME/IP to communication with Adaptive AUTOSAR and/or Classic AUTOSAR ?
- how to use Adaptive AUTOSAR Identity & Access Management (IAM) ?
- Once we know direction, what parts are missing and need to be developed?
- signal-to-service speci
|
Backlog topics | Time | Day 2 |
---|
08.30 | Start |
08:30-9:00 | Agenda bashing |
| Audio HAL - presentation of the work done by the HV project on the standard interfaces for the audio platform
- review of the list of prioritarized topics
- work on highest priority topics
- siurce management, networked audio devices
- controlling audio effects / audio data transfer
- multi-source management
|
Backlog topics | 12.00 | Lunch |
13.00-13:30 | Agenda bashing |
1413.30-16:00 | Vehicle HAL topics likely |
16:00 | End of Day 2 | 15.30 | 16.30 |
| Backlog topics |
Agenda backlog
...
Draft agenda planning here.
...