Communication FT Weekly [2026-10-26]

[LittleHuba]

Participants

@crimson11
@LittleHuba
@Thomas-Mikhael
@NEOatNHNG
@basheerFZ(LGE)
@AEK2HI
@artem-rudskyy
@mariuswbr
@basheerFZ
@alberto-s-avila
@jorgecasal
@artem-rudskyy
@AbdElrahmanKhalileJad

Agenda

1. Status update SOME/IP
2. Status update Flatbuffers
3. Status update Rust API
4. Status Methods&Fields
5. Status CI/Infrastructure
6. Open bug tickets
7. Short notice topics

Meeting Minutes

to (1)

@NEOatNHNG

Current topic: mw::com/LoLa usage in SOCOM
Next steps: Trim down of SOCOM @mariuswbr

to (2)

eclipse-score/communication#1435 ready for review

to (3)

No update

to (4)

No timeline for eclipse-score/communication#767 yet.

to (5)

CI not yet updated. Waiting for dependent PRs.
QNX workflow quite unreliable from forks. This is the well-known problem of accessing secrets from forks.
@LittleHuba will contact @nradakovic to discuss how we can improve the situation now that we can host our own SDP in S-CORE infra.

to (6)

eclipse-score/communication#1420 to be addressed by BMW (@LittleHuba)

to (7)

SOME/IP stack from LG:
Next week Communication/FT meeting (26th October) LG @basheerFZ will do a short presentation which compares it to existing vsomeip stack currently used by SOME/IP gateway incubator.

Main benefits:

• proven in field
• no boost dependency
• better performance than vsomeip
• lower maintenance cost

Opensomeip better in most performance regards but it does force a separate SOME/IP stack instance per application. No port sharing.

Safety Qualification for the lg-someip stack in regard to ASIL-B?
Ceritifaction was done with AUTOSAR variant of the stack. But not with the open sourced one.
LG commits to doing the necessary qualification steps for the opensourced stack.

What is the contribution model?
Currently in a standalone open source repository. Further discussions are currently ongoing with S-CORE PLs.

Please take a look at the slides. We will finish the discussion next week and do a vote whether we propose the change to the architecture circle of S-CORE.

Discussion of eclipse-score/communication#1433 . See comment in ticket.

[basheerFZ]

@LittleHuba ,
As discussed please find attached the lgsomeIP presentation material for your references
lg-someip-for-S-CORE_v0.3_26102026.pdf

[LittleHuba]

Offline feedback from @bharatGoswami8 regarding agenda point 3:

Rust API side Update

• Addressed all the review feedback from user side regarding method and field design - Rust::com Field and Method Rust Design and Example of APIs usage communication#818
• Rust-side E2E enablement discussion for this ticket: Improvement: E2E protection for Rust Method/Field APIs communication#1062, once the C++ side finalizes the design and implementation approach.