his view is to capture the management functions to be implemented in NGNM. The management functions are categorized under a set of blocks like the operations systems function block (OSF) and network element function block (NEF). Management information view (architecture): In order for entities to perform functions that are defined in a functional view, these entities need to com- municate management information. The characteristics of this management information are defined in this view. Next Generation Network Management (NGNM) Management functional architecture Management information architecture Management physical architecture Figure 17.2 NGNM management architecture. (Based on ITU-T documentation.) Management physical view (architecture): The deployment and physical con- figuration for mapping the functions is a critical part of network manage- ment and is handled in this view. Security considerations are also shown as spanning across the physical, informa- tion, and functional view. Security in the next generation network and the NGN management infrastructure is part of NGNM and is given under a separate set of definitions from ITU-T. Another important aspect in the M.3060 document is the logical layered archi- tecture (see Figure 17.3) that brings back the conventional concept of dividing the management pane into a business management layer (BML), service manage- ment layer (SML), network management layer (NML), element management layer (NML), and network element layer (NEL). A set of functional blocks are defined across each of these layers to list the entities and management functions that span across the different layers in NGNM as defined in M.3060. The M3060 identifies NGNM functionality to support NGN by: End-to-end management of physical and logical resources. The networks to be managed would include core network, access network, and customer net- works. The interconnect components and the supporting terminals also need to be managed. Management platform that ensures secure access to customer and ma