Contents
StandardIEEE

IEEE 802.1Qav / 802.1Qbv

Credit-based shaper and enhancements for scheduled traffic

IEEE 802.1Qav and 802.1Qbv define ways to control Ethernet transmission so time-sensitive vehicle traffic can share links with other data while meeting engineered timing requirements.

What it is

IEEE 802.1Qav and IEEE 802.1Qbv introduced complementary Ethernet traffic-control mechanisms used in Time-Sensitive Networking (TSN). They act at transmission queues in bridges, commonly called switches, and suitably equipped end stations.

Qav introduced the credit-based shaper (CBS), which regulates transmission eligibility using a credit value. Qbv introduced scheduled traffic, commonly called time-aware shaping, which opens and closes queue gates according to a timed schedule. Neither mechanism alone guarantees an application deadline: the complete path and its traffic must be engineered.

Who it applies to

These specifications matter to switch and Ethernet-controller suppliers, ECU platform developers, network designers and vehicle integrators implementing TSN capabilities. They are technical standards rather than vehicle regulations; a project makes particular capabilities mandatory through its network specification, supplier requirements or selected profile.

An ECU that sends ordinary Ethernet traffic may share a network with shaped or scheduled traffic without implementing every TSN mechanism. Nevertheless, its traffic must remain within the assumptions used to design that network. Integrators must identify which ports, queues and end stations need each capability.

What it covers

The mechanisms address how queued Ethernet frames become eligible for transmission on an output port.

Mechanism Basic operation Main engineering task
Credit-based shaping Credit increases or decreases under defined conditions; transmission eligibility depends on credit and queue state. Set bandwidth-related parameters and evaluate interference and delay.
Scheduled traffic A gate control list determines when each queue’s transmission gate is open or closed. Coordinate transmission windows, clocks and traffic arrival times.

CBS smooths traffic and supports bandwidth allocation without requiring globally aligned transmission windows. Its parameters must account for link speed, frame sizes and competing traffic.

Scheduled traffic supports planned transmission opportunities using a shared time reference where schedules require coordination. An open gate permits a queue to compete for transmission; it does not force an application to produce a frame or guarantee immediate transmission.

Closing a gate does not interrupt a frame already being transmitted. Designs therefore account for blocking, often through guard bands or separately supported frame preemption.

How it fits with other documents

The historical amendment names remain common in requirements and product descriptions, but their mechanisms belong to the consolidated IEEE 802.1Q standard. Use that document to understand their interaction with VLAN priorities, queue selection and other bridge functions.

IEEE 802.1AS supplies the time synchronization commonly used for coordinated schedules. IEEE 802.1Qbu and IEEE 802.3br address frame preemption, which can reduce interference from an ongoing lower-priority transmission. IEEE 802.1Qci provides per-stream filtering and policing to help contain traffic that violates its contract. These capabilities complement shaping and scheduling; they require separate implementation and configuration decisions.

The consolidated IEEE 802.1Q-2022 PDF is available without charge through the IEEE GET program. IEEE publication information

In practice

Start with a traffic inventory: source, destination, maximum frame size, transmission pattern, deadline and permitted delay variation. Map streams to paths and queues, then choose shaping or scheduling according to their timing needs and available hardware.

For example, a periodic control stream may use scheduled windows while an audio stream uses CBS on the same link. Validate their interaction alongside diagnostic and background traffic, including bursts and maximum-size frames.

Check the complete sender-to-receiver delay, including application release, software buffering and every network hop. Test schedule activation, clock loss, startup and overload behavior. Record configurations and traffic assumptions with the timing evidence so later software or topology changes can be assessed.

What it means for your discipline

  • Networks & communicationCore

    Own traffic classification, queue configuration, shaping parameters and transmission schedules. Demonstrate timing bounds across the complete network path under the agreed traffic load.

  • Hardware & siliconCore

    Select and validate switches and Ethernet controllers with the required shaping, scheduling and clock capabilities. Check queue resources, scheduling precision and implementation limits.

  • E/E architecturePartial

    Allocate communication deadlines and bandwidth budgets across ECUs and links. Ensure topology and traffic assumptions support the required end-to-end timing.

  • Base softwarePartial

    Configure Ethernet drivers and switch interfaces to realize the network design. Coordinate queue mapping, schedule activation and clock synchronization with platform startup.

  • HPC & application softwarePartial

    Keep application message sizes, rates and release times within their communication contracts. Include software execution and buffering delays when assessing whether a deadline is met.

  • Functional safetyPartial

    Assess whether communication timing evidence supports safety requirements. Define the required response when synchronization, configuration or traffic assumptions fail.

No direct stake: Cybersecurity · Diagnostics & lifecycle · Software update & OTA