MTOSI: Meeting the Integrated OSS Challenge

1
MTOSI Meeting the Integrated OSS Challenge

• 1st March 2006

2
Agenda

• MTOSI Overview Why MTOSI?
• MTOSI Catalyst in Detail
• MTOSI and Transport Independence
• MTOSI Now and Next Steps
• Questions

3
MTOSI Overview Why MTOSI?
4
The Challenge
Integrations cost Integration complexity Reduced
features Delay to revenue
Convergence
5
MTOSI Benefits
MTOSI Catalyst Demonstrates how the MTOSI
Standard benefits different types of Stakeholders
6
MTOSI - a Realization of NGOSS
Targets Commercial out of the box integration
plug and play for OSS interconnection
7
MTOSI and MTNM positioning
MTNM Point-to-Point MTOSI Bus-Structure
NMS
OS
OS
OS
MTOSI
MTOSI
MTOSI
CORBA
XML
MTNM
CCV
MTOSI
MTOSI
EMS
OS
OS
subordinate OS
subordinate OS
OTN
Ethernet
SDH
WDM
ATM
DSL
SONET
ASON
MPLS
IP
WiMax
8
mTOP in an Industry Context
Industry
3GPP
ETSI TISPAN
ITU-T
MSF
OSS/J
ATIS TMOC
MEF
DSL Forum
OIF
etc
Liaisons/Collaborations
TMF
Operators Specs
Operators Networks
eTOM
SID
NGOSS Framework
TNA
Vendors Specs
Vendors Products
mTOP Project
RI Catalysts
MTNM
Change Requests
Architecture
Methodology
Implementation
MTOSI
Feature Requests
PPC Prioritisation
Working Teams (Development)
Delivery
IPNM

• mTOP project provides NGOSS compliant interface
  definitions

9
A Collaborative Approach

• TMF Documentation
• NGOSS Principles
• NGOSS Lifecycle Methodology
• Shared Information/Data Model
• Multi-Technology Management
• eTOM

Compliance with TMF Documentation
Common application with other Catalysts

• TMW Catalysts
• NGOSS Service Enablement
• End-to-End Service Fulfillment for VoIP

Mutual Teaming
Liaisons Alliances
10
MTOSI Catalyst in Detail
11
Catalyst Network Topology
Scenarios A and B
12
Demo Scenario AB
CISCO
EMS
Assurance Telcordia Service Director
OSS/J Order Manager Ceon
Telcordia Granite Inventory

Assurance Netrac TTI
Inventory Telcordia TIRKS CE
CISCO
EMS
B
A
SP company A merges with SP company B. Company A
has an OSS/J order manager and a core system to
handle L1 Inventory. With MTOSI Any Network -
One Interface, the two companies are able to
quickly complete the IT consolidation and offer
an integrated solution
Telcordia is a registered Trademark of Telcordia
Technologies, Inc. TIRKS is a registered
trademark of Telcordia Technologies
13
The Customer View
Acme Bank needs an Ethernet Private Line (EPL)
service between two offices in Dallas with
guaranteed QoS. Acme Bank accesses Ceon portal
to purchase the EPL service.
Dallas North East
Dallas North
Ethernet Private Line
Fast Eth
Fast Eth
15454
15454
Huawei
Huawei
15454
14
Establishing the Access Path
TIRKS CE (L1 Inv. subsystem) receives and
processes the Service Order establishing L1
connectivity. Granite Inventory (L2 Inv.
subsystem) establishes pointers for the circuit
back to the L1 subsystem.
PTP /shelf1/slot13/ptp1
TL client1/DLLSTXN1KCD
TL client1/DLLSTXN2KCD
CTP /shelf1/slot12/ptp1/ctp1
client1
client2
FTP /shelf1/slot1/ftpPOS-0
FTP /shelf1/slot1/ftpPOS-1
PTP /shelf1/slot1/ptp1
Client Managed Element MSPP Managed Element OC192
Physical Term Pt CE-100T-8 PTP CTP (Connection
Term Pt) FTP (Floating Term Pt) Topological
Link SNC (SubNetwork Conn)
DLLSTXN1KCD
DLLSTXN2KCD
DLLSTXS1KCD
15
When things go wrong
Fast Eth
Fast Eth
15454
15454
Huawei
Huawei
15454
16
Catalyst Network Topology
Scenario C
Scenario C
17
Delivering Ethernet Service

• Discover Network Inventory
• Newly commissioned Huawei DSLAMs
• Activate Gigabit Ethernet Service
• Over Nortel Optical Network

18
OSS Systems View
TaskEngine
SyncEngine
DeliveryEngine
Cramer Accelerates Service Delivery in Next
Generation Networks
19
Solving The Problem Today
The MTOSI Catalyst Demonstrates realistic
end-to-end provisioning and assurance scenarios
20
Solving The Problem Today
TTI Telecom Assurance
Cramer
Telcordia Assurance
Telcordia Inventory
Ceon
Scenario A Establishing Infra-Structure
Scenario B Network Performance and Fault
Monitoring
Pantero
IONA
Sonic
Scenario C Network Discovery and Service
Activation
Cisco
Nortel
Huawei
21
Catalyst Value

• This Catalyst shows the power of the MTOSI
  standard
• 11 companies across the globe
• 1 Standard
• Successful implementation on real systems!
• Short integration cycle demonstrates the value of
  the MTOSI standard in production systems!

22
MTOSI And Transport Independence
23
MTOSI and Transport Independence

• Common Communication Vehicle (CCV)
• Connect distributed and heterogeneous Systems and
  Services
• IONA is unique in its ability to support Multiple
  transports with WSDL interfaces
• Leverage existing assets
• Real word scenario
• Connecting Inventory and Element Management
  System

24
Scenario C Network Discovery and Service
Activation
25
Service Activation Protocol Bridging
CCV
SOAP
Operations System
JMS
SOAP/JMS
SOAP/HTTP
NMS
26
Standards Driven Solution

• Contract driven
• WSDL based
• Technology agnostic
• Extensible

WSDL
Logical Contract
Bindings
Service
SOAP
Bindings
Bindings
Physical Contract
SOAP
CORBA
XML
Transport
Transports
HTTP
IIOP
JMS
27
MTOSI wsdl Multi-Transport Services

• No canonical transport - multiple bindings
  available

• Re-use existing interfaces
• Enabling Service Oriented Architecture (SOA)

• Flexibility
• Lower Integration costs
• Bindings only involve the physical contract
• They can be added and removed without affecting
  application code
• Allows you to modify transport level
  configuration data at any time

28
Why IONA for MTOSI

• Out of the box support for multiple transports
  with WSDL contracts
• Faster and cheaper development and deployment of
  MTOSI solutions
• Toolkit to easily develop MTOSI compliant
  solutions
• Leverage existing infrastructure (ie CORBA)
• Cut integration costs
• Carrier-grade Qualities of Service
• Major contributor to standard and product
  solutions
• HTTP Binding
• IONA-MTOSI toolkit

29
MTOSI Now and Next Steps
30
MTOSI Release 1 Features

• Inventory
• Includes all TMF 608 entities
• Logical model such as SNC, PTP, Topological Link
• Physical model such as Equipments
• Provides operations
• Bulk retrieval
• Updates via notification
• Alarms
• Retrieval of Active Alarms
• Alarm Reporting via notification

31
MTOSI Next Steps

• Mapping of MTNM version 3.0 and 3.5 to MTOSI XML
• Technology Enhancements
• MPLS, Ethernet, IP
• Inventory Enhancements
• Multi-Object Inventory (MOI) requests and
  notifications
• Service Management
• Service Inventory and Service Activation based
  upon SID
• Device Modeling Templates
• Standardise language for description of network
  devices
• Fault Management Enhancements
• align with fault capabilities of 3GPP and OSS/J.
• Support for additional bindings
• HTTP/S

32
Nice Catalyst

• May be hosted services where another operator
  provides servers and network
• May be single server

Access Border Gateway
SIP Call Agent
Application Server
Access Border Gateway
SIP Call Agent
Application Server
abc
Function
abc

• May be over SP Y or another SP
• Will have access network and ISP etc (model is
  fractal wrt this model)

Location Service
Location Service
Media Server
Media Server
Data
Arbitrary network probably belonging to SP (note
may use other SP services)
Internet - ISP SP X and BB SP etc
Many providers and networks network
VoIP SP network
VoIP SP network

• May have carriers carrier
• May have peer carrier

DSL Modem / Residential Gateway / CPE
User Profile
AAA
User Profile
AAA
SIP Terminal
Access SP network
DSL Modem / Residential Gateway
Access network
Core network
Core network
Access network
Edge Router (PE1) (8600)

• May have complex network

• May have complex network

DSLAM/BRAS Huawei
Edge Router (PE2)
Global Backbone SP Y network
33
Thank you! Any Questions??

• Further information can be found at
• www.tmforum.org
• For information on this specific presentation
  contact
• Francesco Caruso - fcaruso_at_research.telcordia.com
• Nigel Davis - nigeld_at_nortel.com
• Annalisa Sarasini - Annalisa.Sarasini_at_iona.com
• For information on mTOP contact
• Steve Fratini (leader) - sfratini_at_telcordia.com
• Ian Best - ibest_at_tmforum.org