Using MTOSI in BTs 21CN Project

Name of company submitting case study: Huawei Technologies Co., Ltd

www.huawei.com
Names of authors:
Wayne Thompson, Huawei
Jessie Jiang, Huawei
Lily Zhou, Huawei
Kevin Yu, Huawei
Wei Yue, Huawei
Contact for further information: Wayne Thompson, wayne.thompson@huawei.com
Applicable TM Forum technical areas: MTOSI
CATEGORIES APPLICABLE TO THIS CASE STUDY:
VIEWPOINT:
NETWORK TECHNOLOGIES:
Service provider perspective
Mobile GSM/GPRS
Software vendor perspective
Mobile CDMA/EVDO


Hardware vendor perspective
Mobile Edge/UMTS
System integrator perspective
ATM
SONET/SDH
MPLS

Ethernet
SERVICES:


Voice
Frame Relay
Video
Converged network


Data
Cable
VoIP
Satellite

Broadband
IPTV

Fixed Line
VPN

DSL
Content

IP
WiFi/WiMax
APPLICABLE MARKETS:


All
US/Canada
Western Europe
Eastern Europe
Asia
Latin America
Australia

Huawei Case Study

Page 1

April 2006

Applicable Telecom Application Map Categories:

Market/Sales
Resource Management


Campaign Management
Resource Inventory Management
Channel Sales Management
Workforce Management


Product/Service Catalogue
Resource Planning/Optimization
Product Life Cycle
Resource Design/Assign
Management

Resource Activation

Resource Provisioning/
Product
Configuration



Resource Logistics
Product/Service Catalogue
Product Life Cycle
Correlation & Root Cause Analysis
Management
Resource Performance

Monitoring/Management
Customer Management
Resource Data Mediation

Resource Status Monitoring
Customer Contact, Retention &
Loyalty
Customer Self Management
Resource Testing Management
Order Management
Resource Problem Management
Customer QoS/SLA
Billing Data Mediation
Management
Customer Service/Account
Arbitrage Management
Problem Resolution
Customer Billing Management
Real-time Billing Management
Collection and Receivables
Management
Fraud Management
Enterprise Management

Service Management
Service Design/Assign


Service Configuration
Management
Service Performance
Management
Service Quality Monitoring &
Impact Analysis
Service Problem Management
Revenue Assurance
Management
Service Rating/Discounting
Management

HR Management
Financial Management
Asset Management
Security Management
Knowledge Management

Supplier/Partner Manager
Partner Management
Supply Chain Management
Wholesale/Interconnect Billing

Huawei Case Study

Page 2

April 2006

Business Problem to be solved:

The BT21CN project face similar service management challenges to those experienced
by all commercial service providers in that the cost of integration between disparate OSS
platforms and element management platforms is one of the major contributions to
CAPEX expenditure. There are enormous business benefits to being able to separate the
business logic from the massive technical complexity at the network level. One of the
greatest challenges to being able to achieve this abstraction at the OS level has been the
requirement to communicate and manage many different sets of vendor technologies
using an agreed standard between all parties. This project was developed using an
MTOSI compliant interface module which provides a unified open interface which can be
utilized to bridge the gap between the existing OSS layer and the element management
platforms
A primary objective for the integration was to incorporate the MTOSI standard interface
into the whole design methodology in order to ensure an open OSS interface is available
between each vendor platform. The following paper discusses how Huawei, a leading
telecommunications infrastructure provider is using the MTOSI standard.

Working towards a solution:

There are presently three specific criteria which make up the present interface
specification these being;
1) Inventory retrieval based upon MTOSI v1.0
2) Service provisioning for broadband, Ethernet, Voice, VOIP, VLAN and ISDN services
3) Test and Diagnoses

The MTOSI V1.0 presently only defines the physical model therefore we utilized the
published MTNM v1.0 standard and aspects of the emerging standard MTNM v3.5
Ethernet model to define the provisioning model for Ethernet and VLAN and broadband,
VOIP and voice services. Therefore working in close collaboration with the other OSS
and EMS vender suppliers the team was able to develop the service provisioning
interface to support these services.

Solution:

Service provision adopts the coarse grained service provision interface based on the
MTOSI standard.
The coarse grained service provision interface processes all the service provision requests
with the transaction interface. A transaction request contains a series of object
combination of action and mtosiObjects.

Huawei Case Study

Page 3

April 2006

An action indicates the operations performed on mtosiObjects, including build, destroy,

enable, disable, modify, associate, and disassociate.
An action can be performed on one or more objects. Some action, such as associate,
must be performed on two or more objects.
mtosiObjects is the object set defined in the MTOSI. The mtosiObjects can be:


An object


A set of several objects of the same type


A set of objects of different types
The Inventory retrieval interface was based on MTOSI Release1.0, getInventory coarse
grained interface. Satisfies the following scenarios,
1) Retrieve a specific ME name/attributes
2) Retrieve a specific card name/attributes
3) Retrieve a specific shelf/slot name/attributes
4) Retrieve a specific PTP/CTP name/attributes
5) Retrieve all ME under a specific MD
6) Retrieve all slots under a shelf
7) Retrieve all cards under a shelf
8) Retrieve all PTP under an ME
Etc.
The following describes the functions of the entities

Inventory OS

Provision OS

MTOSI

MTOSI
CCV(HTT)
MTOSI
XML NBI
N200
0

EM
S

Inventory OS Inventory Management OS

Provision OS Service Provisioning OS

CCV Common Communication Vehicle

EMS Element Management System

XML NBI XML Northbound Interface

N2000 Huawei EMS

Huawei Case Study

Inventory OS: The inventory operations system of the carrier,

which provides the Common Communication Vehicle (CCV)
interface that meets the Multi Technology Operations System
Interface (MTOSI) standard.

Page 4

April 2006

Provision OS: The service provision operations system of the

carrier, which provides the CCV interface that meets the MTOSI
standard.
XML northbound interface: The extensible mark-up language
northbound interface, which provides interface for other OSS, such
as inventory OS and provision OS, to connect to the Element
Management System (EMS). The interface is a CCV interface
meeting the MTOSI standard.
N2000: The fixed network integrated management system of
Huawei Technologies Co., Ltd., which provides the customized
private interface. The XML northbound interface running on the
N2000 converts the private interface into the interface meeting the
MTOSI standard for other OSS.

The MTOSI process provided an overall structure and business process for the
architecture. The key feature of this architecture is that it supports synchronous Simple
Request/Reply (SSRR) of the MTOSI XML Message Exchange Patters (MEPs). The
protocol between the OS and the EMS supports SSL (HTTPS) and HTTP 1.0/HTTP1.1
keep-alive
Synchronous Simple Request/Reply
Services Requestor

Services Supplier

SOAP Client Stub/Skeleton

OS
HTTPS

SOAP Server Stub/Skeleton

Keep-alive

HTTPS

Services Requestor: Call services method

Service supplier: Implement services method.

SOAP Client Stub: Generated by gSOAP

tools, supports WSDL 1.1, SOAP 1.1, SOAP
1.2, SOAP RPC encoding style, and
literal/document style

SOAP Server Stub: Generated by gSOAP

tools, supports WSDL 1.1, SOAP 1.1, SOAP
1.2, SOAP RPC encoding style, and
literal/document style

HTTPS HTTP support SSL

Results:

This is an on going project is being regarded as a successful as it is a joint development

between all three development parties. The primary objective is to develop an MTOSI

Huawei Case Study

Page 5

April 2006

compliant interface which has minimal vendor specific variations. The lessons learned
form the project are:

The MTOSI interface specification and development has been a shared process
between the parties, this sharing of requirements has enabled the interpretation
and development process to be enhanced due to the sharing of knowledge.
By sharing knowledge and experiences between the EMS vendors, and OSS
provider, this has helped to develop an open standards based solution.
As the initial design stage definition was shared between all parties this had a
major saving in terms of time and validation during the integration phase of the
project.
The interface is flexible as it doesnt constrain the granularity against the interface.
Our service provisioning coarse-grained interface is technology independent. It
therefore it is not constrained by technology for example the same interface could
be utilized to provision xDSL services.

In conclusion the team has produced an MTOSI compliant interface that demonstrated
the ability to apply the MTOSI standards across differing element management platforms.
In the solution the interface variations between each vendor has been kept to a minimum
and thereby enabling the development of the interface to be a shared project between
companies.
The MTOSI interface specifications are still maturing however when a particular part of
the standard was unavailable shared discussion and development between the parties
enabled a compliant solution to be developed.
As the MTOSI standard is still in development there will always be some requirement
which is not presently defined however we are convinced that there is sufficient material
available today to enable other equipment vendors to substantially reduce the cost, time
and effort required to develop a MTOSI standard interface.

Huawei Case Study

Page 6

April 2006