SOME/IP-TP for Segmentation - Automotive Ethernet

Why SOME/IP-TP: The UDP Size Limit

Transport	Max SOME/IP Payload	Fragmentation	Use Case
UDP (no TP)	~65 507 bytes (IP limit)	IP fragmentation (unreliable over switches)	Small payloads: control, sensor values
UDP + SOME/IP-TP	Unlimited (segmented)	SOME/IP-TP segments; application reassembles	LiDAR point clouds (1–5 MB), OTA chunks
TCP	Unlimited (stream)	TCP handles segmentation transparently	Reliable large transfers: OTA, configuration download
UDP fragmentation (avoid)	~65 507 bytes	IP layer; any fragment lost → entire datagram lost	Not recommended: packet loss causes full retransmit

SOME/IP-TP Segmentation Header

SOME/IP-TP Header: Extra 4 Bytes

  Standard SOME/IP header (16 bytes): same as always
  Message Type bit 5 = 1 → indicates TP segmented message
  (e.g., 0x20 = TP Request, 0x22 = TP Notification)

  Immediately after the 16-byte SOME/IP header:
  ┌─────────────────────────────────────┬────────┐
  │  Offset (28 bits)                   │  More  │
  │  Byte offset of this segment in the │  Frags │
  │  complete reassembled payload        │  (1b)  │
  └─────────────────────────────────────┴────────┘
  4 bytes total; offset in multiples of 16 bytes

  First segment: offset = 0, More = 1
  Middle segments: offset = N*16, More = 1
  Last segment: offset = M*16, More = 0

  Segment size: limited by MTU; typical = 1392 bytes payload
  (1500 MTU - 20 IP - 8 UDP - 16 SOME/IP - 4 TP header = 1452 bytes payload)

Reassembly and Timeout Handling

C++someip_tp_reassembly.cpp

// SOME/IP-TP reassembly: collect segments, reassemble in order
#include 
#include 
#include 

struct TpSession {
    std::map> segments;  // offset → data
    std::chrono::steady_clock::time_point first_seen;
    bool complete = false;
};

std::map g_tp_sessions;  // keyed by session_id
constexpr auto TP_TIMEOUT = std::chrono::seconds(5);

void receive_tp_segment(uint32_t session_id, uint32_t offset,
                         bool more_fragments, const uint8_t *data, size_t len)
{
    auto &session = g_tp_sessions[session_id];
    if (session.segments.empty()) {
        session.first_seen = std::chrono::steady_clock::now();
    }

    session.segments[offset] = std::vector(data, data + len);

    if (!more_fragments) {
        // Attempt reassembly: check all offsets are contiguous
        std::vector full_payload;
        uint32_t expected = 0;
        for (auto &[off, seg] : session.segments) {
            if (off != expected) { /* gap detected: drop session */ return; }
            full_payload.insert(full_payload.end(), seg.begin(), seg.end());
            expected = off + static_cast(seg.size());
        }
        session.complete = true;
        process_complete_message(full_payload);
        g_tp_sessions.erase(session_id);
    }
}

void cleanup_stale_tp_sessions() {
    auto now = std::chrono::steady_clock::now();
    for (auto it = g_tp_sessions.begin(); it != g_tp_sessions.end(); ) {
        if (now - it->second.first_seen > TP_TIMEOUT) {
            it = g_tp_sessions.erase(it);
        } else { ++it; }
    }
}

Summary

SOME/IP-TP is used when payload size exceeds what fits comfortably in a single UDP datagram over a non-jumbo-frame network (typically payloads > 1400 bytes). The primary automotive use cases are LiDAR point cloud transmission and OTA chunk delivery. TCP is a simpler alternative for large reliable transfers — the choice depends on whether the application needs the low-overhead, unordered delivery of UDP-TP or the reliability and flow control of TCP. AUTOSAR SOME/IP-TP configuration: set SomeIpTpMaxSegmentLength in ARXML; the stack handles segmentation and reassembly automatically.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.