Contents

Platform services on the zone controller (MCU)

These services coordinate a zone’s network availability, diagnostic records, security events and electrical power outputs.

What runs here

A zone controller connects nearby sensors, actuators and networks, and may distribute their electrical power. Its platform services provide shared mechanisms for these responsibilities, typically within AUTOSAR Classic Platform.

Component Role
Network Management Interface (Nm) and bus-specific NM modules Coordinate network participation and readiness for sleep.
Communication Manager (ComM), ECU State Manager (EcuM), Basic Software Mode Manager (BswM) Coordinate communication requests, ECU lifecycle and configured mode actions.
Diagnostic Communication Manager (Dcm) Handles diagnostic requests, sessions, service timing and access conditions.
Diagnostic Event Manager (Dem) Manages reported diagnostic events, DTC status and associated fault records.
Intrusion Detection System Manager (IdsM) Collects security events from sensors, applies configured qualification rules and prepares events for storage or forwarding.
eFuse management Supervises power channels, interprets switch feedback and applies enable, shutdown and recovery policies.

These modules have distinct responsibilities: network sleep coordination is broader than Nm alone. Dcm delegates application-specific diagnostic work to other software. IdsM processes events reported by security sensors; detection logic must exist elsewhere. AUTOSAR Dcm specification, AUTOSAR IdsM specification.

“eFuse management” describes a project-specific service, not a universal AUTOSAR module. Its implementation depends on the selected power devices and electrical architecture.

Why it looks like this

Local ownership keeps power supervision and network availability close to the hardware they control. A central computer can request a power mode, but local protection and recovery must remain defined when backbone communication disappears.

MCUs suit predictable execution and direct peripheral access. Nevertheless, multiple cores do not eliminate contention: diagnostics, security reporting and power supervision compete for CPU time, memory, communication buffers and nonvolatile storage. Statically configured services help bound these demands within the controller’s cost and memory budget.

Safety integrity follows allocated safety requirements. An MCU supporting ASIL B–D development does not make every hosted service equally safety-critical. Power switching may require safety mechanisms and interference protection, while diagnostic uploads can tolerate delay. Fast electrical protection must follow the device’s capabilities and safety concept; smart switches can provide hardware current limiting and thermal shutdown beneath software supervision. Example smart-switch capabilities.

Protection calibration and mode sequencing should change through controlled configuration and validation. Their update cadence can differ from frequently changing central applications.

How it connects

Above, gateway and I/O applications request communication availability, report faults and consume power-channel status. AUTOSAR software components access services through configured RTE interfaces where applicable; BSW modules also use direct module APIs.

Below, Dcm exchanges diagnostic PDUs through PduR and the configured transport stack. Dem works with nonvolatile storage services to retain selected records. Power supervision reaches smart switches through device drivers, potentially using SPI, digital pins and analog feedback.

ComM coordinates communication demand with Nm and bus state managers; EcuM and BswM participate in wake-up and mode sequencing. Their configurations must agree before a network or supplied node can shut down. AUTOSAR ComM specification.

Across nodes, the zone may route diagnostic traffic while answering its own requests separately. Qualified security events can travel to a central collector. Power commands require authorization, freshness checks and local acceptance rules appropriate to their consequences.

Compared with other node classes

  • HPC application processor: Platform services emphasize richer diagnostic APIs, OTA coordination, host intrusion detection and extensive logging; the zone retains local hardware supervision.
  • HPC safety island: Services concentrate on watchdog supervision, communication protection and safety fault handling, usually with a narrower hardware scope.
  • MCU-based ECU: Similar Dcm/Dem services support a specific function; a zone additionally coordinates several local networks and power branches.
  • Smart node / LIN slave: Configuration and basic diagnostics are smaller in scope, with much of the coordination handled by an upstream controller.

Best practices

  • Define one coordinated state model for communication availability, supplied loads, diagnostics and shutdown.
  • Specify each power channel’s startup, fault, retry and reset behavior against the actual load and wiring.
  • Bound diagnostic and security-event processing, including queues, storage writes and overload behavior.
  • Preserve useful fault context across brownouts, while accounting for storage endurance and incomplete writes.
  • Validate mixed-criticality scheduling and shared-resource access against the allocated safety requirements.
  • Test lost backbone communication, stuck wake requests, diagnostic activity during shutdown and repeated load faults on hardware.

Common pitfalls

  • Treating network sleep permission as permission to remove power from every connected load.
  • Assuming a generic smart switch provides all required wire protection without checking its characteristics.
  • Allowing diagnostic output control or remote power requests to bypass local interlocks.
  • Recording every repeated security event until buffers or persistent storage become exhausted.

What it means for your discipline

  • Base software Core

    Own the integration and configuration of mode management, diagnostics, event handling and power-service interfaces. Daily work includes initialization sequencing, scheduling and shutdown dependencies.

  • Networks & communication Core

    Define how communication requests, network management and wake sources interact across the zone’s channels. Verify that sleep and wake behavior matches vehicle use cases.

  • Diagnostics & lifecycle Partial

    Define diagnostic services, event-to-DTC mappings and fault records for the controller and its power channels. Distinguish locally answered requests from routed requests.

  • Cybersecurity Partial

    Specify security-event sources, qualification rules and forwarding policy. Review diagnostic and power-control authorization paths.

  • Functional safety Partial

    Allocate safety requirements to power supervision and supporting services. Check fault reactions and interference from diagnostic or security processing.

  • Software update & OTA Partial

    Coordinate diagnostic sessions, network availability and power-channel states so the zone and downstream targets remain reachable and powered during flashing. Define shutdown inhibition and recovery behavior for interrupted updates.

No direct stake: E/E architecture · HPC & application software · Hardware & silicon

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)

Not directly involved on this node type.

MCU-based ECU · AUTOSAR Classic
  • Communication — Coordinates network participation and sleep readiness through network management integrated with communication and ECU mode control.
  • Diagnostics — Dcm handles local diagnostic requests while Dem maintains event status, DTCs and selected fault records.
  • Memory · crypto · WdgM — Retains selected diagnostic and security-event records through configured nonvolatile storage services.
  • ECU abstraction — Provides board-specific interfaces to smart switches for power-channel commands, current feedback and fault reporting.