MPLS-based Telecommunication Network Modeling And Data Collecting

MPLS, which stands for Multi-Protocol Label Switch, is the new generation standard for network layer routing on IP-based backbone network. This paper discourses on the software upgrade of a commercial software product to deal with MPLS-based telecommunication network design and planning. The product is named as Network Toolkit, which is on the Service Management Layer of TMN. This paper focuses on two important parts of the project: the network modeling and data collecting.The paper describes the product architecture and functionalities of NT and simply analyses the advantages and disadvantages first, and then points out what goals should be achieved by the design under the original product architecture:1. By means of Hibernate, the open source Object-Relation Mapping tool, to solve the impedence mismatch between the design model and implementation model of data, to boost up the resistance to the dependence on model change, and then improve the extensibility and maintainability of the NT product as a result.2. By means of Spring Framework, the open source light weight Java Bean Container, to introduce the technology of Dependence Injection into NT, to reduce coupling degree among modules, to enhance the configurability of functional units, and fulfill the requirement from NT's commercial strategy as a result.3. To design and implement product-oriented infrastructure and facilities, to reduce the difficulty of features implementation, to enforce consistency of interfaces between functional units, and accomplish the software plug&play as far as possible.About the data modeling, this paper describes the abstract framework of data model in the NT product, and then expands on the system management model, equipment side model and server side model.About the data collecting, this paper describes the design and analysis of architecture and software package of NT server application, and then expands on the design of functional modules in details. The NT server application has four-layer architecture: GUI Layer, Control Layer, Driver Layer and Data Access Layer. GUI Layer adopts MVC design patten to isolate the GUI logic from application logic, Control Layer and Driver Layer are subjected to the popular pipe-filter structure, and with the features of Blackboard Data Exchange, Implicit Invocation and Plug&Play.In the epilogue, the main ingredient of the design is reviewed simply, and is made try to classify from the viewpoint of Model Driven Architecture.