“Multi-Technology Operations System Interface (MTOSI) is a standard for implementing interfaces between OSSs. Service providers (carriers) use multiple Operational Support Systems (OSS) to manage complex networks. Since the various parts of the network must interact, so must the OSSs. It is standardized by the Telemanagement Forum (TM Forum). The TMF Frameworx provides a set of reference models that aid in analyzing and designing next generation BSS and OSS solutions that may utilize the MTOSI interface specifications.”
In yesterday’s blog, I spoke of a connectionless modelling spec that supports MTOSI but then realised that I haven’t described MTOSI anywhere here on my site.
MTOSI is an interesting concept for organisations that have multi-layered network (ie SONET/SDH/DWDM through to higher order layers such as IP and above with various different EMS) and/or multi-vendor networks as well as a variety of OSS/BSS tools. The theory is that commonality / consistency between interfaces should allow the various management applications (eg EMS, OSS, BSS, etc) to be integrated more quickly and easily.
As shown in the diagram below, MTOSI specifies a middleware layer (the Common Communication Vehicle – CCV) that maps MTOSI interfaces from various applications. It should be noted that the MTOSI specification is generic enough to allow middleware neutrality so that organisations can bind MTOSI to any middleware of their choosing. As can also be observed in the diagram, MTOSI supports key OSS functionalities for information sharing including workflow, discovery, inventory, order management, alarm notification / retrieval, etc.
MTOSI builds upon Web Services Description Language (WSDL) and eXtensible Markup Language (XML) and is built for alignment with OSS/J.
You may like to have a look at this great slide-deck for a deeper analysis of MTOSI and it’s MTNM (Multi-Technology Network Management) roots.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email