Area overview
Start here
Network Management (NM) decides when ECUs may sleep. Every node periodically signals whether it still needs the network. When no node requests it any more, all nodes move to bus-sleep together; any node can wake the network again.
In AUTOSAR the responsibilities are split:
- NM modules (CanNm, UdpNm, FrNm) run the distributed sleep/wake protocol on each bus,
- ComM (Communication Manager) collects who needs which channel from applications,
- EcuM / BswM handle ECU-level power and mode transitions,
- Nm interface coordinates several buses so a gateway sleeps only when all its networks can.
Partial networking
Partial networking lets a subset of ECUs wake for a use case — for example only the body controller and telematics for a remote door unlock — while the rest stay asleep. On CAN, transceivers with selective wake-up listen for specific wake frames while the MCU sleeps. On Ethernet, wake-up over data lines and switch power states add new questions.
Why it matters more in an SDV
- Always-on connectivity — telematics, remote functions and OTA keep parts of the vehicle awake.
- Central compute draws far more power than a classic ECU, so its sleep strategy becomes decisive.
- Zonal architectures move NM coordination into zone controllers, which must manage CAN, LIN, 10BASE-T1S and Ethernet segments together.
Commercial-vehicle angle
Long parking periods, auxiliary loads (sleeper cabs, refrigeration, tail lifts) and fleet telematics make the quiescent-current budget a design-driving requirement — a truck that will not start after a weekend is an expensive failure.
Key sources & further reading
- AUTOSAR R25-11, Requirements on Network Management (Foundation) and the CanNm, UdpNm, ComM, EcuM and BswM specifications — free at autosar.org.
- ISO 11898-2:2024 — CAN physical layer incl. selective wake-up (partial networking) transceivers.
- CAN in Automation — application notes on partial networking.