Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Backlog topics >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Time

Day 1

09.00

Welcome, logistics (e.g. IT) and agenda review


Security design (owner) (duration)
09:30-10:00

Access control and permissions in Android (Stefan) (30mn)

  • Build connection VSS to Android permissions model
  • How to verify permissions
10:00-10:30

External service approach - how to use Adaptive AUTOSAR Identity & Access Management (IAM)  (Alexander - TBC) (30mn)

  • = which authentication methods exist and could be used ?
  • 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 entities (not details or protocols).
  • /TODO/ Alexander sync with Giovanni Vergine on Adaptive Autosar IAM prior to the F2F WIP
10:30-10:45Break
10:45-11:30

VSS Layers (Gunnar) (45mn)

  • concept could be used to put signals into access control groups
  • how to map the concept to Android permissions (how it will be done on the Android side)

11:30-12:00

Users vs. permissions - presentation of the zone concept in Android 10 (Piotr) (30mn)

  • Different users could have different permissions
    • For example audio zones...  Some users should not be able to control the audio.
    • But can this simply be built into the application rather ? is this only controlled based on the  application identity ?
    report on CDD (Sachin - TBC)
12:00-12:30

Security design backlog review & update

  • Vectors of attack
    • as a recap following the discussion on solutions
    • brainstorming on which attacks are targeted with the solutions discussed ?
    • follow the attack tree modeling method ? (topic likely for a later stage / F2F)
  • recap on the morning outcome

12.30

Lunch, at BMW office


Technical proposals - further refinement (owner, duration)
13:30-14:15

Android internal service (Some signal-connecting library using VSS standard) (Stefan) (45mn)

  • VSS to standard Vehicle HAL - detailed design  can be done right away.
    • Focus on:  "Easiest way" to expose data to Android applications
14:15-15:00

External services - SOME/IP (Gunnar) (45mn)

  • how to use SOME/IP to communicate with Adaptive AUTOSAR and/or Classic AUTOSAR ?
15:00-15:15Break
15:15-16:00

External services - VISS, REST/Web sockets (Gunnar - TBC) (45mn)

  • relevance of topic depends on OEM requirements
  • Gunnar can lead the discussion but needs inputs on whether REST/Web sockets are in scope)
  • /TODO/ Sachin, Alex, others provide inputs prior to the F2F

16:00-16:45

Compatibility Android and non-Android systems - common solutions (TBD) (45mn)

  • brainstorming needed prior to the F2F
  • /TODO/ Alexander sync with Giovanni Vergine and Piotr Krawczyk on FARACON project prior to the F2F WIP
  • Tool chains:   VSS (or Franca) to Android IDLs translation ?
16:45-17:15

Technical proposals - Backlog review & update

  • Decision point:  Which design to use (develop), or at least prioritize
    • ....Decide how the application layer should be fusing fueliing the connection - e.g. direct socket connection or bound through android service
  • 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
    • have agreed on which design to follow , what parts are missing and need to be developed?
  • signal-to-service specification in AR 19-11
  • introduction to Android CDD (Sachin) (30mn TBC)
  • recap on the afternoon outcome

17:3015

end of Day 1

Time

Day 2

Time

Day 2

08.30

Start



08:30-9:00Agenda bashing

Audio HAL

  • presentation of the work done by the HV project on the standard interfaces for the audio platform (Gunnar)
  • review of the list of prioritarized topics (TBD)


  • 9:00-9:45

    Common topic : introduction to the Automotive Virtualization Platform Specification (Gunnar, 45mn)

    • standard audio interfaces
    • other relevant standard interfaces


    9:45-10:15Common topic; introduction to Android CDD (Sachin) (30mn)

    10:15-10:30Splitting break


    Audio HAL
    Vehicle HAL
    10:30-11:30

    Work

    work

    on highest priority topics

    • source management, networked audio devices (TBD)
    • multi-source management (TBD)
    10:30-12:15

    Brainstorming

    • Decision point:  Which design to use (develop), or at least prioritize
    • What parts are missing and need to be developed ?
    11:30-12:15

    Work on highest priority topics

    • controlling audio effects / audio data transfer (TBD)
  • multi-source management (TBD)
  • 12.00

    Lunch

    13.00-13:30

    Agenda bashing

    12.15-13:15

    Lunch

    12.15-13:15

    Lunch

    13:15-14:00

    Audio HAL - backlog review and update (All Audio HAL participants) (45mn)

    • recap on the morning outcome
    • review of the list of prioritarized topics

    13:15-14:00

    Vehicle HAL - backlog review and update (All Vehicle HAL participants) (45mn)

    • recap on the morning outcome
    • backlog update

    14:00

    End of Audio HAL split meeting

    14.00-14:15

    Merging Break


    14.15-15:30

    Vehicle HAL topics (TBD)


    15:

    13.

    30-16:00

    Vehicle HAL topics likely

    Wrap-up



    16:00End of Day 2
    Backlog topics

    Planned Attendees

    Name

    Attending

    VHALAUDIO

    Arrival day; flight no and time

    Departure day; flight no and time

    Hotel

    Notes

    Car Parking?



    117




    F2FYESYES




    F2FYES





    F2FYES





    F2F
    YES




    F2FYES





    F2FYES





    F2F or telco (TBC)
    YES




    F2F or telco (TBC)YES





    telcoYES





    F2FYESYES




    Stephen Lawrence +domain expert (TBC)

    telcoYES





    F2F
    YES




    telcoYESYES




    F2FYESYESMonday 3 FebruaryThursday 6 February

    no

    ...