Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J2366‑2 Link Layer: Token Bus Protocol for the ITS Data Bus
SAE J2366‑2 defines the link layer of the Intelligent Transportation Systems Data Bus (IDB‑C). It specifies the Media Access Control (MAC) and Logical Link Control (LLC) sublayers for a virtual token bus network, providing deterministic access and fault tolerance for automotive and ITS applications. This article covers the key mechanisms that enable reliable communication in vehicular environments.
🛠️ Design Insight: Bounding the token hold time (TTokenHoldMax) ensures predictable latency and fair bus access. This deterministic behavior is critical for real‑time control and sensor data in vehicles.
Overview of the Link Layer and MAC Sublayer
The link layer in IDB‑C is divided into two sublayers: Logical Link Control (LLC) and Media Access Control (MAC). The MAC sublayer implements a virtual token bus protocol that coordinates which node may transmit at any given time. The LLC layer provides framing, error control, and handling of protocol data units (PDUs).
The physical layer relies on dominant/recessive signaling for non‑destructive arbitration during token passing. This signaling scheme allows multiple nodes to contend for the bus without corruption.
Token Bus Arbitration and Collision Handling
Access to the bus is controlled by a token that circulates among active nodes. Only the token holder can initiate transmission. After its transmission, the node passes the token to the next logical neighbor. This eliminates collisions in normal operation and guarantees a maximum latency for every node.
Collisions can still occur during network initialization or when nodes join. The protocol uses a robust collision resolution mechanism based on random backoff and retransmission of token start frames. Dominant/recessive levels ensure that arbitration is non‑destructive — a node sending a dominant bit wins arbitration.
⚠️ Common Mistake: Misconfiguring the token hold timer can lead to unfair bus access or unnecessary timeouts. Ensure TTokenHoldMax and TMaxRot are tuned to the network’s propagation delays and application requirements.
Node States and Network Management Timers
The protocol defines several node states to handle normal operation, failures, and recovery: Active, Not Active, Not Present, Quiescent, Key On/Off. Timers such as TInactive and TNodeRemove allow the network to detect and isolate nodes that have stopped responding, preventing the token from being lost.
The following table summarizes key timing parameters defined in SAE J2366‑2:
| Parameter | Description | Purpose |
|---|---|---|
| TTokenHoldMax | Maximum time a node can hold the token | Ensures fair bus access |
| TMaxRot | Maximum token rotation time | Bounded latency for all nodes |
| TInactive | Node inactivity maximum | Detects node failure |
| TNodeRemove | Node removal timer | Removes non‑responsive nodes |
| TStartActivity | Activity timer | Detects bus idle |
| TLostToken | Lost token recovery time | Reinitializes token bus |
Proper setting of these timers is essential for maintaining network stability. The protocol also specifies an inter‑frame delay (TInterFrame) to allow for synchronization and timing recovery.
Frequently Asked Questions
How does token passing provide deterministic bus access?
Each node knows its successor and predecessor in the logical ring. The token rotates in a predefined order, and only the token holder can send frames. This eliminates collisions and ensures a known worst‑case access time.
What mechanisms detect and resolve collisions?
Collisions are detected during token passing or initialization. The protocol uses a frame‑collision counter and random backoff before retransmitting the token/start frame. Dominant/recessive signaling ensures that arbitration is non‑destructive.
How are node failures and insane nodes handled?
If a node fails to pass the token, the sending node repeats the token; after several failures, it tries to identify the next healthy node. Timers (TInactive, TNodeRemove) detect and isolate insane or unresponsive nodes.
What are the critical timing constraints for token hold and rotation times?
TTokenHoldMax must be bounded to prevent one node from monopolizing the bus. TMaxRot ensures that every node gets a chance to transmit within a predictable interval, even if a node holds the token for the maximum allowed time.
Understanding these mechanisms is key for designing robust IDB‑C networks. SAE J2366‑2 provides the foundation for reliable, low‑latency communication in ITS applications.
