Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

SOME/IP-TP Purpose: Beyond Single UDP Datagram

TransportMax PayloadSOME/IP-TP Needed?
UDP single datagram65507 bytesNo — base SOME/IP sufficient
Camera image (1080p compressed)~300 KBYes — SOME/IP-TP segmentation
FOTA software package~50 MBYes — SOME/IP-TP with large offset field
UDS ReadMemoryByAddress (large ECU)Up to 0xFFD bytesYes for large responses

SOME/IP-TP Segment Structure

SOME/IP-TP Segment Layout
  Standard SOME/IP 16-byte header (same Service/Method/Client/Session IDs)
  ├── Message Type bit 5 set (TP flag)
  └── Length includes TP header size

  SOME/IP-TP Header (4 bytes, immediately after SOME/IP header):
  Bits [31:4] = Offset (in 16-byte units from start of reassembled payload)
  Bits  [3:1] = Reserved (0)
  Bit      0  = More_Segments flag (1 = more follow, 0 = last segment)

  Example: 1500-byte UDP with 1400 bytes of TP payload:
  Segment 0: Offset=0, More=1, 1400 bytes
  Segment 1: Offset=87 (87×16=1392), More=1, 1400 bytes (some overlap possible)
  Segment 2: Offset=174, More=0, remaining bytes → reassembly complete

Reassembly Logic

Pythonsomeiptp_reassemble.py
# SOME/IP-TP reassembler
class SomeIpTpReassembler:
    def __init__(self, timeout_ms=500):
        self.sessions = {}   # (client_id, session_id) → segment list
        self.timeout_ms = timeout_ms

    def receive_segment(self, client_id, session_id, offset_units, more_seg, payload):
        key = (client_id, session_id)
        if key not in self.sessions:
            self.sessions[key] = {"segments": {}, "complete": False}

        byte_offset = offset_units * 16
        self.sessions[key]["segments"][byte_offset] = payload

        if not more_seg:
            self.sessions[key]["last_offset"] = byte_offset + len(payload)
            return self._try_reassemble(key)
        return None

    def _try_reassemble(self, key):
        session = self.sessions[key]
        if "last_offset" not in session:
            return None  # haven't seen last segment yet

        # Sort by offset and check for gaps
        sorted_segs = sorted(session["segments"].items())
        reassembled = bytearray()
        expected_offset = 0
        for offset, data in sorted_segs:
            if offset != expected_offset:
                print(f"Gap at offset {expected_offset} (got {offset}) — incomplete")
                return None  # gap → wait for missing segment or timeout
            reassembled.extend(data)
            expected_offset += len(data)

        del self.sessions[key]
        return bytes(reassembled)

AUTOSAR SomeIpTp Configuration

XMLSomeIpTp_Config.arxml


  SomeIpTp_CameraStream
  
    
      0  
      1400  
    
    
      500  
    
  

Summary

SOME/IP-TP extends base SOME/IP beyond single UDP datagram limits using a 4-byte offset+More_Segments header. The Offset field (in 16-byte units) enables out-of-order reassembly — segments can arrive in any order and the receiver fills in the buffer by offset. The RX timeout discards stale incomplete messages and frees the reassembly buffer. Set SomeIpTpMaxSegmentLength to 1400 bytes to leave headroom for Ethernet + IP + UDP + VLAN headers within the 1500-byte MTU.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousSerialization & DeserializationNext →Hands-On: SOME/IP Service Implementation