UDS2SOVD Workstream Weekly Meetings

[stmuench]

2026-01-27 (upcoming)

Participants

Agenda

• further discuss design draft for communication between UDS2SOVD and ServiceApps via SOVDServer (@stmuench)

Meetings Minutes

• ...

[stmuench]

2025-09-09

Participants

@stmuench
@darkwisebear
@florianfueller
Badi Ennouri (self employed)

Agenda

n/a

Meetings Minutes

• BMW colleagues to create an initial slide deck for ideas about how a client-library API could look like for applications that would like to communicate with SOVD Server and thereby potentially also with UDS2SOVD Proxy

[stmuench]

2025-09-16

Participants

@stmuench
@florianfueller
Ravi Prasad

Agenda

n/a

Meetings Minutes

• short discussion about experiences when playing around with OpenSOVD's ODX Converter but no results yet from anybody

[stmuench]

2025-09-23 (canceled)

Participants

meeting is planned to NOT take place since @stmuench and @darkwisebear are not available that time

Agenda

n/a

Meetings Minutes

n/a

[stmuench]

2025-09-30

Participants

@stmuench
@florianfueller
John Emad

Agenda

Meetings Minutes

• no particular topics discussed
• John Emad introduced himself and asked around how he could contribute to OpenSOVD project

[stmuench]

2025-10-07

Participants

@stmuench (BMW)
@darkwisebear (BMW)
@lh-sag (Liebherr)
Ravi Prasad (Valeo)
Andrei Rusu (Continental)
Mihai Chelaru (Continental)

Agenda

• early feedback round for first design draft of diagnostic client library to be used by applications

Meetings Minutes

• @stmuench presented a first API draft for a diagnostic client library to be used by applications
• corresponding draft PR to be uploaded to OpenSOVD main repo by end of this week

[stmuench]

2025-10-21

meeting skipped since there were no topics to discuss

[stmuench]

2025-10-28

Participants

@stmuench (BMW)
Andrei Rusu (Aumovio)
RafalBrewka
Martin Jehle (Schaeffler AG)

Agenda

• discuss feedback provided for docs: add design for abstraction layer API to be used by user code #46 if not done already done offline or in Core Workstream

Meetings Minutes

• @stmuench shortly mentioned that feedback provided for docs: add design for abstraction layer API to be used by user code #46 got already discussed in today's Core Workstream
• RafalBrewka requested @stmuench to come up with some short demo implementation how such APIs and the contained Builder are supposed to be used by developers.

[stmuench]

2025-11-04

Participants

@stmuench (BMW)
@lh-sag (Liebherr)
Ravi Prasad (Valeo)
John Emad (Brightskies)
Daniel Krippner

Agenda

n/a

Meetings Minutes

• discussion about @lh-sag's open comments to docs: add design for abstraction layer API to be used by user code #46, results got documented as replies to the respective discussion items in such PR
• @lh-sag brought up SOVD Topology #19 and asked the round for opinions about how we want to expose the fault topology of a vehicle
  -> consensus was that this topic should be brought up in the architecture round again for further discussion and to reach an agreement

[stmuench]

2025-11-11 (skipped due to no topics on the Agenda)

Participants

Agenda

• none

Meetings Minutes

• n/a

[stmuench]

2025-11-18

Participants

@stmuench (BMW)
Andrei Rusu (Aumovio)
Kai Hudalla (ETAS)
Sherif Hegazy (Valeo)

Agenda

• present design draft for communication between UDS2SOVD and ServiceApps via SOVDServer (@stmuench)

Meetings Minutes

• presentation of design draft for communication between UDS2SOVD and ServiceApps via SOVDServer shifted to next due to lack of usual attendees
• @stmuench answered some general questions about the high-level scope for the UDS2SOVD component

[lh-sag]

@stmuench any chance to attach or share the presentation?

[stmuench]

@lh-sag I would like to bring up the topic in tomorrow's Core Workstream Meeting

[stmuench]

2025-11-25

Participants

@stmuench (BMW)
Sherif Hegazy (Valeo)

Agenda

• present design draft for communication between UDS2SOVD and ServiceApps via SOVDServer (@stmuench)

Meetings Minutes

• presentation of design draft for communication between UDS2SOVD and ServiceApps via SOVDServer got performed in today's Core Workstream where a need for a dedicated session regarding related discussions got identified; @stmuench to set up such a session
• edit: such clarification meeting between @stmuench and @lh-sag took place at 2025-11-27 where @stmuench explained the design to @lh-sag and the result was following design draft
• Sherif Hegazy formulated his intent to contribute to this workstream and is waiting for work packages to be created where he could pick some then

[stmuench]

2025-12-02 (skipped due to sickness)

Participants

Agenda

• none

Meetings Minutes

• n/a

[stmuench]

2025-12-09 (skipped due to sickness)

Participants

Agenda

• none

Meetings Minutes

• n/a

[stmuench]

2025-12-16

Participants

@stmuench (BMW)
Andrei Rusu (Aumovio)
Klaus Hartwig (Softing AE)

Agenda

• none

Meetings Minutes

• @stmuench gave a very brief introduction about this workstream to Klaus Hartwig

Further Announcements

• due to year-end season, the next UDS2SOVD Workstream meeting will take place on 2026-01-13

[stmuench]

2026-01-13 (skipped due to Zoom outage)

Participants

Agenda

• none

Meetings Minutes

• n/a

[stmuench]

2026-01-20

Participants

@stmuench (BMW)
@darkwisebear (BMW)
Andrei Rusu (Aumovio)
Bartosz Burda (42dot)
Klaus Hartwig (Softing AE)
Ravi Prasad (Valeo)

Agenda

• further discuss design draft for communication between UDS2SOVD and ServiceApps via SOVDServer (@stmuench)

Meetings Minutes

• first agenda point got shifted to next meeting since @stmuench to double-check how CDA handles such communication and whether we could re-use some functionality
• @stmuench gave a short announcement about the ongoing development of a POC for a DoIP server in Rust which is subject to get demonstrated as part of one of the next workstream meetings
• such DoIP server is intended to serve as the basis for implementation of the UDS2SOVD Proxy component