Page History

Table of Contents

This page is to find out a date for a 2-day F2F meeting in January. We will propose to We proposed the Audio HAL project to consider having a F2F meeting possibly the same days (TBC).on a half-day on Day 2

Date

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

Minutes 20200204-05-AASIG-F2F-meeting-minutes

Venue

BMW at Petuelring 130, 80809 Munich in Germany.

...

Contact Person

Unknown User (alexander.domin) : +4915160160632

Agenda

Time	Day 1
09.00

Agenda Review and introduction

09:30

Welcome, logistics (e.g. IT) and agenda review
	Vehicle HAL Security design (owner) (duration)
09:30-10:00

Security design (-owner)

Vectors of attack (TBD)

Access control and permissions in Android (Stefan

- TBC

)

How to verify permissions

(

TBD

30mn)

report on CDD (Sachin - TBC)

Build connection VSS to Android permissions model

(Stefan)

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

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).

VSS Layers:

/TODO/ Alexander sync with Giovanni Vergine on Adaptive Autosar IAM prior to the F2F WIP

10:30-10:45

Break

10:45-11:30

VSS Layers (Gunnar) (45mn)

concept could be used to put signals into access control groups

(Gunnar

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

? 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 rather ? is this only controlled based on the application

?Use cases and general requirements (TBD)

- identity ?

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

E.g. How fine grained must the permissions model be?Technical proposals


12.30	Lunch, at BMW office

13.30

Vehicle HAL Technical Proposals - further refinement

1 External services e.g. VISS, REST (TBD)

2 External services e.g. SOME/IP (TBD)

3

(owner, duration)
13:30-14:15	Android internal service (Some signal-connecting library using VSS standard) (

TBD

Stefan) (45mn)

VSS to standard Vehicle HAL - detailed

design -

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:15	Break
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

17:30

end of Day 1

Backlog topics

how to use SOME/IP to communication with Adaptive AUTOSAR and/or Classic AUTOSAR ?Once we know direction

how to use Adaptive AUTOSAR Identity & Access Management (IAM) ?

Once we 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:15	end of Day 1

Time	Day 2	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 (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

	Audio HAL		Vehicle HAL

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:15	Splitting break
10:15 -11:30	Work on highest priority topics of Audio HAL backlog - Source Management (Bartosz TBC) Networked audio devices Multi-source management: Multi‐source multi‐sink stream types, audio zones handling, still limited to one sink ?, limited number of sources Limited number of priorities (2), No priorities of phone call types.	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 of Audio HAL backlog - Common HAL (Piotr+1) Controlling audio effects Audio data transfer Multiple audio channels Equalization	10:30-12:15
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 discussion on additional extensions to Audio HAL that "would not change too many things" discussion on the part of the Audio HAL that could common for all SoC vendors 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:30-16:00	Wrap-up
		16:00	End of Day 2

Planned Attendees

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

+

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

+

Gunnar Andersson

??????????YESYESYESYESno

+

??YESYESYESYES

F2F, VHAL & Audio

Name	Attending	VHAL	AUDIO	Notes
		11	7
Gunnar Andersson	F2F	YES	YES
Unknown User (gururaja.n)	F2F	YES	YES	Vegetarian Food

Unknown User (alexander.domin)

YES

F2F

YES

+

YESYESF2F, VHAL (will add another colleague for audio)


Unknown User (wassim.filali)	F2F	YES
Stefan Wysocki

YES

F2F

YES

YESYES????YESYESYESYES

+

YESYESYESYESYES

F2F

Johan

??YESYESYES????YESYESYES??

+

??YESYESYES??

Partly via Telco, VHAL

Pete

+

Sachin

+

YESYES

F2F, VHAL (AUDIO)

Piotr KrawczykYESYESYESYESYESYESYESYESYESYES

+

YESYESYESYESYES

F2F, VHAL (exact person not decided)

Pontus

+

GuruYESYESYESYESYESYESYESYESYESYES

+

YESYESYESYES

F2F

Gerald

+

Unknown User (patrick.carlisle)NONONONONONONONONONO

+

NONONONONO

F2F. Audio/vehicle. Can't travel.

Stephen Lawrence

????

+

YESYESYESYESYES

Telco (need to check travel but would prefer to

get domain expert from within company)

Unknown User (markku.tamski@tieto.com)

??YESYESYES????YESYESYES??

+

??YESYESYES??

F2F

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

(+1 is registering)

YESYESYESYESYESYESYESYESYESYES

+

YESYESYESYESYES

F2F, AUDIO

Andrey ErshovNONONONONONONONONONO

+

NONONONONO

Will not be able to travel those days

Unknown User (bartoszbialek)

+

YESYES

F2F/Telco, AUDIO

+

Rooms available at BMW

YESYES

+

YES

YESOne room in february with video conference

	LO353 3 Feb 2020 18:55	LO354 5 Feb 2020 19:45	Arthotel ANA Olympiapark		no
Unknown User (bartoszbialek)	F2F		YES	LO353 3 Feb 2020 18:55	LO354 5 Feb 2020 19:45	Arthotel ANA Olympiapark		no
Piotr Krawczyk	F2F	YES		LO353 3 Feb 2020 18:55	LO354 5 Feb 2020 19:45	Arthotel ANA Olympiapark		no
Unknown User (johan.strand)	telco	YES
Sachin Athanikar	F2F	YES	YES
Stephen Lawrence	telco	YES					If you need to discuss h/w feel free to contact me to phone in. Meanwhile I spend the time improving the Genivi LAVA automated test system
Unknown User (niskandar)+ 1	F2F	YES	YES	by Car	by Car	TBD		yes please
Andrey Ershov (TBC)	telco	YES	YES				Andrey has a demo scheduled on 6 February and will likely be preempted totally by it
Philippe Robin	F2F	YES	YES	Monday 3 February	Thursday 6 February			no
Unknown User (kevinval)	F2F	YES					Joining the first day	no

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 name	Address	ZIP	Price 2020 (EUR)	Breakfast	Internet	Parking	Breakfast time	Breakfast-To-Go	Booking scode
Munich	Arthotel ANA Olympiapark	Helene-Mayer-Ring 12	80809	90,00	included	included	12,00 €	06:30-10:00	No
Munich	Super 8 Munich City North	Frankfurter Ring 143	80607	79,00	included	included	15,00 €	06:30-10:00	No
Munich	Leonardo Hotel Munich City Olympiapark	Dachauer Str. 199	80637	90,00	included	included	17,00 €	06:30-10:30	No
Munich	Harry's Home Hotel München	Bunzlauer Platz 5	80992	89,00	included	included	15,00 €	07:00-10:00	No	Buchungscode M_C88LI
Munich	Adagio access München City Olympiapark	Am Oberwiesenfeld 20	80809	87,00	included	included	8,00 €	06:30-10:00	No
Munich	Park Inn Frankfurter Ring	Frankfurter Ring 20-22	80807	87,00	included	included	18,00 €	06:30-10:00	Yes
Munich	Ibis Hotel München Nord	Ungererstrasse 139	80805	82,00	included	included	11,00 €	06:00-10:00	No
Munich	Ruby Lilly Hotel Munich City Center	Dachauer Str. 37	80335	88,00	included	included	17,00 €	06:30-10:30	No	LCOFIXBLXBMW
Munich	Vienna House Easy Munich (ehem. arcona)	Nymphenburger Str. 136	80626	90,00	included	included	18,00 €	06:30-10:30	Yes
Munich	Motel One Deutsches Museum	Rablstraße 2	81669	90,50	included	included	12,00 €	06:00-10:00	Yes
Munich	Motel One München Olympia-Gate	Petra-Kelly-Straße 4	80797	80,50	included	included	9,00 €	06:00-10:00	Yes
Munich	Rilano 24\|7 Hotel München City	Schillerstraße 17	80336	95,00	included	included	not available	06:30-10:30	No
Munich	Courtyard by Marriott City Center	Schwanthalerstraße 37	80336	99,00	included	included	25,00 €	06:30-11:00	No

Planned Attendees

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

Car Parking?

Name	Jan	Jan	Jan	Jan	Jan	+	Jan	Jan	Jan	Jan	Jan	+	Feb	Feb	Feb	Feb	Feb	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	+	3	4	5	6	7
Total YES												+
Total no												+
Gunnar Andersson	??	??	??	??	??		YES	YES	YES	YES	no	+	??	YES	YES	YES	YES	F2F, VHAL & Audio
Unknown User (alexander.domin)							YES	YES				+		YES	YES			F2F, VHAL (will add another colleague for audio)
Stefan Wysocki	YES	YES	YES	YES	??		??	YES	YES	YES	YES	+	YES	YES	YES	YES	YES	F2F
Johan	??	YES	YES	YES	??		??	YES	YES	YES	??	+	??	YES	YES	YES	??	Partly via Telco, VHAL
Pete												+
Sachin												+		YES	YES			F2F, VHAL (AUDIO)
Piotr Krawczyk	YES	YES	YES	YES	YES		YES	YES	YES	YES	YES	+	YES	YES	YES	YES	YES	F2F, VHAL (exact person not decided)
Pontus												+
Guru	YES	YES	YES	YES	YES		YES	YES	YES	YES	YES	+	YES	YES	YES	YES		F2F
Gerald												+
Unknown User (patrick.carlisle)	NO	NO	NO	NO	NO		NO	NO	NO	NO	NO	+	NO	NO	NO	NO	NO	F2F. Audio/vehicle. Can't travel.
Stephen Lawrence				??	??							+	YES	YES	YES	YES	YES	Telco (need to check travel but would prefer to get domain expert from within company)
Unknown User (markku.tamski@tieto.com)	??	YES	YES	YES	??		??	YES	YES	YES	??	+	??	YES	YES	YES	??	F2F
Unknown User (niskandar) +1 (MOBIS Frankfurt office) (+1 is registering)	YES	YES	YES	YES	YES		YES	YES	YES	YES	YES	+	YES	YES	YES	YES	YES	F2F, AUDIO
Andrey Ershov	NO	NO	NO	NO	NO		NO	NO	NO	NO	NO	+	NO	NO	NO	NO	NO	Will not be able to travel those days
Unknown User (bartoszbialek)												+		YES	YES			F2F/Telco, AUDIO
Unknown User (wassim.filali)												+			YES			AUDIO
												+
												+
Rooms available at BMW							YES	YES				+		YES	YES			One room in february with video conference	Name	Attending	Arrival day; flight no and time	Departure day; flight no and time	Hotel	Notes

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:

...

Page tree

Versions Compared

Old Version 37

New Version Current

Key

Date

Minutes 20200204-05-AASIG-F2F-meeting-minutes

Venue

Contact Person

Agenda

Date Planning

Planned Attendees

Availability planning

Transportation

Accommodation / Hotels

Planned Attendees

Date Planning

Availability planning

Agenda backlog

<Title of proposal (Template)>