3bk-11204-0568-dszza

ED01 Released OMC-R export interface for PM data

30/05/2011 3BK 11204 0568 DSZZA 1/50

All rights reserved. Passing on and copying of this

document, use and communication of its contents not

permitted without written authorization from Alcatel-Lucent

Site

VELIZY

Mobile Access Division

Originators

B. CANOVAS

OMC-R export interface for PM data

Release B12

System : ALCATEL GSM BSS

Sub-system : SYS/SYS-TLA/SYS-OAM

Document Category : PRODUCT DEFINITION

ABSTRACT

This document is the specification of the interface for PM post processing application.

Approvals

Name App.

X. Lambert

DPM OSY

Roberto Albu

DPM OMC

REVIEW

Ed. 01 Proposal 01 31/03/11 By mails

HISTORY

Ed. 01 Proposal 01 25/02/11 Creation from B11 document Ed 05 Released 3BK 11204 0383

DSZZA.

B12 modifications take into account:

- AUPoIP: SFD ‘A User Plane over IP’ ref. 3BK 10204 0163 DTZZA

- VAMOS: SFD ‘VAMOS’ ref. 3BK 10204 0678 DTZZA

Ed. 01 Proposal 02 05/04/11 - CRQ 307457: In BSC section of BSSconf, add the number of cells in VAMOS mode.

- VERSION field set at ‘12<x>’ for B12.<x> version.

- Examples of B11 OBSYNT files for BSC and MFS.

- In OBSYNT, highlight Header Configuration and Suspected Flags parts.

Ed. 01 Released 30/05/11 - In §3.2.1: NB_CELL_VAMOS name missing in header.


30/05/2011 3BK 11204 0568 DSZZA 2/50





30/05/2011 3BK 11204 0568 DSZZA 3/50




TABLE OF CONTENTS

1 SCOPE ............................................................................................................................................................6

2 GENERAL OMC-R ACCESS FOR PM EXTERNAL INTERFACE ..........................................................................8

3 BSS CONFIGURATION DATA INTERFACE ......................................................................................................9 3.1 Files storage..........................................................................................................................................9

3.1.1 BSSConf files storage ...................................................................................................................9 3.1.2 BSSConf ZIP files storage.............................................................................................................9

3.2 Data description..................................................................................................................................10 3.2.1 BSC Section ................................................................................................................................12 3.2.2 Cell Section................................................................................................................................13 3.2.3 BTS Section ................................................................................................................................15 3.2.4 TRX Section................................................................................................................................16 3.2.5 TS Section (TRXTS) ....................................................................................................................16 3.2.6 N7 Signalling Link Section (N7SL) – useless section .................................................................17 3.2.7 N7 Link Set Section (N7LS) – useless section ...........................................................................17 3.2.8 N7 Signalling Link Code (N7) .....................................................................................................17 3.2.9 MSC Section ...............................................................................................................................19 3.2.10 Adjacency ..................................................................................................................................19 3.2.11 A Interface Channel (AIC) ..........................................................................................................20 3.2.12 X25 .............................................................................................................................................21 3.2.13 LAPD Section (LAPDA)................................................................................................................21 3.2.14 ABIS topology sections...............................................................................................................21 3.2.15 TC Section..................................................................................................................................24 3.2.16 GSL Section ................................................................................................................................24 3.2.17 MFS Section................................................................................................................................24 3.2.18 RNC Section ...............................................................................................................................25

4 BSS PM COUNTERS BINARY INTERFACE .....................................................................................................26 4.1 Files storage........................................................................................................................................26 4.2 Data description..................................................................................................................................26

4.2.1 BSS PM counter files: Description..............................................................................................26 4.2.2 Binary PM file format ................................................................................................................27

4.3 PM semantic ........................................................................................................................................27

5 MFS COUNTERS INTERFACE........................................................................................................................28 5.1 Files storage........................................................................................................................................28 5.2 Data format .........................................................................................................................................28 5.3 Information semantic .........................................................................................................................28

6 PM COUNTERS ASCII INTERFACE ................................................................................................................29 6.1 Obsynt interface .................................................................................................................................29

6.1.1 Configuration.............................................................................................................................29 6.1.2 Files storage ..............................................................................................................................29 6.1.3 Counter processing ....................................................................................................................31 6.1.4 Input file ....................................................................................................................................32 6.1.5 Format of the result files (GSM or GPRS) ..................................................................................32

7 TRACE AND OBSERVATION INTERFACE......................................................................................................50 7.1 Retrieve data ......................................................................................................................................50 7.2 File format and semantic ...................................................................................................................50


30/05/2011 3BK 11204 0568 DSZZA 4/50



permitted without written authorization from Alcatel-Lucent INTERNAL REFERENCED DOCUMENTS

[1]

3BK 11204 0564 DSZZA (B12) 3BK 11204 0452 DSZZA (B11)

OMC/MFS PM file interface specification

[2] 3BK 10263 0006 DCZZA System Specification O&M Documentation Plan B12

[3] 3BK 11204 0602 DSZZA FB Management of Trace Services

[4] 3BK 11204 0591 DSZZA NPO GSM part Services Description B12

REFERENCED DOCUMENTS

[5] FBS – Logical configuration management 3BK 11204 0577 DSZZA

RELATED DOCUMENTS

[A] 3BK 11204 0556 DSZZA (BSS B12)

3BK 11204 0446 DSZZA (BSS B11)

OMC/BSC PM FILE FORMAT

[B] 3BK 11203 0251 DSZZA (BSS B12)

3BK 11203 0173 DSZZA (BSS B11)

BSC COUNTERS CATALOGUE

[C] 3BK 11202 0252 DSZZA (MFS B12)

3BK 11203 0174 DSZZA (MFS B11)

MFS COUNTERS CATALOGUE

[D] 3BK 11204 0552 DSZZA OMC-BSS MIB Specification B12

PREFACE

This document describes for release B12 the external interface for PM data, from a B12 OMC-R.

The PM data come from a BSC/MFS B12 or a BSC/MFS B11.

OPEN POINTS / RESTRICTIONS

OP1 = What is the version field value of BSSconf in B12 according B12 index i.e. B12.1, B12.2 ?

-> Closed: 12<x> for B12.<x> version e.g. 121 for B12.1 version.


30/05/2011 3BK 11204 0568 DSZZA 5/50





30/05/2011 3BK 11204 0568 DSZZA 6/50




1 SCOPE

B12 PM Export Interface

OMC_R / B12 Server

NPO B12

Client with Laser application inside

BSC/MFS B11

BSC/MFS B12

OMC_R/B11

Server

B11 PM Export

Interface

This document intends to describe the external interface for PM data, from a B12 OMC-R and from a BSC/MFS B12 or B11. From a B12 OMC_R, the PM data come from B12 and B11 BSS.

File format of equipment B12 and B11 may not be the same: when counters document or interfaces are referenced, please take care of the release of the BSS or MFS.

Rk: the external interface for PM data from a B11 OMC-R is described in the B11 OMC-R export interface document.

The PM post processing applications such as NPO need to have access to the OMC-R data.

These data are:

• the BSS configuration data, which describe all the objects available in the network,

• the BSS PM counters, which are the results of the monitoring of the network activity,

• the MFS PM counters, which monitor GPRS network element activity,

• the IMSI trace and observations.

NB: BSS PM counters and MFS PM counters are provided in two versions: binary format from the BSC/MFS and ASCII post processing by the OMC-R

For each interface this document describes:

• how the data is extracted from the OMC-R

• the data format • the meaning of information.


30/05/2011 3BK 11204 0568 DSZZA 7/50



permitted without written authorization from Alcatel-Lucent By these interfaces, the OMC-R acts as a server and external applications as clients. The interface is not

dedicated to one client. NPO application is among the clients of the OMC_R.

The BSS configuration data are made available on request and the current BSS PM counters files are available at any time for a fixed period.


30/05/2011 3BK 11204 0568 DSZZA 8/50




2 GENERAL OMC-R ACCESS FOR PM EXTERNAL INTERFACE

The external application will access to the OMC-R with ftp. The ‘pmuser’ is a ftp user dedicated to this usage. The interface is based on stored files.

Each external application transfers the files to its own computer. External applications have only read access to exported files and to the directories hosting these files.

After a fixed period of time (typical 5 days), the OMC-R delete old files. The files are created in one step.

An external application has no need to check if the file is growing during file transfer.

The Unix last modification time of files is related to file data modification. So this time is NOT related to the time when the file is put in the external interface directory.

The external application should not use this modification time to detect new files.


30/05/2011 3BK 11204 0568 DSZZA 9/50




3 BSS CONFIGURATION DATA INTERFACE

A file containing the BSS configuration data is generated every 30 minutes by AXADMIN crontab job: GetBSSconf . It is up to the external application to retrieve it. The external application has only read access on the BSS configuration file.

3.1 Files storage

3.1.1 BSSConf files storage

The BSSConf files are stored in /alcatel/var/share/AFTR/ACME on OMC machine.

It is not advised to store the BSSConf files during more than 5 days.

The files are automatically purged after storage duration period through an AXADMIN crontab job: MF-cleanup:

40 3 * * * /usr/local/bin/sudo /alcatel/omc3/osm/script/MF-cleanup -t

PM,OBS,IMSI,GPRS,ACME,OBSYNT,NPO_INPUT,ALERTERS_INPUT -s 4

Files are read using ftp.

3.1.2 BSSConf ZIP files storage

In order to optimise the data transfer times for the customer, the output files are compressed in a zip file and put in a specific directory to be retrieved once a day and at the end of the day.

The directory name is: /alcatel/var/share/AFTR/ACME/ZIP

In this directory, the zip file containing all BSSConf files of one day is created:

Naming rule of the zip file:

- BSSConf.<OMC-R Name>.<date>.zip

where: date= yyyymmdd (previous day date)

Example: BSSConf.omcr07.20060613.zip

The zip file is automatically created once a day through an AXADMIN crontab job: createZipFiles.pl

The job is launched after the last BSSConf file of the day is available (03:20 by default). The hour of launching can be modified.

Axadmin Crontab:

20 3 * * * /alcatel/omc3/osm/script/createZipFiles.pl

The zip files are stored and available for one week (7 days). The zip files are automatically purged after storage duration period through an AXADMIN crontab job: MF-cleanup:


30/05/2011 3BK 11204 0568 DSZZA 10/50



permitted without written authorization from Alcatel-Lucent 25 3 * * * /usr/local/bin/sudo /alcatel/omc3/osm/script/MF-cleanup –t ACME_ZIP,OBSYNT_ZIP -s 7

The zip files are read using ftp.

3.2 Data description

The file is coming from the B12 OMC_R and can be related to a B12 or B11 BSC. In case some data are not available for a release, the related fields are empty. The new data in B12 are highlighted “only in B12”.

The file generated by the GetBSSConf script, is an ASCII text file, which contains a version identification and all here-below described information, with, for each set of them, a title.

The lines starting by a “#” character shall be considered as column title except for the first line of the file which is a comment line.

The “,” character is used as separator character in the file and no blank character must be inserted between “,” character and the parameter values.

In the case some data are not available for a BSC generation (e.g. G2 or Mx), the related fields are empty except if another behaviour is explicitly required.

In case of empty field, because the data is not available for the related BSC, the syntax is “,,”.

In this case the related release of the BSC is indicated in comment. When nothing is indicated in comment the field is then available for B12 as for B11.

The “;” character is used as end of line character in the sections.

The name of the file is: “BSSConf”, the name of the OMC-R, the date and time (YYYYMMDDHHMMSS) of generation, each part being separated by a dot (“.”) character.

The file is made up of two parts:

◊ A header containing the version and the OMC-R name identifier. In this part, the <carriage return> is used to end each line.

VERSION ⇒ Keyword

<version_value> ⇒ Value of the OMC version, 3 digits : 2 digits for the release and 1 digit for the version (whatever the Ed, if any). Example: 12<x> for B12.<x> version e.g. 121 for B12.1 version

OMC_NAME ⇒ Keyword

<OMC_name> ⇒ OMC-R name

DELTA_TIME ⇒ Keyword

<delta_time_value> ⇒ Value of the timezone (omc_local_time - GMT_time) in


30/05/2011 3BK 11204 0568 DSZZA 11/50



permitted without written authorization from Alcatel-Lucent minutes, 3 digits. A negative value is preceded with a minus

sign.

CHECKSUM ⇒ Keyword

<checksum_value> ⇒ Value of the checksum of the BSSConf body (all the sections present in the message)

OP1 = What is the version field value of BSSconf in B12 according B12 index i.e. B12.1, B12.2 ?

-> Closed: 12<x> for B12.<x> version e.g. 121 for B12.1 version.

◊ A body containing the following sections:

◊ BSC

◊ Cell

◊ BTS

◊ TRX

◊ TRXTS (TS object)

◊ N7SL (Signalling Link object)

◊ N7LS (Link Set object)

◊ N7 (Signalling Link Code)

◊ MSC

◊ ADJACENCY

◊ AIC (A Channel object)

◊ X25

◊ LAPDA (LAPD object)

◊ The Abis topology sections

◊ ABIS section

◊ ABIS_BTS section

◊ TC

◊ IP GSL

◊ MFS

◊ RNC


30/05/2011 3BK 11204 0568 DSZZA 12/50




Example : BSSConf.bourg.19970818091200 # BSS configuration file generated 19970818091200 VERSION 600 OMC_NAME Bourg DELTA_TIME 001 CHECKSUM 23 START BSC_SECTION # BSC_NUM, BSC_NAME, BSC_MCC,BSC_MNC,MIB_VERSION, [...]; 1,Bourg1,F82,243, 82, [...];

END BSC_SECTIONSTART CELL_SECTION [...]

3.2.1 BSC Section

START BSC_SECTION ⇒ keyword

# BSC_NUM, BSC_NAME, BSC_ MCC, BSC_MNC, MIB_VERSION, BSC_TYPE, BSC_NB_DTC, BSC_NB_ACH , BSC_NB_N7,NB_CELL_GPRS , NB_CELL, NB_TRX, EN_IP, NB_CELL_IP, NB_CELL_VAMOS, NB_BTS_IP_BSC, NB_AbisGroup, NB_AbisGroup_IPoE1,NB_GSL;

⇒ see under

END BSC_SECTION ⇒ keyword

BSC_NUM, BSC_NAME : BSC number and name

BSC_MCC, BSC_MNC : PLMN identification

MIB_VERSION : Version number of the MIB

BSC_TYPE : Type of BSC (or also called generation (1= G1, 2 = G2, 3 = MX)

BSC_NB_DTC : number of DTC

BSC_NB_ACH : number of ACH

BSC_NB_N7 : number of N7

NB_CELL_GPRS : Number of GPRS cell

NB_CELL : Number of cells in the BSC (GSM or GPRS)

NB_TRX : Number of TRX mapped on a TRE in the BSC

EN_IP : Enable IP (“TDM mode”, value=false, “IP mode“, value=true). If the field is empty then transmission mode is "TDM mode".

NB_CELL_IP : number of cells in IP mode,

NB_CELL_VAMOS : number of cells in VAMOS mode (thus also in IP mode),


30/05/2011 3BK 11204 0568 DSZZA 13/50



permitted without written authorization from Alcatel-Lucent NB_BTS_IP_BSC : number of BTS in IP mode,

NB_AbisGroup : number of AbisGroup,

NB_AbisGroup_IPoE1 : number of AbisGroup in IP over E1 mode

NB_GSL : number of GSL in IP or TDM mode

This line is repeated for each BSC.

Remark on BSC_MNC: the MNC value can be composed of either 3 digits or 2 digits. In this last case, the BSC_MNC is left-padded with an « F » character in order to always get 3 digits.

3.2.2 Cell Section

START CELL_SECTION ⇒ keyword

# BSC_NUM, BTS_INDEX, BTS_SECTOR, CELL_LAC, CELL_CI, CELL_NAME, CELL_NB_TCH, CELL_NB_SDCCH , BCCH_COMB, CCCH_CONF, BS_AGBLK_RES, TRX_NB, BTS_NAME,SEC_BTS_INDEX,SEC_BTS_SECTOR, CELL_NB_DYN, CELL_NB_EXTRA_ABIS_TS, CELL_NB_MPDCH, EME_PWR_MAX_GSM, EME_PWR_MAX_DCS, MAX_POWER_PER_SECTOR_GSM, MAX_POWER_PER_SECTOR_DCS, BCCH_BAND, BS_TX_PWR_MAX, BS_TX_PWR_MAX_INNER, BS_TXPWR_ATTENUATION, BS_TXPWR_ATTENUATION_INNER;

⇒ see under

END CELL_SECTION ⇒ keyword

BSC_NUM : BSC number

BTS_INDEX : BTS Site Manager (index in the BSC)

BTS_SECTOR : Sector number in the BTS

CELL_LAC, CELL_CI : LAC and CI of the cell

CELL_NAME : Cell name

CELL_NB_TCH : number of TCH

CELL_NB_SDCCH : number of SDCCH

BCCH_COMB : BCCH_COMBined flag (no more used by O&M tools because not take into account the 2nd CCCH TS)

CCCH_CONF : Configuration of the CCCH, broadcast on the PBCCCH for CS service establishment


30/05/2011 3BK 11204 0568 DSZZA 14/50



permitted without written authorization from Alcatel-Lucent BS_AGBLK_RES : BS_AGBLK_RES value

TRX_NB : Number of the TRX mapped on a TRE in the cell

BTS_NAME : OMC BTS site name. SEC_BTS_INDEX : BTS index for the secondary part of the cell (NULL if cell not shared)

SEC_BTS_SECTOR : BTS sector of the secondary part of the cell (NULL if cell not shared)

CELL_NB_DYN : Number of dynamic timeslot for SDCCH

CELL_NB_EXTRA_ABIS_TS : Number of configured extra Abis timeslot

CELL_NB_MPDCH : Number of MPDCH timeslots

EME_PWR_MAX_GSM : EME power threshold for GSM frequency band (GSM850 or PGSM or E-GSM ) in tenth of Watt

EME_PWR_MAX_DCS : EME power threshold for DCS frequency band (DCS1800or DCS1900) in tenth of Watt

MAX_POWER_PER_SECTOR_GSM : GMSK output power for the GSM frequency band (GSM850 or PGSM or E-GSM ) at the BTS antenna output connector in dBm with a precision of 0.1 (eg 42.1)which the concerned RA (sector) can provide.

MAX_POWER_PER_SECTOR_DCS : GMSK output power for the DCS frequency band (DCS1800 or DCS1900) at the BTS antenna output connector in dBm with a precision of 0.1 which the concerned RA (sector) can provide.

BCCH_BAND : Indicates the frequency band used as BCCH.

BS_TX_PWR_MAX : Power reduction in step of 2 dB required by the OMC_R relative to the attenuated GMSK output power of the sector.

BS_TX_PWR_MAX_INNER : Power reduction in step of 2 dB required by the OMC_R relative to the attenuated GMSK output power of the TRX of the inner zone in a concentric or multi-band cell.

BS_TXPWR_ATTENUATION : Power reduction expressed in dB (with a precision of 0.1 eg 42.1), applied on the sector, on the outer TRE (eg 2.3)

BS_TXPWR_ATTENUATION_INNER : Power reduction expressed in dB (with a precision of 0.1 eg 42.1), applied on the sector, on the inner TRE

This line is repeated for each cell.

Note for BCCH_BAND:

The frequency band of the TRX is encoded as follows:

00: The frequencies defined on the TRX are in the P-GSM band


30/05/2011 3BK 11204 0568 DSZZA 15/50



permitted without written authorization from Alcatel-Lucent 01: The frequencies defined on the TRX are in the DCS1800 band

02: The frequencies defined on the TRX are in the E-GSM band 03: The frequencies defined on the TRX are in the DCS1900 band 04: Not used 05: Not used 06: The frequencies defined on the TRX are in the GSM850 band

Note for BCCH_COMB flag:

1: the BCCH channel is configured as combined (i.e. CBC or CBH) 0: the BCCH channel is not configured as combined (i.e. BCC).

Note for CCCH_CONF:

0: one CCCH not combined, 1: one CCCH combined 2: two CCCH not combined

3.2.3 BTS Section

START BTS_SECTION ⇒ keyword

# BSC_NUM, BTS_INDEX, BTS_NAME, BTS_HW_GENERATION, BTS_FAMILY, ANTENNA_DIVERSITY, QMUX_ADDRESS, MUX_RULE, COMMERCIAL_USE;

⇒ see under

END BTS_SECTION ⇒ keyword



BTS_Name : BTS name

BTS_ HW_GENERATION* : BTS hardware generation

BTS_FAMILY* : Hardware family of a BTS

ANTENNA_DIVERSITY : Antenna diversity mode (NULL = unknown, False= no, True= yes)

QMUX_ADDRESS : QMUX address

MUX_RULE* : Multiplexing rule for all LAPD link of the BTS (NULL if no address)

COMMERCIAL_USE : whether the BTS is in commercial use (value 1) or not (value 0). If the BTS is not in commercial use, no cell is reported in the cell section.

* Notes:

- BTS_ HW_GENERATION: see BtsHwGenerationAndFamily in ACIE Interface for the values. Examples: evolium, unknown

- BTS_Family: see BtsHwGenerationAndFamily in ACIE Interface for the values. Examples: NULL, a9100.

- MUX_RULE: see MuxRule in ACIE Interface for the values.


30/05/2011 3BK 11204 0568 DSZZA 16/50




3.2.4 TRX Section

START TRX_SECTION ⇒ keyword

# BSC_NUM, BTS_INDEX, BTS_SECTOR,BBT_ID, TRX_NUMBER; ⇒ see under

END TRX_SECTION ⇒ keyword




BBT_ID : Baseband Transceiver identification

TRX_NUMBER : TRX rank in the cell

Notes:

- In case of cell shared, the BTS_INDEX and BTS_SECTOR refer to the primary BTS - If the TRX is not mapped on a TRE, the section related to this TRX is not filled in.

- If the BTS is not in commercial use, no trx related to the BTS is reported in the trx section.

3.2.5 TS Section (TRXTS)

START TRXTS_SECTION ⇒ keyword

# BSC_NUM, BTS_INDEX, BTS_SECTOR, TRX_NUMBER, TRXTS_NUMBER;

⇒ see under

END TRXTS_SECTION ⇒ keyword




TRX_NUMBER : TRX rank in the cell

TRXTS_NUMBER : TS Id in the TRX (0 to 7)


30/05/2011 3BK 11204 0568 DSZZA 17/50



permitted without written authorization from Alcatel-Lucent Notes:

- In case of cell shared, the BTS_INDEX and BTS_SECTOR refer to the primary BTS - If the TRX is not mapped on a TRE, the sections related to the TS of this TRX are not filled in.

- If the BTS is not in commercial use, no ts related to the BTS is reported in the ts section.

3.2.6 N7 Signalling Link Section (N7SL) – useless section

This section is reported when the signalling between BSC and MSC is in TDM

START N7SL_SECTION ⇒ keyword

# BSC_NUM, LINK_ID; ⇒ see under

END N7SL_SECTION ⇒ keyword


LINK_ID : Identification of the N7 Signalling link . In case of LSL: CIC on the A Intf. In case of HSL: N7_SLC value ( Signalling Link Code of the N7)

3.2.7 N7 Link Set Section (N7LS) – useless section


START N7LS_SECTION ⇒ keyword

# BSC_NUM, LINK_SET_ID; ⇒ see under

END N7LS_SECTION ⇒ keyword


LINK_SET_ID : Identification of the N7 link set (always 1)

3.2.8 N7 Signalling Link Code (N7)


START N7_SECTION ⇒ keyword

# BSC_NUM, N7_SLC,N7_NAME, N7_RATE, TS_NUM, ATER_NUM,LINK_ID;

⇒ see under


30/05/2011 3BK 11204 0568 DSZZA 18/50




END N7_SECTION ⇒ keyword


N7_SLC : Signalling Link Code of the N7

N7_NAME : Name of the N7: N7n where n is the SBL number

N7_RATE : N7 rate ( “LSL”, value=0,”HSL”, value=1)

TS_NUM : TS_number (value from 0 to 31)

ATER_NUM : Atrunk/Atermux number

LINK_ID : Identification of the N7 Signalling link : CIC/N7_SLC number.

Notes:

• N7_Signalling Link Code:

o LSL case (IP or not): value within the 1…15 range or 0…15 range

o HSL case(IP or not ):value within the 1…2 range or 0…1 range

• “n” from N7n in N7 name

o G2 BSC case: n is the Atrunk carrying the N7.

o MX BSC, 2 cases:

� LSL case (IP or not) : n is the N7_SBL number value within the 1…16 range

� HSL case (IP or not) : n is the N7_SBL number value within the 1…2 range

• TS_number_:

o LSL case (IP or not), it is the timeslot number on A-Trunk carrying the N7 which is always “16”.

o HSL case (IP or not):, this field is not significant.

• Atrunk number and Atermux number:

o LSL case (IP or not) or HSL IP, it is the A-trunk (E1 link) number carrying the N7

o HSL TDM case, it is the Atermux number carrying the N7

• Identification of the N7 Signalling link:


30/05/2011 3BK 11204 0568 DSZZA 19/50



permitted without written authorization from Alcatel-Lucent o LSL case (IP or not) : CIC on the A Intf : high weight which represents the Atrunk number

on 11 bits and the TS on 5 bits which is always “16”. The Atrunk number is the value of the Atrunk as set on MSC side for CIC - cf. CIC use in [A].

o HSL case (IP or not): N7_SLC value (Signalling Link Code of the N7) Refer above.

3.2.9 MSC Section

This section is reported when the signalling between BSC and MSC is in IP

START MSC_SECTION ⇒ keyword

# BSC_NUM,MSC_NAME, MSC_SBL; ⇒ see under

END MSC_SECTION ⇒ keyword


MSC_NAME : MSC name (discriminating MSC identification, checked at OMC level)

MSC_SBL : MSC SBL number (discriminating MSC identification, used at BSC level).

3.2.10 Adjacency

START ADJACENCY_SECTION ⇒ keyword

# BSC_NUM, BTS_INDEX, BTS_SECTOR, CELL_MCC_SOURCE, CELL_MNC_SOURCE, CELL_LAC_SOURCE, CELL_CI_SOURCE, CELL_MCC_TARGET, CELL_MNC_TARGET, CELL_LAC_TARGET, CELL_CI_TARGET;

⇒

⇒

see under

This group of parameter names is repeated 64 times

END ADJACENCY _SECTION ⇒ keyword

64 is the maximum number of target adjacency cells for one source cell.





30/05/2011 3BK 11204 0568 DSZZA 20/50



permitted without written authorization from Alcatel-Lucent CELL_MCC_SOURCE, CELL_MNC_SOURCE : PLMN identification of the source cell

CELL_LAC_SOURCE, CELL_CI_SOURCE : LAC and CI of the source cell

CELL_MCC_TARGET, CELL_MNC_TARGET : PLMN identification of the target cell

CELL_LAC_TARGET, CELL_CI_TARGET : LAC and CI of the target cells

Example of an adjacency section :

The section has to be built for 3 source cells. One source cell has 1 adjacency cell (or target cell) another source cell has 2 adjacency cells and the last one 3 adjacency cells.

The sub-lines “CELL_MCC_TARGET, CELL_MNC_TARGET, CELL_LAC_TARGET, CELL_CI_TARGET” are repeated 64 times and after that, there is one line per cell giving all its adjacencies.

START ADJACENCY_SECTION # BSC_NUM, BTS_INDEX, BTS_SECTOR, CELL_MCC_SOURCE, CELL_MNC_SOURCE, CELL_LAC_SOURCE, CELL_CI_SOURCE, CELL_MCC_TARGET, CELL_MNC_TARGET, CELL_LAC_TARGET, CELL_CI_TARGET, CELL_MCC_TARGET, CELL_MNC_TARGET, CELL_LAC_TARGET, CELL_CI_TARGET, CELL_MCC_TARGET, CELL_MNC_TARGET, CELL_LAC_TARGET, CELL_CI_TARGET; … … 1,1,1 ,100,100,202,261, 132,125, 1,1; 1,2,2 ,100,100,202,262, 132,125, 2,2, 32,125,3,3, 32,125,4,4 ; 1,3,3 ,100,100,202,263, 132,125, 4,4, 100,100,3,3; END ADJACENCY_SECTION

Notes: - If the BTS is not in commercial use, no adjacency related to the BTS is reported in the section.

3.2.11 A Interface Channel (AIC)

START AIC_SECTION ⇒ keyword


END AIC_SECTION ⇒ keyword


LINK_ID : Identification of the link on the A Interface Channel (CIC number on A Intf)


30/05/2011 3BK 11204 0568 DSZZA 21/50



permitted without written authorization from Alcatel-Lucent 3.2.12 X25

START X25_SECTION ⇒ keyword


END X25_SECTION ⇒ keyword


LINK_ID : Identification of the X25 link (ie CPR SBL number 1..4, 4 for G2 BSC, 1 for MX BSC)

3.2.13 LAPD Section (LAPDA)

START LAPDA_SECTION ⇒ keyword

# BSC_NUM, BTS_INDEX, LAPD_TYPE, LAPD_NUMBER; ⇒ see under

END LAPDA_SECTION ⇒ keyword


BTS_INDEX : BTS index

LAPD_TYPE : LAPD type (OML: 42 or RSL: 43)

LAPD_NUMBER : LAPD number (OML/RSL SBL)

Remark: LAPD type (44) on TSL is not taken into account

3.2.14 ABIS topology sections

3.2.14.1 ABIS section


30/05/2011 3BK 11204 0568 DSZZA 22/50




START ABIS_SECTION ⇒ keyword

# BSC_NUM, ABIS_NUM, ABIS_NAME, ABIS_TYPE, ABIS_TRANSPORT_MODE, ABIS_BANDWIDTH, BANDWIDTH_PER_SIG_LINK, BANDWIDTH_PER_TCH_TS, TCH_TS_ACTIVITY_FACTOR, NRT_GUARANTEED_BW_FACTOR, IPGCH_PACKET_SIZE, IPGCHU_DELAY_HIGH_THRES_DL, IPGCHU_DELAY_HIGH_THRES_UL, IPGCHU_DELAY_LOW_THRES_DL, IPGCHU_DELAY_LOW_THRES_UL;

⇒ see under

END ABIS_SECTION ⇒ keyword


ABIS_NUM : ABIS number (used at BSC level)

ABIS_NAME : ABIS name (discriminating Abis identification at OMC level)

ABIS_TYPE : ABIS type (“chain”, value= 0, “Ring”, value=1, “Group configuration”, value= 2)

ABIS_TRANSPORT_MODE : Transport mode (“TDM“, value= 1, “IP framed”, value=2, “IP unframed “,value= 3, “IP Ethernet”, value= 4)

ABIS_BANDWIDTH : Total Abis bandwidth available (for the Abis BTS group if Abis-Transport-Mode = "IP Ethernet", or for one E1 link if Abis-Transport-Mode = "IP framed" or "IP unframed"). If transmission mode is TDM, the bandwidth is set to 0)

BANDWIDTH_PER_SIG_LINK : Bandwidth consumed by a signalling link on Abis interface:

-OML link associated to a BTS,

-or the RSL link associated to a TRX on Abis interface. If transmission mode is TDM, the bandwidth is set to 0

BANDWIDTH_PER_TCH_TS : Abis bandwidth consumed by a RTS supporting some TCH(s) (one FR TCH or two HR TCHs). If transmission mode is TDM, the bandwidth is set to 0 TCH_TS_ACTIVITY_FACTOR: : Maximum percentage of RTSs supporting some TCH(s) at the same time (one FR TCH or two HR TCHs), among all the RTSs configured as TCH or configured as dynamic SDCCH. If transmission mode is TDM, the value is set to 0 NRT_GUARANTEED_BW_FACTOR: Percentage of “reserved PS bandwidth” (Abis bandwidth) which is not considered as usable for GBR PS traffic by the MFS. If transmission mode is TDM, the bandwidth is set to 0. IPGCH_PACKET_SIZE : Max IPGCH packets size (including TCP/UDP/IP headers) used by IPGCHC and IPGCHU. If transmission mode is TDM, the value is set to 0

IPGCHU_DELAY_HIGH_THRES_DL : Threshold on measured differential delay in downlink for a given Abis. If transmission mode is TDM, the value is set to 0


30/05/2011 3BK 11204 0568 DSZZA 23/50



permitted without written authorization from Alcatel-Lucent IPGCHU_DELAY_HIGH_THRES_UL : Threshold on measured differential delay in uplink for a given

Abis. If transmission mode is TDM, the value is set to 0

IPGCHU_DELAY_LOW_THRES_DL : Threshold on measured differential delay in downlink for a given Abis below that the system is in nominal mode without any regulation. If transmission mode is TDM, the value is set to 0

IPGCHU_DELAY_LOW_THRES_UL : Threshold on measured differential delay in uplink for a given Abis below that the system is in nominal mode without any regulation. If transmission mode is TDM, the value is set to 0

3.2.14.2 ABIS_BTS section

This section aims at linking the BTS with the Abis link. A BTS can be linked to 2 different Abis links. The first Abis link is considered as “primary” and the other as “secondary”. An Abis link can be linked to 7 different BTS.

START ABIS_BTS_SECTION ⇒ keyword

# BSC_NUM, ABIS_NUM, BTS_INDEX_ON_ABIS, BTS_NAME,TP_TYPE;

⇒ see under

END ABIS_BTS_SECTION ⇒ keyword


ABIS_NUM : ABIS number

BTS_INDEX_ON_ABIS : BTS number on the related Abis link (Abis number) (This field is not significant in case of Abis_type = Group configuration)

BTS_NAME : BTS name

TP_TYPE : Terminal Point (“primary”, value= 0, “Secondary”, value=1) (This field is not significant in case of Abis_type = Group configuration)

Example of a ABIS_BTS section (G2 BSC case):

- Abis 1 on BSC 1 linked to BTS_4 and BTS_5 (secondary) - Abis 1 on BSC 1 linked to BTS_1 (primary) - Abis 2 on BSC 1 linked to BTS_1 (secondary)

START ABIS_BTS section


30/05/2011 3BK 11204 0568 DSZZA 24/50



permitted without written authorization from Alcatel-Lucent # BSC_NUM, ABIS_NUM, BTS_INDEX_ON_ABIS, BTS_NAME,TP_TYPE;

1,1,1,BTS_4,1; 1,1,2,BTS_5,1; 1,1,1,BTS_1,0; 1,2,1,BTS_1,1;

END ABIS_BTS section

3.2.15 TC Section

START TC_SECTION ⇒ keyword

# BSC_NUM, TC_RACK_NAME,TCSL_SBL; ⇒ see under

END TC_SECTION ⇒ keyword


TC_RACK_NAME : TC Rack name (discriminating TC identification, checked at OMC level)

TCSL_SBL : TCSL SBL number (used at BSC level). Value “0” is reported for a non IP BSC

3.2.16 GSL Section

This section is reported for both an IP and TDM BSC

START GSL SECTION ⇒ keyword

# BSC_NUM, GSL_SBL ,FABRIC_GPU; ⇒ see under

END GSL_SECTION ⇒ keyword


GSL_SBL : (used at BSC level) IP -GSL SBL number when BSC is in IP mode or GSL SBL number when BSC is in TDM mode

FABRIC_GPU : GPU identification (discriminating GPU identification, checked at OMC level and not significant in TDM mode)

3.2.17 MFS Section


30/05/2011 3BK 11204 0568 DSZZA 25/50




START MFS SECTION ⇒ keyword

# BSC_NUM, MFS_ID; ⇒ see under

END MFS_SECTION ⇒ keyword


MFS_ID : MFS number

3.2.18 RNC Section

This section is reported when an Iur-g interface is defined between BSC and RNC.

START RNC_SECTION ⇒ keyword

# BSC_NUM, RNC_NAME, RNC_SBL; ⇒ see under

END RNC_SECTION ⇒ keyword


RNC_NAME : RNC name (discriminating RNC identification, checked at OMC level)

RNC_SBL : RNC SBL number (discriminating RNC identification, used at BSC level).


30/05/2011 3BK 11204 0568 DSZZA 26/50




4 BSS PM COUNTERS BINARY INTERFACE

After each reporting period the OMC-R receives from the connected BSSs the PM result files per measurement type.

The list of BSC type of counters are given by the document : BSS counters catalog ref [B].

Detailed counters may have a measurement polling period of 30mn. GSM permanent counters have a minimum polling period of 15mn. Exception: 4 hours for type 180 counters. Each file is dedicated to a specific BSS raw measurement type and one reporting period. The OMC-R stores the required result files of the measurement type in a defined PM export directory of its file system. For the PM observation counters (type 10 to 15), please refer to §7 for the description of the specific interface.

4.1 Files storage

• The BSS PM files are stored in /alcatel/var/share/AFTR/APME/BSC.

• They can be retrieved using ftp pmuser user.

• Out put files are automatically purged after storage duration period (4 days) through an AXADMIN crontab job: MF-cleanup (same as for the BSSConf, OBSYNT …).

4.2 Data description

4.2.1 BSS PM counter files: Description

• Each PM export file is identified by a unambiguous file name. The file name contains the following information:

◊ identifier of the measurement type,

◊ file version number, i.e. the rank of the file in the sequence of files for the specified measurement type,

◊ BSS identifier,

◊ Date and time of file creation on BSS.


30/05/2011 3BK 11204 0568 DSZZA 27/50



permitted without written authorization from Alcatel-Lucent File naming rule:

"BSS_file_name".”BSC_num”."BSS_name"."file_creation_date"."file_creation_time"."sequence_num"."BSS_version "

"BSS_file_name": PMYYY-tt.xxA

YYY: RES for binary file and ASC for ASCII files.

tt: raw measurement type number. For type 110, 180 the formats are PMYYY110.xxA and PMYYY180.xxA;

xx: version number (01...99) of the file in the BSC.

“BSC_num”: BSC number

"BSS_name": name of the BSS as it is known by the OMC (up to 20 characters).

"file_creation_date": date when the file is created on the OMC-R. Format: YYYY-MM-DD

“file_creation_time": time when the file is created on the OMC-R. Format: HH:MM:SS

"sequence_num": number (between 1 and 9999) given by the OMC in order to guarantee the unicity of the file.

"BSS_version ": BSS phase version (see [D])

Example for measurement type 7 from BSS "bss-paris2" in B9.1:

PMRES-07.43A.2.bss-paris2.2004-06-11.10:30:00.9999.111

Example for measurement type 110 from BSS "MxBSC_A24" in B11:

PMRES110.48A.3.MxBSC_A24.2011-02-16.06:30:21.1115.259

4.2.2 Binary PM file format

BSS Binary file format is described in [A].

4.3 PM semantic

The counters are described in [B].


30/05/2011 3BK 11204 0568 DSZZA 28/50




5 MFS COUNTERS INTERFACE

OMC-R stores in a dedicated directory all MFS counters files. All supervised MFS files are stored in the same directory.

No MFS configuration interface is provided: MFS configuration data are included in the MFS counters files

The period of measurement for MFS counters is 1 hour

5.1 Files storage

• MFS PM files are stored in /alcatel/var/share/AFTR/APME/MFS

• They can be retrieved using ftp.

• Out put files are automatically purged after storage duration period (4 days) through an AXADMIN crontab job: MF-cleanup (same as for the BSSConf, OBSYNT …)

5.2 Data format

The MFS counter file format is described in the document [1].

All files are stored in compressed mode by using the gzip (Version 1.3 21 Dec 99) and have corresponding ".gz" extension.

To allow storage of MFS files for more than one day, a prefix is added by OMC to original MFS file name, which contains the UTC month and day when the file was created (i.e. last updated) on the MFS, converted into OMC local time (OMC time zone).

Example: MFS counter file for day 9 of January of MFS number 001 compressed.

Jan-9-GPMRES0500101.gz

5.3 Information semantic

Described in [C], counters part of the document.


30/05/2011 3BK 11204 0568 DSZZA 29/50




6 PM COUNTERS ASCII INTERFACE

The OBSYNT formats the files created by the OBSAL parsers from the binary PM files received from BSS or MFS to provide ASCII PM files (B11 or B12 files).

There is only one B12 OBSAL parser for generating the GSM OBSYNT format and only one B12 OBSAL parser for generating the GPRS OBSYNT format whatever the release B12 or B11. So the GSM result file/GPRS result file is identique regardless the release except the counters and the parameters which are specific. Please refer to the preface for knowing the differences between the two releases.

The OBSYNT formats are available on OMC-R.

Remark: From B10 there is no more need of MetricaTM on OMC-R to get the OBSYNT formats.

These ASCII files are stored in a specific directory and can be retrieved by an external component, for further analysis. Zip files are created and stored in a specific directory.

6.1 Obsynt interface

6.1.1 Configuration.

The operator can enable/disable the OBSYNT application through the OBSAL GUI. If it is ENABLE, the OBSAL parser sends, the PM result files to Obsynt.

The OBSYNT directory is not configurable. It is an internal data of the OBSAL parser.

The storage duration is specified in the axadmin crontab through the MF cleanup job.

6.1.2 Files storage

6.1.2.1 OBSYNT file storage

The output files results are stored in the /alcatel/var/share/AFTR/APME/OBSYNT directory. In this directory:

• Files are sorted by BSC and by day (for GSM part): one sub-directory per BSC (BSC name) and in this sub-directory, one sub-directory per day (yyyymmdd).

• Files are sorted by MFS and by day (for GPRS part): one sub-directory per MFS (MFS identifier) and in this sub-directory, one sub-directory per day (yyyymmdd).

The yyyymmdd corresponds to the day according to the end date of the measurement including midnight in case the measurement ends at midnight.

If a measurement starts at a D day and ends at a D+1 day, in this case it will be stored in the sub-directory of the D+1 day.

Remark: there is no sorting on the release.


30/05/2011 3BK 11204 0568 DSZZA 30/50



permitted without written authorization from Alcatel-Lucent It is not advised to store these files during more than 5 days. Out put files are automatically purged after

storage duration period through an AXADMIN crontab job: MF-cleanup (same as for the BSSConf, PM …).

40 3 * * * /usr/local/bin/sudo /alcatel/omc3/osm/script/MF-cleanup -t

PM,OBS,IMSI,GPRS,ACME,OBSYNT,NPO_INPUT,ALERTERS_INPUT -s 4

To modify, the storage duration, the axadmin operator has to perform the following steps:

- open the crontab file using the vi editor: crontab –e - modify the value “4” at the end of the command - save the crontab file

Each external application transfers the needed files from the directory, using ftp server.

6.1.2.2 OBSYNT ZIP file storage

In order to optimise the data transfer times for the external applications, the output files are compressed in zip files and put in a specific directory to be retrieved once a day and at the end of the day. They concern measurements which are finished this day.

The name of this directory is :

/alcatel/var/share/AFTR/APME/OBSYNTZIP

Inside the directory, the following zip files are created:

- The zip files containing all OBSYNT output files of a certain BSC of one day.

- The zip files containing all OBSYNT output files of a certain MFS of one day.

Naming rule: OBSYNT.<OMC-R Name>.<NE Name>.<date>.zip

where: NE Name represents BSC or MFS name and date=yyyymmdd (previous day date)

Example: OBSYNT.omcr07.R218.20060613.zip.

The zip files are automatically created once a day through an AXADMIN crontab job: createZipFiles.pl. This job is the same as for the BSSConf zip files creation.

Axadmin Crontab:

20 3 * * * /alcatel/omc3/osm/script/createZipFiles.pl

The job is launched after the last OBSYNT file of the day is available (03:20 by default). The hour of launching can be modified.

The ZIP files are available for one week (7 days). The zip files are automatically purged after storage duration period through an AXADMIN crontab job: MF-cleanup.

25 3 * * * /usr/local/bin/sudo /alcatel/omc3/osm/script/MF-cleanup –t ACME_ZIP ,OBSYNT_ZIP -s 7

Each external application transfers the needed zip files from the directory, using ftp server.


30/05/2011 3BK 11204 0568 DSZZA 31/50



permitted without written authorization from Alcatel-Lucent 6.1.3 Counter processing

The OBSYNT manages the OMC_R measurement files to be analyzed based on the following criteria:

- the release of the BSS or MFS

- the name of the BSS or MFS

- the duration of the measurements to be analysed indicating a begin and end date.

Each time the process OBSYNT is launched, the user can read information about it, inserted in the following OBSAL file:

/alcatel/var/maintenance/log/parser.log

If the process OBSYNT has detected a problem, the user can read information about it, inserted in the following OBSAL files:

/alcatel/var/maintenance/ltrace/parser. data, /alcatel/var/maintenance/ltrace/parser. stats, /alcatel/var/maintenance/ltrace/parser. traces

OBSYNT processes the following types of measurement in GSM (B12 and B11)

RT01_Traffic Measurements

RT02_Resource Availability Measurements

RT03_Resource Usage Measurements CCCH

RT04_Resource Usage Measurements SDCCH

RT05_Resource Usage Measurements RTCH

RT06_RTCH HO Measurements

RT07_LAPD Measurements

RT08_X.25 Measurements

RT09_No.7 Measurements

RT18_A Interface Measurements

RT19_SMS Measurements

RT25_SCCP Measurements

RT26_Detailed Handover measurements for serving cells

RT27_Detailed Handover measurements for a target cell


30/05/2011 3BK 11204 0568 DSZZA 32/50



permitted without written authorization from Alcatel-Lucent RT28_SDCCH HO Measurements

RT29_Directed Retry Measurements

RT30_SMSCB direct connection Measurements

RT32_Change of frequency band Measurements

RT33_Electro Magnetic Environment (EME) Supervision

RT35: IP Measurements (Present when IP supported)

RT36: IURG Measurements (Present when Iur-g interface enabled)

RT37: VAMOS Measurements (Present when VAMOS enabled)

RT110_CELL/TRX related overview counters

RT180_Traffic Flow Measurements.

OBSYNT processes all GPRS counters

Nota:

- There are no Obsynt files for RMS counters (type 31).

- The list of counters and their meaning can be found in counters catalog (ref. [B] and [C]).

- The values of counters are the ones reported on BSS/OMC interface: it means that when these values are modified for reporting (for example, multiplied per 10 in case of decimal values), the user of Obsynt interface has to translate correctly these values using the counter catalog.

6.1.4 Input file

OBSYNT retrieves the input files in the:

-/alcatel/var/share/AFTR/APME/BSC directory for the GSM counters

- /alcatel/var/share/AFTR/APME/MFS directory for the GPRS counters

The GSM and GPRS input files are the binary PM files from B12/B11 BSC and B12/B11 MFS.

6.1.5 Format of the result files (GSM or GPRS)

Each result file is composed of a file header and a data part. The GSM result files are related to B12 BSC or B11 BSC and GPRS result files are related to B12 MFS or B11 MFS.

The file header is composed of several lines and related to GSM or GPRS result file but does not depend on the release (B12 or B11).

The data part is composed of one or several sections, each section beginning with a section header. Some section can be present or not depending on the release. Also when an optional feature is not activated the related section included the header is not present. The order of the section does not matter.


30/05/2011 3BK 11204 0568 DSZZA 33/50



permitted without written authorization from Alcatel-Lucent Section header and data are represented by a table with several columns.

The meaning of the columns is given by the section header on one line. They are: the objects identification, some possible parameters and the counters identification. The objects identification in a given section does not depend on the release (B12 or B11) but the parameters can depend. The order between object identification part, parameters part and counters part is given below in the description of the result files.

The counter values are given in the data part of the section that is to say in the different lines of the table.

In a given section type the counters can be different depending on the release (B12 or B11).

Following requirements have to be applied:

- A column meaning in the section (section header or data) consists of a text field followed by a tab.

- Each line in a file header consists of a text field followed by one or several tabs then “:”and then the content. The number of tabs is such that one “:” is set below the one of the previous line (refer to the result file example)

- Each line ends with a carriage return.

- 2 empty lines separate the file header from the first one section

- 2 empty lines separate two successive sections

- The counters are sorted in alphabetical order

- The counters identification are written in upper case

- A "?" table element indicates that no valid or missing value is received for the corresponding counter.

- Within a section header:

o the object identification part follows the order defined below in the description of the result files.

o the specific part for parameters i.e. configuration or special suspected flags (basic are not relevant) are alphabetically ordered inside each type of parameter i.e. configuration or special suspected flags (but the order of each type of parameters follows the order defined below in the description of the result files). Eventual threshold parameters belong to the parameter type configuration and are alphabetically ordered inside configuration parameters.

6.1.5.1 GSM result files

There is one result file per PM type and per release

The name of the result file is in the following shape:

RXXXYYYYY.ZZZ

With:


30/05/2011 3BK 11204 0568 DSZZA 34/50



permitted without written authorization from Alcatel-Lucent R: for Result file

XXX: the measurement type number e.g.:110 or 018

YYYYY: the number of the file within the day e.g.:00001

ZZZ: the number of the day within the year e.g.:024

The result file contains two parts:

1. The file header

GSM measurement file header file with the following lines:

BSS release :12 (for B12) or 11 (for B11)

Name of BSC : friendly name of the BSC

Type of measurement : refer to the list in 6.1.3

Measurement begin date and time : yyyy-mm-dd hh-mm

Measurement end date and time : yyyy-mm-dd hh-mm

Input file name : full pathname

Output file name : full pathname

2. The data

Data are stored in tables that have the following structure:

- Section header part giving the meaning of the columns (in one line):

o the object Identifications

o the counters Identifications

- Section Data part indicating the values of the columns (one line per object).

In the object identifications, cells are identified in GCI mode that is to say with MCC/MNC/LAC/CI. The TRX

counters from type 110 are aggregated by the OBSAL parser in cells through the “on the fly” mechanism. So

these counters are reported twice in the obsynt resulting file: once at TRX level and a second time at cell

level (Example: MC370a); and at Cell level, the OBSAL parser sums only the valid values for TRX,

discarding, for sum, invalid TRX values (i.e. '?' values) and not setting the resulting sum to '?’.

The IP address value is displayed as a character string in the format "www.xxx.yyy.zzz" (it is coded in PM file

as 32 bits in 4 groups of 8 bits). For instance MGW_IP_ADDRESS is displayed as 139.54.87.128 (coded in

PM file as 2335594368).

The number of sections for each file result depends on types of counters and on the structure of the PM file from the BSC. Refer to BSC/OMC PM File Format document ([A]).

The following paragraph details the different sections for he different GSM types of counters:

• Type:1 (2 sections)

Cell section


30/05/2011 3BK 11204 0568 DSZZA 35/50




Header BTS_

INDEX

BTS_

SECTOR

CELL_

NAME

CELL_CI CELL_LAC BSC_MCC BSC_MNC Counter1 …

Data …

….. ….. …

TRX section

Header BTS_

INDEX

BTS_

SECTOR

CELL_

NAME

CELL_CI CELL_LAC BSC_MCC BSC_MNC TRXID Counter1 …

Data …

….. ….. …

• Type 2, 6,19, 28, 29, 32 ,33 (1 section)

Cell section

Header BTS_

INDEX

BTS_

SECTOR

CELL_NAME CELL_CI CELL_LAC BSC_MCC BSC_MNC Counter1 …

Data …

….. ….. …

• Type 3, 4, 5 (1 section)

TRX TS section

Header BTS_

INDEX

BTS_

SECTOR

CELL_

NAME

CELL_CI CELL_LAC BSC_MCC BSC_MNC TRXID TSID Counter 1 …

Data … …

….. ….. … …

• Type 7 (2 sections)

Lapd section

Header BTS_INDEX LAPD_TYPE LAPD_NUMBER Counter 1 …

Data …


30/05/2011 3BK 11204 0568 DSZZA 36/50




….. ….. …

GSL section (for TDM transport only)

Header GSL_SBL Counter 1 …….

Data

….. ….. ……

• Type 8, 25 (1 section)

X25 section

Header LINK_ID Counter 1 …….

Data

….. …..


CIC section


Data

….. …..

Link_Set section

Header LINK_ SET_ ID Counter 1 …….

Data

….. …..


Global BSS section (related to whole BSS)

Header Counter 1 …….

Data

….. …..


30/05/2011 3BK 11204 0568 DSZZA 37/50




CIC section (Not reported when A-interface is fully based on IP (i.e. “Full AUPoIP”) in case A User Plane over IP feature is enabled)


Data

….. ….. ……

• Type 26 (1 section)

Adjacent cell section

Header CELL_CI CELL_LAC CELL_CI_ADJ CELL_LAC_ADJ BSC_MCC BSC_MNC CELL_MCC_MNC_ADJ Counter 1 …..

Data …… ……

….. ….. ….. …….

• Type 27, 180 (1 section)

Adjacent cell section

Header CELL_CI _ADJ CELL_LAC_ADJ CELL_CI CELL_LAC BSC_MCC BSC_MNC CELL_MCC_MNC_ADJ Counter 1 …..

Data …… ……

….. ….. ….. …….

Note that the maximum number of adjacent cells (identified by CELL_MCC_MNC_ADJ, CELL_LAC_ADJ, CELL_CI_ADJ) reported in this section for the same cell (identified by BSC_MCC, BSC_MNC, CELL_LAC, CELL_CI) is equal to the maximum own cells per BSC ‘MAX-CELL’ defined in [5] (e.g. 264 for G2 BSC or 500 for Mx BSC).

• Type 30 (1 section)

Global BSS section

Header Counter 1 …….

Data

….. …..

• Type 35 ( present only for IP BSC)


30/05/2011 3BK 11204 0568 DSZZA 38/50



permitted without written authorization from Alcatel-Lucent (5 sections)

Cell section

Header BTS_INDEX BTS_SECTOR CELL_NAME CELL_CI CELL_LAC BSC_MCC BSC_MNC Counter 1 …..

Data …… …… ……

….. ….. ….. ……. …….

TC rack section

Header TC_RACK_NAME TCSL_SBL Counter 1 …..

Data

….. ….. …… ……

BSC-TCrack section

Header TC_RACK_NAME TCSL_SBL Counter 1 …..

Data

….. ….. …… ……

BTS section

Header TC_RACK_NAME TCSL_SBL BTS_INDEX Counter 1 …….

Data

….. ….. ….. ……

AbisNum section (Reported only on Abis with IPoE1 that is to say: Abis-Transport-Mode = IP unframed* or IP framed)

Header Abis_Name ABIS-NUM Counter 1 …….

Data

….. ….. ….. ……

(*): Not supported.


30/05/2011 3BK 11204 0568 DSZZA 39/50



permitted without written authorization from Alcatel-Lucent • Type 36 (present only when Iur-g interface is used between BSC and RNC)

(1 section)

RNC section

Header RNC_NAME RNC_SBL Counter1 …..

Data …… ……

….. ….. ….. …….

• Type 37 (present only for IP BSC and when at least one cell is enabled for VAMOS)

(1 section)

Cell section


Data …… …… ……

….. ….. ….. ……. …….


Cell section


Data …… …… ……

….. ….. ….. ……. …….

TRX section

Header BTS_INDEX

BTS_SECTOR

CELL_NAME

CELL_CI CELL_LAC BSC_MCC BSC_MNC TRXID Counter 1

Data …… ……

….. ….. ….. …….

CIC section (Reported only in signaling TDM mode between BSC and MSC)

Header LINK_ID Counter 1 …..

Data …… ……

….. ….. ……. …….


30/05/2011 3BK 11204 0568 DSZZA 40/50




Whole BSS section

Header Counter 1 Counter 2 …..

Data …… …… ……

….. ……. ……. …….

MSC section (Reported only in signaling IP mode between BSC and MSC)

Header MSC_NAME MSC_SBL Counter 1 …..

Data

….. ….. …… ……

NRI section (Reported only in signaling IP mode between BSC and MS and when the feature “Aflex” is activated)

Header MSC_NAME MSC_SBL NRI_NUM Counter1

Data

….. ….. …… ……

GSL section (Reported both for IP mode or TDM mode for GSL Transport)

Header FABRIC_GPU GSL_SBL Counter 1 …….

Data

….. ….. ….. ……

In case of TDM mode, the FABRIC_GPU is not significant.

MGW section (Reported only in A User Plane Over IP mode and when signaling between BSC and

MSC is IP)

Header MGW_IP_ADDRESS Counter 1 ….. …..

Data

….. ….. …… ……


30/05/2011 3BK 11204 0568 DSZZA 41/50



permitted without written authorization from Alcatel-Lucent Example of a B11 GSM measurement result file: R11000017.047 - for a B11 Mx BSC

NB: Example of a B12 GSM measurement result file for a next edition.

The file name indicates that it is the 17th result file (R) of the measurement type RT110 from the beginning of

day 047 of the year.

BSS release : 11

Name of BSC : MxBSC_A24

Type of Measurement :RT110_CELL/TRX related overview counters

Measurement begin date and time : 2011-02-16 08:00

Measurement end date and time : 2011-02-16 08:30

Input file name : /alcatel/var/share/AFTR/APME/BSC/PMRES110.48A.3.MxBS C_A24.2011-02-16.06:30:21.1115.259

Output file name :/alcatel/var/share/AFTR/APME/OBSYNT/MxBSC_A24/2011 0216/R11000017.047

BTS_ INDEX BTS_ SECTOR CELL_ NAME CELL_ CI CELL_ LAC BSC_MCC BSC_MNC MC01

MC02 MC02A MC02B …

1 1 cell00424_42405 42405 424 208 F05 12

537 526 3 …

BTS_ INDEX BTS_ SECTOR CELL_ NAME CELL_ CI CELL_ LAC BSC_MCC BSC_MNC TRXID

MC1200 MC1201 MC1202 …

1 1 cell00424_42405 42405 424 208 F05 1

153 0 0 …

1 1 cell00424_42405 42405 424 208 F05 2

153 0 0 …

1 1 cell00424_42405 42405 424 208 F05 3

153 0 0 …

… … … …

LINK_ ID MC350 MC351 MN1_1

16 8963 9010 3600


30/05/2011 3BK 11204 0568 DSZZA 42/50




144 8965 8906 3600

… … … …

MC182 MC19 MC35 MC36 …

40 50 92 81 …

MSC_NAME MSC_SBL MC1101 MC1102 MC1103 …

MSC01 1 40 35 33 …

MSC_NAME MSC_SBL NRI MC980 MC981 MC982 …

MSC01 1 1 83 75 90 …

MSC01 1 2 0 0 0 …

FABRIC_GPU GSL_SBL MC1060 MC1062 MC1063 …

16974080 1 57 2 11 …

6.1.5.2 GPRS Result file.

There is only one result file per MFS and per BSS release (there can be B12 GPU and B11 GPU in a same MFS). The name of the result file is in the following shape:

RMFSYYYYY.ZZZWith:

RMFS: for MFS Result file

YYYYY: the number of the file within the day e.g.:00001

ZZZ: the number of the day within the year e.g.:024

The result file contains two parts:

1. The file header:

MFS version : refer to PM File interface spec.

MFS subversion : Interface version, refer to PM File interface spec.

Number of the MFS : MFS identifier, refer to PM File interface spec.


30/05/2011 3BK 11204 0568 DSZZA 43/50



permitted without written authorization from Alcatel-Lucent Scanner identity : refer to PM File interface spec.

Measurement begin date and time : yyyy-mm-dd hh-mm

Measurement end date and time : yyyy-mm-dd hh-mm

Input file name : full pathname

Output file name : full pathname

2. the data

Data are grouped in sections structured in tables with the following structure:

- a section header part giving the meaning of the columns in one line:

o the objects identification

o the configuration data,

o the special suspected flag related to the counters. This excludes the basic suspected flags which indicate that the counter values are not relevant.

o the counters identification

- a section data part indicating the values of the different columns above (one line per object):

In the object identifications, cells are identified in GCI mode that is to say with MCC/MNC/LAC/CI.

The IP address value is displayed as a character string in the format "www.xxx.yyy.zzz" (it is coded in PM file

as 32 bits in 4 groups of 8 bits). For instance SGSN_IP_ADDRESS is displayed as 139.54.87.128 (coded in

PM file as 2335594368).

One section refers to only one type of object even there are several PM blocks for one object in the PM files received from MFS.

So also in a same section:

- Configuration data and special suspected flags are optional or can be not relevant,

- The counters can be different

Data and counters all depend on the release, the transport mode or the feature introduced or not.

For each section, for knowing the different PM blocks and their associated counters, if they are present or not and also for knowing the description of the different data, please refer to the MFS/OMC PM File Format document ([1]).

Except in some cases indicated below the identification data related to one object is always present and relevant.

Example of one section:

The cell section gathers B10cellPMUCOM, B11cellPMUTDM, B11cellPMUIP, B20cellPTUCOM, LCScell, DISTCell, B41CELLNACC.

When a MFS is not associated to any BSC there is no GPRS file.

The following paragraph details the section structure for the GPRS result file:

BearerChannel section (Reported only in Frame Relay Transport mode)


30/05/2011 3BK 11204 0568 DSZZA 44/50




Header (identification

and counter)

TP Bearer Counter 1 Counter 2 ….. …..

Data …… …… ……

….. ….. ….. ……. …….

PVC section (Reported only in Frame Relay Transport mode)


and counter)

TP Bearer PVC Counter 1 Counter 2 …..

Data …… …… …… ……

….. ……. ……. ……. …….

SGSN_IP_NSVC section (Reported only in GB over IP Transport mode)

Header

(identification)

FABRIC SGSNIPENDPOINT

Header

(configuration)

SGSN_IP_ADDRESS SGSN_UDP_Port Peer_NSE_Signalling_Weight

Peer_NSE_Data_Weight Gb_Configuration_type

Header

(configuration)

SGSN_NAME SGSN_IP_NSVC_NSEI

Header

(counter)

Counter 1 Counter 2 ……

Data ……. ……. …….

Recall: the section header part (composed here in identification, configuration and counter) gives the

meaning of the columns in one line.

SGSN section (Reported only in GB Flex Transport mode)

Header

(identification)

FABRIC SGSN _NAME

Header

(configuration)

SGSN_NSEI

Header

(counter)

Counter 1 ……

Data ……. …….


30/05/2011 3BK 11204 0568 DSZZA 45/50



permitted without written authorization from Alcatel-Lucent Recall: the section header part (composed here in identification, configuration and counter) gives the


LAPD section (Reported only in TDM Transport mode between BSC and MFS)


and counter)

BSS TP GSL Counter 1 Counter 2 …..

Data …… …… …… ……

….. ……. ……. ……. …….

Cell section

Header

(identification)

BSS FABRIC BTS CI LAC MCC MNC

Header

(configuration)

BS_PBCCH_BLKS BS_PRACH_BLKS MAX_PDCH MIN_PDCH List of Threshold (refer below)

….. …..

Header

(configuration)

BSS_TRANSPORT_MODE

BSS_TRANSPORT_MODE

Header

(suspected

flag and

counter)

DSF CSSF Counter1 Counter2 …..

Data …… ……

….. ….. …..

Recall: the section header part (composed here in identification, configuration, suspected flag and

counter) gives the meaning of the columns in one line.

The thresholds are as the counters sorted in alphabetical order:

• EGPRS_LLC_THROUGHPUT_THR_1 to EGPRS_LLC_THROUGHPUT_THR_11

• GPRS_LLC_THROUGHPUT_THR_1 to GPRS_LLC_THROUGHPUT_THR_10

• PD_DL_PDCH_UNIT_ALLOC_THR_1 to PD_DL_PDCH_UNIT_ALLOC_THR_10

• PD_DL_TBF_DURATION_THR_1 to PD_DL_TBF_DURATION_THR_10

• PD_DL_TBF_VOLUME_THR_1 to PD_DL_TBF_VOLUME_THR_10

• PD_UL_PDCH_UNIT_ALLOC_THR_1 to PD_UL_PDCH_UNIT_ALLOC_THR_10

• PD_UL_TBF_DURATION_THR_1 to PD_UL_TBF_DURATION_THR_10

• PD_UL_TBF_VOLUME_THR_1 to PD_UL_TBF_VOLUME_THR_10

The following parameters are for B12 only (CRQ 304666):

• BSS_TRANSPORT_MODE

• ABIS_TRANSPORT_MODE


30/05/2011 3BK 11204 0568 DSZZA 46/50




BTS section

Header

(identification)

BSS FABRIC BTS

Header

(configuration and

counter)

BTS_NB_EXTRA_ABIS_TS

Counter1 …..

Data …..

….. …..

Recall: the section header part (composed here in identification, configuration and counter) gives the


BSC section

Header

(identification)

BSS FABRIC

Header (suspected

flag and counter)

GCSF Counter 1 …..

Data …..

….. …..

Recall: the section header part (composed here in identification, suspected flag and counter) gives the


Abis section (Reported only in IP Transport mode)

Header

(identification and

counter)

BSS FABRIC ABISGROUP_NUMBER Counter 1 …..

Data …..

….. …..

Adjacent Cell section (Reported only with RIM-NACC enable)

Header

(identification)

BSS FABRIC CI LAC MCC MNC Counter 1 …..

Data ……


30/05/2011 3BK 11204 0568 DSZZA 47/50




….. …..

Example of a GPRS measurement result file : RMFS001.047 - for a B11 MFS

NB: Example of a B12 GPRS measurement result file for a next edition

MFS version : 7

MFS subversion : 7

Number of the MFS : 507

Scanner identity : 1

Measurement begin date and time : 2011-02-16 00: 00

Measurement end date and time : 2011-02-16 01: 00

Input file name : /alcatel/var/share/AF TR/APME/MFS/Feb-15-GPMRES0750711

Output file name : /alcatel/var/share/ AFTR/APME/OBSYNT/ mfs507/20110216/RMFS00001.047

TP Bearer P33 P3a P3b P6a P6b

16974082 31 0 0 0 0 0

16974593 15 0 0 0 0 0

…

TP Bearer PVC P23 P34 P4 …

16974082 31 521 0 0 0 …

16974593 15 520 0 0 0

…

BSS TP GSL P2a P2b P2c …

6 16974080 31 0 0 0 …

1 16974592 31 0 0 0 …

…


30/05/2011 3BK 11204 0568 DSZZA 48/50




BSS FABRIC BTS CI LAC MCC MNC

BS_PBCCH_BLKS

BS_PRACH_BLKS

MAX_PDCH MIN_PDCH EGPRS_LLC_THROUGHPUT_THR_1

… GPRS_LLC_THROUGHPUT_THR_9

CSSF DSF P10 P100C P100D …

6 16974080 25 62421 37193 460 F00

3 2 6 0 1 … 9

0 0 0 0 0 …

…

BSS FABRIC BTS BTS_NB_E

XTRA_ABI

S_TS

P201BIS P202BIS P203BIS

P472 P484 …

1 16974080 2 0 ? ? ?

864000 24 …

…

BSS FABRIC GCSF P100F P101 P103 …

1 16974080 0 0 8640000 0 …

…

FABRIC SGSNIPENDPOINT

GB_CONFIGURATION_TYPE

PEER_NSE_DATA_WEIGHT

PEER_NSE_SIGNALLING_WEIGHT

SGSN_IP_ADDRESS

SGSN_IP_NSVC_NSEI

SGSN_NAME SGSN_UDP_PORT

P34A P45A P46A

BSS FABRIC ABISGROUPNUMBER

P549A


30/05/2011 3BK 11204 0568 DSZZA 49/50




BSS FABRIC CI LAC MCC MNC P182C

P182D P182E

FABRIC SGSN_NAME

SGSN_NSEI

P180A P180B


30/05/2011 3BK 11204 0568 DSZZA 50/50




7 TRACE AND OBSERVATION INTERFACE

OMC-R stores in a dedicated directory all trace and observation files (PM types 10 to 15).

7.1 Retrieve data

• The trace files and observation files are stored in /alcatel/var/share/traces directory

• The trace files have to be copied under /alcatel/var/share/AFTR/MISC to be transfered by any external applications using the ftp server.

File names ruling are the following:

Trace Type Name of the trace result Example

Basic IMSI MIB.<BSS number>.<BSS name>.<trace number>.<transaction Id>.<sequence number>.<file creation date>.<file creation time>.<bss phase version>

MIB.001. BSS_Velizy .002.65535.001.1999-06-22.10:30:00.33

Radio IMSI MIR.<BSS number>.<BSS name>.<trace number>.<transaction Id>.<sequence number>.<file creation date>.<file creation time>.<bss phase version>

MIR.001. BSS_Velizy .002.65535.001.1999-06-22.10:30:00.33

7.2 File format and semantic

This piece of information is provided in [A] and [B] as for PM files. Sections related to trace and observations are IMSI basic trace, IMSI radio trace, PM types 10 to 15.

END OF DOCUMENT

3bk-11204-0568-dszza

Documents

pm external interface

canovas omcr export

pm data release b12

general omcr access

data description

alcatellucent ed01

bssconf files storage

bsc section of bssconf