EMS NMS TUTORIAL PDF

But, these two terminologies do differ in their true meaning and should be used wisely. One or more management interfaces are exposed by NEs that the EMS uses to communicate with and to manage them. The network elements in the network each communicate with their respective EMS. This is depicted in the diagram below:. It is the sole mediator of this information and the control of the NEs to the Network Management Layer.

Author:Goltirr Teshakar
Country:Senegal
Language:English (Spanish)
Genre:Love
Published (Last):19 December 2009
Pages:329
PDF File Size:11.88 Mb
ePub File Size:9.6 Mb
ISBN:941-7-88130-368-1
Downloads:77064
Price:Free* [*Free Regsitration Required]
Uploader:Vur



Element Management System. Useful Resources. Related websites:. Free Downloads on Element Management System:. It is important to understand that EMS's make the link to the NML for tasks such as integrated faultmanagement and flow-through provisioning.

The NML basically has three primary functions:. EMS's with open, standard, northbound interfaces provide the solid foundation required for service providers to deploy the TeleManagement Forum—defined, high-level processes by applications at the TMN framework network, service, and BML's.

EMS's also offer sign ificant value via cost- and time-reducing tasks provided in addition to enabling cost-effective development of the TeleManagement Forum high-level processes. This tutorial supports and represents the value contribution of the EMS with a four-function model. This model incorporates all tasks performed by an EMS and includes the following:.

Topics 5 through 8 describe typical tasks that legitimately belong in the four-function domain of an EMS. These tasks represent significant potential cost savings and revenue generation for service providers. EMS's are now valuable components of the network in their own right and not mere extensions of the NE craft interface as EMS's have often been perceived in the past. Not all EMS's will perform all of these tasks; some will perform these tasks and more; and some will perform unique tasks that target the requirements of a particular NE.

Whether or not a specific function is accomplished via the EMS GUI depends upon whether or not the task is subsumed in an application performed at a higher level. An EMS 's architecture should meet some of the following basic requirements:.

Database technology is a critical part of any credible EMS strategy. Figure 16 shows an example of element management—software architecture that meets the above requirements.

Their work is sponsored by service providers and PTTs from around the world, as well as large equipment vendors and national standards organizations. The seminal reference document for the TMN model is M It had a dual role in providing software for telecommunications management and defining standards for adoption by the RBOCs.

These standards covered all aspects of telecommunications from physical cabling specifications to network management information modeling.

Telcordia is now independently owned by SAIC and is addressing the network management of telecommunications networks using its existing technologies combined with advanced technology programs.

Tele Management Forum, formerly the NMF, is a nonprofit, global organization that provides the telecom industry with leadership on the most effective ways to streamline the management of communications networks and services. Established in , the mission of OMG is to promote the theory and practice of object technology for the implementation of distributed computing systems.

The goal is to provide a common architectural framework for object-oriented applications based on widely available interface specifications. In addition to its initial use for diverse information systems IS applications, CORBA has gained widespread acceptance as the object-oriented distributed computing protocol for network management applications.

For this reason, the OMG has a separate telecommunication subgroup to ensure that the tools and methodologies evolve to meet the unique needs of the telecommunications application environment. These are industry bodies that, in general, promote standardization within their technology domains. In most cases, such standardization also covers management activities. The organizations typically define information models for managing the equipment and specify which management protocols are to be used.

Make a free website with Yola. Typically, the EMS manages the functions and capabilities within each NE but does not manage the traffic between different NEs in the network. To support management of the traffic between itself and other NEs, the EMS communicates upward to higher-level network management systems NMS as described in the telecommunications management network TMN layered model.

The EMS provides the foundation to implement TMN—layered operations support system OSS architectures that enable service providers to meet customer needs for rapid deployment of new services, as well as meeting stringent quality of service QoS requirements. Its purpose is to partition the functional areas of management into layers. The key benefit of this architecture is to identify five functional levels of telecommunications management: business management layer BML , service management layer SML , network management layer NML , element management layer EML , and the increasingly intelligent NEs in the network element layer NEL.

TMN segregates the management responsibilities based on these layers. This makes it possible to distribute these functions or applications over the multiple disciplines of a service provider and use different operating systems, different databases, and different programming languages. TMN calls for each layer to interface with adjacent layers through an appropriate interface to provide communications between applications, and as such more standard computing technologies can be used.

The TMN M. TMN model is simple but elegant and has been effectively used to represent the complex relationships within network-management architectures graphically. Originally based on common management information service element CMISE , the object-oriented technology available at the time of inception in , the model now demonstrates its flexibility with the recent adoption of technologies such as common object request broker architecture CORBA , as we drive toward a more generic data-processing type of computing.

This, however, takes no recognition of the fact that most devices deployed in the marketplace use other protocols such as TL1, SNMP, and a variety of proprietary mechanisms. The effective EMS will also communicate with other higher-level management systems using protocols that are the most cost-effective to implement. Therefore, the TMN layering is achieved by using whatever protocols are appropriate. It is, however, too abstract to use to understand the operational contribution and economic value of EMS's.

Service providers SPs think in terms of work and the related cost and time that must be invested to provide service to customers. This study, based on interviews with service providers, identified a number of high-level processes and supporting subprocesses that should be accomplished by each layer of the TMN architecture.

The TeleManagement Forum—defined, high-level processes for which the EML must provide the base data and operations are the following: Service provisioning Network development and planning Network inventory management Network provisioning Service assurance Network maintenance and restoration Network monitoring and control It is important to understand that EMS's make the link to the NML for tasks such as integrated faultmanagement and flow-through provisioning.

This model incorporates all tasks performed by an EMS and includes the following: Function 1: service provisioning Function 2: service assurance Function 3: EMS and NE operations support Function 4: automation enabler Topics 5 through 8 describe typical tasks that legitimately belong in the four-function domain of an EMS.

An EMS 's architecture should meet some of the following basic requirements: It should provide the correct level of management functionality appropriate to the device and to the management environment. It should be scalable to grow with the requirements and complexity of the network.

It should be distributable in order to support such scalability and to provide a level of high availability.

ALTERNITY RULES PDF

Difference between EMS and NMS

.

AICONTACTSAFE TUTORIAL PDF

Fundamentals of EMS, NMS and OSS/BSS

.

GREGORY BATESON PASOS HACIA UNA ECOLOGIA DE LA MENTE PDF

EMS-NMS Frequently Asked Questions

.

DELEM DM02 PDF

.

Related Articles