Contents

Partial networking and selective wake-up

Waking only the ECUs a use case needs — for example only telematics and the door module for a remote unlock — to save energy in always-connected vehicles.

Why it exists

Classic NM wakes the entire bus. Remote services, charging and over-the-air updates happen while the vehicle is parked; waking every ECU each time costs energy and wear.

What it is

ECUs are grouped into partial network clusters. NM messages carry bits indicating which clusters are requested. Transceivers with selective wake-up stay asleep unless they see a frame that targets them.

How it works

For a remote unlock, the telematics unit wakes the body and door cluster only. Powertrain and chassis ECUs on the same bus keep sleeping, because their transceivers ignore the wake-up frame.

Best practices

  • Derive clusters from concrete parked use cases, and measure current consumption for each.
  • Test transitions under bus load and with mixed transceiver types.

Common pitfalls

  • A single non-selective transceiver on the bus that wakes its ECU anyway.

What it means for your discipline

  • Networks & communication Core

    Defines partial-network clusters and wake-up frames per use case.

  • Hardware & silicon Core

    Requires transceivers that can recognise specific wake-up frames while the MCU sleeps.

  • Base software Core

    Configures partial network information in NM messages and the behaviour of ComM and Nm.

  • E/E architecture Partial

    Use cases while parked (remote services, charging, OTA) must be mapped to the minimal set of ECUs.

  • Software update & OTA Partial

    Defines which partial network clusters an update needs, including target ECUs and routing gateways. Verifies selective wake-up and keep-awake behavior to complete parked updates within the energy budget.

No direct stake: Cybersecurity · Functional safety · HPC & application software · Diagnostics & lifecycle

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Vehicle services — Maps parked service requests to the minimal set of network clusters needed for each use case.
  • OTA client · UCM — Requests target ECU and gateway clusters during parked updates and releases requests when finished.
MCU-based ECU · AUTOSAR Classic
  • Communication — CanNm and ComM handle partial network cluster requests and the associated NM information.
  • ECU abstraction — Transceiver drivers configure selective wake-up filters and report matching wake-up events.
  • Microcontroller · HSM — Remains in a low-power state while the external transceiver filters frames for selective wake-up.