You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

We proposed the Audio HAL project to consider having a F2F meeting possibly on a half-dathe same days

Date

From Tuesday the 4th of February to Wednesday 5th of February

Venue

BMW at Petuelring 130, 80809 Munich in Germany.

Timetable

Time

Day 1

09.00

Agenda Review and introduction

09:30

Security design  (owner)

  • Access control and permissions in Android (Stefan) (30mn)
    • Build connection VSS to Android permissions model (Stefan)
    • How to verify permissions (Stefan)
  • External service approach (Alexander - TBC) (30mn)
    • = 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).
  • 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)
  • Different users could have different permissions?  Or is this only controlled based on application identity? (TBD)
    • For example audio zones...  Some users should not be able to control the audio.
      • But can this simply be built into the application?
      • Stefan: this is similar to what was introduced in Android 10
      • presentation of the zone concept in Android 10 (Piotr) (30mn)
  • Use cases and general requirements (TBD)
    • E.g. How fine grained must the permissions model be?
  • Vectors of attack (as a recap following the discussion on solutions) (brainstorming ?, follow the attack tree modeling method ?) topic for a later stage / F2F
  • report on CDD (Sachin - TBC)

12.30

Lunch, at BMW office

13.30

Technical proposals - further refinement

  • 1 External services e.g. VISS, REST/Web sockets (Gunnar: depends on OEM requirements) (Gunnar can lead the discussion, 
  • 2 External services e.g. SOME/IP (Gunnar) (45mn)
  • 3  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
  • Compatibility Android and non-Android systems - common solutions (brainstorming: preparation call with Giovanni, Piotr and Alex)
    • 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 specification in AR 19-11

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)
  • work on highest priority topics
    • source management, networked audio devices (TBD)
    • controlling audio effects / audio data transfer (TBD)
    • multi-source management (TBD)

12.00

Lunch

13.00-13:30

Agenda bashing

13.30-16:00

Vehicle HAL topics likely

16:00

End of Day 2


Backlog topics

Date Planning

Edit the table below to indicate your status with respect to the proposed dates for the F2F, entering one of the following:

Symbol

Meaning


[empty] Not yet determined

YES

this day works fine for me

no

This day definitely does not work for me

??

This day could work, but I would prefer not to

If you would use case exactly as shown ("YES", "no") that would help for visually scanning the table.

There are a lot of people to try to schedule to suitable dates, so please be as generous as possible in specifying "YES" or "??"

Availability planning

Name

Jan

Jan

Jan

Jan

Jan

+

Jan

Jan

Jan

Jan

Jan

+

FebFebFebFebFeb

Notes

please indicate F2F or telco

(and write AUDIO if you are interested
primarily in Audio HAL meeting)


20

21

22

23

24

+

27

28

29

30

31

+

34567


Total YES












+






 

Total no












+






 

??????????
YESYESYESYESno

+

??YESYESYESYES

F2F, VHAL & Audio

Unknown User (alexander.domin)







YESYES


+


YESYES

F2F, VHAL (will add another colleague for audio)

YESYESYESYES??
??YESYESYESYES

+

YESYESYESYESYES

F2F

Johan

??YESYESYES??
??YESYESYES??

+

??YESYESYES??

 Partly via Telco, VHAL

Pete










+







Sachin










+


YESYES

F2F, VHAL (AUDIO)

Piotr KrawczykYESYESYESYESYES
YESYESYESYESYES

+

YESYESYESYESYES

F2F, VHAL (exact person not decided)

Pontus










+







GuruYESYESYESYESYES
YESYESYESYESYES

+

YESYESYESYES

F2F

Gerald










+







Unknown User (patrick.carlisle)NONONONONO
NONONONONO

+

NONONONONO

F2F. Audio/vehicle. Can't travel.




????





+

YESYESYESYESYES

Telco (need to check travel but would prefer to

get domain expert from within company)

??YESYESYES??
??YESYESYES??

+

??YESYESYES??

F2F

Unknown User (niskandar) +1
(MOBIS Frankfurt office)

(+1 is registering)

YESYESYESYESYES
YESYESYESYESYES

+

YESYESYESYESYES

F2F, AUDIO

Andrey ErshovNONONONONO
NONONONONO

+

NONONONONO

Will not be able to travel those days

Unknown User (bartoszbialek)










+


YESYES

F2F/Telco, AUDIO












+



YES

AUDIO













+



















+







Rooms available at BMW







YESYES


+


YES

YES

One room in february with video conference

Transportation

  • From Munich Airport:
    • Ticket to bay:  M-5 (11.50€ for a single)
    • Take the S-Bahn S1 from the Airport (direction citi center).
    • Change to the U-Bahn U3 in Moosach (direction Fürstenrid West).
    • Exit the U-Bahn on Petuelring or Olympiazenter.
  • From Munich central railway station:
    • Ticket to bay:  M (3.30€ for a single)
    • Take the U-Bahn U2 from the Munich central railway station (direction Feldmoching)
    • Change to the U-Bahn U3 in Scheidplatz (direction Moosach).
    • Exit the U-Bahn on Petuelring or Olympiazenter.
  • By Car:

Accommodation / Hotels


City

Hotel nameAddressZIP

Price 2020 (EUR)

Breakfast

Internet

Parking

Breakfast time

Breakfast-To-Go

Booking scode

MunichArthotel ANA OlympiaparkHelene-Mayer-Ring 128080990,00includedincluded12,00 €06:30-10:00No
Munich Super 8 Munich City North Frankfurter Ring 1438060779,00includedincluded15,00 €06:30-10:00No
Munich Leonardo Hotel Munich City OlympiaparkDachauer Str. 1998063790,00includedincluded17,00 €06:30-10:30No
Munich Harry's Home Hotel MünchenBunzlauer Platz 58099289,00includedincluded15,00 €07:00-10:00NoBuchungscode M_C88LI
Munich Adagio access München City Olympiapark Am Oberwiesenfeld 208080987,00includedincluded8,00 €06:30-10:00No
Munich Park Inn Frankfurter RingFrankfurter Ring 20-228080787,00includedincluded18,00 €06:30-10:00Yes
Munich Ibis Hotel München NordUngererstrasse 1398080582,00includedincluded11,00 €06:00-10:00No
Munich Ruby Lilly Hotel Munich City CenterDachauer Str. 378033588,00includedincluded17,00 €06:30-10:30NoLCOFIXBLXBMW
Munich Vienna House Easy Munich (ehem. arcona)Nymphenburger Str. 1368062690,00includedincluded18,00 €06:30-10:30Yes
Munich Motel One Deutsches MuseumRablstraße 28166990,50includedincluded12,00 €06:00-10:00Yes
Munich Motel One München Olympia-GatePetra-Kelly-Straße 48079780,50includedincluded 9,00 €06:00-10:00Yes
Munich Rilano 24|7 Hotel München CitySchillerstraße 178033695,00includedincludednot available06:30-10:30No
Munich Courtyard by Marriott City CenterSchwanthalerstraße 378033699,00includedincluded25,00 €06:30-11:00No


Planned Attendees

Name

Attending

Arrival day; flight no and time

Departure day; flight no and time

Hotel

Notes

Car Parking?





































Agenda backlog


Draft agenda planning here.

<Title of proposal (Template)>

  • Proposer: <Person proposing topic>
  • Responsible group: Vehicle HAL project / Audio HAL project
  • Topic owner: <Person leading topic (may be different from Proposer)>
  • Length: <How much time is required for this session>
  • Abstract: <Short description of topic>
  • Content:



  • No labels