Telecommunication Management Network Organization: Protocols, Fault Management, And Configuration State

Identification of various protocols in the TMN architectures model

Discuss about the Telecommunication Management Network Organization.

The report focuses on the organization “Telecom Australia” which has network management environment across Victoria.  The organization faces challenges in providing services to the customers due to expensive as well legacy tool sets. The organization also wants to expand their customer base and therefore they want to provide better customer experience to the customers in the marketplace. For this, the organization wants to research telecommunication network software, which can be helpful in providing service assurance platform considering TMN and FCAPS.

 The report illustrates various protocols in the TMN architecture model, fault management process, fault identification, configuration state and software network of the level resources. The report also discusses disaster recovery plan, quality of service management and identification of various monitoring parameters in the fault management model.

The TMN architecture is defined as an approach of hierarchical telecommunication management. The main aim of the architecture model is to divide the various functional areas or regions of management into various protocols (Kim and Feamster 2013). The TMN architecture model helps in identifying different protocols in the functional level of telecommunication management. The protocols of TMN architecture model includes Business Management Layer, Service Management layer, Network Management Layer, Element Management Layer and the Network Element Layer (Ghezzi, Cortimiglia and Frank 2015). The protocols are described below:

Network Element Layer: The network management layer helps in defining various interfaces of the network elements that helps in instantiating different functions, which are associated with device instrumentation (Mijumbi et al. 2016). They also assist in covering all the areas related with FCAPS.

Element Management Layer: It helps in providing various management functions for connecting different network elements on an individual or in the group. It also assists in supporting an abstraction of different functions, which are provided by different network element layer (Han et al. 2015). The examples include determination of various equipment error, measuring temperatures of device, collection of various statistical data for accounting purpose and notification of various logging event as well as performance statistics.

Network Management Layer: It helps in offering a holistic view of the network between the various pieces of equipment as well as independent types. It helps in managing a network, which is generally supported by the element management layer (Bolla et al. 2013). The examples of network management layer include end-to-end report of network utilization, root cause analysis as well as traffic engineering.

Analyzing the fault management process and fault identification

Service Management Layer: It generally deals with various contractual aspects of services, which are provided to the customers. The main functions of this layer include service creation, handling of orders, implementation of service, monitoring of service, handling of complaint as well as invoices (Dotcenko, Vladyko and Letenko 2014). Examples of service management layer include QoS management, VPN and monitoring as well as verification of SLA.

Business Management Layer: The layer is responsible for total enterprise. The protocol is considered as a goal setting approach. The information as well as data is related with the level of abstraction addresses of the objectives (Cohn et al. 2013). TMN implementation and standards provide proper specification, which are related with all the protocols except BML.

Fault management in telecommunication management network includes all the procedures as well as processes that are required for handling various systems for responding properly to the complaints of the customers. The fault management process includes the following:

Alarm: TMN must have the capability of monitoring the failures of NE in real time. Indication is generally created by NE when a failure occurs. TMN helps in determining both the severity as well as nature of the fault basing (Wood et al. 2015). It also helps in determining the effect of various fault on the services which are supported by the fault equipment by using two methodologies.

Correction: The procedure of automatic restoration from NE to TMN helps in indicating a specific line, equipment, service as well as system that helps in switching the protection procedures of NE’s. Telecommunication management network requests NE so that they start hot-standby procedures for the system for letting a redundant unit that is further helpful in minimizing disruption (Monza et al. 2016). Reloading process includes a request to NE from telecommunication management network for reconstructing a system or a service from a specific dumb record. Reload report is the procedure of reporting a service or a system from NE to TMN.

Testing: The procedure of testing can be completed using two ways. In the first way, a TMN orders a NE for carrying out analysis about the circuit as well as characteristics of the equipment. The procedure is entirely done with the NE. The results of testing are provided to the TMN automatically as well as immediately on a delayed basis. Another procedure’s analysis is completed within the TMN (Forbes Causam Energy 2016). It assists NE for providing proper as well as effective access to the different circuit  and it is analyzed that there are no more messages which are exchanged with the NE.

Description of the configuration state and software level of the network resources

The main purpose of fault identification within a specific system is to identify various replaceable units. The level of granularity is fully dependent on the system under some specific consideration (John et al. 2013). The fault identification technique includes experienced based technique and model based technique that involves models of some expected system as well as behavior.

Configuration state helps in providing proper as well as effective functions for exercising control, proper identification, collection of data and providing effective data to NEs. It includes the following:

NE installation: Telecommunication management network helps in supporting the installation of equipment that assists in generating telecommunication networks. It helps in covering the extension as well as reduction of a system. Some of the NEs call in order to exchange data between themselves and TMN (Lara, Kolasani and Ramamurthy 2014). Another example, is the installation of various programs into NE

Provisioning: It consists of different procedures, which are needed for bringing equipment inside the device including the process of installation. The supporting programs are generally initialized with the help of TMN when the unit is ready for providing service (Peng et al. 2013). The various state of service including in-service, out-of-service, stand-by as well as selected parameters are controlled by provisioning different functions. It mainly comprises of NE configuration, NE administrative functions and NE database management.

NE status as well as Control: The TMN helps in providing proper capability for monitoring as well as for controlling various aspects of NE. TMN will be helpful in enabling the exclusion for some faulty equipment as a result it assists in rearranging as well as re-route traffic.  (Kanode et al. 2013). It helps in enabling the entry of various proposed configuration for automatically analyzing the feasibility of the design before implementing it. It generally includes generic NE status as well as control functions, message-handling systems as well as network status, leased circuits as well as transmission network status.

 The management information modeling consists of an abstraction of the management aspect of network resources and the associated support management activities. The network resources present helps in determining the various scope of information and data which can be exchanged in a standardized manner (de Assis et al. 2014). The network architecture also helps in providing a set of generic components for network resources. The components also provide high-level abstraction of resources that is connection. It is mainly used by several service applications for providing the network resources to the management.

The disaster recovery plan for a telecommunication network includes the following steps:

Constitute a Disaster Recovery Team: The organization “Telecom Australia” should form a DR team for assisting the entire disaster recovery operations. The team must comprise of core member from all departments of the organization with representative from the top management of Telecom Australia (Tingfang et al. 2015). The team members must be responsible for overseeing the implementation as well as development of the DR Paln.

Performing risk assessment: Proper risk analysis as well as business impact analysis must be conducted which includes various possible disasters both natural as well as man-made. Various disaster scenarios must be conducted for determining the security of various crucial resources.

Prioritizing various processes as well as operations: The critical requirements of the organization that is pertained to each department must be determined properly with respect to various data, documentation, service as well as processes (Sun et al. 2015). They must be categorized properly depending on the priority essential, non-essential as well as important.

Data Collection: Complete data about “Telecom Australia” must be collected as well as documented. The documentation must include inventory of forms, proper policies as well as procedures, communications, equipments, applications, systems as well as various retention schedules.

Creation of Recovery Plan: The DR plan must be generated in a standard format for enabling various detail procedures. All significant procedures must be outlined completely for explaining the plan (Yu et al. 2014). The plan helps in providing systematic information about the disasters. It must all includes different procedures for maintaining as well as updating the plan.

Plan Testing: The disaster recovery plan is mainly developed as well as tested in order to enhance the efficiency. It also assists in providing a platform where proper analysis can be done for making proper adjustments in the plan (Mavromoustakis et al. 2015). The plan should be tested using test like simulation test, parallel test, full interruption test and many more.

 Quality of Service as well as Service Level Agreement management is needed for supporting various modes of accounting as well as alarm handling. Quality of service data is generally needed by the Telecommunication management network from NE either with the help of threshold or with the help of schedule (Lara,  Kolasani and Ramamurthy 2014). It comprises of raw data, which either are required in order to process in a TMN or in a NE, which is very much capable of analyzing the data before the report, is forwarded.

Quality of Service includes monitoring as well as recording of various parameters, which are associated with establishment, retention as well as quality of connection for cooperating properly with the fault management in order to establish possible failure of resources. It also cooperates with various configuration management for changing routing as well as load parameters for links. Element Management Systems helps in detecting the performance threshold crossings, which include SLIPS and BERs, which further assist in forwarding those to the fault manager of NML (Kim and Feamster 2013). This data helps in identifying various degrading facilities before they become apparent to various customers. It also helps in storing the performance measurement data from NEs in order to make it available to EMA report generators to various SML performance management as well as QoS systems.

 EMSs sometimes help in providing the capability to perform various diagnostics depending on the ability of NE as well as EMS. It is related with various communication facilities on a scheduled as well as demand basis (Ghezzi et al. 2015). Quality of service components is fully dependent on the ability of pinpointing the cause of a problem quickly for repairing the resources quickly. The main objective is to achieve the minimum mean time in order to repair the MTTR. In some situations, the procedure of repair can be done from either by NOC or by a customer under the direction of NOC technician (Yaz?c?, Kozat and Sunay 2014). It also helps in reflecting the application of cable telephony for diagnosing the RSU on the customer house. It also helps in performing tests for determining the problem in the customer’s telephone equipment or inside wiring.

The availability of the system is compromised if the failure of the system is not handled correctly. In order to ensure availability of various computing resources, it is quite important to have an effective framework for fault management. An ARMA model is utilized as a parameter prediction method for the framework (Dotcenko, Vladyko and Letenko 2014). The fault management framework helps in predicting the future state of a system by utilizing some components or parameters. The five parameters that are utilized by the framework include monitoring module, pre-processing module, availability analysis module, resource manager module and migration module (Monza et al. 2016). The different modules are connected with the database of the system for storing as well as retrieving various predicted as well as historical data. The monitoring module helps in capturing various set of hardware parameters from each of the physical machine. The different parameters of fault management are observed periodically, which is dependent on a predefined interval.

ARMA model of time series are mainly utilized in order to formulate a system model for predicting various future value of the systems. Results from the model are used for analyzing availability by the fault tree. Fault tree helps in analyzing the structure, which is mainly utilized in reality analysis field. The prediction model is generally created with the help of the data training set. When the real time data is analyzed with the help of the monitoring module, it is mainly fed in order to predict with the help of ARMA prediction model that is generally formulated in the Availability Analyzing module (Yaz?c?, Kozat and Sunay 2014). The output is fed into the module for storing data back into the database of the system. The leaf nodes as well as fault tree are mainly helpful in analyzing the threshold value in order to collect various parameters for calculating the state.

Conclusion

It can be concluded that proper research about the telecommunication network software, helps in providing proper service assurance platform considering TMN and FCAPS. The telecommunication management network not only helps in resolving the issues which are associated with the challenges in providing services to the customers due to expensive as well legacy tool sets. It also assists in expanding the customer base of the organization for providing better customer experience to the customers in the marketplace. It is analyzed that the assignment also provides proper information about development of a disaster recovery plan for a telecommunication network with required procedures and policies. Proper fault management is created in order to resolve the challenges that occurred due to improper fault management. It is identified that fault management includes all the procedures as well as processes that are required for handling various systems for responding properly to the complaints of the customers. In order to ensure availability of various computing resources, it is quite important to have an effective framework for fault management. It is analyzed that an ARMA model is utilized as a parameter prediction method for the framework.

References

Bolla, R., Bruschi, R., Davoli, F., Di Gregorio, L., Donadio, P., Fialho, L., Collier, M., Lombardo, A., Recupero, D.R. and Szemethy, T., 2013. The green abstraction layer: A standard power-management interface for next-generation network devices. IEEE Internet Computing, 17(2), pp.82-86.

Cohn, A.W., Battles, R.E., Proft, D. and Shumate, S.W., Icontrol Networks, Inc., 2013. Method and system for automatically providing alternate network access for telecommunications. U.S. Patent 8,451,986.

de Assis, M.V., Rodrigues, J.J. and Proença, M.L., 2014. A seven-dimensional flow analysis to help autonomous network management. Information Sciences, 278, pp.900-913.

Dotcenko, S., Vladyko, A. and Letenko, I., 2014, February. A fuzzy logic-based information security management for software-defined networks. In Advanced Communication Technology (ICACT), 2014 16th International Conference on (pp. 167-171). IEEE.

Forbes Jr, J.W., Causam Energy, Inc., 2016. System, method, and apparatus for electric power grid and network management of grid elements. U.S. Patent 9,513,648.

Ghezzi, A., Cortimiglia, M.N. and Frank, A.G., 2015. Strategy and business model design in dynamic telecommunications industries: A study on Italian mobile network operators. Technological Forecasting and Social Change, 90, pp.346-354.

Han, B., Gopalakrishnan, V., Ji, L. and Lee, S., 2015. Network function virtualization: Challenges and opportunities for innovations. IEEE Communications Magazine, 53(2), pp.90-97.

John, W., Pentikousis, K., Agapiou, G., Jacob, E., Kind, M., Manzalini, A., Risso, F., Staessens, D., Steinert, R. and Meirosu, C., 2013, November. Research directions in network service chaining. In Future Networks and Services (SDN4FNS), 2013 IEEE SDN for (pp. 1-7). IEEE.

Kanode, M.E., Karmarkar, K.K., McCann, T.M., Sprague, D.M., Tomar, M., Wallace, D.E. and Marsico, P.J., Tekelec, Inc., 2013. Methods, systems, and computer readable media for diameter network management. U.S. Patent 8,498,202.

Kim, H. and Feamster, N., 2013. Improving network management with software defined networking. IEEE Communications Magazine, 51(2), pp.114-119.

Lara, A., Kolasani, A. and Ramamurthy, B., 2014. Network innovation using openflow: A survey. IEEE communications surveys & tutorials, 16(1), pp.493-512.

Mavromoustakis, C.X., Bourdena, A., Mastorakis, G., Pallis, E. and Kormentzas, G., 2015. An energy-aware scheme for efficient spectrum utilization in a 5G mobile cognitive radio network architecture. Telecommunication Systems, 59(1), pp.63-75.

Mijumbi, R., Serrat, J., Gorricho, J.L., Latre, S., Charalambides, M. and Lopez, D., 2016. Management and orchestration challenges in network functions virtualization. IEEE Communications Magazine, 54(1), pp.98-105.

Monza, J.V., McCord, A.W. and Anderson, D.H., Genesys Telecommunications Laboratories, Inc., 2016. Method and system for providing adaptive and proactive interaction management for multiple types of business interactions occurring in a multimedia communications environment. U.S. Patent RE46,181.

Peng, M., Liang, D., Wei, Y., Li, J. and Chen, H.H., 2013. Self-configuration and self-optimization in LTE-advanced heterogeneous networks. IEEE Communications Magazine, 51(5), pp.36-45.

Sun, S., Kadoch, M., Gong, L. and Rong, B., 2015. Integrating network function virtualization with SDR and SDN for 4G/5G networks. IEEE Network, 29(3), pp.54-59.

Tingfang, J.I., Song, O., Damnjanovic, A., Gaal, P., Luo, T. and Malladi, D.P., Qualcomm Incorporated, 2015. Heterogeneous network (HetNet) user equipment (UE) radio resource management (RRM) measurements. U.S. Patent 9,125,072.

Wood, T., Ramakrishnan, K.K., Hwang, J., Liu, G. and Zhang, W., 2015. Toward a software-based network: integrating software defined networking and network function virtualization. IEEE Network, 29(3), pp.36-41.

Yaz?c?, V., Kozat, U.C. and Sunay, M.O., 2014. A new control plane for 5G network architecture with a case study on unified handoff, mobility, and routing management. IEEE Communications Magazine, 52(11), pp.76-85.

Yu, T., Zhou, Z., Zhang, D., Wang, X., Liu, Y. and Lu, S., 2014, April. INDAPSON: An incentive data plan sharing system based on self-organizing network. In INFOCOM, 2014 Proceedings IEEE (pp. 1545-1553). IEEE.