or connecting to the element from the management system. Commands to be triggered on the element can be sent using these basic application layer protocols, which are simpler rather than using the pure management protocols like SNMP, CMIP, and SO on. Fundamentals of EMS, NMS and OSS/BSS Protocols SNMP, CMIP, SOAP, and NETCONF will be handled in detail later in this book. Different networks have different requirements and it can be seen that this resulted in the introduction of various protocols. While internet-based man- agement like a web-based enterprise management would require a management protocol that works with HTTP, a telecom network would rather use SNMP with a well-defined MIB for its management. Evolution: The initial management requirements were limited to man- aging individual elements based on proprietary protocols. With stan- dard protocols it was later possible to manage networks. Then a single management solution was expected to manage a set of networks in a domain. Now management solutions are expected to manage networks across multiple domains. An organization in the communication indus- try wants its management solution to handle enterprise management, telecom network management, service management, and management of its storage devices. Most management solutions (Adventnet, IBM Netcool, etc.) support a variety of management protocols and can handle networks associated with different domains. Having support for multiple management solutions is just a stepping stone in devel- oping a converged management solution. Having a common information model and set of standard interface definitions for interaction between management com- ponents are some of the other factors that affect the development of a converged management solution. Additional Reading 1. William Stallings. The Practical Guide to Network Management Standards. Reading, MA: Addison-Wesley, 1993. Natalia Olifer and Victor Olifer. Computer Networks: Principles, Technologies and Protocols for Network Design. New York: John Wiley & Sons, 20