Proposals

Eclipse eXtensible State Machine (XSM) provides a middleware to implement state machines. It allows to alter an existing state machine without altering the existing code. As a middleware it does not provide a  service to a user directly but helps developers to focus on business logic.

An example:

Imagine a simple LIN node. The standard behaviour might be, that if it cannot serve due to internal issues it signals no service to the gateway. A carmaker explicitly requires the LIN node to signal operating the first 2s after powering on. With Eclipse eXtensible State Machine you can add this custom behaviour without touching the existing code.

Eclipse Biscuit provides an authorization token with decentralized verification, offline attenuation and strong security policy enforcement based on a logic language.

The Ankaios Dashboard is the UI for the Eclipse Ankaios project. It offers insights into a running Ankaios cluster, allows for modification/deletion/creation of workloads and offers a dependency graph for easier understanding of the interdependencies between workloads. The dashboard is a powerful tool to understand the functionality of Ankaios, if one didn't use the Ankaios CLI commands so far. Furthermore, if one is running into any issues during the execution of the Ankaios workloads, it is a good starting point to start debugging, especially for finding workloads that are missing that other workloads are depending on.

Eclipse Tradista is a Java based financial software covering Front and Middle Office processes in the market finance industry.

As the unique Open Source software in this area, it can retain attention of financial institutions and can be of interest in the academic sector as well.

Eclipse Tradista is based on several Jakarta EE technologies and can also be used to showcase the usage of Jakarta EE in the market finance area.

AAS made easy! - Eclipse Mnestix AAS Browser is the easy entry to the world of Asset Administration Shells (AAS) and is an easy-to-use browser for AAS.

The Eclipse Mnestix AAS Browser is basically a single page application written in React which allows you to visualize Asset Administration Shells and their submodels. It supports the AAS Metamodel and API in version 3.

You configure the endpoint of an AAS repository and search for AAS-IDs and if a Discovery Service is available, you also can search for Asset-IDs and visualize the corresponding AAS.

Eclipse Mnestix AAS Browser is also optimized for mobile view to have a great user experience on mobile phones.

Eclipse Mnestix AAS Browser can visualize every submodel even if it is not standardized by IDTA. There are some submodels visualized in a extra user friendly manner. These are:

• Digital Nameplate
• Handover Documentation
• Hierarchical Structures enabling BoM
• Carbon Footprint

Moreover dedicated visualizations for submodels can be added as a further feature.

Decoupling of the application logic from the basic software stack enables automotive suppliers (no matter if Tier-1 or in-house teams at an OEM) to contribute with building blocks to Software-defined Vehicle (SDV) projects. The Eclipse Automotive API Framework provides a stable application-facing interface, thereby minimizing the prevalence of proprietary solutions throughout the automotive sector. A corresponding model allows configuration and offers the needed flexibility for the handling of vehicle variants and different E/E architectures. Such solution also creates a win-win situation for both suppliers and OEMs. Suppliers aim to provide off-the-shelf software, while OEMs seek seamless integration and flexibility in feature selection. To maximize its applicability in the automotive HPC domain, the application interface shall encompass a wide range of functionalities relevant to application development. These functionalities include communication, diagnostics, non-volatile memory, and logging. Additionally, lifecycle (startup, operation, shutdown) and execution management will be covered, laying the foundation for a system-wide deterministic execution of control algorithms.

The  Eclipse CSP provides following layers and components:

• Offboard Platform Layer 
  
  • Data Collection and Processing: Enables gathering and processing vehicle data.
    
    • GDPR Compliance: The Eclipse CSP ensures compliance with GDPR standards throughout data storage and processing. 
    • Data Acquisition: Vehicles (using a vehicle client) transmit data using a lightweight MQTT protocol, minimizing data overhead and optimizing bandwidth usage. 
    • Data Processing: Kafka streams handle data processing, guaranteeing high throughput, reliable connectivity, and exchanges between vehicles and platform. 
• Reference Application:
  
  •  Remote Operations Application for vehicles to control door, Window, lights, Horn, Alarm, trunk, and  demonstrate how new services can be written using the code platform layer. 
• Vehicle Profile and Device Management: Manages vehicle profiles and connected devices.
• Setting and Configuration Management: Allows settings and configuration to be deployed and applied to a vehicle. 
• User and Identity Management: Secure user access and authentication.
• Notification Center: Facilitates sending and receiving notifications over push notifications to Mobile Apps, Email , SMS, and HTTPS push.  
• Device Management Orchestrator: Orchestrates device management tasks.
• Notification & Campaign Management: Enables managing notification campaigns.
• Onboard Client:
  
  • Vehicle Client: A C++ Client, ready to be deployed on TCUs/ECUs/IVI to validate the RO application use case. 
• Vehicle Simulator/Test Application: 
• A Linux-based vehicle simulator capable of simulating vehicle messages or receiving and responding to messages from a Cloud application. This is provided for testing and development purposes.
• Observability 
  
  • For enhanced monitoring and troubleshooting, SCP is integrated with observability tools like Graylog and Prometheus. 
• Mobile Application:
  
  • Reference Mobile Application (iOS/Android): Provides a reference application enabling vehicle users to visualize platform capabilities.
• Single-Click CD : Instructions & framework that shall enable single click deployment for Platform on AWS. The framework uses Kubernetes and ArgoCD for automated and scalable deployment of containerized applications/services.  

This open-source platform is designed to support connected car deployments of up to 100,000 vehicles, while the opensource offering utilizes a community version of open-source software currently like HiveMQ, Zookeeper Kafka, PostgreSQL and MongoDB, the system is inherently scalable for millions of devices in enterprise deployments. 

The project provides an embedded basic software (BSW) stack for microcontrollers written in C++ (language features up to C++14 are used). 
It provides libraries for

• lifecycle (startup/shutdown)
• communication (CAN, DoCAN, UDS)
• simple OS abstraction layer (reduced to scheduling and events, FreeRTOS implementation provided)
• STL-like container classes and a lock-free SPSC queue for inter task/core  communication
• basic I/O
• development tools (serial console, logging framework)

A demo implementation supporting two platforms, POSIX as a virtualized environment for rapid prototyping and NXP S32K148EVB with an example BSP, is provided.
 

Trust forms the basis for any data exchange transactions to occur. However, the control and transfer as well as claims protocols are trust agnostic and they are expected to connect to (one or multiple) trust frameworks. 

Since each dataspace is free to choose its own topology as well as standards and trust frameworks it uses/requires, the participants must be able to establish trust and fulfill requirements of the trust framework in order to perform trusted data exchange.

The proposal aims to establish requirements in the form of profiles which enables organizations to use these profiles with any of the protocols underneath and complete the connection to trust framework.

In a Data exchange transaction there may be various parties involved in different roles as defined in the trust framework and the mapping to those roles in a transaction is necessary to understand how the compliance and other requirements of the trust framework apply.

Example:

1. A Connector that is requesting the data from another connector is acting on behalf of a participant and the policies of trust framework as well as dataspace apply to it. 

    

The role model is used to determine the appropriate functions and requirements for those components in a given data exchange context.

Jakarta Query defines the syntax and semantics of the query language itself, including the type system of the language. 

Jakarta Query prioritizes clients written in Java. However, it is not by nature limited to Java, and implementations in other sufficiently Java-like programming languages might be contemplated.

The language is closely based on the existing query languages defined by Jakarta Persistence and Jakarta Data.

The Jakarta Query project will not cover:

• the Java APIs used to execute queries written in the language, nor
• how the query language maps to, or is implemented for, any particular database technology.