09982laaae01

8/13/2019 09982LAAAe01

http://slidepdf.com/reader/full/09982laaae01 1/46

A1353-RA Remote Inventory Export Interface - Release B10

ED 01 RELEASED

9982l1re.doc26/10/2007 3BK 09982 LAAA PBZZA 1/1

A l l r i g h t s r e s e r v e d .

P a s s i n g o n a n d c

o p y i n g o f t h i s

d o c u m e n t , u s e a n d c o m m u n i c a t i o n o

f i t s c o n t e n t s

A1353-RA Remote Inventory Export Interface

(Release B10 onwards)

8/13/2019 09982LAAAe01



ED 01 RELEASED







SYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS

1. INTRODUCTION...............................................................................................5 1.1 Scope of the document ......................................................................... 5

1.2 Overview of the ARIE interface.............................................................5

1.3 Conventions and notations...................................................................5

2. A1353-RA REMOTE INVENTORY FILE EXPORT REPOSITORY .................. 7

3. THE ABTRIE FILES .........................................................................................9

3.1 Format and name of the ABTRIE files..................................................9

3.1.1 Unitary ABTRIE files......................................................................9

3.1.2 Full ABTRIE files............................................................................9

3.2 Structure of the unitary ABTRIE files.................................................10 3.2.1 General description......................................................................10

3.2.2 Line indicator description .............................................................10

3.2.3 Header data area description ......................................................10

3.2.4 Item data area description ...........................................................12 3.2.4.1 Structure of the item data area ......................................... ...............................12 3.2.4.2 Further information on the rack/shelf/slot organisation..................................12 3.2.4.3 The allowed properties....................................................................................13 3.2.4.4 Objects versus properties association table.....................................................14 3.2.4.5 Final data area description ........................................ ......................................15

3.3 Structure of the full ABTRIE files ....................................................... 15

3.3.1 General description......................................................................15

3.3.2 The header of a full ABTRIE file ..................................................15 3.3.3 The sub-header of a full ABTRIE file ...........................................15

3.3.4 The body of a full ABTRIE file......................................................16

3.3.5 The concerned fields of a full ABTRIE file ...................................16

4. THE AMERIE FILES.......................................................................................18

4.1 Format and Name of the AMERIE files...............................................18

4.1.1 Unitary AMERIE files ...................................................................18

4.1.2 Full AMERIE files.........................................................................18

4.2 Structure of the unitary AMERIE files ................................................18




4.2.4 Item data area description ...........................................................20 4.2.4.1 Structure and field of the item data area ......................................... ................20

4.3 Structure of the full AMERIE files.......................................................21


4.3.2 The header of a full AMERIE file .................................................21

4.3.3 The sub-header of a full AMERIE file...........................................21

8/13/2019 09982LAAAe01



ED 01 RELEASED







4.3.4 The body of a full AMERIE file.....................................................22

4.3.5 The concerned fields of a full AMERIE file...................................22

5. THE ABSRIE FILES .......................................................................................24

5.1 Format and Name of the ABSRIE files...............................................24

5.1.1 Unitary ABSRIE files....................................................................24

5.1.2 Full ABSRIE files .........................................................................24 5.2 Structure of the unitary ABSRIE files.................................................24




5.2.4 Item data area description ...........................................................26 5.2.4.1 Structure and field of the item data area ......................................... ................26

5.3 Structure of the full ABSRIE files ....................................................... 27


5.3.2 The header of a full ABSRIE file ..................................................27

5.3.3 The sub-header of a full ABSRIE file ...........................................27

5.3.4 The body of a full ABSRIE file .....................................................27

5.3.5 The concerned fields of a full ABSRIE file ...................................27

6. THE ATCRIE FILES .......................................................................................30

6.1 Format and Name of the ATCRIE files ...............................................30

6.1.1 Unitary ATCRIE files....................................................................30

6.1.2 Full ATCRIE files .........................................................................30

6.2 Structure of the unitary ATCRIE files.................................................30




6.2.4 Item data area description ...........................................................32

6.2.4.1 Structure and field of the item data area ......................................... ................32 6.3 Structure of the full ATCRIE files ....................................................... 33


6.3.2 The header of a full ATCRIE file ..................................................33

6.3.3 The sub-header of a full AMERIE file...........................................33

6.3.4 The body of a full ATCRIE file .....................................................34

6.3.5 The concerned fields of a full ATCRIE file ...................................34

7. EXPORT MECHANISMS................................................................................36

7.1 Unitary Remote Inventory Export sessions.......................................36

7.2 Full Remote Inventory Exportsessions..............................................38

8. ACRONYMS................................................................................................... 41

9. APPENDIX A: EXAMPLES OF ABTRIE FILES.............................................42

9.1 Example of a unitary ABTRIE file ....................................................... 42

9.2 Example of a full ABTRIE file..............................................................42

8/13/2019 09982LAAAe01



ED 01 RELEASED







10. APPENDIX B: EXAMPLES OF AMERIE FILES ............................................43

10.1 Example of a unitary AMERIE file.......................................................43

10.2 Example of a full AMERIE file .............................................................43

11. APPENDIX C: EXAMPLES OF ABSRIE FILES.............................................44

11.1 Example of a unitary ABSRIE file ....................................................... 44

11.2 Example of a full ABSRIE file..............................................................44

12. APPENDIX D: EXAMPLES OF ATCRIE FILES.............................................45

12.1 Example of a unitary ATCRIE file ....................................................... 45

12.2 Example of a full ATCRIE file..............................................................45

01 071026 First issue O&M System TD/MRC/OMD Spec

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

8/13/2019 09982LAAAe01



ED 01 RELEASED







LIST OF FIGURES AND TABLES

Figure 1: Organization of the ARIE repository....................................................................8

Table 1: The possible line indicators .....................................................................................10 Table 2: Rack/shelf/slot description and value ranges ..........................................................13 Table 3: The allowed properties ............................................................................................14 Table 4: Full ABTRIE header parts........................................................................................15 Table 5: Fields for the full ABTRIE files.................................................................................17 Table 6: The possible line indicators .....................................................................................19 Table 7: The allowed properties ............................................................................................21 Table 8: Full AMERIE header parts.......................................................................................21 Table 9: Fields for the full AMERIE files................................................................................23 Table 10: The possible line indicators ...................................................................................25 Table 11: The allowed properties ..........................................................................................27 Table 12: Full ABSRIE header parts .....................................................................................27 Table 13: Fields for the full ABSRIE files...............................................................................29 Table 14: The possible line indicators ...................................................................................31 Table 15: The allowed properties ..........................................................................................33 Table 16: Full ATCRIE header parts .....................................................................................33 Table 17: Fields for the full ATCRIE files...............................................................................35

HISTORY

Ed. 01:

− 08/10/2007: Creation from 3BK 09982 JAAA PBZZA Ed.03 ReleasedThe changes performed are those implied by the enhanced A1353-RA RemoteInventory feature for TC equipments.

− 26/10/2007: no technical changes

REFERENCED DOCUMENTS

[ACIE-gene] A1353 RA Configuration Import/Export Interface3BK 09661 LAAA PBZZA

RELATED DOCUMENTS

None

8/13/2019 09982LAAAe01



ED 01 RELEASED







1. INTRODUCTION

1.1 Scope of the document

This document specifies the A1353-RA Remove Inventory Export (ARIE) Interface forRelease B10 onwards.

The way the corresponding files (called ARIE files in what follows) are transferred is out ofthe scope of this document.

The way the corresponding files are build in the equipment is out of the scope of thisdocument.

1.2 Overview of the ARIE interface

The A1353-RA Remove Inventory Export (ARIE) interface is an interface that permits toaccess to ARIE files located in the A1353-RA File Transfer Repository (AFTR).

An ARIE file contains the necessary data for a precise identification of an item (hardware,firmware, ...) of a given equipment.Examples of such remote inventory data are:

− board manufacturing information (serial number, factory release date),

− board identification (name, identification),

− board history information (date of warrant, first in service date),

− repair history (date of last repair).

The inventory data retrieval can be processed in different ways, automatic or on demand,according to the A1353-RA operators needs.

The ARIE files produced can be distinguished according to:

− The concerned equipments.• For Evolium BTS equipments, the files are called A1353-RA BTS Remote

Inventory Export files (ABTRIE files for short).

• For MFS equipments, the files are called A1353-RA MFS Equipment RemoteInventory Export files (AMERIE files for short).

• For BSC equipments, the files are called A1353-RA BSC Equipment RemoteInventory Export files (ABSRIE files for short).

• For TC equipments, the files are called A1353-RA TC Equipment RemoteInventory Export files (ATCRIE files for short).

− The granularity of the exported data.

• If the granularity is the equipment itself, the qualifier 'unitary' will be used as prefix;

• If the granularity is the A1353-RA instance, the qualifier 'full' will be used as prefix.

A similar convention is used for related issues (directories, export mechanisms, ...).

1.3 Conventions and notations

To specify the form taken by a number of items (names, etc..), the following conventionsare used:

Item Meaning

CR carriage return

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED







2. A1353-RA REMOTE INVENTORY FILE EXPORT REPOSITORY

The A1353-RA has a repository dedicated to file transfers to external clients, called theA1353-RA File Transfer Repository (AFTR). The information required to reach this moregeneral file repository is predefined at the installation of an A1353-RA instance.

One sub-directory under AFTR is dedicated to the A1353-RA Remote Inventory Interface.The A1353-RA Remote Inventory Export directory is named ‘ARIE’.The full ARIE files (produced per A1353-RA instance) are directly placed under thatdirectory.

Under the ARIE directory, the following (sub-)directories are defined for unitary ARIE files:

−−−− The unitary A1353-RA BTS Remote Inventory Export directoriesThere is one sub-directory per BSS used for the unitary ABTRIE files for that BSS. Ithas a name of the form:

‘ARIE_BSS<BSCId >export’where <BSCId > is an integer that identifies the BSC equipment (called the BSC ID in

what follows). It is equal to the value of the “M.3100”:managedElementComplexId of thecorresponding “EML”:alcatelManagedElementComplex object instance.When a BSC is declared/removed by an A1353-RA operator, then the correspondingdirectory is automatically created/deleted by the A1353-RA.

− The unitary A1353-RA MFS Equipment Inventory Export directory There is one sub-directory dedicated to the unitary AMERIE files. It has the followingname:

‘ARIE_MFSexport’It is created at the A1353-RA installation time.

− The unitary A1353-RA BSC Equipment Inventory Export directory There is one sub-directory per BSS used for the unitary ABSRIE files for that BSC (the

same as for BTS). It has a name of the form:‘ARIE_BSS<BSCId >export’where <BSCId > is an integer that identifies the BSC equipment (called the BSC ID inwhat follows).When a BSC is declared/removed by an A1353-RA operator, then the correspondingdirectory is automatically created/deleted by the A1353-RA.

− The unitary A1353-RA TC Equipment Inventory Export directory There is one sub-directory dedicated to the unitary ATCRIE files. It has the followingname:

‘ARIE_TCexport’It is created at the A1353-RA installation time.

Only the A1353-RA is allowed to create or delete such directories. The files contained insuch directories can only be created/modified/deleted by the A1353-RA. On the other hand,any application can fetch them via ftp.

8/13/2019 09982LAAAe01



ED 01 RELEASED







This organization can be pictured as follows:

Unitary ABTRIE/ABSRIE directories.

AFTR ARIE repo sito ry

ARIE

ARIE_MFSexport

ARIE_BSS1export

ARIE_BSS2export

ARIE_BSSnexport

ARIE_TCexport

Figure 1: Organization of the ARIE repository

8/13/2019 09982LAAAe01



ED 01 RELEASED







3. THE ABTRIE FILES

3.1 Format and name of the ABTRIE files

3.1.1 Unitary ABTRIE files

The format used for a unitary ABTRIE file is plain ASCII text, organized in lines withmaximum 255 characters each.

Its name corresponds to the serial number of the first rack, which is defined so as to bealways unique.More precisely, this serial number has the following form:

<factory ><year ><week number ><XY ><ABC >where:

− <factory > is two characters identifying the factory in which the rack has beenmanufactured.

− <year > is the two digits representation of the year at which the rack was manufactured.− <week number> is the two digits representation of the week number at which the rack

was manufactured.

− <XY ><ABC > is five (2+3) characters ensuring the uniqueness of the serial numberamong the racks manufactured in the same factory the same week of the same year.

The corresponding unitary ABTRIE file name is <factory ><year ><weeknumber ><XY >.<ABC >. Its length is therefore of 12 characters.For example, if the first rack has the serial number EK0023AB146

− it is a rack manufactured in the factory identified by EK, week 23 of year 2000 with arelative identifier equal to AB146

− the name of the corresponding ARIE file is EK0023AB.146

3.1.2 Full ABTRIE filesThe format used for a full ABTRIE file is the (so-called) Comma Separated Value (CSV)format that consists in several lines separated by CR, each line being of the form:

<linePart >[;<linePart >];where <linePart > contains only characters different from ‘;’ and CR.It is the same as for the ACIE MOC files. See [ACIE-gene] for more information on thisformat.

The name of a full ABTRIE file is of the form:<A1353RAInstance> _abtrie.csv

where <A1353RAInstance> is a character string that indicates the concerned A1353-RAinstance.

More precisely, it is a predefined value that uniquely identifies the A1353-RA instancethroughout the world. It is assigned at the A1353-RA instance installation time. Its length isat most 32 characters.Example: A1353RA_83193b5b_abtrie.csv

8/13/2019 09982LAAAe01



ED 01 RELEASED







3.2 Structure of the unitary ABTRIE files

3.2.1 General description

The unitary ABTRIE file is divided in three areas (that appear in that order):

<ABTRIE header data area><ABTRIE item data area><ABTRIE final data area >

Each data area consists in a set of lines.

Each line represents one type of information. It begins with a first character, called the lineindicator, followed by a character that is either a space or "-" (see section 3.2.2).

3.2.2 Line indicator description

The line indicator indicates the structure and meaning of the rest of the line.The following table indicates, for each of the possible line indicators, the character following

it, the type of line and the area in which such a line can appear:

Line indicator (first character)

second character Type of line Area(s) in which itcan appear

C space Comment line(see below)

any

C - header data line(see section 3.2.3)

header data area

1 space Rack item data linedescribing a rack asa replaceable item(see section 3.2.4)

item data area

2 space Shelf item data linedescribing a shelf asa replaceable item(see section 3.2.4)

item data area

3 space Slot item data linedescribing a singlereplaceable item(see section 3.2.4)

item data area

E space 'end of file' line(see section 3.2.4.5)

final data area

Table 1: The possible line indicators

In particular, each line beginning with character 'C' followed by a space character is a

comment line. Such a line can be inserted anywhere in the file. Its contents are onlycomments intended for human readers, e.g. for additional information or just to improve thereadability of the file (table titles, split lines, ...).

3.2.3 Header data area description

The header data area gives general information concerning the entire file.It consists in a set of header data lines that can appear in any order.

8/13/2019 09982LAAAe01



ED 01 RELEASED







A header data line is of the following form:<headerDataName ><headerDataValue >

where:

− <headerDataName > is a character string in which the character case is not relevant (allcharacters are treated as uppercase ones).

− <headerDataValue > is the value of the corresponding header data, beginning at aspecific column.

The table below indicates, for each of the possible <headerDataName >:

− the format of the corresponding <headerDataValue > with possibly an example (initalics);

− the column at which this value begins;

− its maximum length;

− its description;

− whether the corresponding line is mandatory (M) or optional (O).

headerD ataName Format ofheaderD ataValueand examples

Val.begins at

Max.lengt

h

Description M/O

C-OMC-comment Text 15 80 Network Element Label of the form:

<BSC label clause><tab> <BTS label clause >where

− <BSC label clause> is of the form: BSC user label:<tab> <BSC name>

− <BTS name clause> is of the form: BTS user label:<tab> <BTS name>

in which

− <BSC name> (resp. <BTS name>)denotes the friendly name of the BSC(resp. BTS).

<tab> denotes the TAB character.

M

C-ProducedWith Text 16 80 Name and Version number of the tool thathas created the unitary ABTRIE file

M

C-CheckSum Integer 29 6 Checksum over relevant item data(Mnemonic, SerialNo.,...). The checksumcomputation is alcatel proprietary.

M

C-OrderData-NetId

3 characters 29 3 Customer alias called "network identifier" O

C-OrderData-Cypher

4 characters(3 characters plus1 checksumcharacter)

29 4 Station identifier called "cypher". O

C-OrderData-Location

Text 29 30 Cypher location description (station namecorresponding to the cypher above)

O

C-OrderData-NetElement

Text BTS

29 3 Network Element Type (Station typealways equal to “BTS”)

M

C-OrderData-

Time

DD.MM.YYYY

hh:mm:ss

29 20 File creation date and time

N.B.: ':ss' is optional

M

C-FirstCommDate DD.MM.YYYY 30.12.1999

29 10 First commissioning date M

C-Err Text 9 80 Error messages produced by the equipment O

C-Inf Text 9 80 Warning or information messages producedby the equipment

O

8/13/2019 09982LAAAe01



ED 01 RELEASED







3.2.4 Item data area description

3.2.4.1 Structure of the item data area

The item data area defines the properties of all inventory items.

It is arranged as a table in which:

− Each column corresponds to one property.The set of possible properties together with the corresponding layout window (startcolumn + length) are specified in section 3.2.4.2 and the characteristics that depend onthe concerned object are specified in section 3.2.4.2.The position of a property value within its layout window is not relevant (i.e. itsalignment can be left, centered, right or justified)

− Each line corresponds to one object which can be one of the following:

• a rack,

• a shelf (also called a subrack),

• a firmware,

• another replaceable item (also called module)

If this item provides remote inventory data itself, it is called a module, otherwise, itis called an additional module

The aforementioned objects are mainly considered to be organized into racks containingshelves, themselves containing slots. This corresponds to a classic hardware organisation.

Some hardware equipment architecture or aforementioned objects differ from the classicrack/shelf/slot organisation. For example, a box may contain modules without anyrack/shelf/slot organisation. For such type of hardware, the rack/shelf/slot value should beconsidered as a logical number. Further information on this logical organisation can befound in section 3.2.4.2.

Item data lines are sorted by ascending order of the position in that rack/shelf/slot

organisation, i.e.:− The first item data line describes rack number 1 (called the basic rack)

− The next item data line describes the first available shelf in rack 1.N.B.: Shelf data lines can be omitted if shelves are not treated as replaceable items

− The following item data lines describe all replaceable items located in this shelf inascending order of the slot number.

3.2.4.2 Further information on the rack/shelf/slot organisation

The following conventions are used as regards the rack/shelf/slot organisation assumed bythe item data area:

−Rack/shelf/slot convention for firmware items The rack/shelf/slot values for a firmware item are deduced from those of thecorresponding hardware item on which it is mounted using the following convention:

• firmware item rack value = hardware item rack value

• firmware item shelf value = hardware item shelf value + 10

• firmware item slot value = hardware item slot valueFor example, for a hardware item placed in rack1, shelf2, slot5, the associated firmwareis considered to be placed in rack1, shelf12, slot5.

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED







Notes:(1) The mnemonic of a firmware item are deduced from that of the corresponding hardware

item on which it is mounted by suffixing the latter's mnemonic with "FW".For example, for the hardware item with mnemonic "TRGM ", the associated firmwarehas the mnemonic "TRGMFW".

(2) The mnemonic of an additional module is equal to "ADDIMOD".

3.2.4.5 Final data area description

The final item area defines the end of a unitary ABTRIE file.

It consists in one line beginning with the "E” character (see section 3.2.2) completed by afree text.

3.3 Structure of the full ABTRIE files


A full ABTRIE file is composed as follows:<ABTRIE header ><ABTRIE sub-header ><ABTRIE body>

All these parts are described in the following sub-sections.

3.3.2 The header of a full ABTRIE file

The header of a full ABTRIE file corresponds to the first line of the file.It has the following form:

<A1353RAInstance >;<date >;<hour >;

The following table specifies each of the header parts in turn:

− The format

− A description of the part.

Header part Format Description

<A1353RAInstance > String identifies the concerned A1353-RA instance,as in the file name (see section 3.1.2)

<date> DD.MM.YYYY (local) date at which the file was created<hour> hh:mm:ss (local) time at which the file was created

Table 4: Full ABTRIE header parts

3.3.3 The sub-header of a full ABTRIE file

The sub-header of a full ABTRIE file corresponds to the second line of the file.It has the following form:

<fieldName >{;<fieldName >}+

where <fieldName > is a string that corresponds to the name of a field defined for the fullABTRIE files.

8/13/2019 09982LAAAe01



ED 01 RELEASED







3.3.4 The body of a full ABTRIE file

The body of a full ABTRIE file consists in a set of lines.One line is associated with a given BTS equipment.It has the following form:

<fieldValue >{;<fieldValue >}+

where <fieldValue > is the value of a field defined for the full ABTRIE files.

3.3.5 The concerned fields of a full ABTRIE file

The following table specifies, for each of the fields relevant for a full ABTRIE file (in the orderin which they appear):

− The field name used in the sub-header

− The format

− The source of the corresponding data in unitary ABTRIE files if any; A1353-RAotherwise

− The associated property(ies) in unitary ABTRIE files.It is noteworthy that, since in unitary ABTRIE files, when the property does not apply,the corresponding column is filled in with space characters, this also applies to theassociated field mentioned below.

− Comments, if any.

Field name Format Datasource

Property(ies) Comments

EqtType String header data C-OrderData-NetElement

Always equal to“BTS”

NEId String A1353-RA identifies the BSC(same value as<BSCId > in thename of thecorresponding

unitary ABTRIEdirectory)

EqtLabel String header data C-OMC-comment

<BSC name >/<BTS name > with <BSC name >(resp. <BTS name >)a stringcorresponding to thefriendly name of theBSC (resp. BTS).Example:BSS_116/BTS_016

ScanDate DD.MM.YYYY

HW itemdata

Scan date

ScanTime hh:mm[:ss] HW itemdata

Scan time Seconds areoptional

Cypher String HW itemdata

Cypher Station Identifier

CypherLocation String HW itemdata

Cypherlocation

Rack Integer HW itemdata

Rack number See section 3.2.4.2

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED







4. THE AMERIE FILES

4.1 Format and Name of the AMERIE files

4.1.1 Unitary AMERIE files

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

<linePart >[;<linePart >];where <linePart > contains only characters different from ‘;’ and CR.

Its name is of the form:mfs<MFSId >_amerie.csv

with <MFSId > an integer value equal to the MFS Identifier.Example: mfs500_amerie.csv

4.1.2 Full AMERIE files

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

<linePart >[;<linePart >];where <linePart > contains only characters different from ‘;’ and CR.It is the same as for the ACIE MOC files. See [ACIE-gene] for more information on thisformat.The name of a full AMERIE file is of the form:

<A1353RAInstance> _amerie.csvwhere <A1353RAInstance> is a character string that indicates the concerned A1353-RAinstance.More precisely, it is a predefined value that uniquely identifies the A1353-RA instance

throughout the world. It is assigned at the A1353-RA instance installation time. Its length isat most 32 characters.Example: A1353RA_83193b5b_amerie.csv

4.2 Structure of the unitary AMERIE files


The unitary AMERIE file is divided in two areas (that appear in that order):<AMERIE header data area><AMERIE item data area>


Each line represents one type of information. It begins with a first character, called the lineindicator, followed by a character that is either a ‘;’ or "-" (see section 4.2.2).

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED







C-Checksum Integer2717

Checksum over relevant itemdata (Mnemonic,SerialNumber.,...). Thechecksum computation isalcatel proprietary.


4.2.4.1 Structure and field of the item data area

The item data area defines the properties of all inventory items.One line corresponds per equipment.The following table specifies, for each of the fields relevant for a unitary AMERIE file (in theorder in which they appear):

− The field name used in the header

− The max lenght of the field

− The format

− Example for the field with its specific format

− Comments, if any.− Letter M (Mandatory) means “shall always have a meaningful value”, even if the module

is faulty. Letter O (Optional) means that, in case of faulty module, the field is set with“#ERROR#” and for equipments without firmware, the value is not significant.

Field name max.length

Format Example Comments M/ O

RACK Integer 1 Rack number M

SUBRACK Integer 0 Subrack (also called asShelf) number

M

SLOT Integer 0 Slot number M

MNEMONIC String BDAFU3 Rit name OPART NUMBER+ICS 15 String 3AF02465AC

AA 01 Identifies the technicaldefinition of the item (partnumber) + one space + 2characters (ICS = ItemStatus Change). Partnumber and ICS areseparated by one space.

O

SERIAL NUMBER 12 String BS0102U06R N

Board Serial Numberincludes the factory id

O

FLASH EPROM ID 16 String Firmware PartNumberincludes Item StatusChange

O

END OF WARRANTYDATE

10 DD.MM.YYYY 10.01.2005 No significant forequipment withoutfirmware

O

FIRSTCOMMISSIONINGDATE

10 DD.MM.YYYY 10.01.2005 No significant forequipment withoutfirmware

O

8/13/2019 09982LAAAe01



ED 01 RELEASED









LAST REPAIR DATE 10 DD.MM.YYYY 10.01.2005 No significant forequipment withoutfirmware

O

FACTORY RELEASEDATE 10 DD.MM.YYYY 10.01.2005 No significant forequipment withoutfirmware

O

SW VERSION 32 String No significant forequipment withoutfirmware

O

Table 7: The allowed properties

4.3 Structure of the full AMERIE files


A full AMERIE file is composed as follows:<AMERIE header ><AMERIE sub-header ><AMERIE body>


4.3.2 The header of a full AMERIE file

The header of a full AMERIE file corresponds to the first line of the file.It has the following form:



− The format





Table 8: Full AMERIE header parts

4.3.3 The sub-header of a full AMERIE file

The sub-header of a full AMERIE file corresponds to the second line of the file.It has the following form:


where <fieldName > is a string that corresponds to the name of a field defined for the fullAMERIE files.

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED







Field name Format Data source Corresponding datain unitary AMERIEfiles

Comments

FirstCommDate DD.MM.YY YY

Item data FIRSTCOMMISSIONINGDATE

No significant forequipment withoutfirmware

LastRepairDate DD.MM.YY YY Item data LAST REPAIR DATE No significant forequipment withoutfirmware

FactoryReleaseDate

DD.MM.YY YY

Item data FACTORY RELEASEDATE


SwVersion String Item data SW VERSION No significant forequipment withoutfirmware

Table 9: Fields for the full AMERIE files

(1) The format of the date is changed to be in line with the format used at the other A1353-RA external interfaces (meant to be recognized easily by widely available tools).

8/13/2019 09982LAAAe01



ED 01 RELEASED







5. THE ABSRIE FILES

5.1 Format and Name of the ABSRIE files

5.1.1 Unitary ABSRIE files

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


Its name is of the form:mxbsc<BSCId >_absrie.csv

with <BSCId > an integer value equal to the BSC Identifier.Example: mxbsc7_absrie.csv

Note: Only BSC Evolution has remote inventory capabilities.

5.1.2 Full ABSRIE files

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

<linePart >[;<linePart >];where <linePart > contains only characters different from ‘;’, CR and ‘,’.It is the same as for the ACIE MOC files. See [ACIE-gene] for more information on thisformat.

Note: The operator can choose the separator (‘;’ or ‘,’) from A1353-RA interface.

The name of a full ABSRIE file is of the form:<A1353RAInstance> _absrie.csv

where <A1353RAInstance> is a character string that indicates the concerned A1353-RAinstance.More precisely, it is a predefined value that uniquely identifies the A1353-RA instancethroughout the world. It is assigned at the A1353-RA instance installation time. Its length isat most 32 characters.Example: A1353RA_83a8ed03_absrie.csv

5.2 Structure of the unitary ABSRIE files

5.2.1 General descriptionThe unitary ABSRIE file is divided in two areas (that appear in that order):

< ABSRIE header data area>< ABSRIE item data area>


8/13/2019 09982LAAAe01



ED 01 RELEASED









The line indicator shows the structure and the meaning of the rest of the line.

The following table indicates, for each of the possible line indicators, the character followingit, the type of line and the area in which such a line can appear:

Line indicator (first character)

second character Type of line Area(s) in which itcan appear

C space or ; Comment line(see below)

any


header data area

space ; item data area item data area


In particular, each line beginning with character 'C' followed by a space or “;” character is a

comment line. Such a line can be inserted anywhere in the file. Its contents are onlycomments intended for human readers, e.g. for additional information or just to improve thereadability of the file (table titles, split lines, ...).



A header data line is of the following form:<headerDataName >;<headerDataValue >;

where:

−

<headerDataName > is a character string in which the character case is not relevant (allcharacters are treated as uppercase ones).

− <headerDataValue > is the value of the corresponding header data, beginning at aspecific column.





Description

C-OMC-comment BSCuser label

<BSC name>Mx_BSC_A07

Network Element Label <BSC name> denotes thefriendly name of the BSC.

C-File-Date-Retrieval

DD.MM.YYYYhh:mm:ss26.05.2006 11:54:24

Creation date and time of theunitary ABSRIE file.

8/13/2019 09982LAAAe01



ED 01 RELEASED







C-Equipment-Type

TextBSC

Network Element Type (Station type always equal to“BSC”).

C-Network-Element-Id

Integer4

Customer alias called "networkidentifier", identifies the BSC(same value as <BSC>).

C-Checksum Integer61871 Checksum over relevant itemdata (Mnemonic,SerialNumber.,...). Thechecksum computation isalcatel proprietary.



The item data area defines the properties of all inventory items.One line corresponds per equipment.

The following table specifies, for each of the fields relevant for a unitary ABSRIE file (in theorder of appearance):



− The format



− Letter M (Mandatory) means “shall always have a meaningful value”, even if the moduleis faulty. Letter O (Optional) means that, in case of faulty module, the field is set with“#ERROR#” and for equipments without firmware, the value is not significant.

Field name max.

length

Format Example Comments M/

O



M


MNEMONIC String JBXMUX Rit type O

PART NUMBER+ICS 16 String 3BK26881AAAA 05

Identifies the technicaldefinition of the item (partnumber) + one space + 2characters (ICS = ItemStatus Change). Partnumber and ICS areseparated by one space.

O

SERIAL NUMBER 17 String BS0510U0TLM


O

FIRMWARE VERSION 16 String 00000000000 0000


11 DD.MM.YYYY ---------- No significant forequipment withoutfirmware

O

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED








− The format

− The source of the corresponding data in unitary ABSRIE files if any; A1353-RAotherwise


Field name Format Data source Corresponding datain unitary ABSRIEfiles

Comments

EqtType String Header data C-Equipment-Type Always equal to “BSC”

NEId String Header data C-Network-Element-Id identifies the BSC(same value as<BSCId > in the name ofthe correspondingunitary ABSRIE file)

EqtLabel String Header data C-OMC-comment Friendly name of theBSC

ScanDate DD.MM.YY YY

Header data C-File-Date-Retrieval

ScanTime hh:mm[:ss] Header data C-File-Date-Retrieval Seconds are optionalRack Integer Item data RACK

Shelf Integer Item data SUBRACK

Slot Integer Item data SLOT

Mnemonic String Item data MNEMONIC Short name

PartNumberAndICS

String Item data PART NUMBER+ICS Identifies the technicaldefinition of the item +one space + 2characters (ICS = ItemStatus Change). Partnumber and ICS areseparated by one space.

SerialNumber String Item data SERIAL NUMBER Board Serial Numberincludes the factory idFlashEpromId String Item data FLASH EPROM ID Firmware PartNumber

includes Item StatusChange

EndOfWarrDate DD.MM.YY YY

Item data END OF WARRANTYDATE





LastRepairDate DD.MM.YY YY

Item data LAST REPAIR DATE No significant forequipment without

firmware FactoryReleaseDate

DD.MM.YY YY

Item data FACTORY RELEASEDATE



8/13/2019 09982LAAAe01



ED 01 RELEASED







Table 13: Fields for the full ABSRIE files


8/13/2019 09982LAAAe01



ED 01 RELEASED







6. THE ATCRIE FILES

6.1 Format and Name of the ATCRIE files

6.1.1 Unitary ATCRIE files

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


Its name is of the form:tc_<TC Name >_atcrie.csv

with <TC Name > a string value equal to the TC Name.Example: tc_T15_atcrie.csv

6.1.2 Full ATCRIE files

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

<linePart >[;<linePart >];where <linePart > contains only characters different from ‘;’ and CR.It is the same as for the ACIE MOC files. See [ACIE-gene] for more information on thisformat.Note: The operator can choose the separator (‘;’ or ‘,’) from A1353-RA interface.The name of a full ATCRIE file is of the form:

<A1353RAInstance> _atcrie.csvwhere <A1353RAInstance> is a character string that indicates the concerned A1353-RAinstance.

More precisely, it is a predefined value that uniquely identifies the A1353-RA instancethroughout the world. It is assigned at the A1353-RA instance installation time. Its length isat most 32 characters.Example: A1353RA_83a8ed03_atcrie.csv

6.2 Structure of the unitary ATCRIE files


The unitary ATCRIE file is divided in two areas (that appear in that order):< ATCRIE header data area>

< ATCRIE item data area>



8/13/2019 09982LAAAe01



ED 01 RELEASED








The line indicator shows the structure and the meaning of the rest of the line.The following table indicates, for each of the possible line indicators, the character followingit, the type of line and the area in which such a line can appear:

Line indicator (first character) second character Type of line Area(s) in which itcan appear

C space or ; Comment line(see below)

any


header data area

space ; item data area item data area


In particular, each line beginning with character 'C' followed by a space or “;” character is acomment line. Such a line can be inserted anywhere in the file. Its contents are onlycomments intended for human readers, e.g. for additional information or just to improve thereadability of the file (table titles, split lines, ...).



A header data line is of the following form:<headerDataName >;<headerDataValue >;

where:

− <headerDataName > is a character string in which the character case is not relevant (allcharacters are treated as uppercase ones).

− <headerDataValue > is the value of the corresponding header data, beginning at a

specific column.





Description

C-OMC-comment TCuser label

<TC name>TC15

Network Element Label <TC name> denotes thefriendly name of the TC.

C-File-Date-Retrieval

DD.MM.YYYYhh:mm:ss09.02.2007 12:45:13

Creation date and time of theunitary ATCRIE file.

C-Equipment-Type

TextTC

Network Element Type (Station type always equal to“TC”).

8/13/2019 09982LAAAe01



ED 01 RELEASED









The item data area defines the properties of all inventory items.

One line corresponds per equipment.The following table specifies, for each of the fields relevant for a unitary ATCRIE file (in theorder of appearance):



− The format



− Letter M (Mandatory) means “shall always have a meaningful value”, even if the moduleis faulty. Letter O (Optional) means that, in case of faulty module, the field is set with“#ERROR#” and for equipments without firmware, the value is not significant.


Format Example Comments M/

O



M


MNEMONIC String JBTCIF Rit type O

PART NUMBER String 3BK26881AAAA

Identifies the technicaldefinition of the item (partnumber).

O

SERIAL NUMBER String BS0510U0TLM


O

FIRMWARE VERSION String 00000000000 0000

Not significant forequipment withoutfirmware

O


DD.MM.YYYY ---------- Not significant forequipment withoutfirmware

O

COMMISSIONINGDATE


O

FLASH EPROMIDENTITY

String ---------- Not significant forequipment withoutfirmware

O

SW VERSION String ----------

Not significant forequipment withoutfirmware

O

END OF WARRANTYDATE


O

8/13/2019 09982LAAAe01



ED 01 RELEASED









LAST REPAIR DATE DD.MM.YYYY ---------- Not significant forequipment withoutfirmware

O

EQUIPMENT ERRORS String ---------- Not significant forequipment withoutfirmware

O

EQUIPMENTADDITIONALINFORMATION

String ---------- Not significant forequipment withoutfirmware

O

Table 15: The allowed properties

6.3 Structure of the full ATCRIE files


A full ATCRIE file is composed as follows:<ATCRIE header ><ATCRIE sub-header ><ATCRIE body>


6.3.2 The header of a full ATCRIE file

The header of a full ATCRIE file corresponds to the first line of the file.It has the following form:



− The format





Table 16: Full ATCRIE header parts

6.3.3 The sub-header of a full AMERIE file

The sub-header of a full ATCRIE file corresponds to the second line of the file.It has the following form:


where <fieldName > is a string that corresponds to the name of a field defined for the fullATCRIE files.

8/13/2019 09982LAAAe01



ED 01 RELEASED







6.3.4 The body of a full ATCRIE file

The body of a full ATCRIE file consists in a set of lines.One line is associated with a given TC equipment.It has the following form:

<fieldValue >{;<fieldValue >}+

where <fieldValue > is the value of a field defined for the full ATCRIE files.

6.3.5 The concerned fields of a full ATCRIE file

The following table specifies, for each of the fields relevant for a full ATCRIE file (in theorder in which they appear):


− The format

− The source of the corresponding data in unitary ATCRIE files if any; A1353-RAotherwise



Comments

EqtType String Header data C-Equipment-Type Always equal to “TC”

EqtLabel String Header data C-OMC-comment Friendly name of the TC

ScanDate DD.MM.YY YY

Header data C-File-Date-Retrieval

ScanTime hh:mm[:ss] Header data C-File-Date-Retrieval Seconds are optionalRack Integer Item data RACK

Shelf Integer Item data SUBRACK

Slot Integer Item data SLOT

Mnemonic String Item data MNEMONIC Short name

PartNumber String Item data PART NUMBER Identifies the technical

definition of the item.SerialNumber String Item data SERIAL NUMBER Board Serial Number

FirmwareVersion

String Item data FIRMWARE VERSION No significant forequipment withoutfirmware




CommissioningDate

DD.MM.YY YY

Item data COMMISSIONINGDATE


FlashEpromId String Item data FLASH EPROM

IDENTITY

Firmware PartNumbe


EndOfWarrDate DD.MM.YY YY

Item data END OF WARRANTYDATE


LastRepairDate DD.MM.YY Item data LAST REPAIR DATE No significant for

8/13/2019 09982LAAAe01



ED 01 RELEASED








Comments

YY equipment withoutfirmware

EquipmentError

s

String Item data EQUIPMENT

ERRORS

No significant for

equipment withoutfirmware

EquipmentAdditionalInformation

String Item data EQUIPMENTADDITIONALINFORMATION


Table 17: Fields for the full ATCRIE files


8/13/2019 09982LAAAe01



ED 01 RELEASED







7. EXPORT MECHANISMS

7.1 Unitary Remote Inventory Export sessions

Triggers:A unitary Remote Inventory Export session can be triggered either by an A1353-RAoperator (entitled to perform Remote Inventory tasks) or automatically.

Pre-conditions:None.

Inputs:

− Export session mode: either automatic or on-demand

− Additional inputs for automatic export:

• administrative state (locked/unlocked)• acquisition period (in days)

• acquisition time

(same value for all kind of unitary Remote Inventory Export session).− Additional inputs for on-demand export

• List of selected equipments(BTS equipments for unitary ABTRIE sessions, MFS equipments for unitaryAMERIE sessions, BSC equipments for unitary ABSRIE sessions, TCequipments for unitary ATCRIE sessions)

• Force Remote Inventory (FALSE/TRUE) only in case of BTS remote inventory

Outputs:In the concerned export directory, the corresponding ARIE files are produced.More precisely,

• For a unitary ABTRIE session:

−

The concerned export directory is the unitary A1353-RA BTS RemoteInventory Export directory corresponding to the associated BSC (i.e. thecorresponding ARIE_BSS<BSCId >export directory)

− The corresponding produced ARIE files are unitary ABTRIE files.• For a unitary AMERIE session:

− The concerned export directory is the unitary A1353-RA MFS EquipmentRemote Inventory Export directory (i.e. the ARIE_MFSexport directory)

−−−− The corresponding produced ARIE files are unitary AMERIE files

• For a unitary ABSRIE session:

− The concerned export directory is the unitary A1353-RA BSC RemoteInventory Export directory corresponding to the BSC (i.e. the correspondingARIE_BSS<BSCId >export directory)

− The corresponding produced ARIE files are unitary ABSRIE files.

• For a unitary ATCRIE session:− The concerned export directory is the unitary A1353-RA TC Equipment

Remote Inventory Export directory (i.e. the ARIE_TCexport directory)

−−−− The corresponding produced ARIE files are unitary ATCRIE files

Description:

The inventory data can be exported by different means:

8/13/2019 09982LAAAe01



ED 01 RELEASED







− Automatically by configuring an acquisition period and positioning appropriately theadministrative state (equal to unlocked)In that case, the A1353-RA polls all the equipments having the remote inventorycapability with the periodicity indicated by the acquisition period argument and at thetime indicated by the activation time argument. The ARIE export repository is updatedwith most recent files.This allows the A1353-RA to provide up-to-date inventory data at a user-definedperiodicity.

− Automatically by positioning appropriately the administrative state (equal to unlocked)In that case, whenever the A1353-RA detects the extension or reduction of equipmentshardware, it exports the corresponding ARIE files.This allows the A1353-RA to provide automatically up-to-date ARIE files.

− On operator's demandIn that case, the A1353-RA uploads the ARIE files for each of the selected equipments.This allows detecting the minor changes or is an alternative of the automatic mode.

The operator can lock/unlock the autonomous triggering of the ARIE files export. Whenlocked, no automatic export is performed, but the A1353-RA operator can always performthe on demand inventory. The lock allows not to jeopardize the performance of long

activities like a migration.

In case of BTS equipment, on A1353-RA request, the equipment polls its inventoryEEPROM. The equipment only sends back its inventory data if and only if hardwaremodifications have been done since the last acquisition. This allows, in the nominal case, toeasily reduce the inventory data flow with the equipments. The acquisition can be onlyforced in the on demand case.In case of MFS equipment, on A1353-RA request, the inventory data is transferred toA1353-RA. Based on checksum mechanism, the new inventory data is kept (if different thanprevious) or not.In case of BSC equipment, on A1353-RA request, the equipment polls its inventoryEEPROMs. Then the inventory data is transferred to A1353-RA. Based on checksummechanism, the new inventory data is kept (if different than previous) or not.

In case of TC equipment, on A1353-RA request, the inventory data is transferred to A1353-RA. Based on checksum mechanism, the new inventory data is kept (if different thanprevious) or not.

On reception of inventory data, the A1353-RA stores the inventory data as file.There is at most one ARIE file produced per equipment.

When choosing the automatic mode, the operator can modify the acquisition period fromone day to 30 days (7 days is the default value). The inventory data retrieval is usually madeduring non-busy hours and does not disrupt the other data retrieval (alarms,performances,…). Nevertheless, the user has the capability to stop the automatic mode atany time (lock/unlock inventory). In that case, the operator can still retrieve the inventorydata by using the “on demand” function.

Files cleanup:An ARIE file thus produced is deleted when the equipment is no longer supervised orwhen the related NE (BSC for unitary ABTRIE files, MFS for unitary AMERIE files, BSCfor unitary ABSRIE files and TC for unitary ATCRIE files) is no longer managed by theA1353-RA.

8/13/2019 09982LAAAe01



ED 01 RELEASED







7.2 Full Remote Inventory Exportsessions

Triggers:A full Remote Inventory Export session can be triggered either by an A1353-RAoperator (entitled to perform Remote Inventory tasks) or automatically by the A1353-RAafter the automatic ACIE export sessions.

N.B.: These automatic ACIE export sessions are triggered automatically by theA1353-RA every day at a time that is defined at the installation of a A1353-RAinstance. For more information, see [ACIE-gene].

Pre-conditions:None.

Inputs:

− Export session mode: either automatic or on-demand

Outputs:In the ARIE directory, the full corresponding full ARIE file is produced.For a full ABTRIE session, the produced file is a full ABTRIE file. For a full AMERIE

session, the produced file is a full AMERIE file. For a full ABSRIE session, theproduced file is a full ABSRIE file. For a full ATCRIE session, the produced file is a fullATCRIE file.

Description:

− For a full ABTRIE session:In an internal temporary directory:

− A temporary file is created with the ABTRIE sub-header.

− For each ARIE_BSS<BSCId >export directory and each unitary ABTRIE file inthis directory, the Remote Inventory data of each line corresponding to aHardware and the line corresponding to the associated Firmware (if any) areconverted as one line appended to the temporary file according to the newformat and structure for full ABTRIE file (see above).

− Then the header is added to the temporary full ABTRIE file.When this is completed, the temporary file is copied to the ARIE directory as thedefinitive full ABTRIE file.

− For a full AMERIE session:In an internal temporary directory:

− A temporary file is created with the AMERIE sub-header.− For each unitary AMERIE file in the ARIE_MFSexport directory, the Remote

Inventory data of each line are converted as one line appended to thetemporary file according to the new format and structure for full AMERIE files(see above).

− Then the header is added to the temporary file.When this is completed, the temporary file is copied to the ARIE directory as thedefinitive full AMERIE file.

− For a full ABSRIE session:In an internal temporary directory:

− A temporary file is created with the ABSRIE sub-header.

− For each unitary ABSRIE file in the ARIE_BSS<BSCId >export directory, theRemote Inventory data of each line are converted as one line appended to thetemporary file according to the new format and structure for full ABSRIE file(see above).

− Then the header is added to the temporary file.

8/13/2019 09982LAAAe01



ED 01 RELEASED







When this is completed, the temporary file is copied to the ARIE directory as thedefinitive full ABSRIE file.

− For a full ATCRIE session:In an internal temporary directory:

− A temporary file is created with the ATCRIE sub-header.

− For each unitary ATCRIE file in the ARIE_TCexport directory, the RemoteInventory data of each line are converted as one line appended to thetemporary file according to the new format and structure for full ATCRIE files(see above).

− Then the header is added to the temporary file.When this is completed, the temporary file is copied to the ARIE directory as thedefinitive full ATCRIE file.

Files cleanup:The full ARIE file is kept until another full ARIE sessions is requested in which case thenew produced file automatically replaces the old one, if any.

Error handling:

Type of problem Comments

Fatal errors Problems with the ARIE directory The ARIE directory does not exist or

an attempt to place the produced filein this directory has failed.

File-related errors

Problems with a unitary ABTRIEdirectory

The attempt to access to a unitaryABTRIE directory(ARIE_BSS<n >export) has failed

Problems with a unitary AMERIEdirectory

The attempt to access to the unitaryAMERIE directory(ARIE_MFSexport) has failed

Problems with a unitary ABSRIEdirectory

The attempt to access to the unitaryABSRIE directory(ARIE_BSS<n >export) has failed

Problems with a unitary ATCRIEdirectory

The attempt to access to the unitaryATCRIE directory (ARIE_TCexport)has failed

Problems with a unitary ABTRIE file A unitary ABTRIE file (relating toone BTS equipment) cannot beaccessed or converted for somereasons.

Problems with a unitary AMERIE file A unitary AMERIE file (relating toone MFS equipment) cannot beaccessed or converted for somereasons.

Problems with a unitary ABSRIE file A unitary ABSRIE file (relating toone BSC equipment) cannot beaccessed or converted for somereasons.

Problems with a unitary ATCRIE file A unitary ATCRIE file (relating toone TC equipment) cannot beaccessed or converted for somereasons.

8/13/2019 09982LAAAe01



ED 01 RELEASED







In case of a fatal error,

• an appropriate error message is displayed

• the export session is terminated.In case of a file-related error,

• an appropriate error message is displayed• the concerned directory or file is skipped and the export session continues.

8/13/2019 09982LAAAe01



ED 01 RELEASED







8. ACRONYMS

ARIE A1353-RA Remote Inventory Export InterfaceBSC Base Station ControllersBSS Base Station SubsystemBTS Base Transceiver StationDD Two digit representation of a dayhh Two digit representation of an hourMFS Multi-BSS Fast packet Server (A9135 equipment)MM Two digit representation of a monthBSC evolution Multi Standard Platform BSCmm Two digit representation of the minutesOMC Operation and Maintenance CentreRI Remote Inventoryss Two digit representation of the secondsTC TransCoderYYYY Four digit representation of a year

8/13/2019 09982LAAAe01


8/13/2019 09982LAAAe01



ED 01 RELEASED







11. APPENDIX C: EXAMPLES OF ABSRIE FILES

11.1 Example of a unitary ABSRIE file

C-OMC-Comment BSC user label;Mx_BSC_A07;

C-File-Date-Retrieval;26.05.2006 11:54:24;C-Equipment-Type;BSC;C-Network-Element-Id;4;C-Checksum;61871;C; RACK; SUBRACK; SLOT; MNEMONIC; PART NUMBER+ICS; SERIAL NUMBER; FIRMWARE VERSION; FIRST COMMISSIONING DATE;; 1; 1; 21; JBXPEM ; 3BK26883AAAA 01; BS0509U03FE ; 000000000000000; ---------- ;; 1; 1; 1; JBXPEM ; 3BK26883AAAA 01; BS0509U03GB ; 000000000000000; ---------- ;; 1; 1; 10; JBXMUX ; 3BK26881AAAA 05; BS0519U0E06 ; 000000000000000; -------- --;; 1; 1; 12; JBXMUX ; 3BK26881AAAA 05; BS0510U0TLM ; 000000000000000; ---------- ;; 1; 1; 19; ; ; ; ; ;; 1; 1; 20; JBXLIU ; 3BK26879AAAB 02; BS0536U16H3 ; 000000000000000; --------- -;...

11.2 Example of a full ABSRIE file

N.B.: Part of the file that corresponds to the unitary ABSRIE file

in the preceding section.A1353RA_83a8ed03;01.06.2006;22:05:35EqtType;NEId;EqtLabel;ScanDate;ScanTime;Rack;Shelf;Slot;Mnemonic;PartNumberAndICS;SerialNumber;FlashEpromId;EndOfWarrDate;FirsfCommDate;LastRepairDate;FactoryReleaseDate;SwVersion;

...BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 21; JBXPEM ; 3BK26883AAAA 01; BS0509U03FE ; 000000000000000; ----------;;;;BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 1; JBXPEM ; 3BK26883AAAA 01; BS0509U03GB ; 000000000000000; ---------- ;;;;BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 10; JBXMUX ; 3BK26881AAAA 05; BS0519U0E06 ; 000000000000000; ----------;;;;BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 12; JBXMUX ; 3BK26881AAAA 05; BS0510U0TLM ; 000000000000000; --------- -;;;;BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 20; JBXLIU ; 3BK26879AAAB 02; BS0536U16H3 ; 000000000000000; ----------;;;;BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 19; ; ; ; ; ;;;;BSC;4;Mx_BSC_A07;01. 06.2006;12:10:50; 1; 1; 2; JBXLIU ; 3BK26879AAAB 01; BS0509U0DN6 ; 000000000000000; --------- -;;;;...

8/13/2019 09982LAAAe01







12. APPENDIX D: EXAMPLES OF ATCRIE FILES

12.1 Example of a unitary ATCRIE file

C-OMC-Comment TC user label;TC-69

C-File-Date-Retrieval;2007.10.11 09:37:36C-Equipment-Type;TC;C;RACK;SUBRACK;SLOT;MNEMONIC;PART NUMBER;SERIAL NUMBER;FIRMWARE VERSION;FIRST COMMISSIONING DATE;COMMISSIONING DATE;FLASH EPROM IDENTITY;SWVERSION;END OF W ARRANTY DATE;LAST REPAIR DATE;EQUIPMENT ERRORS;EQUIPMENT ADDITIONAL INFORMATION;;7;11;10;;0;0;0;10106;10106;0;0;0;10106;10106;0;0;;7;12;20;;0;0;0;10106;10106;0;0;0;10106;10106;0;0;

12.2 Example of a full ATCRIE file

A1353RA_843b6481;11.10.2007;09:38:14EqtType;EqtLabel;ScanDate;ScanTime;Rack;Shelf;Slot;Mnemonic;PartNumber;SerialNumber;FirmwareVersion;FirstCommDate;ComissioningDate;FlashEpromId;SwVersion;EndOfWarrDate;LastRepairDate;EquipmentErrors;EquipmentAdditionalInformationTC;TC-69;2007.10.11;09:37:36;7;11;10;;0;0;0;10106;10106;0;0;0;10106;10106;0;0;TC;TC-69;2007.10.11;09:37:36;7;12;20;;0;0;0;10106;10106;0;0;0;10106;10106;0;0;

END OF DOCUMENT

09982laaae01

Documents