You are on page 1of 103

Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION

31/05/2011 3BK 11204 0556 DSZZA 1/103



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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Site
VELIZY
Mobile Access Division

Originators
B. CANOVAS
OMC/BSC PM FILE FORMAT SPECIFICATION
B12

System : ALCATEL GSM BSS
Sub-system : SYS/SYS-TLA/SYS-OAM
Document Category : PRODUCT DEFINITION
ABSTRACT
This document describes, for B12, the format of the files (PM result files, Trace Management result
files) exchanged between BSCs and OMC-R.


Approvals

Name
App.


Xavier Lambert

DPM OSY

Roberto Albu
DPM OMC

Zhang Hua

DPM BSC

Name
App
Raimund Sabellek

DPM BTS

Anca Nedelcu
DPM TC

REVIEW
Ed. 01 Proposal 01 15/12/10 By mails
Ed. 01 Proposal 02 24/03/11 By mails
Ed. 01 Proposal 03 11/04/11 By mails

HISTORY


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 2/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Ed. 01 Proposal 01 29/11/10

Creation from B11 document Ed 06 Released 3BK 11204 0446
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 17/12/10 Updating with remarks from OMC (C. De Sabata, P. Kumar)
and BSC (A. Singh, L. Wei):
- TYPE 37 (VAMOS) activated even if no VAMOS cell
enabled.
- Clarification on order of split blocks with the same
measured objects of the same PM type (3.2).

Ed. 01 Proposal 03 31/03/11 - In 3.2.35, name of measured object changed from MGW IP@
into MGW_IP_ADDRESS for PM Type block 1146.
- In 3.2.9, big typo removed (text from 3.2.7).
- In 3.2.18 and 3.2.35, clarification that block 181 in Type 18
and block N7 in Type 110 are not reported in case of A-
Signalling link over IP is enabled when blocks MSC and NRI in
Type 110 are only reported in case of A-Signalling link over IP
is enabled (with A-Flex for NRI).
- In 3.2.9 and 3.2.21, clarification that Type 9 and 25 are not
activated by OMC in case of A-Signalling link over IP is
enabled.
Ed. 01 Released 30/05/11
- Clarification in 3.2.33: Defense case could actually occur for
Type 37 even if quite rare.
- Clarification in 3.2: some blocks could be missing according
the BSC type or mode.




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 3/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

TABLE OF CONTENTS

1 SCOPE ........................................................................................................................................................................ 7
1.1 Aim of the document ...................................................................................................................................... 7
2 GENERAL FILE FORMATS........................................................................................................................................ 8
2.1 BSS files organisation and types ................................................................................................................... 8
2.2 Record organisation and record types ......................................................................................................... 9
2.3 File Structure ................................................................................................................................................. 10
2.4 BSS file names and numbers ........................................................................................................................ 10
2.4.1 BSS file names......................................................................................................................................... 10
2.4.2 BSS file numbers..................................................................................................................................... 11
3 Performance Management FILE FORMATS ...................................................................................................... 12
3.1 Performance Generic Header Record description.................................................................................... 12
3.1.1 Physical layout of PGHR........................................................................................................................ 13
3.2 PM Result File Formats................................................................................................................................. 16
3.2.1 TYPE 1: TRAFFIC MEASUREMENTS........................................................................................................ 20
3.2.2 TYPE 2: RESOURCE AVAILABILITY MEASUREMENTS............................................................................ 24
3.2.3 TYPE 3: RESOURCE USAGE MEASUREMENTS CCCH............................................................................. 24
3.2.4 TYPE 4: RESOURCE USAGE MEASUREMENTS SDCCH........................................................................... 26
3.2.5 TYPE 5: RESOURCE USAGE MEASUREMENTS RTCH............................................................................. 27
3.2.6 TYPE 6: RTCH HO MEASUREMENTS....................................................................................................... 28
3.2.7 TYPE 7: LAPD MEASUREMENTS.............................................................................................................. 29
3.2.8 TYPE 8: X.25 MEASUREMENTS............................................................................................................... 30
3.2.9 TYPE 9: No.7 MEASUREMENTS .............................................................................................................. 31
3.2.10 TYPE 10: SDCCH OBSERVATION............................................................................................................ 32
3.2.11 TYPE 11: RTCH MEASUREMENTS OBSERVATION ................................................................................. 33
3.2.12 TYPE 12: INTERNAL HANDOVER OBSERVATION.................................................................................. 35
3.2.13 TYPE 13: INCOMING HANDOVER OBSERVATION.................................................................................. 36
3.2.14 TYPE 14: OUTGOING HANDOVER OBSERVATION................................................................................ 37
3.2.15 TYPE 15: TCH OBSERVATION................................................................................................................. 38
3.2.16 TYPE 16: (NOT USED)............................................................................................................................. 39
3.2.17 TYPE 17: (NOT USED)............................................................................................................................. 39
3.2.18 TYPE 18: A INTERFACE MEASUREMENTS.............................................................................................. 40
3.2.19 TYPE 19: SMS MEASUREMENTS.............................................................................................................. 40
3.2.20 TYPE 20 to 24: (NOT USED)................................................................................................................... 41
3.2.21 TYPE 25: SCCP MEASUREMENTS............................................................................................................ 41
3.2.22 TYPE 26: DETAILED HO MEASUREMENTS FOR A SERVING CELL........................................................ 41
3.2.23 TYPE 27: DETAILED HO MEASUREMENTS FOR A TARGET CELL......................................................... 43
3.2.24 TYPE 28: SDCCH HO MEASUREMENTS .................................................................................................. 43
3.2.25 TYPE 29: DIRECTED RETRY MEASUREMENTS....................................................................................... 45
3.2.26 TYPE 30: SHORT MESSAGE SERVICE CELL BRODCAST MEASUREMENTS........................................... 45
3.2.27 TYPE 31: RADIO MEASUREMENTS STATISTICS..................................................................................... 45
3.2.28 TYPE 32: Change of frequency band measurements ........................................................................ 55


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 4/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.29 TYPE 33: Electro Magnetic Environment (EME) Supervision............................................................ 55
3.2.30 TYPE 34: Voice Group Call Services (VGCS)...................................................................................... 56
3.2.31 TYPE 35: IP MEASUREMENTS ................................................................................................................. 56
3.2.32 TYPE 36: IUR-G MEASUREMENTS .......................................................................................................... 58
3.2.33 TYPE 37: VAMOS MEASUREMENTS ........................................................................................................ 59
3.2.34 Type 38 TO TYPE 109: (NOT USED) ..................................................................................................... 60
3.2.35 TYPE 110: OVERVIEW MEASUREMENTS ................................................................................................ 60
3.2.36 TYPE 111 TO TYPE 179: (NOT USED) ................................................................................................... 64
3.2.37 TYPE 180: TRAFFIC FLOW MEASUREMENTS ........................................................................................ 65
3.3 Directory File.................................................................................................................................................. 66
4 Trace Management FILE FORMATS ................................................................................................................... 67
4.1 General Trace file formats .......................................................................................................................... 67
4.2 IMSI Radio Trace file formats ...................................................................................................................... 68
4.2.1 Trace Result File Format ...................................................................................................................... 69
4.2.2 IMSI Basic Trace file format ................................................................................................................. 75
5. GLOSSARY AND ABBREVIATIONS ........................................................................................................................ 97
5.1 Glossary........................................................................................................................................................... 97
6. ANNEX.................................................................................................................................................................... 100
6.1 CIC use in PM................................................................................................................................................ 100
6.2 Synthesis of BSC PM File Formats ............................................................................................................. 101



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 5/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

INTERNAL REFERENCED DOCUMENTS
[1] BSS Counters catalogue
3BK 11203 0251 DSZZA
[2] BSS Telecom Parameters
3BK 11203 0250 DSZZA
[3]
MIB specification document
3BK 11204 0552 DSZZA
[4] O&M A-bis interface
3BK 11204 0557 DSZZA
[5] FBS - Performance Management
3BK 11204 0590 DSZZA
[6] FBS Logical configuration management
3BK 11204 0577 DSZZA
[7] FB Management of Trace Services
3BK 11204 0602 DSZZA
[9] Layer 3 Message Dictionary A Interface
3BK 11203 0231 DSZZA
[10] Radio Measurements
3BK 11202 0523 DSZZA

REFERENCED DOCUMENTS


RELATED DOCUMENTS
[A] BSS Counters catalogue
3BK 11203 0251 DSZZA
[B] BSS Telecom Parameters
3BK 11203 0250 DSZZA
[C] BSC Counters block Layout
3BK ???? AAAA PC ZZA

PREFACE
This document describes for release B12, the format of the PM files (PM result files, Trace
Management result files) exchanged between the BSC and the OMC-R.

For the B12 release the impacts on files format are:


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 6/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
- Creation of a new block in PM type 110 for the A User Plane over IP counters.
- Creation of a new type 37 for VAMOS counters.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 7/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

1 SCOPE
1.1 Aim of the document
The aim of this document is to provide the description of the PM files exchanged between the BSC and the OMC-
R.
There are two main types of files:
Performance Management result files: These are measurement or observation result files; chapter 3 deals with
this type of files.
Trace Management result files: These files are defined in chapter 4.

B12 applicability
This section describes the specific requirements relevant for B12 release of the Alcatel BSS.
The list counters applicable for B12 is defined in the BSS Counters Catalogue [1].
The requirements defined in this specification, for which no restriction would be defined in this chapter, are
applicable to B12 release of the Alcatel BSS.



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 8/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

2 GENERAL FILE FORMATS
2.1 BSS files organisation and types
A BSS file is organised as a sequence of records, all of which are numbered sequentially. Different
record types form a BSS file. The following PM BSS file types are defined:

File Type Name File Type Number Description
GPMF 03 Generic Performance Measurement File
HPMF 04 History Performance Measurement File
OPMF 10 Observation Performance Measurement File
PMDF 12 Performance Measurement Directory File
TRCF 13 Trace Result File
ITRF 16 IMSI Trace Result File
Table 1: BSS File Types



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 9/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
2.2 Record organisation and record types
The generic organisation of a BSS file record is shown in figure below, where the shaded area is the 6
bytes System Record Header (SRH).

Number of bytes in the header
2 bytes
Record Sequence Number
2 bytes System Record Header (SRH)
Record Type Number 1 byte (absent within transmission settings file)
File Type Number 1 byte

Record content

max. 250 bytes


Important Note: the BTS transmission settings files are record structured (256 bytes records), but
there is no record header information. All 256 bytes are unformatted record content.

The first two bytes contain the total number of bytes in the header (System Record Header plus the
optional specific part of the header). Only some Record Types have a specific header, which is part of
the Record content.

For each file, the Record Sequence Number starts from 0.
The following Record Types are defined:

Record Type
Name
Record Type
Number
Description Reference
GPMR 03 Global Performance Measurement Record
3.2
OPMR 09 Observation Perf. Measurement Record
3.2
PGHR 12 Performance Generic Header Record
3.1
DPMR 14 Directory Performance Measurement Record
3.3
TRHR 15 Trace generic Header Record
4.1
TRDR 16 Trace Result Data Record
4.2
ITDR 20 IMSI Trace result Data Record
0



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 10/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
2.3 File Structure
Files are constructed with the following Record Types:

Record 0 Record 1 Record 2 . . . Record N File Type Names
PGHR OPMR OPMR . . . OPMR OPMF
PGHR GPMR GPMR . . . GPMR GPMF
DPMR DPMR DPMR . . . DPMR PMDF
TRHR TRDR TRDR . . . TRDR TRCF
TRHR ITDR ITDR . . . ITDR ITRF
2.4 BSS file names and numbers
This paragraph defines the general convention for the naming and numbering of BSS files with in
addition, the assignment of specific file numbers to BSS files exchanged between BSS sub-systems.

2.4.1 BSS file names
The general format of a BSS file name is composed of 12 characters: cccccccc.xxy, where:
c = A through Z or 0 through 9 or - (hyphen filler)
. = .
x = 0 through 9
y = A through Z

The <cccccccc> part of file name is used to identify one type of file e.g. PMRES-01 (see 2.4.2) and
<xxy>
1
part is the file version which is used to avoid overwriting old version of the same file type (cf.
[5]).


1
In current implementationin BSC, <y> is fixed to A for all files and <xx> part is from 01 to 99 for PM result file.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 11/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
2.4.2 BSS file numbers
The table below summarizes the file names and numbers for the PM and trace BSS files.

File type File Name File Number
Files for PM
Performance result file
Observation result file
Directory perf. Msmt. File
PMRESccc
2

PMOBS-cc
3

PMDIR---
311 490
4

320 325
500
Files for Trace IMSI Basic Trace Result File
IMSI Radio Trace Result File
TRACE-FR
TRACE-FB
2010
2011

The File Number is used in BSC to identify one type of file e.g. the file name PMRES-01 is one to
one map to file number 311 in BSC (the file number is not part of the file name as defined in 2.4.1 i.e.
cccccccc.xxy).



2
For the measurement type number 110 or 180, ccc = 110 or 180. For the measurement type = 01..09, 18, 19 or 25..37, ccc = -nn where nn
is the measurement type number.
3
cc is the measuerement type number: 10..15.
4
An allowed file number for a PM file is equal to: 310 + nnn, where nnn is the number of the associated measurement type. Therefore, the only
values used for PM file numbers are: 311..319, 328, 329, 335..347, 420 and 490.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 12/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

3 PERFORMANCE MANAGEMENT FILE FORMATS
3.1 Performance Generic Header Record description
Note: this is the same header for G2 BSC as for MX BSC
The Performance Generic Header Record (PGHR) is the first record (record sequence number 0) of
each performance report file. It has the following layout:
Description Size (Bytes)
System Record Header (SRH) 6B (See 2.2)
BSS Version 2B
BSC Release 1B
FILLER 1B
Managed Object Class 2B
Managed Object Instance 2B
File Creation 16B
Measurement Type 2B
Total Size 4B
Number of Records 2B
Begin Collection Time 16B
End Collection Time 16B
FILLER 3B (FFh FFh FFh)
Sample Percentage 1B (default: FFh)
Sample Rate Reduced 1B
FILLER 1B
FFh nB
Remaining space in
file record 0

Usage:
System Record Header: number of bytes = 76
record sequence number = 00
record type = 12 (PGHR)
file type = 03 or 10 (GPMF or OMPF)
BSS Version: BSS-Phase-Version: For the BSS version values please refer to the last
edition of the OMC-BSS MIB Specification B12 document ref [3].


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 13/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


BSC Release BSC-Release: For the values, please refer to the MIB Specification, for
information: (34) for BSC B11
Managed Object Class: Measurement
Managed Object Instance: measurement-ID defined in Measurement Object Class
File Creation: Time and date given in an ASCII format from tenth of second to year
Measurement Type: Measurement-Type (ex (110) for measurement type 110)
Total size: equal to (Record Size) * (Number of Records); Record Size is
measurement type dependent (see to 3.2.1 to 3.2.37)
Number of Records: Integer
Begin Collection Time: Time and date given in an ASCII format from tenth of second to year
End Collection Time: Time and date given in an ASCII format from tenth of second to year
Sample Percentage: Sample-Rate (value 0 to 100 or 255)
Sample Rate Reduced: Boolean
False = Sample rate not reduced
True = Sample rate reduced during reporting period

3.1.1 Physical layout of PGHR
Description
Layout (Intel) Octet Count

7 . . . . . . . . . . . bit . . . . . . . . . . 0
Header Bytes
integer - LSB 0

- MSB (not used) 1

Rec. Seq. Nbr.
Integer - LSB 2

- MSB 3

Record Type
integer 4
File Type
integer 5

BSS Version.
Integer - LSB 6

- MSB 7
BSC Release
integer 8

Filler
integer (FFh) 9





Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 14/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Managed Object
integer - LSB 10
Class (MOC)
- MSB (not used) 11

Managed Object
integer - LSB 12
Instance (MOI)
- MSB 13

File Creation 1 Character (tenth of sec.) 14
1 Character ( . ) 15
1 Character (sec) 16
1 Character (sec) 17
1 Character (min.) 18
1 Character (min.) 19
1 Character (hour)
20
1 Character (hour) 21
1 Character (day) 22
1 Character (day) 23
1 Character (month) 24
1 Character (month) 25
1 Character (year) 26
1 Character (year) 27
1 Character (year) 28
1 Character (year) 29



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 15/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Measurement-
integer - LSB 30
Type
- MSB (not used) 31

Total Size
integer - MSW, LSB 32

- MSW, MSB 33

- LSW, LSB 34

- LSW, MSB 35

Number of Rec.
Integer - LSB 36

- MSB 37

Begin Collect Time
(as above: File Creation) 38 53

End Collect Time
(as above: File Creation) 54 69

Filler
integer (FFh) 70

integer (FFh) 71

integer (FFh) 72

Sample Percentage
integer 73
Sample Rate Reduced
boolean 74
Filler
integer (FFh) 75


FFh

FFh

. . . . . . . . . . . . . . .


FFh

FFh



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 16/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2 PM Result File Formats
This paragraph describes the layout of the PM result files exchanged between the BSC and the OMC.

1. Counter Result Files:
Each type of counter data has its particular record data layout. File records are divided into
blocks of counters (e.g.: for global BSS or for cells). Every block is identified by an associated
BLOCK TYPE. The following description of the blocks in this document does not guarantee the
real order of the blocks in the PM file result. Nevertheless when a block type is split into several
blocks with the same measured object (since the size allowed for the counters defined in BCC for
the concerned block type is exceeded), these blocks are built for the same measured object
according the order of the definition of these blocks e.g. in PM type 110, block type for cell are
split into 5 blocks which are built in the following order 1110, 1120, 1122, 1123, 1126 for the
same cell. But some blocks could be missing according the BSC type or mode (even if mapped
on the same measured object than other blocks of the same PM type) e.g. when BSC is G2,
1126 block is not reported in the set of blocks of PM type 110 mapped on cell i.e. 1110, 1120,
1122, 1123.
A file header is present at the top of the file. It constitutes the first record (PGHR type record) of
the file.

2. Observation Result Files:
The collection of observation reports is executed autonomously. The observation file is
completed and notified to the OMC at the end of a measurement and in case of an intermediate
report is required. It has not a fixed length because the amount of observation data depends
strongly from the traffic assumptions and from the combination of sampling percentage and
number of observed objects.
As for counter result files, each type of observation data has its particular record data layout.
The file header has the same structure as for the counter result file header.

Notes on description layout contents:
0. Sometimes, a dummy byte (named FILLER) has been inserted to allow even length data
structures. This is done due to some constraints of the CHILL compiler that would have
troubles to handle odd length structures or blocks.
1. Dates and times are to be expressed as GeneralizedTime. If another representation is
required, the file sizes should be recomputed according to the changes of these fields.
2. Although from Release B6 each cell has up to 64 adjacent cells, we continue to provide data
for 16 cells within the measurement types 12 and 14 because the maximum record size of
256 bytes would be exceeded otherwise and because this limited number of cells is enough
according to the actual number of cells involved in the handover procedures observed.
3. Although from Release B6 each cell has up to 64 adjacent cells, we continue to provide data
for 32 cells within the measurement type 11 because the maximum record size of 256 bytes
would be exceeded otherwise.
4. CELL-ID, TRX-ID and CHANNEL-ID structure.
Those entries are used for most of the PM types and are laid out as follows:


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 17/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
CELL-ID: 2 bytes. In case the cell is shared between two BTSs, reference is always to the main
BTS and the main sector that is CELL-ID does not know about the cell being shared.
BTS-INDEX: 1 byte (1 255)
Sector Number: 1 byte (1 6)


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 18/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
TRX-ID: 3 bytes
CELL-ID: 2 bytes as above
TRX Number: 1 byte (1 MaxNbTRX) MaxNbTRX is 16 (thanks to cell shared feature).
In case of cell shared, the TRXs are numbered from 1 up to 16 without reference to them
being main or secundary TRXs, that is supported by a main or secundary sector.

CHANNEL-ID: 5 bytes
CELL-ID: 2 bytes as above
TRX Number: 1 byte as above
TRX TS: 1 byte (0 7)
Subchannel: 1 byte (0 or 1)

5. Counters in restriction: although described in the Counters Catalogue and referenced in
the tables, some counters may be in restriction for a given release (refer to the Counters
Catalogue); they may even not be implemented at all. As a convention, the corresponding
entry in the File Format table is to be filled with 0FFFFH value.

Records 1 to N of a Generic Performance Measurement File (GPMF) are called Generic Performance
Measurement Records (GPMR). They have the following layout:


System Record Header
(SRH) (see 2.2)


6 bytes
nbr of bytes 06
rec seq from 01 onwards
Record Type 03 (GPMR)
File Type 03 (GPMF)


PM Counter Results


See 3.2.1 to 3.2.9 and 3.2.16 to 3.2.36.

FILLER Remaining space in record
Records 1 to N of an Observation Performance Measurement File (OPMF) are called Observation
Performance Measurement Records (OPMR). They have the following layout:


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 19/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


System Record Header
(SRH) (see 2.2)


6 bytes
nbr of bytes 06
rec seq from 01 onwards
Record Type 09 (OPMR)
File Type 10 (OPMF)

Observation Results


See 3.2.10 to 3.2.15.

FILLER Remaining space in record



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 20/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.1 TYPE 1: TRAFFIC MEASUREMENTS
TYPE 1 is composed of a set of counters repeated for all the selected BSS cells and a set of counters
repeated for each TRX of the cells.

The result file has a variable number of records depending on the number (N) of selected cells and the
number of TRX within each cell.

For TYPE 1, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom. The size of the block of counters for
cells allows just one block per record.


BLOCK TYPE (011) 2B
BLOCK LENGTH (refer to documents [A] and [C]) 2B CELL COUNTERS
CELL-ID (BTS INDEX + Sect. Nb.) 2B repeated for each cell
Refer to documents [A] and [C]
..

BLOCK TYPE (012) 2B
BLOCK LENGTH (refer to documents [A] and [C]) 2B TRX COUNTERS
TRX-ID (BTS-INDEX+Sect. Nb.+TRX. Nb.) 3B repeated for each TRX
Filler 1B
Refer to documents [A] and [C]

..



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 21/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.1.1 Physical layout of contents of TYPE 01

Description
Layout (Intel) Octet Count

Cell counters (repeated N times)

7 . . . . . . . . . . . bit . . . . . . . . . . 0
Block Type
integer - LSB 0

integer - MSB 1
Block Length
integer - LSB 2

integer - MSB 3

BTS INDEX
integer (1 255) 4
Sector Number
integer (1 6) 5

C01
integer - MSW, LSB 5

- MSW, MSB 6

- LSW, LSB 8

- LSW, MSB 9



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 22/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


C02
integer - MSW, LSB 10

- MSW, MSB 11

- LSW, LSB 12

- LSW, MSB 13

C04
integer - MSW, LSB 14

- MSW, MSB 15

- LSW, LSB 16

- LSW, MSB 17

C07
integer - MSW, LSB 18

- MSW, MSB 19

- LSW, LSB 20

- LSW, MSB 21

. . . etc. for the remaining 4B counters . . .
and
7 . . . . . . . . . . . bit . . . . . . . . . . 0
Block Type
integer - LSB 0

integer - MSB 1
Block Length
integer - LSB 2

integer - MSB 3

BTS INDEX
integer (1 255) 4
Sector Number
integer (1 6) 5
TRX Number
integer (1 MaxNbTRX) 6

Filler 7




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 23/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
C621
integer - LSB 8

- MSB 9

. . . etc. for the remaining 2B counters . . .


Note: This is an example for Type 01 counters. The remaining counters for performance measurements are coded
in a similar manner.

Warning: The RMS counters (type 31) follow a different encoding scheme.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 24/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.2 TYPE 2: RESOURCE AVAILABILITY MEASUREMENTS
TYPE 2 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records depending on the number (N) of selected cells.

For TYPE 2, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (021) 2B
BLOCK LENGTH (refer to documents [A] and
[C])
2B
CELL COUNTERS
CELL-ID (BTS INDEX + Sect. Nb.) 2B
REPEATED N TIMES
Refer to documents [A] and [C]

Refer to documents [A] and [C]

3.2.3 TYPE 3: RESOURCE USAGE MEASUREMENTS CCCH
TYPE 3 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records depending on the number (N) of selected cells and
measured timeslots. For each selected cell, a first block contains validity information followed by as
many sub-blocks as CCCH TRX TSs managed by the cell during all or part of the observation period
(in the limit of 8 sub-blocks).

For TYPE 3, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (030) 2B
BLOCK LENGTH (2) 2B CELL COUNTERS
CELL-ID (BTS_IDX + Sect. Nb.) 2B REPEATED N TIMES

BLOCK TYPE (031) 2B
CCCH COUNTERS
BLOCK LENGTH (refer to documents [A] and
[C])
2B
REPEATED UP TO 8 TIMES
CCCH-ID (CELL_ID + TRX-nb + TRX-TS) 4B
Refer to documents [A] and [C]

Refer to documents [A] and [C]


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 25/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 26/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.4 TYPE 4: RESOURCE USAGE MEASUREMENTS SDCCH
TYPE 4 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records depending on the number (N) of selected cells and
measured timeslots. For each selected cell, a first block contains validity information followed by as
many sub-blocks as SDCCH TRX TSs managed by the cell during all or part of the observation period
(in the limit of 16 sub-blocks).

For TYPE 4, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (040) 2B
BLOCK LENGTH (2) 2B CELL COUNTERS
CELL-ID (BTS_IDX + Sect. Nb.) 2B REPEATED N TIMES

BLOCK TYPE (041) 2B
SDCCH COUNTERS
BLOCK LENGTH (refer to documents [A] and
[C])
2B
REPEATED UP TO 16 TIMES
DCCH-ID (CELL_ID + TRX-nb + TRX-TS) 4B
Refer to documents [A] and [C]
..
Refer to documents [A] and [C]



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 27/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.5 TYPE 5: RESOURCE USAGE MEASUREMENTS RTCH
TYPE 5 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records depending on the number (N) of selected cells and
measured timeslots. For each selected cell, a first block contains validity information followed by as
many sub-blocks as traffic channel TRX TSs managed by the cell during all or part of the observation
period (in the limit of 96 sub-blocks).

For TYPE 5, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (050) 2B
BLOCK LENGTH (2) 2B
CELL_ID (BTS_IDX + Sect. Nb.) 2B REPEATED N TIMES

BLOCK TYPE (051) 2B
RTCH COUNTERS
BLOCK LENGTH (refer to documents [A] and
[C])
2B
REPEATED UP TO 96 TIMES
RTCH-ID (CELL_ID + TRX-nb + TRX-TS) 4B


Refer to documents [A] and [C]

Refer to documents [A] and [C]



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 28/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.6 TYPE 6: RTCH HO MEASUREMENTS
TYPE 6 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records and blocks depending on the number (N) of selected
cells.

For TYPE 6, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.


BLOCK TYPE (060) 2B
BLOCK LENGTH (refer to documents [A] and [C]) 2B
CELL_ID (BTS INDEX + Sect. Nb.) 2B
Refer to documents [A] and [C]
CELL COUNTERS
.
REPEATED N TIMES
Refer to documents [A] and [C]



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 29/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.7 TYPE 7: LAPD MEASUREMENTS
TYPE 7 is composed of counters repeated for all the configured LAPD links of the BSS.
The result file has a variable number of records and blocks depending on the number of configured
LAPD links.
For TYPE 7, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.


BLOCK TYPE (071) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

LAPD-LINK-ID
5
4B
COUNTERS REPEATED
FOR
Refer to documents [A] and [C]
EVERY LAPD LINK
..
Refer to documents [A] and [C]

BLOCK TYPE (072) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

GSL-SBL 2B
COUNTERS REPEATED
Refer to documents [A] and [C] 4B
FOR EVERY GSL link

...
4B
Refer to documents [A] and [C] 4B
The counters are defined in TDM mode for GSL Transport with MFS at LAPD level.


5
The 4 bytes are as follows:
1 byte for unit number: BTS_IDX (1..255) for OML/RSL or TSC_IDX(1..3) for TSL;
2 bytes for Sbl-Type (can be RSL (43) or OML (42) or TSL (44));
1 byte for TEI number (=Sbl-Number).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 30/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.8 TYPE 8: X.25 MEASUREMENTS
TYPE 8 is composed of counters repeated for all the configured X25 links of the BSS.
The result file has 4 records for G2 BSC (covering CBC and O&M traffic) , one record for MxBSC (only
covering CBC traffic) with identification 1 (no CPRA id).

For TYPE 8, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.


BLOCK TYPE (081) 2B

BLOCK LENGTH (Refer to documents [A]
and [C])
2B

LINK-ID (CPRA LOGICAL ID) 2B

COUNTERS REPEATED FOR
Refer to documents [A] and [C]

EVERY X.25 LINK


Refer to documents [A] and [C]




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 31/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.9 TYPE 9: No.7 MEASUREMENTS
TYPE 9 is composed of counters repeated for all equipped N7 links and some other counters relate to
all defined Link sets of the BSS.
The result file has a variable number of records and blocks depending on the number of equipped N7
links and Link sets.
For TYPE 9, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.
When A-signalling link over IP is enabled
6
, the OMC doesnt activate the BSC for PM type 9. Defence on
BSC side if PM type 9 is activated for an Mx BSC with A-signalling link over IP enabled: it is however
forecasted that the BSC provides to the OMC only the file header in the PM type 9 file result.

The link-Id for block 091 is the identification of the N7 Signalling link.
- In case of LSL, the link-Id gives the CIC code composed of: high weight which represents the trunk-Id on
11 bits and the TS on 5 bits which is always 16.
- In case of HSL, the link-Id gives the SLC (Signaling Link Code) which represents the entire N7 trunk: a
number from 0 to 15 or from 1 to 15 depending on operator choice.
The link_Id blocks based on SLC or CIC are not ordered (increasing or decreasing) .



BLOCK TYPE (091) 2B
BLOCK LENGTH (refer to documents [A] and
[C])
2B
LINK-ID 2B
SL COUNTERS
Refer to documents [A] and [C]
REPEATED FOR
..
EVERY N7 SL
Refer to documents [A] and [C]


BLOCK TYPE (093) 2B

BLOCK LENGTH (refer to documents [A] and
[C])
2B
LINK_SET_ID 2B
LS COUNTERS
Refer to documents [A] and [C] REPEATED FOR
..
EVERY LS
Refer to documents [A] and [C]


6
Therefore in case A User Plane over IP feature is enabled.



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 32/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.10 TYPE 10: SDCCH OBSERVATION
TYPE 10 is composed of a variable sequence of observation blocks, all of them having the same fixed
format.

For this measurement type a record size of 76 bytes is defined. Every file record is filled with only one
complete observation block. The file is composed of a variable number of records depending on the
number of observed transaction during the collection period.

Remark: Because of the PGHR record header size, the record size is greater than a block size.

BLOCK TYPE (100) 2B
BLOCK LENGTH (60) 2B
S01 CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
FILLER 1B
S02 CHAN_SEIZ_TIME
7
16B
S03 CHAN_RELEASE_TIME
7
16B
S04 END_INDICATION 1B
S05 SEIZURE_TYPE 1B
S06 MS_POWER 2B
S07 BS_POWER 2B
S08 TIMING_ADVANCE 2B
S09 NBR_FRAMES_NOT_REPEATED 2B
S16 NBR_FRAMES_REPEATED 2B
S17 NBR_OF_SABM_AFTER_UA_SENT 1B
S18 NBR_OF_PHYSICAL_INFO_SENT 1B
S19 NBR_OF_ERRONEOUS_FRAMES_SENT 1B
S20 NBR_OF_REJ_FRAMES_SENT 1B
S21 NBR_OF_REJ_FRMES_RECEIVED 1B
S22 NBR_OF_MS_TX_PWR_MAX_SENT 1B
S23 RADIO_LINK_FAILURE_INDICATION 1B
S24 PERC_OF_INCOR_SACCH_FRAMES_RX 1B
S25 PERC_OF_INCOR_NOT_SACCH_FM_RX 1B
S26 SAMPLE_RATE 1B



7
Time and date given in an ASCII format from tenth of second to year (see physical layout of PGHR in 3.1.1).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 33/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.11 TYPE 11: RTCH MEASUREMENTS OBSERVATION
TYPE 11 is composed of a variable sequence of observation blocks, all of them having the same fixed
format.

For this measurement type a record size of 246 bytes is defined. Every file record is filled with only one
complete observation block. The file is composed of a variable number of records depending on the
number of observed transactions during the collection period.
The R01 to R12, R04a, R05a, R17 are observations for the serving cell.
The Ri13 to Ri16 observations are observations for the 2G neighbour cells, with i=1 to 32
The Rj18 to Rj20 observations are observations for the 3G neighbour cells , with j=1 to 8


BLOCK TYPE (110) 2B
BLOCK LENGTH (236) 2B
R01 CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
R01a RTCH_TYPE 1B
R03 RCVD_TIMESTAMP
7
16B
R04 AV_RXLEV_UL_HO 1B
R05 AV_RXLEV_DL_HO 1B
R06 AV_RXLEV_PBGT_HO 1B
R07 AV_RXQUAL_UL_HO 1B
R08 AV_RXQUAL_DL_HO 1B
R09 AV_RANGE_HO 1B
R10 MS_TXPWR 1B
R11 BS_TXPWR 1B
R12 BTSNUM 1B
FILLER 1B
R113 BSIC
8
(1) 1B
R114 BCCH_FREQ
9
(1) 2B
R115 AV_RXLEV_NCELL (1) 1B
R116 PBGT(1) 1B
R213 BSIC (2) 1B
R214 BCCH_FREQ
9
(2) 2B

8
The BSIC is a 6-bits value comprising of the National Colour Code (NCC) and Base-station Colour Code
(BCC) which is padded out to 8 bits, as indicated below:

Bit 7 6 5 4 3 2 1 0
Content 0 0 N C C B C C

Note: It is displayed at the OMC-R operator as two separate values.
9
The BCCH frequency is coded as the absolute radio frequency (0 1023).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 34/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
R215 AV_RXLEV_NCELL (2) 1B
R216 PBGT (2) 1B

. . . . . . . . . . .

Filled with
FFh values because only
16 possibles
neighbours.

R3213 BSIC
7
(32) 1B
R3214 BCCH_FREQ
9
(32) 2B

R3215 AV_RXLEV_NCELL (32) 1B
R3216 PBGT (32) 1B
R04a AV_RXLEV_UL_MCHO 1B
R05a AV_RXLEV_DL_MCHO 1B
R17 SAMPLE_RATE 1B
FILLER 1B
R118 SCRAMBLING_CODE 2B
R119 FDD_FREQ 2B
R120 AV_ECNO 1B

. . . . . . . . . . .

SCRAMBLING_CODE 2B
FDD_FREQ 2B
AV_ECNO 1B

. . . . . . . . . . .

R818 SCRAMBLING_CODE 2B
R819 FDD_FREQ 2B
R820 AV_ECNO 1B





Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 35/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.12 TYPE 12: INTERNAL HANDOVER OBSERVATION
TYPE 12 is composed of a variable sequence of observation blocks, all of them having the same
format.
For this measurement type a record size of 202 bytes is defined. Every file record is filled with only one
complete observation block. The file is composed of a variable number of records depending on the
number of observed handovers during the collection period.

BLOCK TYPE (120) 2B
BLOCK LENGTH (192) 2B
HO1 SIGNALLING/TRAFFIC_INDIC 1B
HO2 INTRA/INTER-CELL_INDICATION 1B
HO3 HO_REQUIRED_TIME_STAMP
7
16B
HO5 OLD_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
HO5a OLD_RTCH_TYPE 1B
HO6 NEW_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
HO6a NEW_RTCH_TYPE 1B
HO7 INT_HO_SUCCESS_FAILURE_IND 1B
HO8 HO_DURATION 2B
HO11 HO_CAUSE 1B
HO12 SYNCHRONIZED 1B
HO23 A_LEV_HO 1B
HO25 AV_RXLEV_UL_HO 4B
HO26 AV_RXLEV_DL_HO 4B
HO27 A_PBGT_HO 1B
FILLER 1B
HO29 AV_RXLEV_PBGT_HO 4B
HO30 A_QUAL_HO 1B
FILLER 1B
HO32 AV_RXQUAL_UL_HO 4B
HO33 AV_RXQUAL_DL_HO 4B
HO34 A_RANGE_HO 1B
FILLER 1B
HO36 AV_RANGE_HO 4B
HO37 MS_TXPWR 1B
HO38 BS_TXPWR 1B
Honn47 BSIC
8
1B
REPEATED
Honn48 FREQ 2B
16 TIMES
10

Honn49 RXLEV 4B
FILLER
1B
HO23a A_LEV_MCHO 1B

10
These 3 fields contain information related to an adjacent cell; they are repeated for 16 possible adjacent cells
only due to memory constraint. If info for less than 16 adjacent cells are available, the non used groups of fields
are filled in with dummy values (Hex FF FFFF FFFFFFFF).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 36/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

HO25a AV_RXLEV_UL_MCHO 4B
HO26a AV_RXLEV_DL_MCHO 4B
HO74 SAMPLE_RATE 1B
HO75 MS_SPEED 1B

3.2.13 TYPE 13: INCOMING HANDOVER OBSERVATION
TYPE 13 is composed of a variable sequence of observation blocks, all of them having the same
format.

For this measurement type a record size of 76 bytes is defined. Every file record is filled with only one
complete observation block. The file is composed of a variable number of records depending on the
number of observed handovers during the collection period.

Remark: Because of the PGHR record header size, the record size is greater than a block size.

BLOCK TYPE (130) 2B
BLOCK LENGTH (28) 2B
HO40 SIGNALING/TRAFFIC_INDIC 1B
HO41 INCOMING_HO_INDICATION 1B
HO42 HO_REQUEST_TIME_STAMP (BSS Clock) 16B
HO43 NEW_CHAN_ID (CELL_ID + TRX-nb + TRX-TS +SUBCH.) 5B
HO43a NEW_RTCH_TYPE 1B
HO44 INC_EXT_HO_SUCCESS_FAILURE_IND 1B
HO45 SYNCHRONISED 1B
HO46 SAMPLE_RATE 1B
FILLER 1B




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 37/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.14 TYPE 14: OUTGOING HANDOVER OBSERVATION
TYPE 14 is composed of a variable sequence of observation blocks, all of them having the same
format.

For this measurement type a record size of 238 bytes is defined. Every file record is filled with only one
complete observation block. The file is composed of a variable number of records depending on the
number of observed handovers during the collection period.
The HOj101 to HOj103 observations are observations for the 2G -> 3G HO , with j=1 to 8
The other observations are dedicated to the 2G >2G HO

BLOCK TYPE (140) 2B
BLOCK LENGTH (228) 2B
HO60 SIGNALLING/TRAFFIC_INDIC 1B
HO61 OUTGOING_HO_INDICATION 1B
HO62 HO_REQUIRED_TIME_STAMP
7
16B
HO63 HO_REQUIRED_NBR 2B
HO64 OLD_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
HO64a OLD_RTCH_TYPE 1B
HO65 OUT_EXT_HO_SUCCESS_FAILURE_IND 1B
HO68 HO_CAUSE 1B
FILLER 1B
HO80 A_LEV_HO 1B
HO82 AV_RXLEV_UL_HO 4B
HO83 AV_RXLEV_DL_HO 4B
HO84 A_PBGT_HO 1B
FILLER 1B
HO86 AV_RXLEV_PBGT_HO 4B
HO87 A_QUAL_HO 1B
FILLER 1B
HO89 AV_RXQUAL_UL_HO 4B
HO90 AV_RXQUAL_DL_HO 4B
HO91 A_RANGE_HO 1B
FILLER 1B
HO93 AV_RANGE_HO 4B
HO94 MS_TXPWR 1B
HO95 BS_TXPWR 1B
Honn98 BSIC
8
1B
REPEATED 16
Honn99 FREQ 2B TIMES
10

Honn100 RXLEV 4B
FILLER 1B
HO80a A_LEV_MCHO 1B
HO82a AV_RXLEV_UL_MCHO 4B
HO83a AV_RXLEV_DL_MCHO 4B


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 38/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
HO111 SAMPLE_RATE 1B
HO76 MS_SPEED 1B
FILLER 1B
HO1101 SCRAMBLING_CODE 2B
HO1102 FDD_FREQ 2B
HO1103 AV_ECNO 1B

. . . . . . . . . . .

SCRAMBLING_CODE 2B
FDD_FREQ 2B
AV_ECNO 1B

. . . . . . . . . . .

HO8101 SCRAMBLING_CODE 2B
HO8102 FDD_FREQ 2B
HO8103 AV_ECNO 1B
FILLER 1B
3.2.15 TYPE 15: TCH OBSERVATION
TYPE 15 is composed of a variable sequence of observation blocks, all of them having the same
format.

For this measurement type a record size of 76 bytes is defined. Every file record is filled with only one
complete observation block. The file is composed of a variable number of records depending on the
number of observed transactions during the collection period.

BLOCK TYPE (150) 2B
BLOCK LENGTH (60) 2B
T01 CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
T01a RTCH_TYPE 1B
T02 CHAN_SEIZ_TIME
7
16B
T03 CHAN_RELEASE_TIME
7
16B
T04 END_INDICATION 1B
T04a SEIZURE_TYPE 1B
T05 MS_POWER 2B
T06 BS_POWER 2B
T07 TIMING_ADVANCE 2B
T08 NBR_FRAMES_NOT_REPEATED 2B
T15 NBR_FRAMES_REPEATED 2B
T16 NBR_OF_SABM_AFTER_UA_SENT 1B
T17 NBR_OF_PHYSICAL_INFO_SENT 1B
T18 NBR_OF_ERRONEOUS_FRAMES_SENT 1B
T19 NBR_OF_REJ_FRAMES_SENT 1B


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 39/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

T20 NBR_OF_REJ_FRMES_RECEIVED 1B
T21 NBR_OF_MS_TX_PWR_MAX_SENT 1B
T22 RADIO_LINK_FAILURE_INDICATION 1B
T23 PERC_OF_INCOR_SACCH_FRAMES_RX 1B
T24 PERC_OF_INCOR_NOT_SACCH_FM_RX 1B
T25 SAMPLE_RATE 1B

3.2.16 TYPE 16: (NOT USED)

3.2.17 TYPE 17: (NOT USED)




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 40/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.18 TYPE 18: A INTERFACE MEASUREMENTS
TYPE 18 is composed of global counters related to the whole BSS and counters related to the A
interfaces of the BSS.
For this measurement type a record size of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (180) 2B
BLOCK LENGTH (refer to documents [A] and [C]) 2B
Refer to documents [A] and [C]

Refer to documents [A] and [C]

BLOCK TYPE (181) 2B Repeated for each
BLOCK LENGTH (Refer to documents [A] and [C]) 2B A channel
LINK-ID (CIC) 2B
Refer to documents [A] and [C]
..
Refer to documents [A] and [C]
Not reported when A-interface is fully based on IP (i.e. Full AUPoIP) in case A User Plane over IP
feature is enabled.
NB: Full CS Achannel or mixed CS/PS Achannel: the TS 1 -> TS31 is reported in the Achannel
3.2.19 TYPE 19: SMS MEASUREMENTS
TYPE 19 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records and blocks depending on the number (N) of selected
cells.

For TYPE 19, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (190) 2B
BLOCK LENGTH (Refer to documents [A]
and [C])
2B
CELL_ID (BTS_IDX + Sect. Nb.)
Refer to documents [A] and [C]
CELL COUNTERS
.. Repeated N times
Refer to documents [A] and [C]



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 41/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.20 TYPE 20 to 24: (NOT USED)

3.2.21 TYPE 25: SCCP MEASUREMENTS
TYPE 25 is composed of counters repeated for all the equipped N7 signalling links of the BSS.
The result file has a variable number of records and blocks depending on the number of equipped N7
signalling links in the BSS.
For TYPE 25, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.
When A-signalling link over IP is enabled
11
, the OMC doesnt activate the BSC for PM type 25. Defence on
BSC side if PM type 25 is activated for an Mx BSC with A-signalling link over IP enabled: it is however
forecasted that the BSC provides to the OMC only the file header in the PM type 25 file result.

The link-Id is the identification of the N7 Signalling link.
- In case of LSL, the link-Id gives the CIC code composed of: high weight which represents the trunk-Id on
11 bits and the TS on 5 bits which is always 16.
- In case of HSL, the link-Id gives the SLC (Signaling Link Code) which represents the entire N7 trunk: a
number from 0 to 15 or from 1 to 15 depending on operator choice.
The link_Id blocks based on SLC or CIC are not ordered (increasing or decreasing) .



BLOCK TYPE (251) 2B
BLOCK LENGTH (refer to documents [A]
and [C])
2B
LINK-ID 2B
Refer to documents [A] and [C] 4B
REPEATED FOR
. 4B
EVERY N7 SL
Refer to documents [A] and [C] 4B

3.2.22 TYPE 26: DETAILED HO MEASUREMENTS FOR A SERVING CELL
TYPE 26 is composed of counters repeated for all the cells adjacent to the cell specified by the
operator.
The result file has a variable number of records and blocks depending on the number of adjacent cells.
There is one block 261 only if handover took place on the adjacency.
There is one block 260 if there is at least one record 261.

11
Therefore in case A User Plane over IP feature is enabled.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 42/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
For TYPE 26, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.
Remark: The record number 1 of the result file contains at the beginning a block specifying the
identity of the serving cell under measurement.

BLOCK TYPE (260) 2B
global block
BLOCK LENGTH (2) 2B
only in the record
SERVING CELL_ID (BTS_IDX + Sect. Nb.) 2B
number 1

BLOCK TYPE (261) 2B
repeated up to 64 times
BLOCK LENGTH (Refer to documents [A] and [C]) 2B
(i.e. per adjacent cell
MCC_MNC 3B
identified by
MCC+MNC+LAC+CI)
FILLER 1B

LAC 2B

CI 2B

Refer to documents [A] and [C]
.
Refer to documents [A] and [C]

Remark on MCC_MNC coding

MCC and MNC are coded each one on 3 * 4 bits ( one digit on 4 bits). MCC is coded the first and then
MNC.
The coding of MCC_MNC over the 3 octets is the following:
If MCC= d1d2d3 and MNC= d1d2d3 with d=digit

8 7 6 5 4 3 2 1
MCC d2 MCC d1 Octet 1
MNC d3 MCC d3 Octet 2
MNC d2 MNC d1 Octet 3
In case of 2 digits for MNC the bits 5 to 8 of octet 2 shall be coded as "1111"
Example: MCC=246 and MNC=81, the coding is: 42 F6 18


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 43/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.23 TYPE 27: DETAILED HO MEASUREMENTS FOR A TARGET CELL
TYPE 27 is composed of counters repeated for all the serving cells from which handovers are received
for the cell specified by the operator (target cell).

The result file has a variable number of records and blocks depending on the number of adjacent cells.
There is one block 271 only if handover took place on the adjacency.
There is one block 270 if there is at least one record 271.

For TYPE 27, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.

Remark: The record number 1 of the result file contains at the beginning a block specifying the
identity of the target cell under measurement.

BLOCK TYPE (270) 2B
global block
BLOCK LENGTH (2) 2B
only in the record
TARGET CELL_ID (BTS_IDX + Sect. Nb.) 2B
number 1

BLOCK TYPE (271) 2B repeated up to N times
12

BLOCK LENGTH (Refer to documents [A] and [C]) 2B
(i.e. per adjacent cell
MCC_MNC 3B
identified by MCC+MNC
lac+ci)
FILLER 1B

LAC 2B

CI 2B

Refer to documents [A] and [C]



Refer to documents [A] and [C]


Remark on MCC_MNC coding:
Refer to type 26.

3.2.24 TYPE 28: SDCCH HO MEASUREMENTS
TYPE 28 is composed of counters repeated for all the selected BSS cells.

12
N is the maximum own cells per BSC MAX-CELL defined in [6] (e.g. 264 for G2 BSC or 500 for Mx BSC).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 44/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

The result file has a variable number of records and blocks depending on the number of selected cells.

For TYPE 28, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.


BLOCK TYPE (280) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B

CELL_ID (BTS INDEX + Sect. Nb.) 2B


Refer to documents [A] and [C]

CELL COUNTERS


REPEATED N TIMES
Refer to conter catalog





Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 45/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.25 TYPE 29: DIRECTED RETRY MEASUREMENTS
TYPE 29 is composed of counters repeated for all the selected BSS cells.

The result file has a variable number of records and blocks depending on the number of selected cells.

For TYPE 29, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (290) 2B
BLOCK LENGTH (Refer to documents [A] and [C]) 2B
CELL-ID (BTS INDEX + Sect. Nb.) 2B
Refer to documents [A] and [C]
CELL COUNTERS

REPEATED N TIMES
Refer to documents [A] and [C]

3.2.26 TYPE 30: SHORT MESSAGE SERVICE CELL BRODCAST MEASUREMENTS
TYPE 30 is composed of global counters related to the whole BSS.

For this measurement type a record size of 256 bytes is defined.

BLOCK TYPE (300) 2B
BLOCK LENGTH (Refer to documents [A] and [C]) 2B
Refer to documents [A] and [C]

Refer to documents [A] and [C]

3.2.27 TYPE 31: RADIO MEASUREMENTS STATISTICS
TYPE 31 contains the parameters and the counters of the Radio Statistics Measurements for the all
cells or a list of cells of the BSC.
There is one file per BSC, it contains a number of blocks depending on the variable number of selected
cells and the number of TRXs and neighbour cells of the cell. The number of blocks is also variable
(refer to the note related to the AMR and TA blocks).
The counters are set to 0 in the result file if the feature is not activated.
The block types organisation in the file is a three levels structure:


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 46/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
a cell level structure repeated for each cell
within the cell structure, a TRX structure repeated for each TRX of the cell
within the TRX structure, a repetition for each neighbour cell and EMO frequency attached to the
cell.
The first block type of the cell structure contains the Radio Measurement Statistics general cell
information (parameters of the RMS plus global results at cell level).
The following block types of the cell structure contain the results for each TRX plus indications on
events occurred during the job on the TRX like a RMS restart, partial results or an overload; these
blocks are repeated for each TRX of the cell.
For RMS, parameters are reported back to the OMC-R, in addition to the counters resulting from
measurements. For information on the parameters refer to the document ref [B].
Some of the parameters and results fields are tables. There are several types of tables:

Table of parameters TAB_PAR_X table of one dimension which sequence is:
PAR_X(0) 1B Example of use: TAB-PAR_MEAS_LEVEL
PAR_X(1) 1B
.
PAR_X(N) 1B

Table of results with X(i) characteristics [i stands for columns of the vector], TPR_X table of one
dimension which sequence is below.
PR_X(0) 1B Example of use: TPR_CIN, TPR_CIF
PR_X(1) 1B
.
PR_X(N) 1B


Table of results with X(I) and Y(j) characteristics, TPR_X_Y, table of two dimensions (X stands for the
columns and Y for the rows i.e. RXLEV, of the matrix, as given in [10]) which sequence is:
PR_XY(0,0) 1B or 3B Example of use: TPR_BFI_RXLEV_UL (1 B)
PR_XY(1,0) - - TPR_RXQUAL_DL_RXLEV_DL (3 B)
.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 47/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

PR_XY(M,0) For 3 bytes entries the order is Ci, PWRi, TAi
PR_XY(0,1)
PR_XY(1,1)
.
PR_XY(M,N) - -

The tables TPR-RXQUAL_UL_RXLEV_UL and TPR-RXQUAL_DL_RXLEV_DL follow this pattern
where each item is 3B long.

Table of Maximum of results with, on all X(i) characteristics [consider all columns] with Y(j)
characteristics [RXLEV rows], TMR_X_Y, table of one dimension which sequence is Max XY(j)
MR_XY(0) 4B Example of use: TMR_RXQUAL_UL_RXLEV_UL
MR_XY(1) 4B
.
MR_XY(N) 4B

The tables of percentage results and maximum results allow to calculate the number of results by the
formula: R_XY(i,j) = PR_XY(i,j) * MR_ XY(j) /254.

Note on the Physical layout for TYPE 31: In order to avoid bytes transposition by the BSC, the order
of bytes within a 2 bytes or 4 bytes result is the order specified on the A-bis interface (which differs
from the usual order specified in the File Format for other PM results).
- for 2 bytes: MSB , LSB
- for 4 bytes: (MSW, MSB), (MSW, LSB), (LSW, MSB), (LSW, LSB).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 48/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
This applies to the data part of the blocks not to the headers prepared by the BSC (indicated by a
vertical line in the margin) nor to the filler.

BLOCK TYPE (3100) RMS-CELL 2B
REPEATED FOR EACH CELL
BLOCK LENGH (72) 2B
CELL_ID(BTS-INDEX + Sect. Nb. ) 2B
RMSpt5 TAB_PAR_MEAS_LEVEL 9B
Table of 9 parameters
Alignment-Filler-Byte 1B

RMSpt1 TAB_PAR_MEAS_C/I 9B
Table of 9 parameters
Alignment-Filler-Byte 1B

RMSpt2 TAB_PAR_MEAS_STAT_BFI 9B
Table of 9 parameters
Alignment-Filler-Byte 1B

RMSpt3 TAB_PAR_MEAS_STAT_S 9B
Table of 9 parameters
Alignment-Filler-Byte 1B

RMSpt4 TAB_PAR_MEAS_PATH_BALANCE 9B
Table of 9 parameters
Alignment-Filler-Byte 1B

RMSpt6 TAB_PAR_MEAS_STAT_TA 9B
Table of 9 parameters
Alignment-Filler-Byte 1B

RMSpa PAR-EN-BALANCED-CI 1B
Boolean
RMSpb PAR_TA_STAT 1B
RMSpc PAR_VQ_AVERAGE 1B
RMSpd PAR_VQ_RXLEV 1B
RMSpe PAR_VQ_RXQUAL 1B
RMSpf PAR_VQ_RXQUAL_VS_RXFER 1B
RMSpg PAR_VQ_GOOD_RXFER 1B
RMSph PAR_VQ_BAD_RXFER 1B
RMSpi PAR_VQ_INTF_THRESHOLD 1B


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 49/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

RMSpj PAR_VQ_FER_THRESHOLD 1B


BLOCK TYPE (3110) RMS-TRX 2B
REPEATED FOR EACH TRX
BLOCK LENGH (135) 2B
for N=1 to MaxNbrTRX

TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B
REPEATED
FOR EACH
CELL
Alignment-Filler-Byte 1B



RMS20 TRE_BAND 1B
Refer to note 1 for coding


RMS22 IND_RMS_RESTARTED 1B Boolean

RMSpw1 BS_TX_PWRMAX
13
1B



RMSpw2 MS_TX_PWRMAX
13
1B

RMS21 IND_TRE_OVERLOAD 1B Boolean
RMS23 IND_CI_PARTIAL_OBSERVATION 1B 2 bits, Refer to note 2 for
coding

RMS24 IND_CI_OVERFLOW 1B Boolean

RMS31 TOT_SEIZ_TCH 4B
RMS32 TOT_MEAS 4B
RMS33 TOT_MEAS_L1INFO_NOL3INFO 4B
RMS34 TOT_MEAS_DTX_UL 4B
RMS35 TOT_MEAS_DTX_DL 4B
RMS36 PERC_TA_GT_TA_STAT 1B
RMS37 MAX_ TA 1B



RMS38 TOT_EMR 4B



RMS10 VQ_NOISY_UL_INTERFERENCE 2B

RMS11 VQ_NOISY_DL_INTERFERENCE 2B


13
BSC shall select the value for inner or outer in case of concentric cell


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 50/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

RMS12 VQ_NOISY_UL_COVERAGE 2B

RMS13 VQ_NOISY_DL_COVERAGE 2B

RMS14 VQ_NOISY_UL_UNDEFINED 2B

RMS15 VQ_NOISY_DL_UNDEFINED 2B

RMS16 VQ_NOISY_UL_BAD_FER 2B

RMS17 VQ_NOISY_UL_GOOD_FER 2B

RMS18 VQ_ABNORMAL_BAD_FER 2B

RMS3b TMR_RXQUAL_UL_RXLEV_UL 40B
Table of 10 Maximum results
RMS4b TMR_RXQUAL_DL_RXLEV_DL 40B
Table of 10 Maximum results


BLOCK TYPE (3115) RMS-BFI 2B
REPEATED FOR EACH TRX
BLOCK LENGH (172) 2B


REPEATED
FOR EACH
CELL
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMS5a TPR_BFI_RXLEV_UL 100B
Table of 10 X 10 results
RMS5b TMR_BFI_RXLEV_UL 40B
Table of 10 Maximum results
RMS6a TPR_RADIO_LINK 10B
Table of 10 1B results
RMS6b MAX_RADIO_LINK 4B

RMS7a TPR_PATH_BALANCE 10B
Table of 10 1B results
RMS7b MAX_PATH_BALANCE 4B


BLOCK TYPE (3111) RMS-UL 2B
BLOCK LENGH (244) 2B
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMS3a TPR_RXQUAL_UL_RXLEV_UL 240B
Table of 8 X 10 results with 3B
per result



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 51/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

BLOCK TYPE (3112) RMS-DL 2B
BLOCK LENGH (244) 2B
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMS4a TPR_RXQUAL_DL_RXLEV_DL 240B
Table of 8 X 10 results with 3B
per result



BLOCK TYPE (3116)
RMS-BFI-AMR, RMS-TA
2B
REPEATED FOR EACH TRX
BLOCK LENGH (121) 2B


REPEATED
FOR EACH
CELL
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMS50a TPR_TIMING_ADVANCE 10B Table of 10 1B results

RMS50b MAX_TIMING_ADVANCE 4B

RMS51 TPR_UL_RXLEV_TA_BAND 20B Table of 10 2B results

RMS52 TPR_DL_RXLEV_TA_BAND 20B Table of 10 2B results

RMS53 TPR_UL_RXQUAL_TA_BAND 20B Table of 10 2B results

RMS54 TPR_DL_RXQUAL_TA_BAND 20B Table of 10 2B results

RMS44a AMR_FR_UL_BAD 8B Table of 8 1B results

RMS44b MAX_AMR_FR_UL_BAD 4B

RMS45a AMR_HR_UL_BAD 5B Table of 5 1B results

RMS45b MAX_AMR_HR_UL_BAD 4B

RMSPw3 MAX_POWER_PER_TRX * 2B

*: If the feature (Unbalancing TRX output power per BTS sector ) is activated, the counter shall be set, by the
BTS, to the power required by the BSC for the corresponding TRE (TRE on which the TRX is mapped).



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 52/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

BLOCK TYPE (3117)
RMS-AMR-UL
2B
REPEATED FOR EACH TRX
BLOCK LENGH (214) 2B


REPEATED
FOR EACH
CELL
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMS46a AMR_FR_UL_RXLEV_UL 80B Table of 10 X 8 results

RMS46b MAX_AMR_FR_UL_RXLEV_UL 40B Table of 10 maximum
results

RMS48a AMR_HR_UL_RXLEV_UL 50B Table of 10 X 5 results

RMS48b MAX_AMR_HR_UL_RXLEV_UL 40B Table of 10 maximum
results


BLOCK TYPE (3118)
RMS-AMR-DL
2B
REPEATED FOR EACH TRX
BLOCK LENGH (214) 2B


REPEATED
FOR EACH
CELL
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMS47a AMR_FR_DL_RXLEV_DL 80B Table of 10 X 8 results

RMS47b MAX_AMR_FR_DL_RXLEV_DL 40B Table of 10 maximum
results

RMS49a AMR_HR_DL_RXLEV_DL 50B Table of 10 X 5 results

RMS49b MAX_AMR_HR_DL_RXLEV_DL 40B Table of 10 maximum
results



BLOCK TYPE (3119)
RMS-BFI-WB-AMR, RMS-WB-AMR-UL,
RMS-WB-AMR-DL
2B REPEATED FOR EACH
TRX
BLOCK LENGH (151) 2B
REPEATED
FOR EACH
CELL
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 53/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Alignment-Filler-Byte 1B
Rms41a AMR_WB_GMSK_FR_UL_BAD 3B Table of 3 results
Rms41b MAX_AMR_WB_GMSK_FR_UL_BAD 4B 1 maximum result
Rms42a AMR_WB_GMSK_FR_UL_RXLEV_UL 30B Table of 10 X 3 results
Rms42b MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL 40B Table of 10 maximum
results

Rms43a AMR_WB_GMSK_FR_DL_RXLEV_DL 30B Table of 10 X 3 results
Rms43b MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL 40B Table of 10 maximum
results



BLOCK TYPE (3120) RMS-CIN 2B
from one to 11 times
BLOCK LENGH (242 max) 2B (min 0, max 154 cells
14
)

TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B



RMSp80 NEIGB_CELL_ID(BCCH_ARFCN
9
, 2B Repeated up to 14 times
15


BSIC
8
) 1B
with no inserted filler


RMS8a TPR_CIN 10B
CI Vector


RMS8b MR_CIN 4B
Maximum result



BLOCK TYPE (3121) RMS-CIF 2B
from zero to two times
BLOCK LENGH (244max) 2B
(max 21 EMO ARFNs)


TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) 3B

Alignment-Filler-Byte 1B




14
The actual maximum number, RMS_BCCH_BSIC_NB, of measured neighbour frequencies reported by the BTS to the BSC is a
configurable value up to 154 if the RMS improvement is enabled with EN_MORE_RMS_BCCH_BSIC flag otherwise it is 42 (cf. [2]).
15
This data is prepared by the BTS/TRE: the blocks are repeated without inserted filler.The last repetition (if is not the 14 th or
15 th) is followed by a 4B filler, put in place by the BSC) instead of a neighbour cell or EMO frequency identity. In this case the
block length is adapted to cover only the significant data before the filler.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 54/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

RMSp90 Frequency ARFCN 2B Repeated up to 15 times
15

END
RMS9a TPR_CIF 10B
CI vector for END FOR
RMS9b MR_CIF 4B
Maximum result TRX CELL

Note related to Block 3121: this block is reported if the MAFA function is activated.
Note 1: Frequency band of the TRX. (TRE_BAND)

The frequency band of the TRX is encoded as follows:
00: The frequencies defined are those available for a P-GSM TRX (See the external comment)
01: The frequencies defined are those available for a DCS1800 TRX (See the external comment)
02: The frequencies defined are those available for an E-GSM band (See the external comment)
03: The frequencies defined are those available for a DCS1900 TRX
04: Not used
05: Not used
06: The frequencies defined are those available for a GSM850 TRX (See the external comment)


External comment

The term E-GSM TRX refers to:
i. a TRX configured with all the frequencies belonging to the G1 band in an E-GSM cell (i.e.
a cell where FREQUENCY_RANGE is set to EGSM or E-GSM-DCS1800) if the
EGSM_RR_ALLOC_STRATEGY parameter is set to Same behaviour for E-GSM capable MS, or,
ii. a TRX configured with all the frequencies belonging to the E-GSM band in an E-GSM cell
(i.e. a cell where FREQUENCY_RANGE is set to EGSM or E-GSM-DCS1800) if the
EGSM_RR_ALLOC_STRATEGY parameter is set to Same behaviour for E-GSM capable MS.
The term P-GSM TRX refers to a TRX configured with all the frequencies belonging to the P-GSM band:
i. in an E-GSM cell (i.e. a cell where FREQUENCY_RANGE is set to EGSM or EGSM-
DCS1800) if the EGSM_RR_ALLOC_STRATEGY parameter is set to Different behaviour
for E-GSM capable MS
ii. in a P-GSM cell (i.e. a cell where FREQUENCY_RANGE is set to PGSM or PGSM-
DCS1800).
The term DCS1800 TRX refers to a TRX configured with frequencies belonging to the DCS1800 band (i.e. a
cell where FREQUENCY_RANGE is set to DCS1800, PGSM-DCS1800 or EGSM-DCS1800)
The term DCS1900 TRX refers to a TRX configured with frequencies belonging to the DCS1900 band (i.e. a
cell where FREQUENCY_RANGE is set to DCS1900
The term GSM850 TRX refers to a TRX configured with frequencies belonging to the GSM850 band (i.e. a
cell where FREQUENCY_RANGE is set to GSM850



Note 2: coding of the IND_CI_PARTIAL_OBSERVATION


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 55/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Bit map indicating that the measurements (for and only for CI vector computation) are on either NMR ("Normal"
Measurements Reports) or on EMR (Extended Measurements Reports) or on both or none were RESTARTED
during RMS job duration.
This counter is encoded as follows:
0: no CI partial result
1: EMO/EMR CI partial result
2: NMR CI partial result
3: EMR and NMR partial result

3.2.28 TYPE 32: Change of frequency band measurements
This type of counters allow to observe handovers between different frequency band.
TYPE 32 is composed of counters repeated for all the selected BSS cells.
The result file has a variable number of records depending on the number (N) of selected cells.
For TYPE 32, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (320) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B

CELL-ID (BTS INDEX + Sect. Nb.) 2B

Refer to documents [A] and [C]
CELL counters

Repeated
Refer to documents [A] and [C] N times
3.2.29 TYPE 33: Electro Magnetic Environment (EME) Supervision
This type of counters allows to supervise the emitted power at the BTS antenna. Power data is
provided per cell and per frequency band.
TYPE 33 is composed of counters repeated for all the selected BSS cells.
The counters are set to 0 in the result file if the feature is not activated.
The result file has a variable number of records depending on the number (N) of selected cells.
For TYPE 33, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.


BLOCK TYPE (330) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B
Cell counters
CELL-ID (BTS INDEX + Sect. Nb.) 2B
Repeated N times
Refer to documents [A] and [C]
N is the number of cells covered by BSC and selected for PM jobs.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 56/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.30 TYPE 34: Voice Group Call Services (VGCS)
The Voice Group Call Service (VGCS) allows speech conversation of a predefined group of service
subscribers in half duplex mode on the radio link taking into account multiple mobile service subscribers
involved in the VGCS call per cell.
TYPE 34 is composed of global counters related to the whole BSS and counters related to the
selected BSS cells. The result file has a variable number of records depending on the number (N) of
selected cells.

Every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a record is
completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (340) 2B
BLOCK LENGTH (refer to documents [A] and [C]) 2B
Refer to documents [A] and [C]

Refer to documents [A] and [C]

BLOCK TYPE (341) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B
Cell counters
CELL-ID (BTS INDEX + Sect. Nb.) 2B
Repeated N times
Refer to documents [A] and [C]

Refer to documents [A] and [C]
N is the number of cells covered by BSC and selected for PM jobs.

3.2.31 TYPE 35: IP MEASUREMENTS
This type of counters is dedicated to IP measurements performed by the BSC, the TC, the MFS or the
IP BTS. The BSC in IP mode gathers these IP measurements in a same type. TYPE 35 is composed
of IP counters related to every cell, to every BTS, to every Abis link, and to every TC.
The result file has a variable number of records and blocks depending on the number of selected cells,
TC, BTS, Abis link, in the BSS.
The TCSL blocks (353 and 354) are not reported when A-interface is fully based on IP (i.e. Full
AUPoIP) in case A User Plane over IP feature is enabled.

The result file has a variable number of records and blocks depending on the number of selected cells,
TC rack, BTS, Abis link, and BSC-TC rack link in the BSS.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 57/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
When the BSC is a G2 BSC or a MX BSC in TDM mode, the OMC does not activate the BSC for IP type.
Defence for a TDM MX BSC side: it is however forecasted that the BSC provides to the OMC only the file
header in the IP file result.
For TYPE 35, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary,
a record is completed with dummy values (Hex FF) at its bottom.
Cell block:

BLOCK TYPE (350) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B
Cell counters
CELL-ID (BTS INDEX + Sect. Nb.) 2B
Repeated N times
Refer to documents [A] and [C]
.

N is the number of cells covered by BSC and selected for PM jobs. Only cells mapped on IP BTS (IPoE1 or
IPoEth) are reported.
TC rack block:

BLOCK TYPE (353) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

TCSL_SBL 1B
COUNTERS REPEATED
Filler 1B
FOR EVERY TC rack
Refer to documents [A] and [C]
.
Not reported when A-interface is fully based on IP (i.e. Full AUPoIP) in case A User Plane over IP feature is
enabled.

BSC-TC rack block:

BLOCK TYPE (354) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

TCSL_SBL 1B
COUNTERS REPEATED
Filler 1B
Refer to documents [A] and [C]
FOR EVERY BSC-TC rack
linkTC
.
Reported only on TCSL mode with TC.
Not reported when A-interface is fully based on IP (i.e. Full AUPoIP) in case A User Plane over IP feature is
enabled.



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 58/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t



BTS blocks:

BLOCK TYPE (355) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B
COUNTERS REPEATED
TCSL_SBL (*) 1B
BTS-ID (BTS INDEX ) 1B
For every BTS
Refer to documents [A] and [C]
.

The TC rack primary is the one present at the block construction time in case of TC rack primary has
changed between 2 measurement periods.
(*): When A-interface is fully based on IP (i.e. Full AUPoIP) in case A User Plane over IP feature is enabled,
TCSL_SBL is not relevant (no TC) and set to dummy value = Hex FF.


BLOCK TYPE (356) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B
COUNTERS REPEATED
BTS-ID (BTS INDEX ) 1B
For every BTS
Filler 1B

Refer to documents [A] and [C]
.
This block is dedicated for counters of BTS frequency synchronization.

Abis link block:

BLOCK TYPE (358) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B
COUNTERS REPEATED
ABIS-NUM 2B
FOR EVERY IPoE1ABIS LINK
Refer to documents [A] and [C]
.
Reported only on Abis with IPoE1 (Abis-Transport-Mode= IP unframed or IP framed)

3.2.32 TYPE 36: IUR-G MEASUREMENTS
This type of counters is dedicated to Iur-g measurements performed by the BSC on the Iur-g interface
between BSC and RNC.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 59/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
The result file has a variable number of records depending on the number of selected BSC-RNC link in the
BSS.
When the BSC is a G2 BSC or a Mx BSC with Iur-g interface mode disable, the OMC doesnt activate the
BSC for PM type 36. Defence on BSC side if PM type 36 is activated for a Mx BSC with Iur-g interface mode
disable: it is however forecasted that the BSC provides to the OMC only the file header in the PM type 36 file
result.
For TYPE 36, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.
RNC block:

BLOCK TYPE (360) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

RNC_SBL 1B
COUNTERS REPEATED
Filler 1B
Refer to documents [A] and [C]
FOR EVERY RNC
.

3.2.33 TYPE 37: VAMOS MEASUREMENTS
This type of counters is dedicated to VAMOS measurements performed by the BSC when VAMOS feature is
enabled for the allowed cells (VAMOS is allowed only for cells with an IP Abis transport mode i.e. mapped on
IP BTS of Mx BSC with IP transport mode feature enabled).
The result file has a variable number of records depending on the number of selected cells in the BSS.
When the BSC is a G2 BSC or a Mx BSC in TDM mode, the OMC doesnt activate the BSC for PM type 37
(OMC could activate TYPE 37 even if there is no BTS in IP mode thus no VAMOS cell in the BSC or even if
there is no cell enabled for VAMOS in the BSC despite at least one BTS is IP). Defence on BSC side if PM
type 37 is activated for a Mx BSC in TDM mode or if there is no VAMOS cell in the BSC: it is however
forecasted that the BSC provides to the OMC only the file header in the PM type 37 file result
16
.
For TYPE 37, every record has a fixed length of 256 bytes and is filled with whole blocks. If necessary, a
record is completed with dummy values (Hex FF) at its bottom.
Cell blocks:

BLOCK TYPE (370) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B
Cell counters
CELL-ID (BTS INDEX + Sect. Nb.) 2B
Repeated N times
Refer to documents [A] and [C]
.

16
Unlike to other Types, this defense case could occur for Type 37 even if quite rare; for instance during experimentation or
exceptionally during BSC life if last VAMOS cells are disabled while VAMOS PM campaign is still running. Therefore, this defense is
actually implemented in OMC (if the BSC reports successfully a null-size file, no message is raised to the user) and in BSC
(a successfull null-size file is autonomously deleted after being reported to OMC).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 60/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


BLOCK TYPE (371) 2B

BLOCK LENGTH (refer to documents [A] and [C]) 2B
Cell counters
CELL-ID (BTS INDEX + Sect. Nb.) 2B
Repeated N times
Refer to documents [A] and [C]
.


N is the number of cells covered by BSC and selected for PM jobs. Only VAMOS cells i.e. cells enabled for
VAMOS (mapped on IP BTS i.e. IPoE1 or IPoEth) are reported
17
.

3.2.34 Type 38 TO TYPE 109: (NOT USED)

3.2.35 TYPE 110: OVERVIEW MEASUREMENTS
TYPE 110 is composed of counters repeated for all BSS cells, for all BSS TRXs, for every N7 SL, for
every MSC and of counters related to the whole BSS; each counter of this second type is in fact the
sum of timeslot related raw counters calculated on a TRX basis.

The result file has a variable number of records and blocks depending on the number of selected cells,
TRXs, MSC, NRI, GSL and N7 in the BSS.
The N7 SL block is reported when the signalling between BSC and MSC is in TDM and the MSC block
is reported when the signalling between BSC and MSC is in IP.
The NRI blocks (1143 and 1144) are reported only when the signaling between BSC and MSC is in IP
and when the feature Aflex is activated.
If there is no NRI counters to be reported for a given MSC, the related blocks (1143 and 1144) are not
reported.
The MGW block (1146) is reported only in A-Interface IP transport mode when A User Plane over IP
feature is enabled.


For TYPE 110, every record has a fixed length of 256 bytes and is filled with whole blocks. If
necessary, a record is completed with dummy values (Hex FF) at its bottom.


17
Since a cell could be enabled for VAMOS then disabled and so on during the Accumulation Period (AP) of
TYPE 37 measurement, the VAMOS counters reported in VAMOS result file could be relevant only for a part
of AP (not for the complete AP). If there is at least one VAMOS cell in BSC during AP, BSC reports PM type
37 with only the cell(s) in VAMOS state during at least a Granularity Period (GP) of the Accumulation Period
(enough to count something for VAMOS). The cell never in VAMOS state during AP is not reported.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 61/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
CELL blocks:
Remark: Cell related counters are split into 5 different blocks so that each block can fit into a 256-
bytes record.


BLOCK TYPE (1110) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

CELL-ID (BTS INDEX + Sect. Nb.) 2B

Refer to documents [A] and [C]
CELL COUNTERS
..
REPEATED
Refer to documents [A] and [C]
N TIMES


BLOCK TYPE (1120) 2B
BLOCK LENGTH (Refer to documents [A] and [C]) 2B
CELL-ID (BTS INDEX + Sect. Nb.) 2B
CELL COUNTERS
Refer to documents [A] and [C]
REPEATED

N TIMES
Refer to documents [A] and [C]

BLOCK TYPE (1122) 2B
CELL COUNTERS
BLOCK LENGTH (refer to documents [A] and [C]) 2B
REPEATED N TIMES
CELL-ID (BTS INDEX + Sect. Nb.) 2B

Refer to documents [A] and [C]

Refer to documents [A] and [C]

BLOCK TYPE (1123) 2B
CELL COUNTERS
BLOCK LENGTH (refer to documents [A] and [C]) 2B
REPEATED N TIMES
CELL-ID (BTS INDEX + Sect. Nb.) 2B

Refer to documents [A] and [C]

Refer to documents [A] and [C]

Note: the counters on TRX Power Saving feature have valid values even if the feature is not activated and
even if there is no MC module on by the MC modules on the BTS.

BLOCK TYPE (1126) 2B
CELL COUNTERS
BLOCK LENGTH (refer to documents [A] and [C]) 2B
REPEATED N TIMES
CELL-ID (BTS INDEX + Sect. Nb.) 2B

Refer to documents [A] and [C]

Refer to documents [A] and [C]



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 62/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
Not reported when BSC is a G2 BSC.
Note: this block contains cell counters defined for RFD 283007 and for A User Plane over IP feature.

TRX blocks:


BLOCK TYPE (1125) 2B
REPEATED
BLOCK LENGTH 2B
FOR EACH
CELL-ID (BTS INDEX + Sect. Nb.) 2B
CELL

BLOCK TYPE (1130) 2B
BLOCK LENGTH (Refer to documents [A] and [C]) 2B


TRX-ID (BTS-INDEX+Sect. Nb.+TRX. Nb.) 3B
TRX counters
Filler 1B
REPEATED

Refer to documents [A] and [C]



FROM 0 TO

.
MaxNbTRX

Refer to documents [A] and [C]
TIMES

N7 block:

BLOCK TYPE (1135) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

LINK-ID (CIC) 2B
COUNTERS REPEATED
Refer to documents [A] and [C]
FOR EVERY N7 SL
.
Refer to documents [A] and [C]
Not reported when A-signalling link over IP is enabled (therefore in case A User Plane over IP feature is
enabled).
The link-Id is the identification of the N7 Signalling link.
- In case of LSL, the link-Id gives the CIC code composed of: high weight which represents the trunk-Id on
11 bits and the TS on 5 bits which is always 16.
- In case of HSL, the link-Id gives the SLC (Signaling Link Code) which represents the entire N7 trunk: a
number from 0 to 15 or from 1 to 15 depending on operator choice.
The link_Id blocks based on SLC or CIC are not ordered (increasing or decreasing).
BSS block:

BLOCK TYPE (1140) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

Refer to documents [A] and [C]
COUNTERS RELATED
..
TO THE WHOLE BSS
Refer to documents [A] and [C]


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 63/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
MSC block:

BLOCK TYPE (1142) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

MSC-SBL 1B
COUNTERS REPEATED
Filler 1B
Refer to documents [A] and [C]
FOR EVERY MSC
..
Refer to documents [A] and [C]
This block is reported only when A-signalling link over IP is enabled (therefore in case A User Plane over
IP feature is enabled).
NRI block:

BLOCK TYPE (1143) 2B
REPEATED
BLOCK LENGTH (Refer to documents [A] and [C]) 2B
FOR EACH
MSC-SBL 1B


Filler 1B
MSC

BLOCK TYPE (1144) 2B
BLOCK LENGTH (Refer to documents [A] and [C]) 2B


NRI Num 2B

Refer to documents [A] and [C]



FROM 1 TO

.
Max 9 NRIs

Refer to documents [A] and [C]
These NRI blocks are reported only when A-signalling link over IP is enabled and A-Flex is enabled.
The NRI Number can be a value from 0 to 1023 coded in 2 bytes (LSB, MSB). One special NRI (NULL NRI)
is defined by the NULL NRI CS parameter. As the Null NRI can be any NRI number, the maximum number
of NRI which can be reported is 9 instead of 8 per MSC.

GSL block:

BLOCK TYPE (1145) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

GSL-SBL 2B
COUNTERS REPEATED
Refer to documents [A] and [C] 4B
FOR EVERY GSL link

...
4B
Refer to documents [A] and [C] 4B



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 64/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
All the counters are defined both on IP mode and on TDM mode for GSL Transport with MFS at BSCGP
level.
When the transport is in IP mode, the counters are identified by the IP-GSL SBL.
When the transport is in TDM mode, the counters are identified by the GSL SBL

MGW block:

BLOCK TYPE (1146) 2B

BLOCK LENGTH (Refer to documents [A] and [C]) 2B

MGW_IP_ADDRESS 4B
COUNTERS REPEATED
Refer to documents [A] and [C] 4B
FOR EVERY MGW

...
4B
Refer to documents [A] and [C] 4B

This block is reported only in A-Interface IP transport mode when A User Plane over IP feature is
enabled.
MGW_IP_ADDRESS is the IP address (32 bits in 4 groups of 8 bits) of a given Media GateWay
connected to BSC on A interface.

3.2.36 TYPE 111 TO TYPE 179: (NOT USED)



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 65/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.2.37 TYPE 180: TRAFFIC FLOW MEASUREMENTS
TYPE 180 is composed of counters (related to handover information) repeated per couple of serving
and target cells basis.

The result file has a variable number of records and blocks depending on the number of reported target
cells with their associated serving cells.
There is one block 1810 only if handover took place on the adjacency.
There is one block 1800 if there is at least one record 1810.

For TYPE 180, every record has a fixed length of 256 bytes and is filled with whole blocks. If
necessary, a record is completed with dummy values (Hex FF) at its bottom.

BLOCK TYPE (1800) 2B
BLOCK LENGTH (2) 2B
CELL COUNTERS
CELL-ID (BTS INDEX + Sect. Nb.) 2B
REPEATED

BLOCK TYPE (1810) 2B
CELL FOR EACH REPORTED
BLOCK LENGTH (Refer to
documents [A] and [C])
2B
COUNTERS

TARGET CELLS
MCC_MNC
18
3B



FILLER 1B



LAC
18
2B
REPEATED
CI
18
2B
FOR EACH
Refer to documents [A] and [C] 4B
SERVING
4B
CELL up to N
times
19



Refer to documents [A] and [C] 4B






18
MCC_MNC, LAC and CI identify the reported serving cell. Refer to type 26 for the codage description.
19
N is the maximum own cells per BSC MAX-CELL defined in [6] (e.g. 264 for G2 BSC or 500 for Mx BSC).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 66/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
3.3 Directory File
The directory file contains identities of PM result files produced by the BSC.

Every file record (called Directory Performance Measurement Record: DPMR) stores the information
related to a single PM result file. The number of file records should range between 1 and 35 (i.e.: the
BSS may have a maximum of 35 running measurements at any one instant).

A DPMR has the following layout:

System Record Header (SRH) 6B (See 2.2)
BLOCK_ID (1000) 2B
BLOCK_LENGTH (22) 2B
THIS RECORD
MEASUREMENT_ID 2B
CAN BE REPEATED A
JOB_PM_ERRORINFO
20
2B
MAX. OF 35 TIMES

RESULT_FILE_IDENTITY 12B

IN THE DIRECTORY FILE
NBR_RECORDS 2B
RECORD_SIZE 2B
MEASUREMENT_TYPE 1B
LAST_RESULT_INDICATOR 1B

Usage:
System Record Header: number of bytes = 06
record sequence number = from 00 onwards
record type = 14 (DPMR)
file type = 12 (PMDF)
Measurement_Id: Measurement-Id (integer)
Job_PM_ErrorInfo: Job-PM-ErrorInfo (integer)
Result_File_Identity: File-NameVersion (refer to 2.4.1)
Nbr_records This field indicates the number of records used for the construction of the related
result file.
Record_size This field indicates the size (in nbr of bytes) of the record used for the
construction of the related result file (see paragraph 3.2. for the definitions of
these records).
Measurement_Type: Measurement-Type (example: (110) for measurement type 110)
Last_Result_Indicator: Last-PM-Result-Indicator (False or true)

20
When no file can be reported for a given measurement job, the Job-PM-ErrorInfo field in the corresponding record is set to
the value 'no-report-no-traffic'.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 67/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

4 TRACE MANAGEMENT FILE FORMATS
4.1 General Trace file formats
IMSI Basic and IMSI Radio Traces can be activated
Each type of trace has a different file format:
IMSI Radio Trace Result File (TRCF) for IMSI Radio Trace
IMSI Basic Trace Result File (ITRF) for IMSI Basic Trace.
For both types of files, the first record is the Trace generic Record Header (TRHR). It has the following
layout (a record is completed with dummy values 0FFH at its bottom):

Description Size (Bytes)
System Record Header (SRH) 6B (See 2.2)
Managed Object Class 2B
Managed Object Instance 6B
File Creation 16B
File Closure 16B
Number Of Records 2B
File Sequence Number 1B
Last File Info 1B
File Closure Reason 1B

msc_invoke_trace_msg 64B

Classmark 5B
BSC Trace Type 2B




Usage:
System Record Header: number of bytes = 06
record sequence number = 00
record type = 15 (TRHR)
file type = 13 or 16 (TRCF or ITRF).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 68/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Managed Object Class = TRACE
Managed Object Instance = BSC-trace-number = trace originator (1 byte) + 1 spare byte +
trace number (2 bytes) + MSC transaction number (2 bytes)
File Creation = Time and date of start trace (given in an ASCII format from tenth of
second to year ; see physical layout of PGHR in 3.1.1).
File Closure = Time and date of stop trace (given in an ASCII format from tenth of
second to year ; see physical layout of PGHR in 3.1.1).
Number Of Records = number of records composing the file.
File Sequence Number = gives the file ordering in case the transaction has been traced over 20
Kbytes, thus multiple files are needed.
Last File Info = boolean; if true this is the final file
File Closure Reason: Four possible reasons:
(0) = transaction successfully ended or 20 Kbytes reached.
(1) = BSC internal errors prevented tracing continuation.
(2) = Disk became full during the tracing of this transaction.
(3) = External HO
msc_invoke_trace_msg = all Hex FF if no message
Classmark = all Hex FF if no Classmark
BSC Trace Type = BASIC, RADIO

The following records (records 1 to N) of the IMSI Radio trace result file are: Trace Result Data
Records (TRDR). They are described in 4.2.1.

The following records (records 1 to N) of the IMSI Basic trace result file are: IMSI Trace result Data
Records (ITDR). They are described in 0.

4.2 IMSI Radio Trace file formats
The IMSI Radio trace results are reported to the OMC as a combination of different pieces of
information. Each of such pieces of information constitute a record of the file. The records are called
Trace Result Data Record (TRDR). All the different pieces of information are derived from the available
observations gathered by the Performance Measurement function within the BSC. The BSC is only
able to treat files with a fixed format, that is all the records constituting the file must have the same
length. This implies that the record length is determined by the biggest observation type (internal
handover observation), and that all the records related to the other observations are filled with Hex FF
values from the last meaningful byte to the end of the record.
Every record begins with the SYSTEM RECORD HEADER (bytes 0 to 5). The following 4 bytes provide
the type of observation (bytes 6 and 7) and the length of the information (bytes 8 and 9). Starting from
byte 10 the record is filled in with the trace result information, according with the layouts described
hereafter.
The length of Trace Result Data Record is 226 bytes.



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 69/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
4.2.1 Trace Result File Format
4.2.1.1 CIRCUIT IDENTITY CODE
Format of Circuit Identity Code record

SYSTEM RECORD HEADER (SRH) 6B (See 2.2)
BLOCK TYPE (value 300) 2B
BLOCK LENGTH (value 2) 2B
CIC 2B
IMSI 9B



4.2.1.2 SDCCH Observation
Format of SDCCH OBSERVATION record

SYSTEM RECORD HEADER (SRH) 6B
(See 2.2)
BLOCK TYPE (100) 2B
BLOCK LENGTH (66) 2B
CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
FILLER 1B

CHAN_SEIZ_TIME
7
16B
CHAN_RELEASE_TIME
7
16B
END_INDICATION 1B
SEIZURE_TYPE 1B
MS_POWER 2B
BS_POWER 2B
TIMING_ADVANCE 2B
NBR_FRAMES_NOT_REPEATED 2B
NBR_FRAMES_REPEATED 2B
NBR_OF_SABM_AFTER_UA_SENT 1B
NBR_OF_PHYSICAL_INFO_SENT 1B
NBR_OF_ERRONEOUS_FRAMES_SENT 1B
NBR_OF_REJ_FRAMES_SENT 1B
NBR_OF_REJ_FRMES_RECEIVED 1B
NBR_OF_MS_TX_PWR_MAX_SENT 1B
RADIO_LINK_FAILURE_INDICATION 1B
PERC_OF_INCOR_SACCH_FRAMES_RX 1B
PERC_OF_INCOR_NOT_SACCH_FM_RX 1B
SAMPLE_RATE 1B
TSC 1B
FHS_ID (=FFh in non freq. hopping case) 1B
MAIO (=FFh in non freq. hopping case) 1B
ARFN (=FFh in freq. hopping case) 2B


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 70/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
CU_ID (=FFh in freq. hopping case) 1B

4.2.1.3 Timeslot Radio Measurements Observations
Format of TIMESLOT RADIO MEASUREMENTS OBSERVATIONS record

SYSTEM RECORD HEADER (SRH) 6B
(See 2.2)
BLOCK TYPE (110) 2B
BLOCK LENGTH (235) 2B
CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
RTCH_TYPE 1B

INFO-RECEIVED_TIMESTAMP
7
16B
AVERAGE_RXLEVEL_UPLINK_HO 1B
AVERAGE_RXLEVEL_DOWNLINK_HO 1B
AVERAGE_RXLEVEL_DOWNLINK_PBGT 1B
AVERAGE_RXQUALITY_UPLINK_HO 1B
AVERAGE_RXQUALITY_DOWNLINK_HO 1B
AVERAGE_RANGE_HO 1B
MS_TXPOWER 1B
BS_TXPOWER 1B
BTSnumber 1B
BSIC
8
(1) 1B
BCCH_FREQUENCY
9
(1) 2B
AVG_RXLEVEL_NEIGHBOURCELL (1) 1B
POWERBUDGET(1) 1B
BSIC (2) 1B
BCCH_FREQUENCY (2) 2B
AVG_RXLEVEL_NEIGHBOURCELL (2) 1B
POWERBUDGET (2) 1B

. . . . . . . . . . .

BSIC
8
(BTSnum) 1B
BCCH_FREQUENCY (BTSnum) 2B
AVG_RXLEV_NEIGHBCELL (BTSnum) 1B
POWERBUDGET (BTSnum) 1B

. . . . . . . . . . .

Filled with
BSIC
8
(32) 1B H-FF
BCCH_FREQUENCY (32) 2B values
AVG_RXLEVEL_NEIGHBOURCELL (32) 1B
POWERBUDGET (32) 1B
AV_RXLEV_UL_MCHO 1B
AV_RXLEV_DL_MCHO 1B
SAMPLE_RATE 1B
SCRAMBLING_CODE (1) 2B
FDD_FREQ (1) 2B


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 71/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
AV_ECNO (1) 1B
SCRAMBLING_CODE (2) 2B
FDD_FREQ (2) 2B
AV_ECNO (2) 1B
.
SCRAMBLING_CODE (8) 2B
FDD_FREQ (8) 2B
AV_ECNO (8) 1B
TSC 1B





4.2.1.4 Internal Handover Observation
Format of INTERNAL HANDOVER OBSERVATION record
SYSTEM RECORD HEADER (SRH) 6B (See 2.2)
BLOCK TYPE (120) 2B
BLOCK LENGTH (193) 2B
SIGNALLING/TRAFFIC INDICATOR 1B
INTRA/INTERCELL INDICATOR 1B
HO REQUIRED TIME STAMP
21
16B
OLD_CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
OLD_RTCH_TYPE 1B

NEW_CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
NEW_RTCH_TYPE 1B

SUCCESS/FAIL INDICATION 1B
HO DURATION (tenths of sec.) 2B
HO CAUSE 1B
SYNCHRONIZED FLAG 1B
A_LEV_HO 1B
AV_RXLEV_UL_HO 4B
AV_RXLEV_DL_HO 4B
A_PBGT_HO 1B
FILLER 1B
AV_RXLEV_PBGT_HO 4B
A_QUAL_HO 1B
FILLER 1B
AV_RXQUAL_UL_HO 4B
AV_RXQUAL_DL_HO 4B
A_RANGE_HO 1B
FILLER 1B
AV_RANGE_HO 4B
MS_TXPWR 1B
BS_TXPWR 1B

21
Time and date given in an ASCII format from tenth of second to year (see physical layout of PGHR in 3.1.1).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 72/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
BSIC
8
1B REPEATED
FREQ 2B 16 TIMES
22

RXLEV 4B
A_LEV_MCHO 1B
FILLER 1B
AV_RXLEV_UL_MCHO 4B
AV_RXLEV_DL_MCHO 4B
SAMPLE_RATE 1B
MS_SPEED 1B
TSC 1B

4.2.1.5 Incoming Handover Observation
Format of INCOMING HANDOVER OBSERVATION record

SYSTEM RECORD HEADER (SRH) 6B
(See 2.2)
BLOCK TYPE (130) 2B
BLOCK LENGTH (28) 2B
SIGNALING/TRAFFIC_INDIC 1B
INCOMING_HO_INDICATION 1B
HO_REQUEST_TIME_STAMP
21
16B
NEW_CHAN_ID (CELL_ID + TRX-nb + TRX-TS +SUBCH.) 5B
NEW_RTCH_TYPE 1B

SUCCESS_FAIL_INDICATION 1B

SYNCHRONISED 1B
SAMPLE_RATE 1B
TSC 1B



22
These 3 fields contain information related to an adjacent cell; they are repeated for 16 possible adjacent cells. If info for
less than 16 adjacent cells are available, the non used groups of fields are filled in with dummy values (Hex FF FFFF
FFFFFFFF).


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 73/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
4.2.1.6 Outgoing Handover Observation
Format of OUTGOING HANDOVER OBSERVATION record

SYSTEM RECORD HEADER (SRH) 6B
(See 2.2)
BLOCK TYPE (140) 2B
BLOCK LENGTH (227) 2B
SIGNALLING/TRAFFIC INDIC 1B
OUTGOING HO INDICAT 1B
HO REQUIRED TIME STAMP
21
16B
HO REQUIRED NBR 2B
OLD_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) 5B
OLD_RTCH_TYPE 1B

SUCCESS/FAIL INDICATION 1B

HO CAUSE 1B
FILLER 1B

A_LEV_HO 1B
AV_RXLEV_UL_HO 4B
AV_RXLEV_DL_HO 4B
A_PBGT_HO 1B
FILLER 1B

AV_RXLEV_PBGT_HO 4B
A_QUAL_HO 1B
FILLER 1B

AV_RXQUAL_UL_HO 4B
AV_RXQUAL_DL_HO 4B
A_RANGE_HO 1B
FILLER 1B

AV_RANGE_HO 4B
MS_TXPWR 1B
BS_TXPWR 1B
BSIC
8
1B REPEATED 16
FREQ 2B TIMES
22

RXLEV 4B
A_LEV_MCHO 1B
FILLER 1B

AV_RXLEV_UL_MCHO 4B
AV_RXLEV_DL_MCHO 4B
SAMPLE_RATE 1B
MS_SPEED 1B
SCRAMBLING_CODE 2B REPEATED
8
FDD_FREQ 2B TIMES
AV_ECNO 1B
TSC 1B



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 74/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

4.2.1.7 RTCH Observation
Format of RTCH OBSERVATION record

SYSTEM RECORD HEADER (SRH) 6B
(See 2.2)
BLOCK TYPE (150) 2B
BLOCK LENGTH (66) 2B
CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS +SUBCH.) 5B
RTCH_TYPE 1B

CHAN_SEIZ_TIME
21
16B
CHAN_RELEASE_TIME
21
16B
END_INDICATION 1B
SEIZURE_TYPE 1B
MS_POWER 2B
BS_POWER 2B
TIMING_ADVANCE 2B
NBR_FRAMES_NOT_REPEATED 2B
NBR_FRAMES_REPEATED 2B
NBR_OF_SABM_AFTER_UA_SENT 1B
NBR_OF_PHYSICAL_INFO_SENT 1B
NBR_OF_ERRONEOUS_FRAMES_SENT 1B
NBR_OF_REJ_FRAMES_SENT 1B
NBR_OF_REJ_FRMES_RECEIVED 1B
NBR_OF_MS_TX_PWR_MAX_SENT 1B
RADIO_LINK_FAILURE_INDICATION 1B
PERC_OF_INCOR_SACCH_FRAMES_RX 1B
PERC_OF_INCOR_NOT_SACCH_FM_RX 1B
SAMPLE_RATE 1B
TSC 1B
FHS_ID (=FFh in non freq. hopping case) 1B
MAIO (=FFh in non freq. hopping case) 1B
ARFN (=FFh in freq. hopping case) 2B
CU_ID (=FFh in freq. hopping case) 1B
BSIC
8
2B
HEX FF in
CLASSMARK 1 1B
case of a
CLASSMARK 2 3B
Call trace
CLASSMARK 3 4B





Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 75/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
4.2.2 IMSI Basic Trace file format
The IMSI Basic Trace results are reported to the OMC-R as a combination of different pieces of
information. All the different pieces of information are obtained within the BSC independently of
Performance Measurement functions.

The IMSI Trace results are reported to the OMC-R into:
either one single file (e.g. no partial records i.e. Timer-Trace-Value = 0)
or several files (e.g. timed records i.e. Timer-Trace-Value 0)

Each IMSI Trace file consists of a series of entries. Each entry (TLV) in the file consists of 3 subfields:
IMSI Trace File Entry Identifier
This field uniquely identifies the entry item in the IMSI Trace file (it is always 1 octet long)
IMSI Trace File Entry Length
This field gives the length of the following data item (it is always 1 octet long)
IMSI Trace File Entry Data
This field contains the data item (it is of a variable length which is given in the preceding subfield).

This implies that the data content of the trace file is of variable length and is determined by the number
of entries in the file. Each file is limited to a maximum length of 20k bytes.

The file is in fact made up of a variable number of records: the first record is the TRHR (Trace generic
Header Record) (see 4.1); the following records are IMSI Trace result Data Records. Each IMSI Trace
result Data Record has a fixed length of 256 bytes, starts with a System Record Header (SRH, see
2.2) and contains then a variable number of entries. The remaining space at the end of the record is
filled in with dummy values 'FFh'.


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 76/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

IMSI TRACE RESULT DATA RECORD

System Record Header
(SRH) (see 2.2)


6 bytes
nbr of bytes 06
rec seq from 01 onwards
Record Type 20 (ITDR)
File Type (ITRF)

Entry var

. . . . . . . . . . . . . . .

Entry

var




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 77/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
The following table identifies the different entries that can be found in the IMSI Basic Trace file and
indicates, for each type of file (i.e. single file, first file, middle file or last file), which entries have to
be provided, may be provided or shall not be provided. Entries which may be repeated (such as the
Cell_ID so that lists may be generated in the OMC-R) are specifically identified.


Entry No. Rep. First Middle Last Single
IMSI or IMEI (Traced party) 1 N
Trace Reference 2 N
Transaction Id 3 N C C C C
Trace Type 4 N - -
Trace Type Used 5 N - -
Start Time 6 N - -
End Time 7 N - -
Trace Event Invocation Message 8 N - -
Record Cell ID 9 Y M1 M1 M1
TRX ID 10 Y M1 M1 M1
Radio Channel Info 11 Y M1 M1 M1
Request type 12 Y C1 C1 C1 C
End Indication 13 Y C1 C1 C1 C
MS Classmark 1 14 Y C1 C1 C1 C
MS Classmark 2 15 Y C1 C1 C1 C
MS Classmark 3 22 Y C1 C1 C1 C
BSIC
7
16 Y M1 M1 M1
CIC 17 Y C1 C1 C1 C
Handover result 18 Y C1 C1 C1 C
Handover cause 19 Y C1 C1 C1 C
Sequence Number 20 N -
Reason for Record 21 N

Key:
: Must be provided
- : Not required
M1 : Must be provided in at least one Trace file
C1 : If available, provided in at least one Trace file
C : Provided if available
Rep. : Entry can be repeated several time: Y = Yes, N = No


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 78/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
The tables below give the structure of the different entries:

Type 1 IMSI or IMEI Lg
ELEMENT IDENTIFIER (=1) 1
LENGH (=9) 1
IMSI or IMEI 9
9 bytes coded on the basis of Mobile Identity IE without IEI (information element
identifier) and octet length value (for more details, see TS GSM 04.08). The layout
is as described below:

8 7 6 5 4 3 2 1
Identity digit 1 O/E Type of ident. Octet 1
Identity digit p+1 Identity digit p Octets 2 to 9


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 79/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

with:
Type of identity (octet 1)
Bits
3 2 1
0 0 1 IMSI
0 1 0 IMEI
0 1 1 IMEISV (i.e. IMEI with Software Version Number)
1 0 0 TMSI (not used for trace)
0 0 0 No identity (not used for trace)
All other values are reserved.
O/E = Odd/even indication (octet 1)
Bit
4
0 even number of identity digits
1 odd number of identity digits
Identity digit (octets 2 to 9)
Each digit is coded on 4 bits using BCD coding.
IMEISV (16 digits): Bits 5 to 8 of octet 9 are filled in with '1111B'.
IMEI (15 digits): Octet 9 is filled in with FFh.
IMSI (<= 15 digits): If the number of identity digits is even, bits 5 to 8 of last
meaningful octet are filled in with '1111B'. Unused
octet(s) is(are) filled in with FFh.




Type 2 Trace Reference Lg
ELEMENT IDENTIFIER (=2) 1
LENGH (=2) 1
TRACE NUMBER integer - LSB 2
- MSB


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 80/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Type 3 Transaction Id Lg
ELEMENT IDENTIFIER (=3) 1
LENGH (=2) 1
MSC-TRANSACTION-NUMBER integer - LSB 2
- MSB

Type 4 Trace Type Lg
ELEMENT IDENTIFIER (=4) 1
LENGH (=1) 1
TRACE TYPE 1
One byte coded as described below (for more details, see TS GSM 12.08 ):
8 7 6 5 4 3 2 1
X 0 X X X X X X

123 123 123

Invoking event*

MSC Record Type*


BSS Record Type*


Priority indication*

* Same coding as Type 5.

Type 5 Trace Type Used Lg
ELEMENT IDENTIFIER (=5) 1
LENGH (=1) 1
TRACE TYPE 1
One byte coded as described below (for more details, see TS GSM 12.08):
8 7 6 5 4 3 2 1
X 0 0 0 1 1 0 0

123 123 123

Invoking event = all events

MSC Record Type = 'No MSC trace'


BSS Record Type = 'Basic'


Priority indication (1 = Priority ; 0 = No priority)




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 81/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Type 6 Start Time Lg
ELEMENT IDENTIFIER (=6) 1
LENGH (=16) 1
TIME & DATE 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)

Type 7 End Time Lg
ELEMENT IDENTIFIER (=7) 1
LENGH (=16) 1
TIME & DATE 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 82/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Type 8 Invocation Message Lg
ELEMENT IDENTIFIER (=8) 1
LENGH (var) 1
INVOCATION MESSAGE v
Octet string containing the 08.08 invocation
message (MSC Invoke Trace) which started the
trace action (for detailed layout of this message,
refer to TS GSM 08.08 )
The size of this message can vary between 6 and
64 octets.

OCTET STRING (6..64)
a
r

Type 9 CELL ID Lg
ELEMENT IDENTIFIER (=9) 1
LENGH (=20) 1
CI integer - LSB 2
Cell Identity - MSB
LAC integer - LSB 2
Location Area Code - MSB
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 83/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Type 10 TRX ID Lg
ELEMENT IDENTIFIER (=10) 1
LENGH (=17) 1
TRX NUMBER integer (1..MaxNbTRX) 1
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 84/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Type 11 Radio Channel Info Lg
ELEMENT IDENTIFIER (=11) 1
LENGH (=155) 1
CHANNEL TYPE
Channel Type IE as defined in TS GSM 08.08 (IE used in
Assignment Request and Handover Request messages).
It consists of the following octets:
- 1st octet: speech/data indicator
- 2nd octet: channel rate and type
- 3rd octet: permitted speech version indication (if
speech)/data rate + transparency indicator (if data)
- 4th octet up to 8th octet: other permitted speech
versions (if any)
Note: unused bytes are filled in with '00' (zero).
8
CHANNEL DESCRIPTION
Channel Description IE as defined in TS GSM 04.08
It consists of 3 octets containing the following information:
- channel type and TDMA offset
- Timeslot number
- Training Sequence Code
- flag (hopping or non-hopping)
- in case of hopping: MAIO and HSN
- in case of non-hopping: ARFCN
It is to be decoded by OMC as follows
3
8 7 6 5 4 3 2 1 Byte
Channe l Type and TDMA offset Timeslot number 1
TSC H=1 MAIO (high part) 2
H=0 spare ARFCN (high part)
MAIO (low
part)
HSN 3
ARFCN (low part) 3

Channel Type and TDMA offset:
bits 87654
00001 TCH/F +ACCHs
0001T TCH/H + ACCCHs
001TT SDCCH/4 + SACCH/C4 or CBCH (SCDDH /4)
01TTT SCDDH/8 + SACCH/8 or CBCH (SDCCH/8)
Timeslot number: decoded as an integer
TSC: decoded as an integer
H: flag: 0: non hopping
1: hopping
ARFCN: decoded as an integer
MAIO: decoded as an integer
HSN: decoded as an integer



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 85/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
FREQUENCY LIST
This field gives the list of ARFCNs used in the Frequency
hopping sequence.

It contains a sequence of up to 64 ARFCNs, each ARFCN
being coded on 2 bytes: INTEGER (0..1023). It is padded
out with dummy values (FFh).
In case of non-hopping, this field is not relevant and it is
therefore filled in with dummy values (FFh).
128
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 86/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Type 12 Request type Lg
ELEMENT IDENTIFIER (=12) 1
LENGH (=17) 1
ESTABLISHMENT CAUSE
One octet containing the 'Channel request'
message. Lower bits (between 2 bits and 5 bits
depending on the case) contain a Random
reference. Upper bits (between 6 bits and 3 bits
depending on the case) contain the actual
Establishment Cause.
For more details, refer to TS GSM 04.08.
The different establishment causes are:
Emergency call
Call reestablishment (3 values)
Answer to paging
Originating call (3 values)
Location updating
Other procedures which can be
completed with an SDCCH
The octet is to be decoded by OMC as follows:
bits 8..1
101xxxxx Emergency call
110xxxxx Call re-establishment
011010xx Call re-establishment
011011xx Call re-establishmnent
100xxxxx answer to paging
0010xxxx answer to paging
0011xxxx answer to paging
(the value 0001xxxx is duplicated in the
norm, it has been chosen to keep the other
meaning)
111xxxxx originating call
0100xxxx originating speech call
0101xxxx originating data call
(if this value is used, the next 2 values are useless)
0000xxxx location updating
0001xxxx SDCCH call
other values: reserved for future use.
Byte 1
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)

Type 13 End Indication Lg


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 87/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
ELEMENT IDENTIFIER (=13) 1
LENGH (=17) 1
RR CAUSE
One byte with the following meaning (for more
details, see TS GSM 04.08):
0 : Normal event
1 : Abnormal release, unspecified
2 : Abnormal release, ch. unacceptable
3 : Abnormal release, timer expired
4 : Abnormal release, no activity on the radio
path
5 : Preemptive release
8 : Handover impossible, timing advance out
of range
9 : Channel mode unacceptable
10 : Frequency not implemented
65 : Call already cleared
95 : Sementically incorrect message
96 : Invalid mandatory information
97 : Message type non-existent or not
implemented
98 : Message type not compatible with
protocol state
100 : Conditional IE error
101 : No cell allocation available
111 : Protocol error unspecified
(All other cause values are treated as '0': normal
event)
integer (0..255) 1
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 88/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Type 14 MS Classmark 1 Lg
ELEMENT IDENTIFIER (=14) 1
LENGH (=17) 1
MOBILE STATION CLASSMARK 1 1
One byte coded as described below (for more details, see TS GSM 04.08):
8 7 6 5 4 3 2 1
0 X X X X X X X

123

14243



RF Power Capability

Encryption algorithm A5/1
(0: A5/1 available; 1: A5/1 not available)

Controlled Early Classmark Sending option
(0: not implem.; 1: implemented)

Revision level
spare
with:
RF power capability
Bits
3 2 1
0 0 0 class 1 (for GSM 900 & DCS 1800/1900)
0 0 1 class 2 (for GSM 900 & DCS 1800/1900)
0 1 0 class 3 (for GSM 900 & DCS 1800/1900)
0 1 1 class 4 (for GSM 900 only)
1 0 0 class 5 (for GSM 900 only)
All other values are reserved.
Revision level
Bits
7 6
0 0 Reserved for Phase 1
0 1 Used by Phase 2 MSs
All other values are reserved.


TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 89/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)

Type 15 MS Classmark 2 Lg
ELEMENT IDENTIFIER (=15) 1
LENGH (=19) 1
MOBILE STATION CLASSMARK 2: 3 octets 3
First octet: coded as Mobile Station Classmark 1 (see above)
Second octet: coded as described below (for more details, see TS GSM 04.08):

8 7 6 5 4 3 2 1
0 X X X X 0 0 X

123

123

Frequency Capability

spare


Short Message Capability


SS Screening Indicator


Pseudo synchronisation capability


spare



Third octet: coded as described below (for more details, see TS GSM 04.08):
8 7 6 5 4 3 2 1
X 0 0 0 0 0 X X

144424443


A5/2 (0: A5/2 not avail. ;
1: A5/2 avail.)


A5/3 (0: A5/3 not avail.; 1: A5/3
available)


spare


CM3 ( 0: no additional MS capability info available ; 1: additional
MS capability in Classmark 3)


TIMESTAMP 1 char. (tenth of sec.) 16


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 90/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)

Type 16 BSIC Lg
ELEMENT IDENTIFIER (=16) 1
LENGH (=2) 1
NCC integer (0..7) 1
Network Colour Code
BCC integer (0..7) 1
Base station Colour Code

Type 17 CIC Lg
ELEMENT IDENTIFIER (=17) 1
LENGH (=18) 1
CIC
Circuit Identity Code = 16 bits
(top 11 bits contain the trunk-id;

integer - LSB
2
other 5 bits contain the timeslot number)
derived from Cic-Atrk-Ch0


- MSB

TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 91/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 92/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Type 18 Handover Result Lg
ELEMENT IDENTIFIER (=18) 1
LENGH (=17) 1
MESSAGE TYPE
1 octet coded as described below (for more details, refer to
TS GSM 04.08):
Bits
8 7 6 5 4 3 2 1
0 0 1 0 1 0 0 1 Assignment complete
0 0 1 0 1 1 1 1 Assignment failure
0 0 1 0 1 1 0 0 Handover complete
0 0 1 0 1 0 0 0 Handover failure

1
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 93/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

Type 19 Handover Cause Lg
ELEMENT IDENTIFIER (=19) 1
LENGH (=18) 1
CAUSE
2 octets coded as described in TS GSM 08.08
If the extension bit (bit 8 = MSB) of the first octet is
set to 0, then the second octet is not meaningful; in
this case, it is filled in with 'ffh'.
- class:
bits 765 (of first octet)
000 normal event
001 normal event
010 resource unavailable
011 service or option unavailable
100 service of option not implemented
101 invalid message
110 protocol error
111 interworking

- Value:
- if the extension bit is set to 0, the field value is
decoded as a string
- if the extension bit is set to 1 (the first octet of
the cause field is then 1xxx0000 where xxx is
the class), the second octet of the cause field
is decoded as an integer.

2
TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 94/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t


Type 20 Sequence Number Lg
ELEMENT IDENTIFIER (=20) 1
LENGH (=2) 1
SEQUENCE NUMBER integer - LSB 2
- MSB

Type 21 Record Reason Lg
ELEMENT IDENTIFIER (=21) 1
LENGH (=1) 1
RECORD CRITERIA
The possible values are the following:

0 : no partial records
1 : timed
4 : manuf. specific criteria
integer 1

Type 22 MS Classmark 3 Lg
ELEMENT IDENTIFIER (=22) 1
LENGH (=20) 1
MOBILE STATION CLASSMARK 3: 4 octets 4
First octet: coded as described below (for more details, see TS GSM 04.08)
23
:
8 7 6 5 4 3 2 1
0 X X X X X X X


A5/4 (0: A5/4 not avail.;
1: A5/4 avail.)


A5/5 (0: A5/5 not avail.; 1: A5/5
available)


A5/6 (0: A5/6 not available; 1: A5/6
available)


A5/7 (0: A5/7 not available; 1: A5/7
available)


Band 1: P-GSM (0: not supported; 1: supported)


Band 2: E-GSM (0: not supported; 1: supported


Band 3: DCS1800 (0: not supported; 1: supported)


E(xtension) bit




23
This specification does not take DCS 1900 into account


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 95/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
Second octet:
This octet contains the Radio Capability 1 and Radio Capability 2. The Radio
Capability 1 corresponds to the first bit set to one of the multiband support bits (in
increasing order starting from band 1) and Radio Capability 2 corresponds to the
second bit set to 1 of the multiband support bits.
Radio Capability 1/2 is in fact the binary coding of the power class associated with
the band indicated in the multiband support bits (see TS GSM 05.05).
This octet is coded as described below (for more details, see TS GSM 04.08):

8 7 6 5 4 3 2 1
X X X X X X X X

1442443 1442443


Assoc. Radio Capability 1


Associated Radio Capability 2


Third octet (for more details, see TS GSM 04.08):
The R band associated radio capability (3 bits field) is set if the R band is
supported.
The Multi Slot Class (5 bits field) is set if the Multi Slot Capability is supported.
This octet is coded as described below:

8 7 6 5 4 3 2 1
X X X X X X X X

1442443

1442443





Multi Slot Class





MSCI: Multi Slot Capability
(0: not supported; 1: supported)





R band associated radio capability





R_PRES: R band (0: not supported; 1: supported)


Fourth octet (for more details, see TS GSM 04.08):
This octet is coded as described below:

8 7 6 5 4 3 2 1
X X X X X X X X


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 96/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

123


spare bit


spare bit


spare bit


spare bit


spare bit


UCS2 support (0: preference for default alphabet;
1: no preference for default alphabet)





Multi Slot Class (continued)


TIMESTAMP 1 char. (tenth of sec.) 16
String of 16 ASCII characters 1 char. (.)
1 char. (sec)
1 char. (sec)
1 char. (min.)
1 char. (min.)
1 char. (hour)
1 char. (hour)
1 char. (day)
1 char. (day)
1 char. (month)
1 char. (month)
1 char. (year)
1 char. (year)
1 char. (year)
1 char. (year)




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 97/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

5. GLOSSARY AND ABBREVIATIONS
5.1 Glossary
ACH A CHannel
BCCH Broadcast Control CHannel
BIE BSS Interface Equipment
BS Base Station
BSC Base Station Controller
BSIC Base Station Identity Code
BSS Base Station Subsystem
BTS Base Transceiver Station
CCCH Common Control CHannel
CGHR Configuration Generic Header Record
CHILL CCITT HIgh Level Language
CIC Circuit Identity Code
CM Configuration Management
DCCH Dedicated Control CHannel
DFR Data File Record
DFS Data File Segment
DSP Digital Signal Processor
DTC Digital Trunk Controller
FTAM File Transfer, Access and Management
FU Frame Unit
IMSI International Mobile Subscriber Identity
LAPD Link Access Protocol on D channel
LCA Logical Cell Array
LSB Least Significant Byte


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 98/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
LSW Least Significant Word
LT Local Terminal
MFP Multi-Frame Processor
MGW Media GateWay
MS Mobile Station
MSB Most Significant Byte
MSC Mobile services Switching Center
MSW Most Significant Word
OMC Operation and Maintenance Center
PGHR Performance Generic Header Record
PM Performance Measurement
RIT Replaceable Item
RNC Radio Network Controller
RTCH Radio Traffic CHannel
RMS Radio Measurement Statistics
RTS Radio Time Slot
SACCH Slow Associated Control CHannel
SBL Security BLock
SCCP Signalling Control Connection Part
SCP Signalling and Control Processor
SDCCH Stand-alone Dedicated Control CHannel
SMS Short Message Service
SRH System Record Header
TCH Traffic CHannel
TCU Terminal Control Unit
TEI Terminal Endpoint Identifier
TSC Transcoder Submultiplexer Controller


Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 99/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
TTCH Terrestrial Traffic Channel



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 100/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t

6. ANNEX
6.1 CIC use in PM

BSC provides counters in PM file with LINK ID = CIC as defined by 3GPP i.e. 16 bits with 11 high bit = A
TRunk number and 5 low bit = TS with A TRunk number as defined in MSC. This word LINK-ID is a generic
name used in plenty of PM Type to identify CIC, SLC, CPRA, LAPD, and which must be not confused with
LINK-ID name used in BSC to identify A TRunk SBL number.
BSC fits this CIC number (in MSC range) in its own environment by different means i.e. POLO, BSC
extension, OMC-R.
MSC A TRunk number is in range [0..2047] while BSC A TRunk number (about DTC number) is in range
[1..72] for G2 BSC or [1..304] for Mx BSC.

The A TRrunk number may have any value (configurable from OMC-R per BSC A TRunk), as long as it is
unique from BSC point of view. Yet, in practice, A TRunk numbers are consecutive for a BSC. For example:
- for a first G2 BSC1 (conf-3, no-GPRS) connected to an MSC, the A TRunk number could be in the
range [1..72],
- for a second G2 BSC2 (conf-3, no-GPRS) connected to the same MSC, the A TRunk number could be
in the range [73..144].
Until the whole range of the MSC, i.e. [0..2047], is filled, the series may continue.

Translation between MSC range and BSC range done with:
- POLO: when installing a BSC build using POLO, the Link IDs get a default value based on ATR SBL
number i.e. ATR SBL number - 1. It is also possible to configure a base i.e. to configure an arbitrary
value for the Link ID of ATR 1 and then the formula becomes LINK-ID = ATR SBL number 1 + LINK-
ID of ATR 1 (as below).
- BSC extension: when performing a BSC extension, the Link IDs for the new A TRunks get a value
based on their ATR SBL number and the Link ID of ATR 1 i.e. LINK-ID = ATR SBL number 1 + LINK-
ID of ATR 1 (as above).
- OMC-R: When modifying A-Interface configuration from OMC-R (see [6] use case AInterfaceConfig),
the Link ID of any ATR can be modified to any value (coded on 11 bits; unique in a BSC). OMC-R
manages an internal table Cic-Atr-Ch0() which provides for a given BSC, the link between A TRunk
number in BSC for TS0 and A TRunk number in MSC (CIC for TS 0) i.e. Cic-Atr-Ch(ATR sbl) = MSC
ATR for TS0 = CIC/32.
For PM reporting, the BSC uses the configured value, value which comes from POLO, BSC Extension, or
from OMC-R and which must be consistent i.e. equal, to MSC A TRunk number. The BSC Link ID, together
with the TS number, values reported in PM files for each A-interface channel, forms the CIC.

Example of CIC use in NPO/OBSAL alerter:
- OBSAL application in OMC uses LINK ID value set in PM file type 18 (AIC) as it is provided by BSC, to
create an alerter instance with 'BSC name/LINK ID' reference so with CIC as defined in 3GPP,
- OMC must map this OBSAL alerter on 'alcatel2MbTTP' OMC object with ACH SBL instance knowing
that ACH SBL is defined as DTC number (SBL number rather like A TRunk number) + TS number
(SBL sub-number) using the 'Cic-Atrk-Ch0' OMC table (in order to retrieve i = DTC number = A TRunk
number BSC view where Cic-Atr-Ch0(i) = MSC A TRunk number = CIC/32).



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 101/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
6.2 Synthesis of BSC PM File Formats

Currently there are 5 BSC file types: OPMF, GPMF, TRCF, ITRF, PMDF with 2 kinds of record:

Record 0 (except for PMDF file type)
Number of bytes in the header 2 bytes
Record Sequence Number 2 bytes
Record Type Number 1 byte
File Type Number 1 byte
System Record Header (SRH) absent
within transmission settings file (see 2.2)

System File
Header
Specific header info
for PGHR, TRHR record
max. 250
bytes
Specific Header Info (SHI)
present only in first record of the file types:
OPMF, GPMF, TRCF, ITRF
User data
Header
||
PGHR or TRHR record



Record > 0 (or 0 for PMDF file type)
Number of bytes in the header
2 bytes
Record Sequence Number
2 bytes
Record Type Number 1 byte
File Type Number 1 byte
System Record Header (SRH) absent
within transmission settings file (see 2.2)
System File
Header
Result info
for OPMR, GPMR, DPMR, TRDR,
ITDR records
max. 250
bytes

Always present in PMDF file type

Present in OPMF, GPMF, TRCF, ITRF file
types if number of records > 0 in SHI
User data
||
OPMR, GPMR, DPMR, TRDR or ITDR record




Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 102/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
Example of GPMF file type with a PMtype 35 result file (file name = PMRES-35.345)

PGHR = Record 0
File type=03 (GPMF)
Record type=12 (PGHR)
6B
(see 2.1 and 2.2) SRH
BSS Version 2B
BSC Release 1B
FILLER 1B
Managed Object Class 2B
Managed Object Instance 2B
File Creation 16B

Measurement Type=35 2B
Total Size 4B

Number of Records 2B
Begin Collection Time 16B

End Collection Time 16B

FILLER 3B (FFh FFh FFh)
Sample Percentage 1B (default: FFh)
Sample Rate Reduced 1B
FILLER 1B

Specific
header info
(see 3.1)

76 bytes
FFh 274B
Remaining space
in
file record 0
274 bytes

GPMR = Record > 0 (present if number of records >0 in SHI of PGHR record)
File type=03 (GPMF)
Record type=03 (GPMR)
6B (see 2.1 and 2.2)
SRH
Block type=35<x>
Block length
PM counter results
Block type=35<y>
Block length
PM counter results

max.
250
bytes
(see 3.2.31) Results Info
FFh nB
Remaining space
in
file record



Ed01 Released OMC-BSS PM FILE FORMAT SPECIFICATION
31/05/2011 3BK 11204 0556 DSZZA 103/103

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

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t





END OF DOCUMENT