Service discovery, method calls, event subscriptions - what SOME/IP testing covers for domain controllers and central compute units. No hardware required.

SOME/IP (Scalable service-Oriented MiddlewarE over IP) testing is the validation of AUTOSAR-compliant service middleware communication over Ethernet - verifying that ECUs correctly offer and consume services via SOME/IP Service Discovery, invoke and respond to method calls, and publish and subscribe to event notifications.
SOME/IP is the inter-process communication middleware defined by AUTOSAR for Adaptive Platform ECUs - the domain controllers, central compute units, and zonal ECUs that replace multiple CAN-based ECUs in next-generation vehicle architectures. Every EV and ADAS platform built on AUTOSAR Adaptive uses SOME/IP for ECU-to-ECU communication.
What SOME/IP testing covers: Service Discovery (offer/find/subscribe sequences), method invocation (request/response, fire-and-forget), event notification delivery and filtering, error handling, and multi-instance service scenarios. Like DoIP, all SOME/IP testing runs over standard Ethernet - zero hardware required beyond a network cable.
SOME/IP's service-oriented model creates specific validation requirements beyond traditional message-based protocols.
SOME/IP SD allows ECUs to find each other's services dynamically. Testing validates: service offering (OfferService), service finding (FindService), stop-offer behaviour, and that subscribing clients receive event notifications only after successful subscription.
SOME/IP methods follow a request/response pattern with session IDs. Testing validates: correct session ID handling, method payload encoding (SOME/IP serialisation), return code validation, and timeout behaviour for unavailable services.
SOME/IP events are published by servers and consumed by subscribers. Testing validates: EventGroup subscribe/unsubscribe, correct multicast vs unicast delivery, event payload content, and re-subscription after service restart.
SOME/IP uses its own serialisation format for method payloads and event data. Testing validates that data types - integers, strings, arrays, structs - are correctly serialised and deserialised according to the AUTOSAR ARXML interface definition.
TestBot's SOME/IP Client Agent subscribes to services and invokes methods. The SOME/IP Server Agent offers services and publishes events. Both run over your PC Ethernet port - no hardware required.
| Scenario | Agents Used | Validated Outcome |
|---|---|---|
| Service Discovery Validation | SOME/IP Client Agent - FindService + SD monitor | Service found within 1s, OfferService message received with correct service ID and version |
| Method Call Request/Response | SOME/IP Client Agent - method invocation + response assert | Method response received within timeout, payload deserialised correctly, return code 0x00 |
| Event Subscription + Notification | SOME/IP Client Agent - SubscribeEventGroup + event monitor | Subscription acknowledged, events received at correct rate with correct payload |
| Service Restart Behaviour | SOME/IP Client Agent - StopOfferService + re-find | Client detects service stop, re-subscribes after service restart, no data loss |
| Domain Controller Integration | SOME/IP Server Agent (service simulation) | ECU under test correctly discovers simulated service, calls methods, receives events |
| Multi-Client Scenario | SOME/IP Server Agent + 2× SOME/IP Client | Server delivers events to all subscribers simultaneously; unicast and multicast paths validated |

SOME/IP (Scalable service-Oriented MiddlewarE over IP) is the service communication middleware defined by AUTOSAR for Adaptive Platform ECUs. It enables ECUs to offer and consume services over Ethernet using a service-discovery mechanism, method call pattern, and event notification model. It is used in domain controllers, central compute units, and connected ECUs in EV and ADAS platforms.
SOME/IP Client and Server agents over PC Ethernet. 14-day free trial.