Service-Oriented Architecture in Autosar

Hello Readers,

My name is Nithyanand T, and I work at Luxoft India as a Junior Software Developer. Luxoft has given me several opportunities to work on various projects, which has inspired me to learn the essential processes involved in developing AUTOSAR Modulеs and Add-Ons in Service-Oriented Architecture in Autosar .

Service-Oriented Architecture

Service-oriented architecture (SOA) is a modern software architecture paradigm for building applications as a collection of software units called services. In SOA, offerings are self-contained, modular, and loosely coupled. This approach allows you to build complex and distributed applications where you can update individual components instead of entire monolithic applications. A typical SOA software package includes an application that includes services, platform services, and middleware. These services run on high-performance hardware or a virtual machine.

Service-Oriented Communication (SOC)

SOA-based applications use service-oriented interfaces for service-oriented communication to provide and use functions to exchange information through messages. Services act as clients or servers in SOA. Each client or server service is implemented as part of the software. The connection points between client and server components are known as client/server ports, which make up the service-oriented interfaces.

To facilitate data exchange, the client and server components use different service-oriented communication models, such as publish-state, request-response, and fire-forget. These patterns can be asynchronous or periodic, which is a key feature of SOC. Event-based modeling can be done using Stateflow and SimEvents. In addition, the Messages & Events library in Simulink® enables you to model, simulate, and generate C++ code for applications using message-based communication.

SOA Workflow

A model-driven design workflow enables you to build service-oriented applications:

Specifying requirements with Requirements Toolbox
Authoring SOAs using System Composer Modeling and simulating services and components in Simulink Importing existing services and components for reuseGenerating C++ production code with Embedded Coder® Integrating the full SOA application
Deploying SOA applications to edge devices and the cloud SOA in Automotive SOAs are most common in the automotive industry with Software Defined Vehicles (SDVs).

SDV integrates both signal-based and service-oriented applications into newer EE architectures with vehicle computers and zone controllers. With System Composer and Simulink, developers can model SOAs, simulate them, and generate C++ production code before deploying them as modular services to edge devices and the cloud.

In addition, these services can be wirelessly updated with software updates throughout the life of the vehicle to improve the customer experience. SOAs are included in both the above-mentioned industry standards and in-house frameworks.

Use Cases for SOA

In software-based systems that include autonomy, connectivity and electrification, service-oriented architecture plays a crucial role as a foundation. SOAs are also used to build systems, multi-agent systems, discrete event systems, and distributed systems in the automotive, aerospace, industrial automation and Internet of Things, medical device, and robotics industries.

To support these industries, software architecture frameworks, middleware standards and communication protocols based on service-oriented architecture and service-oriented communication have appeared. Examples of these frameworks and standards are AUTOSAR Adaptive, DDS, ROS/ROS2, FACE, SOME/IP, MOSA, MQTT and OPC UA.

In a service-oriented architecture, communication between services takes place with clearly defined interfaces at the SW level, i.e. by middleware. The middleware supports abstraction of the specific HW environment and greatly simplifies software development and testing. This provides the foundation for a truly distributed development environment that can and does collaborate with third parties. Automotive SOA takes the basic SOA concept of service providers and service consumers and transforms them into an automotive software environment. Each ECU uses layers of abstraction to hide network topology, communication and implementation complexity. Interactions between software components are therefore no longer coded. Each new service is represented in a directory where you can propose its functions and find the services you need. The relationship between services is not fixed and can be changed dynamically. Each ECU supported by the hypervisor can run several different operating systems in parallel: popular operating systems such as Windows, MacOS, iOS, Android, etc. can support installing standard applications and third-party applications.

While downloading malicious or buggy apps to a smartphone can affect the functionality of the smartphone or the user's privacy, downloading such inappropriate apps to the car can affect driving safety and have fatal consequences.

Therefore, communication between services is limited to mandatory interactions. Everything else is blocked. Highly secure SWC OTA download and deployment prevents malicious or unintended attack vectors from affecting your car's security.

Conclusion

In this Article I have tried to explain about the Significance of in Service-Oriented Architecture Autosar, Please let me know if any improvements needs to be done Thank you.