eclipse-score / eclipse-score/score

Feature Request: Vehicle External Control Interface (VECI)

Open
#2,751 8 comments 0 reactions 1 assignee Claimed by @Haishi2016 View on GitHub
community:architecture feature_request fep fep:needs-shepherd
Dominant language
Starlark
Stars
109
Forks
105
Avg merge
1d 9h
Merged PRs (30d)
24

Description

### Feature Request / Modification Description

## 1. Problem

S-CORE defines a unified software platform for Software Defined Vehicles (SDV), including in-vehicle lifecycle and orchestration capabilities (e.g., #2597).

However, there is currently no standardized mechanism for vehicles to:

* expose controllable system capabilities to external systems
* report system state in a consistent and structured manner
* safely accept externally provided constraints or policies

Without such an interface, consistent management, observability, and policy enforcement across multiple vehicles (such as a fleet) becomes fragmented and implementation-specific.

## 2. Proposal

S-CORE shall define an on-vehicle interface layer that enables interaction with external control systems (e.g., cloud or on-premises orchestrators).

This interface provides:

* standardized control hooks for system components
* structured state reporting and observability
* policy and constraint injection points with local validation

This proposal does not define any external orchestration system, but only the vehicle-side capabilities required to support such interaction.

## 3. General Idea

The proposed Vehicle External Interface for Control (VEIC) defines a state-oriented interaction model, where:

* the vehicle exposes selected current system state and capabilities
* external systems may provide desired states, such as payloads, configurations and AI capabilities
* the vehicle runtime evaluates and enforces these inputs under local safety and policy rules

This approach ensures that:

* vehicles from different manufacturers can expose a consistent interaction model
* external systems can interact with vehicles in a standardized and safe manner
* all control remains subject to vehicle-side validation and override

### Expected Changes ot work products

- [ ] Requirements
- [ ] Architecture
- [ ] Safety Analysis
- [ ] Security Analysis
- [ ] Detailed Design
- [ ] Implementation and Testing
- [x] all

### Impact analysis

VEIC is an incremental extension to the S-CORE platform that introduces a standardized vehicle-side interface for external interaction. It augments existing components with control, state reporting, and policy enforcement hooks without modifying their core behavior.

By enabling a consistent interaction model across vehicles, VEIC supports scalable multi-vehicle scenarios and serves as a key enabler for large-scale adoption of S-CORE in fleet-based deployments. The proposal integrates with existing modules such as lifecycle management, IPC, and security, without requiring fundamental architectural changes, while preserving vehicle-side autonomy and safety constraints.

### Safety or Security relevance

- [ ] none
- [ ] Safety relevant
- [x] Security relevant

### Expected required ASIL classification

QM

### Expected Implementation Version (Release)

1.0

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.