B11 OMC-BSC File Specification

All rights reserved.
Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
Site VELIZY Originators
Mobile Access Division
OMC/BSC PM FILE FORMAT SPECIFICATION B11

: : :
B. CANOVAS
System Sub-system Document Category
ALCATEL GSM BSS SYS/SYS-TLA/SYS-OAM PRODUCT DEFINITION
ABSTRACT
This document describes, for B11, the format of the files (PM result files, Trace Management result files) exchanged between BSCs and OMC-R.
Approvals Name App. E. Mermilliod Lucian-Florin MUNTEAN Zhu Haiyan
DPM OSY
DPM OMC
DPM BSC
Name App
Ingo Schwarz
Alexandru NEGRESCU
DPM BTS
DPM TC
REVIEW
Ed. 01 Proposal 01 Ed 01 Proposal 03 Ed 01 Released Ed. 02 Proposal 01 Ed 02 Released 21/06/07 02/10/07 10/10/07 24/05/08 01/07/08 207157 207237
HISTORY
Ed04 Released
OMC-BSS PM FILE FORMAT SPECIFICATION

B11_PM_File_Format_ed4_Rl.doc 02/04/2010
3BK 11204 0446 DSZZA
1/97
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
Ed. 01 Proposal 01
21/06/07
Creation from B10 document Ed 03 proposal 01 3BK 11204 0373 DSZZA . A new type for the IP counter has aready taken into account in the B10 document. Type 35: o TCSL Id -> RACK Id o New block for the counters related to the whole BSC o New block for the counters related to MFS identified by the GSL Id Please, refer to the B10 document for the historic. B11 modifications: In the B10 document, the IP information was tagged:present when IP supported, they are now no more tagged.
Ed. 01 Proposal 02
12/07/07
Updating with remarks from Y.Gorjux: - Replace the TC_Rack id by the TCSL_SBL in the TC section of the type 35 (refer also to CRQ 216781) - Impact of the A signaling over IP: new block per MSC in type 110 Updating with IP counters on type 35: GSL Id -> GSL-TEI
Ed. 01 Proposal 03
17/09/07
Removing all informations related to G1/G2/DRFU BTS.
Ed 01 Released
08/10/07
EVOLIUM/R&D/OSY/ECH/0446- Refer to 1p3/207237/Review Report - Remarks from Chen Zhangyi: 1) For block 354, the TCSL_SBL should be only one byte. 2) For block 355, the BTS_INDEX should be only one byte. ECH: OK and IP-GSL SBL and MSC SBL should be also on one byte => accepted 3) Add a filler between objects identifiers and counters to keep the two-byte alignment.
Ed04 Released

3BK 11204 0446 DSZZA
2/97
Ed 02 Proposal 01
24/05/08
B11 3BKA20CBR230582: report from B10 CRQ 223453: SLC identifier in measurement type 9 and 25 in case of HSL B11 3BKA20CBR226871 : BSC PM File Format: New block in type 110 for Aflex feature. B11 3BKA20CBR230167: report from B10 3BKA20CBR 207886: PM block on X25 B11 3BKA20CBR225233: New IP blocks for NPO topology 3BKA20CBR234267: New counters block in type 110 for GSL
o o
3BKA20CBR238966: Clarifications on type 35 for G2/TDM BSC CR 3BKA20CBR241145: BSC PM Clarifications on type 110 for NRI block File Format:
Ed 02 Released
01/07/08
3BKA20CBR241594: B11 BSC PM File Format: The BSS version is now defined on 2 bytes CR 3BKA20CBR243383: BSC PM File Format: More Clarifications on type 110 for NRI block CR 3BKA20CBR255905: B11 BSC PM File Format: The counter RMSpw3 is now defined on 2 bytes CR 3BKA20CBR274793: B11 BSC PM File Format: PGHR total size indicated in document changed from 74 to 76 bytes. CR 3BKA20CBR274524: Clarification on CIC use in PM Add chapter 6 for annex 6.1: CIC use in PM 3BKA20CBR289388: Increase neighbour cells limit in RMS. of the BCCH/BSIC
Ed 03 Released
18/05/09
Ed 04 Released
02/04/10
3BKA20CBR286418: More incoming links per cell.
Ed04 Released

3BK 11204 0446 DSZZA
3/97
TABLE OF CONTENTS
SCOPE ........................................................................................................................................................................ 8 1.1 Aim of the document ...................................................................................................................................... 8
GENERAL FILE FORMATS ....................................................................................................................................... 9 2.1 2.2 2.3 BSS files organisation and types ................................................................................................................... 9 Record organisation and record types ....................................................................................................... 10 File Structure ................................................................................................................................................. 11
2.4 BSS file names and numbers ........................................................................................................................ 11 2.4.1 BSS file names ........................................................................................................................................ 11 2.4.2 BSS file numbers..................................................................................................................................... 12 3 Performance Management FILE FORMATS...................................................................................................... 13 3.1 Performance Generic Header Record description ................................................................................... 13 3.1.1 Physical layout of PGHR........................................................................................................................ 14 3.2 PM Result File Formats................................................................................................................................. 17 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 Ed04 Released

3BK 11204 0446 DSZZA
4/97
3.2.29 3.2.30 3.2.31 3.2.32 3.2.33 3.2.34 3.2.35 3.3 4
TYPE 33: Electro Magnetic Environment (EME) Supervision ........................................................... 55 TYPE 34: Voice Group Call Services (VGCS) ..................................................................................... 56 TYPE 35: IP MEASUREMENTS................................................................................................................. 56 Type 36 TO TYPE 109: (NOT USED) ..................................................................................................... 58 TYPE 110: OVERVIEW MEASUREMENTS................................................................................................ 58 TYPE 111 TO TYPE 179: (NOT USED)................................................................................................... 61 TYPE 180: TRAFFIC FLOW MEASUREMENTS ........................................................................................ 62
Directory File.................................................................................................................................................. 63
Trace Management FILE FORMATS ................................................................................................................... 64 4.1 General Trace file formats .......................................................................................................................... 64
4.2 IMSI Radio Trace file formats ...................................................................................................................... 65 4.2.1 Trace Result File Format ...................................................................................................................... 66 4.2.2 IMSI Basic Trace file format ................................................................................................................. 72 5. GLOSSARY AND ABBREVIATIONS ........................................................................................................................ 94 5.1 6. Glossary ........................................................................................................................................................... 94
ANNEX...................................................................................................................................................................... 96 6.1 CIC use in PM .................................................................................................................................................. 96
Ed04 Released

3BK 11204 0446 DSZZA
5/97
INTERNAL REFERENCED DOCUMENTS

[1] [2] BSS Counters catalogue 3BK 11203 0173 DSZZA BSS Telecom Parameters 3BK 11203 0172 DSZZA MIB specification document 3BK 11204 0443 DSZZA O&M A-bis interface 3BK 11204 0447 DSZZA FBS - Performance Management 3BK 11204 0477 DSZZA FBS Logical configuration management 3BK 11204 0471 DSZZA FB Management of Trace Services 3BK 11204 0404 DSZZA Layer 3 Message Dictionary A Interface 3BK 11203 0176 DSZZA Radio Measurements 3BK 11202 0523 DSZZA
[3] [4] [5] [6] [7] [9] [10]
REFERENCED DOCUMENTS
RELATED DOCUMENTS
[A] [B] [C] BSS Counters catalogue 3BK 11203 0173 DSZZA BSS Telecom Parameters 3BK 11203 0172 DSZZA BSC Counters block Layout 3BK ???? AAAA PC ZZA
PREFACE
This document describes for release B11, the format of the PM files (PM result files, Trace Management result files) exchanged between the BSC and the OMC-R.
For the B11 release the impacts on files format are:
Ed04 Released

3BK 11204 0446 DSZZA
6/97
Creation of a new type 35 for IP counters (already taken into account in the B10 document)
Ed04 Released

3BK 11204 0446 DSZZA
7/97
1
1.1
SCOPE
Aim of the document
The aim of this document is to provide the description of the PM files exchanged between the BSC and the OMCR. 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.
B11 applicability
This section describes the specific requirements relevant for B11 release of the Alcatel BSS. The list counters applicable for B11 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 B11 release of the Alcatel BSS.
Ed04 Released

3BK 11204 0446 DSZZA
8/97
2 2.1
GENERAL FILE FORMATS 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 GPMF HPMF OPMF PMDF TRCF ITRF
File Type Number 03 04 10 12 13 16
Description Generic Performance Measurement File History Performance Measurement File Observation Performance Measurement File Performance Measurement Directory File Trace Result File IMSI Trace Result File
Table 1: BSS File Types
Ed04 Released

3BK 11204 0446 DSZZA
9/97
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 Record Sequence Number
2 bytes 2 bytes System Record Header (SRH)
Record Type Number File Type Number
1 byte 1 byte
(absent within transmission settings file)
max. 250 bytes Record content
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 GPMR OPMR PGHR DPMR TRHR TRDR ITDR
Record Type Number 03 09 12 14 15 16 20
Description Global Performance Measurement Record Observation Perf. Measurement Record Performance Generic Header Record Directory Performance Measurement Record Trace generic Header Record Trace Result Data Record IMSI Trace result Data Record
Reference 3.2 3.2 3.1 3.3 4.1 4.2 0
Ed04 Released

3BK 11204 0446 DSZZA
10/97
2.3
File Structure
Files are constructed with the following Record Types:
Record 0 PGHR PGHR DPMR TRHR TRHR
Record 1 OPMR GPMR DPMR TRDR ITDR
Record 2 OPMR GPMR DPMR TRDR ITDR
... ... ... ... ... ...
Record N OPMR GPMR DPMR TRDR ITDR
File Type Names OPMF GPMF PMDF TRCF 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
Ed04 Released

3BK 11204 0446 DSZZA
11/97
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 1 PMOBS-cc 2 PMDIR--TRACE-FR TRACE-FB
311 490 3 320 325 500 2010 2011
Files for Trace
IMSI Basic Trace Result File IMSI Radio Trace Result File
1 For the measurement type number 110 or 180, ccc = 110 or 180. For the measurement type = 01..09, 18, 19 or 25..32, ccc = -nn where nn is the measurement type number. 2 cc is the measuerement type number: 10..15. 3 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..342, 420 and 490.
Ed04 Released

3BK 11204 0446 DSZZA
12/97
3 3.1
PERFORMANCE MANAGEMENT FILE FORMATS 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 System Record Header (SRH) BSS Version BSC Release FILLER Managed Object Class Managed Object Instance File Creation Measurement Type Total Size Number of Records Begin Collection Time Size (Bytes) 6B 2B 1B 1B 2B 2B 16B 2B 4B 2B 16B (See 2.2)
End Collection Time FILLER Sample Percentage Sample Rate Reduced FILLER FFh
16B 3B 1B 1B 1B nB Remaining space in file record 0 (FFh FFh FFh) (default: FFh)
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-Phase-Version: For the BSS version values please refer to the last edition of the OMC-BSS MIB Specification B11 document ref [3].
BSS Version:
Ed04 Released

3BK 11204 0446 DSZZA
13/97
BSC Release Managed Object Class: Managed Object Instance: File Creation: Measurement Type: Total size: Number of Records: Begin Collection Time: End Collection Time: Sample Percentage: Sample Rate Reduced:
BSC-Release: For the values, please refer to the MIB Specification, for information: (34) for BSC B11 Measurement measurement-ID defined in Measurement Object Class Time and date given in an ASCII format from tenth of second to year Measurement-Type (ex (110) for measurement type 110) equal to (Record Size) * (Number of Records); Record Size is measurement type dependent (see to 3.2.1 to 3.2.35) Integer Time and date given in an ASCII format from tenth of second to year Time and date given in an ASCII format from tenth of second to year Sample-Rate (value 0 to 100 or 255) 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 - MSB (not used) 0 1
Rec. Seq. Nbr.
Integer
- LSB - MSB
2 3
Record Type File Type
integer integer
4 5
BSS Version.
Integer
- LSB - MSB
6 7 8
integer BSC Release
Filler
integer
(FFh)
Ed04 Released

3BK 11204 0446 DSZZA
14/97
Managed Object Class (MOC)
integer
- LSB - MSB (not used)
10 11
Managed Object Instance (MOI)
integer
- LSB - MSB
12 13
File Creation
1 Character (tenth of sec.) 1 Character ( . ) 1 Character (sec) 1 Character (sec) 1 Character (min.) 1 Character (min.) 1 Character (hour)
14 15 16 17 18 19
20 1 Character (hour) 1 Character (day) 1 Character (day) 1 Character (month) 1 Character (month) 1 Character (year) 1 Character (year) 1 Character (year) 1 Character (year) 21 22 23 24 25 26 27 28 29
Ed04 Released

3BK 11204 0446 DSZZA
15/97
MeasurementType
integer
- LSB - MSB (not used)
30 31
Total Size
integer
- MSW, LSB - MSW, MSB - LSW, LSB - LSW, MSB
32 33 34 35
Number of Rec.
Integer
- LSB - MSB
36 37
Begin Collect Time
(as above: File Creation)
38 53
End Collect Time
(as above: File Creation)
54 69
Filler
integer integer integer
(FFh) (FFh) (FFh)
70 71 72
integer Sample Percentage boolean Sample Rate Reduced integer Filler (FFh)
73 74 75
FFh FFh
...............
FFh FFh
Ed04 Released

3BK 11204 0446 DSZZA
16/97
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. 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: 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)
Ed04 Released

3BK 11204 0446 DSZZA
17/97
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 5. CELL-ID: TRX TS: 2 bytes as above 1 byte (0 7) TRX Number: 1 byte as above Subchannel: 1 byte (0 or 1)
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:
nbr of bytes System Record Header (SRH) (see 6 bytes rec seq
06
from 01 onwards 03 (GPMR) 03 (GPMF)
2.2)
See 3.2.1 to 3.2.9 and 3.2.16 to 3.2.35. PM Counter Results
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:
Ed04 Released

3BK 11204 0446 DSZZA
18/97
nbr of bytes System Record Header (SRH) (see 6 bytes rec seq
06
from 01 onwards 09 (OPMR) 10 (OPMF)
2.2)
Observation Results
See 3.2.10 to 3.2.15.
FILLER
Remaining space in record
Ed04 Released

3BK 11204 0446 DSZZA
19/97
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) BLOCK LENGTH (refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] ..
2B 2B 2B
CELL COUNTERS repeated for each cell
BLOCK TYPE (012) BLOCK LENGTH (refer to documents [A] and [C]) TRX-ID (BTS-INDEX+Sect. Nb.+TRX. Nb.) Filler Refer to documents [A] and [C] ..
2B 2B 3B 1B
TRX COUNTERS repeated for each TRX
Ed04 Released

3BK 11204 0446 DSZZA
20/97
3.2.1.1
Physical layout of contents of TYPE 01

Layout (Intel) Octet Count
Description
Cell counters (repeated N times)
7 . . . . . . . . . . . bit . . . . . . . . . . 0 Block Type integer integer - LSB - MSB 0 1 2 3
integer
Block Length integer
- LSB
- MSB
BTS INDEX Sector Number
integer (1 255) integer (1 6)
4 5
C01
integer
5 6 8 9
Ed04 Released

3BK 11204 0446 DSZZA
21/97
C02
integer
10 11 12 13
C04
integer
14 15 16 17
C07
integer
18 19 20 21
. . . etc. for the remaining 4B counters . . . and 7 . . . . . . . . . . . bit . . . . . . . . . . 0 Block Type integer integer integer Block Length integer - MSB 3 - LSB - MSB - LSB 0 1 2
BTS INDEX Sector Number
integer (1 255) integer (1 6) integer (1 MaxNbTRX)
4 5 6 7
TRX Number Filler
Ed04 Released

3BK 11204 0446 DSZZA
22/97
C621
integer
- LSB - MSB
8 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.
Ed04 Released

3BK 11204 0446 DSZZA
23/97
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) BLOCK LENGTH (refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B 2B
CELL COUNTERS REPEATED N TIMES
3.2.3
TYPE 3: RESOURCE USAGE MEASUREMENTS CCCH
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).
BLOCK TYPE (030) BLOCK LENGTH (2) CELL-ID (BTS_IDX + Sect. Nb.) BLOCK TYPE (031) BLOCK LENGTH (refer to documents [A] and [C]) CCCH-ID (CELL_ID + TRX-nb + TRX-TS) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B 2B 2B 2B 4B
CCCH COUNTERS REPEATED UP TO 8 TIMES
Ed04 Released

3BK 11204 0446 DSZZA
24/97
Ed04 Released
3BK 11204 0446 DSZZA
25/97
3.2.4
TYPE 4: RESOURCE USAGE MEASUREMENTS SDCCH
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).
BLOCK TYPE (040) BLOCK LENGTH (2) CELL-ID (BTS_IDX + Sect. Nb.) BLOCK TYPE (041) BLOCK LENGTH (refer to documents [A] and [C]) DCCH-ID (CELL_ID + TRX-nb + TRX-TS) Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B 2B 2B 2B 4B
SDCCH COUNTERS REPEATED UP TO 16 TIMES
Ed04 Released

3BK 11204 0446 DSZZA
26/97
3.2.5
TYPE 5: RESOURCE USAGE MEASUREMENTS RTCH
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).
BLOCK TYPE (050) BLOCK LENGTH (2) CELL_ID (BTS_IDX + Sect. Nb.) BLOCK TYPE (051) BLOCK LENGTH (refer to documents [A] and [C]) RTCH-ID (CELL_ID + TRX-nb + TRX-TS) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B 2B 2B 2B 4B
REPEATED N TIMES
RTCH COUNTERS REPEATED UP TO 96 TIMES
Ed04 Released

3BK 11204 0446 DSZZA
27/97
3.2.6
TYPE 6: RTCH HO MEASUREMENTS
The result file has a variable number of records and blocks depending on the number (N) of selected cells.
BLOCK TYPE (060) BLOCK LENGTH (refer to documents [A] and [C]) CELL_ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] . Refer to documents [A] and [C]
2B 2B 2B
Ed04 Released

3BK 11204 0446 DSZZA
28/97
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) BLOCK LENGTH (Refer to documents [A] and [C]) LAPD-LINK-ID 4 Refer to documents [A] and [C]
2B 2B 4B
COUNTERS FOR REPEATED
EVERY LAPD LINK
.. Refer to documents [A] and [C]
BLOCK TYPE (072) BLOCK LENGTH GSL-SBL (Refer to documents [A] and [C])
2B 2B 2B 4B 4B 4B
COUNTERS REPEATED FOR EVERY GSL link
Refer to documents [A] and [C]
...
The counters are defined in TDM mode for GSL Transport with MFS at LAPD level.
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).
Ed04 Released

3BK 11204 0446 DSZZA
29/97
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).
BLOCK TYPE (081) BLOCK LENGTH (Refer to documents [A] and [C]) LINK-ID (CPRA LOGICAL ID) Refer to documents [A] and [C]
2B 2B 2B
COUNTERS REPEATED FOR EVERY X.25 LINK
Ed04 Released

3BK 11204 0446 DSZZA
30/97
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.
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 (072) BLOCK LENGTH GSL-SBL Refer to documents [A] and [C]
2B 2B 2B 4B 4B 4B
...
The counters are defined in TDM mode for GSL Transport with MFS at LAPD level.
BLOCK TYPE (091) BLOCK LENGTH (refer to documents [A] and [C]) LINK-ID Refer to documents [A] and [C] .. Refer to documents [A] and [C] BLOCK TYPE (093) BLOCK LENGTH (refer to documents [A] and [C]) LINK_SET_ID Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B 2B
SL COUNTERS REPEATED FOR EVERY N7 SL
2B 2B 2B
LS COUNTERS REPEATED FOR EVERY LS
Ed04 Released

3BK 11204 0446 DSZZA
31/97
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) S01 S02 S03 S04 S05 S06 S07 S08 S09 S16 S17 S18 S19 S20 S21 S22 S23 S24 S25 S26 BLOCK LENGTH (60) CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) FILLER CHAN_SEIZ_TIME END_INDICATION SEIZURE_TYPE MS_POWER BS_POWER TIMING_ADVANCE NBR_FRAMES_NOT_REPEATED NBR_FRAMES_REPEATED NBR_OF_SABM_AFTER_UA_SENT NBR_OF_PHYSICAL_INFO_SENT NBR_OF_ERRONEOUS_FRAMES_SENT NBR_OF_REJ_FRAMES_SENT NBR_OF_REJ_FRMES_RECEIVED NBR_OF_MS_TX_PWR_MAX_SENT RADIO_LINK_FAILURE_INDICATION PERC_OF_INCOR_SACCH_FRAMES_RX PERC_OF_INCOR_NOT_SACCH_FM_RX SAMPLE_RATE
5 5
2B 2B 5B 1B 16B 16B 1B 1B 2B 2B 2B 2B 2B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B
CHAN_RELEASE_TIME
Time and date given in an ASCII format from tenth of second to year (see physical layout of PGHR in 3.1.1).
Ed04 Released

3BK 11204 0446 DSZZA
32/97
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) R01 R01a R03 R04 R05 R06 R07 R08 R09 R10 R11 R12 R113 R114 R115 R116 R213 BLOCK LENGTH (236) CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) RTCH_TYPE RCVD_TIMESTAMP5 AV_RXLEV_UL_HO AV_RXLEV_DL_HO AV_RXLEV_PBGT_HO AV_RXQUAL_UL_HO AV_RXQUAL_DL_HO AV_RANGE_HO MS_TXPWR BS_TXPWR BTSNUM FILLER BSIC 6 (1) BCCH_FREQ (1) AV_RXLEV_NCELL (1) PBGT(1) BSIC (2)
7
2B 2B 5B 1B 16B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 2B 1B 1B 1B
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 Content 7 0 6 0 5 N 4 C 3 C 2 B 1 C 0 C
Note: It is displayed at the OMC-R operator as two separate values. The BCCH frequency is coded as the absolute radio frequency (0 1023).
Ed04 Released

3BK 11204 0446 DSZZA
33/97
R214 R215 R216
BCCH_FREQ7 (2) AV_RXLEV_NCELL (2) PBGT (2) ...........
2B 1B 1B
Filled with FFh values because only 16 possibles neighbours.
R3213 R3214 R3215 R3216 R04a R05a R17 R118 R119 R120
BSIC6 (32) BCCH_FREQ (32) AV_RXLEV_NCELL (32) PBGT (32) AV_RXLEV_UL_MCHO AV_RXLEV_DL_MCHO SAMPLE_RATE FILLER SCRAMBLING_CODE FDD_FREQ AV_ECNO ........... SCRAMBLING_CODE FDD_FREQ AV_ECNO ...........
7
1B 2B 1B 1B 1B 1B 1B 1B 2B 2B 1B
2B 2B 1B
R818 R819 R820
SCRAMBLING_CODE FDD_FREQ AV_ECNO
2B 2B 1B
Ed04 Released

3BK 11204 0446 DSZZA
34/97
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) HO1 HO2 HO3 HO5 HO5a HO6 HO6a HO7 HO8 HO11 HO12 HO23 HO25 HO26 HO27 HO29 HO30 HO32 HO33 HO34 HO36 HO37 HO38 Honn47 Honn48 Honn49 HO23a BLOCK LENGTH (192) SIGNALLING/TRAFFIC_INDIC INTRA/INTER-CELL_INDICATION HO_REQUIRED_TIME_STAMP5 OLD_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) OLD_RTCH_TYPE NEW_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) NEW_RTCH_TYPE
2B 2B 1B 1B 16B 5B 1B 5B 1B 1B 2B 1B 1B 1B 4B 4B 1B FILLER 1B 4B 1B FILLER 1B 4B 4B 1B FILLER 1B 4B 1B 1B 1B 2B FILLER 4B 1B 1B

REPEATED 16 TIMES 8
INT_HO_SUCCESS_FAILURE_IND
HO_DURATION HO_CAUSE SYNCHRONIZED A_LEV_HO AV_RXLEV_UL_HO AV_RXLEV_DL_HO A_PBGT_HO AV_RXLEV_PBGT_HO A_QUAL_HO AV_RXQUAL_UL_HO AV_RXQUAL_DL_HO A_RANGE_HO AV_RANGE_HO MS_TXPWR BS_TXPWR BSIC
6
FREQ RXLEV A_LEV_MCHO
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).
Ed04 Released

3BK 11204 0446 DSZZA
35/97
HO25a HO26a HO74 HO75
AV_RXLEV_UL_MCHO AV_RXLEV_DL_MCHO SAMPLE_RATE MS_SPEED
4B 4B 1B 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) HO40 HO41 HO42 HO43 HO43a HO44 HO45 HO46 BLOCK LENGTH (28) SIGNALING/TRAFFIC_INDIC INCOMING_HO_INDICATION HO_REQUEST_TIME_STAMP (BSS Clock) NEW_CHAN_ID (CELL_ID + TRX-nb + TRX-TS +SUBCH.) NEW_RTCH_TYPE
2B 2B 1B 1B 16B 5B 1B 1B 1B 1B FILLER 1B
INC_EXT_HO_SUCCESS_FAILURE_IND
SYNCHRONISED SAMPLE_RATE
Ed04 Released

3BK 11204 0446 DSZZA
36/97
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
HO60 HO61 HO62 HO63 HO64 HO64a HO65 HO68 HO80 HO82 HO83 HO84 HO86 HO87 HO89 HO90 HO91 HO93 HO94 HO95 Honn98 Honn99 Honn100 HO80a HO82a HO83a
BLOCK TYPE (140) BLOCK LENGTH (228) SIGNALLING/TRAFFIC_INDIC OUTGOING_HO_INDICATION HO_REQUIRED_TIME_STAMP5 HO_REQUIRED_NBR OLD_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) OLD_RTCH_TYPE
2B 2B 1B 1B 16B 2B 5B 1B 1B 1B 1B 1B 4B 4B 1B 1B 4B 1B 1B 4B 4B 1B 1B 4B 1B 1B 1B 2B 4B 1B 1B 4B 4B
REPEATED 16 TIMES
8
OUT_EXT_HO_SUCCESS_FAILURE_IND
HO_CAUSE FILLER A_LEV_HO AV_RXLEV_UL_HO AV_RXLEV_DL_HO A_PBGT_HO FILLER AV_RXLEV_PBGT_HO A_QUAL_HO FILLER AV_RXQUAL_UL_HO AV_RXQUAL_DL_HO A_RANGE_HO FILLER AV_RANGE_HO MS_TXPWR BS_TXPWR BSIC6 FREQ RXLEV FILLER A_LEV_MCHO AV_RXLEV_UL_MCHO AV_RXLEV_DL_MCHO
Ed04 Released

3BK 11204 0446 DSZZA
37/97
HO111 HO76 HO1101 HO1102 HO1103
SAMPLE_RATE MS_SPEED FILLER SCRAMBLING_CODE FDD_FREQ AV_ECNO ........... SCRAMBLING_CODE FDD_FREQ AV_ECNO ...........
1B 1B 1B 2B 2B 1B
2B 2B 1B
HO8101 HO8102 HO8103
SCRAMBLING_CODE FDD_FREQ AV_ECNO FILLER
2B 2B 1B 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) T01 T01a T02 T03 T04 T04a T05 T06 T07 T08 T15 T16 T17 T18 T19 BLOCK LENGTH (60) CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) RTCH_TYPE CHAN_SEIZ_TIME5 CHAN_RELEASE_TIME END_INDICATION SEIZURE_TYPE MS_POWER BS_POWER TIMING_ADVANCE NBR_FRAMES_NOT_REPEATED NBR_FRAMES_REPEATED NBR_OF_SABM_AFTER_UA_SENT NBR_OF_PHYSICAL_INFO_SENT NBR_OF_ERRONEOUS_FRAMES_SENT NBR_OF_REJ_FRAMES_SENT
5
2B 2B 5B 1B 16B 16B 1B 1B 2B 2B 2B 2B 2B 1B 1B 1B 1B
Ed04 Released

3BK 11204 0446 DSZZA
38/97
T20 T21 T22 T23 T24 T25
NBR_OF_REJ_FRMES_RECEIVED NBR_OF_MS_TX_PWR_MAX_SENT RADIO_LINK_FAILURE_INDICATION PERC_OF_INCOR_SACCH_FRAMES_RX PERC_OF_INCOR_NOT_SACCH_FM_RX SAMPLE_RATE
1B 1B 1B 1B 1B 1B
3.2.16 TYPE 16: (NOT USED)
3.2.17 TYPE 17: (NOT USED)
Ed04 Released

3BK 11204 0446 DSZZA
39/97
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) BLOCK LENGTH (refer to documents [A] and [C]) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B
BLOCK TYPE (181) BLOCK LENGTH (Refer to documents [A] and [C]) LINK-ID (CIC) Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B 2B
Repeated for each A channel
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.
BLOCK TYPE (190) BLOCK LENGTH (Refer to documents [A] and [C]) CELL_ID (BTS_IDX + Sect. Nb.) Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B
CELL COUNTERS
Repeated N times
Ed04 Released

3BK 11204 0446 DSZZA
40/97
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.
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) BLOCK LENGTH (refer to documents [A] and [C]) LINK-ID Refer to documents [A] and [C] . Refer to documents [A] and [C]
2B 2B 2B 4B 4B 4B
REPEATED FOR EVERY N7 SL
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. 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) BLOCK LENGTH (2)
2B 2B
global block only in the record
Ed04 Released

3BK 11204 0446 DSZZA
41/97
SERVING CELL_ID (BTS_IDX + Sect. Nb.) BLOCK TYPE (261) BLOCK LENGTH (Refer to documents [A] and [C]) MCC_MNC FILLER LAC CI Refer to documents [A] and [C] . Refer to documents [A] and [C]
2B 2B 2B 3B 1B 2B 2B
number 1 repeated up to 64 times (i.e. per adjacent cell identified by MCC+MNC+LAC+CI)
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 MCC d2 MNC d3 MNC d2
3 2 MCC d1 MCC d3 MNC d1
1 Octet 1 Octet 2 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
Ed04 Released

3BK 11204 0446 DSZZA
42/97
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.
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) BLOCK LENGTH (2) TARGET CELL_ID (BTS_IDX + Sect. Nb.) BLOCK TYPE (271) BLOCK LENGTH (Refer to documents [A] and [C]) MCC_MNC FILLER LAC CI Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B 2B 2B 2B 3B 1B 2B 2B
global block only in the record number 1 repeated up to N times (i.e. per adjacent cell identified by MCC+MNC lac+ci)
9
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.
9
N is the maximum own cells per BSC MAX-CELL defined in [6] (e.g. 264 for G2 BSC or 500 for Mx BSC).
Ed04 Released

3BK 11204 0446 DSZZA
43/97
The result file has a variable number of records and blocks depending on the number of selected cells.
BLOCK TYPE (280) BLOCK LENGTH (refer to documents [A] and [C]) CELL_ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C]
2B 2B 2B
CELL COUNTERS
REPEATED N TIMES
Refer to conter catalog
Ed04 Released

3BK 11204 0446 DSZZA
44/97
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.
BLOCK TYPE (290) BLOCK LENGTH (Refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B 2B
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) BLOCK LENGTH (Refer to documents [A] and [C]) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B
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:
Ed04 Released

3BK 11204 0446 DSZZA
45/97
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) PAR_X(1) . PAR_X(N) 1B 1B 1B Example of use: TAB-PAR_MEAS_LEVEL
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) PR_X(1) . PR_X(N) 1B 1B 1B Example of use: TPR_CIN, TPR_CIF
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) PR_XY(1,0) . 1B or 3B - Example of use: TPR_BFI_RXLEV_UL (1 B) TPR_RXQUAL_DL_RXLEV_DL (3 B)
Ed04 Released

3BK 11204 0446 DSZZA
46/97
PR_XY(M,0) PR_XY(0,1) PR_XY(1,1) . PR_XY(M,N) --
For 3 bytes entries the order is Ci, PWRi, TAi
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) MR_XY(1) . MR_XY(N) 4B 4B 4B Example of use: TMR_RXQUAL_UL_RXLEV_UL
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).
Ed04 Released

3BK 11204 0446 DSZZA
47/97
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) BLOCK LENGH (72) CELL_ID(BTS-INDEX + Sect. Nb. ) RMSpt5 TAB_PAR_MEAS_LEVEL Alignment-Filler-Byte RMSpt1 TAB_PAR_MEAS_C/I Alignment-Filler-Byte RMSpt2 TAB_PAR_MEAS_STAT_BFI Alignment-Filler-Byte RMSpt3 TAB_PAR_MEAS_STAT_S Alignment-Filler-Byte RMSpt4
RMS-CELL
2B 2B 2B 9B 1B 9B 1B 9B 1B 9B 1B 9B 1B 9B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B
REPEATED FOR EACH CELL
Table of 9 parameters
TAB_PAR_MEAS_PATH_BALANCE Alignment-Filler-Byte
RMSpt6
TAB_PAR_MEAS_STAT_TA Alignment-Filler-Byte
RMSpa RMSpb RMSpc RMSpd RMSpe RMSpf RMSpg RMSph RMSpi
PAR-EN-BALANCED-CI PAR_TA_STAT PAR_VQ_AVERAGE PAR_VQ_RXLEV PAR_VQ_RXQUAL PAR_VQ_RXQUAL_VS_RXFER PAR_VQ_GOOD_RXFER PAR_VQ_BAD_RXFER PAR_VQ_INTF_THRESHOLD
Boolean
Ed04 Released

3BK 11204 0446 DSZZA
48/97
RMSpj
PAR_VQ_FER_THRESHOLD
1B
BLOCK TYPE (3110) BLOCK LENGH (135)
RMS-TRX
2B 2B 3B 1B 1B 1B 1B 1B 1B 1B 1B 4B 4B 4B 4B 4B 1B 1B 4B 2B 2B
REPEATED FOR EACH TRX for N=1 to MaxNbrTRX
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS20 RMS22 TRE_BAND IND_RMS_RESTARTED

10
Refer to note 1 for coding
Boolean
RMSpw1 BS_TX_PWRMAX
RMSpw2 MS_TX_PWRMAX 10 RMS21 RMS23 RMS24 RMS31 RMS32 RMS33 RMS34 RMS35 RMS36 RMS37 RMS38 RMS10 RMS11
10
IND_TRE_OVERLOAD IND_CI_PARTIAL_OBSERVATION IND_CI_OVERFLOW TOT_SEIZ_TCH TOT_MEAS TOT_MEAS_L1INFO_NOL3INFO TOT_MEAS_DTX_UL TOT_MEAS_DTX_DL PERC_TA_GT_TA_STAT MAX_ TA TOT_EMR VQ_NOISY_UL_INTERFERENCE VQ_NOISY_DL_INTERFERENCE
Boolean 2 bits, Refer to note 2 for

coding
Boolean
BSC shall select the value for inner or outer in case of concentric cell
Ed04 Released

3BK 11204 0446 DSZZA
49/97
RMS12 RMS13 RMS14 RMS15 RMS16 RMS17 RMS18 RMS3b RMS4b
VQ_NOISY_UL_COVERAGE VQ_NOISY_DL_COVERAGE VQ_NOISY_UL_UNDEFINED VQ_NOISY_DL_UNDEFINED VQ_NOISY_UL_BAD_FER VQ_NOISY_UL_GOOD_FER VQ_ABNORMAL_BAD_FER TMR_RXQUAL_UL_RXLEV_UL TMR_RXQUAL_DL_RXLEV_DL
2B 2B 2B 2B 2B 2B 2B 40B 40B
Table of 10 Maximum results Table of 10 Maximum results
RMS-BFI
2B 2B 3B 1B 100B 40B 10B 4B 10B 4B
REPEATED FOR EACH TRX
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS5a RMS5b RMS6a RMS6b RMS7a RMS7b TPR_BFI_RXLEV_UL TMR_BFI_RXLEV_UL TPR_RADIO_LINK MAX_RADIO_LINK TPR_PATH_BALANCE MAX_PATH_BALANCE
Table of 10 X 10 results Table of 10 Maximum results Table of 10 1B results
Table of 10 1B results
RMS-UL
2B 2B 3B 1B 240B
Table of 8 X 10 results with 3B per result
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS3a TPR_RXQUAL_UL_RXLEV_UL
Ed04 Released

3BK 11204 0446 DSZZA
50/97
RMS-DL
2B 2B 3B 1B 240B
Table of 8 X 10 results with 3B per result
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS4a TPR_RXQUAL_DL_RXLEV_DL
BLOCK TYPE (3116) RMS-BFI-AMR, RMS-TA BLOCK LENGH (121) TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS50a RMS50b RMS51 RMS52 RMS53 RMS54 RMS44a RMS44b RMS45a RMS45b TPR_TIMING_ADVANCE MAX_TIMING_ADVANCE TPR_UL_RXLEV_TA_BAND TPR_DL_RXLEV_TA_BAND TPR_UL_RXQUAL_TA_BAND TPR_DL_RXQUAL_TA_BAND AMR_FR_UL_BAD MAX_AMR_FR_UL_BAD AMR_HR_UL_BAD MAX_AMR_HR_UL_BAD
2B
2B 3B 1B 10B 4B 20B 20B 20B 20B 8B 4B 5B 4B 2B Table of 5 1B results Table of 10 2B results Table of 10 2B results Table of 10 2B results Table of 10 2B results Table of 8 1B results Table of 10 1B results
RMSPw3 MAX_POWER_PER_TRX *
*: 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).
Ed04 Released

3BK 11204 0446 DSZZA
51/97
BLOCK TYPE (3117) RMS-AMR-UL BLOCK LENGH (214) TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS46a RMS46b RMS48a RMS48b AMR_FR_UL_RXLEV_UL MAX_AMR_FR_UL_RXLEV_UL AMR_HR_UL_RXLEV_UL MAX_AMR_HR_UL_RXLEV_UL
2B
2B 3B 1B 80B 40B 50B 40B

Table of 10 X 8 results Table of results 10 maximum
BLOCK TYPE (3118) RMS-AMR-DL BLOCK LENGH (214) TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMS47a RMS47b RMS49a RMS49b AMR_FR_DL_RXLEV_DL MAX_AMR_FR_DL_RXLEV_DL AMR_HR_DL_RXLEV_DL MAX_AMR_HR_DL_RXLEV_DL
2B
2B 3B 1B 80B 40B 50B 40B

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

3BK 11204 0446 DSZZA
52/97
Alignment-Filler-Byte Rms41a Rms41b Rms42a Rms42b Rms43a Rms43b AMR_WB_GMSK_FR_UL_BAD MAX_AMR_WB_GMSK_FR_UL_BAD AMR_WB_GMSK_FR_UL_RXLEV_UL
1B 3B 4B 30B
Table of 3 results 1 maximum result
Table of 10 X 3 results
Table of results 10 maximum
MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL 40B AMR_WB_GMSK_FR_DL_RXLEV_DL 30B
MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL 40B
BLOCK TYPE (3120) BLOCK LENGH (242 max)
RMS-CIN
2B 2B 3B 1B 2B 1B 10B 4B
from one to 11 times

11
(min 0, max 154 cells )
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte RMSp80 NEIGB_CELL_ID(BCCH_ARFCN7, BSIC6) RMS8a RMS8b TPR_CIN MR_CIN
Repeated up to 14 times
12
with no inserted filler
CI Vector Maximum result
BLOCK TYPE (3121) BLOCK LENGH (244max)
RMS-CIF
2B 2B 3B 1B
from zero to two times (max 21 EMO ARFNs)
TRX_ID(BTS-INDEX+Sect. Nb.+TRX Nb.) Alignment-Filler-Byte

11
12
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]).
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.
Ed04 Released

3BK 11204 0446 DSZZA
53/97
RMSp90 Frequency ARFCN RMS9a RMS9b TPR_CIF MR_CIF
2B 10B 4B
Repeated up to 15 times
12
END
CI vector Maximum result
for TRX
END FOR 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 EGSMDCS1800) 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 PGSMDCS1800). 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
Ed04 Released

3BK 11204 0446 DSZZA
54/97
Note 2: coding of the IND_CI_PARTIAL_OBSERVATION 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.
2B 2B 2B
CELL counters Repeated
N times
3.2.29 TYPE 33: Electro Magnetic Environment (EME) Supervision This type of counters allow 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) BLOCK LENGTH (refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.)
2B 2B 2B
Cell counters Repeated N times
Ed04 Released

3BK 11204 0446 DSZZA
55/97
N is the number of cells covered by BSC and selected for PM jobs. 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) BLOCK LENGTH (refer to documents [A] and [C]) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B
2B 2B 2B
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 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.
Ed04 Released

3BK 11204 0446 DSZZA
56/97
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) BLOCK LENGTH (refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] .
2B 2B 2B
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) BLOCK LENGTH (Refer to documents [A] and [C]) TCSL_SBL Filler Refer to documents [A] and [C] .
2B 2B 1B 1B
COUNTERS REPEATED FOR EVERY TC rack
BSC-TC rack block:
BLOCK TYPE (354) BLOCK LENGTH (Refer to documents [A] and [C]) TCSL_SBL Filler Refer to documents [A] and [C] .
2B 2B 1B 1B
FOR EVERY BSC-TC rack linkTC COUNTERS REPEATED
Reported only on TCSL mode with TC
BTS block: Ed04 Released

3BK 11204 0446 DSZZA
57/97
BLOCK TYPE (355) BLOCK LENGTH (Refer to documents [A] and [C]) TCSL_SBL BTS-ID (BTS INDEX ) Refer to documents [A] and [C] .
2B 2B 1B 1B
For every BTS COUNTERS REPEATED
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.
Abis link block:
BLOCK TYPE (358) BLOCK LENGTH (refer to documents [A] and [C]) ABIS-NUM Refer to documents [A] and [C] .
2B 2B 2B
COUNTERS REPEATED FOR EVERY IPoE1ABIS LINK
Reported only on Abis with IPoE1 (Abis-Transport-Mode= IP unframed or IP framed)
3.2.32 Type 36 TO TYPE 109: (NOT USED)
3.2.33 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
Ed04 Released

3BK 11204 0446 DSZZA
58/97
Remark:
Cell related counters are split into 6 different blocks so that each block can fit into a 256bytes record.
BLOCK TYPE (1110) BLOCK LENGTH (Refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B 2B
BLOCK TYPE (1120) BLOCK LENGTH (Refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] Refer to documents [A] and [C] BLOCK TYPE (1122) BLOCK LENGTH (refer to documents [A] and [C]) CELL-ID (BTS INDEX + Sect. Nb.) Refer to documents [A] and [C] Refer to documents [A] and [C]
2B 2B 2B
2B 2B 2B
2B 2B 2B
Note: the counters on TRX Power Saving feature have valid values even the feature is not activated and even there is no MC module on by the MC modules on the BTS.
BLOCK TYPE (1125) BLOCK LENGTH CELL-ID (BTS INDEX + Sect. Nb.) BLOCK TYPE (1130) BLOCK LENGTH (Refer to documents [A] and [C]) TRX-ID (BTS-INDEX+Sect. Nb.+TRX. Nb.) Filler
2B 2B 2B 2B 2B 3B 1B
TRX counters REPEATED
Ed04 Released

3BK 11204 0446 DSZZA
59/97
Refer to documents [A] and [C] . Refer to documents [A] and [C]
FROM 0 TO MaxNbTRX TIMES
BLOCK TYPE (1135) BLOCK LENGTH (Refer to documents [A] and [C]) LINK-ID (CIC) Refer to documents [A] and [C] . Refer to documents [A] and [C]
2B 2B 2B
COUNTERS REPEATED FOR EVERY N7 SL
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 (1140) BLOCK LENGTH (Refer to documents [A] and [C]) Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B
COUNTERS RELATED TO THE WHOLE BSS
BLOCK TYPE (1142) BLOCK LENGTH (Refer to documents [A] and [C]) MSC-SBL Filler Refer to documents [A] and [C] .. Refer to documents [A] and [C]
2B 2B 1B 1B
FOR EVERY MSC COUNTERS REPEATED
NRI block:
BLOCK TYPE (1143) BLOCK LENGTH (Refer to documents [A] and [C]) MSC-SBL Filler BLOCK TYPE (1144) BLOCK LENGTH (Refer to documents [A] and [C]) NRI Num
2B 2B 1B 1B 2B 2B 2B
REPEATED FOR EACH
MSC
Ed04 Released

3BK 11204 0446 DSZZA
60/97
Refer to documents [A] and [C] . Refer to documents [A] and [C]
FROM 1 TO
Max 9 NRIs
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) BLOCK LENGTH GSL-SBL (Refer to documents [A] and [C])
2B 2B 2B 4B 4B 4B
...
All the counters are defined both on IP mode or 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
3.2.34 TYPE 111 TO TYPE 179: (NOT USED)
Ed04 Released

3BK 11204 0446 DSZZA
61/97
3.2.35 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.
BLOCK TYPE (1800) BLOCK LENGTH (2) CELL-ID (BTS INDEX + Sect. Nb.) BLOCK TYPE (1810) BLOCK LENGTH (Refer to documents [A] and [C]) MCC_MNC13 FILLER LAC
13
2B 2B 2B 2B 2B 3B 1B 2B 2B 4B 4B 4B
REPEATED FOR EACH SERVING CELL up to N times
14
CELL COUNTERS REPEATED CELL COUNTERS FOR EACH REPORTED TARGET CELLS
CI13 Refer to documents [A] and [C] Refer to documents [A] and [C]
13
14
MCC_MNC, LAC and CI identify the reported serving cell. Refer to type 26 for the codage description. N is the maximum own cells per BSC MAX-CELL defined in [6] (e.g. 264 for G2 BSC or 500 for Mx BSC).
Ed04 Released

3BK 11204 0446 DSZZA
62/97
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) BLOCK_ID (1000) BLOCK_LENGTH (22) MEASUREMENT_ID JOB_PM_ERRORINFO
15
6B 2B 2B 2B 2B 12B 2B 2B 1B 1B
(See 2.2)
THIS RECORD CAN BE REPEATED A MAX. OF 35 TIMES IN THE DIRECTORY FILE
RESULT_FILE_IDENTITY NBR_RECORDS RECORD_SIZE MEASUREMENT_TYPE LAST_RESULT_INDICATOR
Usage: System Record Header: number of bytes = 06 record sequence number = from 00 onwards record type = 14 (DPMR) file type = 12 (PMDF) Measurement-Id (integer) Job-PM-ErrorInfo (integer) File-NameVersion (refer to 2.4.1) This field indicates the number of records used for the construction of the related result file. 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 (example: (110) for measurement type 110) Last-PM-Result-Indicator (False or true)
Measurement_Id: Job_PM_ErrorInfo: Result_File_Identity: Nbr_records Record_size
Measurement_Type: Last_Result_Indicator:
15
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'.
Ed04 Released

3BK 11204 0446 DSZZA
63/97
4 4.1
TRACE MANAGEMENT FILE FORMATS 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)
6B 2B 6B 16B (See 2.2)
System Record Header (SRH) Managed Object Class Managed Object Instance File Creation
File Closure Number Of Records File Sequence Number Last File Info File Closure Reason
16B 2B 1B 1B 1B
msc_invoke_trace_msg
64B
Classmark BSC Trace Type
5B 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).
Ed04 Released

3BK 11204 0446 DSZZA
64/97
Managed Object Class

= = = = = = =
TRACE BSC-trace-number = trace originator (1 byte) + 1 spare byte + trace number (2 bytes) + MSC transaction number (2 bytes)
Managed Object Instance File Creation File Closure Number Of Records File Sequence Number Last File Info File Closure Reason:
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). 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 composing the file. gives the file ordering in case the transaction has been traced over 20 Kbytes, thus multiple files are needed. boolean; if true this is the final file 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 Classmark BSC Trace Type
= = =
all Hex FF if no message all Hex FF if no Classmark 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.
Ed04 Released

3BK 11204 0446 DSZZA
65/97
4.2.1 4.2.1.1
Trace Result File Format CIRCUIT IDENTITY CODE Format of Circuit Identity Code record
SYSTEM RECORD HEADER (SRH) BLOCK TYPE (value 300) BLOCK LENGTH (value 2) CIC IMSI
6B 2B 2B 2B 9B
(See 2.2)
4.2.1.2
SDCCH Observation Format of SDCCH OBSERVATION record
SYSTEM RECORD HEADER (SRH) BLOCK TYPE (100) BLOCK LENGTH (66) CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) FILLER CHAN_SEIZ_TIME5 CHAN_RELEASE_TIME5 END_INDICATION SEIZURE_TYPE MS_POWER BS_POWER TIMING_ADVANCE NBR_FRAMES_NOT_REPEATED NBR_FRAMES_REPEATED NBR_OF_SABM_AFTER_UA_SENT NBR_OF_PHYSICAL_INFO_SENT NBR_OF_ERRONEOUS_FRAMES_SENT NBR_OF_REJ_FRAMES_SENT NBR_OF_REJ_FRMES_RECEIVED NBR_OF_MS_TX_PWR_MAX_SENT RADIO_LINK_FAILURE_INDICATION PERC_OF_INCOR_SACCH_FRAMES_RX PERC_OF_INCOR_NOT_SACCH_FM_RX SAMPLE_RATE TSC FHS_ID (=FFh in non freq. hopping case) MAIO (=FFh in non freq. hopping case) ARFN (=FFh in freq. hopping case)
6B 2B 2B 5B 1B 16B 16B 1B 1B 2B 2B 2B 2B 2B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 2B
(See 2.2)
Ed04 Released

3BK 11204 0446 DSZZA
66/97
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) BLOCK TYPE (110) BLOCK LENGTH (235) CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) RTCH_TYPE INFO-RECEIVED_TIMESTAMP5 AVERAGE_RXLEVEL_UPLINK_HO AVERAGE_RXLEVEL_DOWNLINK_HO AVERAGE_RXLEVEL_DOWNLINK_PBGT AVERAGE_RXQUALITY_UPLINK_HO AVERAGE_RXQUALITY_DOWNLINK_HO AVERAGE_RANGE_HO MS_TXPOWER BS_TXPOWER BTSnumber BSIC6 (1) BCCH_FREQUENCY7 (1) AVG_RXLEVEL_NEIGHBOURCELL (1) POWERBUDGET(1) BSIC (2) BCCH_FREQUENCY (2) AVG_RXLEVEL_NEIGHBOURCELL (2) POWERBUDGET (2) ........... BSIC6 (BTSnum) BCCH_FREQUENCY (BTSnum) AVG_RXLEV_NEIGHBCELL (BTSnum) POWERBUDGET (BTSnum) ........... BSIC6 (32) BCCH_FREQUENCY (32) AVG_RXLEVEL_NEIGHBOURCELL (32) POWERBUDGET (32) AV_RXLEV_UL_MCHO AV_RXLEV_DL_MCHO SAMPLE_RATE SCRAMBLING_CODE (1) FDD_FREQ (1)
6B 2B 2B 5B 1B 16B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 2B 1B 1B 1B 2B 1B 1B
(See 2.2)
1B 2B 1B 1B Filled with 1B 2B 1B 1B 1B 1B 1B 2B 2B H-FF values
Ed04 Released

3BK 11204 0446 DSZZA
67/97
AV_ECNO (1) SCRAMBLING_CODE (2) FDD_FREQ (2) AV_ECNO (2) . SCRAMBLING_CODE (8) FDD_FREQ (8) AV_ECNO (8) TSC
1B 2B 2B 1B 2B 2B 1B 1B
4.2.1.4
Internal Handover Observation
Format of INTERNAL HANDOVER OBSERVATION record

SYSTEM RECORD HEADER (SRH) BLOCK TYPE (120) BLOCK LENGTH (193) SIGNALLING/TRAFFIC INDICATOR INTRA/INTERCELL INDICATOR HO REQUIRED TIME STAMP 16 OLD_CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) OLD_RTCH_TYPE NEW_CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) NEW_RTCH_TYPE SUCCESS/FAIL INDICATION HO DURATION (tenths of sec.) HO CAUSE SYNCHRONIZED FLAG A_LEV_HO AV_RXLEV_UL_HO AV_RXLEV_DL_HO A_PBGT_HO FILLER AV_RXLEV_PBGT_HO A_QUAL_HO FILLER AV_RXQUAL_UL_HO AV_RXQUAL_DL_HO A_RANGE_HO FILLER AV_RANGE_HO MS_TXPWR BS_TXPWR 6B 2B 2B 1B 1B 16B 5B 1B 5B 1B 1B 2B 1B 1B 1B 4B 4B 1B 1B 4B 1B 1B 4B 4B 1B 1B 4B 1B 1B (See 2.2)
16
Time and date given in an ASCII format from tenth of second to year (see physical layout of PGHR in 3.1.1).
Ed04 Released

3BK 11204 0446 DSZZA
68/97
BSIC6 FREQ RXLEV A_LEV_MCHO FILLER AV_RXLEV_UL_MCHO AV_RXLEV_DL_MCHO SAMPLE_RATE MS_SPEED TSC
1B 2B 4B 1B 1B 4B 4B 1B 1B 1B
REPEATED 16 TIMES 17
4.2.1.5
Incoming Handover Observation
Format of INCOMING HANDOVER OBSERVATION record
SYSTEM RECORD HEADER (SRH) BLOCK TYPE (130) BLOCK LENGTH (28) SIGNALING/TRAFFIC_INDIC INCOMING_HO_INDICATION HO_REQUEST_TIME_STAMP16 NEW_CHAN_ID (CELL_ID + TRX-nb + TRX-TS +SUBCH.) NEW_RTCH_TYPE SUCCESS_FAIL_INDICATION SYNCHRONISED SAMPLE_RATE TSC
6B 2B 2B 1B 1B 16B 5B 1B 1B 1B 1B 1B
(See 2.2)
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).
17
Ed04 Released

3BK 11204 0446 DSZZA
69/97
4.2.1.6
Outgoing Handover Observation
Format of OUTGOING HANDOVER OBSERVATION record
SYSTEM RECORD HEADER (SRH) BLOCK TYPE (140) BLOCK LENGTH (227) SIGNALLING/TRAFFIC INDIC OUTGOING HO INDICAT HO REQUIRED TIME STAMP16 HO REQUIRED NBR OLD_CHAN_ID (CELL_ID + TRX-nb + TRX-TS + SUBCH.) OLD_RTCH_TYPE SUCCESS/FAIL INDICATION HO CAUSE FILLER A_LEV_HO AV_RXLEV_UL_HO AV_RXLEV_DL_HO A_PBGT_HO FILLER AV_RXLEV_PBGT_HO A_QUAL_HO FILLER AV_RXQUAL_UL_HO AV_RXQUAL_DL_HO A_RANGE_HO FILLER AV_RANGE_HO MS_TXPWR BS_TXPWR BSIC6 FREQ RXLEV A_LEV_MCHO FILLER AV_RXLEV_UL_MCHO AV_RXLEV_DL_MCHO SAMPLE_RATE MS_SPEED SCRAMBLING_CODE FDD_FREQ AV_ECNO TSC
6B 2B 2B 1B 1B 16B 2B 5B 1B 1B 1B 1B 1B 4B 4B 1B 1B 4B 1B 1B 4B 4B 1B 1B 4B 1B 1B 1B 2B 4B 1B 1B 4B 4B 1B 1B 2B 2B 1B 1B
(See 2.2)
REPEATED 16 TIMES
17
REPEATED 8 TIMES
Ed04 Released

3BK 11204 0446 DSZZA
70/97
4.2.1.7
RTCH Observation
Format of RTCH OBSERVATION record
SYSTEM RECORD HEADER (SRH) BLOCK TYPE (150) BLOCK LENGTH (66) CHANNEL_ID (CELL_ID + TRX-nb + TRX-TS +SUBCH.) RTCH_TYPE CHAN_SEIZ_TIME16 CHAN_RELEASE_TIME16 END_INDICATION SEIZURE_TYPE MS_POWER BS_POWER TIMING_ADVANCE NBR_FRAMES_NOT_REPEATED NBR_FRAMES_REPEATED NBR_OF_SABM_AFTER_UA_SENT NBR_OF_PHYSICAL_INFO_SENT NBR_OF_ERRONEOUS_FRAMES_SENT NBR_OF_REJ_FRAMES_SENT NBR_OF_REJ_FRMES_RECEIVED NBR_OF_MS_TX_PWR_MAX_SENT RADIO_LINK_FAILURE_INDICATION PERC_OF_INCOR_SACCH_FRAMES_RX PERC_OF_INCOR_NOT_SACCH_FM_RX SAMPLE_RATE TSC FHS_ID (=FFh in non freq. hopping case) MAIO (=FFh in non freq. hopping case) ARFN (=FFh in freq. hopping case) CU_ID (=FFh in freq. hopping case) BSIC6 CLASSMARK 1 CLASSMARK 2 CLASSMARK 3
6B 2B 2B 5B 1B 16B 16B 1B 1B 2B 2B 2B 2B 2B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 1B 2B 1B 2B
(See 2.2)
HEX FF in
1B
case of a
3B
Call trace
4B
Ed04 Released

3BK 11204 0446 DSZZA
71/97
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'.
Ed04 Released

3BK 11204 0446 DSZZA
72/97
IMSI TRACE RESULT DATA RECORD nbr of bytes System Record Header (SRH) (see 2.2) 6 bytes rec seq 06 from 01 onwards 20 (ITDR) (ITRF)
Entry
var
...............
Entry
var
Ed04 Released

3BK 11204 0446 DSZZA
73/97
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 IMSI or IMEI (Traced party) Trace Reference Transaction Id Trace Type Trace Type Used Start Time End Time Trace Event Invocation Message Record Cell ID TRX ID Radio Channel Info Request type End Indication MS Classmark 1 MS Classmark 2 MS Classmark 3 BSIC6 CIC Handover result Handover cause Sequence Number Reason for Record Key: 3 M1 C1 C : : : : :
No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 22 16 17 18 19 20 21
Rep. N N N N N N N N Y Y Y Y Y Y Y Y Y Y Y Y N N
First 3 3 C 3 3 3 3 M1 M1 M1 C1 C1 C1 C1 C1 M1 C1 C1 C1 3
Middle 3 3 C M1 M1 M1 C1 C1 C1 C1 C1 M1 C1 C1 C1 3
Last 3 3 C 3 M1 M1 M1 C1 C1 C1 C1 C1 M1 C1 C1 C1 3
Single 3 3 C 3 3 3 3 3 3 3 3 C C C C C 3 C C C -
Must be provided Not required Must be provided in at least one Trace file If available, provided in at least one Trace file Provided if available Entry can be repeated several time: Y = Yes, N = No
Rep. :
Ed04 Released

3BK 11204 0446 DSZZA
74/97
The tables below give the structure of the different entries:
Type 1 IMSI or IMEI ELEMENT IDENTIFIER (=1) LENGH (=9) IMSI or IMEI 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 Identity digit 1 Identity digit p+1 4 O/E 3 2 1 Type of ident. Identity digit p
Lg 1 1 9
Octet 1 Octets 2 to 9
Ed04 Released

3BK 11204 0446 DSZZA
75/97
with: Type of identity (octet 1) Bits 3 2 1 0 0 1 0 1 0 0 1 1 1 0 0 0 0 0 IMSI IMEI IMEISV (i.e. IMEI with Software Version Number) TMSI (not used for trace) No identity (not used for trace)
All other values are reserved. O/E = Odd/even indication (octet 1) Bit 4 0 1 even number of identity digits odd number of identity digits
Identity digit (octets 2 to 9) Each digit is coded on 4 bits using BCD coding. IMEISV (16 digits): IMEI (15 digits): IMSI (<= 15 digits): Bits 5 to 8 of octet 9 are filled in with '1111B'. Octet 9 is filled in with FFh. 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 ELEMENT IDENTIFIER (=2) LENGH (=2) TRACE NUMBER
integer
- LSB - MSB
Lg 1 1 2
Ed04 Released

3BK 11204 0446 DSZZA
76/97
Type 3 Transaction Id ELEMENT IDENTIFIER (=3) LENGH (=2) MSC-TRANSACTION-NUMBER
integer
- LSB - MSB
Lg 1 1 2
Type 4 Trace Type ELEMENT IDENTIFIER (=4) LENGH (=1) TRACE TYPE One byte coded as described below (for more details, see TS GSM 12.08 ): 8 X 7 0 6 X 5 X 4 X 3 X 2 X 1 X Invoking event* MSC Record Type* BSS Record Type* Priority indication*
Lg 1 1 1
123
123
123
* Same coding as Type 5.
Type 5 Trace Type Used ELEMENT IDENTIFIER (=5) LENGH (=1) TRACE TYPE One byte coded as described below (for more details, see TS GSM 12.08): 8 X 7 0 6 0 5 0 4 1 3 1 2 0 1 0 Invoking event = all events MSC Record Type = 'No MSC trace' BSS Record Type = 'Basic' Priority indication (1 = Priority ; 0 = No priority)
Lg 1 1 1
123
123
123
Ed04 Released

3BK 11204 0446 DSZZA
77/97
Type 6 Start Time ELEMENT IDENTIFIER (=6) LENGH (=16) TIME & DATE String of 16 ASCII characters
1 char. (tenth of sec.) 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)
Lg 1 1 16
Type 7
End Time
Lg
1 1 16
ELEMENT IDENTIFIER (=7) LENGH (=16) TIME & DATE String of 16 ASCII characters
Ed04 Released

3BK 11204 0446 DSZZA
78/97
Type 8 Invocation Message ELEMENT IDENTIFIER (=8) LENGH (var) INVOCATION MESSAGE 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)
Lg 1 1 v a r
Type 9 CELL ID ELEMENT IDENTIFIER (=9) LENGH (=20) CI Cell Identity LAC Location Area Code TIMESTAMP String of 16 ASCII characters
- LSB - MSB integer - LSB - MSB 1 char. (tenth of sec.) 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)
integer
Lg 1 1 2 2 16
Ed04 Released

3BK 11204 0446 DSZZA
79/97
Type 10 TRX ID ELEMENT IDENTIFIER (=10) LENGH (=17) TRX NUMBER TIMESTAMP String of 16 ASCII characters
integer (1..MaxNbTRX) 1 char. (tenth of sec.) 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)
Lg 1 1 1 16
Ed04 Released

3BK 11204 0446 DSZZA
80/97
Type 11 Radio Channel Info ELEMENT IDENTIFIER (=11) LENGH (=155) 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). 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
Lg 1 1 8
It is to be decoded by OMC as follows

8 7 6 5 Channe l Type and TDMA offset TSC H=1 H=0 MAIO part) (low HSN 4 MAIO (high part) spare ARFCN (high part) 3 3 3 Timeslot number 2 1 Byte 1 2
ARFCN (low part)
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
Ed04 Released

3BK 11204 0446 DSZZA
81/97
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). TIMESTAMP String of 16 ASCII characters 1 char. (tenth of sec.) 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)
128
16
Ed04 Released

3BK 11204 0446 DSZZA
82/97
Type 12 Request type ELEMENT IDENTIFIER (=12) LENGH (=17) 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.
Lg 1 1 Byte 1
TIMESTAMP String of 16 ASCII characters
16
Ed04 Released

3BK 11204 0446 DSZZA
83/97
Type 13 End Indication ELEMENT IDENTIFIER (=13) LENGH (=17) 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) TIMESTAMP String of 16 ASCII characters
integer
(0..255)
Lg 1 1 1
16
Ed04 Released

3BK 11204 0446 DSZZA
84/97
Type 14 MS Classmark 1 ELEMENT IDENTIFIER (=14) LENGH (=17) MOBILE STATION CLASSMARK 1 One byte coded as described below (for more details, see TS GSM 04.08): 8 0 7 X 6 X 5 X 4 X 3 X 2 X 1 X
Lg 1 1 1
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 0 0 1 0 1 0 0 1 1 1 0 0 class 1 class 2 class 3 class 4 class 5 (for GSM 900 & DCS 1800/1900) (for GSM 900 & DCS 1800/1900) (for GSM 900 & DCS 1800/1900) (for GSM 900 only) (for GSM 900 only)
All other values are reserved. Revision level Bits 7 6 0 0 0 1 Reserved for Phase 1 Used by Phase 2 MSs
All other values are reserved. TIMESTAMP String of 16 ASCII characters 1 char. (tenth of sec.) 1 char. (.) 1 char. (sec) 16
Ed04 Released

3BK 11204 0446 DSZZA
85/97
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 15 MS Classmark 2 ELEMENT IDENTIFIER (=15) LENGH (=19) MOBILE STATION CLASSMARK 2: 3 octets 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 0 7 X 6 X 5 X 4 X 3 0 2 0 1 X Frequency Capability spare Short Message Capability SS Screening Indicator Pseudo synchronisation capability spare
Lg 1 1 3
123
123
Third octet: coded as described below (for more details, see TS GSM 04.08): 8 X 7 0 6 0 5 0 4 0 3 0 2 X 1 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)
Ed04 Released

3BK 11204 0446 DSZZA
86/97
16
Type 16 BSIC ELEMENT IDENTIFIER (=16) LENGH (=2) NCC Network Colour Code BCC Base station Colour Code
integer integer
(0..7) (0..7)
Lg 1 1 1 1
Type 17 CIC ELEMENT IDENTIFIER (=17) LENGH (=18) CIC integer Circuit Identity Code = 16 bits (top 11 bits contain the trunk-id; other 5 bits contain the timeslot number) derived from Cic-Atrk-Ch0 - MSB - LSB
Lg 1 1 2
1 char. (tenth of sec.) 1 char. (.) 1 char. (sec) 1 char. (sec) 1 char. (min.) 1 char. (min.) 1 char. (hour) 1 char. (hour)
16
Ed04 Released

3BK 11204 0446 DSZZA
87/97
1 char. (day) 1 char. (day) 1 char. (month) 1 char. (month) 1 char. (year) 1 char. (year) 1 char. (year) 1 char. (year)
Ed04 Released

3BK 11204 0446 DSZZA
88/97
Type 18 Handover Result ELEMENT IDENTIFIER (=18) LENGH (=17) 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 0 0 1 0 1 1 1 1 0 0 1 0 1 1 0 0 0 0 1 0 1 0 0 0 Assignment complete Assignment failure Handover complete Handover failure
Lg 1 1 1
16
Ed04 Released

3BK 11204 0446 DSZZA
89/97
Type 19 Handover Cause ELEMENT IDENTIFIER (=19) LENGH (=18) 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.
Lg 1 1 2
16
Ed04 Released

3BK 11204 0446 DSZZA
90/97
Type 20 Sequence Number ELEMENT IDENTIFIER (=20) LENGH (=2) SEQUENCE NUMBER
integer
- LSB - MSB
Lg 1 1 2
Type 21 Record Reason ELEMENT IDENTIFIER (=21) LENGH (=1) RECORD CRITERIA The possible values are the following: 0 1 4 : : : no partial records timed manuf. specific criteria
Lg 1 1 integer 1
Type 22 MS Classmark 3 ELEMENT IDENTIFIER (=22) LENGH (=20) MOBILE STATION CLASSMARK 3: 4 octets First octet: coded as described below (for more details, see TS GSM 04.08) 18: 8 0 7 X 6 X 5 X 4 X 3 X 2 X 1 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
Lg 1 1 4
18
This specification does not take DCS 1900 into account
Ed04 Released

3BK 11204 0446 DSZZA
91/97
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 X 7 X 6 X 5 X 4 X 3 X 2 X 1 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 X 7 X 6 X 5 X 4 X 3 X 2 X 1 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 X 7 X 6 X 5 X 4 X 3 X 2 X 1 X
Ed04 Released

3BK 11204 0446 DSZZA
92/97
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 String of 16 ASCII characters 1 char. (tenth of sec.) 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) 16
Ed04 Released

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

3BK 11204 0446 DSZZA
94/97
LSW LT MFP MS MSB MSC MSW OMC PGHR PM RIT RTCH RMS RTS SACCH SBL SCCP SCP SDCCH SMS SRH TCH TCU TEI TSC TTCH
Least Significant Word Local Terminal Multi-Frame Processor Mobile Station Most Significant Byte Mobile services Switching Center Most Significant Word Operation and Maintenance Center Performance Generic Header Record Performance Measurement Replaceable ITem Radio Traffic CHannel Radio Measurement Statistics Radio Time Slot Slow Associated Control CHannel Security BLock Signalling Control Connection Part Signalling and Control Processor Stand-alone Dedicated Control CHannel Short Message Service System Record Header Traffic CHannel Terminal Control Unit Terminal Endpoint Identifier Transcoder Submultiplexer Controller Terrestrial Traffic Channel
Ed04 Released

3BK 11204 0446 DSZZA
95/97
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 + LINKID 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). Ed04 Released

3BK 11204 0446 DSZZA
96/97
Ed04 Released
END OF DOCUMENT
3BK 11204 0446 DSZZA
97/97

B11 OMC-BSC File Specification

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B11 OMC-BSC File Specification

Uploaded by

Copyright:

Available Formats

All rights reserved.

Site VELIZY Originators

Mobile Access Division

OMC/BSC PM FILE FORMAT SPECIFICATION B11

ALCATEL GSM BSS SYS/SYS-TLA/SYS-OAM PRODUCT DEFINITION

Approvals Name App. E. Mermilliod Lucian-Florin MUNTEAN Zhu Haiyan

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

Removing all informations related to G1/G2/DRFU BTS.

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

3BKA20CBR286418: More incoming links per cell.

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

3.2.29 3.2.30 3.2.31 3.2.32 3.2.33 3.2.34 3.2.35 3.3 4

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

INTERNAL REFERENCED DOCUMENTS

[3] [4] [5] [6] [7] [9] [10]

For the B11 release the impacts on files format are:

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

GENERAL FILE FORMATS BSS files organisation and types

File Type Name GPMF HPMF OPMF PMDF TRCF ITRF

File Type Number 03 04 10 12 13 16

Table 1: BSS File Types

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

Record organisation and record types

Number of bytes in the header Record Sequence Number

2 bytes 2 bytes System Record Header (SRH)

Record Type Number File Type Number

(absent within transmission settings file)

max. 250 bytes Record content

Record Type Number 03 09 12 14 15 16 20

Reference 3.2 3.2 3.1 3.3 4.1 4.2 0

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

Files are constructed with the following Record Types:

Record 0 PGHR PGHR DPMR TRHR TRHR

Record 1 OPMR GPMR DPMR TRDR ITDR

Record 2 OPMR GPMR DPMR TRDR ITDR

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

Record N OPMR GPMR DPMR TRDR ITDR

File Type Names OPMF GPMF PMDF TRCF ITRF

BSS file names and numbers

BSS file names

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

BSS file numbers

PMRESccc 1 PMOBS-cc 2 PMDIR--TRACE-FR TRACE-FB

311 490 3 320 325 500 2010 2011

Files for Trace

OMC-BSS PM FILE FORMAT SPECIFICATION

3BK 11204 0446 DSZZA

PERFORMANCE MANAGEMENT FILE FORMATS Performance Generic Header Record description

Note: this is the same header for G2 BSC as for MX BSC