MTOSI

Last updated

In telecommunications, 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.

Contents

Description

A visual representation of the TMF MTOSI offered SOA Service Candidates is shown in the figure.

The MTOSI specifications are produced by the TM Forum MToP program.[ citation needed ]

MTOSI standard is a unified open interface that can be used among multiple types of management systems to provide network and service management. MTOSI standard covers all communication technologies (from layer 1, e.g., SONET/SDH, through higher layer technologies such as VoIP).

MTOSI facilitates application-to-application inter-working, reduces time to deployment, and lowers the cost of ownership of systems.

Figure 1

Current management and support system implementations employ diverse middleware technologies, a reality that is not likely to change in the immediate future. To be widely adopted, MTOSI cannot mandate specific middleware technologies for its implementation. Therefore, the MTOSI interfaces are sufficiently abstract to be middleware neutral, yet rigorous enough that vendors can map them quickly to their middleware of choice. The CCV is the common middleware required to implement MTOSI.

CCV is a middleware abstraction that allows MTOSI interfaces to be bound to different middleware technologies as needed. By exploiting the expressive power of Web Services Description Language, MTOSI interfaces are composed of logical and physical definitions.

MTOSI standard offers a number of unique business advantages (1-4) as well as advantages applicable to any well-designed and well-supported interface standard (5-8):

1. MTOSI provides a standard interface between different systems for fulfillment and assurance functionality. In effect different instances of the same interface are reused at different reference points. Benefit: Knowledge can be re-used in the design of systems
2. MTOSI uses XML (eXtended Mark-Up Language) based messaging. Benefit: XML technology is widely accepted and used technology.
3. MTOSI provides rules for versioning and for vendor extensions to the XML messages. Benefit: When MTOSI is deployed, the server and consumer application ends of the interfaces can be upgraded independently. Also, when several vendors’ equipment is deployed, the proprietary extensions are managed in a consistent manner.
4. MTOSI uses standard communication patterns to support business activities that can be implemented by a range of IT platforms and transport protocols. Benefit: The underlying platform can be changed without propagating the change to the applications.
5. MTOSI allows service providers to implement management and support systems quickly. For example, without MTOSI, each of the four EMS providers in Figure 1 would need to define and agree upon a common interface (on a pair-wise basis), build the interface and then do interoperability testing. Benefit: MTOSI lowers the time and costs needed to integrate management and support system software from different suppliers.
6. MTOSI is designed to support service provider requirements for an open systems environment. Benefit: This allows service providers to more easily deploy management and support systems from multiple vendors and to replace existing ones. This increase in choice creates a more competitive environment for service providers, allowing them to choose products that best fit their functional and financial needs.
7. MTOSI encourages system integrators to pre-integrate products that are MTOSI-compliant. Benefit: This results in lower up-front costs and faster deployment for service providers.
8. MTOSI helps carriers to avoid wholesale replacements of legacy systems and instead allows them to introduce and integrate point applications that can address new solutions and services. Benefit: Allows a service provider to preserve its investment in legacy systems while still addressing the need to manage new technologies and services.

The MTOSI standard is available for download to members of the TM Forum. Membership fees are based on corporate annual revenues.

Related Research Articles

Middleware in the context of distributed applications is software that provides services beyond those provided by the operating system to enable the various components of a distributed system to communicate and manage data. Middleware supports and simplifies complex distributed applications. It includes web servers, application servers, messaging and similar tools that support application development and delivery. Middleware is especially integral to modern information technology based on XML, SOAP, Web services, and service-oriented architecture.

A web service (WS) is either:

Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the complexity of developing applications that span multiple operating systems and network protocols. The middleware creates a distributed communications layer that insulates the application developer from the details of the various operating systems and network interfaces. APIs that extend across diverse platforms and networks are typically provided by MOM.

In software engineering, service-oriented architecture (SOA) is an architectural style that focuses on discrete services instead of a monolithic design. By consequence, it is as well applied in the field of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies.

Enterprise application integration (EAI) is the use of software and computer systems' architectural principles to integrate a set of enterprise computer applications.

Element management is concerned with managing network elements on the network element management layer (NEL) of the TMN . An element management system (EMS) manages one or more of a specific type of telecommunications network elements (NE).

Enterprise service bus Communication system in a service-oriented architecture

An enterprise service bus (ESB) implements a communication system between mutually interacting software applications in a service-oriented architecture (SOA). It represents a software architecture for distributed computing, and is a special variant of the more general client-server model, wherein any application may behave as server or client. ESB promotes agility and flexibility with regard to high-level protocol communication between applications. Its primary use is in enterprise application integration (EAI) of heterogeneous and complex service landscapes.

CEN/XFS or XFS provides a client-server architecture for financial applications on the Microsoft Windows platform, especially peripheral devices such as EFTPOS terminals and ATMs which are unique to the financial industry. It is an international standard promoted by the European Committee for Standardization. The standard is based on the WOSA Extensions for Financial Services or WOSA/XFS developed by Microsoft.

Call Control eXtensible Markup Language (CCXML) is an XML standard designed to provide asynchronous event-based telephony support to VoiceXML. Its current status is a W3C Proposed Recommendation, adopted May 10, 2011. Whereas VoiceXML is designed to provide a Voice User Interface to a voice browser, CCXML is designed to inform the voice browser how to handle the telephony control of the voice channel. The two XML applications are wholly separate and are not required by each other to be implemented - however, they have been designed with interoperability in mind

OSS/J is a TM Forum technical program whose primary goal is to develop open interface standards (APIs) for the integration of Business Support Systems (BSS) & Operations Support System (OSS).

Uniface (programming language) Low-code development platform

Uniface is a low-code development and deployment platform for enterprise applications that can run in a large range of runtime environments, including mobile, mainframe, web, Service-oriented architecture (SOA), Windows, Java EE, and .NET. Uniface is used to create mission-critical applications.

An XML appliance is a special-purpose network device used to secure, manage and mediate XML traffic. They are most popularly implemented in service-oriented architectures (SOA) to control XML-based web services traffic, and increasingly in cloud-oriented computing to help enterprises integrate on premises applications with off-premises cloud-hosted applications. XML appliances are also commonly referred to as SOA appliances, SOA gateways, XML gateways, and cloud brokers. Some have also been deployed for more specific applications like Message-oriented middleware. While the originators of the product category deployed exclusively as hardware, today most XML appliances are also available as software gateways and virtual appliances for environments like VMWare.

A service delivery platform (SDP) is a set of components that provides a service(s) delivery architecture for a type of service delivered to consumer, whether it be a customer or other system. Although it is commonly used in the context of telecommunications, it can apply to any system that provides a service. Although the TM Forum (TMF) is working on defining specifications in this area, there is no standard definition of SDP in industry and different players define its components, breadth, and depth in slightly different ways.

Communications servers are open, standards-based computing systems that operate as a carrier-grade common platform for a wide range of communications applications and allow equipment providers to add value at many levels of the system architecture.

Service-oriented architectures (SOA) are based on the notion of software services, which are high-level software components that include web services. Implementation of an SOA requires tools as well as run-time infrastructure software. This is collectively referred to as a service-oriented architecture implementation framework or (SOAIF). The SOAIF envisions a comprehensive framework that provides all the technology that an enterprise might need to build and run an SOA. An SOAIF includes both design-time and run-time capabilities as well as all the software functionality an enterprise needs to build and operate an SOA, including service-oriented:

Frameworx is an enterprise architecture framework geared towards communications service providers.

The Spacecraft Monitoring & Control (SM&C) Working Group of the Consultative Committee for Space Data Systems, which sees the active participation of 10 space agencies and of the Space Domain Task Force of the Object Management Group, is defining a service-oriented architecture consisting of a set of standard end-to-end services between functions resident on board a spacecraft or based on the ground, that are responsible for mission operations.

openTMS is an acronym for Open Source Translation Management System.

Operations support systems (OSS), operational support systems in British usage, or Operation System (OpS) in NTT, are computer systems used by telecommunications service providers to manage their networks. They support management functions such as network inventory, service provisioning, network configuration and fault management.

Cloud Infrastructure Management Interface (CIMI) is an open standard API specification for managing cloud infrastructure.

References

    This page is based on this Wikipedia article
    Text is available under the CC BY-SA 4.0 license; additional terms may apply.
    Images, videos and audio are available under their respective licenses.