TC8 Conformance Test Requirements#

Overview#

This document defines the requirements for verifying someipd against the OPEN Alliance TC8 SOME/IP test specification.

It belongs to a set of three documents that work together:

Table 4 TC8 Conformance Documentation Set#

Document

Purpose

requirements.rst (this file)

Defines what must be verified: one feature requirement and multiple component requirements, each linked to the S-CORE requirement hierarchy.

TC8 Test Specifications

Defines how each test runs: purpose, preconditions, stimuli, and expected results.

TC8 Conformance Traceability

Maps external OA spec test case IDs to internal test IDs and component requirements, and shows generated test results.

How the feature / component split works for TC8#

For TC8 conformance, the split is simple:

  • One feature requirement (feat_req__tc8_conformance__conformance) covers the overall goal: “verify someipd against OA TC8 SOME/IP at the wire level.” This requirement does not change when new test areas are added.

  • Many component requirements, one per testable protocol aspect (e.g., SD offer format, cyclic timing, response headers, TCP transport). Each component requirement:

    • Describes the specific behaviour under test.

    • References the relevant AUTOSAR PRS or TC8 specification section.

    • Is verified by one or more pytest functions.

Feature Requirement#

The following feature requirement establishes TC8 SOME/IP conformance testing as a formal verification activity for the SOME/IP Gateway’s protocol stack.

TC8 SOME/IP Protocol Conformance
status: valid
security: NO
safety: QM

The SOME/IP Gateway project shall verify protocol conformance of its SOME/IP stack (someipd) against OPEN Alliance TC8 SOME/IP test specifications at the wire protocol level, without requiring application processes.

Scope boundary: This document currently defines only the top-level feature requirement and the initial set of TC8 component requirements established for the test infrastructure split. The remaining component requirements, covering method calls, field access, and the detailed traceability matrix against the OA TC8 v3.0 Chapter 6 test catalog, are added together with the test modules that implement and verify them.

Component Requirements: Service Discovery#

The following component requirements define the high-priority TC8 conformance tests for SOME/IP Service Discovery (SD), aligned with SOME/IP-SD Protocol Specification (AUTOSAR PRS_SOMEIP_SD).

TC8 SD Offer Entry Format Validation
status: valid
security: NO
safety: QM

The conformance test suite shall verify that someipd transmits SOME/IP-SD OfferService entries on the configured multicast group with correct service ID, instance ID, major/minor version, and TTL fields upon startup.

Note: Traces to AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, section 5.1.2.5.2 (Offer Service Entry).

TC8 SD Cyclic Offer Timing
status: valid
security: NO
safety: QM
tags: tc8, conformance, service_discovery, timing
reqtype: Functional
version: 1

The conformance test suite shall verify that, in the main phase, two consecutive OfferService messages of someipd are cyclic_offer_delay apart within the OA ParamToleranceTime.

Note: Traces to OA TC8 SOMEIPSRV_SD_BEHAVIOR_02.

TC8 SD Multicast Response to FindService
status: valid
security: NO
safety: QM

The conformance test suite shall verify that someipd answers a FindService with a multicast OfferService, as defined by the OA tests for a FindService received after half of cyclic_offer_delay and for a FindService with the Unicast Flag cleared.

Note: Traces to OA TC8 SOMEIPSRV_SD_BEHAVIOR_03 and SOMEIPSRV_SD_BEHAVIOR_04.

TC8 SD FindService Response
status: valid
security: NO
safety: QM

The conformance test suite shall verify that someipd responds to a SOME/IP-SD FindService entry with a unicast OfferService for a known service, and does not respond for an unknown service.

Note: Traces to AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, section 5.1.4.2 (Server Answer Behavior).

TC8 SD Subscribe Eventgroup Lifecycle
status: valid
security: NO
safety: QM

The conformance test suite shall verify that someipd correctly handles the SubscribeEventgroup lifecycle: acknowledge valid subscriptions (SubscribeEventgroupAck), reject unknown eventgroups (SubscribeEventgroupNack with TTL=0), honor StopSubscribeEventgroup by ceasing notifications, and clean up expired subscriptions after the subscription TTL elapses.

Note: Traces to AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, sections 5.1.3.1.1 (Subscribe Eventgroup Entry, including TTL), 5.1.3.1.2 (Stop Subscribe Eventgroup Entry), 5.1.3.1.3 (Subscribe Eventgroup Acknowledgement), and 5.1.3.1.4 (Subscribe Eventgroup Negative Acknowledgement).

TC8 SD Subscription TTL Expiry
status: valid
security: NO
safety: QM
tags: tc8, conformance, service_discovery, eventgroup, timing
reqtype: Functional
version: 1

The conformance test suite shall verify that event notifications cease to arrive after the subscription TTL expires: when a tester subscribes with TTL = 3 and no renewal is sent, no further SOME/IP notifications shall be received beyond 2 seconds after the TTL expiry, conforming to OA TC8 SOMEIP_ETS_095.

TC8 SD Initial Delay and Repetitions Phase
status: valid
security: NO
safety: QM
tags: tc8, conformance, service_discovery, timing
reqtype: Functional
version: 1

The conformance test suite shall verify that someipd doubles the delay between offers in the Repetition Phase: the first gap is shorter than half of cyclic_offer_delay and the second gap is twice repetitions_base_delay within the OA tolerance.

Note: Traces to OA TC8 SOMEIPSRV_SD_BEHAVIOR_01 (Repetition Phase delay doubling). The offer count (repetitions_max), the initial wait delay and the main phase transition are not defined by this OA test and are out of scope.

TC8 SD IPv4 Endpoint Option Validation
status: valid
security: NO
safety: QM
tags: tc8, conformance, service_discovery
reqtype: Functional
version: 1

The conformance test suite shall verify that someipd includes a valid IPv4EndpointOption in OfferService SD entries, carrying the correct unicast address, port, and L4 protocol (UDP) so that clients can reach the offered service.

Note: Traces to AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, section 5.1.2.4.3 (IPv4 Endpoint Option).

TC8 SD Reboot Detection
status: valid
security: NO
safety: QM

The conformance test suite shall verify that someipd resets its SD state upon restart: the reboot flag (SD flags byte bit 7) shall be set in the first SD message after restart, and the SD session ID shall reset to a low value (≤ 2).

Note: Traces to AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, section 5.1.2.2 (SOME/IP-SD Header, Reboot Flag and Session ID handling).

TC8 SD Multicast Eventgroup Option
status: valid
security: NO
safety: QM
tags: tc8, conformance, service_discovery, multicast
reqtype: Functional
version: 1

The conformance test suite shall verify that someipd includes a multicast IPv4EndpointOption in the SubscribeEventgroupAck for eventgroups configured with a multicast address, so that clients know which multicast group to join for event delivery.

Note: Traces to AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, section 5.1.3.1.3 (Subscribe Eventgroup Acknowledgement Entry, multicast endpoint option).

Component Requirements: SOME/IP Message Format#

TC8 SOME/IP Response Header Validation
status: valid
security: NO
safety: QM
tags: tc8, conformance, message_format
reqtype: Functional
version: 1

The conformance test suite shall verify that someipd returns SOME/IP RESPONSE messages with correct protocol version (0x01), message type (0x80), matching session ID, and matching client ID for each received REQUEST.

Note: Traces to AUTOSAR SOME/IP Protocol Specification R24-11, sections 4.1.2.5 (Protocol Version), 4.1.2.7 (Message Type), and 4.1.2.4 (Request ID, Client ID / Session ID).

TC8 SOME/IP Error Return Codes
status: valid
security: NO
safety: QM
tags: tc8, conformance, message_format, error_handling
reqtype: Functional
version: 1

The conformance test suite shall verify that someipd returns the correct SOME/IP return codes for error conditions: E_UNKNOWN_SERVICE (0x02) for requests to non-existent services, E_UNKNOWN_METHOD (0x03) for invalid method IDs, and E_WRONG_INTERFACE_VERSION for interface version mismatches.

Note: Traces to AUTOSAR SOME/IP Protocol Specification R24-11, section 4.1.2.8 (Return Code) and section 4.2.6.1 (Return Codes, requirement PRS_SOMEIP_00191).

Component Requirements: Event Notification#

TC8 Event Notification Subscription Lifecycle
status: valid
security: NO
safety: QM
tags: tc8, conformance, events, notification
reqtype: Functional
version: 1

The conformance test suite shall verify that someipd delivers NOTIFICATION messages (message type 0x02) with correct event ID only to endpoints with an active eventgroup subscription, and ceases delivery after StopSubscribeEventgroup.

Note: Traces to AUTOSAR SOME/IP Protocol Specification R24-11, section 4.2.4 (Notification Events), and AUTOSAR SOME/IP Service Discovery Protocol Specification R24-11, section 5.1.3.1.1 (Subscribe Eventgroup Entry).