The focus of this Thesis has been to evaluate different monitoring systems and processes that are used by the Network Operations Center at TDC Sverige AB. The problem formulation involves (i) how the monitoring systems are used, (ii) how these work together, (iii) what processes are involved and (iv) how the systems and processes can be improved to benefit the Network Operations Center. Processes involved in TDC’s work follows the Information Technology Infrastructure Library. To be able to answer the problem formulation, the current documentation is browsed and together with meetings with key figures within the company; such as managers, project managers, technicians and system administrators; information is gathered to give a comprehensive view of the current state of the monitoring systems, and the whole process leading to handover to the Network Operations Center. TDC Network as a Service is a concept that includes different networking solutions in which LAN and WLAN as a Service offers standardized networking solutions for LAN and WLAN. The Network Management System is described, which includes HP Network Node Manager i, Network Performance Servers and incident ticket systems. The process of how incident tickets can be created, both manually and automatically, is described as well as the whole process of how new customers are added to the monitoring and how customers are registered in the different Service Asset and Configuration Management applications. It is discussed how new nodes are added to the monitoring, and which systems are involved in this process, including Network Node Manager i, VisionApp, NetMRI and incident ticket systems. The regular monitoring process of the Network Operations Center is presented in this Thesis. It is suggested that the improvements include involving the Network Operations Center at an earlier stage during the selling and implementation process, and devised a better transition to the Service Operation phase. TDC would benefit from fewer Service Asset and Configuration Management applications and incident ticket systems and there should be better routines regarding documentation.

After the National Communications Commission lifted the ban on cross-industry, the boundaries of cable television and telecommunication services become increasingly blurred. Thereafter, cable business owners in network operations management area are facing the telecommunication industry with fierce competition. They also need to overcome the high morphological variable services with the impacting of increasingly complex processes. The Information communications in business organizations have generated problems of the information exchanging fault and the recognition process management gap. Therefore, the operational mechanism on cable network management systems becomes very important and meaningful. This study is based on system architecture and logic rule to use the structure-behavior coalescence (SBC) architecture description language (ADL). Through the design-based research (DBR) methodology, it integrates the concepts of information systems and business management, and develops a proprietary architecture tools by innovating cable televisions with architecture-oriented cable network management system model (AOCNMSM). This study also uses logical classification rules to verify the following purposes: (1) Building the network management systems model to meet the business integrated operations. (2) Combining of network management system and organizational information flow to avoid information exchange faults. (3) Excluding the potential barriers on the network management system to avoid the recognition gap of organizational management. By introducing the AOCNMSM, we allow cable business owners to view their online network easier on most environmental management issues. They shall truly achieve the integration of information systems and organizational management and enhance the service quality of cable television to create a more flawless business performance.

Context: Software architecture is an emerging field and progressively more popular in software engineering. Software architecture has become an essential part in development of software systems. Prototyping is possibly one of the most commonly used learning paradigms in software architecture. Hence, it is reasonable to accept some of the requirements that could be expressed as specific quality attributes for developing and comparative analysis of prototype. In this thesis we deal with software architecture based on different prototypes, where the different platforms have been shared canonical within the software architecture. It also has a good potential for performance intensification to analyze the prototype according to the required quality attributes. Objectives: In this study, we investigate the significance of quality attributes such as performance, maintainability and implementation cost of different software platforms. Mainly, it is focused on integration of prototypes in software architecture. We specifically investigate several challenges being faced by the organizations in the maintainability for addressing the challenges in prototype of network management system using software platforms. Methods: In this study, both theoretical and empirical research methods have been applied. In order to accomplish the goal of this thesis, literature review in this research has performed by studying articles from several sources and also performed snowball sampling method to decrease the chance of missing any relevant article. During literature review, we have analyzed learning structure and workflow of prototypes and then incorporated quality attributes by theoretical analysis. In the experiment part, three prototypes were built by deploying different software platforms such as PHP, JSP and Perl. Each of these prototypes was evaluated with respect to maintainability using twenty five surveys from industrial experts, implementation cost in number of hours and performance in terms of response time. Results: As a result of our study, we have identified different challenges in software architecture and practicing in software prototypes by using different software platforms. By this study we analyze the performance, maintainability and implementation cost for different software platforms. Survey has been conducted to recognize challenges and practices in maintainability of prototypes. We have shown the possibility to achieve better quality attributes given to a certain system. Conclusions: There is trade-off, the best implementation alternative depends on how important the different quality attributes are in a certain situation. / +46 455 38 50 00

The diploma thesis deals with the issue of computer network management design with all the necessary steps at the level of a medium-sized engineering company. In addition to the implementation of the monitoring system, the work also focuses on the design of network devices, organizational changes, compilation of a network graph and structural settings with a precise layout for project management.

Software Defined Networking (SDN) has become increasingly popular in combination with Network Function Virtualization (NFV). SDN is a way to make a network more programmable and dynamic. However, in order to create a homogeneous network using this concept, legacy equipment will have to be substituted by SDN equipment, which is costly. To close the gap between the legacy world and SDN, we introduce the concept of a legacy Network Management System (NMS) that is connected to an SDN controller to perform service provisioning. This way, the NMS is capable of configuring both legacy as well as SDN networks to provide customers with the services that they have ordered, while still allowing for new SDN features in the SDN domain of the network. The main service we wish to provide using SDN is Service Function Chaining (SFC). Service provisioning consists of dynamically constructing a path through the ordered network services, in this case Virtual Network Functions (VNFs). This thesis focuses on the SDN controller and its interaction with the NMS. This project aims at configuring OpenFlow rules in the network using an SDN controller to perform SFC. Moreover, the focus will be on how to represent an SDN element and a service function chain in the legacy network NMS. The thesis also contains a discussion on what information should be exchanged between the management software and the controller. The management software used is called BECS, a system developed by Packetfront Software. Integrating SDN in BECS is done by creating a proof of concept, containing a full environment from the low level network elements to the NMS. By using a bottom-up approach for creating this proof of concept, the information that BECS is required to send to the SDN controller can be identified before designing and implementing the connection between these two entities. When sending the information, the NMS should be able to receive acknowledgement of successful information exchange or an error. However, when the proof of concept was created a problem arose on how to test and troubleshoot it. For this reason, a web Graphical User Interface (GUI) was created. This GUI shows the number of packets that have gone through a VNF. Because it is possible to see how many packets go through a VNF, one can see where a network issue occurs. The subsequent analysis investigates the impact of making such a GUI available for a network administrator and finds that the part of the network where the configuration error occurs can be narrowed down significantly. / Software Defined Networking (SDN) har blivit mer och mer populärt i kombination med Network Function Virtualization (NFV). SDN är en sätt för att göra ett nätverk mer programmerbart och dynamiskt. För att skapa ett homogent nätverk med detta koncept, behöver man dock ersätta traditionell utrustning med SDN utrustning som är dyr. För att stänga gapet mellan traditionella nätverk och SDN-världen, introducerar vi ett koncept med ett traditionell Network Management System (NMS) som är anslutet till en SDN-styrenhet för att utföra tjänsteprovisionering. På detta sätt kan NMS:et konfigurera både traditionella och SDN-nätverk, samt provisionera tjänster för kunderna medan nya SDN-funktioner möjliggörs i SDN-delen av nätverket. Den huvudsakliga tjänsten som vi vill lansera genom SDN är Service Function Chaining (SFC). Tjänsteprovisionering består av att konstruera en väg genom beställda tjänster, i detta fall Virtual Network Functions (VNFs). Detta examensarbete fokuserar huvusakligen på SDN-styrenheten och dess interaktion med NMS:et. Projektet syftar till att konfigurera OpenFlow regler i SDN-styrenheten för att utföra SFC. Dessutom fokuserar arbetet på hur man kan representera SDN-element och SFCs i ett traditionellt NMS. Vidare diskuteras vilken information som ska utbytas mellan NMS:et och SDNstyrenheten. NMS:et som ska vara användas är BECS, ett system utvecklat av Packetfront Software. Uppgiften löses genom att skapa ett proof of concept, som innehåller ett komplett system med alla komponenter från nätverkselement till NMS:et. Genom att använda en bottom-up-strategi för detta proof of concept kan informationen som BECS måste skicka till SDN styrenheten indentifieras, innan design och implementation av förbindelsen mellan enheterna kan utföras. När informationen är skickad ska NMS:et kunna hämta information om huruvida styrenheten fick informationen utan fel. Dock uppstår ett problem gällande hur man testar och felsöker detta proof of concept. Av denna anledning skapades ett web Graphical User Interface (GUI). Användargränssnittet visar antalet paket som går genom varje VNF, samt var i nätverket fel uppstår. Analysen undersöker hur stor effekten är för en nätverkadministrator och visar att området där fel kan uppstå begränsas avsevärt.

Network management plays a vital role to keep a network and its application work e ciently. The network management in MANETs is a crucial and the challenging task, as these networks are characterized by dynamic environment and the scarcity of resources. There are various existing approaches for network management in MANETs. The Ad hoc Network Management Protocol (ANMP) has been one of the rst e orts and introduced an SNMP-based solution for MANETs. An alternative SNMP-based solu-tion is proposed by GUERRILLA Management Architecture (GMA). Due to self-organizing characteristic feature of MANETs, the management task has to be distributed. Policy-based network management relatively o ers this feature, by executing and applying policies pre-viously de ned by network manager. Otherwise, the complexity of realization and control becomes di cult Most of the works address the current status of the MANET to take the network man-agement decisions. Currently, MANETs addresses the dynamic and intelligent decisions by considering the present situation and all related history information of nodes into consid-eration. In this connection we have proposed a network management system using agents (NMSA) for MANETs, resolving major issues like, node monitoring, location management, resource management and QoS management. Solutions to these issues are discussed as inde-pendent protocols, and are nally combined into a single network management system, i.e., NMSA. Agents are autonomous, problem-solving computational entities capable of performing e ective operation in dynamic environments. Agents have cooperation, intelligence, and mobility characteristics as advantages. The agent platforms provide the di erent services to agents, like execution, mobility, communication, security, tracking, persistence and directory etc. The platform execution environment allows the agents to run, and mobility service allows them to travel among the di erent execution environments. The entire management task will be delegated to agents, which then executes the management logic in a distributed and autonomous fashion. In our work we used the static and mobile agents to nd some solutions to the management issues in a MANET. We have proposed a node monitoring protocol for MANETs, which uses both static agent (SA) and mobile agents (MA), to monitor the nodes status in the network. It monitors the gradational energy loss, bu er, bandwidth, and the mobility of nodes running with low to high load of mobile applications. Protocol assumes the MANET is divided into zones and sectors. The functioning of the protocol is divided into two segments, The NMP main segment, which runs at the chosen resource rich node (RRN) at the center of a MANET, makes use of SA which resides at same RRN, and the NMP subsegment which runs in the migrated MAs at the other nodes. Initially SA creates MAs and dispatches one MA to each zone, in order to monitor health conditions and mobility of nodes of the network. MAs carrying NMP subsegment migrates into the sector of a respective zone, and monitors the resources such as bandwidth, bu er, energy level and mobility of nodes. After collecting the nodes information and before moving to next sector they transfer collected information to SA respectively. SA in turn coordinates with other modules to analyze the nodes status information. We have validated the protocol by performing the conformance testing of the proposed node monitoring protocol (NMP) for MANETs. We used SDL to obtain MSCs, that repre-sents the scenario descriptions by sequence diagrams, which in turn generate test cases and test sequences. Then TTCN-3 is used to execute the test cases with respect to generated test sequences to know the conformance of protocol against the given speci cation. We have proposed a location management protocol for locating the nodes of a MANET, to maintain uninterrupted high-quality service for distributed applications by intelligently anticipating the change of location of its nodes by chosen neighborhood nodes. The LMP main segment of the protocol, which runs at the chosen RRN located at the center of a MANET, uses SA to coordinate with other modules and MA to predict the nodes with abrupt movement, and does the replacement with the chosen nodes nearby which have less mobility. We have proposed a resource management protocol for MANETs, The protocol makes use of SA and MA for fair allocation of resources among the nodes of a MANET. The RMP main segment of the protocol, which runs at the chosen RRN located at the center of a MANET, uses SA to coordinate with other modules and MA to allocate the resources among the nodes running di erent applications based on priority. The protocol does the distribution and parallelism of message propagation (mobile agent with information) in an e cient way in order to minimize the number of message passing with reduction in usage of network resources and improving the scalability of the network. We have proposed a QoS management protocol for MANETs, The QMP main segment of the protocol, which runs at the chosen RRN located at the center of a MANET, uses SA to coordinate with other modules and MA to allocate the resources among the nodes running di erent applications based on priority over QoS. Later, to reallocate the resources among the priority applications based on negotiation and renegotiation for varying QoS requirements. The performance testing of the protocol is carried out using TTCN-3. The generated test cases for the de ned QoS requirements are executed with TTCN-3, for testing of the associated QoS parameters, which leads to performance testing of proposed QoS management protocol for MANETs. We have combined the developed independent protocols for node monitoring, location management, resource management, and QoS management, into one single network management system called Network Management System using Agents (NMSA) for MANETs and tested in di erent environments. We have implemented NMSA on Java Agent development environment (JADE) Platform. Our developed network management system is a distributed system. It is basically divided into two parts, the Network Management Main Segment and other is Network Management Subsegment. A resource rich node (RRN) which is chosen at the center of a MANET where the Main segment of NMSA is located, and it controls the management activities. The other mobile nodes in the network will run MA which has the subsegments of NMSA. The network management system, i.e., the developed NMSA, has Network manage-ment main (NMSA main), Zones and sector segregation scheme, NMP, LMP, RMP, QMP main segments at the RRN along with SA deployed. The migrated MA at mobile node has subsegments of NMP, LMP, RMP, and QMP respectively. NMSA uses two databases, namely, Zones and sectors database and Node history database. Implementation of the proposed work is carried out in a con ned environment with, JDK and JADE installed on network nodes. The launched platform will have AMS and DF automatically generated along with MTP for exchange of message over the channel. Since only one JVM, which is installed, will executes on many hosts in order to provide the containers for agents on those hosts. It is the environment which o ered, for execution of agents. Many agents can be executed in parallel. The main container, is the one which has AMS and DF, and RMI registry are part of JADE environment which o ers complete run time environment for execution of agents. The distribution of the platform on many containers of nodes is shown in Fig. 1. The NMSA is based on Linux platform which provides distributed environment, and the container of JADE could run on various platforms. JAVA is the language used for code development. A middle layer, i.e., JDBC (java database connection) with SQL provides connectivity to the database and the application. The results of experiments suggest that the proposed protocols are e ective and will bring, dynamism and adaptiveness to the applied system and also reduction in terms network overhead (less bandwidth consumption) and response time.