Time-Aware Shaper - Scheduled Traffic - Automotive Ethernet

Time-Aware Shaper (TAS): Gate Control List

GCL: Gate Control List for a 1 ms Cycle

  Port cycle: 1000 µs (1 ms); all queues Q0–Q7

  Gate Control List entry format: [operation, gate_states, time_interval]
  Operation S = SetGates (set which queues are open)

  GCL example (1 ms cycle on downstream port):
  ┌─────────────┬──────────────────────┬────────────────────────────┐
  │ Interval    │ Gates Open           │ Purpose                    │
  ├─────────────┼──────────────────────┼────────────────────────────┤
  │ 0–50 µs     │ Q7 only              │ Safety: brake/steering cmd │
  │ 50–150 µs   │ Q6, Q5              │ Video/signalling burst      │
  │ 150–900 µs  │ Q4, Q3, Q2, Q1, Q0 │ Best-effort + OTA          │
  │ 900–1000 µs │ Q7 only              │ Second safety window       │
  └─────────────┴──────────────────────┴────────────────────────────┘

  Guard band: inserted before Q7 gate opens to prevent large frame spillover
  Guard band = max_interfering_frame_size / link_rate
  e.g., 1500 bytes at 100 Mbit/s = 120 µs guard band required

  With guard band: Q7 window starts 120 µs early (closed to Q0–Q6)
  → Q0 cannot start a new 1500-byte frame within 120 µs of Q7 gate opening

TAS Configuration via NETCONF/YANG or AUTOSAR

XMLtas_config.xml





  port0
  
    
      1
      1000  
    
    0   
    0xFF  

    
      
      
        Set-And-Hold-MAC
        50000  
        0x80  
      

      
      
        Set-And-Hold-MAC
        100000
        0x60  
      

      
      
        Set-And-Hold-MAC
        850000
        0x1F

Worst-Case Latency Calculation

Pythonwcl_calc.py

#!/usr/bin/env python3
# Worst-Case Latency (WCL) for a TAS-scheduled stream

# Stream parameters
LINK_RATE_MBPS   = 100       # 100 Mbit/s link
CYCLE_TIME_US    = 1000      # 1 ms TAS cycle
GATE_OPEN_US     = 50        # Q7 gate open for 50 µs per cycle
MAX_FRAME_BYTES  = 100       # safety stream max frame size
MAX_INTERF_BYTES = 1500      # largest interfering frame (Q0)

# Transmission times
tx_safety_us  = (MAX_FRAME_BYTES * 8) / LINK_RATE_MBPS       # µs
tx_interf_us  = (MAX_INTERF_BYTES * 8) / LINK_RATE_MBPS      # µs

# Guard band: must be open GUARD_BAND_US before gate to prevent interference
guard_band_us = tx_interf_us     # = 120 µs at 100 Mbit/s for 1500-byte frame

# Worst-case delay for a single hop:
# = guard_band + CYCLE_TIME (missed gate in worst case) + tx_safety
wc_single_hop_us = guard_band_us + CYCLE_TIME_US + tx_safety_us

# Two-hop path (ECU → Zone Switch → Central Switch):
propagation_us = 2.0   # cable propagation, ~2 µs per 400 m (0.7c)
wc_two_hop_us  = 2 * wc_single_hop_us + propagation_us

print(f"Safety frame transmission time: {tx_safety_us:.1f} µs")
print(f"Interfering frame time:         {tx_interf_us:.1f} µs")
print(f"Guard band required:            {guard_band_us:.1f} µs")
print(f"WC single hop:                  {wc_single_hop_us:.1f} µs")
print(f"WC two-hop path:                {wc_two_hop_us:.1f} µs")
# Output: WC two-hop ≈ 2 × (120 + 1000 + 8) + 2 = 2258 µs ≈ 2.3 ms

Summary

TAS provides deterministic worst-case latency by giving safety streams an exclusive transmission gate. The guard band is the non-obvious but critical parameter: if the guard band is too small, a large interfering frame that started just before the gate closes will spill into the safety window, violating the latency guarantee. The guard band must be ≥ maximum frame size on that queue divided by link rate. At 100 Mbit/s with 1500-byte frames, the guard band is 120 µs — which means the Q0 gate must close 120 µs before the Q7 gate opens, consuming 12% of the cycle just for guard time.

🔬 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.