2026-04-27 LGE Contribution Pitch for Some/IP & Diagnostics

[qor-lb]

Location

Hyprid:

• F2F: BMW Autonomous Driving Campus, Landshuter Str. 26, 85716 Unterschleißheim (only possible via registration to @antonkri until 2026-04-22 EoB)
• Online: https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZDU3ZjZiM2QtMjgyZi00Njc4LTk5MmMtYjk5MDNkYzRmM2Uy%40thread.v2/0?context=%7b%22Tid%22%3a%22ce849bab-cc1c-465b-b62e-18f07c9ac198%22%2c%22Oid%22%3a%22b8b88e68-f07f-4c82-b01d-b4e2aec59438%22%7d

Participants

Agenda

Timeslot: 14:00 - 17:00 CEST

14:00 - 14:15 - Introduction round
14:15 - 15:15 - Presentation of Diagnostic Module Architecture (#2808) and Implementation
15:15 - 15:30 - Short break
15:30 - 16:30 - Presentation of SomeIP Module Architecture (#2807) and Implementation
16:30 - 17:00 - Discussion of next steps

Meeting Minutes

[antonkri]

• The code for the two modules (Diagnosis, Some/IP) is currently unavailable due to ongoing legal (AUTOSAR IP) review at LGE side.

• The AAS stack from LGE is called LARA (LG ARA).

• It was discussed, that currently there is a COMASSO organization, that is only available for AUTOSAR partners and that is planned to be used for hosting of those modules, that has AUTOSAR IP.

• Review of Diagnosis Module

  • Implementation of DoIP/UDS Diagnosis stack hat was already used in the series projects.
  • The code was co-developed together with another company. This company has no problems to open-source the code, but they are also currently doing source code review in parallel.
  • LGE presented an overview of the diagnosis module high-level architecture (link to slides will be added later). Sub-modules of diagnosis module has following colorings:
    • red: AUTOSAR IP and needs to be removed before open-sourcing
    • blue: modules should be developed jointly in S-Core community as a replacement for red modules
    • yellow: modules need to be refactored to remove AUTOSAR or OEM specific parts
    • green: can be open-sourced as they are right now.
  • It was decided, that it makes sense to publish red modules in COMASSO.
  • Further decisions and discussions are not possible due to missing source code
  • Next steps:
    • LGE will check with their legal department whether publishing of "red" modules in COMASSO is generally possible
    • LGE will communicate the timeline when the modules can be available open-source
    • LGE will provide interface between "red" and other modules, so that architecture community can judge whether the other modules can be reused in OpenSOVD implementation
    • S-Core technical leads will discuss what is the best way (also from licensing point of view) to get the access to the source code as fast as possible
      • Option 1: first put everything, also green sub-modules, into COMASSO
      • Option 2: put only red modules under COMASSO and the rest in S-Core

• Review of SOME/IP Module

  • Situation is comparable to the Diagnosis module, high-level architecture was presented with the same coloring.
    • The "blue" modules should be actually already there in S-Core
    • The red modules could be still first put to COMASSO for a review
    • E2E protection feature is put to "yellow" as implementation is "green" and profiles itself are "red", so it needs to be refactored.
  • SOME/IP implementation was never qualified/certified, however there are currently discussions with Exida to make Some/IP qualifiable.
  • SOME/IP module(s) are implemented with C++ 14. Exceptions are used, boost libraries not.
  • Serialization code for SOME/IP is generated based on the armxl generator from LGE. Generator is not qualified. This will need rework anyhow, as arxml will not be used in S-Core
  • The SOME/IP deamon from LGE compared to open vsomeip deamon implementation has some advantages:
    • LGE tests show that their deamon has better performance as the vsomeip
    • LGE deamon has some additional features, e.g. security (IAM)
  • Next steps
    • same as for diagnosis

[qor-lb]

@antonkri my notes to extend:

Next steps (sequential in order):

1. Prepare contribution possibility
   • S-CORE: clarify COMASSO setup (technical & organizational)
     • steering
     • option 1 vs 2
   • LGE: clarify if "red" parts can be contributed aswell
2. LGE: Open source code & prepare pitch (proposal how to adhere to the feature request and already discussed architecture)
3. S-CORE & LGE: evaluate & start consensus phase

Supporting diagram for option 1/2:

[Chulhee1Lee]

Apologies for the delayed response.

1. Regarding opening the source code, an internal legal review is still ongoing and is expected to be completed within May.
2. As for the presentation materials, due to internal company policy, an internal approval process must be completed in advance.
   This process is currently in progress, and we plan to upload the materials by the end of this week.