3bk 10204 0672 muse m0 external interfaces sfd

7/30/2019 3bk 10204 0672 MUSE M0 External Interfaces SFD

1/13

SiteVELIZY

EVOLIUM SAS

OriginatorsMUSE-Spec Task Force

MUSEExternal Interfaces

System : MUSE

Sub-system :

Document Category : SYSTEM FEATURE DESCRIPTION

ABSTRACT

This SFD describes the "External Interfaces of MUSE.

Approvals

NameApp.

David RinchetTPL

Andre MechalyPM

Yannick BeucherDPM

Name

App.

REVIEWEd1. 01 Proposal 03 01/10/2005

HISTORYEd. 01 Proposal 01 12/17/2004 First proposalEd. 01 Proposal 02 12/24/2004 After internal review.Ed. 01 Proposal 03 01/05/2005 After internal review.Ed. 01 Released 01/20/2005 After review.

MUSE Analysis Application External Interfaces chapter

ED 01 Released

EVOLIUM 3BK 10204 0672 DSZZA 1/13


2/13

SYSTEM FEATURE DESCRIPTION

TABLE OF CONTENTS

1 INTRODUCTION................................................................................................................................ 4

2 GENERAL OVERVIEW..................................................................................................................... 52.1 External Interfaces.................................................................................................................... 5

2.1.1 Requirements...................................................................................................................... 6

3 SERVICES DESCRIPTION...............................................................................................................73.1 External Interfaces.................................................................................................................... 7

3.1.1 SYS_REQ-MUSE_ITF-001: UMTS R4 PM Files................................................................73.1.2 SYS_REQ-MUSE_ITF-002: Metadata................................................................................ 73.1.3 SYS_REQ-MUSE_ITF-003: EQL interface......................................................................... 83.1.4 SYS_REQ-MUSE_ITF-004: Report Template Import/Export.............................................93.1.5 SYS_REQ-MUSE_ITF-004: Customer Indicator definition import/export...........................93.1.6 SYS_REQ-MUSE_ITF-005: RNP Planification Parameters...............................................93.1.7 SYS_REQ-MUSE_ITF-006: Fault management interface................................................103.1.8 SYS_REQ-MUSE_ITF-007: Supervision interface...........................................................103.1.9 SYS_REQ-MUSE_ITF-008: MUSE Platform Interface.....................................................113.1.10 SYS_REQ-MUSE_ITF-009: Topology change interface.................................................113.1.11 SYS_REQ-MUSE_ITF-010: GSM B9 PM files................................................................113.1.12 SYS_REQ-MUSE_ITF-011: Customer topology interface..............................................113.1.13 SYS_REQ-MUSE_ITF-012: Free fields.......................................................................... 123.1.14 SYS_REQ-MUSE_ITF-013: WZ, CZ, OZ definition import/export.................................123.1.15 SYS_REQ-MUSE_ITF-014: 3GPP PM Interface Import.................................................12

4 GLOSSARY..................................................................................................................................... 13


ED 01 Released



3/13

INTERNAL REFERENCED DOCUMENTS

Not applicable.

REFERENCED DOCUMENTSAlcatel references[1] 3DC 25339 0045 DRZZA MFD Multi-Standard OMC-R.

Alcatel ref. List the MFD(s) used as an input for the present SFD.List the RFD(s) used as an input for the present SFD

[2] Thales/RNO spec. E311188Ed2

Generic RNP Cell Design Interface

[3] 3BK 11274 0002 DSZZAEd1

MUSE Sub-system architecture definition (SSAD)

[4] 3BK 11274 0002 DSZZAEd1

MUSE M0 EIS QoS Metadata definition

RELATED DOCUMENTS[5] 3BK 10204 0659 DSZZA SFD MUSE Analysis Application Introduction & General

Principles Chapter[6] 3BK 10204 0660 DSZZA SFD MUSE Analysis Application QoS Chapter[7] 3BK 10204 0661 DSZZA SFD MUSE Analysis Application Topology Chapter[8] 3BK 10204 0662 DSZZA SFD MUSE Analysis Application Object Zone Chapter[9] 3BK 10204 0663 DSZZA SFD MUSE Analysis Application Radio Parameters

Chapter[10] 3BK 10204 0664 DSZZA SFD MUSE Analysis Application Reports Chapter[11] 3BK 10204 0665 DSZZA SFD MUSE Analysis Application Diagnosis & Rules

Chapter[12] 3BK 10204 0666 DSZZA SFD MUSE Analysis Application Cartography Chapter[13] 3BK 10204 0667 DSZZA SFD MUSE Analysis Application Thematic Layers Chapter

[14] 3BK 10204 0668 DSZZA SFD MUSE Analysis Application Events Chapter[15] 3BK 10204 0669 DSZZA SFD MUSE Analysis Application Tuning Chapter[16] 3BK 10204 0670 DSZZA SFD MUSE Analysis Application LASER Chapter[17] 3BK 10204 0671 DSZZA SFD MUSE Analysis Application Administration Chapter[18] 3BK 10204 0672 DSZZA SFD MUSE Analysis Application External Interfaces

Chapter[19] 3BK 10204 0673 DSZZA SFD MUSE Migration

PREFACEThis document gathers all external interfaces of MUSE.

OPEN POINTS / RESTRICTIONS


ED 01 Released



4/13

1 INTRODUCTION

See MUSE Analysis Application Introduction & General Principles Chapter (document [5]).


ED 01 Released



5/13

2 GENERAL OVERVIEW

2.1 External Interfaces

The following figure gives an overview of the interfaces in the scope M0 and M1:

Oracle Data Warehouse

AS IM

EQL

MUSE Analysis Application Tier (MAAT)

ExternalFTP server

Import Export

OMC

MUSE

3GPP IM

Metadata(XML)

UMTS R4GSM B9

W2PM files

AS Interface(CMIP)

RNP Planif.Parameters

MUSE PlatformInterface

(FTP ) Free FieldsAndCustomerTopologydefinition

Topologychangeinterface

Figure 1: External Interfaces Overview

The following table gives the list of external interfaces with their scope in Muse program. Only theinterfaces in the scope M0 and M1 will be described in this edition of the document.

In the table below, the Interface Type value can contain values defined as follows:

South, North: it is a permanent interface. South means that MUSE gets information from the

OMCs. North means the MUSE provides information to external applications.

Import, Export: it is non a permanent.

Scop

e Name Domain

Interface

TypeM0 UMTS R4 PM Files QoS Import

M0 Metadata QoS Import

M0 EQL (including excel and csv access) X domain Export

M0 Reporttemplate import /export Report Import/Export

M0 Customer Indicator definition import /export Report Import/Export

M1 RNP planification Parameters Parameters Import


ED 01 Released



6/13

M1 Supervision interface Supervision South

M1 Fault management interface Supervision South

M1 MUSE Platform Interface (including Navigationconfiguration, Citrix, IconBox, OMC configurationdata)

Platform Import

M1 Topology Change Interface Topology Import

M1 GSM B9 PM Files QoS Import

M1 Customer Topology Interface Topology Import

M1 Free Fields Topology Import

M1 WZ, CZ, OZ definition import/export OZ Import/Export

M1 Open 3GPP PM Interface QoS Import

M2+ 3GPP Entry Point IRP and AlarmIRP (for Muse-alarm only) Platform North

M2+ Cartography Cartography Import/Export

M2+ Thematic Layers THL Import/Export

M2+ LASER (user logs are not the complete one tobe refined)

Log/Hist Alarms Import

M2+ ACO Interface Supervision South

M2+ GSM Operational Radio Parameters Operational RadioParameters Import

M2+ UMTS Operational Radio Parameters Operational RadioParameters

Import

M2+ Experience matrix generation Export

M2+ System Capacity Planning Export

2.1.1 Requirements

Marketing Feature Requirement Title Priority 1820 Support of Entry

Point IRP from 3GPP

Support of Entry Point

IRP from 3GPP

P2

1830 Real-time alarminterface based on the3GPP Corba interface

Real-time alarminterface based on the3GPP Corba interface

P2

1840 Configurationdata interface, basedon 3GPP specification

Configuration datainterface, based on3GPP specification

P2

1850 Performance datainterface, based on3GPP specification

Performance datainterface, based on3GPP specification

P2

1860 Inventory datainterface, based on

3GPP specification

Inventory datainterface, based on

3GPP specification

P2


ED 01 Released



7/13

1890 Import of RNP fullprojects

SYS_REQ-MUSE_ITF-005 Import of RNP fullprojects

P1

1900 Import of RNPdelta projects

SYS_REQ-MUSE_ITF-005 Import of RNP deltaprojects

P2

1910 Export Cell designto Radio NetworkPlanning Tool

SYS_REQ-MUSE_ITF-005 Export Cell design toRadio Network PlanningTool

P2

1920 Alarm loginterface

LASER interfaces P2

1930 Export tostandard officeapplications

SYS_REQ-MUSE_ITF-003 Export to standardoffice applications

P0

5320 RNP batchscheduling

SYS_REQ-MUSE_ITF-005 RNP batch scheduling P2

5530Experience Matrixgeneration for networkfrequency planning

Experience Matrixgeneration

P2

5540 System CapacityPlannning

System Capacity Planning

P2

3 SERVICES DESCRIPTION

3.1 External Interfaces

3.1.1 SYS_REQ-MUSE_ITF-001: UMTS R4 PM Files

Performance data of UMTS R4 may be imported in MUSE.

3.1.2 SYS_REQ-MUSE_ITF-002: Metadata

It is possible to import the following metadata definitions:

3.1.2.1 System metadata

Aggregation methods and Normalization methods.

3.1.2.2 Telecom metadata

Supported standards and Network objects for UMTS, GSM and W2.

QoS Counters definition data.

QoS Indicators definition data.

QoS Families definition data.

QoS Threshold definition data.

For more information, please refer to the MUSE SSAD document [3] and the Metadata EIS document[4].


ED 01 Released



8/13

3.1.3 SYS_REQ-MUSE_ITF-003: EQL interface

A part of the MAAT north API is public (visible by the customer through various interfaces). It is calledEQL (Extensible Query Layer).

EQL is in fact composed of two different interfaces:

HTTP based interfaces (described hereafter in the web interfaces section)

o

Only a reduced set of services will be available in first releases,o In later releases, several MAAT services may be published.

(M2+ only) A JDBC access to the data warehouse (using a particular user) which allows to

access in read-only mode a subset of the objects (or only views).

EQL interface will be documented in a dedicated MUSE Interface specification document.

3.1.3.1 Web service interface

This component fulfills the following requirements:

A lot of people know and like to manipulate and present data using Excel, Access and other

Office applications.

People want to send MUSE results via Email attachment; this requires the support of well-

known file formats (PDF or Office again). Some people need to have access to MUSE without having the MUSE analysis desktop

installed on their PC.

Integrators need to access to MUSE data in order to build additional applications on top of

MUSE.

The web service interface answers to theses needs. It is based on the HTTP/HTTPS protocol and onusing URI to pass parameters, just like every web server on the Internet is doing.

For example, exposing reports services is as simple as making a script accessible on a Web servervia the following URI: http:///report?name =MyReport&date=today&view=XML

Following HTTP/HTTPS messages are used:

GET to retrieve information, GET never modifies the state of the data warehouse.

DELETE is used to remove definition (reports, object zone).

PUT to create definition (from report, object zone).

POST to create or update a definition (from a report, object zone) .

By default both HTTP and HTTPS are allowed but HTTP access can be blocked in a high securitycontext.

Authentication is managed via the HTTP basic authentication mechanism (user / password), thesame login as for the rest of the application is valid.

FAD are managed through SEC by underlying MAAT components.

The following output formats are supported (via the view parameter of the URI):

XML, to be used by integrators.

Excel (the XML format of Excel 2003), to be used by end users.

CSV, to be used by integrators and end users (import for Access).

Two CSV standards are supported:

The international Coma Separated Value standard,

The Semi Column Separated Value standard (for France).

The operator can use many different tools to access the information:

Web browsers such as Mozilla and Internet Explorer.


ED 01 Released



9/13

Many web enabled tools, for example Access and Excel can directly access information via

HTTP.

Almost all modern development languages support directly HTTP (VB, .NET, C#, java,

python, perl).

The operator performs an operation, for example display indicators in the spreadsheet. This operationexecutes a request to get the data.

The operator requests to display the URL corresponding to this request for the format of its choice(CSV, XML, Excel).

The Excel Web Query Files (.IQY files) are also supported. When double clicking on a file of thistype, it creates an Excel spreadsheet that performs the query written in the .IQY file. It can be used tobuild dynamic Excel spreadsheets that are updated with new data.

Alternatively, the push mode is also supported. The operator creates a scheduled task. This taskcreates the file with the XML/Excel/CSV format and puts it to an external FTP/SFTP server.

For more information, please refer to the MUSE SSAD document [3].

3.1.4 SYS_REQ-MUSE_ITF-004: Report Template Import/Export

Muse manages report templates (i.e. report definitions) and updates the definition table when anoperator modifies a template.

It is possible to import and export the definition of a report.

3.1.5 SYS_REQ-MUSE_ITF-004: Customer Indicator definition import/export

MUSE allows to import non-system indicators defined by the customer operator. It is also possible toexport indicators definition to be re-used (imported) in another MUSE session.

3.1.6 SYS_REQ-MUSE_ITF-005: RNP Planification Parameters

It is possible to import (or export) planification parameters from (or toward) the RNP tool.

MUSE supports the generic RNP interface (interface to inter-operate with some other Radio Planningtools) and the A955 RNP interface.

In the following figures, MUSE will import only the CEL/ADJ/FRQ files.


ED 01 Released



10/13

POLO

CEL

CEL(RNO)

FRQ

ADJ

CEL files

merger

INM

Best Server

Cell Contour

detection

.vcc

Cell

Design

Import

Best Server

Cell Contour

import

Background

maps

import

.mif

MUSE

GenericRNP interface

BestServer

A955

RNP

ADJ

FRQ

CEL

INM

.sup

.ssv

.mif.mif

For more information, please refer to the specification documentation of RNO/RNP interface in [2].

3.1.7 SYS_REQ-MUSE_ITF-006: Fault management interface

Fault Management interface relies on the ALMAP AS interface component. MUSE AS will be directlycollecting alarms from OMCs by connecting to their AS IMs.

In a second step (M2+), alarm collection could be made using the 3GPP Alarm IRP. The SNW IMcomponent is responsible of converting the 3GPP alarms into ALMAP AS X733 Alarms and

forwarding actions made in MUSE AS USM toward OMCs, or in the opposite way, forwarding theactions made in OMC AS USM toward MUSE AS (acknowledgment, alarm clear, alarm annotation).

3.1.8 SYS_REQ-MUSE_ITF-007: Supervision interface

The data are retrieved through a 3GPP interface provided by each OMC:

Network topology and states relevant for supervision,

Notification of state change, creation and deletion of NEs.

The required 3GPP IRPs (integration Reference Point) implementation at the OMC level are:

Basic CM IRP for information retrieval.

Kernel CM IRP for sending object creation/deletion and attribute value changes notifications.


ED 01 Released



11/13

Notification IRP for subscription/unsubscription to notifications.

Entry Point IRP which is the unique entry point to retrieve all IRPs.

Communication surveillance IRP to monitor IRPAgent status.

State management IRP to specify the semantics of the network resource state.

Furthermore, depending on the technology of the OMCs, GERAN and UTRAN 3GPP NRM modelsare supported to enable Muse SUP USM to retrieve the networks objects and their attributes.

The complete 3GPP interfaces required by MUSE Supervision will be documented in dedicatedMUSE Interface specification documents (idl files containing the IRPs and NRMs models with vendorspecifics).

3.1.9 SYS_REQ-MUSE_ITF-008: MUSE Platform Interface

The MUSE Platform Interface will be fully described in a dedicated MUSE Portal IntegrationSpecification document.

3.1.9.1 Navigation configuration

MUSE navigation configuration relies on the configuration of each declared OMCs. So MUSEsupports the ALMAP NAV component configuration files (interface specified by ALMAP).

It also relies on the Citrix product interfaces (interface specified by Citrix products).

3.1.9.2 IconBox configuration

MUSE IconBox configuration is made combining XML files, imported from OMCs, that describe theOMCs applications in the context of the IconBox (application name, icon, ..).

3.1.10 SYS_REQ-MUSE_ITF-009: Topology change interface

This interface allows MUSE to get LAC/CI changes.

These interfaces will be specified by the OMCs.

3.1.11 SYS_REQ-MUSE_ITF-010: GSM B9 PM files

MUSE may import all files handled by NPA (as described in A985-NPA B9 functional specifications)excepted PM created by LASER:

OMC-BSS HW/SW files format specification,

MFS/OMC-R PM file interface specification,

Topology files (as described in NPA functional specifications)

These interfaces are the same as the interfaces used by NPA B9

3.1.12 SYS_REQ-MUSE_ITF-011: Customer topology interface

This interface allows MUSE to import the definition of network objects and relation links, which arespecific for each customer.

This interface will be documented in a dedicated MUSE Interface specification document.


ED 01 Released



12/13

3.1.13 SYS_REQ-MUSE_ITF-012: Free fields

This interface allows MUSE to create new free fields and import the definition of free fields. It isbackward compatible with RNO file format (CSV).

Free fields interface will be documented in a dedicated MUSE Interface specification document.

3.1.14 SYS_REQ-MUSE_ITF-013: WZ, CZ, OZ definition import/export

MUSE allows to export and import Working Zone and Object Zone objects definition (XML files). TheXML format is not public.

3.1.15 SYS_REQ-MUSE_ITF-014: 3GPP PM Interface Import

MUSE allows to import the counters defined in the 3GPP PM Interface.

Vendor specificity are not loaded (but may be present in the PM file).

MUSE will deliver documentation to be able to extend the import model with additional vendorspecific counters.


ED 01 Released



13/13

4 GLOSSARY

See MUSE Analysis Application Introduction & General Principles Chapter (document [5]).

END OF DOCUMENT


ED 01 Released


3bk 10204 0672 muse m0 external interfaces sfd

Documents