Professional Documents
Culture Documents
11
RELEASED
9661m11re.doc
17/03/2010
1/1
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.
3.
3.1
3.2
3.2.1
3.2.2
3.2.3
Description......................................................................................................25
Corresponding ASN1 type definitions............................................................27
3.3
Description......................................................................................................32
Corresponding ASN1 type definitions............................................................32
Description......................................................................................................34
Corresponding ASN1 type definitions............................................................35
11
RELEASED
9661m11re.doc
17/03/2010
1/66
4.
4.2.2
4.2.3
4.2.4
4.2.5
5.
Introduction.....................................................................................................53
run_UnitaryExportSession.pl..........................................................................53
run_FileTransferAchieved.pl..........................................................................54
5.1
5.2
5.3.1.1
5.3.1.2
5.3.2
5.4
6.
11
04
03
02
01
ED
Update
Update
Update
Update
First issue
CHANGE NOTE
O&M System
O&M System
O&M System
O&M System
O&M System
APPRAISAL AUTHORITY
TD/MRC/OMD Spec
TD/MRC/OMD Spec
TD/MRC/OMD Spec
TD/MRC/OMD Spec
TD/MRC/OMD Spec
ORIGINATOR
11
RELEASED
9661m11re.doc
17/03/2010
2/66
HISTORY
Ed. 01
18/02/2008:
20/02/2009:
The document is updated following the new capability to export circuitPack MOIs.
This implies to export also equipmentHolder MOIs (parent MOIs for circuitPack
MOIs).
13/03/2009:
08/10/2009:
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
3/66
Ed. 11
21/12/2009:
REFERENCED DOCUMENTS
Standards
[ISO/IEC 8859-1]
[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]
[X.721]
[M.3100]
[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]
[GSM 12.20]
ED
11
RELEASED
9661m11re.doc
17/03/2010
4/66
[ANOIgdmo]
[ANOIcs-gene]
[ACIE-si]
[ACIE-siex]
[ACIE-map]
RELATED DOCUMENTS
[ANOIappli]
11
RELEASED
9661m11re.doc
17/03/2010
5/66
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:
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]
[ACIE-siex]
[ACIE-map]
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.
the 9153 OMC-R Configuration databases (ACDB) which store the 9153 OMC-R
Configuration data
perform an import session, i.e. import a set of ASCII files from the ACFR to the ACDB;
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
6/66
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 Databases
(ACDB)
Import
Export
data
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:
11
RELEASED
9661m11re.doc
17/03/2010
7/66
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
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,
11
RELEASED
9661m11re.doc
17/03/2010
8/66
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):
A cell reference which identifies uniquely a cell within those that have been created
by the same application.
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:
The CGI mode is supported neither for a Radio Network Level export session
requested by a NMC, not for the automatic export session.
11
RELEASED
9661m11re.doc
17/03/2010
9/66
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.
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]
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
10/66
Hexa Codes
Characters
41 to 5A
[A-Z]
5F
61 to 7A
[a-z]
C0 to FC
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
the
Dark grey (patterned or not) is used to indicate that the corresponding feature is
not supported or not concerned.
11
RELEASED
9661m11re.doc
17/03/2010
11/66
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 <ieCredit> (sub-)directories called the ACIE
export directories for that BSC-NE. These directories have a name of the form
ACIE_BSS<MECId>export_Dir<i>
11
RELEASED
9661m11re.doc
17/03/2010
12/66
where
<MECId>
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 <ieCredit> (sub-)directories called the ACIE
export directories for that MFS-NE. These directories have a name of the form
ACIE_MFS<NEId>export_Dir<i>
where <NEId> 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.
11
RELEASED
9661m11re.doc
17/03/2010
13/66
ACIE
ACIE_NLimport_Dir1
ACIE_NLimport_Diri
ACIE_NLimport_Dirc
ACIE_NLexport_Dir1
ACIE_NLexport_Diri
ACIE_NLexport_Dirc
ACIE_BLexport
ACIE_BSS1export_Dir1
ACIE_BSS1export_Diri
ACIE_BSS1export_Dirc
ACIE_BSSnexport_Dir1
ACIE_BSSnexport_Diri
ACIE_BSSnexport_Dirc
ACIE_MLexport
ACIE_MFS1export_Dir1
ACIE_MFS1export_Diri
ACIE_MFS1export_Dirc
ACIE_MFSnexport_Dir1
ACIE_MFSnexport_Diri
ACIE_MFSnexport_Dirc
11
RELEASED
9661m11re.doc
17/03/2010
14/66
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.
11
RELEASED
9661m11re.doc
17/03/2010
15/66
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.
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.
N.B.:
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.
ED
11
RELEASED
9661m11re.doc
17/03/2010
16/66
<header>
[<MOIs-related part>]
in which <MOIs-related part> is present only when there is at least one MOI of the
associated MOC and has the following form:
<sub-header>
<body>
<header>, <sub-header> and <body> are described in the following sections.
N.B.:
As regards <header> and <sub-header>, the strings mentioned in the
following sections are not enclosed between " characters, contrary to strings
in <body>.
11
RELEASED
9661m11re.doc
17/03/2010
17/66
<n> is an integer
<date> indicates the (local) date at which the file was created.
It is of the form YYYY-MM-DD.
<hour> indicates the (local) time at which the file was created.
It is of the form hh:mm:ss.
<9153OMCRInstance> 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.
<from/to> is:
a character string that indicates which entity has created the file for an import file.
<sessionName> is a character string that indicates:
11
RELEASED
9661m11re.doc
17/03/2010
18/66
the first (lower case) letter is replaced by the corresponding upper case letter
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.
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.
It is the responsability of the entity that has created the import file to guarantee this unicity.
9153 OMC-R Configuration Import/Export interface
ED
11 RELEASED
9661m11re.doc
17/03/2010
19/66
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.
<attributeValueList> has the form:
*
[;[<attributeValueX>]]
in which <attributeValueX>
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.
N.B.:
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
INTEGER
INTEGER {
int1 (0),
int2 (1),
.....
intn (<n>)
}
ENUMERATED {
enum1 (0),
enum2 (1),
.....
enumn (<n>)
}
REAL
<n>
int1 | int2 | ... | intn
123
degraded
locked
Symbolic name of
the
enumerated
value in which each
"-" character, if any,
is replaced by "_"
C
double
precision
floating point value as
3.4E3
C double precision
floating point
11
RELEASED
9661m11re.doc
17/03/2010
20/66
defined
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
9899]
BIT STRING or
OCTET STRING or
BIT STRING {
bitstr1
(0),
bitstr2
(1),
.....
bitstrn
(<n>)
}
NULL
character string type
(e.g.
PrintableString,
GraphicString)
GeneralizedTime
OBJECT IDENTIFIER
in
[ISO/IEC
'[0-9A-F] 'H
'3FE2EBAD'H
BIT STRING or
OCTET
STRING
value
in
hexadecimal form
NULL
*
[<char>]
where <char> is any
character allowed for the
character string type
possibly
translated
according
to
the
character translation rule
mentioned in section 1.3.
First
form
of
a
GeneralizedTime value
defined in [ASN1]
<MOINetworkLevelIdValu
e>
NULL
BSS
keyword NULL
(possibly converted)
character
string
value
19951106210627.3
(6th
Nov
1995,
21:06:27.3 local time.)
{bsc{100}, btsRdn 1}
GeneralizedTime
value, local time
form.
See section 2.6.4.2.
<TValRep> (resp. <TnValRep>) denotes the representation of a value of type <T> (resp.
<Tn>).
N.B.:
Tags are not mentioned hereafter since they do not influence the representation of the
value.
SEQUENCE OF<T>
{[<TValRep>]
{12, 13, 14}
List of values of type
*
(value of type SET OF <T> separated with
or SET OF <T>
[,<TValRep>] ]}
INTEGER)
, and enclosed
between { and }.
SEQUENCE {
{ [f1 <T1ValRep>]
{hreqave
16} List of field names
f1 <T1>,
represents a value of and values of the
[, f2 <T2ValRep>]
f2 <T2> OPTIONAL, ...
type
associated
type
HoAveragingDistPara
separated with ,
...
[, fn <TnValRep>]
m (from [GSM 12.20]). and
enclosed
fn <Tn>
}
between { and }.
}
If
a
field
is
or SET {
OPTIONAL and is
f1 <T1>,
not present, it does
f2 <T2>,
not appear in the
...
list.
fn <Tn>
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 <ieMode> =
"M") or the default
11
RELEASED
9661m11re.doc
17/03/2010
21/66
CHOICE {
alt1 [1] <T1>,
alt2 [2] <T2>,
...
altn [n] <Tn>
}
alt1:<T1ValRep>
alt2:<T2ValRep>
...
altn:<TnValRep>
noUse:NULL
represents a value of
type FrequencyUsage
(from [GSM 12.20]) for
which
the
noUse
alternative is relevant.
11
RELEASED
9661m11re.doc
17/03/2010
22/66
whether it is allowed to create (C), delete(D) or modify the attribute values of (M) these
object instances.
9153 OMC-R MOC
NML:adjacency
GSM 12.20:
adjacentCellHandOver
GSM 12.20:
adjacentCellReselection
NML:adjacency2gTo
3g
none
NML:adjacency2gTo
Lte
none
NML:cell
GSM 12.20:bts
NML:
externalOmc3gCell
none
NML:
externalOmcCell
GSM 12.20:bts
NML:
externalOmcLteCell
none
NML:hoControl
GSM 12.20:
handoverControlGSM0508
NML:rnlAlcatelMFS
None
Short description
C D M
(1)
11
RELEASED
9661m11re.doc
17/03/2010
23/66
GSM 12.20:bssFunction
GSM 12.20:bsc
NML:rnlAlcatelSector
GSM 12.20:bts
NML:
rnlAlcatelSiteManager
GSM 12.20:btsSiteManager
NML:rnlAlcatelTcRac
kManager
"GSM 12.20":
gsmManagedFunction
NML:rnlBasebandTra
nsceiver
Merge of:
GSM
12.20:
basebandTransceiver
GSM 12.20: channel
NML:rnlFrequencyHo
ppingSystem
GSM 12.20:
frequencyHoppingSystem
NML:rnlPowerControl
GSM 12.20:
powerControlGSM0508
NML:subNetwork
GSM 12.00:plmnNetwork
C D M
Short description
Alcatel MFS (NE for GPRS
handling).
Represents
the
Radio
Network Level view of an
Alcatel BSC.
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.
Represents
the
Radio
Network Level view of an
Alcatel BTS Site Manager.
Represents
the
Radio
Network Level view of an
Alcatel TC Rack Manager.
Represents
the
Radio
Network Level view of an
Alcatel
Baseband
Transceiver.
Represents a set of radio
frequency channels used in a
specific frequency hopping
sequence.
Supports the management of
parameters for the power
control algorithm used by
Alcatel.
Represents the radio network
managed by the 9153 OMCR.
(1)
NML:
externalOmc3gCell
NML:
externalOmcLteCell
NML:
externalOmcCell
"NML":
rnlAlcatelMFS
NML:
rnlAlcatelBSC
11
RELEASED
9661m11re.doc
17/03/2010
24/66
NML:
rnlAlcatelTcRackManager
NML:
rnlAlcatelSiteManager
NML:
rnlAlcatelSector
NML:cell
NML:
adjacency
NML:
hoControl
NML:
adjacency2gTo3g
NML:
rnlBasebandTransceiver
NML:
rnlFrequencyHoppingSystem
NML:
rnlPowerControl
NML:
adjacency2gToLte
"NML":adjacency
"NML":adjacency2gTo3g
"NML":adjacency2gToLte
"NML":cell
"NML":externalOmcCell
"NML":externalOmc3gCell
"NML":externalOmcLteCell
"NML":hoControl
"NML":rnlBasebandTransceiver
"NML":rnlFrequencySystem
"NML":rnlPowerControl.
N.B.:
11
RELEASED
9661m11re.doc
17/03/2010
25/66
NML:adjacency2gTo3g
NML:adjacency2gToLte
NML:cell
NML:externalOmcCell
NML:externalOmc3gCell
NML:externalOmcLteCell
NML:hoControl
ED
11
RELEASED
9661m11re.doc
17/03/2010
26/66
Comments
else:
The value corresponds to the
NetworkCellID value of the
containing cell
NetworkCellID
NML:rnlAlcatelBSC
NML:rnlAlcatelMFS
NML:rnlAlcatelSector
NML:rnlAlcatelSiteManager
NetworkBSCID
NetworkMFSID
NetworkSectorID
NetworkSiteManagerID
NML:rnlAlcatelTcRackManage
r
NML:rnlBasebandTransceiver
NetworkTcRackManag
erID
In CGI mode:
CGIBasedBbtID
else:
NetworkBbtID
In CGI mode:
NML:rnlFrequencyHoppingSys
tem
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.
CGIBasedFhsID
else:
NetworkFhsID
NML:rnlPowerControl
CellGlobalIdentity
NetworkCellID
NML:subNetwork
INTEGER
In CGI mode:
The value corresponds to the
CellGlobalIdentity value of
the containing cell
else:
The value corresponds to the
NetworkCellID value of the
containing cell
RDN of the corresponding
MOI
11
RELEASED
9661m11re.doc
17/03/2010
27/66
EML:alcatelAbisChainRingCoordin
ator
Closest standard
MOC(s)
Merge of:
M.3100:trailTerminatio
nPointBidirectional
M.3100:connectionTer
minationPointBidirection
al
none
EML:alcatelAbisChainRing
none
EML:alcatelBasebandTransceiver
EML:alcatelBssFunction
Merge of:
GSM
12.20:
basebandTransceiver
GSM 12.20: channel
Merge of:
GSM
12.20:bssFunction
GSM 12.20:bsc
GSM 12.00":bssFunction
EML:alcatelBts-Sector
GSM 12.20:bts
EML:alcatelBtsSiteManager
GSM 12.20:
btsSiteManager
EML:alcatelCircuitPack
M.3100:circuitPack
EML:alcatelConnectionR1
M.3100:connectionR1
EML:alcatelFunction
none
EML:alcatelBsc
Short description
Represents a 2Mb termination
point of a BSC, a BTS
equipment or a transcoder.
11
RELEASED
9661m11re.doc
17/03/2010
28/66
Closest standard
MOC(s)
Short description
EML:alcatelFunctionCoordinator
none
EML:alcatelIPCoordinator
none
EML:alcatelIPLink
none
EML:alcatelIpPeer
none
EML:alcatelLapdLink
GSM 12.20:lapdLink
EML:alcatelManagedElement
M.3100:
managedElement
EML:alcatelManagedElementCom
plex
EML:alcatelOperatingSoftwareUnit
M.3100:managedEleme
ntComplex
GSM 12.20:
operatingSoftwareUnit
EML:alcatelPeerCoordinator
none
EML:alcatelRadioCarrier
GSM 12.20:radioCarrier
EML:alcatelReplaceableSoftware
Unit
GSM 12.20:
replaceableSoftwareUnit
EML:alcatelSignLinkN7
Q.751.1:signLinkTp
EML:alcatelSignLinkSetTp
Q.751.1:signLinkSetTp
EML:alcatelTcRackManager
E6ML:alcatelX25Coordinator
"GSM 12.20":
gsmManagedFunction
none
E6ML:alcatelX25Link
none
M.3100:equipmentHolder
M.3100:
equipmentHolder
GSM 12.20:
executableSoftwareUnit
GSM 12.20:
executableSoftwareUnit
BSC-NE
This MOC models all the
functions related to the same
"EML":alcatelManagedElement
MOI
This MOC is introduced to
optimize requests concerning
EML:alcatelIPLink
object
instances.
Represents the IP link between
the 9153 OMC-R and the BSCNE
Represents the IP association
between the BSC-NE and
another NE.
Represents a logical LapD
connection on a signalling link
on the Abis interface.
Represents
an
equipment
composing a BSC-NE, i.e. either
a BSC, a BTS or a Transcoder
equipment.
Models all aspects (functionality,
equipment, ...) of a BSC-NE
Represents
an
operating
software resource in the Alcatel
BSC-NE.
This MOC is introduced to
optimize requests concerning
EML:alcatelIpPeer
object
instances.
Contains manageable properties
of a radio carrier (notably
hardware ones)
Represents a unit of software
that needs to be separately
identifiable and/or replaceable in
the Alcatel BSC-NE.
Represents the termination of a
SS No.7 signalling link between
the BSC-NE and the MSC.
Represents a SS No.7 signalling
link set termination point.
Represents
the
supervising
BSSIM view of an TC Rack.
This MOC is introduced to
optimize requests concerning
EML:alcatelX25Link
object
instances.
Represents
the
X25
link
between the 9153 OMC-R and
the BSC-NE
Represents either a shelf or a
rack in the BSC-NE.
Represents a unit of software
that is separately identifiable and
11
RELEASED
9661m11re.doc
17/03/2010
29/66
Q.751.1:mtpSignPoint
Closest standard
MOC(s)
Short description
Q.751.1:mtpSignPoint
11
RELEASED
9661m11re.doc
17/03/2010
30/66
"EML":
alcatelManagedElement
"EML":
alcatelAbisChainRingCoordinator
E6ML:
alcatelX25Coordinator
"EML":
alcatelAbisChainRing
E6ML:
alcatelX25Link
"Q.751.1":
mtpSignPoint
"EML ":
alcatelSignLinkSetTp
"EML":alcatelFunctionCoordinator
"EML":
alcatelSignLinkN7
"EML":alcatelFunction
"M.3100":
equipmentHolder (Rack)
EML:
alcatelConnectionR1
"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":
alcatelBasebandTransceiver
EML:
alcatelRadioCarrier
SW:alcatelReplaceableSoftwareUnit
"EML":
alcatelIPLink
"EML":
alcatelPeerCoordinator
"EML":
alcatelIpPeer
GSM 12.20:executableSoftwareUnit
11
RELEASED
9661m11re.doc
17/03/2010
31/66
N.B.:
EML:alcatel2MbTTP
EML:alcatelAbisChainRing
EML:alcatelAbisChainRingCoordinator
EML:alcatelBasebandTransceiver
EML:alcatelBsc
EML:alcatelBssFunction
EML:alcatelBts-Sector
EML:alcatelBtsSiteManager
EML:alcatelCircuitPack
EML:alcatelConnectionR1
EML:alcatelFunction
EML:alcatelFunctionCoordinator
EML:alcatelIPCoordinator
EML:alcatelIPLink
EML:alcatelIpPeer
EML:alcatelLapdLink
EML:alcatelManagedElement
EML:alcatelManagedElementComplex
EML:alcatelOperatingSoftwareUnit
EML:alcatelRadioCarrier
EML:alcatelPeerCoordinator
EML:alcatelReplaceableSoftwareUnit
EML:alcatelSignLinkN7
EML:alcatelSignLinkSetTp
EML:alcatelTcRackManager
E6ML:alcatelX25Coordinator
E6ML:alcatelX25Link
M.3100:equipmentHolder
GSM 12.20:executableSoftwareUnit
Q.751.1:mtpSignPoint
NetworkAlcatel2MbTTPID
NetworkAlcatelAbisChainRingID
NetworkAlcatelAbisChainRingCoordinatorID
NetworkAlcatelBasebandTransceiverID
NetworkAlcatelBscID
NetworkAlcatelBssFunctionID
NetworkAlcatelBtsSectorID
NetworkAlcatelBtsSiteManagerID
NetworkAlcatelCircuitPackID
NetworkAlcatelConnectionR1ID
NetworkAlcatelFunction
NetworkAlcatelFunctionCoordinator
NetworkAlcatelIPCoordinatorID
NetworkAlcatelIPLinkID
NetworkAlcatelIpPeerID
NetworkAlcatelLapdLinkID
NetworkAlcatelManagedElementID
NetworkAlcatelMECID
NetworkAlcatelOSUID
NetworkAlcatelRadioCarrierID
NetworkAlcatelPeerCoordinatorID
NetworkAlcatelRSUID
NetworkAlcatelSignLinkN7ID
NetworkAlcatelSignLinkSetTpID
NetworkAlcatelTcRackManagerID
NetworkAlcatelX25CoordinatorID
NetworkAlcatelX25LinkID
NetworkEquipmentHolderID
NetworkESUID
NetworkMtpSignPointID
11
RELEASED
9661m11re.doc
17/03/2010
32/66
The following table lists these MOCs, indicating, for each MOC:
Closest standard
MOC(s)
None
Short description
"AGFR":aGprsBearerChannel
None
"AMFSME":aGprsFabric
None
"AATER":aGprsIpSigLink
None
"AGVC":aGprsNse
None
"AGVC":aGprsNsvc
None
"AGFR":aGprsPvc
None
"AGVC":aGprsSgsnIpEndPoint
None
M.3100:circuitPack
M.3100:circuitPack
M.3100:crossConnection
M.3100:crossConnection
M.3100:equipmentHolder
M.3100:equipmentHolde
r
11
RELEASED
9661m11re.doc
17/03/2010
33/66
Closest standard
MOC(s)
None
Short description
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.
"AMFSME":
aGprs2MbTTP
"M.3100":
equipmentHolder (Rack)
"AGFR":
aGprsBearerChannel
"M.3100":
equipmentHolder (Shelf)
"AGFR":
aGprsPvc
"M.3100":
circuitPack
"AATER":
aGprsIpSigLink
"AGVC":
aGprsNse
"AGVC":
aGprsSgsnIpEndPoint
"AGVC":
aGprsNsvc
"AMFSME":
aGprsFabric
"M.3100":
crossConnection
N.B.:
"AMFSME":aGprs2MbTTP
"AGFR":aGprsBearerChannel
"AMFSME":aGprsFabric
"AATER": aGprsIpSigLink
"AGVC":aGprsNse
"AGVC":aGprsNsvc
"AGFR":aGprsPvc
"AGVC":aGprsSgsnIpEndPoint
M.3100:circuitPack
M.3100:crossConnection
M.3100:equipmentHolder
NetworkAlcatelGprs2MbTTPID
NetworkAlcatelGprsBearerChannelID
NetworkAlcatelGprsFabricID
NetworkAlcatelGprsIpSigLinkID
NetworkAlcatelGprsNseID
NetworkAlcatelGprsNsvcID
NetworkAlcatelGprsPvcID
NetworkAlcatelGprsSgsnIpEndPointID
NetworkAlcatelGprsCircuitPackID
NetworkAlcatelCrossConnectionID
NetworkEquipmentHolderID
11
RELEASED
9661m11re.doc
17/03/2010
34/66
NMD:networkElement
11
RELEASED
9661m11re.doc
17/03/2010
35/66
4. IMPORT/EXPORT MECHANISMS
4.1 Import mechanism
Triggers:
An import session can only be triggered by a 9153 OMC-R operator.
Pre-conditions:
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:
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,
11
RELEASED
9661m11re.doc
17/03/2010
36/66
If the <processId> 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:
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:
11
RELEASED
9661m11re.doc
17/03/2010
37/66
The
value
in
the
column
corresponding
to
the
"C9ML":global3gCellIdentity attribute obeys the CGI-related
functional checks described below, i.e.
The
value
in
the
column
corresponding
to
the
"CBML":eGlobalLteCellIdentity attribute obeys the CGI-related
functional checks described below, i.e.
For
"NML":cell,
"NML":externalOmcCell
and
"NML":externalOmcLteCell MOIs, this implies to assign a
NetworkCellID value that corresponds to the CGI value
supplied in <MOINetworkLevelIdValue>.
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
38/66
If <ieMode> is equal to M:
there may be several lines with an <ieMode> 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 <ieMode> equal to C.
(I3b)
If a value is provided for the attribute associated with the column and:
ED
11
RELEASED
9661m11re.doc
17/03/2010
39/66
N.B.:
the "NML":cell MOI to which sector1 was mapped, say cell1, to become
unmapped, i.e. the "NML":rnlSupportingSector attribute for cell1 becomes
equal to NULL (notAvailable alternative).
Since this implicit unmapping is peculiar, a corresponding warning message
shall be issued.
Functional checks:
The overall strategy is to limit the number of functional checks as much as possible and
notably not to duplicate the checks that are performed at activation time. Broadly
speaking, the checks performed at the ACIE interface are mainly meant to avoid:
Title:
Mandatory values check for creation
<ieMode>: "C"
MOIs:
See first column below
Description:
The table below indicates, for the MOIs in the first column, the associated
attributes for which a value shall be mandatorily supplied in a creation
request.
MOIs
Attributes
"NML":adjacency
"NML":rnlAdjacencyType
"NML":adjacency2gTo3g
"NML":rnlAdjacencyType
"NML":adjacency2gToLte
"NML":rnlAdjacencyType
"NML":cell
"GSM 12.20":cellGlobalIdentity.lai.mcc
"GSM 12.20":cellGlobalIdentity.lai.mnc
"GSM 12.20":cellGlobalIdentity.lai.lac
"GSM 12.20":cellGlobalIdentity.ci
"NML":externalOmcCell
"GSM 12.20":bCCHFrequency
"GSM 12.20":cellGlobalIdentity.lai.mcc
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
40/66
"NML":externalOmc3gCell
"NML":externalOmcLteCell
ED
"GSM 12.20":cellGlobalIdentity.lai.mnc
"GSM 12.20":cellGlobalIdentity.lai.lac
"GSM 12.20":cellGlobalIdentity.ci
"COML":frequencyRange
"CMB":rnlCellType
C9ML:ci3g
C9ML:fDD_ARFCN
"C9ML":global3gCellIdentity.mcc3g
"C9ML":global3gCellIdentity.mnc3g
"C9ML":global3gCellIdentity.local3gCi
C9ML:lac3g
CBML:rat3g
C9ML:rncId
"CBML":eGlobalLteCellIdentity.ciLte
"CBML":eGlobalLteCellIdentity.mccLte
"CBML":eGlobalLteCellIdentity.mncLte
"CBML":eUARFCN
"CBML":ratLte
Title:
cellGlobalIdentity unicity check
<ieMode>: "C", "M"
MOIs:
"NML":cell and "NML":externalOmcCell MOIs
Description:
For "NML":cell MOIs, a creation or modification request is only allowed if the
value supplied for the "GSM 12.20":cellGlobalIdentity attribute is such that
there is no existing "NML":cell MOI with the same value for this attribute in the
PRC (when in the SC, the problem is only detected at activation time).
The same check applies to "NML":externalOmcCell MOIs.
Title:
global3gCellIdentity unicity check
<ieMode>: "C", "M"
MOIs:
"NML":externalOmc3gCell MOI
Description:
For "NML":externalOmc3gCell MOIs, a creation or modification request is only
allowed if the value supplied for the "C9ML":global3gCellIdentity attribute is
such that there is no existing "NML":externalOmc3gCell MOI with the same
value for this attribute in the PRC (when in the SC, the problem is only
detected at activation time).
Title:
eGlobalLteCellIdentity unicity check
<ieMode>: "C", "M"
MOIs:
"NML":externalOmcLteCell MOI
Description:
For "NML":externalOmcLteCell MOIs, a creation or modification request is
only allowed if the value supplied for the "CBML":eGlobalLteCellIdentity
attribute is such that there is no existing "NML":externalOmcLteCell MOI with
the same value for this attribute in the PRC (when in the SC, the problem is
only detected at activation time).
Title:
<ieMode>:
MOIs:
11
41/66
Description:
For "NML":externalOmc3gCell MOIs, a creation or modification request is only
allowed if the values supplied for the "C9ML":global3gCellIdentity.mcc3g,
"C9ML":global3gCellIdentity.mnc3g, "C9ML":rncId and "C9ML":ci3g attributes
are such that there is no existing "NML":externalOmc3gCell MOI with the
same values for these attributes in the PRC (when in the SC, the problem is
only detected at activation time).
Title:
MNC/MCC check for cell MOIs
<ieMode>: "C", "M"
MOIs:
"NML":cell
Description:
The following couple of sub-field values:
("GSM 12.20":cellGlobalIdentity.lai.mcc,"GSM 12.20":cellGlobalIdentity.lai
.mnc)
shall be equal to one of the couples of attribute values of the
"NML":subNetwork MOI (defined at the 9153 OMC-R installation time):
("N7ML":ownMCC-x, "N7ML":ownMNC-x) with x {1,2,3,4}
N.B.:
For x {2,3,4}, this check is performed only if the corresponding
couple is significant, i.e. when it is different from:
Title:
MNC/MCC check for "NML":externalOmcCell MOIs
<ieMode>: "C", "M"
MOIs:
"NML":externalOmcCell MOIs
Description:
The following couple of sub-field values:
("GSM 12.20":cellGlobalIdentity.lai.mcc,"GSM 12.20":cellGlobalIdentity.lai
.mnc)
shall be equal to one of the couples of attribute values of the
"NML":subNetwork MOI (defined at the 9153 OMC-R installation time):
Title:
MNC_3G/MCC_3G check for "NML":externalOmc3gCell MOIs
<ieMode>: "C", "M"
MOIs:
"NML":externalOmc3gCell MOIs
Description:
The following couple of sub-field values:
("C9ML":global3gCellIdentity.mcc3g,"C9ML":global3gCellIdentity.mnc3g)
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
42/66
Title:
MNC_LTE/MCC_LTE check for "NML":externalOmcLteCell MOIs
<ieMode>: "C", "M"
MOIs:
"NML":externalOmcLteCell MOIs
Description:
The following couple of sub-field values:
"CBML":eGlobalLteCellIdentity.mccLte,"CBML":eGlobalLteCellIdentity.mn
cLte)
shall be equal to one of the couples of attribute values of the
"NML":subNetwork MOI (defined at the 9153 OMC-R installation time):
Title:
cellsToBeDeleted check
<ieMode>: "C", "D", "M"
MOIs:
"NML":cell MOIs
Description:
For "NML":cell MOIs, a creation/deletion/modification request shall not
concern a cell that is identified by the "NML":cellsToBeDeleted attribute of the
"NML":subNetwork MOI.
Title:
change cellType check
<ieMode>: "M"
MOIs:
"NML":cell and "NML":externalOmcCell MOIs
Description:
For a "NML":cell or "NML":externalOmcCell MOIs, a modification request
concerning the "CMB":rnlCellType attribute value is only allowed for the
transitions from a current value (line) to a requested value (column) marked
with "" in the table below:
requested
single
concentric
umbrella
micro
umbrella
mini
extended
extended
other
11
RELEASED
9661m11re.doc
17/03/2010
43/66
\
currentl
single
concentric
umbrella
micro
umbrella
Concentric
mini
extended
Inner
extended
Outer
other
Concentric
Outer
Title:
<ieMode>:
MOIs:
N.B.:
Inner
Description:
gsm-dcs
e-gsm-dcs
(from B7.1 onwards)
other values
where '' means the values for the two attributes are compatible (and
therefore possible); otherwise the cell is filled in with dark grey.
Title:
max adjacency per cell check
<ieMode>: "C"
MOIs:
"NML":adjacency MOIs
Description:
A request to create a "NML":adjacency MOI is only allowed if it does not
cause the number of such MOIs for the parent "NML":cell MOI to exceed 64.
Title:
max 2g-3g adjacency per cell check
<ieMode>: "C"
MOIs:
"NML":adjacency2gTo3g MOIs
Description:
A request to create a "NML":adjacency2gTo3g MOI is only allowed if it does
not cause the number of such MOIs for the parent "NML":cell MOI to exceed
8.
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
44/66
Title:
max 2g-Lte adjacency per cell check
<ieMode>: "C"
MOIs:
"NML":adjacency2gToLte MOIs
Description:
A request to create a "NML":adjacency2gToLte MOI is only allowed if it does
not cause the number of such MOIs for the parent "NML":cell MOI to exceed
20.
Title:
max rnlBBT check
<ieMode>: "C"
MOIs:
"NML":rnlBasebandTransceiver MOIs
Description:
A request to create a "NML":rnlBasebandTransceiver MOI is only allowed if it
does not cause the number of such MOIs to exceed 16.
Title:
NetworkFhsID.fhsRdn check
<ieMode>: "C"
MOIs:
"NML":rnlFrequencyHoppingSystem MOIs
Description:
A request to create a "NML":rnlFrequencyHoppingSystem MOI is only allowed
if the value supplied for <MOINetworkLevelIdValue> (second column), fhsRdn
field lies in the range [1..16].
Title:
mobileAllocation versus cellAllocation check
<ieMode>: "C", "M"
MOIs:
"NML":rnlFrequencyHoppingSystem MOIs
Description:
For "NML":rnlFrequencyHoppingSystem MOIs, all the radio frequencies
(ARFCNs) specified in the "A12.20":mobileAllocation attribute must belong to
the set of allowed radio frequency values specified by the
"GSM 12.20":cellAllocation attribute of the parent "NML":cell MOI.
with
the
ACIE
Step
Comments
Fatal errors
import
The
import
directory
I1
ACIE_NLimport_Diri has not been
created as specified in section 2.1.
The administrator of the 9153 OMCR instance shall be contacted.
In ACIE_NLimport_Diri, a lock file is
I1
present and <processId> in it
corresponds to a process that is still
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
45/66
Type of problem
Step
Comments
alive.
No ACIE import files can be found in
the
import
directory
ACIE_NLimport_Diri.
Problems with an ACIE import file
An attempt to read an ACIE import
I2
file has failed
Headers not valid or not consistent
A header in one of the ACIE import
I2
disregarding <InfoModelVersion>
file does not comply with the rules
stated in section 2.6.2 (disregarding
<InfoModelVersion>) or the headers
are not consistent
Sub-header not valid
A sub-header in one of the ACIE
I2
import file does not comply with the
rules stated in section 1.3
Line-related errors
Inconsistent <InfoModelVersion>
<InfoModelVersion> mentioned in
I2
the header is not consistent with the
Information Model version of the
9153 OMC-R instance on which the
parsed file is imported.
Wrong <ieMode>
I3a <ieMode> is:
not equal to either C, M or D,
or not consistent with the set of
operations allowed for object
instances of the MOC associated
with the parsed file
Line inconsistent with sub-header
I3a The <attributeValueList> part of the
line has not the same number of
elements as <attributeNameList> in
the sub-header of the parsed file
Missing
or
invalid I3a <MOINetworkLevelIdValue> is not
<MOINetworkLevelIdValue>
supplied or not compliant/consistent
with the Network Level Id type
corresponding to the ACIE Cell
Identification mode for the MOC
associated with the parsed file
<MOINetworkLevelIdValue> and CGI I3a In CGI mode, for "NML":cell and
values not equal (in CGI Cell
"NML":externalOmcCell MOIs
Identification mode)
<ieMode> is equal to C and
<MOINetworkLevelIdValue> is not
equal to the value in the column
corresponding to the "GSM
12.20":cellGlobalIdentity attribute
<ieMode> is equal to D, a value
is supplied in the column
corresponding to the "GSM
12.20":cellGlobalIdentity attribute
which
is
not
equal
to
<MOINetworkLevelIdValue>
In
CGI
mode,
for
"NML":externalOmc3gCell MOIs
I2
11
RELEASED
9661m11re.doc
17/03/2010
46/66
Type of problem
Step
I3a
I3a
I3a
I3a
I3a
Comments
<ieMode> is equal to C and
<MOINetworkLevelIdValue> is not
equal to the value in the column
corresponding
to
the
"C9ML":global3gCellIdentity
attribute
<ieMode> is equal to D, a value
is supplied in the column
corresponding
to
the
"C9ML":global3gCellIdentity
attribute which is not equal to
<MOINetworkLevelIdValue>
In CGI mode and for "NML":cell and
"NML":externalOmcCell
MOIs,
<ieMode> is equal to M and a valid
value is supplied in the column
corresponding
to
the
"GSM
12.20":cellGlobalIdentity attribute
In
CGI
mode
and
for
"NML":externalOmc3gCell
MOIs,
<ieMode> is equal to M and a valid
value is supplied in the column
corresponding
to
the
"C9ML":global3gCellIdentity
attribute
<ieMode> is equal to C and the
MOI
corresponding
to
<MOINetworkLevelIdValue> already
exists either in a PRC or in the SC.
N.B.: The SC and the set of existing
PRCs shall be consistent with
respect to the object instances
that are created in these
domains.
<ieMode> is equal to M or D and:
there are no implied object
instances
the corresponding object instance
is present neither in the target
PRC nor in the SC
<ieMode> is equal to M or D and:
there are implied sub-object
instances
at least one of these implied subobject instances is not present in
the target PRC
No value is indicated for at least one
of the attributes that are mandatory
for creating the corresponding
Managed Object Instance or the
value is invalid
11
RELEASED
9661m11re.doc
17/03/2010
47/66
Comments
At least one of the functional checks
has
failed
for
deleting
the
corresponding Managed Object
Instance
ARCI
mode,
when
In ARCI mode and <ApplicationID> I3a In
equal to 9153 OMC-R the <ieMode>
<ApplicationID> is equal to 9153
can not be equal to C.
OMC-R, then any object instance
can not be created.
Column-related errors
An attribute value cannot be modified
I3b <ieMode> is equal to M, a value is
supplied for an attribute and:
this
value
is
not
compliant/consistent
with
the
ASN1 type of the attribute
or the corresponding attribute has
not the REPLACE property (i.e. it
is read-only) for the concerned
BSC release
a functional check concerning this
value has failed.
Type of problem
Invalid attribute value(s) to delete a
Managed Object Instance
Step
I3a
If this error does not cause the total number of errors to exceed
<maxDisplayedErrors>, an appropriate error message is displayed indicating
notably the file, the line at which the problem has occurred and (in case of a
column-related error) the concerned attribute.
Otherwise, a last error message is displayed indicating that the max number of
displayed errors is exceeded.
For a line-related error, the line is skipped and, for a column-related error, the
column is skipped.
N.B.:
Whenever a problem is encountered but is automatically solved somehow
(e.g. by taking advantage of some default values), a warning message could
be issued provided the same operation performed by an 9153 OMC-R
operator (i.e. via the 9153 OMC-R HMI) also causes a warning to be issued.
11
RELEASED
9661m11re.doc
17/03/2010
48/66
It 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.
Pre-conditions:
None.
Inputs:
Export Scope: either at Network Level or for a given BSC-NE or for a given MFSNE
or the SC.
By default, the export domain is the SC.
for an export session at Network Level, one ACIE MOC file per Network Level
MOC defined in section 3.1.
for an export session at BSC-NE Level, one ACIE MOC file per BSC-NE Level
MOC defined in section 3.2.
for an export session at MFS-NE Level, one ACIE MOC file per MFS-NE Level
MOC defined in section 3.3.
If an error arises, either no ACIE MOC files or only a subset of these files are created.
Scenario:
General Mechanism
The different steps of the export general mechanism are as follows:
(E1) Check the concerned directory
It is checked that:
If the <processId> it contains does not correspond to a process that is still alive,
the ACIE lock file is deleted.
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
49/66
An ACIE lock file is created in the concerned directory and the lock body is stored in it.
(E3) For an export session at Network Level or BSC-NE Level, a frozen snapshot of the part
of the 9153 OMC-R Configuration database containing the configuration data to be
exported is produced (so as to ensure that the exported data is consistent).
For an export session at MFS-NE level, the configuration data to be exported is
retrieved from the MFS-NE with a special care with respect to the consistency of the
retrieved data.
From an external viewpoint, this retrieval can be viewed as a M-GET request of the
following form:
BOC:
"M.3100":managedElement
BOI
"M.3100":managedElement MOI
corresponding to the MFS-NE supplied as input
scope:
baseToNthLevel = 3
filter:
equal(objectClass,<concernedMFSNEMoc_1>)
or equal(objectClass, <concernedMFSNEMoc_2>)
...
or equal(objectClass, <concernedMFSNEMoc_n>)
where <concernedMFSNEMoc_n> denotes in turn each of the concerned
MFS-NE Level MOCs (see section 3.3) except "NMD":networkElement
which
is
replaced
by
its
MFS-NE
counterpart,
namely
"M.3100":managedElement.
(E4) For each of the MOC concerned by the export session (i.e. the Network Level ones
defined in section 3.1, the BSC-NE Level ones defined in section 3.2 or the MFS-NE
Level ones defined in section 3.3), a corresponding ACIE MOC file is created and filled
up by translating the configuration data associated with all the existing object instances
of the MOC to the ACIE MOC file format and structure.
N.B.:
In CGI mode, this implies to convert all the NetworkCellID values to the
corresponding CGI values.
(E5) The ACIE lock file is deleted.
(E6) A corresponding ACIE done file is stored in the concerned directory.
Files cleanup:
The produced ACIE export files are kept until another similar export session (i.e. with
the same concerned export directory) is requested in which case the new produced
files automatically replace old ones, if any.
This strategy makes it possible for another entity (be it a 9153 OMC-R operator or
another NMC) to:
Check if there are ACIE MOC files in one of the directories corresponding the level
of the desired export session and that the number of files correspond to the
number of concerned MOCs at that level.
If yes, to transfer one of these files and extract the header and sub-headers to
decide whether the available ACIE MOC files are sufficient to meet the perceived
need of that entity.
If these files are sufficient, to transfer these files instead of requesting a new
export session.
In other words, this makes it possible to avoid triggering export sessions if the needed
information is already available, which is recommended (for performance reasons).
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
50/66
The produced ACIE done file is deleted via the File Transfer Achieved function (see
section 4.2.1.2).
Error handling:
Type of problem
Step
Comments
Fatal errors
Problems with the ACIE export
The concerned export directory
E1
directory
does not exist, e.g. because the
E4
supplied sub-directory number is
erroneous or an attempt to place the
produced files in this directory has
failed.
ACIE done file present in the ACIE
In the concerned export directory,
E1
export directory
an ACIE done file is present,
indicating that there are ACIE MOC
files in this directory that have not
yet been transferred.
Concurrent export session
In the concerned export directory, a
E2
lock file is present and <processId>
in it corresponds to a process that is
still alive.
9153 OMC-R Configuration data
For an export session at Network
E3
Level or BSC-NE Level, an attempt
cannot be retrieved
to produce a frozen snapshot of the
part
of
the
9153
OMC-R
Configuration database containing
the configuration data to be
exported has failed
For an export session at MFS-NE
level, the attempt to retrieve the
corresponding configuration data
has failed.
the ACIE lock file, if already produced by the export session, is deleted
Export Scope: either at Network Level or for a given BSC-NE or for a given MFSNE
11
RELEASED
9661m11re.doc
17/03/2010
51/66
The directory in which the ACIE Done file shall be deleted (called the concerned
directory in what follows) is:
Step
Comments
Fatal error
Problems with the ACIE export
The concerned export directory
F1
directory
does not exist, e.g. because the
supplied sub-directory number is
erroneous
Warning
ACIE done file not present in the
In the concerned export directory,
F1
ACIE export directory
no ACIE done file is present.
Export session:
to the mode preferred by the operator for export sessions (ARCI mode by
default)
If the export domain is a PRC, this PRC should be closed by the 9153 OMC-R
operator at the end of the export session.
File Transfer Achieved function:
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
52/66
4.2.3.2 run_UnitaryExportSession.pl
Trigger/Inputs:
To trigger ACIE export sessions, the run_UnitaryExportSession.pl script can be called
as follows:
run_UnitaryExportSession.pl -exportScope <export scope> -exportDirNumber <i> [-cgiMode]
where:
bss <x> where <x> is a number to request an ACIE unitary export session for
the BSC-NE identified by <x>2
bss ALL to request an ACIE unitary export session for all the existing BSCNEs at the time the script is launched.
mfs <x> where <x> is a number to request an ACIE unitary export session for
the MFS-NE identified by <x>3
mfs ALL to request an ACIE unitary export session for all the existing MFSNEs at the time the script is launched.
-cgiMode shall only be present when <export scope> is equal to rnl and <i> is
different from 1 and indicates that the export session is triggered in CGI mode.
Otherwise, the export session is triggered in ARCI mode.
Outputs:
Per triggered ACIE unitary export session,
9661m11re.doc
17/03/2010
53/66
4.2.3.3 run_FileTransferAchieved.pl
Trigger/Inputs:
To trigger the File Transfer Achieved function, the run_FileTransferAchieved.pl script
can be called as follows:
run_FileTransferAchieved.pl -exportScope <export scope> -exportDirNumber <i>
where:
11
RELEASED
9661m11re.doc
17/03/2010
54/66
Type of problem
Comments
and/or the arguments passed to it
is/are not correct.
In that case, the script terminates with an indication that an error has occurred.
NMC
9153
OMC-R
requestTransferUp action Req.
(simpleFileTransferControl)
(N1)
(N2)
(N3)
(N5)
(N4)
(N6)
11
RELEASED
9661m11re.doc
17/03/2010
55/66
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
fileType
This
sub-field
should
contain
configurationFile
M
fileSubType
This sub-field should contain a valid subdirectory number (see section 4.2.1).
transferId
M
This field contains an integer value that
uniquely identifies the export session for the
requesting NMC. It is the responsability of the
requesting NMC to guarantee this unicity.
(N2) The 9153 OMC-R checks whether it can process the corresponding export request.
This step is similar to steps E1 and E2 of the general export scenario except that a
requestTransferUp
response
primitive
is
emitted
by
the
GSM
12.00:simpleFileTransferControl object instance. If:
the Action Info parameter of the request is valid from a GDMO viewpoint but
does not comply with its aforementioned description or
probableCause
This sub-field contains the ProbableCause
value fileError (defined in AttributeASN1Module of [X.721]).
C
specificProblems
(absent)
M
perceivedSeverity
This sub-field contains major
C
11
RELEASED
9661m11re.doc
17/03/2010
56/66
fileName
typeOfFile
M
fileType
contains configurationFile
M
fileSubType
This sub-field is used to indicate the
sub-directory number (see section
4.2.1).
C
fileSize
linkedTransferId
M
This field indicates whether or not the
notification is linked to a requestTransferUp
action identified by a transferId.
Its contains TRUE.
transferId
M
This field contains the transferId value
supplied by the requesting NMC in the
corresponding requestTransferUp action
request.
(N5) The corresponding ACIE MOC files are transferred by the requesting NMC.
This step is under the responsability of the requesting NMC. The protocol used is the
one
indicated
in
the
ANOI:typeOfFileTransfer
attribute
of
the
ANOI:anoiPlmnNetwork object (see [ANOIcs-gene]).
N.B.:
It is noteworthy that nothing prevents another NMC to transfer the same files.
(N6) When the requesting NMC has finished transferring these files, a GSM
12.00:transferUpReceived
action
request
is
sent
by
the
GSM
12.00:simpleFileTransferControl object instance.
This causes the File Transfer Achieved function to be triggered (i.e. steps F1 to F2
above).
The Action Info parameter of the corresponding M-ACTION Request primitive is a list
with only one element which can be described as follows:
FIELDS
M/C COMMENTS
fileList
M
List that shall contain only one element with
the following sub-fields:
M
fileName
typeOfFile
M
fileType
shall contain configurationFile
M
fileSubType
shall contain a valid sub-directory
number (see section 4.2.1).
C
fileSize
(shall be absent)
transferId
M
This field contains the transferId value supplied
by the requesting NMC in the corresponding
requestTransferUp action request.
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
57/66
If the Action Info parameter of the request is valid from a GDMO viewpoint but does
not comply with its aforementioned description,
the request is denied with an 'accessDenied' error.
11
RELEASED
9661m11re.doc
17/03/2010
58/66
an input file, called an ACIE Filter file in which the external application can express its
needs
Empty lines and comment lines which are not intended to be processed but to make
the body of the file more readable. Comment lines begin with either the character '#' or
two characters '-' (GDMO comment, see [GDMO]).
Any number of space characters (including zero) can be written before and after
the character ':' above
9153 OMC-R Configuration Import/Export interface
ED
11 RELEASED
9661m11re.doc
17/03/2010
59/66
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
<MOC name> is a string corresponding to the name of one of the concerned 9153
OMC-R Managed Object Class (see section 3).
<ACIE export directory indication> is formed from the name of the associated ACIE
export directory by removing the 'ACIE_' prefix.
For example,
The name of the unitary APP file corresponding to the 'Cell.csv' ACIE MOC file in the
directory ACIE_NLexport_Dir2 is 'Cell_NLexport_Dir2.app'.
The name of the unitary APP file corresponding to the 'AlcatelBsc.csv' ACIE MOC file
in the directory ACIE_BSS5export_Dir3 is 'AlcatelBsc_BSS5export_Dir3.app'.
The name of the unitary APP file corresponding to the 'AGprsNsvc.csv' ACIE MOC file
in the directory ACIE_MFS6export_Dir4 is 'AGprsNsvc_MFS6export_Dir4.app'.
11
RELEASED
9661m11re.doc
17/03/2010
60/66
either for each of the existing BSC-NEs with a given ACIE sub-directory number.
In this case, its name has the following form:
<MOC-related name>_BSSALLexport_Dir<i>.app
or for each of the existing MFS-NEs with a given ACIE sub-directory number.
In this case, its name has the following form:
<MOC-related name>_MFSALLexport_Dir<i>.app
where:
the name of the global APP file corresponding to the 'AlcatelBsc.csv' ACIE MOC file in
the directories ACIE_BSS<x>export_Dir3 (with <x> identifying any of the existing BSCNEs) is 'AlcatelBsc_BSSALLexport_Dir3.app'.
the name of the global APP file corresponding to the 'AGprsNsvc.csv' ACIE MOC file in
the directories ACIE_MFS<x>export_Dir4 (with <x> identifying any of the existing MFSNEs) is 'AGprsNsvc_MFSALLexport_Dir4.app'.
11
RELEASED
9661m11re.doc
17/03/2010
61/66
{<BSS-NE x indication>
<header of the unitary APP files for BSS-NE x>
<sub-header unitary APP files for BSS-NE x>
+
<body of the unitary APP file for BSS-NE x>}
where:
For a BSC-NE:
# Data for BSS <x>
For a MFS-NE:
# Data for MFS <x>
For example:
# Data for BSS 3
<header of the unitary APP files for BSS-NE x> corresponds to the header of the
unitary APP files for the corresponding BSC-NE or MFS-NE and for the concerned
MOC.
<sub-header of the unitary APP files for BSS-NE x> corresponds to the sub-header of
the unitary APP files for the corresponding BSC-NE or MFS-NE and for the concerned
MOC.
<body of the unitary APP file for BSS-NE x> correspond to the body of the unitary APP
file for the corresponding BSC-NE or MFS-NE and for the concerned MOC.
<ACIE Filter file> is the (absolute) name (i.e. possibly preceded by a path name) of
an ACIE Filter file
-v (verbose) indicates that the supplied ACIE Filter file contains (MOC,
attribute) couples to keep.
If this option is not present, this indicates that the supplied ACIE Filter file
contains (MOC, attribute) couples to remove (in that case, the file is called
also an ACIE exception file).
-mode indicates that the first column (relating to <ieMode>) shall be removed.
If this option is not present, this indicates that the first column shall be kept.
-nid
indicates
that
the
second
column
(relating
to
<MOINetworkLevelIdValue>) shall be removed.
If this option is not present, this indicates that the second column shall be
kept.
<ACIE export directory(ies)> indicates the ACIE export directory(ies) in which the
ACIE MOC files to process can be found.
It has the following form:
-exportScope <export scope> -exportDirNumber <i>
where:
11
RELEASED
9661m11re.doc
17/03/2010
62/66
-global is an option that can only be specified if <export scope> is equal to 'bss
ALL' or 'mfs ALL'.
If present, it indicates that global APP files shall be produced instead of the unitary
APP files for each BSC <x> or MFS <x>.
<output directory> indicates the (absolute) name of the directory in which the
produced files shall be placed (called the output directory in what follows).
It is recommended not to use one of the ACIE import directories as output
directory.
N.B.:
It cannot be one of the ACIE export directories since the access rights of
the latter are (luckily) not sufficient.
Pre-conditions:
The considered ACIE export directory(ies) contain(s) a set of ACIE MOC files produced
by the corresponding ACIE unitary export session(s).
Outputs:
In the directory <output directory>,
If the -v option is absent, one unitary APP file is produced per considered
ACIE export directory and per ACIE MOC file present in that directory.
Otherwise, one unitary APP file is produced per considered ACIE export
directory and per ACIE MOC file present in that directory that is also present
in the ACIE Filter file.
If the -v option is absent, one global APP file is produced per ACIE MOC file
present in
Otherwise, one global APP file is produced per ACIE MOC file present in
11
RELEASED
9661m11re.doc
17/03/2010
63/66
then
if -v is absent, for each of the attributes listed in the ACIE Filter file
for that MOC, the column corresponding to the attribute is removed;
by copying the header and sub-header of one of these unitary APP files
by copying the body of each of the unitary APP files in turn preceded by
the appropriate <BSS-NE x indication> part.
(A2.2) Delete the set of corresponding unitary APP files for that MOC.
Files cleanup:
The deletion of the produced APP files is under the responsability of the external
application that has launched the script. It is recommended that this deletion is
performed as soon as these files are no longer of interest to this external
application and, to the least, prior to calling the script with the same ACIE export
directory(ies) and the same output directory as input: due to how APP files are
named (see section 5.3.1), this could lead e.g.
to have a set of unitary APP files for a given ACIE export directory that is not
consistent;
or to remove a set of APP files whereas they are still needed (e.g. in case the
script is called with the same ACIE export directory and the same output directory
but different options and/or different ACIE Filter files).
Error handling:
Type of problem
Comments
Fatal errors
Problems with the usage of the script
The syntax used to launch the script
A0
9153 OMC-R Configuration Import/Export interface
ED
11
RELEASED
9661m11re.doc
17/03/2010
64/66
Comments
and/or the arguments passed to it
is/are not correct.
Problems with an ACIE export A1.1 The
considered
ACIE
export
directory
directory does not exist, e.g.
because the supplied sub-directory
number is erroneous
Problems with the ACIE Filter file
A1.1 The ACIE Filter file cannot be found
Problems with the output directory
A1.1 The output directory does not exist
or it is not possible to place the APP
files to be produced in it.
Non-Fatal error
Problems with an ACIE export file
A1.1 An ACIE export file to process
cannot be found (e.g. because the
corresponding ACIE export session
has
not
been
terminated
successfully)
ACIE Filter file errors
Problems with the syntax of a line in A1.2 A line of the ACIE Filter file has not
the syntax described in section 5.2
the ACIE Filter file
Problems with a MOC indication in a A1.2 The MOC name specified in a line of
line of the ACIE Filter file
the ACIE Filter file does not
correspond to one of the MOC for
the concerned export level
Problems with an attribute indication A1.2 The attribute name specified for a
in a line of the ACIE Filter file
given MOC in a line of the ACIE
Filter file does not correspond to a
column of the corresponding ACIE
MOC file
In the fatal error cases, the script terminates with an indication that an error has
occurred.
In the non-fatal error case, the production of the APP file for the concerned MOC is
simply skipped.
In the ACIE Filter file error cases, each line in error is simply skipped.
Type of problem
11
RELEASED
9661m11re.doc
17/03/2010
65/66
6. ACRONYMS
ACDB
ACFR
ACIE
AFTR
APP
ARCI
BSC
BSS
BSSIM
BTS
BBT
CGI
CI
DD
GDMO
GSM
hh
HMI
I/E
LAC
MCC
MFS
MLU
mm
MM
MNC
MOC
MOI
NE
NMC
NS-VC
NSE
OID
O&M
OMC
PLMN
PRC
PVC
SC
SGSN
ss
YYYY
11
RELEASED
9661m11re.doc
17/03/2010
66/66