What it is
AUTOSAR Classic Platform standardizes how an ECU starts, keeps its networks awake, and returns to sleep. The work is split across basic software modules. The ECU State Manager (EcuM) runs startup, checks wakeup sources, and enters the chosen shutdown or sleep target. The BSW Mode Manager (BswM) holds the rules and action lists that carry out a mode change. The Communication Manager (ComM) tracks whether each user and each channel wants full communication, silent communication, or no communication. The generic Network Management interface (Nm), with bus modules such as CanNm, FrNm, and UdpNm, decides whether the bus itself may sleep.
Who it applies to
These specifications apply to ECUs developed with AUTOSAR Classic. The OEM sets one sleep and wake policy. Each supplier implements it with the same state machines, so nodes on a channel agree when the bus is requested, ready to sleep, or asleep.
AUTOSAR Adaptive uses a separate execution and machine state model. An Adaptive controller that shares that Ethernet network still has to speak the same UDP network management, or the link stays awake.
What it covers
Network behavior is a short state machine. After a wake, nodes enter Repeat Message and announce themselves. A node that still needs the bus stays in Normal Operation and sends network management PDUs on a cycle. A node that is finished, while others are not, enters Ready Sleep: it stays awake, stops sending, and watches the bus. When those PDUs stop, the channel moves through Prepare Bus-Sleep into Bus-Sleep. A local wake or a received network management PDU starts the cycle again.
ECU state follows the same idea one level up: startup, run, then a shutdown path into sleep or off. With flexible EcuM, software requests RUN while it has work and releases RUN when the work is done.
Partial networking narrows who must wake. Related functions form a partial network cluster, and network management user data carries a bit vector of active clusters. An ECU may sleep when every cluster it belongs to is idle, even if other clusters on the same bus stay awake. The transceiver must support selective wake-up and inspect those bits before it disturbs the microcontroller.
| Module | What you configure it for |
|---|---|
| EcuM | Wakeup sources, startup, sleep and shutdown targets |
| BswM | Rules that turn mode requests into actions |
| ComM | Users, channels, and partial network clusters |
| CanNm, FrNm, UdpNm | PDU layout, cycle timing, and cluster filters |
How it fits with other documents
Bus State Managers (CanSM, LinSM, FrSM, EthSM) sit under ComM and drive the controller and the transceiver. ComM asks for full or silent communication; the bus state manager applies that to the driver. LIN is the outlier: LinSM and the schedule handle sleep, with no CanNm-style network management PDU.
Application software stays above this stack. A component requests a ComM user, or requests RUN from EcuM, and releases that request when the feature is idle. An open diagnostic session is a normal reason for ComM to keep a channel in full communication. Where the project requires it, secure onboard communication authenticates network management PDUs so a spoofed keep-awake is dropped. The OEM power-mode specification remains the source for wakeup lines, cluster membership, and timer values. AUTOSAR specifies the modules that carry those decisions out.
In practice
Give each feature that can prevent sleep its own ComM user, mapped only to the channels and clusters that feature needs. Name an owner for releasing that user and any EcuM RUN request. One request left open is enough to hold the network and drain the battery.
Take the network management cycle, timeout, and repeat message time from the OEM network specification and use them on every node of the channel. Keep shutdown sequencing in BswM: when every channel is silent and every RUN request is released, select the shutdown target, store non-volatile data, and hand the ECU to EcuM for sleep.
On the bench, trace one wake and one sleep beside the bus log, EcuM, and ComM. Cover a local wake, a remote wake, and a single cluster wake, including after an aborted diagnostic session.