• 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.
  •  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)
    • The 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?
  • How to SOME/IP to AUTOSAR?
  • Once we know direction, what parts are missing and need to be developed? 


  • No labels