| Release 2.1 of the MTOSI product is a minor release. It means that it does not contain any new features. There is one exception however: MTOSI 2.1 introduces a new supporting document documenting how to use MTOSI Service Management activation interfaces for the provisioning of broadband Ethernet services.
The modifications introduced in this release all relate to bug fixes at different levels: from simple editorial modifications to more important changes in the information model or in the WSDL or XML Interface specification.
Those different modifications have had an impact on many files from the BA, the IA and the IIS. Also several Supporting Documents have been updated to reflect the changes.
Complementary to this release, and based on MTOSI (XML solution), the technical report TR164 (Rfx_Guide_for_Transport_Networks_Management.doc) was published in November 2010 as a supporting document to provide some reusable RFx material concerning the management of transport networks intended for reuse by service providers. This TR 164 is published independently from the MTOSI release.
The MTOSI artifacts are structured into self-contained (though not independent) units called Document Delivery Packages (DDPs).
There are three kinds of DDPs: - the FrameWork DDP (FMW) – this DDP contains the generic artifacts that are applicable to all the other DDPs.
- Data Model DDP (DM-DDP) – a DDP that concerns a data model (entities, data structures, attributes, state, but no operations)
- Operation Model DDP (OM-DDP) – a DDP that concerns a computational model (operations, notifications, transactions) for a given functional area (such as resource inventory management)
The unified deliverables structure for each DDP is as follows: - Business Agreements (BAs): a business view specification
- Information Agreements (IAs): a system view specification
- Interface Implementation Specifications (ISSs): implementation and deployment view specification for XML (WSDL, XSD, bindings…)
- Supporting Documentation: normative and informative supporting documents, MTOSI 2.1 Release Notes
For further information on the TM Forum Integration Program (TIP) team click here
Declaration of Patent Interest Form If you would like help on this material or to join current discussions please visit the TM Forum Integration Program (TIP) Community Area Return to the TM Forum Integration Program (TIP) Home page | Downloads | Type |  | General - MTOSI Release 2.1 Release Notes (RN306)
The Release Notes detail the additions and changes made in this particular release since the last release. In addition it identifies the complete list of documents and associated version numbers which are contained in the release. | 
966.71 kb | | | General - MTOSI Release 2.1 Download instructions (Readme)
A Readme text file which describes how to download and un-package the various zip files. | 
2.31 kb | | | General - MTOSI Release 2.1 Implementation Statement
The purpose of this document is to provide a map of all mTOP DDPs with their content (XML IIS inclined) as delivered in MTOSI R2.1. | 
654.85 kb | | | General - Framework (FMW)
This DDP covers all the generic mechanisms commonly used by all the MTOSI interfaces concerning both the interface communication mechanisms and the general artifacts .
The following items are covered:
* Common information
* Resource naming
* Functional modeling
* Resources data retrieval mechanisms (filtering and attribute matching)
* Notification mechanisms
* Exceptions | 
16303.13 kb | | | Resource Management & Operations related - DM-DDPS - NetworkResourceBasic (NRB)
This DDP covers the general aspects of the network resources, in terms of the entities and other kind of information (e.g. state) which are common to all the interfaces related to network resources. |
2928.81 kb | | | Resource Management & Operations related - DM-DDPS - NetworkResourceFulfilment (NRF)
This DDP addresses the Data Model (DM) aspects of resource fulfillment and as such it defines all resource related managed entities visible across the Interface that are used in support of resource fulfillment.
The following items are covered:
* -Entities:
OS, ME, TP, PTP, Edge TP, CTP, FTP, GTP,
TP Pool, CPTP, FD Edge CPTP, Flow Point,
TL, MLSN, MLSN Type, SNC, Bundled SNC,
XC, Route, Connection State,
Matrix Flow Domain, FD, FDDr, MFDFr, FDFrRoute,
Equipment, Equipment Holder,
Transmission Descriptor, Traffic Conditioning Profiles
* Relevant notifications |
6252.34 kb | | | Resource Management & Operations related - DM-DDPs - NetworkResourceAssurance (NRA)
This DDP addresses the Data Model (DM) aspects of resource assurance and as such it defines all resource related managed entities visible across the Interface that are used in support of resource assurance.
The following items are covered:
* Alarm Severity Assignment Profile
* Performance Monitoring Point
* Protection
* Threshol Crossing Alert
* Relevant notifications. |
3371.76 kb | | | Resource Management & Operations related - DM-DDPs - ManageResourceInventory (MRI)
This capability is supported by means of the interface that both allows an OS to retrieve all or part of the inventory known to another OS, and also allows an OS to send inventory update notifications to a set of interested OSs. |
3878.73 kb | | | Resource Management & Operations related - OM-DDPS - Resource Provisioning (RP)
This capability allows for creating, modifying and deleting network resource entities handling control of connections, flow domains (for connectionless technologies), software, termination points, transmission descriptors, topological links, the provisioning of equipment and the management of traffic conditioning profiles and flow domain fragments. |
5532.22 kb | | | Resource Management & Operations related - OM-DDPS - ResourceTroubleManagement (RTM)
This set of capabilities covers resource fault management, protection management and maintenance and diagnostics. |
3359.13 kb | | | Resource Management & Operations related - OM-DDPS - ResourcePerformanceManagement (RPM)
This capability covers resource performance monitoring and control:
* Monitor Performance Management
o PM Retrieval – this includes the retrieval of both current and historical PM data
o Threshold Crossing Alert (TCA) Notifications
* Control Performance Management
o PM Control – this includes, for example, the enabling and disabling of PM collection
o TCA Control – this includes, for example, the enabling and disabling of TCA generation |
3029.86 kb | | | Service Management and Operations related - DM-DDPS - ServiceBasic (SB)
This DDP presents the Service Management technology neutral data model. It initiates from the SID service management information model with several extensions and adaptations introduced to fit the business needs for service activation and inventory.
It defines the static and structural requirements of the managed objects that are visible across the Service Activation Interface(s) and the Service Component Activation Interface, and the Service Inventory interface.
The following items are covered:
* State Attributes
* Attributes common to all SM Objects
* CFS, RFS, SAP, SAPSpecification, Service Catalog,
Service Definition, Service Template,
Service Order, Service Order Item,
ServiceSpecCharacteristic, ServiceCharacteristicValue. |
8504.52 kb | | | Service Management and Operations related - OM-DDPS - ServiceActivation (SA)
This capability entails the provisioning, activation and subsequent deactivation and release of services. There are currently to two interfaces defined in this area, i.e.
* Service Activation Interface (SAI) – an activation interface between an OS support the Customer Relationship Management (CRM) capability and another OS supporting the Service Configuration and Activation (SC&A) capability.
* Service Component Activation Interface (SCA) an activation interface between two OSs supporting the SC&A capability. |
5235.32 kb | | | Service Management and Operations related - OM-DDPS - ManageServiceInventory (MSI)
This capability entails the retrieval of Service Inventory related information. The interface supports only bulk inventory retrieval (retrieving selected information in a single operation) where a filter mechanism can be used to drive the information of interest. This filter uses a white page or a yellow page style (filtering by name or properties). |
481.83 kb | | |