reshold detection and alarm generation versus net- work managers. This implies that an element manager is intended to deal with many types of alarms from AFs itself, without bothering its network manager. It also implies that there can exist network-MOs (NW-MO) in an element man- ager that rely on network element MOs (NE-MOs) in AFs, where the NW-MOs are used by network managers. Thus, an element manager will behave as an OSF versus AFs, but as an AF versus network managers. 2. Network manager (NM): A network manager that connects element managers will deal primarily with network configuration (setting data in routing tables, etc.). This is the management area in which AMLn logical-network models and configuration tables would be specially helpful. The manager may also deal with testing and traffic analysis. 3. Service manager (SM): Deals with definition, administration, and charging of services. 4. Business manager (BM): This manager deals with business oriented aspects, such as analysing usage trends, service quality and producing accounting reports. The functional area classification assumes that, for each manager type, several or all of five types of problems may have to be handled (although, for each man- ager, constrained to resources that are characteristic for the type of manager): 1. Fault handling: These are functions that deal with fault detection, fault isolation, and fault reporting and logging. 5 Management and Traffic Systems 2. Accounting: These are functions that deal with collecting, storing, and delivery of charging information. 3. Performance handling: These are functions that deal with collecting, storing, and delivery of operations statistics, and with optimization of the traffic system within the limits of existing resources. 4. Configuration: These are functions that deal with installation and initiation of resources and with network configuration, for example. 5. Security handling: These are functions that deal with authentication, with multi- ple access of management functions and with p