Popular Posts

Tuesday, April 06, 2010

TM Forum's MTOSI standard: Setting the Context

MTOSI stands for Multi-Technology Operations Systems Interface. It is a standard specified by TM Forum. It is now part of TM Forum's Interface Program (TIP).

Why is it called "multi-technology"? Why do you need to worry about it? What does it really do? How does it relate to other TM Forum standards and initiatives (often, quite confusing for starters!)? This article attempts to explain the answers for these questions.

This article is organized as follows: 
1) Intent

The intent of TeleManagement Forum's (TMF) Multi-Technology Operations Systems (MTOSI) is to provide open and standards-based interfaces between OSSs (e.g., Service Activation systems, Inventory systems, Network Management Systems, Element Management Systems, etc.). For a detailed exploration of OSS/BSS systems, see my earlier post titled "Telecom OSS/BSS: An Overview".

2) Related TM Forum Standards

2.1 Relationship with MTNM

TeleManagement Forum's (TMF) Multi-Technology Operations Systems Interface (MTOSI) started as an MTNM (Multi-Tehchnology Network Management) substream sometime in 2003. Lets discuss MTNM first.

MTNM provides CORBA-based Element Management Layer (EML)-to-Network Management Layer (NML) interfaces for the management of "multi-technology" networks (SONET, SDH, PDH, ATM, Frame Relay, DSL, connectionless networks such as Ethernet, etc.). However, it can also be used to support a single technology such as ATM. Examples of management areas are: connection management, NE and EMS configuration, network inventory discovery, euqipment inventory management, performance monitoring, alarm surveillance and event reporting, etc. MTNM can also be used to manage a particular subset of a management area - say, alarm surveillance.

Around the time MTNM 3.5 commenced, it was realized that several vendors were using MTNM by converting the CORBA IDLs to XMLs, due to lack of XML based interfaces. Enter MTOSI.

MTOSI has gradually taken sets of MTNM interfaces, generalized the operations systems to operations systems interactions and created XML, SOAP Web services based interfaces - recasting and extending MTNM. Like MTNM, it provides a single interface for the management of many technologies. Moreover, MTOSI has had the goal to make XML interfaces independent of the underlying transport (HTTP, JMS, etc.)

2.2 Relationship with TIP and mTOP

MTOSI has been part of TM Forum Interface Program (TIP) since April 2008. Multi Technology OSS Program (mTOP) coordinates advances in the SOAP and XML based MTOSI interface standard, as well as the CORBA/IDL based MTNM standard. MTOSI service classifications are based on the eTOM model, while the information model is based on SID and MTNM data models.

2.3 Comparision with OSS/J

MTOSI APIs are focused towards providing interfaces at the service, network and element management layers. OSS/J on the other hand aims to provide open interfaces across the spectrum of both OSS and BSS. OSS/J APIs, unlike most MTOSI APIs are network technology independent [1]. OSS/J APIs are entity centric unlike MTOSI APIs that are task-centric. OSS/J provides a generic set of operations on "Managed Entities" [1]. There are efforts underway to draw the OSS/J and MTOSI communicaties together, and we may see a common goals and plans for migration for both OSS/J and MTOSI in the future.

3) Motivation

Element Management Systems (EMS) typically manage the functions of Network Elements (switches, CPU and remote hubs, gateways, routers, susbcriber line units, etc.) from a single vendor. Examples of such management functions include receiving and executing commands sent by upstream activation systems, feeding equipment status data back to upstream systems such as network and trouble management systems, etc. Moreover, the EMS may be able to manage functions related to a single technology (e.g., ATM, SONET, etc.) for a subset of management area (e.g., performance monitoring). Therefore a service provider environment typically has several types of EMS. Typically a Network Management System (NMS) manages functions of many EMSs. To be easily portable across different NMS systems, an EMS vendor can provide MTOSI based standards interface. This would enable easy integration of the EMS with various NMS that service providers could use.

Lets consider another example. A service activation system (an OS) may allow an order management system (also an OS), to request activation of a given service via a service request. The service activation system (an OS) may in turn need to send requests to multiple NMS and EMS OS's to complete the service activation request. A service provider environment in all likelihood contains multiple service activation systems as well as multiple EMS's. If each of those provided proprietary interfaces containing proprietary information models: a) the order management system must be integrated with each of the service activation interfaces, and b) the service activation systems must be integrated with the relevant EMS interfaces. With many services being added on frequent basis, this can easily turn into a nightmare. Utilizing standards-based interfaces provided by MTOSI the integration becomes lot more easier, reducing costs and increasing agility.

Lets consider yet another example. Say, an operator uses Telcordia TIRKS system to administer Layer 1 facilities and equipment while it uses a seperate OSS inventory system to administer Layer 2/3 (logical inventory) and higher services. TIRKS provides an open interface (data dictionaries and XML message definitions) using MTOSI which can be used by the OSS inventory systems to receive messages generated by TIRKS systems (such as inventory update notifications) and to send messages to the TIRKS system.

Similarly, a fault managent system may need to subscribe to alarm reports based on filtering conditions and may also handle subsequent reporting of alarms to subscribed OSs. Similarly, a manager fault management system may receive alarms from several technology-specific fault management system via active alarm sync.

4) MTOSI Description

MTOSI defines OS-to-OS (OS stands for operations systems) interfaces for service and resource management, where OS functionality can be at the levels of Element Management Layer, Network Management Layer or the Service Management layer, in the Telecommunications Management Network (TMN) Logical model.

Examples of such OS in this context include: Inventory Management, Performance Management Systems, Fault Management Systems, Service Activation, Service Assurance, CRM systems such as Order Entry system, Network Management systems, Element Management Systems (EMS). Refer to my earlier post titled "Telecom OSS/BSS: An Overview" for a description of some of these.

Note, that MTOSI is not concerned with EMS-to-NE API, which is typically based on protocols such as SNMP, TL or CMIP. Nor is it concerned with internal implementation details such as an internal inventory model - it only provides a data format and a number of operations around retrieving or modifying the data.

Management functions covered by MTOSI include (but not limited to): 
  • Inventory Retrieval, Inventory Update Notifications, Enhanced Inventory Retrieval (attribute value matching based on XPath), Multi-Event Inventory Notifications (ability to send multiple inventory updates in a single notification)
  • Alarm Reporting, Active Alarm Retrieval
  • Service Activation
  • Service Inventory Management
  • Resource configuration and activation
  • Performance management and maintenance commands
  • Multi-Action and Request Transactions (MART) (i.e., ability to package multiple requests into a single message)
The output of the MTOSI effort can be downloaded from the TM Forum Web site. The output is partitioned into something called as Document Delivery Packages (DDPs) - often organized based on functional areas (such as resource inventory management). The framework DDPs contain the generic aspects applicable to all other DDPs while the Data Model DDPs contain aspects related to entities, data structures, attributes and states. Each DDP also contains the following set of documents:

  • TMF 518, MTOSI Business Aggreement (BA): Identifies the requirements and use cases to be supported by the interface.
  • TMF 612, MTOSI Information Aggreement (IA): UML description of the interface.
  • TMF 864, MTOSI Interface Implementation Specifications (IIS): Maps the UML model to XML (WSDL, XSD, bindings, etc.)
  • Supporting documentation
5) References

[1] "Bridging the Gap Between MTOSI and OSS/J" by Nigel Davis, John Reilly and Suresh Bhandarkar
[2] "Implementing NGOSS with MTOSI"
[3] "A very short history of mTOP" (Requires login to TM Forum site)
[4] Tim McElligott, "MTOSI brings OSS Integration a Step Closer", Nov 2005,
[5] "Designing a Standards-Based Application", March 2009,
[6] Stephen Fratini, Irene McGoey, Garry Grimes and Enrico Grosso, "Introduction to the TM Forum's Multi-Technology Network Model", National Fiber Optic Engineers Conference, 2001
 

10 comments:

jaakovb said...

I read your interesting paper.
I'm novice in WEB Services, and I'm wondering if you have experience with MTOSI implementation and more precisely if you have some good recommendation regarding the IDE to use (Eclipse, Netbeans...) and a SOAP engine (Axis..) and WEB Service container (Apache, Glassfish...).

Ravi Sharda said...

A good comparision on IDEs is here. Although my personal preference is Eclipse -just because I have used it for along time, I have also used Netbeans and found it very easy to do complicated things easily. For example, writing JSF based UIs or creating JPA based components and configuration XMLs become very easy with Netbeans.

Refer to the Web Services Comparison chart, which does a stack comparison of Axis (1.x, 2), Celtix, Glue, JBossWS, XFire and GlassFish. With JAX-WS 2.x in place, I'd suggest using pure JAX-WS specific syntax and semantics to provide and consume Web services, rather than utilize any SOAP engine specifics (simply, so that you could move from one to another).

Both Tomcat and Glassfish can run your Web services, the selection typically depends on decision made on the server based on factors not related to Web services alone.

jaakovb said...

Thanks for your answer.

I think you are definitively right about using pure JAX-WS.
We still evaluating NetBeans (currently used for Java application) and JDevelopper as IDE (seems that have a better support for WS especially for running generated tests), and should decide soon.

cnu said...

Hello All, I have just started on reading and understanding MTOSI. I have few starter level questions , Appreciate if you can help.

I am doing a POC for implementing Manager of Managers(MOM)for two existing NMS Systems.
The primary objective is Alarm Management.
What might be the role of MTOSI here ?
Can we develop Manager of Mangers Using MTOSI?

Thanks in Advance.

Raj said...

Hi Ravi,

I am new to OSS, I need to learn about MTOSI. I wonder how to integrate MOTSI with jax-ws. I am not sure where to start.

A simple example is highly appreciated.

Please advice.

Regards
Raj

Inventory Management Software said...

I really appreciate your post and it was superb .Thanks for sharing information.
Regards:
http://www.blackitsoft.com/inventory-pos-software.aspx

Woo Yong Lam said...

Hi Ravi...Im very new in web services and im now required to understand what is MTOSI namespace that used in xml. Can you give me some guidance or please correct me if my question sounds weird. Thanks...

shanecastane said...


Through the holiday season, present your products as gifts. This might not be considered a excellent approach for your website, but it is pertinent on social networks. Publish updates about your products as Christmas presents and wait for your visitors to simply accept this as being a likelihood instead of pushing this idea in your site. This Webpage

Business Management System

sudheesh said...

thanks a lot for publishing this article.

I am new to TMF 864.Where can I get the tutorials and docs.Could you please share if you have ant URL

Thanks in advance
Sudheesh

Prologic Corporation said...

This is a good article & good site.Thank you for sharing this article. It is help us following categorize:
healthcare, e commerce, programming,multi platform, it consulting, retail, manufacturing, CRM, technology means, digital supply chain management, Delivering high-quality service for your business applications,
Solutions for all Industries,
Getting your applications talking is the key to better business processes,
Rapid web services solutions for real business problems,
Web-based Corporate Document Management System,
Outsourcing Solution,
Financial and Operations Business Intelligence Solution,

Our address:
2002 Timberloch Place, Suite 200
The Woodlands, TX 77380

prologic-corp