Proposals

Eclipse Keypop open source interfaces will initially be available in Java and C++, designed on the same mutual Object-Oriented Model.

The 'Reader API' is a high-level interface used by terminal applications to operate smart card readers, it:

• provides the means to identify card readers and verify the presence of smart cards,
• offers the possibility to configure the observation of readers in order to be notified on card insertion or withdrawal,
• is the entry point to manage the selection of a smart card in a specific reader.

The 'Card API' defines the internal elements shared by the reader layer to implement specific ticketing card extension.

The 'Calypso API' is an extension of the Reader API which provides a high-level API standardizing the way to interact with Calypso cards.

• The Calypso Card API provides the means to select a target card and then perform a secure transaction with the selected target.
• The Calypso Crypto Legacy SAM API is the interface to manage security modules.

Purpose

Connecting Automotive Apps and Services, Everywhere

The purpose of this project shall be to provide a transport agnostic, layered communication protocol that builds on top of existing automotive and Internet standards, from the mechatronic layer (between ECUs, VMs, etc…) up to the Cloud, enabling a connected software defined vehicles.

Overview

The protocol is divided up into three layers:

• Application Layer (uP-L3):
  • Responsible for business/application logic through definition of methods, topics, messages
  • Core Platform uEs (uSubscription, uDiscovery, etc...)
• Communication Layer (uP-L2):
  • Describing data & metadate in a common way using CloudEvents: publication/notificaitons, request/response, file transfer, etc...
  • Routing & Dispatching of events through Dispatchers (uBus, uStreamer, Device Proxy Router, Cloud Proxy)
• Transport Layer (uP-L1):
  • Sending & receiving of events point-2-point between Software Entities (uEs)
  • Session an connection over automotive & Internet standards

For more information about uProtocol please visit: Overview of uProtocol

Project Contents

The uProtocol project shall contain that contain a number of children repos that are:

1. eclipse-uprotocol/uprotocol: Protocol specification & various layers interface definitions  and interface definitions
2. eclipse-uprotocol/uprotocol-sdk-java: Java Software development Kit (implements uP-L2 and includes other helper code for the protocol)
3. eclipse-uprotocol/uprotocol-sdk-cpp: Same as Java SDK but for C++
4. eclipse-uprotocol/uprotocol-android: Android implementation of uProtocol, both the transport protocol (Binder) and core dispatchers and application logic 

Eclipse Tocandira is a collection of tools aiming to help industries to remove their barriers on observability. To achieve this goal it uses the cutting edge technologies in the field. You will find the deploy easily configured with Docker, the connectivity with PLCs powered by 4diac, the gathering and storage done by Prometheus and the visualization shown with Grafana.Ec

Eclipse Tocandira was build focusing on:

• Reusability: Every technology chosen for this stack is the cutting edge of its field and the majority of them are well known in the IT world.
• Microservice Based: All services composing this application are truly independent and linked only by configurations, APIs and protocols.
• Cloud Native Architecture: These packages are usually applied for observability in IT world, and are therefore fully compatible with cloud environments, from instances to databases
• Small servers: Its components can run though several machines and consume little resources. It even runs on single board computers.
• Unlimited storage: Enough of charging for every variable read, the limit is only your hardware or the cloud capacity.

Eclipse SDV Developer Console (DCO) integrates necessary sources for software lifecycle management and there by optimizes the complete process from development to release of software. The core of DCO includes services for development, testing, simulations, release and lifecycle management of software. Hereby, DCOs mission is to automize as much as possible by using different concepts of re-usability and standardization by connecting different business roles along the software lifecycle on one source. As our open-source contribution, we focus on simulation of services with DCO.

With DCO you benefit from the concepts of standardization and re-usability. You can directly experience the scenario simulation in your productive environment. For instance simulate vehicle or fleet behaviours or use your own virtual vehicles or simulators to simulate backend services.

DCO comes with an user interface and related endpoints for backend interactions for defining your scenario, creating your simulation setup and to simulate your set of scenarios. In addition, your tool chain can be easily integreated to trigger a simulation with third-party applications, to analyze the simulation result and track the defects with your devops toolchain as well as the integration of applications for reporting and monitoring.

Eclipse Store provides a Java micro persistence layer built for cloud-native microservices and serverless functions written in Java. Eclipse Store is based on the system prevalence architectural pattern. It enables seamlessly storing any Java objects of any size and complexity transaction-save into cloud blob stores such as AWS S3 or any other binary data storage. Therefore, Eclipse Store provides connectors to various relational and NoSQL database systems. ACID transactions are journaled and changes in the system state are regularly saved to disk (deltas only). All transactions are stored in a highly optimized serialization byte format appended to the storage. To reduce startup time and run also with a small RAM capacity, Eclipse Store provides lazy loading. At the system start, only object IDs must be loaded into memory. Related object references (subgraphs) are only loaded and restored in memory on demand by calling common get methods. The Java Streams API is used for searching and filtering data in memory. Eclipse Store provides object versioning, dynamic class loading, and serialization control for handling class changes, ensuring that applications can continue to function even if classes are modified. Eclipse Store runs also on Android mobile, edge, and embedded devices.

Eclipse Heimlig is a Hardware Security Module (HSM) firmware for embedded platforms written in Rust.

As an HSM, Eclipse Heimlig typically runs on dedicated hardware and provides cryptographic services to clients running on other cores. These include:

• Generation and secure storage of cryptographic keys.
• Key use (encryption, decryption, signing, verification) without revealing key material to the client.
• Generation of cryptographically secure random numbers (CSPRNG).

Eclipse Heimlig implements common cryptographic algorithms:

• Symmetric encryption and decryption (AES-CBC, AES-GCM, AES-CCM, Chacha20Poly1305)
• Signing and verification (ECDSA)
• Key exchange (ECDH)
• Hashing (SHA-2, SHA-3, BLAKE3)
• Random number generation (ChaCha20Rng)

Eclipse Serializer is a serialization written from the ground up that works fundamentally differently from Java serialization and other encodings. Eclipse Serializer strictly separates data from code and transfers data only. Through deserialization, no code is executed at all. Thus, injecting and executing malicious code is impossible. Due to this highly-secure design, Eclipse Serializer protects against fatal deserialization attacks and eliminates the biggest security flaw of Java. This makes Eclipse Serializer a highly secure alternative to other serialization. 

Eclipse Xpanse provides a framework to describe and deploy cloud managed services to enable anyone to create them in a open and portable way.

To enable an Open Services Cloud market, the Eclipse Xpanse project provides:

• OCL (Open Services Cloud Configuration Language), a manifest file (json) describing all resources needed for a managed service. The OCL includes artifacts, identity, network, computing, storage, billing, console, etc. resource descriptions.
• Xpanse Runtime, the main component deployed on the cloud infrastructure, exposing an API to load OCL manifest, register and deploy managed services.
• XpansePlugins, specific to a cloud provider/infrastructure backend (e.g. openstack, kubernetes, Cloud Service Providers, etc.) which converts the abstract APIs from the Xpanse Runtime into the specific Cloud Service Providers concrete internal southbound APIs.
• Mockup UI, showing the concept of how Open Services Cloud market can operate.

The Stochastic Cognitive Model (SCM) is a driver behavior model for the use in multi-agent highway traffic simulations. SCM models cognitive processes of human drivers ranging from gaze behavior over situation recognition to decision on a specific action. SCM agents are further parametrized by driver parameters to ensure a range of driver behavior by different SCM agents and thus a high level of realism in the traffic simulation.

Creating a vertical Oniro OH solution has advantages for the Oniro Project. Some of them are outlined below.

• Provides a way to demonstrate Oniro features and technology using functional IoT device examples.
• Simplifies discussion with potential partners when one is able to show a real-world IoT device (albeit not fully-featured) built on top of Oniro by reducing the barrier to entry.
• Allows more thorough integration testing of Oniro components based on real user stories.
• Access to existing ecosystem for applications and services.

For Oniro, we want to provide blueprints of some IoT devices that can be built using Oniro. Eclipse Oniro OH is the first vertical solution add-on to provide this.