SOME/IP Protocol

SOME/IP Overview

SOME/IP is a communication protocol primarily used in automotive and other embedded systems. It facilitates communication between electronic control units (ECUs) within a networked environment. The protocol is built on top of the Internet Protocol (IP) stack, making it suitable for use in IP-based networks.

Embien’s SOME/IP stack covers all the services defined as part of the AUTOSAR standard specification, enabling communication between ECUs. Our SOME/IP stack is implemented on top of the Internet Protocol (IP) stack.

Some of the salient features of RAPIDSEA SOME/IP protocol stack are

  • Support for both server mode and client mode

  • ISO-TP layer with up to 4095 bytes transfer support

  • MISRA-C compliant ANSI C source code

  • Can be used with or without RTOS

  • Can support 8, 16, 32, 64-bit CPUs

The implementation is fully configurable and are offered for both server and client mode of operation.

SOME/IP Model

Supported Services

1. Service Discovery (SD)

  • Automatically announces and discovers services and instances on the network.

  • Handles service availability and offers/requests using multicast messages.

  • Key features include:

    • Service offer/request announcements.

    • Service version and instance management.

    • Subscription to event groups.

2. Message Serialization and Deserialization

  • Encodes and decodes data for communication between client and server.

  • Supports multiple data types such as arrays, structures, and basic data types.

  • Ensures compatibility between different system components.

3. Remote Procedure Call (RPC)

  • Facilitates remote invocation of services and methods over IP.

  • Supports synchronous and asynchronous communication patterns.

4. Event Notification

  • Provides mechanisms for servers to notify clients of changes or updates via events.

  • Supports subscription-based notification for specific event groups.

5. Event Group Handling

  • Groups related events together for efficient subscription and notification.

  • Allows clients to subscribe to specific event groups for tailored data updates.

SOME/IP Server

SOME/IP server is typically implemented in the ECUs so that the client can connect to it and perform data tranfer operations on the same. RAPIDSEA implements the SOME/IP server with the following features.

  • Support for all the services

  • Modular and extensible design

  • Portable across architectures

The SOME/IP Server stack implementation is covered in detail in the SOME/IP Server Stack page.

SOME/IP Client

RAPIDSEA implements SOME/IP client where service discovery process, Request and response can be performed on the ECUs. APIs are provided to perform services on the server with high level of control and performance.RAPIDSEA implements the SOME/IP client with the following features.

  • Support for all the services

  • Modular and extensible design

  • Portable across architectures

The SOME/IP Client stack implementation is covered in detail in the SOME/IP Client Stack page.

SOME/IP Header Details

Documentation from the relevant header as follows:

Warning

doxygenfile: Cannot find file “rs_someip.h