09661MAAAe11.pdf

9153 OMC-R Configuration Import/Export interface

ED 11 RELEASED

9661m11re.doc 17/03/2010

3BK 09661 MAAA PBZZA 1/1

All rights reserved. P

assing on and copying of this

document, use and communication of its contents

not permitted without w

ritten authorization from

Alcatel.

9153 OMC-R Configuration Import/Export Interface

(Release B11 MR1ed2 onwards)


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

SYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS

1. INTRODUCTION...............................................................................................6

1.1 Scope of the document .........................................................................6

1.2 Overview of the ACIE interface.............................................................6 1.2.1 Presentation ..................................................................................6 1.2.2 The supported services .................................................................7

1.3 Conventions and notations.................................................................10

2. THE FILES CONCERNED BY THE ACIE INTERFACE.................................12

2.1 The 9153 OMC-R Configuration File Repository (ACFR)..................12

2.2 The 9153 OMC-R External Interfaces General repository (AEIGR)..14

2.3 The different types of ACIE files.........................................................15

2.4 Formats of the ACIE files ....................................................................15

2.5 Names of the ACIE files.......................................................................16

2.6 Structure of the ACIE files ..................................................................16 2.6.1 General description .....................................................................16 2.6.2 The header of an ACIE MOC file.................................................17 2.6.3 The sub-header of an ACIE MOC file..........................................18 2.6.4 The body of an ACIE MOC file ....................................................19

2.6.4.1 The different types of lines contained in the body .........................................19 2.6.4.2 Structure of MOI-related lines ........................................................................19 2.6.4.3 Representation of values in MOI-related lines ...............................................20

3. CONCERNED 9153 OMC-R MOCS ...............................................................23

3.1 Concerned Network Level MOCs .......................................................23 3.1.1 Description...................................................................................23 3.1.2 Corresponding Naming Tree .......................................................24 3.1.3 Corresponding Network Level Id types........................................25

3.1.3.1 Description......................................................................................................25 3.1.3.2 Corresponding ASN1 type definitions............................................................27

3.2 Concerned BSC-NE Level MOCs........................................................28 3.2.1 Description...................................................................................28 3.2.2 Corresponding Naming Tree .......................................................31 3.2.3 Corresponding Network Level Id types........................................32


3.3 Concerned MFS-NE Level MOCs........................................................32 3.3.1 Description...................................................................................32 3.3.2 Corresponding Naming Tree .......................................................34 3.3.3 Corresponding Network Level Id types........................................34



ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

4. IMPORT/EXPORT MECHANISMS.................................................................36

4.1 Import mechanism...............................................................................36

4.2 Export mechanism...............................................................................48 4.2.1 General export mechanism .........................................................48

4.2.1.1 Unitary export session ....................................................................................48 4.2.1.2 File Transfer Achieved function.....................................................................51

4.2.2 Peculiarities for an export triggered by an 9153 OMC-R operator52 4.2.3 Peculiarities for export sessions triggered by scripts ...................53

4.2.3.1 Introduction.....................................................................................................53 4.2.3.2 run_UnitaryExportSession.pl..........................................................................53 4.2.3.3 run_FileTransferAchieved.pl..........................................................................54

4.2.4 Peculiarities for exports that are automatically triggered .............55 4.2.5 Peculiarities for an export triggered by a NMC ............................55

5. THE ACIE FILTERING FACILITY...................................................................59

5.1 INTRODUCTION ...................................................................................59

5.2 The ACIE Filter files.............................................................................59 5.2.1 Names of the ACIE Filter files .....................................................59 5.2.2 Structure of the ACIE Filter files ..................................................59

5.3 The ACIE post-processing (APP) files ...............................................60 5.3.1 Names of the APP files................................................................60

5.3.1.1 Names of the unitary APP files.......................................................................60 5.3.1.2 Names of the global APP files ........................................................................61

5.3.2 Structure of the APP files ............................................................61 5.3.2.1 Structure of the unitary APP files ...................................................................61 5.3.2.2 Structure of the global APP files ....................................................................61

5.4 The ACIE filtering mechanism (apply_ACIEFilter.pl) ........................62

6. ACRONYMS ...................................................................................................66 11 100317 Update O&M System TD/MRC/OMD Spec 04 091023 Update O&M System TD/MRC/OMD Spec 03 090330 Update O&M System TD/MRC/OMD Spec 02 080229 Update O&M System TD/MRC/OMD Spec 01 080215 First issue O&M System TD/MRC/OMD Spec ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

LIST OF FIGURES AND TABLES

Figure 1: The 9153 OMC-R Configuration Import/Export (ACIE) Interface ........................... 7 Figure 2: The different Levels for the 9153 OMC-R configuration data ................................. 8 Figure 3: Organisation of the ACFR for equal to c............................................. 14 Figure 4: Naming Tree for the concerned Network Level MOCs......................................... 25 Figure 5: Naming Tree for the concerned BSC-NE Level MOCs ........................................ 31 Figure 6: Naming Tree for the concerned MFS-NE Level MOCs ........................................ 34 Table 1: Set of characters allowed in productions, names and labels ................................. 11 Table 2: Character translation rule...................................................................................... 11 Table 3: Representation of values in ACIE MOC files......................................................... 22 Table 4: Description of the concerned Network Level MOCs.............................................. 24 Table 5: Network Level Id types for the Network Level MOCs ............................................ 27 Table 6: Description of the concerned BSC-NE Level MOCs.............................................. 30 Table 7: Network Level Id types for the BSC-NE Level MOCs............................................ 32 Table 8: Description of the concerned MFS-NE Level MOCs ............................................. 34 Table 9: Network Level Id types for the MFS-NE Level MOCs............................................ 35

HISTORY

Ed. 01 21/10/2007: Creation from 3BK 09661 LAAA PBZZA Ed.01 Released

B10 is replaced by B11 The REFERENCED DOCUMENTS and RELATED DOCUMENT parts are updated

for B11 together with the corresponding references in the body of the document. A1353 RA is replaced by 9153 OMC-R.

15/02/2008: No technical changes. Ed. 02 18/02/2008:

The document is updated following the new capability to export alcatelIpPeer MOIs. This implies to export also alcatelIPCoordinator MOIs (parent MOIs for alcatelIpPeer MOIs).

The changes implied by the new capability to export alcatelTcRackManager MOIs and rnlAlcatelTcRackManager MOIs.


The changes implied by the new capability to export aGprsFabric MOIs. The document is updated following the new capability to export circuitPack MOIs.

This implies to export also equipmentHolder MOIs (parent MOIs for circuitPack MOIs).

The changes implied by the new capability to export crossConnection MOIs. 13/03/2009:

The changes implied by the new capability to export aGprsIpSigLink MOIs. 30/03/2009: No technical changes. Ed. 04 08/10/2009:


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

CBML:rat3g parameter is added to the list of the parameters to be checked at creation of the "NML":externalOmc3gCell MOIs.


The aGprsIpSigLink MOIs definition is updated. The changes implied by the new capability to export adjacency2gToLte MOIs. The changes implied by the new capability to export externalOmcLteCell MOIs.

17/03/2010: No technical changes.

REFERENCED DOCUMENTS

Standards

[ISO/IEC 8859-1] Information technology - 8-bit single-byte coded graphic character sets Part 1: Latin alphabet No.1 ISO/IEC 8859-1, April 1998

[ASN1] Information Processing Systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1) CCITT Rec. X.208 (1988) | ISO/IEC 8824 (1990)

[ISO/IEC 9899] Programming languages - C Recommendation ISO/IEC 9899, 1990

[GDMO] Information Technology - Open Systems Interconnection- Structure of Management Information: Guidelines for the Definition of Management Information CCITT Recommendation X.722 (ISO/IEC 10165-4), 1992

[X.721] Information Technology - Open Systems Interconnection Structure of Management Information - Part 2: Definition of Management Information CCITT Recommendation X.721 (ISO/IEC 10165-2); 1991 with the technical corrigendum 1, 1994

[M.3100] Maintenance: Telecommunications Management Network - Generic Network Information Model; CCITT Recommendation M.3100, July 1995

[Q.751.1] Specifications of signalling system No. 7 - Network Element Management Information Model for the Message Transfer Part (MTP) ITU-T Recommendation Q.751.1, October 1995

[GSM 12.00] Digital cellular telecommunications system (Phase 2); Network Management (NM); Part 1: Objectives and structure of Network Management GSM 12.00 version 4.5.1, ETS 300 612-1, August 1996

[GSM 12.20] Digital cellular telecommunications system (Phase 2);


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

Base Station System (BSS) Management Information GSM 12.20 version 4.2.1, ETS 300 622, June 1996

Alcatel documents

[ANOIprofile] Profile for the NMC/A1353 RA Q3 Interface 3BK 09654 LAAA PBZZA

[ANOIgdmo] NMC/A1353-RA Q3 Interface Information Model: GDMO Formal Specification 3BK 09707 LAAA PBZZA

[ANOIcs-gene] NMC/A1353-RA Q3 Interface: Overview and Conformance Statements 3BK 09709 LAAA PBZZA

[ACIE-si] 9153 OMC-R Configuration Import/Export Interface: Supplementary Information For Release B11

3BK 09773 MAAA PBZZA

[ACIE-siex] 9153 OMC-R Configuration Import/Export Interface: Informal excerpts of [ACIE-si] For Release B11

9153 OMC-R Configuration Import/Export Interface: Informal excerpts of 3BK 09773 MAAA PBZZA 3BK 09830 MAAA PBZZA

[ACIE-map] 9153 OMC-R Configuration Import/Export Interface: Mapping to BSS Telecom/O&M Parameters and to HMI names For Release B11

3BK 29094 MAAA PBZZA

RELATED DOCUMENTS

[ANOIappli] NMC/A1353-RA Q3 Interface: Position with respect to standards of the GDMO Formal Specification 3BK 09708 LAAA PBZZA


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

1. INTRODUCTION

1.1 Scope of the document

The 9153 OMC-R has several interfaces allowing external applications to access easily to its internal data, among which:

A Q3 interface, namely the NMC/9153 OMC-R Q3 Interface This Q3 interface is presented in [ANOIprofile] and is fully specified in [ANOIgdmo] and [ANOIcs-gene].

Several interfaces based on ASCII files These interfaces are distinguished according to the domain they are concerned with. One of these interfaces concern the Configuration Management domain. This interface is called the 9153 OMC-R Configuration Import/Export (ACIE) interface. Typical applications that can be interested are: Radio Network Level Configuration data:

Radio network planning, optimisation and tuning tools (e.g. A9159-NPO, A9155-RNP)

BSS-NE Level Configuration data: Tools for network inventory or equipment provisioning.

This document specifies the issues that are not release-dependent for the 9153 OMC-R Configuration Import/Export (ACIE) interface with a special emphasis on the relationships with the NMC/9153 OMC-R Q3 Interface. The issues that are release-dependent are specified in the following documents associated with a given 9153 OMC-R Release:

Reference Contents

[ACIE-si] Supplementary Information for a given 9153 OMC-R release

[ACIE-siex] Informal excerpts of [ACIE-si]

[ACIE-map] Mapping to BSS Telecom/O&M Parameters and to HMI names

The way files are transferred is out of the scope of this document together with issues pertaining to the 9153 OMC-R security or installation.

1.2 Overview of the ACIE interface

1.2.1 Presentation

The 9153 OMC-R Configuration Import/Export (ACIE) interface is an interface between: the 9153 OMC-R Configuration databases (ACDB) which store the 9153 OMC-R

Configuration data and the 9153 OMC-R Configuration File Repository (ACFR). This interface enables to: perform an import session, i.e. import a set of ASCII files from the ACFR to the ACDB;


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

perform an export session, i.e. export a set of ASCII files from the ACDB to the ACFR. These files are called ACIE files in what follows. This can be sketched out as follows:

9153 OMC-R configuration data

Export

Import

ACIE files (ASCII)

9153 OMC-R Configuration Databases

(ACDB)

9153 OMC-R Configuration File Repository

(ACFR)

Figure 1: The 9153 OMC-R Configuration Import/Export (ACIE) Interface

1.2.2 The supported services

The 9153 OMC-R configuration data that can be imported/exported are split up into the following levels, in accordance with TMN principles: Radio Network Level (associated acronym: RNL)

This corresponds to the Radio Configuration data at (sub-)network level Core BSS-NE level (also called BSC-NE level, associated acronym: BL)

This corresponds to the Equipment, Transmission and Software configuration data for a given core BSS-NE (also called BSC-NE).

GPRS BSS-NE level (also called MFS-NE level, associated acronym ML) This corresponds to the Equipment and Transmission configuration data for a given GPRS BSS-NE (also called MFS-NE). Actually, the data at this level are restricted to the configuration data relating to the GB interface. GPRS Radio configuration data are already addressed by the Radio Network level.

These levels can be sketched out as follows:


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

Radio Network Level (RNL)

BSC-NE Level (BL) MFS-NE Level (ML)

Figure 2: The different Levels for the 9153 OMC-R configuration data

These levels are handled separately. More precisely:

The 9153 OMC-R (externally accessible) configuration data at Network Level can be

imported, partially or completely

exported for a whole domain.

For a 9153 OMC-R operator, this domain can be: either the Supervised Configuration (SC)

N.B.: The SC is the representation of the network in its present state (i.e. it is the active domain). Modifications performed on the SC are immediately applied on the fields.

or a Provisioning Radio Configuration (PRC). N.B.: A PRC is a workspace built by a 9153 OMC-R operator from a copy

of all or part of the SC. It allows to prepare changes on the radio configuration in advance, check them and activate them as a whole. The activation mechanism is either global (Massive Logical Update -MLU- Mode) or atomic (Message Mode). It is possible to create several PRCs concurrently.

For example, a 9153 OMC-R operator can perform a partial export by creating a PRC with a part of the SC and export this PRC.

For a NMC, this domain can only be the SC.

The 9153 OMC-R (externally accessible) configuration data at BSC-NE Level can only be exported for a whole BSC-NE.

The 9153 OMC-R (externally accessible) configuration data at MFS-NE Level can only be exported for a whole MFS-NE.

In addition, An import session can be requested only by a 9153 OMC-R operator. An export session can be requested either by a 9153 OMC-R operator or by a NMC

(via the NMC/9153 OMC-R Q3 Interface) or via a dedicated script.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

A full export session (for the SC, for each of the existing BSC-NE and for each of the existing MFS-NE) is also triggered automatically by the 9153 OMC-R every day at a time that is defined at the installation of a 9153 OMC-R instance.

A Radio Network Level import/export session can be triggered using one of the following modes for uniquely identifying own/external cells at network level (called ACIE Cell Identification modes in what follows): The Application-Relative Cell Identity mode (ARCI mode for short)

In this case, the cells are named by identifying the cell depending on the application that has created it. More precisely, this is performed using a NetworkCellID value. This value is built from: An ApplicationID value which characterises uniquely the application (e.g. an 9153

OMC-R instance) that has created the corresponding cell; A cell reference which identifies uniquely a cell within those that have been created

by the same application. The CellGlobalIdentity mode (CGI mode for short)

In this case, the cells are named by identifying the cell depending on the location area associated with it within a GSM PLMN. More precisely, for a 2g cell this is performed using a CellGlobalIdentity value. This value is built from: A LocationAreaIdentity value which identifies uniquely a Location Area within a

GSM PLMN through its Mobile Country Code (MCC), Mobile Network Code (MNC) and Location Area Code (LAC);

A Cell Identity (CI) which identifies uniquely a cell within a location area. For a 3g cell this is performed using a Global3gCellIdentity value. This value is built from: Mobile Country Code (mcc3g); Mobile Network Code (mnc3g); Local3gCellIdentity which identifies uniquely a 3g cell in a PLMN. For a Lte cell this is performed using a eGlobalLteCellIdentity value. This value is built from: Mobile Country Code (mccLte); Mobile Network Code (mncLte); LteCellIdentity which identifies uniquely a Lte cell.

This ACIE Cell Identification mode applies to any MOI representing a (own or external) cell and whichever context of use, including as parent of another MOI or when referred to by or within an attribute (see [ACIE-si] for more information on the concerned attributes).

The following restrictions apply: The CGI mode is supported neither for a Radio Network Level export session

requested by a NMC, not for the automatic export session. In CGI mode, it is not possible to modify the value of the "GSM

12.20":cellGlobalIdentity attribute both for "NML":cell MOIs and "NML":externalOmcCell MOIs.

In CGI mode, it is not possible to modify the value of the "C9ML":global3gCellIdentity attribute for "NML":externalOmc3gCell MOI.

In CGI mode, it is not possible to modify the value of the "CBML":eGlobalLteCellIdentity attribute for "NML":externalOmcLteCell MOI.

Finally, the contents of a set of ASCII files produced as output of one ACIE export session can be filtered according to a file supplied by a given external application according to the


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

latter's actual needs. For the BSC-NE level, this facility is also supported for a set of ACIE export sessions corresponding to all the existing BSC-NEs. For the MFS-NE level, this facility is also supported for a set of ACIE export sessions corresponding to all the existing MFS-NEs.

1.3 Conventions and notations

To specify the form taken by a number of items (names, parts of ACIE files, etc..), the following conventions are used:

Item Meaning

CR carriage return [09] represents any digit from 0 to 9 [AZ] represents any character value from A to Z [09AF] represents any character value from 0 to 9

or A to F references a part (called a production)

whose semantics and syntax are described separately

represents any integer value is an integer value (possibly equal to 1)

defined at the installation of a 9153 OMC-R instance which represents the maximum number of sessions of the same kind that are allowed.

is an integer value defined at the installation of a 9153 OMC-R instance which represents the maximum number of errors that will be displayed.

| indicates that the form can be either the one referenced by (exclusive) or the one referenced by where and denote either production names or particular constant parts.

[...] delimits a part that may either be absent or present only once.

{...}* delimits a part that may be present zero or more times.

{...}+ delimits a part that may be present once or more times.

In addition, For the names and character strings mentioned below (to value a so-called production)

The set of characters allowed are those whose [ISO/IEC 8859-1] code lies in the following intervals:

Hexa Codes Characters

20 (SPACE)

2D -

30 to 39 [0-9]


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

Hexa Codes Characters

41 to 5A [A-Z]

5F _

61 to 7A [a-z]

C0 to FC

Table 1: Set of characters allowed in productions, names and labels

They contain at most 255 characters For the value of an attribute that contains a character string:

If this attribute represents a name or a label, the aforementioned limitation on the set of characters allowed shall be met.

Otherwise, a character that is not in this set shall be represented according to the following rule, referred to as the 'character translation rule' in what follows

Character Represented as

Character in the aforementioned set The same character

\ \\

Character not in the aforementioned set and different from \

\ where denotes the [ISO/IEC 8859-1] code of the character

Table 2: Character translation rule

The following notations are used: The GDMO notation defined in [GDMO]

N.B.: The labels used hereafter are not always the same as those used within the 9153 OMC-R. The underlying intention is for this document to be directly understandable, especially for readers familiar with the NMC/9153 OMC-R Q3 interface.

The ASN1 notation defined in [ASN1]. In tables and figures:

Dark grey (patterned or not) is used to indicate that the corresponding feature is not supported or not concerned.

indicates that the corresponding feature is supported.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

2. THE FILES CONCERNED BY THE ACIE INTERFACE

2.1 The 9153 OMC-R Configuration File Repository (ACFR)

The 9153 OMC-R has a File Repository dedicated to file transfers from/to external clients, called the 9153 OMC-R File Transfer Repository (AFTR). The information required to reach this general file repository is predefined at the installation of a 9153 OMC-R instance. The 9153 OMC-R Configuration File Repository (ACFR) actually corresponds to a directory of that repository. Its name is ACIE. The access to ACFR is allowed for the 9153 OMC-R operators or external applications having the configuration functional profile. In particular, it is always allowed for NMCs which are assumed to have both the supervision and configuration functional profiles. The authentification requirements are the same as for the 9153 OMC-R File Transfer Repository; these requirements are predefined at the installation of a 9153 OMC-R instance.

ACIE import directories: The ACFR has (sub-)directories dedicated to ACIE (Network Level) import sessions, called the ACIE Network Level import directories. These directories are named

ACIE_NLimport_Dir. where is an integer whose value is between 1 to included. They are created at the installation of a 9153 OMC-R instance.

A peer entity (e.g. a NMC) is allowed to list the contents of an import directory transfer files to an import directory

When a file is transferred which has the same name as an existing file, the latter is replaced.

On the other hand, a peer entity shall not directly delete or modify files in this directory.

ACIE export directories:

The ACFR has (sub-)directories dedicated to ACIE Network Level export sessions, called the ACIE Network Level export directories. These directories are named

ACIE_NLexport_Dir. where is an integer whose value is between 1 to included. They are created at the installation of a 9153 OMC-R instance.

There is one directory dedicated to ACIE BSC-NE Level export sessions, called the ACIE BSC-NE Level export directory. This directory is named ACIE_BLexport and is created at the installation of a 9153 OMC-R instance.

For each BSC-NE, this directory has (sub-)directories called the ACIE export directories for that BSC-NE. These directories have a name of the form

ACIE_BSSexport_Dir


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

where is an integer equal to the value of the M.3100:managedElementComplexId of the corresponding EML:alcatelManagedElementComplex object instance. All the ACIE export directories for a given BSC-NE are created when that BSC-NE is created.

There is one directory dedicated to ACIE MFS-NE Level export sessions, called the ACIE MFS-NE Level export directory. This directory is named ACIE_MLexport and is created at the installation of a 9153 OMC-R instance.

For each MFS-NE, this directory has (sub-)directories called the ACIE export directories for that MFS-NE. These directories have a name of the form

ACIE_MFSexport_Dir where is an integer equal to the value of the NMD:networkElementId of the corresponding NMD:networkEelement object instance. All the ACIE export directories for a given MFS-NE are created when that MFS-NE is created.

A peer entity (e.g. a NMC) is allowed to list the contents of an export directory; transfer files from an export directory but not to add, delete or modify files in such a directory.

Only the 9153 OMC-R (i.e. not a peer entity) is allowed to create or delete a directory of the ACFR.

This organisation can be pictured as follows for equal to c:


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

ACIE

ACIE_BSSnexport_Dir1

ACIE_BSSnexport_Diri

ACIE_BSSnexport_Dirc

ACIE_BLexport

ACIE_MFS1export_Dir1

ACIE_MFS1export_Diri

ACIE_MFS1export_Dirc

ACIE_MLexport

ACIE_NLexport_Dir1

ACIE_NLexport_Diri

ACIE_NLexport_Dirc

ACIE_NLimport_Dir1

ACIE_NLimport_Diri

ACIE_NLimport_Dirc

ACIE_BSS1export_Dir1

ACIE_BSS1export_Diri

ACIE_BSS1export_Dirc

ACIE_MFSnexport_Dir1

ACIE_MFSnexport_Diri

ACIE_MFSnexport_Dirc

Figure 3: Organisation of the ACFR for equal to c

For a given 9153 OMC-R instance on which several clients or applications are likely to trigger import and/or export sessions, it is recommended to have a clear policy with respect to the allocation of sub-directory numbers that can be used by a given type of client or application.

2.2 The 9153 OMC-R External Interfaces General repository

(AEIGR)

The 9153 OMC-R has a repository dedicated to files relating to the 9153 OMC-R external interfaces and supplied by or for external applications. This repository is called the 9153 OMC-R External Interfaces general repository (AEIGR). The information required to reach this general repository is predefined at the installation of a 9153 OMC-R instance.

This repository has at least one sub-directory dedicated to scripts associated with the 9153 OMC-R external interfaces that are made available by the 9153 OMC-R to external applications.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

This (sub-)directory, called the 9153 OMC-R External Interfaces Script (AEIS) directory, is named 'script'. The access rights of this directory and the script files it contains are such that an external application can execute each of these scripts but not read nor modify them.

Depending on the 9153 OMC-R instance, there may or not be another sub-directory, called the 9153 OMC-R External Interfaces Application (AEIA) public repository, named 'public' that can be used by any external application to store files used as input to the aforementioned scripts or produced by the latter. The access rights of this repository are such that any external application can freely use it.

2.3 The different types of ACIE files

The 9153 OMC-R Configuration File Repository contains so-called ACIE files. An ACIE file can be associated:

either with a given Managed Object Class These files are referred to as the ACIE MOC files. These files have the same format, name and structure for import sessions and for export sessions. This makes it possible to take advantage of an export file to produce a corresponding import file.

or with (an) import or export session(s) There are several such files:

Files intended to help a 9153 OMC-R operator to perform an import session. These files are referred to as the ACIE help files. These files are not processed by the 9153 OMC-R, they are only intended for human readers.

Files intended to prevent concurrent import/export sessions. These files are referred to as the ACIE lock files.

Files intended to prevent an export session to be triggered on a directory in case a previous export session has been triggered indicating this directory as input but the corresponding produced ACIE MOC files have not yet been transferred. These files are referred to as the ACIE done files.

2.4 Formats of the ACIE files

The format used for an ACIE MOC file is the (so-called) Comma Separated Value (CSV) format that consists in several lines separated by CR, each line being of the form:

[;]; where contains only characters different from ; and CR. For example,

aaaaaaaaaa;bbbbbbbbbb;cccccccccc;dddddddddd;eeeeeeeee; 1111111;2222222222;333333333;444444444;555555555; fffffff;gggggggg;hhhhhhhhh;iiiiiiiiiiiii;jjjjjjjjjjjjjjjjjjj;

The advantages of this format are as follows:

These files are readable without any specific tool.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

The contents of these files can easily be interpreted/converted as a table in which the lines of the table correspond to the lines of the text and the columns of the tables are splitted using the character ; in the text. For example, the aforementioned text in CSV format can be interpreted as: aaaaaaaaaa bbbbbbbbbb cccccccccc dddddddddd eeeeeeeee 1111111 2222222222 333333333 444444444 555555555 fffffff gggggggg hhhhhhhhh iiiiiiiiiiiii jjjjjjjjjjjjjjjjjjj N.B.: This interpretation is assumed in what follows wherever it is more convenient.

The reverse conversion (from a table to a CSV format) can also easily be performed.

The files to be imported can be manually written or written using widely available tools. For example, it is possible to write a Microsoft Excel worksheet then convert it to the CSV format to produce a corresponding import file.

N.B.: The expression Comma Separated Value comes from the US for which the separator is the Comma (i.e. ,). In France, the Semi colon character is used instead. This implies to configure the tools to interpret the corresponding CSV files (e.g. Microsoft Excel) appropriately.

The format used for the ACIE help files is either plain ASCII or HTML.

The format used for the ACIE lock and done files is plain ASCII.

2.5 Names of the ACIE files

The name of an ACIE MOC file is of the form: .csv

where is similar to the name of the MOC associated with the file, except that it begins with an upper case letter instead of a lower case one; "-" are replaced with "_". An example of such a name is Cell.csv.

The name of an ACIE help file is of the form: Readme.

where is equal to: txt if the format used is plain ASCII html if the format used is HTML.

The name of an ACIE lock file is: Lock

The name of an ACIE done file is: Done

2.6 Structure of the ACIE files

2.6.1 General description

An ACIE MOC file is composed as follows:


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

[]

in which is present only when there is at least one MOI of the associated MOC and has the following form:

, and are described in the following sections. N.B.: As regards and , the strings mentioned in the

following sections are not enclosed between " characters, contrary to strings in .

An ACIE help file has no specific structure.

An ACIE lock file contains a lock body. This lock body shall be placed on the first line of the file and shall be composed of only one line. The structure of the lock body is as follows:

[;] where: is a character string indicating the corresponding host name

It is never present for a session at Network level and is always present for a session at BSS-NE level.

is an integer value corresponding to the process Id of the process handling the import or export session.

An ACIE Done file contains a done body. This done body shall be placed on the first line of the file and shall be composed of only one line. The structure of the done body is as follows:

;; where (resp. ) is identical to the (resp. ) of the part of the corresponding ACIE MOC files (see section 2.6.2).

2.6.2 The header of an ACIE MOC file

The header gives general information concerning the import or export session. It notably supplies information enabling to distinguish ACIE MOC files belonging to different import or export sessions.

This header shall be placed on the first line of the file and shall be composed of only one line. This enables the header to be easily extracted from the file. For example, under Unix, the header of a file named Cell.csv can be extracted taking advantage of the following command:

head-1 Cell.csv

The structure of the header is as follows: ;;;;;;[;] where: is a character string that indicates the considered version of the

9153 OMC-R information model from an ACIE viewpoint. It serves to indicate, for a given (set of) ACIE MOC files, which is the considered version of the associated supplementary information document. It has the form


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

ACIE where: indicates the Base used for the information model. is an integer

indicates the (local) date at which the file was created. It is of the form YYYY-MM-DD.

indicates the (local) time at which the file was created. It is of the form hh:mm:ss.

is a character string that indicates the concerned 9153 OMC-R instance. More precisely, it is a predefined value that uniquely identifies the 9153 OMC-R instance throughout the world. It is assigned at the 9153 OMC-R instance installation time. Its length is at most 32 characters. For more information, the reader is referred to the document that specifies ACIE-related supplementary information for the concerned release.

is: absent for an export file a character string that indicates which entity has created the file for an import file.

is a character string that indicates: For an export file:

At Network Level, the "M.3100":userLabel attribute value of the corresponding "NML":subNetwork MOI, i.e. the name of the PRC or Supervised Configuration.

At BSS-NE Level, the "M.3100":userLabel attribute value of the "EML":alcatelManagedElement MOI representing the corresponding BSC equipment.

For an import file, a session name. A set of file to be imported should indicate the same value for .

is a character string equal to CGIMode. The corresponding part (including the ';' character) shall be present for a file produced for or by a Radio Network Level import/export session triggered in CGI mode and absent otherwise.

2.6.3 The sub-header of an ACIE MOC file

The sub-header corresponds to the column titles of the table associated with the body part of the ACIE MOC file; i.e. it describes the type of information contained in the columns.

This sub-header shall be placed on the second line of the file and shall be composed of only one line. This enables the sub-header to be easily extracted from the file. For example, under Unix, the sub-header of a file named Cell.csv can be extracted taking advantage of the following command:

head 2 Cell.csv | tail 1

The structure of the sub-header is as follows: ;;;

where: is equal to the string Mode is equal to a string formed by concatenating

(see section 2.5) and the string InstanceIdentifier has the form:

[;]*


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

in which corresponds to the name of an attribute of the corresponding managed object instances. For an export file, these names are translated as follows: the first (lower case) letter is replaced by the corresponding upper case letter "-" is replaced by "_" The following should hold: For an export file, the list of attributes indicated in the sub-header shall be

complete. It is specified in the supplementary information document associated with the concerned 9153 OMC-R Release.

For an import file, this list of attributes can be limited to the attributes whose value need to be specified in the body.

2.6.4 The body of an ACIE MOC file

2.6.4.1 The different types of lines contained in the body

The body can contain: Lines that are not processed, namely:

either empty lines or comment lines.

Comment lines begin with the character #. They can serve to make the body more readable.

These lines and comment lines can appear freely in the body. MOI-related lines

These lines correspond to a given object instance of the MOC associated with the file. For an export file, there is exactly one such line per existing object instance of the

MOC. For an import file, several lines may correspond to the same object instance.

This is intended to make it easier to write or modify import files manually and to merge several import operations within one file.

2.6.4.2 Structure of MOI-related lines

MOI-related lines have the following form: ;;;

where: shall always be equal to E for an export file.

For an import file, it shall be equal to either C, M, D. It indicates which kind of operation is requested on the object instance corresponding to the line, namely:

Corresponding request

C create a given object instance M change the value of a number of attributes of a given object

instance. D delete a given object instance

identifies uniquely the object instance at network level1. It is a value of the Network Level Id type for the MOC associated with the file.

1 It is the responsability of the entity that has created the import file to guarantee this unicity.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

N.B.: These Network Level Id types are defined in section 3.1.3 for the concerned Network Level MOCs and section 3.2.3 for the concerned BSS-NE Level MOCs.

has the form: [;[]]

*

in which may be absent for a number of lines and/or a number of columns in an import file; is present for all lines and for all columns in an export file whenever the attribute

value is applicable. An attribute is said to have a value that is 'not applicable' for MOIs of a given MOC when: In an associated export file, the attribute is listed in the sub-header and no value is

indicated in the body. In that respect, to specify an attribute value as 'not applicable' is stronger than specifying that it is 'not significant' since, in that case, a value may be indicated in the body but this value shall not be relied upon.

In an associated import file, if the attribute is listed in the sub-header and a value is indicated in the body, this value is discarded.

These cases along with the possible attribute values are specified in the supplementary information document associated with the concerned 9153 OMC-R Release.

2.6.4.3 Representation of values in MOI-related lines

Values in MOI-related lines (i.e. both and mentioned above) are represented using the ASN1 value notation as defined in [ASN1]. The main peculiarities concern: The ASN1 types for which there are several possible ways to express corresponding

values. In that case, only one way is chosen (the one stated as the preferred one by [ASN1] if any).

The values of type OBJECT IDENTIFIER which are more specifically defined in the framework of the ACIE interface.

The following table defines precisely how the values of the ASN1 types of interest are represented: ASN1 type Represented as Example Description

Simple ASN1 types

BOOLEAN TRUE | FALSE TRUE The keyword TRUE or FALSE.

INTEGER 123 Signed number INTEGER {

int1 (0), int2 (1), ..... intn ()

}

int1 | int2 | ... | intn N.B.: Integer values with

no associated

symbolic name

(legal in GDMO)

shall not be used.

degraded Symbolic name of the integer value in which each "-" character, if any, is replaced by "_"

ENUMERATED { enum1 (0), enum2 (1), ..... enumn ()

}

enum1 | enum2 | ... | enumn

locked Symbolic name of the enumerated value in which each "-" character, if any, is replaced by "_"

REAL C double precision floating point value as

3.4E3 C double precision floating point


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

defined in [ISO/IEC 9899]

BIT STRING or OCTET STRING or BIT STRING {

bitstr1 (0), bitstr2 (1), ..... bitstrn ()

}

'[0-9A-F]+'H '3FE2EBAD'H BIT STRING or OCTET STRING value in hexadecimal form

NULL NULL NULL keyword NULL character string type (e.g. PrintableString, GraphicString)

[]* where is any character allowed for the character string type possibly translated according to the character translation rule mentioned in section 1.3.

BSS (possibly converted) character string value

GeneralizedTime First form of a GeneralizedTime value defined in [ASN1]

19951106210627.3 (6th Nov 1995, 21:06:27.3 local time.)

GeneralizedTime value, local time form.

OBJECT IDENTIFIER

{bsc{100}, btsRdn 1} See section 2.6.4.2.

Structured ASN1 types In what follows: or denotes an ASN1 type (resp. ) denotes the representation of a value of type (resp.

). N.B.: Tags are not mentioned hereafter since they do not influence the representation of the

value. SEQUENCE OF or SET OF

{[] [,]*]}

{12, 13, 14} (value of type SET OF INTEGER)

List of values of type separated with , and enclosed between { and }.

SEQUENCE { f1 , f2 OPTIONAL, ... fn

} or SET { f1 , f2 , ... fn

}

{ [f1 ] [, f2 ] ... [, fn ] }

{hreqave 16} represents a value of type HoAveragingDistParam (from [GSM 12.20]).

List of field names and values of the associated type separated with , and enclosed between { and }. If a field is OPTIONAL and is not present, it does not appear in the list. If a field is present (in particular if it is mandatory), it can nevertheless be omitted in the list for an import file. In that case, the value assumed for this field is the current one (if = "M") or the default


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

one (if ="C")

CHOICE { alt1 [1] , alt2 [2] , ... altn [n]

}

alt1: alt2: ... altn:

noUse:NULL represents a value of type FrequencyUsage (from [GSM 12.20]) for which the noUse alternative is relevant.

Name of the alternative and value of the associated type separated with :

Table 3: Representation of values in ACIE MOC files


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

3. CONCERNED 9153 OMC-R MOCS

3.1 Concerned Network Level MOCs

3.1.1 Description

The Radio Network Level MOCs concerned by import sessions and export sessions are the same. They are all defined in the Network Manager Level part of the 9153 OMC-R Information Model (corresponding GDMO label: NML).

The following table lists these MOCs, indicating, for each MOC: the closest standard MOC(s), if any what the corresponding object instances represent whether it is allowed to create (C), delete(D) or modify the attribute values of (M) these

object instances. 9153 OMC-R MOC Closest standard MOC(s) Short description C D M

NML:adjacency Merge of: GSM 12.20: adjacentCellHandOver

GSM 12.20: adjacentCellReselection

Represents the logical view of an adjacency (containing cell, target cell) managed by a 9153 OMC-R instance.

NML:adjacency2gTo3g

none Represents the relationship between a serving 2G cell and a target (external) 3G cell.

NML:adjacency2gToLte

none Represents the relationship between a serving 2G cell and a target (external) LTE cell.

NML:cell GSM 12.20:bts Represents the logical view of a cell managed by the 9153 OMC-R.

NML: externalOmc3gCell

none Represents a 3G cell that is not managed by the 9153 OMC-R but is used for the handover and reselection mechanisms.

NML: externalOmcCell

GSM 12.20:bts Represents a cell that is not managed by the 9153 OMC-R but is used for the handover and reselection mechanisms.

NML: externalOmcLteCell

none Represents a LTE cell that is not managed by the 9153 OMC-R but is used for the reselection mechanisms.

NML:hoControl GSM 12.20: handoverControlGSM0508

Supports the management of parameters for the handover algorith used by Alcatel.

(1)

NML:rnlAlcatelMFS None Represents the Radio Network Level view of an


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

9153 OMC-R MOC Closest standard MOC(s) Short description C D M

Alcatel MFS (NE for GPRS handling).

NML:rnlAlcatelBSC Merge of: GSM 12.20:bssFunction GSM 12.20:bsc

Represents the Radio Network Level view of an Alcatel BSC.

NML:rnlAlcatelSector GSM 12.20:bts Represents the Radio Network Level view of an Alcatel BTS Sector. An object of this MOC has a relationship attribute (namely NML:rnlRelatedCell) which identifies the cell that is mapped onto the represented BTS sector, if any.

NML: rnlAlcatelSiteManager

GSM 12.20:btsSiteManager Represents the Radio Network Level view of an Alcatel BTS Site Manager.

NML:rnlAlcatelTcRackManager

"GSM 12.20": gsmManagedFunction

Represents the Radio Network Level view of an Alcatel TC Rack Manager.

NML:rnlBasebandTransceiver

Merge of: GSM 12.20: basebandTransceiver

GSM 12.20: channel

Represents the Radio Network Level view of an Alcatel Baseband Transceiver.

NML:rnlFrequencyHoppingSystem

GSM 12.20: frequencyHoppingSystem

Represents a set of radio frequency channels used in a specific frequency hopping sequence.

NML:rnlPowerControl GSM 12.20: powerControlGSM0508

Supports the management of parameters for the power control algorithm used by Alcatel.

(1)

NML:subNetwork GSM 12.00:plmnNetwork Represents the radio network managed by the 9153 OMC-R.

Table 4: Description of the concerned Network Level MOCs

(1) The corresponding object instances are automatically created (resp. deleted) when the containing cell is created (resp. deleted).

Implied sub-object instances: A NML:cell object instance has all the object instances named under it as implied object instances.

3.1.2 Corresponding Naming Tree

The corresponding Naming tree is as follows:

NML:subNetwork

NML:

externalOmc3gCell NML: externalOmcLteCell

NML: externalOmcCell

"NML": rnlAlcatelMFS

NML: rnlAlcatelBSC


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

NML:

rnlAlcatelTcRackManager NML:

rnlAlcatelSiteManager

NML:cell

NML:

rnlAlcatelSector

NML:

adjacency NML:

hoControl NML: rnlBasebandTransceiver

NML: rnlFrequencyHoppingSystem

NML: rnlPowerControl

NML: adjacency2gTo3g

NML: adjacency2gToLte

Figure 4: Naming Tree for the concerned Network Level MOCs

From what precedes, it can be deduced that the MOIs that belong to one of the following MOCs are identified differently depending on the chosen ACIE Cell Identification mode: "NML":adjacency "NML":adjacency2gTo3g "NML":adjacency2gToLte "NML":cell "NML":externalOmcCell "NML":externalOmc3gCell "NML":externalOmcLteCell "NML":hoControl "NML":rnlBasebandTransceiver "NML":rnlFrequencySystem "NML":rnlPowerControl.

3.1.3 Corresponding Network Level Id types

3.1.3.1 Description

N.B.: The notion of Network Level Id type has been presented in section 2.6.4.2.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

9153 OMC-R MOC Network Level Id type Comments

NML:adjacency In CGI mode: CGIBasedAdjacencyID else: NetworkAdjacencyID NML:adjacency2gTo3g In CGI mode: CGIBasedAdjacency2g

To3gID

else: NetworkAdjacency2gTo

3gID

NML:adjacency2gToLte In CGI mode: ECGIBasedAdjacency2

gToLteID

else: NetworkAdjacencyID NML:cell In CGI mode: CellGlobalIdentity else: NetworkCellID NML:externalOmcCell In CGI mode: CellGlobalIdentity else: NetworkCellID The corresponding value for

an externalOmcCell of one 9153 OMC-R instance may differ from that of the corresponding cell of another 9153 OMC-R instance.

NML:externalOmc3gCell In CGI mode: Global3gCellIdentity else: Network3GCellID The corresponding value for

an externalOmc3gCell of one 9153 OMC-R instance may differ from that of the corresponding cell of another 9153 OMC-R instance.

NML:externalOmcLteCell In CGI mode: EGlobalLteCellIdentity else: NetworkCellID The corresponding value for

an externalOmcLteCell of one 9153 OMC-R instance may differ from that of the corresponding cell of another 9153 OMC-R instance.

NML:hoControl In CGI mode: CellGlobalIdentity The value corresponds to the

CellGlobalIdentity value of the containing cell


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

9153 OMC-R MOC Network Level Id type Comments

else: NetworkCellID The value corresponds to the

NetworkCellID value of the containing cell

NML:rnlAlcatelBSC NetworkBSCID NML:rnlAlcatelMFS NetworkMFSID NML:rnlAlcatelSector NetworkSectorID NML:rnlAlcatelSiteManager NetworkSiteManagerID It is recommended to prevent

from working on the configuration of an object instance of this MOC or named under the latter whereas a BTS is moved by the 9153 OMC-R since this changes the value of the btsRdn field of NetworkSiteManagerID.

NML:rnlAlcatelTcRackManager

NetworkTcRackManagerID

NML:rnlBasebandTransceiver In CGI mode: CGIBasedBbtID else: NetworkBbtID NML:rnlFrequencyHoppingSystem

In CGI mode:

CGIBasedFhsID else: NetworkFhsID NML:rnlPowerControl In CGI mode: CellGlobalIdentity The value corresponds to the

CellGlobalIdentity value of the containing cell

else: NetworkCellID The value corresponds to the

NetworkCellID value of the containing cell

NML:subNetwork INTEGER RDN of the corresponding MOI

Table 5: Network Level Id types for the Network Level MOCs

3.1.3.2 Corresponding ASN1 type definitions

These types are defined in [ACIE-si] (ACIENetworkLevelASN1Module).


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

3.2 Concerned BSC-NE Level MOCs

3.2.1 Description

There are no BSC-NE level MOC that is concerned by import sessions. The BSC-NE level MOCs concerned by export sessions are defined in several parts of the 9153 OMC-R Information Model, namely: The Element Manager Level part (corresponding GDMO label: EML) The Software part (corresponding GDMO label: SW) The M.3100 part (corresponding GDMO label: M.3100) The Q.751.1 part (corresponding GDMO label: Q.751.1) The GSM 12.20 customized part (corresponding GDMO label: A12.20)

The following table lists these MOCs, indicating, for each MOC: the closest standard MOC(s), if any what the corresponding object instances represent

9153 OMC-R MOC Closest standard MOC(s)

Short description

EML:alcatel2MbTTP Merge of: M.3100:trailTerminationPointBidirectional

M.3100:connectionTerminationPointBidirectional

Represents a 2Mb termination point of a BSC, a BTS equipment or a transcoder.

EML:alcatelAbisChainRingCoordinator

none This MOC is introduced notably to manage Abis Hardware extension/reduction.

EML:alcatelAbisChainRing none Represents a chain or a ring of BTS at the Abis interface.

EML:alcatelBasebandTransceiver Merge of: GSM 12.20: basebandTransceiver

GSM 12.20: channel

Represents the BSC-NE Level view of an Alcatel Baseband Transceiver.

EML:alcatelBsc Merge of: GSM 12.20:bssFunction

GSM 12.20:bsc

Represents the BSC-NE Level view of an Alcatel BSC.

EML:alcatelBssFunction GSM 12.00":bssFunction Models the functionality of a corresponding Alcatel BSC-NE.

EML:alcatelBts-Sector GSM 12.20:bts Represents the BSC-NE Level view of an Alcatel BTS Sector.

EML:alcatelBtsSiteManager GSM 12.20: btsSiteManager

Represents the BSC-NE Level view of an Alcatel BTS Site Manager.

EML:alcatelCircuitPack M.3100:circuitPack Represents a plug-in replaceable unit that can be inserted or removed from a corresponding equipment holder in the Alcatel BSC-NE.

EML:alcatelConnectionR1 M.3100:connectionR1 Represents a PCM Circuit at the Abis or AterMux interface.

EML:alcatelFunction none This MOC models a function relevant for an equipment in a


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.


Short description

BSC-NE EML:alcatelFunctionCoordinator none This MOC models all the

functions related to the same "EML":alcatelManagedElement MOI

EML:alcatelIPCoordinator none This MOC is introduced to optimize requests concerning EML:alcatelIPLink object instances.

EML:alcatelIPLink none Represents the IP link between the 9153 OMC-R and the BSC-NE

EML:alcatelIpPeer none Represents the IP association between the BSC-NE and another NE.

EML:alcatelLapdLink GSM 12.20:lapdLink Represents a logical LapD connection on a signalling link on the Abis interface.

EML:alcatelManagedElement M.3100: managedElement

Represents an equipment composing a BSC-NE, i.e. either a BSC, a BTS or a Transcoder equipment.

EML:alcatelManagedElementComplex

M.3100:managedElementComplex

Models all aspects (functionality, equipment, ...) of a BSC-NE

EML:alcatelOperatingSoftwareUnit GSM 12.20: operatingSoftwareUnit

Represents an operating software resource in the Alcatel BSC-NE.

EML:alcatelPeerCoordinator none This MOC is introduced to optimize requests concerning EML:alcatelIpPeer object instances.

EML:alcatelRadioCarrier GSM 12.20:radioCarrier Contains manageable properties of a radio carrier (notably hardware ones)

EML:alcatelReplaceableSoftwareUnit

GSM 12.20: replaceableSoftwareUnit

Represents a unit of software that needs to be separately identifiable and/or replaceable in the Alcatel BSC-NE.

EML:alcatelSignLinkN7 Q.751.1:signLinkTp Represents the termination of a SS No.7 signalling link between the BSC-NE and the MSC.

EML:alcatelSignLinkSetTp Q.751.1:signLinkSetTp Represents a SS No.7 signalling link set termination point.

EML:alcatelTcRackManager "GSM 12.20": gsmManagedFunction

Represents the supervising BSSIM view of an TC Rack.

E6ML:alcatelX25Coordinator none This MOC is introduced to optimize requests concerning EML:alcatelX25Link object instances.

E6ML:alcatelX25Link none Represents the X25 link between the 9153 OMC-R and the BSC-NE

M.3100:equipmentHolder M.3100: equipmentHolder

Represents either a shelf or a rack in the BSC-NE.

GSM 12.20: executableSoftwareUnit

GSM 12.20: executableSoftwareUnit

Represents a unit of software that is separately identifiable and


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.


Short description

is ready to be used in the Alcatel BSC-NE.

Q.751.1:mtpSignPoint Q.751.1:mtpSignPoint Represents the Message Transfer Part (MTP) functionality of the BSC.

Table 6: Description of the concerned BSC-NE Level MOCs


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.


The corresponding Naming tree is as follows: EML:

alcatelManagedElementComplex

"EML": alcatelManagedElement

"EML": alcatelAbisChainRingCoordinator

E6ML: alcatelX25Coordinator

EML: alcatelConnectionR1

"EML":

alcatelAbisChainRing E6ML:

alcatelX25Link "Q.751.1":

mtpSignPoint

"EML":alcatelFunctionCoordinator "EML ":

alcatelSignLinkSetTp

"EML":alcatelFunction "EML":

alcatelSignLinkN7

"M.3100":

equipmentHolder (Rack) "EML":alcatel2MbTTP

SW: alcatelOperatingSoftwareUnit

"M.3100":

equipmentHolder (Shelf)

"EML":alcatelCircuitPack

"EML":

alcatelBssFunction

"EML": alcatelBsc

"EML": alcatelBtsSiteManager

"EML": alcatelLapdLink

EML: alcatelTcRackManager

"EML":alcatelBts-Sector

"EML": alcatelIPCoordinator

"EML": alcatelPeerCoordinator

"EML":

alcatelBasebandTransceiver EML: alcatelRadioCarrier

"EML": alcatelIPLink

"EML": alcatelIpPeer

SW:alcatelReplaceableSoftwareUnit

GSM 12.20:executableSoftwareUnit

Figure 5: Naming Tree for the concerned BSC-NE Level MOCs


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.


3.2.3.1 Description

N.B.: The notion of Network Level Id type has been presented in section 2.6.4.2. 9153 OMC-R MOC Network Level Id type

EML:alcatel2MbTTP NetworkAlcatel2MbTTPID EML:alcatelAbisChainRing NetworkAlcatelAbisChainRingID EML:alcatelAbisChainRingCoordinator NetworkAlcatelAbisChainRingCoordinatorID EML:alcatelBasebandTransceiver NetworkAlcatelBasebandTransceiverID EML:alcatelBsc NetworkAlcatelBscID EML:alcatelBssFunction NetworkAlcatelBssFunctionID EML:alcatelBts-Sector NetworkAlcatelBtsSectorID EML:alcatelBtsSiteManager NetworkAlcatelBtsSiteManagerID EML:alcatelCircuitPack NetworkAlcatelCircuitPackID EML:alcatelConnectionR1 NetworkAlcatelConnectionR1ID EML:alcatelFunction NetworkAlcatelFunction EML:alcatelFunctionCoordinator NetworkAlcatelFunctionCoordinator EML:alcatelIPCoordinator NetworkAlcatelIPCoordinatorID EML:alcatelIPLink NetworkAlcatelIPLinkID EML:alcatelIpPeer NetworkAlcatelIpPeerID EML:alcatelLapdLink NetworkAlcatelLapdLinkID EML:alcatelManagedElement NetworkAlcatelManagedElementID EML:alcatelManagedElementComplex NetworkAlcatelMECID EML:alcatelOperatingSoftwareUnit NetworkAlcatelOSUID EML:alcatelRadioCarrier NetworkAlcatelRadioCarrierID EML:alcatelPeerCoordinator NetworkAlcatelPeerCoordinatorID EML:alcatelReplaceableSoftwareUnit NetworkAlcatelRSUID EML:alcatelSignLinkN7 NetworkAlcatelSignLinkN7ID EML:alcatelSignLinkSetTp NetworkAlcatelSignLinkSetTpID EML:alcatelTcRackManager NetworkAlcatelTcRackManagerID E6ML:alcatelX25Coordinator NetworkAlcatelX25CoordinatorID E6ML:alcatelX25Link NetworkAlcatelX25LinkID M.3100:equipmentHolder NetworkEquipmentHolderID GSM 12.20:executableSoftwareUnit NetworkESUID Q.751.1:mtpSignPoint NetworkMtpSignPointID

Table 7: Network Level Id types for the BSC-NE Level MOCs


These types are defined in [ACIE-si] (ACIEBSSLevelASN1Module).

3.3 Concerned MFS-NE Level MOCs

3.3.1 Description

There are no MFS-NE level MOC that is concerned by import sessions. The MFS-NE level MOCs concerned by export sessions are defined in several parts of the 9153 OMC-R Information Model, namely: The MFS-NE Manager Level part (corresponding GDMO label: NMD)


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

The MFS-NE transport part (corresponding GDMO label: AMFSME) The MFS-NE Frame Relay part (corresponding GDMO label: AGFR) The GB interface part (corresponding GDMO label: AGVC)

The following table lists these MOCs, indicating, for each MOC: the closest standard MOC(s), if any what the corresponding object instances represent

9153 OMC-R MOC Closest standard

MOC(s)

Short description

"AMFSME":aGprs2MbTTP None Represents a 2Mb termination point of a MFS-NE

"AGFR":aGprsBearerChannel None Represents a Bearer Channel at the GB interface.

"AMFSME":aGprsFabric None Represents the function of managing the establishment and the release of the cross-connections of 2Mb-TTPs ports.

"AATER":aGprsIpSigLink None Represents the GPRS signaling link over IP. It Carries GPRS signalisation between MFS and BSC in IP mode.

"AGVC":aGprsNse None Represents a Network Service Element (NSE) which is a group of Network Service Virtual Connection (NS-VC).

"AGVC":aGprsNsvc None Represents a Network Service Virtual Connection (NS-VC) which provides an end-to-end communication between the MFS and the SGSN.

"AGFR":aGprsPvc None Represents a Permanent Virtual Connection (PVC) which allows to support multiplexing on a Bearer Channel.

"AGVC":aGprsSgsnIpEndPoint None Represents the Serving Gprs Support Node (Sgsn) side of a Gb IP link.

M.3100:circuitPack M.3100:circuitPack Represents a plug-in replaceable unit that can be inserted or removed from a corresponding equipment holder in the MFS-NE.

M.3100:crossConnection M.3100:crossConnection Represents an assignment relationship between the termination point or GTP object listed in the From Termination attribute and the termination point or GTP objects listed in the To Termination attribute of this managed object.

M.3100:equipmentHolder M.3100:equipmentHolder

Represents either a shelf or a rack in the MFS-NE.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

9153 OMC-R MOC Closest standard

MOC(s)

Short description

NMD:networkElement None Models the MFS-NE as viewed by the 9153 OMC-R. It is mapped onto a corresponding "M.3100":managedElement MOI in the NMF-NE information Model.

Table 8: Description of the concerned MFS-NE Level MOCs


The corresponding Naming tree is as follows:

"NMD":networkElement

"AMFSME":

aGprs2MbTTP "M.3100": equipmentHolder (Rack)

"AATER": aGprsIpSigLink

"AGVC": aGprsNse

"AGFR":

aGprsBearerChannel "M.3100": equipmentHolder (Shelf)

"AGVC":

aGprsSgsnIpEndPoint "AGVC":

aGprsNsvc

"AGFR": aGprsPvc

"M.3100": circuitPack

"AMFSME": aGprsFabric

"M.3100":

crossConnection

Figure 6: Naming Tree for the concerned MFS-NE Level MOCs


3.3.3.1 Description

N.B.: The notion of Network Level Id type has been presented in section 2.6.4.2. 9153 OMC-R MOC Network Level Id type

"AMFSME":aGprs2MbTTP NetworkAlcatelGprs2MbTTPID "AGFR":aGprsBearerChannel NetworkAlcatelGprsBearerChannelID "AMFSME":aGprsFabric NetworkAlcatelGprsFabricID "AATER": aGprsIpSigLink NetworkAlcatelGprsIpSigLinkID "AGVC":aGprsNse NetworkAlcatelGprsNseID "AGVC":aGprsNsvc NetworkAlcatelGprsNsvcID "AGFR":aGprsPvc NetworkAlcatelGprsPvcID "AGVC":aGprsSgsnIpEndPoint NetworkAlcatelGprsSgsnIpEndPointID M.3100:circuitPack NetworkAlcatelGprsCircuitPackID M.3100:crossConnection NetworkAlcatelCrossConnectionID M.3100:equipmentHolder NetworkEquipmentHolderID


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

9153 OMC-R MOC Network Level Id type

NMD:networkElement NetworkAlcatelGprsNetworkElementID

Table 9: Network Level Id types for the MFS-NE Level MOCs


These types are defined in [ACIE-si] (ACIEMFSLevelASN1Module).


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

4. IMPORT/EXPORT MECHANISMS

4.1 Import mechanism

Triggers: An import session can only be triggered by a 9153 OMC-R operator.

Pre-conditions:

A set of files is transferred to an ACIE import directory. This transfer is of under the responsability of the entity which wants an import session to be triggered. It should not be performed if an ACIE lock file is present in that directory.

A (possibly empty) PRC is opened. This PRC is called the target PRC.

Inputs:

N.B.: There is no need to indicate the concerned level of the import session since only the Network Level is supported.

A sub-directory number, say i. The directory that contains the ACIE MOC files to be imported (called the concerned directory in what follows) is ACIE_NLimport_Diri.

Possibly an ACIE help file The ACIE Cell Identification mode

N.B.: It is set: to the mode preferred by the operator for import sessions (ARCI

mode by default) unless changed by the operator for that import session.

Outputs: None

Description: The target PRC modified according to the import files (target configuration) is ready to be applied/activated to a SC. N.B.: The reason why the changes described in the import files are not applied

directly to the operational configuration is to enable a check of the target configuration before the latter is actually applied on the fields.

N.B.: It is noteworthy that, for a PRC activated in MLU mode (see section 1.2.2), the attributes representing BSS/BSC telecom parameters of NML:rnlAlcatelBSC are not taken into account. In this case, before activation, it is necessary to split the PRC in two PRCs, one with these parameters and one without.

Scenario:

The different steps of the import mechanism are as follows:

(I1) Check for a concurrent import session If an ACIE lock file is present in the concerned directory, The lock body is read.


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

If the it contains does not correspond to a process that is still alive, the ACIE lock file is deleted.

An ACIE lock file is created in the concerned directory and the lock body is stored in it.

(I2) Overall checks of the set of import files The following checks are performed on the set of import files: Existence in the concerned directory Valid headers as regards the , ,

and parts (see section 2.6.2) Valid sub-headers: each attribute name listed should correspond to one of the

attributes present in the objects of the MOC for the considered version of the 9153 OMC-R.

If these checks fail, an error message is displayed to the 9153 OMC-R operator indicating the encountered problem and the import session is terminated.

(I3) For each of the ACIE MOC files (processed in the aforementioned order): N.B.: Only the MOI-related lines are considered hereafter. The other lines are

simply skipped.

(I3a) First pass (Load): Each line of the file is processed in turn as follows:

A syntactic check is performed on .

Sub-header/line consistency check: it is checked that the part of the line has the same number of elements as in the sub-header of the file.

It is checked that a value is supplied for and that this value is compliant/consistent with the associated ASN1 type, i.e.: it is consistent with the ACIE Cell Identification mode and syntactically

compliant with the associated ASN1 type; it is consistent with the associated Naming Tree. In particular, the cell field in AdjacencyInstanceIdentifier, Adjacency2gTo3gInstanceIdentifier, Adjacency2gToLteInstanceIdentifier, RnlBasebandTransceiverInstanceIdentifier, RnlFrequencyHoppingSystemInstanceIdentifier and the value of HoControlInstanceIdentifier and RnlPowerControlInstanceIdentifier shall correspond to the NetworkCellID (CellGlobalIdentity in CGI mode) of the parent cell MOI.

In CGI mode and for "NML":cell and "NML":externalOmcCell MOIs. If is equal to C, it is checked that

The value in the column corresponding to the "GSM 12.20":cellGlobalIdentity attribute obeys the CGI-related functional checks described below, i.e. the CGI sub-fields values are all supplied the (mcc,mnc) sub-field values are correct the CGI value is unique.

The value provided in is equal to that value


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

If is equal to M, it is checked that, if a value is supplied in the column corresponding to the "GSM 12.20":cellGlobalIdentity attribute, it is equal to that in .

In CGI mode and for "NML":externalOmc3gCell MOI, If is equal to C, it is checked that

The value in the column corresponding to the "C9ML":global3gCellIdentity attribute obeys the CGI-related functional checks described below, i.e. the CGI sub-fields values are all supplied the (mcc3g, mnc3g) sub-field values are correct. the CGI value is unique.


If is equal to M, it is checked that, if a value is supplied in the column corresponding to the "C9ML":global3gCellIdentity attribute, it is equal to that in .

In CGI mode and for "NML":externalOmcLteCell MOI, If is equal to C, it is checked that

The value in the column corresponding to the "CBML":eGlobalLteCellIdentity attribute obeys the CGI-related functional checks described below, i.e. the CGI sub-fields values are all supplied the (mccLte, mncLte) sub-field values are correct. the CGI value is unique.


If is equal to M, it is checked that, if a value is supplied in the column corresponding to the "CBML":eGlobalLteCellIdentity attribute, it is equal to that in .

The object instance corresponding to is loaded in the target PRC. More precisely:

If is equal to C and if the corresponding managed object instance is present neither in a

PRC nor in the SC if the associated functional checks described below succeed

N.B.: In CGI mode, the CGI-related checks for "NML":cell, "NML":externalOmcCell, "NML":externalOmc3gCell and "NML":externalOmcLteCell MOIs have already been performed at this stage and are, thus, useless.

the corresponding managed object instance is created with notably its naming attribute value set according to and the attributes set to the supplied values if any (when valid). N.B.: In CGI mode,

For "NML":cell, "NML":externalOmcCell and "NML":externalOmcLteCell MOIs, this implies to assign a NetworkCellID value that corresponds to the CGI value supplied in .


ED 11 RELEASED

9661m11re.doc 17/03/2010







Alcatel.

For "NML":externalOmc3gCell MOIs, this implies to assign a Network3GCellID value that corresponds to the CGI value supplied in .

For the MOIs named under a "NML":cell MOI, this implies to convert the CGI value(s) in into corresponding NetworkCellID value(s).

If is equal to M: If there are no implied object instances and the corresponding object

instance is present either in the target PRC or in the SC then: if the corresponding object instance is not present in the target

PRC, then it is copied from the SC; else nothing happens.

If there are implied sub-object instances: If the corresponding object instance is not present in the target

PRC, then it is copied from the SC along with its implied object instances

Else it is checked that all the implied object instances are present in the target PRC.

N.B.: The corresponding object instance denotes the MOI corresponding

to , possibly after CellGlobalIdentity and EGlobalLteCellIdentity to NetworkCellID conversion and Global3gCellIdentity to Network3gCellID conversion in CGI mode.

If the value supplied for the CMB:rnlCellType attribute of a given NML:cell MOI ( = M) is extendedOuter or extendedInner then: the corresponding COML:mateCellID is also copied from the

SC else if it is already in the target PRC, then nothing will happen

If is equal to D, the processing is identical to the one described above (i.e. case is equal to M), provided the associated functional checks described below succeed.

As a consequence, in a given import file and for a given object instance, there can be at most one line with an equal to C; there can be at most one one line with an equal to D; there may be several lines with an equal to M but these lines

must either apply to an object instance that is present in the SC or the target PRC (in case the latter is not empty when the import session is triggered) or follow a line with an equal to C.

(I3b) Second pass (Set): Each column corresponding to of each line of the file with equal to M is processed in turn as follows (excluding the column corresponding to the "GSM 12.20":cellGlobalIdentity, C9ML:global3gCellIdentity and "CBML":eGlobalLteCellIdentity attributes in CGI mode since already processed): If a value is provided for the attribute associated with the column and:

this value is compliant/consistent with the ASN1 type of the attribute; the corresponding attribute has the REPLACE property for the

concerned BSC release (specified in [ACIE-si]);


ED 11 RELEASED

9661m11re.

Date post:	24-Sep-2015
Category:	Documents
Upload:	hosyphuoc
View:	4 times
Download:	0 times

09661MAAAe11.pdf

Documents