1.1 Embedding of the Network Management (NM) NM defines a set of services for node monitoring. Figure 1 shows how the NM is embedded into a system and that the NM shall be adapted to specific requirements of the bus system used or to the resources of the nodes. NM consists of the following: -- interface to interact with the Application Programming Interface(API); -- algorithm for node monitoring; -- internal interfaces (NM <-> COM, etc.); -- algorithm for transition into sleep mode; and -- NM protocol data unit (NMPDU). 1.2 Adaptation to bus protocol specific requirements Adaptation to bus protocol specific requirements consists of the following: -- CAN, VAN, J1850, K-BUS, D2B, etc.; -- error handling, e.g. bus-off handling in a CAN, transmission line error handling; and -- interpretation of the status information, e.g. overrun or error active/passive in a CAN. 1.3 Adaptation to node resources Adaptation to node resources consists of the following: -- scaling of the NM as a requirement of the node; and -- application-specific usage of the NM services. 1.4 Adaptation to hardware-specific requirements This consists of adaptation to a protocol circuit and a physical layer circuit, e.g. switching the bus hardware to one of the possible physically power save modes. 1.5 Station management (system-specific algorithms) There are a variety of additional tasks involved in coordinating a network. These are not described in ISO 17356, since they are system-dependent. Hence, these tasks are done by the application, e.g. by a module called station management.