Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC TS 63001 — Guidelines for In-Vehicle Communication Systems
Designing reliable and secure communication networks for road vehicles
1. Introduction to IEC TS 63001
IEC TS 63001 provides comprehensive guidelines for in-vehicle communication systems in road vehicles, covering architecture, protocol selection, electromagnetic compatibility (EMC), network security, and data integrity requirements. As modern vehicles transition from isolated electronic control units (ECUs) to highly interconnected domains — powertrain, chassis, body, infotainment, and advanced driver-assistance systems (ADAS) — the need for standardized communication guidelines has become critical for safety, reliability, and interoperability.
IEC TS 63001 is a Technical Specification, meaning it serves as a pre-standard that provides implementation guidance ahead of a full International Standard. Engineers should treat it as a best-practices reference while monitoring its progression toward full standard status.
The document addresses both traditional in-vehicle networks (CAN, LIN, FlexRay, MOST) and emerging Ethernet-based architectures (100BASE-T1, 1000BASE-T1). It provides specific guidance on network topology design, message scheduling, error detection, fault containment, and timing synchronization across heterogeneous networks. Special attention is given to the gateway design between legacy and modern network segments.
| Protocol | Data Rate | Typical Application | Key Advantage |
|---|---|---|---|
| CAN (Classical) | 500 kbps – 1 Mbps | Powertrain, chassis, diagnostics | Mature ecosystem, deterministic arbitration |
| CAN FD | Up to 8 Mbps | Software update, high-bandwidth sensors | Larger payload, higher throughput |
| LIN | 20 kbps | Door modules, seat controls, lighting | Low cost, single-wire implementation |
| FlexRay | 10 Mbps | X-by-wire, safety-critical systems | Time-triggered deterministic behavior |
| 100BASE-T1 | 100 Mbps | ADAS, infotainment, backbone | Single twisted pair, IP compatibility |
| 1000BASE-T1 | 1 Gbps | Camera video streaming, radar data fusion | High bandwidth, low latency |
2. Architecture Design and Safety Considerations
IEC TS 63001 advocates for a domain-based or zonal architecture approach. In domain architecture, ECUs are grouped by function (e.g., all powertrain-related controllers share a domain controller). In zonal architecture — increasingly favored for software-defined vehicles — ECUs are grouped by physical location within the vehicle, with a zonal gateway handling data routing to centralized compute platforms. The standard provides quantitative guidance on bus loading limits (typically not exceeding 60% under worst-case conditions), message latency budgets (ranging from 1 ms for airbag triggers to 100 ms for infotainment), and redundancy requirements for safety-critical functions.
A critical design consideration is that CAN bus loading above 60% under worst-case conditions can lead to priority inversion and message starvation. Always design with margin — a fully loaded CAN bus is an accident waiting to happen. Use CAN FD or Ethernet for high-bandwidth subsystems rather than overloading classical CAN.
Functional safety per ISO 26262 imposes additional requirements on in-vehicle communication. The standard provides a mapping between ASIL (Automotive Safety Integrity Level) ratings and communication mechanism requirements. For ASIL D functions (highest integrity level), IEC TS 63001 recommends redundant communication paths, end-to-end data integrity protection (CRC + sequence counter + timeout supervision), and fault-tolerant time synchronization with accuracy better than 10 microseconds.
2.1 Engineering Insights for Network Implementation
When implementing an in-vehicle network per IEC TS 63001 guidelines, engineers should pay particular attention to the physical layer design. Termination resistor values, stub length limitations, and grounding schemes directly impact signal integrity. For CAN networks, the standard recommends maximum stub lengths of 0.3 m at 1 Mbps, with proper termination at both ends of the bus. For 100BASE-T1 Ethernet, the standard emphasizes the importance of common-mode choke selection and EMC filter design to meet CISPR 25 radiated emissions limits. The use of unshielded twisted pair (UTP) for automotive Ethernet requires careful PCB layout to minimize mode conversion.
One of the most effective engineering practices recommended by the standard is the use of network simulation tools (e.g., CANoe, PREEvision) for early validation of message timing and bus load. Simulation at the architecture phase can catch 70-80% of communication issues before any hardware is built, dramatically reducing integration effort.
3. Cybersecurity and Secure On-Board Communication
With the advent of connected and autonomous vehicles, cybersecurity has become a paramount concern for in-vehicle communication. IEC TS 63001 incorporates guidance aligned with ISO 21434 (Road vehicles — Cybersecurity engineering). The standard addresses secure boot, authenticated diagnostic messages, intrusion detection systems for in-vehicle networks, and secure over-the-air (OTA) update mechanisms. Specific recommendations include the use of message authentication codes (MACs) for critical CAN messages, hardware security modules (HSMs) within ECUs for key management, and network segmentation to isolate safety-critical domains from infotainment and telematics systems.
4. Frequently Asked Questions
Q: Is IEC TS 63001 mandatory for vehicle type approval?
A: As a Technical Specification (TS), it is not directly mandatory for type approval. However, its recommendations are increasingly referenced by regulatory frameworks (UN ECE R155 for cybersecurity, for example) and are considered industry best practice.
A: As a Technical Specification (TS), it is not directly mandatory for type approval. However, its recommendations are increasingly referenced by regulatory frameworks (UN ECE R155 for cybersecurity, for example) and are considered industry best practice.
Q: How does IEC TS 63001 relate to AUTOSAR?
A: IEC TS 63001 provides protocol-level and system-level communication guidelines, while AUTOSAR provides the software architecture and runtime environment. They are complementary — the standard’s recommendations can be implemented within an AUTOSAR or non-AUTOSAR stack.
A: IEC TS 63001 provides protocol-level and system-level communication guidelines, while AUTOSAR provides the software architecture and runtime environment. They are complementary — the standard’s recommendations can be implemented within an AUTOSAR or non-AUTOSAR stack.
Q: What is the recommended migration path from CAN to Ethernet?
A: The standard recommends a phased approach: introduce Ethernet as a backbone connecting domain controllers first, retain CAN/CAN FD for latency-sensitive and legacy subsystems, and progressively migrate high-bandwidth functions (camera, radar, software updates) to Ethernet as the ecosystem matures.
A: The standard recommends a phased approach: introduce Ethernet as a backbone connecting domain controllers first, retain CAN/CAN FD for latency-sensitive and legacy subsystems, and progressively migrate high-bandwidth functions (camera, radar, software updates) to Ethernet as the ecosystem matures.
Q: Does IEC TS 63001 address V2X communication?
A: The primary focus is in-vehicle communication. V2X (vehicle-to-everything) is covered by separate standards (IEEE 802.11p, 3GPP C-V2X). However, the standard addresses the gateway requirements between in-vehicle networks and external communication modules.
A: The primary focus is in-vehicle communication. V2X (vehicle-to-everything) is covered by separate standards (IEEE 802.11p, 3GPP C-V2X). However, the standard addresses the gateway requirements between in-vehicle networks and external communication modules.
