#S2S-API #vehicle-API #Service Oriented Architecture #Mobility System Architecture

Open In-vehicle API

Making software complexity manageable.

Vehicle functions are becoming more and more complex. The vehicles of the future are constantly linked to the cloud, and need new cloud-based development paradigms. The “API-principle” is one of them and makes the complex automotive software manageable by introducing vehicle-compatible interfaces and bundling software appropriately.

Cost-efficiency

through software development that is independent from middleware and hardware.

Increased software sustainability

through re-use over several vehicle platforms.

Flexible and fast

fleet roll-out which supports on-demand field upgrades.

Mobility System Architecture (MSA) extends E/E-architecture to the cloud

The increasing connectivity of the vehicle computers to the cloud makes the vehicle an integrated part of the internet. This makes new vehicle functions possible as the much cheaper computing servers in the cloud are used. The classic E/E architecture is therefore being expanded to include the connectivity layers and the cloud layers.

This can be used to describe the approaching development from domain-centralized E/E architectures to domain-fusion architectures and to vehicle-centralized architectures with a strong cloud component. The result is a new mobility ecosystem.

The Mobility System Architecture (MSA) extends the E/E-architecture to the cloud.

An open standard for successive APIs

The API-stack of the Mobility System Architecture.

The rapidly increasing complexity of automotive features will lead to the introduction of Application Programming Interfaces (APIs) and thereby reduce overall complexity. Three main APIs will emerge.

1) Cloud-to-DigitalTwin API
2) Vehicle-to-Cloud API
3) Signal-to-Service API

All three APIs will be based on the open COVESA standard. In the following section we will focus on the Signal-to-Service API.

In-vehicle Signal-to-Service API

The Signal-to-Service API provides the vehicle signals in an open and standardized way to the apps.

The Signal-to-Service API is a programming interface in the vehicle computer that standardizes all necessary interfaces and minimizes adaptation costs. Technically speaking, the application software is abstracted from the middleware/operating system. The API converts the proprietary CAN signals into standardized communication services. This is why this API is also called Signal-to-Service API.

Thanks to the familiar and standardized interfaces, the Signal-to-Service API allows the application software to be enriched with new functions in the field. This has three main advantages:

The costs for new software are reduced thanks to reduced customization efforts.
Software becomes more sustainable and independent from the vehicle.
New functions are available more quickly and can be added after the vehicle has been purchased.

Existing open-source tools (e.g. digital.auto from Eclipse SDV) are already facilitating modern app development.

Open, safe real-time APIs

The secure and access-protected "smartphone on wheels" allows software to be rolled out simultaneously on different vehicle platforms.

The Signal-to-Service API must also meet high vehicle requirements. In particular, these include security aspects and fast response times. The API should be able to make functions portable without massively impairing the response time requirements of control algorithms.

We are cooperating with COVESA and AUTOSAR to establish an open, global standard for this API. Thanks to an open API, the vision of a secure and access-protected “smartphone on wheels” can become a reality. The open standard foresees an access rights concept so that the respective software blocks can only read the signals for which they are enabled. Unauthorized writing access is also controlled and blocked if necessary, so that the driver has the steering wheel safely under control even on the freeway.

The open, secure, and fast API is an essential building block for future vehicle software and brings us a good deal closer to the wide range of software we know from smartphones.

Product benefits

Future-proof software development
Faster software development and roll-out

Reduction of software integration costs
Increased software portability across different vehicle platforms

Contact us

Sales inquiries
Bosch Mobility

Are you interested in our solutions? Then write us a message. Our sales team will be happy to help you.

Start enquiry

Open In-vehicle API

Making software complexity manageable.

Cost-efficiency

Increased software sustainability

Flexible and fast

Mobility System Architecture (MSA) extends E/E-architecture to the cloud

An open standard for successive APIs

In-vehicle Signal-to-Service API

Open, safe real-time APIs

Contact us

Sales inquiries
Bosch Mobility

LinkedIn channel

YouTube channel

Open In-vehicle API

Making software complexity manageable.

Cost-efficiency

Increased software sustainability

Flexible and fast

Mobility System Architecture (MSA) extends E/E-architecture to the cloud

An open standard for successive APIs

In-vehicle Signal-to-Service API

Open, safe real-time APIs

Contact us

Sales inquiriesBosch Mobility

LinkedIn channel

YouTube channel

Further interesting topics

The E/E architecture of the future

Bosch software-defined vehicle

Platform for innovations - the connected vehicle

Sales inquiries
Bosch Mobility