USB Networking Protocols: CDC-ECM, CDC-NCM, CDC-EEM and RNDIS

A comprehensive engineering guide to USB Ethernet networking protocols for hardware OEMs, embedded firmware engineers, and system architects. Learn how USB CDC-ECM functions, why Windows requires specialized driver support, and how to select the right protocol for your product architecture.

Belcarra USBLAN supports all four major USB networking protocol families and automatically matches the protocol presented by your attached device hardware. For system integration maps, see the Host Driver Architecture and device-side USB Framework Architecture.

USB Networking Protocols Comparison Matrix

Comparing packet encapsulation, frame aggregation, host OS support, and target hardware suitability across the four primary USB networking standards:

Protocol Standard / Spec Multi-Frame Aggregation Windows 11 Native Support Belcarra USBLAN Support Typical Applications
USB CDC-ECM USB-IF Class 0x02, SubClass 0x06 No (1 frame per USB transfer) None (No inbox driver) Full Native (AMD64 and ARM64) Embedded Linux gadgets, smart sensors, cellular modems, test equipment
USB CDC-NCM USB-IF Class 0x02, SubClass 0x0D Yes (Network Transfer Blocks) Partial / basic Optimized Multi-Frame High-bandwidth USB-Ethernet adapters, 5G/LTE routers, camera streaming
USB CDC-EEM USB-IF Class 0x02, SubClass 0x0C Yes (Concatenated EEM packets) None (No inbox driver) Full Native (AMD64 and ARM64) Resource-constrained microcontrollers (Cortex-M, PIC32MZ), ultra-low memory IoT
Microsoft RNDIS Microsoft Proprietary Specification Yes (RNDIS message packing) Legacy (deprecated on Windows 11) Maintained for Compatibility Legacy Windows Mobile, older embedded devices, legacy Linux RNDIS gadgets

In-Depth Guide: USB CDC-ECM (Ethernet Control Model)

What is USB CDC-ECM?

USB CDC-ECM (Ethernet Control Model) is a formal USB class specification defined by the USB Implementers Forum (USB-IF). It defines how to encapsulate IEEE 802.3 Ethernet frames across standard USB bulk data endpoints, effectively transforming any USB device into a virtual Ethernet network interface card (NIC).

In a standard CDC-ECM implementation:

The Windows Challenge: Why CDC-ECM Fails Out of the Box

While operating systems such as Linux (via cdc_ether) and macOS include native, out-of-the-box kernel drivers for USB CDC-ECM, Microsoft Windows (including Windows 10 and modern Windows 11 on both AMD64 and ARM64) does not include a native CDC-ECM class driver.

Historically, Microsoft favored its proprietary Remote NDIS (RNDIS) protocol. Consequently, when an engineer or end-user plugs an industry-standard CDC-ECM device into a clean Windows machine:

The Belcarra USBLAN Solution for CDC-ECM

Belcarra USBLAN completely resolves the Windows CDC-ECM limitation. Belcarra provides a production-proven, turnkey Windows kernel-mode NDIS 6.x network driver that:

USB CDC-NCM (Network Control Model)

CDC-NCM is the direct successor to CDC-ECM, engineered specifically for High-Speed USB (USB 2.0) and SuperSpeed USB (USB 3.x) links. While CDC-ECM transmits only one Ethernet frame per USB transfer, CDC-NCM introduces Network Transfer Blocks (NTBs) that aggregate multiple IP datagrams into single USB transfers.

USB CDC-EEM (Ethernet Emulation Model)

CDC-EEM is a streamlined USB-IF protocol designed specifically for cost-sensitive, resource-constrained embedded microcontrollers (such as ARM Cortex-M, Microchip PIC32MZ, and NXP LPC chips). Rather than requiring separate control and data interfaces like ECM, CDC-EEM simplifies everything onto a single USB interface with two bulk endpoints.

Microsoft RNDIS (Remote Network Driver Interface Specification)

RNDIS was Microsoft's proprietary solution for networking over USB. While millions of legacy devices still utilize RNDIS, Microsoft has deprecated RNDIS across modern Windows editions due to security and architectural concerns. Belcarra USBLAN continues to support RNDIS alongside CDC-ECM, CDC-NCM, and CDC-EEM to guarantee backward compatibility for OEM product fleets transitioning to modern standards.

Protocol Selection and Integration Guidance

When selecting a protocol for a new hardware design or device revision, consider the following engineering trade-offs:

  1. Microcontroller / Low RAM (< 64 KB RAM): Choose CDC-EEM for lowest memory footprint and minimal endpoint count.
  2. General Embedded Linux / Smart Devices: Choose CDC-ECM for universal cross-platform compatibility with Linux and macOS hosts, and pair with Belcarra USBLAN for Windows 11 (AMD64 and ARM64) and Windows 10 (AMD64) hosts.
  3. Higher-Bandwidth / SuperSpeed USB: Choose CDC-NCM for multi-frame transfer aggregation and lower host CPU utilization.