mof functional overview 12 nsn

8/11/2019 MOF Functional Overview 12 NSN

1/25

Nokia Siemens Networks 1 (25)

Open EMS Suite by Nokia

Managed Object Framework

Functional OverviewVersion 1.2


2/25


2 (25) Nokia Siemens Networks

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended forthe use of Nokia Siemens Networks customers only for the purposes of the agreement underwhich the document is submitted, and no part of it may be used, reproduced, modified ortransmitted in any form or means without the prior written permission of Nokia SiemensNetworks. The documentation has been prepared to be used by professional and properlytrained personnel, and the customer assumes full responsibility when using it. Nokia SiemensNetworks welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products are given as is and allliability arising in connection with such hardware or software products shall be definedconclusively and finally in a separate agreement between Nokia Siemens Networks and thecustomer. However, Nokia Siemens Networks has made all reasonable efforts to ensure thatthe instructions contained in the document are adequate and free of material errors andomissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks,explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TOSPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,

SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESSINTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THEUSE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademarkof Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2007. All rights reserved.


3/25

Contents


Contents

1

Introduction ............................................................................................5

1.1

Support for the dynamics of todays networks and services ....................5

1.2

Configuration management......................................................................5

2 Functionality of Managed Object Framework......................................72.1 Overview ..................................................................................................72.2

Network modelling..................................................................................10

2.2.1 CM Basic adaptation ..............................................................................112.2.2 CMUI adaptation ....................................................................................132.3

Deployment of CM adaptations in MOF.................................................14

2.4

MOF Desktop tools.................................................................................15

2.4.1

Object Explorer.......................................................................................17

2.4.2

Object Editor ..........................................................................................18

2.4.3 Network View .........................................................................................18

2.5

MOF interfaces.......................................................................................212.5.1 CM Adaptation Interface.........................................................................22

2.5.2 CM South Mediation Interface................................................................222.5.3 CM access interfaces.............................................................................23

3 Technical features................................................................................253.1

Scalability and availability.......................................................................25

3.2 Security ..................................................................................................25


4/25




5/25

Introduction


1 Introduction

1.1 Support for the dynamics of todays networks and

services

Managed Object Framework (MOF) is a scalable, easily extensible, andstandards based solution for network topology and configuration data.MOF provides a complete set of interfaces for accessing, importing, andexporting managed objects and metadata.

Powerful graphical user interfaces MOF Desktop tools providecomprehensive visualisation and comfortable editing of the data storedin MOF.

MOF offers the ability to adapt to changes in the network structure andto add new network element types and versions without developing new

software. Instead, model extensions (metadata) adapt MOF to changesin the network. In this way, MOF fully supports the Open EMS Suiteinstant adaptation concept.

MOF is multi-vendor, multi-service, and multi-technology enabled. It canbe used to model, store, and edit data on all TMN layers, from elementto service models, and it can handle services from radio and fixedaccess to core technologies.

This enables you to manage topology, resources and services in linewith the quickly changing structure and contents of todays networks.

1.2 Configuration management

Management Object Framework provides the most important buildingblocks for configuration management (CM) systems and the means to


6/25



reflect the complex dependencies within configuration data of networkelements.

MOF acts as the integration point between the different FCAPS domainsof Open MES Suite: models and instance data maintained by MOF is

available also in PM (for reporting, for example), FM (alarm correlation),and your own CM applications.


7/25

Functionality of Managed Object Framework


2 Functionality of Managed ObjectFramework

2.1 Overview

Figure 1. Managed Object Framework components in Open EMS Suite

MOF is part of the Open EMS Suite Application Platform. It also providesplug-ins for Adaptation SDK (CM Basic & CM User Interface adaptation


8/25



fragments described in Chapter 2.2) and offers a set of open interfacesas described in Chapter 2.5.

Instant adaptation

MOF has been designed to adapt to new network elements withmetadata. The metadata describing various aspects of a networkelement type is called adaptation. Adaptations are processed at runtime by the Open EMS Suite software. This feature is called instantadaptation, because it enables you to develop and deploy newadaptations with minimum effort and minimum interruption in the run-time system.

Instant adaptations improve release synchronisation and quickintegration of new network elements.


9/25



Figure 2. Instant adaptation

Typical steps in creating an adaptation for a new network elementrelease and in deploying it with MOF could be as follows:

1. Create a model of the new network element release containing allrequired attributes, constraints, relationships, and so on, with yourfavourite UML-modelling tool.

2. Optionally, adjust data visualisation by modifying the configurationmanagement user interface (CMUI) file.

3. Deploy the new adaptation from the SDK to the Open EMS Suiteserver.


10/25



4. Perform a network upload or use Object Creation Wizard to createnew object instances.

5. Use the MOF Desktop tools to display and modify the storedobjects.

Support for instant adaptation in combination with the comprehensivemodelling capabilities of MOF provide Open EMS Suite customers with aversatile solution to cope with todays challenges in the networkmanagement domain.

2.2 Network modelling

In the heart of any management solution stands the model of theresources or services that have to be managed by the system.

In many cases, the object model is tightly built into managementsystems. This means that the systems only work with the model forwhich they have been designed for (3GPP, for example), and allresources within the network have to be squeezed into this fixed model whether it suits the purpose or not.

Implicit assumptions about the object model mean that the applicationsand interfaces need to be hardcoded. Consequently, later changes tothe object model are very expensive or virtually impossible, due to thehigh effort needed in order to change the implicit model.

MOF goes a different way

In order to provide customers with a highly flexible and adaptableconfiguration management and network topology infrastructure, noassumptions about the underlying object model have been made in thedesign of MOF. Instead, MOF has an explicit metamodel that describesthe concepts applicable for the creation of object models. AccordinglyMOF can support standardised object models like 3GPP or your ownexisting models.

MOF metamodel based on UML

The MOF metamodel is based on the UML class model and supports thekey techniques of object-oriented modelling, including:

(object) classes

attributes

inheritance

relationships


11/25


12/25



Figure 3. CM Basic adaptation

Adaptation SDK offers access to all modelling features by the CM Basicmetamodel. Besides the already mentioned features (attributes,

inheritance, and relationships), there are also the following.

Multiple inheritance with attribute groups

This feature allows grouping of several attributes to represent often usedpatterns: once an attribute group is defined, you can re-use it byinheritance. This feature not only saves effort when creating newadaptations, but it also helps to keep complex models well-structuredand maintainable.

A typical example for an attribute group would be an Ethernet Interfacecontaining IP-address, network mask, default gateway, and MACaddress attributes.

Constraints

CMB offers a predefined set of constraints. You can use them to definesimple constraints, for example the string length of an attribute that isused to limit the user input in GUI tools.


13/25



Extensibility with annotations

CMB offers the possibility to add annotations to adaptations. Theseannotations can be used to transfer additional information that is notcaptured by the model into applications built on top of Open EMS Suite.

You can use the annotations for example for object attributes thatrequire a special character set, and therefore a different representationin graphical user interfaces. In general, annotations make it easy to buildyour own metadata driven applications on top of MOF.

Model merging

Like in UML, model merging can be used to merge parts of modelsoriginating from different organisation units. For example, one part ofyour organisation might be responsible for topology (containment andother relationships), and another for detailed parameters. Model mergingallows you to decouple the development and deployment of both parts ofthe model while still presenting a coherent, merged model to the end-

user.

2.2.2 CMUI adaptation

The CMUI adaptation creates an object class specific configuration intoMOF Desktop tools.

You can define the following:

Icons for the object classes- CMUI supports the assignment ofdifferent icons in GIF format for an object class. Different sizes forrepresentation in different applications are supported.

Menus per object class - When certain tools are often used incombination with a certain object class, the respective menus can beassigned to the objects. You can open the menus assigned this way withright-click on the object.

Launch actions per object class- This powerful feature allows you tocreate object specific launch commands. The launch commands cancontain metadata tags that are replaced by the objects attribute values(for example the IP-address of the object), when the launch is selected.

By linking a CMUI adaptation to a base class object (for exampleManagedObject), all derived objects can be initialised with a set ofdefault menu entries and launch actions, so that it is not necessary todefine these items for each adaptation separately.


14/25



Figure 4. CMUI adaptation

2.3 Deployment of CM adaptations in MOFThe zipped CM adaptations are transferred via HTTP from Open EMSSuite SDK to the Add-on Manager and stored into the servers filesystem. The Adaptation Manager unzips the adaptation and triggers theDeployment Controller for the various adaptation fragments.

MOF uses two dedicated deployment controllers to enable easydeployment and run-time activation of CM adaptations:

CM Basic Deployment Controller- The CM Basic DeploymentController analyses the CMB file and stores adaptation data intothe database. It uses an RDB Manager to create the databaseschema for storing object instance data accordingly.

CMUI Deployment Controller - The CMUI Deployment Controllergenerates Layer XML files of the CMUI adaptation. The Layer XMLfiles are downloaded via Java Web Start by the desktop clients atstartup.


15/25



Figure 5. MOF adaptation deployment

Alternatively, adaptations can be deployed into a file system folder fromwhere the adaptation manager retrieves them.

In both deployment methods the CMB and the CMUI DeploymentControllers run the same constraint and consistency checks as in theSDK to ensure that corrupted adaptations are not entered to the system.

2.4 MOF Desktop tools

Integration of MOF Desktop tools into Desktop Framework ensures thatthe following features facilitate intuitive tool navigation and collaboration:

Bookmark support Bookmarks can be set on tools and views.You can click on the saved bookmarks instead of navigatingthrough the menus to launch a regularly used tool or network view.

Forward and backward navigation in subwindows Desktop

Framework tracks the order in which you open desktop windows.In a web browser, for example, you can navigate back and forththrough the opened windows by clicking on navigation arrows.

Drag and drop functionality supported You can use drag anddrop functionality between the Desktop Framework tools. This


16/25



saves you from several mouse-clicks when you are for examplecopying objects from one tool to another or launching the NetworkView tool with a specific view.

Automated software update Each time the Desktop Framework

is started, it checks for software versions on the Open EMS Suiteserver. If the software versions on the client PC are older than onthe server, the latest versions are uploaded via Java Web Startand are automatically deployed by the client PC.

Tooltips provided when selected by mouse Like in mostmodern graphical user interfaces, a tooltip is displayed for as longas you hold the cursor on a menu item.

Figure 6. Service sharing with tool integration in Desktop Framework


17/25



2.4.1 Object Explorer

Object Explorer displays the object hierarchy based on containmentrelationship. Starting from the root object, the hierarchy can be explored

by opening child-level branches of the underlying tree.Object Explorer allows having specific view angles to the hierarchydisplayed. You can choose to display the hierarchy model under thecorresponding physical locations (sites) or grouped by other logicalrelations (maintenance regions, for example).

Figure 7. Object Explorer

In addition to the pure tree hierarchy, the browser can display attributesof the corresponding objects. The result is a mixture of tree and tabledisplay that you can arrange freely.

Object Explorer also provides a quick search functionality that findsobjects and their attributes within the visible area when you type inattribute and object names or values.


18/25



2.4.2 Object Editor

Object Editor provides two features:

a) Object Creation Wizard

Launch the Object Creation Wizard with a right-click on a parent objectin the Object Explorer. The wizard then guides you through thenecessary steps for creating a child object to the parent. You can alsolaunch the Object Creation Wizard from the File menu. In this case theWizard creates a new root object.

b) Property Editor

Property Editor is used to modify object attribute values. The modelledconstraints in the CMB adaptation are then checked before the valuesare changed. To change the attribute values you need appropriate userrights.

2.4.3 Network View

The Network View tool enables you to gain control over the wholenetwork. It provides hierarchical and scalable views over the entiremanaged network. The graphical views allow drilling down from anetwork-wide overview to the lowest modelled elements. In the upperlevel views, you can quickly visualise the general topology of themanaged network. The detailed relationships between objects areshown when you move to a subview.

In order to maintain the required overview, Network View supportszooming and panning of views. Contained objects and the associated

text are zoomed with the views. Depending on the zoom level, objects,labels, and decorations can be hidden away.

Views can be linked to subviews that typically model a specific aspect ofa network, or to a part of it with a higher level of details.

Visualising object state information

Plug-ins from other Open EMS Suite applications can add differentdecorations to an icon or change the color of an icon in order to showthe status of objects. Status information provided by MOF:

Note existing (Coming functionality) The Network View tooloffers the possibility to store free text comments for each object

instance, much like paper notes. The existence of such commentis visualised with decorations that are attached to the object icon.

Subview existing /subview state If an object has a subviewbelow it, this is shown with a decoration. A double-click on the iconopens the respective subview.


19/25



Example: Fault Management Platform plug-ins

The Open EMS Suite Fault Management Platform provides analarm status plug-in for the Network View: view based alarm andstatus monitoring displays the alarm status of an object with

different colours. The alarm with highest severity determines thecolour. Symbols attached to the object icon give further informationon object states, such as administrative state, alarming state,operational state, or active filtering due to ongoing maintenancework.

Figure 8. Comprehensive status information provided by Network View

Launch actions and menus

You can initiate user actions by selecting the objects with right-click. Thepop-up menu opens, and you can select service actions as configured

with the CMUI adaptation. The menus and launch actions shown dependon what tools you have available.


20/25



2.4.3.1 Network View Editor

Network View Editor is a tool that allows the construction of views.These views can have both logical and geographical representation.When editing a view, you can drag and drop objects from the Object

Explorer into the view and place them freely into the view pane. It is alsopossible to draw lines between objects to represent connections or useother geometric shapes to mark logical associations. If required, you canadd background bitmaps, polygon lines, and text to complete the view.Network View Editor also supports the creation of subviews.

Figure 9. Network View Editor


21/25



2.4.3.2 View Explorer

View Explorer is a tool for visualising the view hierarchy with subviews. Itshows the views as folders, which helps to acquire a better overview onthe existing set of views.

Figure 10. Quick Search option in View Explorer

View Explorer provides also search functionality to find views accordingto different aspects, such as contained objects. You can select a view formanipulation or display different attributes of a chosen view in theProperties window.

2.5 MOF interfaces

MOF provides interfaces for easy integration into element managementsolutions.


22/25



Figure 11. MOF interfaces

2.5.1 CM Adaptation Interface

This interface comprises the previously introduced files CM Basic andCM User Interface. The interface is used whenever a new networkelement, technology, or service is introduced in MOF.

2.5.2 CM South Mediation Interface

CM South Mediation Interface is an XML interface for mass data loadingfrom object instances via southbound interfaces. It providesasynchronous data file loading from the file system, and the file format isOpen Configuration Standard (OCoS).

This interface can be used to implement CM upload (or discovery)operation: the upload component queries the network and afterwardscreates an OCoS file that reflects the current network configuration.


23/25



2.5.3 CM access interfaces

You can use CM access interfaces to access the data and metadatastored into the MOF database.

2.5.3.1 OSS Inventory API (CM Access Java API)

OSS Inventory API is the main access interface for Java basedapplications and therefore named in Open EMS Suite as CM AccessJava API. This interface implements the OSS Inventory API as specifiedby the OSS through Java Initiative.

2.5.3.2 CM Access SQL API

CM Access SQL API provides generic SQL read access to the objectinstance data stored in MOF. This interface is used by applicationsimplemented in other programming languages than Java (for example inPerl or C++). It can be used for reading object instances and itcomprises a wide range of object queries.

2.5.3.3 CM Meta Access Java API

In order to enable you to implement your own metadata drivenapplications, MOF provides read access to the metadata inserted into anOpen EMS Suite based system via CMB adaptations.

Additionally, the Java API provides information on the database mappingto clients.

The CM Meta Access Java API is closely aligned with the OSS/Jcommon specification.

2.5.3.4 MOF Business Logic Extension Point

MOF manages the life cycle of managed objects. It is able to trackexactly which objects are being created, modified, and deleted. TheMOF Business Logic Extension point allows you to hook Enterprise JavaBeans into the life cycle management and get them called, in case amanaged object is created, modified, or deleted.

The interface can be used to implement, for example, the followingfeatures on top of MOF:

Network element operations: if you want every managed objectmodification to result in immediate changes on the networkelement, you can use this interface to trigger your provisioning

logic.

Capacity limitation: if you want to limit the number of objectinstances, you can use this interface to disallow new objectcreation.


24/25



Dependent data update: if you have additional data outside ofMOF that is related to MOF data, you can use this interface to getnotified about MOF data changes and consequently update yourown data. Examples include aggregated data like How many

objects with a certain property exists? or additional data, thatshould be created/deleted also in case MOF data is created ordeleted.

Technically, this interface is realized with JPreference basedconfiguration data and RMI call-backs. By using fine-grainedconfiguration data, you can specify the situations where you want to benotified. Needless call-backs can be thus avoided, which guaranteeshigh system performance. Using RMI ensures that the user identity andtransactions context of MOF are transferred to your component, makingthe solution more robust and secure.


25/25

Technical features

3 Technical features

3.1 Scalability and availability

As MOF is a shared component for most other Open EMS Suitecomponents, scalability and availability got intensive attention whendesigning MOF.

MOF is fully J2EE-based and supports clustered J2EE configurations.Consequently, MOF can be scaled in several ways, including up-scaling(more CPUs per nodes), out-scaling (more nodes), and down-scaling(running MOF inside a single Java Virtual Machine). This also meansthat MOF supports the availability features of the J2EE applicationserver, including fail-over.

3.2 Security

MOF may contain sensitive corporate information, including networkelement passwords, service configurations and locations.

Therefore, access to MOF data requires proper authentication andauthorisation. Authentication is handled via J2EE authentication, makingit impossible for persons without credentials to execute MOF businesslogic. Once you have been authenticated, you can use authorisation torestrict MOF data modifications by other people.

mof functional overview 12 nsn

Documents