What it is
The Vehicle Signal Specification (VSS) is COVESA’s open rule set and standard catalog for naming vehicle data. It gives services one shared tree of signals, so a speed, a door state, or a cabin temperature has the same path and the same meaning in every API that adopts the catalog.
The tree is a hierarchy. Branch nodes group related signals, such as the body, the cabin, or the powertrain. Leaf nodes are the data points. A leaf is a sensor (a measured value), an actuator (a value a client may request to change), or an attribute (a property that changes rarely). Each leaf has a datatype, a unit where a unit applies, and a description. The signal’s name is the dot-separated path from the root to that leaf.
Two artifacts are maintained together. The specification states how nodes, datatypes, units, and metadata are written. The standard catalog is the tree COVESA maintains for common passenger-car signals. Projects add their own signals with an overlay or a private branch so the shared paths stay stable.
Who it applies to
VSS applies wherever vehicle data crosses a software boundary: in-vehicle service APIs, a cockpit or high-performance computer exposing data to applications, and the feed from the vehicle to a cloud backend. E/E architects decide where the tree sits in the service-oriented architecture. Software teams implement and call it. Platform teams map it onto the signals the ECUs already produce.
What it covers
VSS covers the vocabulary of vehicle data: the shape of the tree, the kinds of leaves, and the metadata a consumer needs to interpret a value.
| Topic | Role in the specification |
|---|---|
| Tree and paths | Branch and leaf nodes, named by a dot-separated path |
| Leaf roles | Sensors, actuators, and attributes |
| Metadata | Datatype, unit, description, and optional constraints such as allowed values |
| Standard catalog | A shared set of passenger-car signals maintained with the rules |
| Extension | Overlays and private branches for signals outside the shared catalog |
| Instances | A consistent way to index repeated parts, such as doors, seats, and axles |
Name, type, unit, and description are the content of a leaf. Bus frame layout, transport, sampling, authentication, and safety integrity belong in the interface specification, the security concept, and the safety case that sit beside the catalog.
How it fits with other documents
In COVESA’s common vehicle interface work, VSS is the data model. API specifications define how a client reads or writes a path. The W3C Vehicle Information Service Specification is the widely used companion: it defines a service for vehicle data and identifies each signal with a VSS path. Projects also expose the same tree through query interfaces and message topics, so one catalog can serve more than one transport.
AUTOSAR and the in-vehicle bus specifications define how ECUs exchange signals on the network. At the service boundary, a platform maps those signals onto leaves. Off the vehicle, ISO extended-vehicle standards govern remote access to vehicle data, and deployments use the VSS catalog as the vocabulary under those access rules.
In practice
Pin a release of the rules and a release of the catalog, and record both in the interface specification. Start from the standard tree and add a small overlay for brand-specific signals. Leave standard paths unchanged so existing clients keep working.
Agree the path, datatype, and unit before agreeing the transport. State which actuators a service may set and which leaves are measurements. Review a new leaf as an API addition: it is a promise to every consumer of the tree.
When a leaf mirrors a safety-relevant value or personal data, the safety case and the security concept say who may rely on it and who may see it. The catalog entry supplies the shared name and meaning. If you are unsure which release is in force, check the current edition from COVESA and match it to the version the build vendors.