Testing Services

SOME/IP Testing Guide - AUTOSAR Adaptive Middleware Validation

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

SOME/IP testing guide AUTOSAR

WHAT IS SOME/IP TESTING?

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.

KEY SOME/IP CONCEPTS

What SOME/IP Testing Must Cover

SOME/IP's service-oriented model creates specific validation requirements beyond traditional message-based protocols.

Service Discovery (SD)

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.

Method Calls (Request/Response)

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.

Event Subscriptions

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 Serialisation

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 SOME/IP AGENTS

Agent
DoIP Client Agent
Hardware Required
None - PC Ethernet
Hardware Required
Send DoIP vehicle announcement, routing activation, and diagnostic requests over Ethernet - essential for EV and ADAS ECU validation.
Agent
DoIP Server Agent
Hardware Required
None - PC Ethernet
Hardware Required
Simulate a DoIP gateway - test tester tools and diagnostic clients against a controlled virtual Ethernet ECU.
Agent
UDS over DoIP Client Agent
Hardware Required
None - PC Ethernet
Hardware Required
Run full UDS ISO 14229 diagnostic sequences transported over DoIP Ethernet - next-generation ECU diagnostics for domain controllers and EV platforms.
Agent
UDS over DoIP Server Agent
Hardware Required
None - PC Ethernet
Hardware Required
Simulate an Ethernet ECU responding to UDS diagnostic requests over DoIP - validate diagnostic clients without real vehicle hardware.
Agent
SOME/IP Client Agent
Hardware Required
None - PC Ethernet
Hardware Required
Call SOME/IP services, subscribe to events, and validate AUTOSAR Adaptive middleware communication on domain controllers and central compute units.
Agent
SOME/IP Server Agent
Hardware Required
None - PC Ethernet
Hardware Required
Simulate an AUTOSAR Adaptive service provider - offer SOME/IP services and publish events to validate client devices and gateways.
Agent
XCP Server Agent (Ethernet)
Hardware Required
None - PC Ethernet
Hardware Required
Simulate an XCP slave over Ethernet - high-speed calibration and DAQ measurement workflows for Ethernet-connected ECUs.
TEST SCENARIOS

SOME/IP Test Scenarios With TestBot

ScenarioAgents UsedValidated Outcome
Service Discovery ValidationSOME/IP Client Agent - FindService + SD monitorService found within 1s, OfferService message received with correct service ID and version
Method Call Request/ResponseSOME/IP Client Agent - method invocation + response assertMethod response received within timeout, payload deserialised correctly, return code 0x00
Event Subscription + NotificationSOME/IP Client Agent - SubscribeEventGroup + event monitorSubscription acknowledged, events received at correct rate with correct payload
Service Restart BehaviourSOME/IP Client Agent - StopOfferService + re-findClient detects service stop, re-subscribes after service restart, no data loss
Domain Controller IntegrationSOME/IP Server Agent (service simulation)ECU under test correctly discovers simulated service, calls methods, receives events
Multi-Client ScenarioSOME/IP Server Agent + 2× SOME/IP ClientServer delivers events to all subscribers simultaneously; unicast and multicast paths validated

Frequently Asked Questions - SOME/IP Testing

SOME/IP testing FAQ

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.

Continue Learning

RELATED GUIDES

Test SOME/IP Service Middleware - Zero Hardware

SOME/IP Client and Server agents over PC Ethernet. 14-day free trial.