Bridging The Gap - CBE Extension for MTNM

1. Bridging The Gap - CBE Extension for MTNM …Tying up OSS/J and Layer 2 Technologies.

2. Entity Specification Entity CBE Association JVT XVT Service Activation Inventory Management QoS The Gap NMS NML MTNM: TMF Standard Interface EML EMS B EMS A OSS/J APIs & MTNM …

3. CBE Essentials • CBE means Core Business Entities • CBE defines a CORE information model • CORE Information Model of shareable Data Transfer Objects in CBE aligned with SID from which the Vendor Specific Information Model must derive. • CBE defines interfaces that are reusable across multiple OSS components (Activation, Inventory, TroubleTicket, QoS, etc…) • Common Managed Entities: • Service, Resource, Product, Alarms • Common Types • Addresses, TimePeriods etc..

4. CBE Core Model • The CBE Core Model is composed of: • Entity • Entities are value type objects representing inventory concepts such as “Product”, “Service” and “Resource”. • Entity Specification • Entity Specifications are value type objects representing specifications of CBE entities. • Association • Associations are value type objects representing CBE associations, e.g., “ResourceSupportsServiceAssocValue”.

5. So where do I find the CBE ? • javax.oss.cbe • The CBE package defines a set of interfaces that represents the upper layers of a generic information model within the OSS domain.  • The CBE package defines a set of shareable Data Transfer Objects, via interfaces • Implementations of CBE aware APIs provide the implementation; Java™ and J2EE™ do the rest …

6. MTNM Essentials • MTNM - Multi Technology Network Management. • TMF Working Group. • The Goal of MTNM is: • To provide standard, common interface between Element and Network Management Layers. • This interface is provided for ATM, SONET/SDH, Frame Relay, DSL, Ethernet etc (i.e. Layer 2 technologies) • Management Scope • MTNM model is focused on Service Fulfillment and Assurance.

7. Operations Operations Support & Readiness Fulfillment Billing Assurance Customer Interface Management Customer Relationship Management Selling Customer QoS/ SLA Management Billing & Collections Management Problem Handling Marketing Fulfillment Response Order Handling CRM Support & Readiness Retention & Loyalty Service Configuration & Activation Service Quality Management Service Problem Management SM&O Support & Readiness Service Management & Operations Service & Specific Instance Rating Service Problem Management SM&O Support & Readiness Service Configuration & Activation Service Quality Management Resource PerformanceMgmt Resource Trouble Mgmt RM&O Support & Readiness Resource Provisioning Resource Management & Operations Resource Performance Mgmt Resource Trouble Mgmt Resource Data Collection & Processing RM&O Support & Readiness Resource Provisioning Resource Data Collection & Processing Supplier/Partner Relationship Management S/P Settlements & Billing Management S/P Problem Reporting & Management S/P Purchase Order Management S/P Performance Management S/PRM Support & Readiness S/P Buying Retention & Loyalty MTNM Scope – eTOM

8. MTNM Information Model • The MTNM Model is composed of: • Objects that are visible across the interface and the operations that may be performed on these objects. • These objects have a common set of attributes. • A Root Class namely, “CommonResourceInfo” that contains: • A common set of attributes and • A common set of operations permissible on these objects.

9. Entity Specification Entity CBE Association CommonResourceInfo Termination Point CBE Extension for MTNM SubNetworkConnection JVT XVT Service Activation Inventory Management QoS ATM, SONET/SDH, FR, WDM, etc … (Layer 2 Technology) Bridging The Gap …

10. CBE-MTNM Extension …

11. CBE-MTNM Extension … • Extension of CBE also contains some Helper Classes. • These classes deal with Common set of Parameters or constants across MTNM classes. • Examples of helper classes are Layered Parameters, Directionality, Communication State etc. • Helper classes are not inheriting CommonResourceInfo interface. • They have set-get methods for each defined parameter in class.

12. CBE and the OSS/J APIs OSS/J Core Business Entities • OSS/J • Core SID/CBE Entities OSS/J – CBE Extensions for MTNM Vendor and Technology Information Model • Vendor or Technology • Specific • Information • Model is an Extension • of the Core SID/CBE Entities • Functional Partition of • OSS Business Logic • into APIs • And Realization • Of the Vendor or • Technolgy Specific • Information Model Customer Management API Inventory API Service Activation API Other OSS/J API

13. Functionality … we got it covered • Extension of CBE to incorporate MTNM information model • Realization of MTNM information model using OSS/J APIs. • Thereby bridging the gap between OSS/J APIs and Technology.

14. Benefits … • Integration efforts are reduced further as the gap between OSS/J APIs and specific Technology is bridged. • Leveraging work done by CBE, OSS/J APIs and MTNM that adhere to TMF NGOSS standard.

15. SID Provides the Optimal Solution • TMF SID provides rich set of Resource Model. • OSS/J CBE has well defined “Resource” package which uses TMF SID’s Resource Model. • MTNM entities could be logically mapped to SID Model.

16. Why use the SID ? • Rich information models take a great deal of time and effort to develop • OSS through Java is an implementation body, not a modeling forum • SID is a key aspect of NGOSS • Adoption is the key to success • OSS through Java is working to make NGOSS real • OSS/J Common Business Entities map the SID analysis (GB922) and design (GB926) models to Java data models

17. Roadmap … • OSS/J CBE Extension for MTNM • OSS/J – MTNM realization kit for Service Activation and Inventory Management APIs. • TMF Catalyst to demonstrate interoperability of OSS/J and MTNM. • Catalyst to demonstrate “Zero Touch” Service Provisioning involving L2 networking gear • Catalyst to involve: • Sun Microsystems as a Hardware/Platform vendor. • Metasolv as a Product Vendor • MBT as an experienced Telecommunication Products/Services SI • Equipment Vendor - ? • Service Provider / Telco - ?

18. Roadmap … Q1 05 Q3 05 Q4 05 Q2 06 Q2 05 OSS/J CBE Extensions on Java.net Realization Kit- Phase 1 Realization Kit- Phase 2 • OSS/J MTNM realization Kit • Service Activation APIs to be used for the second phase of realization kit. • CBE Extensions • OSS/J CBE APIs extended to incorporate MTNM data model. • CBE-MTNM Extensions available on java.net • OSS/J MTNM realization Kit • Inventory ManagementAPIs to be used for the first phase of realization kit.

19. JCP & Open Source … • OSS/J Common and CBE APIs are “Standards” • These “Standards” are designed to be “Extensible” • Extension Mechanism are“Standardized”. • All these are covered under an umbrella of JCP. • Extensions are not covered under an umbrella of JCP. • Extensions can implement domain specific standards or proprietary models. • E.g. TMF MTNM • These Extensions are illustrative work under open source licensing

20. Takeaway Message … The ultimate goal is: “To strengthen the cooperation with TMF standards, and to promote their adoption”.

21. OSS Through JavaTM Initiative “A new breed of OSS solutionspowered by Java Technology”