Credit-Based Shaper - AVB Streams - Automotive Ethernet

Credit-Based Shaper: How Credit Accumulates

CBS Credit Accumulation Model

  Credit (bytes):
  Max credit ──────────────────────────────
               ↗           ↗
              /           /
  0 ─────────/───────────/──────────────── time
            ╲ (sending) ╲ (sending)
  Min credit ──────────────────────────────

  Credit accumulates at idleSlope (bytes/µs) when NOT transmitting
  Credit decreases at sendSlope = idleSlope - linkRate when transmitting

  Frame transmission allowed when: credit ≥ 0
  Must wait if: credit < 0 (replenish to 0 before sending)

  Result: traffic is shaped to exactly idleSlope average bandwidth
  Bursts are allowed temporarily (up to maxCredit bytes)
  → Bounded burst: predictable bandwidth without wasting link capacity

Stream Reservation Classes A and B

Class	Max Latency (2 hops)	Observation Interval	Use Case
Class A	2 ms	125 µs	Time-sensitive audio, sensor data, control signals
Class B	50 ms	250 µs	Video streams, lower-priority A/V
Class C (non-standard)	varies	500 µs	OEM-defined; e.g., periodic CAN-over-IP
Best Effort	unlimited	—	Diagnostics, OTA, bulk data

CBS Bandwidth and Credit Parameter Calculation

Pythoncbs_calc.py

#!/usr/bin/env python3
# CBS parameter calculation for a camera video stream

# Stream parameters
LINK_RATE_MBPS    = 100       # 100 Mbit/s port
RESERVED_BW_MBPS  = 40        # camera stream: 40 Mbit/s reserved (Class A)
MAX_FRAME_BYTES   = 1400      # camera frame (Ethernet jumbo payload)
MAX_INTERF_BYTES  = 1500      # largest non-AVB frame on same port

# Derived parameters
idle_slope_mbps   = RESERVED_BW_MBPS
send_slope_mbps   = RESERVED_BW_MBPS - LINK_RATE_MBPS   # = -60 Mbit/s

# Max credit: credit accumulated during one max-interference-frame transmission
max_credit_bytes  = (idle_slope_mbps / LINK_RATE_MBPS) * MAX_INTERF_BYTES

# Min credit: max debt accumulated during one max-AVB-frame transmission
min_credit_bytes  = send_slope_mbps / LINK_RATE_MBPS * MAX_FRAME_BYTES

# Class A max latency at one hop
# Worst case: max_credit / idle_slope = time to drain max credit
burst_max_us      = max_credit_bytes * 8 / RESERVED_BW_MBPS

print(f"idleSlope:     {idle_slope_mbps} Mbit/s")
print(f"sendSlope:     {send_slope_mbps} Mbit/s")
print(f"maxCredit:     {max_credit_bytes:.1f} bytes")
print(f"minCredit:     {min_credit_bytes:.1f} bytes")
print(f"Max burst time:{burst_max_us:.1f} µs")
print(f"Bandwidth util:{RESERVED_BW_MBPS}/{LINK_RATE_MBPS} = {RESERVED_BW_MBPS/LINK_RATE_MBPS*100}%")

Summary

CBS provides soft real-time guarantees: a stream cannot exceed its reserved bandwidth on average, but can burst up to maxCredit temporarily. The CBS parameters (idleSlope, sendSlope, maxCredit, minCredit) are calculated from the stream specification and must be consistent across all switches on the path. AUTOSAR AVTP and SOME/IP streaming use CBS Class A for camera/sensor data. CBS alone is not sufficient for hard real-time safety streams — those require TAS. CBS is typically deployed alongside TAS: safety streams use TAS gates; camera streams use CBS bandwidth reservation; OTA traffic uses best-effort queues.

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