15.12.2012 Views

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

130 Deploying <strong>and</strong> Managing IP <strong>over</strong> WDM Networks<br />

7.4 Generic Management System Architecture<br />

This WINMAN architecture looks at the NMSs as derived from a generic solution<br />

h<strong>and</strong>ling the functional management areas: fault, configuration, <strong>and</strong> performance<br />

management. This generic NMS h<strong>and</strong>les in a very similar way any<br />

type <strong>of</strong> domain whether it is WDM, IP, or INMS. Therefore, this architecture is<br />

also extensible to manage any other type <strong>of</strong> technology domain (e.g., ATM or<br />

SDH).<br />

Figure 7.4 shows the system class diagram for the three types <strong>of</strong> NMSs,<br />

which are inherited, from the abstract or generic NMS. All <strong>of</strong> the NMS functionality<br />

is contained in the abstract NMS. This functionality is described by the<br />

following subclasses:<br />

• GUI;<br />

• Fault management, depicted as FM in Figure 7.4;<br />

• Configuration management, depicted as CM in Figure 7.4;<br />

• Performance management, depicted as PM in Figure 7.4;<br />

• Database, depicted as DB in Figure 7.4;<br />

• Northbound, depicted as NB Figure 7.4;<br />

• Southbound, depicted as SB Figure 7.4.<br />

Each <strong>of</strong> the specific NMSs contains all <strong>of</strong> the functionality <strong>of</strong> the components<br />

<strong>and</strong> therefore provides a full <strong>and</strong> independent management system. Under<br />

this point <strong>of</strong> view, WINMAN adopts the polymorphism princ<strong>ip</strong>le so that each<br />

time a new type <strong>of</strong> NMS is inherited for a new type <strong>of</strong> network, the same models<br />

could be used without changing the architecture itself.<br />

This view also shows the difference between the <strong>networks</strong> <strong>and</strong> the s<strong>of</strong>tware<br />

management components. The different types <strong>of</strong> NMSs are related by inheritance<br />

to the abstract NMS object. The different components <strong>of</strong> the network<br />

management functionality are associated to the abstract NMS by means <strong>of</strong> containment<br />

relationsh<strong>ip</strong>s.<br />

7.4.1 The Three-Tiers Concept<br />

The three-tiers concept [4] has been developed in the world <strong>of</strong> browser applications<br />

when the need for independence between the persistence layer <strong>and</strong> server<br />

process to the business logic <strong>and</strong> the presentation is a must. The same need for<br />

independence between layers was identified for the WINMAN generic<br />

architecture.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!