MIS primitives. TMN also uses MIB (management information base) that stems from the OSI/ISO Network management model and is a type of database used for managing the devices in a communications network. The processes that manage the information are called management entities. A management entity can take on one of two possible roles: manager or agent. Manager and agent processes 'send and receive requests' and 'notifications' using the CMIP. TMN is defined in the ITU-T M.3000 recommendation series. The principles of TMN were first specified in an ITU-T M.3010 [25] document in 1996. The M.3200 [26] is intended to provide an overview of TMN Management Services (fixed and mobile services, etc.) and Telecommunications Managed Areas (traffic management, security management, etc.). The M.3400 [27] describes the TMN management functions and management function sets. 8.3.3.1 TMN Architecture The key M.3010 standard describes the architecture of TMN, identifies different types of nodes and the interfaces between them. The TMN architecture has three key aspects namely: TMN functional architecture, TMN information architecture and TMN physical architecture as shown in Figure 8.17. 8.3.3.1.1 TMN Functional Architecture The TMN functional architecture consists of functional blocks which enable it to perform management functions. A Data Communication Function (DCF) is used for this transfer of information between the Next Generation Mobile Communications Ecosystem TM Architecture Functional Information Physical Architecture Architecture Architecture Figure 8.17 TMN architecture TMN function blocks. The pairs of TMN functional blocks which exchange management information are separated by reference points. The reference points define service boundaries between two management function blocks. Table 8.1 shows the relationships between the logical function blocks in terms of the reference points between them. Each functional block consists of functional components and details on these components can be found in M3010 [25]. At the sa