3BK 11204 0564 Dszza

ED 1 PROPOSAL 3 MFS/OMC PM file interface specification
B12 MFS-OMC PM FILE INTERFACE

E1P4

3BK 11204 0564 DSZZA 1/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

Site
Timisoara
GSM / WiMAX Business Division

Originators
Adrian STAN
MFS/OMC PM FILE INTERFACE SPECIFICATION
RELEASE B12

System : ALCATEL 900/BSS
Sub-system : MFS
Document Category : SYSTEM FUNCTIONAL BLOCKS (step 2)
ABSTRACT
This document defines the MFS/OMC-R performance-management (PM) file interface that will allow service
providers (SPs) deploying General Packet Radio Service (GPRS) wireless services to track the ongoing
performance of their Alcatel-Lucent network from end to end.

Approvals
Name
App.

(DPM/MFS)
Noemi KIRALY
(DPM/OSY)
Xavier LAMBERT

REVIEW
Edition 1 Proposal 1 2011-05-26 No remarks
Edition 1 Proposal 2 2011-06-29 No remarks
HISTORY
Edition 1 Proposal 1 2011-05-26
Creation of the first proposal from B11 document, ed4rl.
Update for B12 release
Remove legacy MFS references as no longer
supported in B12
Clarifications about GP alignment to hour boundary

Include impact of Counters for GCH traffic usage feature
o Introduction of new block type: B21cellPTUTDM


E1P4

3BK 11204 0564 DSZZA 2/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

3BKA20CBR293385 B11 NPO services description: SGSN
name configured in OMC filled in MFS PM block.
PM files examples in ANNEX A have been updated to
include MNC/MCC fields in B41CELLNACC block for both
current/previous GPU release
608128 Parameters added for Boosted GP
PM files examples in ANNEX A have been updated to
include GP_HW_Generation and GP_Location


E1P4

3BK 11204 0564 DSZZA 3/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

TABLE OF CONTENTS

TABLE OF CONTENTS.........................................................................................................3
INTERNAL REFERENCED DOCUMENTS .....................................................................................5
REFERENCED DOCUMENTS...................................................................................................5
RELATED DOCUMENTS .......................................................................................................5
PREFACE ........................................................................................................................5
OPEN POINTS / RESTRICTIONS..............................................................................................5
1 SCOPE........................................................................................................................6
2 BASIC PRINCIPLES .........................................................................................................8
2.1 Overview..............................................................................................................8
2.2 Transfer aspects................................................................................................... 10
2.3 Loader Transfer Directory ...................................................................................... 10
2.4 Security aspects ................................................................................................... 10
2.5 Granularity Period (GP).......................................................................................... 10
2.6 Report Period (RP)................................................................................................ 11
2.7 Counters Selection................................................................................................ 12
2.8 History............................................................................................................... 13
3 USE CASES ................................................................................................................ 14
4 FILE FORMAT............................................................................................................. 15
4.1 Files production................................................................................................... 15
4.1.1 MFS first installed in current release .................................................................. 15
4.1.2 MFS migrated from previous release to current release ............................................ 16
4.2 Files name .......................................................................................................... 16
4.3 General File format............................................................................................... 16
4.3.1 Header ....................................................................................................... 17
4.3.2 Guideline for blocks definition .......................................................................... 18
4.3.3 Blocks insertion & Logical configuration............................................................... 19
4.3.3.1 Transport Mode................................................................................... 19
4.3.3.2 PMU & PTU counters reliablity ................................................................ 20
4.3.3.3 LCS 20
4.3.3.4 Exaustive list of blocks.......................................................................... 20
4.3.3.5 Reporting order of blocks & Insertion condition ........................................... 21
4.4 Blocks definition .................................................................................................. 22
4.4.1 BSC BLOCKS ................................................................................................. 22
4.4.1.1 B30BSCCOM BLOCK .............................................................................. 22
4.4.1.2 B31BSCTDM BLOCK............................................................................... 23
4.4.2 BTS BLOCKS ................................................................................................. 25
4.4.2.1 B01BTSTDM........................................................................................ 25
4.4.2.2 B02BTSIP........................................................................................... 26
4.4.3 CELL BLOCKS................................................................................................ 27
4.4.3.1 B10cellPMUCOM BLOCK ......................................................................... 27
4.4.3.2 B11cellPMUTDM BLOCK ......................................................................... 29
4.4.3.3 B12cellPMUIP BLOCK ............................................................................ 30
4.4.3.4 B20cellPTUCOM BLOCK.......................................................................... 31


E1P4

3BK 11204 0564 DSZZA 4/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

4.4.3.5 B21cellPTUTDM BLOCK.......................................................................... 32
4.4.3.6 LcsCell BLOCK .................................................................................... 33
4.4.3.7 DistCell BLOCK ................................................................................... 34
4.4.3.8 B41CELLNACC..................................................................................... 37
4.4.4 EXTERNAL CELL BLOCK.................................................................................... 39
4.4.4.1 B40BSSADJEXT.................................................................................... 39
4.4.5 ABISBTSGROUP BLOCK..................................................................................... 40
4.4.6 Bearer channel BLOCK .................................................................................... 42
4.4.7 Pvc BLOCK................................................................................................... 43
4.4.8 LapD BLOCK................................................................................................. 44
4.4.9 SGSN_IP_NSVC BLOCK ..................................................................................... 45
4.4.10 SGSN BLOCK................................................................................................. 46
4.5 Specific behaviors and impact on Suspected Flag (SF) ................................................... 47
4.5.1 Create/Delete instance................................................................................... 47
4.5.2 LCS service activation/desactivation................................................................... 48
4.5.3 Administrative state....................................................................................... 48
4.5.4 Operational state .......................................................................................... 48
4.5.5 O&M Parameter change................................................................................... 48
4.5.6 GPU switchover / GPU reset ............................................................................. 49
4.5.7 OMCP (MFS EVOLUTION) switch over ................................................................... 49
4.5.8 BTS Provisioning Phase.................................................................................... 49
4.5.9 MFS start-up and re-start ................................................................................. 50
4.5.10 Reshuffling (cells distribution over GPUs) ............................................................. 51
4.5.11 Secured Single Gb.......................................................................................... 51
4.5.12 PTU counters and PMU counters......................................................................... 51
4.5.13 MFS software migration................................................................................... 52
4.5.14 IP transport activation/desactivation (GboIP) ........................................................ 52
4.5.15 IP transport activation/desactivation (BSSoIP) ....................................................... 52
4.5.16 Gb flex activation/desactivation........................................................................ 53
ANNEX A: MFS/OMC FILES EXAMPLE. ................................................................................... 54
4.6 Current release MFS / current release GPU: filename "GPMRES0800101" ........................... 54
4.7 Current release MFS / previous release GPU: filename "GPMRES0700101".......................... 77
GLOSSARY .................................................................................................................... 98


E1P4

3BK 11204 0564 DSZZA 5/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

INTERNAL REFERENCED DOCUMENTS
Not applicable
REFERENCED DOCUMENTS

[1] 3BK 11203 0252 DSZZA MFS counters catalogue
[2] 3BK 11203 0250 DSZZA BSS Telecom Parameter
[3] 3BK 11204 0572 DSZZA MFS/OMC interface: GDMO [part 2] - Implementation Profile
[4] 3BK 29376 NAAA DSZZA MFS Security and supervision enhancements Functional specification
[5] 3BK 11204 0569 DSZZA BSS O&M Parameters
RELATED DOCUMENTS
None
PREFACE
This document defines the MFS/OMC-R performance-management (PM) file interface that will
allow service providers (SPs) deploying General Packet Radio Service (GPRS) wireless services to
track the ongoing performance of their Alcatel network from end to end.
Definition of the interface includes file format, protocol and services.
The list of counters supported by the MFS is not part of the document. The counter given in the
ANNEX A are not guarantied, there are given as example (The reference document for the
counters is document [1]).

OPEN POINTS / RESTRICTIONS
None


E1P4

3BK 11204 0564 DSZZA 6/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

1 SCOPE
Terms:
Current release or N release terms refers to B12 release
Previous release or N-1 release terms refers to B11 release
The terminology BSC is for all platforms: BSC G2 and BSC EVOLUTION (stand alone and
rack shared architecture).
The terminology MFS is for MFS EVOLUTION/MX (stand alone and rack shared
architecture).
OMCP term refers to HW board hosting the MFS O&M function
The terminology GPU is for Global Processing Unit, also called GP in a MFS EVOLUTION
context.
The aim of this document is to provide the specification of the MFS/OMC-R performance-
management (PM) file interface that will allow service providers (SPs) deploying General
Packet Radio Service (GPRS) wireless services to track the ongoing performance of their
Alcatel network from end to end. Definition of the interface includes file format, protocol and
services.
The list of counters supported by the MFS is not part of the document. The counters given in
the ANNEX A are not guarantied, there are given as example (The reference document for the
counters is document [3]).
A current release MFS is able to handle current BSC release and previous BSC release. A
release (previous or current) can be made of several MR (Maintenance Release). A MFS
manage one and only one MR per release at a given time.
Thus, the OMCP is able to manage, at the same time, in the same rack:
previous release MRx GPs connected to a previous release MRx BSC
current release MRy GPs connected to a current release MRy BSC

This edition applies to all Main Releases of the current release.


E1P4

3BK 11204 0564 DSZZA 7/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

Up to 21+1 GPs (MX)
Up to 21+1 GPs (MX)
Control Station

GPU
rel
N-1
MFS release N-1
OMC release N
Control Station

GPU
rel
N-1
GPU
rel
N
MFS release N
BSC
rel
N-1
BSC
rel
N
BSC
rel
N-1


E1P4

3BK 11204 0564 DSZZA 8/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

2 BASIC PRINCIPLES
2.1 Overview
The MFS implements a permanent X.738 Buffered Scanner that realizes the functions of
collection per Monitored object of historical PM data, according to a collection schedule; and of
PM data reporting to the OMC-R according to a reporting schedule.
The Buffered scanner permits to collect per Monitored object a set of historical PM data
collected at the end of each Granularity period (GP).
At the end of the Report period (RP), the Buffered scanner scans all Historical data created at
the end of each Granularity period, produces a Result file.

Historical Data
from GP1
Historical Data
from GP2
Historical Data from
GP3
Historical Data
from GP4
History Data for RP1 (GP1+GP2) History Data for RP1 (GP3+GP4)
GP1 GP2 GP3 GP4
Example with RP value = 2 * GP value
File File

At MFS, the Granularity period (GP) is equal to the Report period (RP).
There is one Result file per BSS release. As the MFS handles two releases of BSS, there are
two result files (one per GPU release) produced by the MFS: one for previous release GPUs,
one for current release GPUs (whatever is the MR)


E1P4

3BK 11204 0564 DSZZA 9/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

The following figure illustrates the PM data collection process:

Parser
Loader
Loader
transfer
directory
Loader
transfer
directory
OMC-R
MFS
Data Transfer
NPR input format
Parsed Data
Counters collector
Collection
GPU
GPU
GPU

1 file per GPU release
Control Station
MUSE
Counters
from
BSC

The parser is responsible for the formatting network performance data into a NPO format. It is
implemented in the MFS network element. The NPO input format consists in a CSV/tabular
structure.
Data transfer: see [2.2]
The loader is a configurable subsystem that maps the output of the parser onto the data model.
The parser only performs syntactic transformations, so it must carry out any semantic
transformations required in the data, such as mapping the performance counters onto columns
defined in the data model
Inputs for OBSAL (OMC-R component ) are the PM files coming from BSC and MFS and the outputs
are alerters, OBSYNT and CSV files for MUSE.


E1P4

3BK 11204 0564 DSZZA 10/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

2.2 Transfer aspects
The OMC-R will monitor the MFS loader transfer directory in order to attempt to load any files
its encounters in that directory directly via ftp to transfer the result files. Transfer is based on a
polling period at OMC-R.
The selection of the GPMRES files to transfer from the MFS by the OMC-R is based on the
files UNIX timestamp (last modification, date/time) at MFS. In consequence, the timezone of
the MFS must be initialized.
2.3 Loader Transfer Directory
A Transfer Directory is defined at the MFS. It is defined at the OMC-R/MFS interface on the
aGprsManagedElementExtension managed object class by the attribute aGprsSpoolDirectory
attribute (See ref [5]). This directory is used for many domains (PM result files, radio
reconfiguration file). For PM, the complete path is the following:
{aGprsSpoolDirectory}\gpmres

2.4 Security aspects
The access to the directory omcxchg is limited to some users. At MFS installation, the user
omcxchg [omcxchange] is defined by default.
More details in ref [4]

2.5 Granularity Period (GP)
GP value is defined in the GPMGP file at OMCP. The GP value is taken into account by the MFS
only at a global restart (OMCPs and all GPU boards): First GPM starts up and reads the RP value.
Then, the GP value is sent to GPU at board initialization.
GPmin is the time in which GPM real time agent is able to collect all the performance
measurement reports for every instances from every GPU boards, in order to provide the
complete MFS results files (one per release) for a given Reporting Period. This global collect
must be finished before to start the next one.
Mandatory rules for these parameters are:
- The maximum value of GP is 60 minutes
- The minimum value of GPmin is 2 minutes


E1P4

3BK 11204 0564 DSZZA 11/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

- GP > GPmin (if not, there is a fatal error at GPM SCIM start up)
- GP is a divisor of 60 minutes. In consequence, theorically, the possible values are 3, 4,
5, 6, 10, 12, 15, 20, 30 and 60. Unit is minutes.
- The Granularity Period (GP) is aligned to the hour boundary (ie from HH:00 to
HH+GP:00), so all the measurements are comparable to the other systems.
From a product point of view:
GP is constant, whatever is the release of the MFS. GP=60 minutes. See GPRS BSS
Technical Feature List document, 3BK102040458DTZZA. In fact this value is the duration
in which an OMC-R is able to collect all the reports from all network elements in a large
network.
(*)(**) GPmin is constant for a given MFS release. This value is the duration in which a
MFS is able to collect all the reports from all the Telecom boards. GPmin=3 minutes for
MFS (MX).
(*) Regarding MX platform, Load tests shows that all reports for 21 GP (stand alone
configuration) have been collected in less than 1mn10sec. To secure the timer value, a margin
of at least 30% is applied.
(**) With MxBSC capacity improvements, the cells capacity of a MFS EVOLUTION increases from
3000 to 4000.
2.6 Report Period (RP)
PM data reporting refers to the ability for the MFS to report PM data on a scheduled basis to the
OMC-R.
The frequency of the report (RP) is defined slow, the usage will be only for a statistical usage of
the PM data (post processing of the results in NPO). This is in opposition to fast, when the usage
is for monitoring.
At MFS, the RP is defined equal to GP. So that, a file that contains history data is reported on
each GP expiry. To secure the integrity of the files (an OMCP swith-over with a file opened is a
critical case), the reporting files are closed at GP expiry + GPMin. So, the history data related to
GPi are available, in the Transfer Directory, at GPi expiry + GPmin


E1P4

3BK 11204 0564 DSZZA 12/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

Control Station
<-- GP 1 --><-- GP 2 --><-- GP 3 -->
GPU board
<-- GP 1 --><-- GP 2 --><-- GP 3 -->
<-> GP min <-> GP min
Transfer
Directory
RP1 files
are ready
RP2 files
are ready

OMC-R
RP 1 files
are
available
RP 2 files
are
available

2.7 Counters Selection
The GPU telecom boards master the counters. The OMCP simply gets them through PM messages
from GPU boards and place them with a specific format into PM file reports to be transferred to
a PM server.
At OMCP, all the counters are defined in the gpmcounterid.txt file, located in the /usr/mfs/etc
directory at the OMCP, and are reported to the OMC-R. It is possible to filter some counters by
removing them from this file, and thus they will be not put inside the file report.
This is a flat file that gives the set of counters identifiers, with their associated counters name,
associated class, and configuration data identifiers with their associated logical name,
associated class. It does not give the relationship between the counters and the release in which
they are implemented by the telecom. So, if a counter is removed from this file, it will be never
reported into the PM file report, neither if it comes from a previous release GPU, nor from a
current release GPU. This file is given in APPENDIX B.
It is possible to reduce this set of counters by removing counters in this file. This will unselect
counters to be filled in the result files. So, a counter coming from GPU board, not present in this
file, will not be inserted it the PM result file.
The gpmcounterid.txt file is read by the MFS (GPM) at an OMCP (re) start. If it is modified, an
OMCP switch-over (or restart) is required to take into account the new one.


E1P4

3BK 11204 0564 DSZZA 13/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

This facility can be used by development and integration. MFS team delivers the reference file.

2.8 History
The MFS keeps, at least, the GPUs results files that correspond to the last 3 days (72 hours).
This requirement is directly taken, into account in the filename in which a suffix is added. To
limit the number of result files stored in the transfer directory, the following rule to compute
the index has been defined:
mm = [ 00 INT( (History Period / Granularity Period) )+ 1 ]


E1P4

3BK 11204 0564 DSZZA 14/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

3 USE CASES

The following use case illustrates the OMC-R PM data collection process.
Mechanism is mainly based on timers expiration, dimensioned with a maximum value
(independent of the number of GPUs, logical configuration, platform).

ftp
MFS GPM MFS exchange GPU1 GPU2 OMC
[1]
[2]
[4] [3]
[5]
[6]
[7]

[1] At MFS start up, the permanent scanner is created in all GPU. It starts at next GP
(GP=60mn).
[2] When a (GP) period starts, Current data are updated by GPU SW.
[3] When GP expired, the GPU SW swaps the two buffers (current/history):
Current data becomes the history data (values are frozen)
History data are reset, and becomes the current data.
And starts the next (GP) period. Current data are updated by GPU SW
[4] When GP expired, GPM (Global Performance Manager) at OMCP


E1P4

3BK 11204 0564 DSZZA 15/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

Asks for all the history data from the GPU boards
Starts (Gpmin) timer
Starts the next (GP) period
[5] GPM (Global Performance Manager) at OMCP receives history data (ReportCnf from GPUs
on a class basis, with link reply) from the GPU boards and produces result files (parser
function), in respect to standard format.
[6] when GPmin expired, GPM closes the report files and move them into the MFS exchange
directory. Thus, the result files are placed in the loader transfer directory at the MFS.
[7] At OMC-R, a periodic timer (10 mn) polls the exchange directory to get the report files of the
MFS. The new (based on the file timestamp) report files are collected.
4 FILE FORMAT
The file format is a proprietary format. It consists in a sequence of report blocks, enclosed in
braces. Two levels of block are defined. A block contains:
Other blocks (the block is a container). This block contains all informations related to a
full Granularity Period. This block contains a set of blocks. The content depends on the
logical configuration (size not fixed).
Measurements of one instance of one class (Identifier/value pairs that associate a
value with a field name). The content depends on the list of defined counters (size not
fixed).
Line starting with the '#' character are interpreted as comments.
New line characters are not recognized as significant by the loader.
Files are compressed. This will be done by using gzip 1.2.4 (18 Aug 93)
The file type is ASCII.
4.1 Files production
As GPU boards report the counters to the OMCP: previous release GPU is reporting previous
release counters results, and the current release GPU is reporting current release counters
results to the OMCP.
4.1.1 MFS first installed in current release
One BSS version is known at MFS: the current one. In this case, the MFS provides one file only,
containing data from current release GPUs with current release counters only.


E1P4

3BK 11204 0564 DSZZA 16/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

4.1.2 MFS migrated from previous release to current release
The current release MFS provides two files: one containing data from previous release GPUs with
previous release counters only and one with data from current release GPUs with current release
counters only.
4.2 Files name
This following table gives the rules to name the PM results files:

FILE NAME Type Comments
NAME PART Char (12) GPMRES<RR><yyy><mm>
with:
RR: ITFVERSION value always coded on 2 digits
(see4.3.1)
yyy: identification of the MFS, configured in the
ServerFile file (handled by Q3 agent). Always coded
on 3 digits.
mm: index of the result file (
see 1
). Always coded on
2 digits. For a given GP, the index of the two files
(previous/current release) is identical.
(1)
1
To limit the number of result files stored in the transfer directory, a following rule to compute the
index has been defined:
mm = [ 00 INT( (History Period / Granularity Period) )+ 1 ]

4.3 General File format
Measurement Items (counters) are typically grouped according functionality. The term
"measured object class" is used to identify such a group. The file format is based on the fact that
the measurements are always collected in sets of one functional group.
A PM file contains the sequence of measurements, values and related information, in a block-
oriented structure.
It includes a list of measurement types and the corresponding values, together with the date and
the time stamp related to the reporting period, the MFS identifier, and the interface identifier.
The following figure gives the general file format:


E1P4

3BK 11204 0564 DSZZA 17/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

The fixed part is exactly the same whatever is the PM interface version.
The variable part is the list of the possible blocks. The presence of a block is not
mandatory, it depends on the configuration.

#%npr MFS
#
{
{
MFS <MFS identifier>
VERSION <MFS version>
ITFVERSION <ITF version>
ScannerIdentity <scanner id>
STARTTIME <HH:MM:SS>
ENDTIME <HH:MM:SS>
DATE <YYYY-MM-DD>
insert here the PVC block (s) * * *
insert here the BearerChannel block (s) * * *
insert here the LAPD block (s) * * *
insert here the SGSN_IP_NSVC block (s) * * *
insert here the B30BSCCOM block (s) * * *
insert here the B31BSCTDM block (s) * * *
insert here the SGSN block (s) * * *
insert here the B01BTSTDM block (s) * * *
insert here the B02BTSIP block (s) * * *
insert here the ABISBTSGROUP block (s) * * *
insert here the B10cellPMUCOM block (s) * * *
insert here the B11cellPMUTDM block (s) * * *
insert here the B12cellPMUIP block (s) * * *
insert here the B20cellPTUCOM block (s) * * *
insert here the B21cellPTUTDM block (s) * * *
insert here the LcsCell block (s) * * *
insert here the B40BSSADJEXT block (s) * * *
insert here the B41CELLNACC block (s) * * *
insert here the DistCell block (s) * * *
}
}
maximum 60 columns
fixed part
variable part
fixed part

4.3.1 Header
MFS identifier: value configured in the nServerFile file (handled by Q3 agent).
VERSION: Software sub version of the MFS network element (see the document [3] for the
version naming rule). It includes the generation of the MFS (i.e. MFS EVOLUTION only) and the
software version of MFS (i.e. previous release or current release). Version name starts with
MFSY for MFS EVOLUTION
Note that the MFS SW VERSION is the one of the current release whatever the release of the
GPU (previous/current release).


E1P4

3BK 11204 0564 DSZZA 18/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

ITFVERSION: identifies the O&M/ Telecom interface version (maximum of 2 digits), ie the
GPU release (previous or current release)

interface type (MFS) VERSION ITFVERSION
Current release MFS current release
GPU (current release all MR BSC)
8 (current
release GPU)
Current release MFS previous
release GPU (previous release all MR
BSC)
AL01.01A
Previous release MFS previous
release GPU (previous release all MR
BSC)
AZ01.01A
7 (previous
release GPU)

ScannerIdentity: Identity of the scanner. The permanent scanner identifier is '1'.
STARTTIME and the ENDTIME are respectively the start and the stop collection times of the
granularity period related to the measurements included in the block. Time stamps are given
in UTC time (Coordinated Universal Time).
DATE is the start date of the granularity period related to the measurements included in the
block.
Note:
A result block is inserted in the result file only if the block is retrieved from the GPU board.
Counters and reporting class are defined into document [3]. Thus, Blocks and counters are
defined based on these informations.
4.3.2 Guideline for blocks definition
Here are given the list of the mandatory rules for defining a block:
MFS insures that eack block name starts with 3 discriminating characters
A parameter is fully defined with a parameter name and a parameter value:
1. A parameter name field is defined on maximum 50 chars (e.g.
PD_DL_PDCH_UNIT_ALLOC_THR_9) in upper case. It is identical to the HMI Name
defined at BTP. But, the limit becomes 27 for parameter on which no indicator is
mapped explicitly in indicators dictionary. This information, when relevant, is specified
in internal comments field at BTP.
2. A parameter value is always reported as an integer type. The length of the parameter
value is parameter value dependent.
A counter is fully defined with a counter name and a counter value:


E1P4

3BK 11204 0564 DSZZA 19/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

1. A counter name field is defined on maximum 10 chars (e.g. "P13 " for the
Number of UL TBF establishment - successes.)
2. A counter value is always reported as an integer type. The length of the
counter value is counter value dependent. The maximum number of bytes is given in the
related document [3]. For instance, when a counter is defined with a length of 4 bytes,
the value provided in the PM result file can be from "0" to " 4294967295 " (numeric
format).
The carriage return is used as delimiter between two successive parameters or counters. It is
inserted just after the last number of the value.
If some counters are suspect for a given granularity period, the suspected flag (SF) will be
set at the block level.
The counter list in a block depends on the GPU software Main Release
The configuration data in a block depends on GPU software Main Release.
It is not possible to define more than one block for one object/granularity period (e.g. For
non-concentric cell specific counters will be present in the cell block with the value 0)
A counter is defined on only one object (see ref [1]). In consequence, a counter cant be
present in two different blocks.
4.3.3 Blocks insertion & Logical configuration
From an interface point of view, the interface data model provides additional objects for
additional services. For instance, a block is defined for GPRS/EDGE counters and another is
defined for LCS counters.
The insertion (or not) of a block into the GPMRES export file depends on the logical
configuration.
4.3.3.1 Transport Mode
Due to the different transport modes, in order to:
- Not to use space storage on MUSE side
- Allow proper spatial aggregation for indicators only valid in a certain technology
- Allow proper management of the reliability
It is decided to build dedicated blocks. For a certain category of counters, we can define three
blocks:
The set of counters valid whatever the technology (the common ones). The third digit
of the blockname is always 0.
The set of counters valid only in TDM mode. The third digit of the block name is always
1.


E1P4

3BK 11204 0564 DSZZA 20/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

The set of counters valid only in IP mode. The third digit of the block name is always 2.
4.3.3.2 PMU & PTU counters reliablity
Moreover, with BSSoIP introduction, when the Abis transport mode is IP, the PTU SW is at BTS.
But PTU counters are still collected by the PMU, in order to keep the same interface with NPO,
whatever is the BTS mode. For reliability reason, counters related to these services
(GPRS/EDGE) are reported into two different blocks: one (cellPMU) is for counters defined at
PMU, another (cellPTU) is for counters defined at PTU.
4.3.3.3 LCS
Location is introduced in B8, and was considered as a new service on top of GPRS/EDGE that is
activated/desactivated via the O&M parameter EN_LCS defined at BSC level. All counters related
to this service are reported into the lcsCell block, defined in 4.4.3.5
4.3.3.4 Exaustive list of blocks
The resulting list of blocks is as follows:
Dependency on Gb transport mode:
Always valid Frame Relay mode IP mode
(static and dynamic configuration type)
-- --
--
-- BearerChannel --
-- pvc --
-- --
SGSN_IP_NSVC
-- --
SGSN (Gb flex enabled)
Dependency on BSS transport mode:
Always valid TDM mode IP mode
-- LapD
--
B30BSCCOM B31BSCTDM
--
Dependency on ABIS transport mode:
Always valid TDM mode IP mode
-- B01BTSTDM
B02BTSIP
B10cellPMUCOM B11cellPMUTDM
B12cellPMUIP
B20cellPTUCOM B21cellPTUTDM
--
LcsCell --
--
DistCell --
--
-- --
ABISBTSGROUP
B40BSSADJEXT --
--


E1P4

3BK 11204 0564 DSZZA 21/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

B41CELLNACC --
--

4.3.3.5 Reporting order of blocks & Insertion condition
There is one GPMRES file per Release.
The reporting of a block depends on the creation of the instance in the GPU. If an instance is not
created at GPU, no block is reported for the instance. If an instance is created at GPU, some
blocks are mandatory; the others are optional (see 4.3.3.4)
The MFS collects all blocks from all GPU in parallel, and inserts them in the order they are
reported by the GPU. By this way, the MFS may interleave blocks from different GPUs.
There is no strict order regarding the order in which the domain reports their blocks. By this
way, the MFS may interleave Gb blocks and Radio blocks.
There is a strict order regarding the order in which blocks related to one domain request are
reported. The first and last blocks of the radio domain are always mandatory.
For a given GPU, a strict order is defined for blocks related to CELL object. The last block is
always present whatever are the configured services. Note that LCS blocks are inserted if LCS
service is configured only, then it cannot be the last one.
Blocks related to Radio domain are inserted in the following order by the MFS

Block Name Presence Condition
B30BSCCOM
Always present (first block of the radio domain)
[B31BSCTDM]
Present if GSL transport mode is TDM
[B01BTSTDM]
Present if ABIS transport mode is TDM
[B02BTSIP]
Present if ABIS transport mode is IP
[ABISBTSGROUP]
B10cellPMUCOM
Always present
[B11cellPMUTDM]
[B12cellPMUIP]
B20cellPTUCOM
Always present
[B21cellPTUTDM]


E1P4

3BK 11204 0564 DSZZA 22/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

[LcsCell]
Present if LCS service is activated
[B40BSSADJEXT]
Present if RIM_NACC is activated and if external cells have
been created for the BSC at MFS
[B41CELLNACC]
Present if RIM_NACC feature is activated
DistCell
Always present (last block of the radio domain)

Blocks related to Gb domain are inserted in the following order by the MFS

Block Name Presence Condition
[SGSN_IP_NSVC]
Present if Gb transport mode is IP, whatever is the
configuration type (Static or dynamic)
[SGSN]
Present if Gb flex feature is activated. Note that Gb flex
feature can be activated if Gb transport mode is IP only.
4.4 Blocks definition
In the following chapters, the different blocks are defined. When a block is not relevant for one
GPU release only (current or previous), this is explicitly indicated.
4.4.1 BSC BLOCKS
The scope of a BSC block is the GPU board. In multi-GPU by BSC, the BSC block is related to a
sub-BSS (identify by BSS+Fabric identifier). There is one sub-BSS by GPU.
Note that the Fabric Identifier is the logical name of the GPU, which is not impacted by the GPU
switch over.
4.4.1.1 B30BSCCOM BLOCK
B30BSCCOM block reports the set of counters. In multi-GPU by BSC, the BSC block is related to a
sub-BSS (identified by BSS+Fabric identifier). There is one sub-BSS by GPU. The block is valid
whatever the BSS transport mode (IP or TDM).


E1P4

3BK 11204 0564 DSZZA 23/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

B30BSCCOM {
BSS <Bss Function Identifier>
FABRIC <Fabric identifier>
<configuration data name> <value>
. . . . . .
GCSF <0/1>
SF <0/1>
<counter name> <value>
. . . . . .
}

Bss Function Identifier: "<ID>"
<Fabric Identifier>
The FABRIC id is the identifier of the Logical GPU. This identifier is a fixed identifier which is
independant of the localisation of the supporting GPU board, which can move following
reconfigurations (ie GPU switch over). Thus, PM results are related to the logical GPU
identifier.
MFS EVOLUTION: is the decimal value of the concatenation of 4 bytes (8 bits each
[0..255]): the rack number(1), the subrack number(3..4) and the GP position
([1..5,10..14] for shelf 3, [1..6,9..14] for shelf 4 ) and a padding. For instance, for the
Fabric: rack 1, sub-rack 3, GP 2, the fabric identifier will be 01030200 Hex or
"16974336 Decimal
Configuration data are:
- None
GPU Configuration Suspected Flag (GCSF) <0/1>: This flag (NO:0, YES:1) indicates that a cell
has been created or removed on the GPU during the Granularity Period.
Suspected Flag: "<SF>". See chapter 4.5
GP_HW_GENERATION
GP_HW_GENERATION indicates the type of the GP board and can take the following values:
JBXGP2 or JBXGPU which refers to old GP board also called GP2
JBXGP3 which refers to Boosted GP also called GP3
GP_LOCATION
GP_LOCATION indicates the physical GPU. The value has the following format: RACK X /
SUBRACK Y / SLOT Z.


E1P4

3BK 11204 0564 DSZZA 24/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

4.4.1.2 B31BSCTDM BLOCK
B31BSCTDM block reports the set of counters. In multi-GPU by BSC, the BSC block is related to a
sub-BSS (identified by BSS+Fabric identifier). There is one sub-BSS by GPU. The block is provided
if the BSS transport mode is TDM only.

B31BSCTDM {
. . . . . .
SF <0/1>
. . . . . .
}

<Fabric Identifier>
identifier.
"16974336 Decimal
No configuration data. This part is empty
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.


E1P4

3BK 11204 0564 DSZZA 25/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

4.4.2 BTS BLOCKS
4.4.2.1 B01BTSTDM
B01BTSTDM reports the set of counters, defined on a BTS basis, valid when the ABIS transport
mode is TDM.
Note that a B01BTSTDM block is reported if at least one cell configured with PS is mapped onto
this BTS.

B 0 1 B T S T D M {
B S S < B s s F u n c t i o n I d e n t i f i e r >
F A B R I C < F a b r i c i d e n t i f i e r >
B T S < B T S I d e n t i f i e r >
< c o n f i g u r a t i o n d a t a n a m e > < v a l u e >
. . . . . .
S F < 0 / 1 >
< c o u n t e r n a m e > < v a l u e >
. . . . . .
}

with:
<Fabric Identifier>
identifier.
"16974336 Decimal
BTS Identifier: "<ID>" is the identifier of BTS carrying the packet. It is the BTS index at BSC
side.
- NB_EXTRA_ABIS_TS: the number of extra Abis TSs available in the BTS.
Note:
Cell shared having PS on primary sector is not shown as shared at OMC/MFS interface.
The value is either N_EXTRA_ABIS_TS_MAIN (number of Extra TS configured on the main
sector of a cell) or N_EXTRA_ABIS_TS_SECONDARY (the number of Extra TS configured
on the secondary sector of a cell in case of cell shared).


E1P4

3BK 11204 0564 DSZZA 26/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

As the two parameters are given by the OMC-R to the MFS on a cell basis, the MFS reads
the parameters from the first cell of the BTS only and applies the following rule:
If N_EXTRA_ABIS_TS_SECONDARY <> 0 (cell shared)
then
NB_EXTRA_ABIS_TS = N_EXTRA_ABIS_TS_SECONDARY
else
NB_EXTRA_ABIS_TS = N_EXTRA_ABIS_TS_MAIN
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.2.2 B02BTSIP
* * * For current release GPU only (introduced with SW release supporting BSSoIP) * * *
B02BTSIP reports the set of counters, defined on a BTS basis, valid when the ABIS transport
mode is IP.
Note that a B02BTSIP block is reported if at least one cell configured with PS is mapped onto this
BTS.

B 0 2 B T S I P {
B S S < B s s F u n c t i o n I d e n t i f i e r >
F A B R I C < F a b r i c i d e n t i f i e r >
B T S < B T S I d e n t i f i e r >
. . . . . .
S F < 0 / 1 >
. . . . . .
}

with:
<Fabric Identifier>


E1P4

3BK 11204 0564 DSZZA 27/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

identifier.
"16974336 Decimal
BTS Identifier: "<ID>" is the identifier of BTS carrying the packet. It is the BTS index at BSC
side.
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.
4.4.3 CELL BLOCKS
Globally, from an O&M point of view, a cell created at MFS is necessarly GPRS/EDGE capable. In
this chapter are defined the blocks related to BSC own cells.
4.4.3.1 B10cellPMUCOM BLOCK
B10CellPMUCOM reports the set of counters, defined on a cell basis, valid whatever the ABIS
transport mode (IP or TDM).


E1P4

3BK 11204 0564 DSZZA 28/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

B10cellPMUCOM{
LAC <lac value>
CI <ci value>
BTS <BTS Identifier>
. . . . . .
CSSF <0/1>
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>
identifier.
"16974336 Decimal
<lac value> is the Location Area Code value of the cell
<ci value> is the cell identity value of the cell
<BTS Identifier> is the identifier of BTS carrying the packet. It is the BTS index at BSC side..
- BS_PBCCH_BLKS (defined in ref [2])
- BS_PRACH_BLKS (defined in ref [2])
- MAX_PDCH (defined in ref [2])
- MIN_PDCH (defined in ref [2])

- BSS_TRANSPORT_MODE (defined in ref [2])
- ABIS_TRANSPORT_MODE (defined in ref [5])
Cell Shared Suspected Flag (CSSF) <0/1>: This flag (NO:0, YES:1) indicates that the PS sector
of a cell shared has changed of BTS during the Granularity Period.


E1P4

3BK 11204 0564 DSZZA 29/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.
4.4.3.2 B11cellPMUTDM BLOCK
B11CellPMUTDM reports the set of counters, defined on a cell basis, valid when the ABIS
transport mode is TDM.

B11cellPMUTDM{
LAC <lac value>
CI <ci value>
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>
identifier.
"16974336 Decimal


E1P4

3BK 11204 0564 DSZZA 30/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

<BTS Identifier> is the identifier of BTS carrying the packet. It is the BTS index at BSC side.
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.3.3 B12cellPMUIP BLOCK
B12CellPMUIP reports the set of counters, defined on a cell basis, valid when the ABIS
transport mode is IP.

B12cellPMUIP{
LAC <lac value>
CI <ci value>
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>
identifier.


E1P4

3BK 11204 0564 DSZZA 31/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

Fabric: rack 1, sub-rack 3, GP 2, the fabric identifier will be "16974336"
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.3.4 B20cellPTUCOM BLOCK
B20CellPTUCOM reports the set of counters, defined on a cell basis, valid whatever the ABIS
transport mode (IP or TDM).

B20cellPTUCOM{
LAC <lac value>
CI <ci value>
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>


E1P4

3BK 11204 0564 DSZZA 32/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

identifier.
"16974336 Decimal
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.3.5 B21cellPTUTDM BLOCK
B21CellPTUTDM reports the set of counters, defined on a cell basis, valid when the ABIS transport mode is
TDM.

B21cellPTUTDM{
LAC <lac value>
CI <ci value>
SF <0/1>
. . . . . .
}

with:


E1P4

3BK 11204 0564 DSZZA 33/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

<Fabric Identifier>
identifier.
"16974336 Decimal
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.3.6 LcsCell BLOCK
LcsCell reports the set of counters, defined on a cell basis, valid when the LCS feature is activated.
LcsCell{
LAC <lac value>
CI <ci value>
SF <0/1>
. . . . . .
}


E1P4

3BK 11204 0564 DSZZA 34/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

with:
<Fabric Identifier>
identifier.
"16974336 Decimal
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.3.7 DistCell BLOCK

DistCell{
CI <ci value>
LAC <lac value>
. . . . . .
DSF <0/1>
SF <0/1>
. . . . . .
}

with:


E1P4

3BK 11204 0564 DSZZA 35/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

<Fabric Identifier>
identifier.
"16974336 Decimal
-
- PD_UL_TBF_DURATION_THR_1

- PD_DL_TBF_DURATION_THR_1

- PD_UL_TBF_VOLUME_THR_1

- PD_DL_TBF_VOLUME_THR_1


E1P4

3BK 11204 0564 DSZZA 36/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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


- PD_UL_PDCH_UNIT_ALLOC_THR_1

- PD_DL_PDCH_UNIT_ALLOC_THR_1

- EGPRS_LLC_THROUGHPUT_THR_1

- GPRS_LLC_THROUGHPUT_THR_1
Distribution Suspected Flag <DSF>. This flag (NO:0, YES:1) indicates whether or not at least
one of the packet distribution thresholds has been modified during the Granularity Period


E1P4

3BK 11204 0564 DSZZA 37/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

(e.g. further to an O&M change). Note that the packet distribution thresholds are defined at
BSC level. Chapter does not apply to this suspected flag.
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.

4.4.3.8 B41CELLNACC
B41CELLNACC reports the set of counters related to a cell.
In multi-GPU context, the block is related to one sub-BSS (identified by BSS+Fabric identifier).
The block may be reported when the feature is activated only (EN_RIM_NACC = 1)
The block is not reported if all counters are null (ie value equals to 0)
* * * 3BKA20CBR241660 BEGIN * * *
Note that Suspected Flag (SF) is not managed because counters must be provided even for
uncomplete Granularity period. By consequence, when it is reported, the block is always
relevant ie SF is always set to 0 value.


E1P4

3BK 11204 0564 DSZZA 38/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

The block is defined as follows:

B41CELLNACC {
FABRIC < FABRIC value>
BSS <BSC id value>
LAC <LAC value>
CI <CI value>
MNC <MNC value>
MCC <MCC value>
. . . . . .
SF <0>
. . . . . .
}

with:
<FABRIC Identifier>
identifier.
"16974336 Decimal
<BSS identifier> identifier of the BSS
<LAC value> identifier of the Location Area Code of a cell of the own BSC
<CI value> identifier of the Cell Identity of a cell of the own BSC
<MNC value> identifier of the Mobile Network Code of a cell of the own BSC
<MCC value> identifier of the Mobile Conutry Code of a cell of the own BSC
No configuration data. This part is empty.
Suspected Flag: "<SF>". Always 0.
GP_HW_GENERATION


E1P4

3BK 11204 0564 DSZZA 39/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

GP_LOCATION
SUBRACK Y / SLOT Z.
* * * 3BKA20CBR241660 END * * *
4.4.4 EXTERNAL CELL BLOCK
Globally, from an O&M point of view, a cell created at MFS is necessarly GPRS/EDGE capable. In
this chapter are defined the blocks related to BSC external cells.
4.4.4.1 B40BSSADJEXT
B40BSSADJEXT reports the set of counters related to a BSC external cell.
In multi-GPU context, the block is related to one sub-BSS (identified by BSS+Fabric identifier).
The block may be reported when the RIM NACC feature is activated only (EN_RIM_NACC = 1)
The block is not reported if all counters are null (ie value equals to 0)
Note that Suspected Flag (SF) is present but not managed because counters must be provided
even for uncomplete Granularity period. By consequence, when it is reported, the block is
always relevant ie the SF is always set to 0 value.

The block is defined as follows:

B40BSSADJEXT {
FABRIC < FABRIC value>
BSS <BSC id value>
LAC <LAC value>
CI <CI value>
MNC <MNC value>
MCC <MCC value>
. . . . . .
SF <0>
. . . . . .
}

with:
<FABRIC Identifier>


E1P4

3BK 11204 0564 DSZZA 40/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

identifier.
"16974336 Decimal
<BSS identifier> identifier of the BSS
<LAC value> identifier of the Location Area Code of a external cell to the BSC
<CI value> identifier of the Cell Identity of a external cell to the BSC
<MNC value> identifier of the Mobile Network Code of a external cell to the BSC
<MCC value> identifier of the Mobile Country Code of a external cell to the BSC
Suspected Flag: "<SF>". Always 0.
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.
4.4.5 ABISBTSGROUP BLOCK
This block is relevant when ABIS transport Mode is IP only.


E1P4

3BK 11204 0564 DSZZA 41/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

ABISBTSGROUP {
FABRIC <Fabric Identifier>
BSS <BSS Identifier>
ABISGROUPNUMBER <ABISGROUP Identifier>
. . . . . .
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>
identifier.
"16974336 Decimal
* * * 3BKA20CBR232802 BEGIN * * *
ABISGROUPNUMBER: "<ID>": value of the ABIS GROUP identifier
* * * 3BKA20CBR232802 END * * *
no configuration data. This part is empty.
GP_HW_GENERATION
GP_LOCATION


E1P4

3BK 11204 0564 DSZZA 42/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

SUBRACK Y / SLOT Z.

4.4.6 Bearer channel BLOCK
This block is relevant in Frame Relay (FR) transport Mode only.
BearerChannel {
TP <TTP Identifier>
Bearer <bearer channel Identifier>
. . . . . .
SF <0/1>
. . . . . .
}

with:
<TTP Identifier>
The TTP id is the identifier of the Logical port. This identifier is a fixed identifier which is
independant of the localisation of the supporting GPU board, which can move following reconfigurations
(ie GPU switch over). Thus, PM results are related to the logical port identifier.
([1..5,10..14] for shelf 3, [1..6,9..14] for shelf 4 ) and a port number [0..15]. For
instance, for the Fabric: rack 1, sub-rack 3, GP 2, TP 6 the fabric identifier will be
01030206 Hex or "16974342 Decimal"
Bearer Identifier: "<ID>": value of the highest timeslot of the Bearer Channel
GP_HW_GENERATION
GP_LOCATION


E1P4

3BK 11204 0564 DSZZA 43/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

SUBRACK Y / SLOT Z.
4.4.7 Pvc BLOCK
This block is relevant in Frame Relay (FR) transport Mode only.
pvc {
TP <TTP Identifier>
Bearer <bearer channel Identifier>
PVC <PVC Identifier>
. . . . . .
SF <0/1>
. . . . . .
}

with:
<TTP Identifier>
reconfigurations (ie GPU switch over). Thus, PM results are related to the logical port
identifier.
01030206 Hex or "16974342 Decimal"
bearer channel Identifier: "<ID>": value of the highest timeslot of the Bearer Channel
PVC Identifier: "<DLCI>": Data Link Connection Id; this is either a Frame Relay network
parameter (case Gb interface through Frame Relay), or a parameter shared with the SGSN
(case direct connection). Range: 16-991
GP_HW_GENERATION


E1P4

3BK 11204 0564 DSZZA 44/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

GP_LOCATION
SUBRACK Y / SLOT Z.
4.4.8 LapD BLOCK
This block is relevant when BSS transport Mode is TDM only.
LapD {
TP <TTP Identifier>
GSL <GSL Identifier>
. . . . . .
SF <0/1>
. . . . . .
}

with:
<TTP Identifier>
reconfigurations (ie GPU switch over). Thus, PM results are related to the logical port
identifier.
01030206 Hex or "16974342 Decimal"
GSL identifier: "tei"
GP_HW_GENERATION


E1P4

3BK 11204 0564 DSZZA 45/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

GP_LOCATION
SUBRACK Y / SLOT Z.
4.4.9 SGSN_IP_NSVC BLOCK
This block is relevant for Gb over IP transport Mode only (Gb_Transport_Mode = 1)
The block is reported whatever is the configuration mode (static or dynamic).
In static configuration, SGSN_IP_NSVC define the IP endpoints used for data and signalling
traffic.
In dynamic configuration, SGSN_IP_NSVC defines first the pre-configured IP endpoint and
then the negociated ones. The BSS uses the pre-configured IP endpoint to exchange the
configuration with the SGSN. Then, the SGSN gives the list of SGSN IP endpoints to use for
data and signalling traffic.

SGSN_IP_NSVC {
SGSNIPENDPOINT <SGSN IP END POINT Identifier>
. . . . . .
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>
identifier.
"16974336 Decimal


E1P4

3BK 11204 0564 DSZZA 46/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

SGSN IP END POINT identifier: "<ID>": value for the Remote IP Endpoint identifier
- SGSN_IP_ADDRESS:
- Syntax is INTEGER (32 bits)
- Coded as follow in 4 groups of 8 bits: 255.255.255.255
- Ex: the IP address 139.54.87.128 is coded 2335594368
- SGSN_UDP_PORT
- PEER_NSE_SIGNALLING_WEIGHT
- PEER_NSE_DATA_WEIGHT
- GB_CONFIGURATION_TYPE
- SGSN_NAME
- SGSN_IP_NSVC_NSEI: the Logical Name of this parameter at BTP is NSEI

GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.
4.4.10 SGSN BLOCK
This block is relevant for Gb flex is activated only.

SGSN {
SGSN <SGSN Identifier>
SGSN_Name <SGSN NAME>
. . . . . .
SF <0/1>
. . . . . .
}

with:
<Fabric Identifier>


E1P4

3BK 11204 0564 DSZZA 47/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

identifier.
"16974336 Decimal
<SGSN Identifier>": value of the identifier of the SGSN (named CN_ID_PS at BTP)
<SGSN NAME>: User Label of the SGSN
- SGSN_NSEI: the Logical Name of this parameter at BTP is NSEI
GP_HW_GENERATION
GP_LOCATION
SUBRACK Y / SLOT Z.
4.5 Specific behaviors and impact on Suspected Flag (SF)
4.5.1 Create/Delete instance
When an instance is created or deleted the block that supports these events become no more
relevant.
GP 1 GP 2 GP 3 GP 4
Create Delete
GP 5

At the end of the GP 1, the instance result block does not exist.
During GP 2, the instance is created, and therefore, the suspect flag is set to TRUE by the GPU.
At the end of GP 2, the instance result block is inserted in the result file but the period is not
completely relevant.


E1P4

3BK 11204 0564 DSZZA 48/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

During all GP 3, the instance exists. At the end of the GP 3, the resource result block is inserted
in the result file.
During GP 4, the instance result block does not exist any more.
At the end of the GP 5, the instance result block does not exist.
4.5.2 LCS service activation/desactivation
The flag EN_LCS flag exists for each BSC instance. When the LCS function is "stopped" on a cell,
the EN_LCS flag is set to FALSE. Consequently, when EN_LCS flag is set to FALSE all objects
linked at the function are deleted into GPU and, at the reverse, if EN_LCS is set to TRUE all
objects linked at the function are created in GPU.
Note that the LCS versus current release is completely different from the LCS versus previous
release, and so the blocks are diferents.
See the "4.5.1 Create/Delete instance" to know the management of the SF and existing or not of
the blocks for the instances.
4.5.3 Administrative state
The administrative state has no effect on the validity of the counters, i.e. neither on the
positioning of the suspect flag nor on the presence/absence of the block.
4.5.4 Operational state
The operational state has no effect on the validity of the counters, i.e. neither on the
positioning of the suspect flag nor on the presence/absence of the block.
4.5.5 O&M Parameter change
In this section, we are interested only in the configuration parameters inserted into result
blocks. During a GP, the OMC-R operator can change the value of some configuration
parameters. The ones that are defined with category = " Site (CAE)" into the BTP.
At the MFS, the following mechanism applies: the configuration parameter values are changed at
GOM, then the related GPU is aligned with the new parameter values. Then, it is up to the GPU
to report the parameter values into the result blocks with the counters ones, on GPM request.
So, the value of the configuration parameters is synchronized to the counter values.
The configuration parameters are handled in the same way as the counters. This means two set
of values: the current and the history data. Only the history data are changeable during GPU
configuration alignment.
The Suspected Flag (SF) is not impacted by such operation.


E1P4

3BK 11204 0564 DSZZA 49/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

4.5.6 GPU switchover / GPU reset
In case of GPU switchover (or GPU reset), a deletion and creation of the instance occurs in the
same GP. All the current measures that are performed on the faulty board are lost. Then, an
instance block for only one Granularity Period has the Suspect Flag set to TRUE. Valid result
blocks will be available from next GP.
If rarely the deletion/creation occurs but on two Granularity Periods, no result block will be
provided for the current GP, then an instance block for next Granularity Period has the Suspect
Flag set to TRUE. Afterwards, valid result blocks will be available from next GPs.
4.5.7 OMCP (MFS EVOLUTION) switch over
Most of the time, a OMCP (MFS EVOLUTION) switch over has no impact on measurement activity.
However, if the switch over occurs between the beginning of a GP (i.e.GP2 in the figure) and
GP+GPMin (i.e. GP2+GPMin in the figure), history result files corresponding to the previous GP
(i.e. GP1 in the figure) are lost and they will not be available on the MFS.

GP 1 GP 2
GPM
expiry of GP1. GP2 is
armed. The counters file for
GP1 is opened. GPM gets
by polling the results from
GP for GP1.
at GP1+ GPmin, the
file for GP1 is closed
if a switch over
occurs, file is lost !
GP 1 GP 2
GP

4.5.8 BTS Provisioning Phase
Some BTS(s) that are in the provisioning phase (or out of commercial use) are not able to
provide a complete commercial service for many reasons (the customer intends to do some
operations on them like commissioning tests before to make them in commercial service).
When these BTS(s) are declared in the OMC-R, they are supervised. When the BTS has Cells
supporting the GPRS, the MFS triggers performance measurements on these cells but all counters
collected from the telecom boards will be reported as suspect to the OMC-R/NPO if this BTS is
out of commercial use.
To identify the BTS out of commercial use, an attribute (aCmbCommercialUse) is defined and
associated to each aGprsBtsSiteMananger.
The commercial use attribute applies to the BTS (included) and whole its subtree (cells,...)


E1P4

3BK 11204 0564 DSZZA 50/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

When the operator changes the value of this attribute from 'true' to false from the OMC-R, he
makes a BTS out of commercial use and the PM data related to cell instances become no more
relevant.
At the MFS, the following mechanism applies. To limit the development cost of this feature, it
will be implemented only at the OMCP side (nothing at the GPU board side). The main drawback
is that the synchronization between the telecom and the O&M in case of commercialUse change
is not complete. At GP expiry, GPM polls all GPU boards. When it receives PM reports, it reads
the commmercialUse value. If it was set from true to false after (GP expiry) but before (GP
expiry+GPU reports reception delay), the SF will be set to 1, while the period was not suspect.

GP 1 GP 2 GP 3 GP 4
false true
GP 5
true

At the end of the GP 1, all cell instances result blocks are inserted in the result file (SF=0)
During GP 2, the aCmbCommercialUse of the aGprsBtsSiteManager instance is set to 'false'. At
the end of GP 2, the instance result blocks are inserted in the result file but the period is not
completely relevant (SF=1).
During all GP 3, the BTS is out of commercial use. No cell instance result block is inserted in the
result file at the end of GP 3.
During GP 4, the aCmbCommercialUse of the aGprsBtsSiteManager instance is set to 'true', and
thus all cell instances result blocks are inserted in the result file, but the period is not
completely relevant (SF=1).
At the end of the GP 5, the cell instances result blocks are inserted in the result file (SF=0)
Note about cell shared: if a cell is shared and the related a secondary BTS is not defined at MFS,
then the aCmbCommercialUse is considered equal to True by the MFS.
4.5.9 MFS start-up and re-start
The Report Period (RP) is launched automatically by the MFS at initialization time.
For example, considering hypothesis below
GP is equal to 60mn
GPmin is equal to 3mn
MFS start or re-start at 9:05


E1P4

3BK 11204 0564 DSZZA 51/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

GP alignment at hour boundary defined in section 2.5
RP shifting compared to GP defined in section 2.6
the first GP covers period from 10:00 to 11:00 and the GPMRES file is available at 11:03.
All the measurements are performed by the GPU. The OMCP authorizes the measurements in the
GPU when it gives the RRM configuration to the GPU.
4.5.10 Reshuffling (cells distribution over GPUs)
Recall:
A BSS can be managed by several GPUs. The BSS cells are distributed by reshuffling algorithm on
the GPUs. The aim of this algorithm is a good repartition of cells to avoid the lack of resource in
a GPU .
The reshuffling is only triggered by the operator command.
Impact:
The reshuffling command can move cells from a GPU to another GPU. It triggers a cell delete
command on the old GPU and after a cell create command on the new GPU.
When the cell is deleted the block is not sent by the GPU and when the cell is created the
Suspect Flag is set to TRUE (see 4.5.1Create/Delete instance).
The consequence is that just one cell block has the Suspect Flag set to TRUE but the set of cell
blocks is all consecutive. Rarely if the deletion/recreation of a cell does not occur in the same
GP one block can miss.
Warning : in this case the fabric identifier changes for this cell.
4.5.11 Secured Single Gb
When the last NS-VC of a GPU becomes disabled due to a Gb failure, the Gb traffic of all cells
related to this GPU is re-directed to the other ones of the same BSC.
Then, BearerChannel and PVC BLOCKS are still present but counters related to the faulty board
and the ones related to the protecting ones are affected (no traffic on the first, more traffic on
the others)
4.5.12 PTU counters and PMU counters
PTU and PMU counters are splited into different blocks. So that, in case of failure during the PTU
counters collection or restart/reset TRE during the GP, the Suspected flag of the PTU blocks are
set only. The PMU blocks are not impacted.


E1P4

3BK 11204 0564 DSZZA 52/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

4.5.13 MFS software migration
Before the activation of the (Vn+1), the MFS (active station) is still in (Vn) and GPM is working in
(Vn). All GPU are in the same (Vn) version and thus, GPM provides one file in MFS (Vn) format.
When the activation is performed, an OMCP switch over occurs. The GPM starts up in (Vn+1). It
is now ready to work with GPU (Vn) and GPU (Vn+1).
The MFS provides a PM file for previous release if at least one GPU is still running with previous
release software
The MFS provides a PM file for current release if at least one GPU is still running with current
release software (whatever is the Main Release)
For the availability at the MFS of the PM files:
the OMCP (MFS EVOLUTION) migration is equivalent to OMCP switch-over (see 4.5.7)
the GPU board migration is equivalent to a GPU switch-over (see 4.5.5)
4.5.14 IP transport activation/desactivation (GboIP)
Regarding the GboIP transport, two flags have been defined: Gb_Transport_Mode (BSS) and
Gb_Transport_Mode_per_NSE (NSE).
When the NSE is associated to a BSS, Gb_Transport_Mode (BSS) is relevant only.
In FR mode, PVC and BearerChannel blocks are relevant while SGSN_IP_NSVC block is not. And
inversely, in IP mode SGSN_IP_NSVC block is relevant while PVC and BearerChannel blocks are
not.
When the Gb transport Mode is changed, the GPU board is reset. And thus, the MFS O&M
downloads only the configuration related to the relevant Gb transport Mode. As the next period
is not completely relevant (not a full observation period), SF is set to TRUE into relevant blocks.
When blocks are no more relevant, they are no more reported.
See the "4.5.1 Create/Delete instance" to know the management of the SF.
4.5.15 IP transport activation/desactivation (BSSoIP)
Regarding the BSSoIP transport, two flags have been defined: BSS_TRANSPORT_MODE (MFS) and
ABIS_TRANSPORT_MODE (MFS)
1. When the BSS_TRANSPORT_MODE (MFS) is changed, the GPU board is reset. And thus, the
MFS O&M downloads only the configuration related to the relevant transport Mode. As the
next period is not completely relevant (not a full observation period), SF is set to TRUE
into relevant blocks. When blocks are no more relevant, they are no more reported.
See the "4.5.1 Create/Delete instance" to know the management of the SF.


E1P4

3BK 11204 0564 DSZZA 53/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

2. When the ABIS_TRANSPORT_MODE (MFS) is changed, the SF of the blocks related to the
previous transport Mode is set to TRUE (not a full observation period), and then, as
blocks are no more relevant, they are no more reported. Regarding the blocks related to
the new transport mode, the SF of the blocks is set to TRUE for the current GP (not a full
observation period), then blocks are reported with SF to FALSE.
4.5.16 Gb flex activation/desactivation
Regarding the Gb flex feature, the fllowing actication flag is defined: EN_GB_FLEX
When Gb_Transport_Mode (BSS) is IP then the EN_GB_FLEX flag is relevant.
The SGSN block is never reported if Gb_Transport_Mode (BSS) is Frame Relay.
When EN_GB_FLEX is changed from (disabled to enabled), the SGSN block becomes relevant and will be
reported. For the current period, SF I set to true (incomplete measures for the Granularity period).
When EN_GB_FLEX is changed from (enabled to disabled), the SGSN block becomes irrelevant and is no
more reported.


E1P4

3BK 11204 0564 DSZZA 54/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

ANNEX A: MFS/OMC FILES EXAMPLE.
For counters list, the reference document is document [1].
Here is only example of files.
4.6 Current release MFS / current release GPU: filename "GPMRES0800101"
#%npr MFS
#
{
{
MFS 102
VERSION MFSYAL05C
ITFVERSION 8
ScannerIdentity 1
STARTTIME 10:00:00
ENDTIME 11:00:00
DATE 2008-02-06

AbisBTSGROUP {
FABRIC 16778752
BSS 102
ABISGROUPNUMBER 15
GP_HW_GENERATION JBXGP2
GP_LOCATION RACK 1 / SUBRACK 3 / SLOT 1
SF 0
P549a 0
}

B01BTSTDM {
FABRIC 16778752
BSS 102
BTS 3
BTS_NB_EXTRA_ABIS_TS 10
SF 0
P472 0
P484 0
}

B02BTSIP {


E1P4

3BK 11204 0564 DSZZA 55/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

FABRIC 16778752
BSS 102
BTS 3
SF 0
P201bis 0
P202bis 0
P384bis 0
P541a 0
P541b 0
P541d 0
P542a 0
P542b 0
P542d 0
P543a 0
P543d 0
}

B10cellPMUCOM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
BS_PBCCH_BLKS 0
BS_PRACH_BLKS 0
MAX_PDCH 2
MIN_PDCH 1
BSS_TRANSPORT_MODE 0
ABIS_TRANSPORT_MODE 0
CSSF 0
SF 0
P10 0
P105e 0
P105f 0
P105o 0
P105p 0
P11 0
P129a 0
P129b 0
P129c 0


E1P4

3BK 11204 0564 DSZZA 56/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P129d 0
P13 0
P14 0
P146 0
P147 0
P15 0
P16 0
P160 0
P161 0
P162 0
P163 0
P164 0
P165 0
P181a 0
P181b 0
P200 0
P203 0
P204 0
P209 0
P210 0
P211 0
P212 0
P213 0
P214 0
P215 0
P216 0
P217 0
P218 0
P219 0
P22 0
P220 0
P221 0
P222 0
P223 0
P224 0
P225 0
P226 0
P227 0
P228 0
P229 0
P22a 0
P231 0
P232 0
P24 0


E1P4

3BK 11204 0564 DSZZA 57/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P26 0
P27 0
P28 0
P302b_1 0
P302b_2 0
P302c_1 0
P302c_2 0
P302c_3 0
P302c_4 0
P303a 0
P303b 0
P30a 0
P30b 0
P30c 0
P30d 0
P30e 0
P35 0
P36 0
P385a 0
P385b 0
P38b 0
P38c 0
P38e 0
P38f 0
P39 0
P390b 0
P396a 0
P396b 0
P397 0
P399 0
P40 0
P400 0
P401 0
P403b 0
P403c 0
P403d 0
P404b 0
P404c 0
P404d 0
P405a 0
P405b 0
P405c 0
P405d 0
P406a 0


E1P4

3BK 11204 0564 DSZZA 58/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P406b 0
P406c 0
P406d 0
P407a 0
P407b 0
P407c 0
P407d 0
P408a 0
P408b 0
P408c 0
P408d 0
P409 0
P410 0
P411 0
P412 0
P413 0
P414bis 0
P415bis 0
P416bis 0
P417 0
P419 0
P420 0
P422 0
P423a 0
P423b 0
P423c 0
P423d 0
P424a 0
P424b 0
P424c 0
P424d 0
P425a 0
P425b 0
P425c 0
P425d 0
P426a 0
P426b 0
P426c 0
P426d 0
P43 0
P431b 0
P431c 0
P432b 0
P432c 0


E1P4

3BK 11204 0564 DSZZA 59/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P433a 0
P433b 0
P433c 0
P433d 0
P434a 0
P434b 0
P434c 0
P434d 0
P435a 0
P435b 0
P435c 0
P435d 0
P436 0
P437a 0
P437b 0
P438a 0
P438b 0
P438c 0
P438d 0
P439 0
P43a 0
P43b 0
P43c 0
P43d 0
P44 0
P440a 0
P440b 0
P440c 0
P441a 0
P441b 0
P441c 0
P44a 0
P44b 0
P44c 0
P44d 0
P451a 0
P451b 0
P452 0
P456 0
P458 0
P460b 0
P460c 0
P461 0
P463 0


E1P4

3BK 11204 0564 DSZZA 60/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P464 0
P466 0
P480 0
P481 0
P482 0
P488 0
P489 0
P49 0
P490 0
P491 0
P492 0
P493 0
P494 0
P495 0
P496 0
P497 0
P498 0
P499 0
P501 0
P502 0
P503 0
P504 0
P505 0
P505a 0
P506 0
P506a 0
P507 0
P507a 0
P508 0
P508a 0
P509 0
P509a 0
P510 0
P510a 0
P511 0
P512 0
P513 0
P514 0
P515 0
P516 0
P518 0
P519 0
P52a 0
P52b 0


E1P4

3BK 11204 0564 DSZZA 61/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P52c 0
P52d 0
P533a_1 0
P533a_10 0
P533a_11 0
P533a_12 0
P533a_13 0
P533a_2 0
P533a_3 0
P533a_4 0
P533a_5 0
P533a_6 0
P533a_7 0
P533a_8 0
P533a_9 0
P533b_1 0
P533b_10 0
P533b_11 0
P533b_12 0
P533b_13 0
P533b_2 0
P533b_3 0
P533b_4 0
P533b_5 0
P533b_6 0
P533b_7 0
P533b_8 0
P533b_9 0
P534a_1 0
P534a_10 0
P534a_11 0
P534a_12 0
P534a_13 0
P534a_2 0
P534a_3 0
P534a_4 0
P534a_5 0
P534a_6 0
P534a_7 0
P534a_8 0
P534a_9 0
P534b_1 0
P534b_10 0
P534b_11 0


E1P4

3BK 11204 0564 DSZZA 62/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P534b_12 0
P534b_13 0
P534b_2 0
P534b_3 0
P534b_4 0
P534b_5 0
P534b_6 0
P534b_7 0
P534b_8 0
P534b_9 0
P535a_1 0
P535a_10 0
P535a_11 0
P535a_12 0
P535a_13 0
P535a_2 0
P535a_3 0
P535a_4 0
P535a_5 0
P535a_6 0
P535a_7 0
P535a_8 0
P535a_9 0
P535b_1 0
P535b_10 0
P535b_11 0
P535b_12 0
P535b_13 0
P535b_2 0
P535b_3 0
P535b_4 0
P535b_5 0
P535b_6 0
P535b_7 0
P535b_8 0
P535b_9 0
P53a 0
P53b 0
P53c 0
P53d 0
P540b 0
P540c 0
P540d 0
P540e 0


E1P4

3BK 11204 0564 DSZZA 63/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P558 0
P559 0
P560 0
P561 0
P562 0
P563 0
P564 0
P565 0
P566 0
P567 0
P568 0
P569 0
P570 0
P571 0
P572 0
P573 0
P574 0
P575 0
P576 0
P577 0
P578 0
P579 0
P595 0
P596 0
P597 0
P598 0
P599 0
P61 0
P61a 0
P61b 0
P62a 0
P62b 0
P62c 0
P62d 0
P62e 0
P65 0
P66 0
P67 0
P74 0
P75 0
P9 0
P90a 0
P90b 0
P90c 0


E1P4

3BK 11204 0564 DSZZA 64/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P90d 0
P90e 0
P90f 0
P90g 0
P90h 0
P90i 0
P91a 0
P91b 0
P91c 0
P91d 0
P91e 0
P91f 0
P91g 0
P91h 0
P91i 0
P95 0
P96 0
P97 0
P98a 0
P98b 0
P98c 0
P98d 0
P98e 0
P98f 0
P99 0
P9a 0
}

B11cellPMUTDM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
SF 0
P100c 0
P100d 0
P100e 0
P105c 0
P105d 0
P105g 0
P105h 0


E1P4

3BK 11204 0564 DSZZA 65/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P105i 0
P105j 0
P105k 0
P105l 0
P403a 0
P404a 0
P465 0
P469 0
P470 0
P471 0
}

B12cellPMUIP {
FABRIC 16778752
BSS 102
BTS 3
LAC 10
CI 6
SF 0
P105m 0
P105n 0
P552 0
}

B20cellPTUCOM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
SF 0
P207 0
P208 0
P20a 0
P20b 0
P20c 0
P20d 0
P20f 0
P20g 0
P20h 0


E1P4

3BK 11204 0564 DSZZA 66/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P20i 0
P20j 0
P20k 0
P20l 0
P20m 0
P20n 0
P21a 0
P21b 0
P21c 0
P21d 0
P21f 0
P21g 0
P21h 0
P21i 0
P21j 0
P21k 0
P21l 0
P21m 0
P21n 0
P310a 0
P310b 0
P310c 0
P310d 0
P335 0
P336 0
P350a 0
P350b 0
P351a 0
P351b 0
P352a 0
P352b 0
P421 0
P457 0
P459 0
P462 0
P55a 0
P55b 0
P55c 0
P55d 0
P55e 0
P55f 0
P55g 0
P55h 0
P55i 0


E1P4

3BK 11204 0564 DSZZA 67/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P55j 0
P55k 0
P55l 0
P55m 0
P57a 0
P57b 0
P57c 0
P57d 0
P57e 0
P57f 0
P57g 0
P57h 0
P57i 0
P57j 0
P57k 0
P57l 0
P57m 0
P59 0
P60 0
P72c 0
P72d 0
P73c 0
P73d 0
}
B21cellPTUTDM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
SF 0
P80a 0
P80b 0
P81a 0
P81b 0
P82a 0
P82b 0
P83a 0
P83b 0
P84a 0
P84b 0
P85 0


E1P4

3BK 11204 0564 DSZZA 68/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

}

B30BSCCOM {
FABRIC 16778752
BSS 102
GCSF 0
SF 0
P104 0
P106 0
P107 0
P201 0
P202 0
P384ter 0
P390a 0
P391a 0
P391b 0
P391c 0
P392a 0
P392b 0
P402 0
P450a 0
P450b 0
P450c 0
P450d 0
P450e 0
P487 0
P500 0
P530a_1 0
P530a_2 0
P530a_3 0
P530a_4 0
P530a_5 0
P530b_5 0
P594 0
P76a 0
P77a 0
P7a 0
P7b 0
P7c_1 0
P7c_2 0
P7d 0
P7e 0


E1P4

3BK 11204 0564 DSZZA 69/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P7f 0
P7g 0
P7h 0
P7i 0
P7j 0
P7k 0
}

B31BSCTDM {
FABRIC 16778752
BSS 102
SF 0
P100f 0
P101 0
P103 0
P383a 0
P383b 0
P384 0
P474 0
P486 0
}

B40BSSADJEXT {
FABRIC 16778752
BSS 102
LAC 205
CI 302
MNC 100
MCC 110
SF 0
P182c 0
P182d 0
P182e 0
}

B41CELLNACC {
FABRIC 16778752
BSS 156
LAC 156
CI 156


E1P4

3BK 11204 0564 DSZZA 70/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

MNC 100
MCC 110
SF 0
P182a 0
P182b 0
}

BearerChannel {
TP 16778756
Bearer 3
SF 0
P33 0
P3a 0
P3b 0
P6a 0
P6b 0
}

DistCell {
FABRIC 16778752
BSS 102
CI 6
LAC 10
PD_UL_TBF_DURATION_THR_1 3278
PD_DL_TBF_DURATION_THR_1 3278


E1P4

3BK 11204 0564 DSZZA 71/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

PD_UL_TBF_VOLUME_THR_1 10000000
PD_DL_TBF_VOLUME_THR_1 10000000
PD_UL_PDCH_UNIT_ALLOC_THR_1 5
PD_DL_PDCH_UNIT_ALLOC_THR_1 5


E1P4

3BK 11204 0564 DSZZA 72/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

EGPRS_LLC_THROUGHPUT_THR_1 1
GPRS_LLC_THROUGHPUT_THR_1 1
DSF 0
SF 0
P453a_1 0
P453a_10 0
P453a_2 0
P453a_3 0
P453a_4 0
P453a_5 0
P453a_6 0
P453a_7 0
P453a_8 0
P453a_9 0
P453b_1 0
P453b_10 0
P453b_2 0
P453b_3 0
P453b_4 0
P453b_5 0
P453b_6 0
P453b_7 0
P453b_8 0
P453b_9 0


E1P4

3BK 11204 0564 DSZZA 73/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P454a_1 0
P454a_10 0
P454a_2 0
P454a_3 0
P454a_4 0
P454a_5 0
P454a_6 0
P454a_7 0
P454a_8 0
P454a_9 0
P454b_1 0
P454b_10 0
P454b_2 0
P454b_3 0
P454b_4 0
P454b_5 0
P454b_6 0
P454b_7 0
P454b_8 0
P454b_9 0
P455a_1 0
P455a_10 0
P455a_2 0
P455a_3 0
P455a_4 0
P455a_5 0
P455a_6 0
P455a_7 0
P455a_8 0
P455a_9 0
P455b_1 0
P455b_10 0
P455b_2 0
P455b_3 0
P455b_4 0
P455b_5 0
P455b_6 0
P455b_7 0
P455b_8 0
P455b_9 0
P531a_1 0
P531a_10 0
P531a_11 0
P531a_2 0


E1P4

3BK 11204 0564 DSZZA 74/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P531a_3 0
P531a_4 0
P531a_5 0
P531a_6 0
P531a_7 0
P531a_8 0
P531a_9 0
P531b_1 0
P531b_10 0
P531b_11 0
P531b_2 0
P531b_3 0
P531b_4 0
P531b_5 0
P531b_6 0
P531b_7 0
P531b_8 0
P531b_9 0
P532a_1 0
P532a_10 0
P532a_2 0
P532a_3 0
P532a_4 0
P532a_5 0
P532a_6 0
P532a_7 0
P532a_8 0
P532a_9 0
P532b_1 0
P532b_10 0
P532b_2 0
P532b_3 0
P532b_4 0
P532b_5 0
P532b_6 0
P532b_7 0
P532b_8 0
P532b_9 0
}

LapD {
TP 16778757


E1P4

3BK 11204 0564 DSZZA 75/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

BSS 101
GSL 1
SF 0
P2a 0
P2b 0
P2c 0
P2d 0
P32 0
P41 0
P42 0
}

LcsCell {
FABRIC 16778752
BSS 102
LAC 10
CI 6
SF 0
P800 0
P801 0
P802 0
P803 0
P804 0
P805 0
P806 0
P807 0
P808 0
P809 0
P810 0
P811 0
P812 0
P813 0
P814 0
P815 0
P816 0
P817 0
P818 0
P819 0
P820 0
P821 0
P822 0
P823 0


E1P4

3BK 11204 0564 DSZZA 76/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P824 0
P825 0
P826 0
P827 0
P828 0
P829 0
P830 0
P831 0
P832 0
P833 0
P834 0
P835 0
P836 0
P837 0
}

pvc {
TP 16778756
Bearer 3
PVC 1
SF 0
P23 0
P34 0
P4 0
P45 0
P46 0
P5 0
P6c 0
P6d 0
}

SGSN_IP_NSVC {
FABRIC 16778752
SGSNIPENDPOINT 1
SGSN_IP_ADDRESS 0
SGSN_UDP_Port 0
Peer_NSE_Signalling_Weight 0
Peer_NSE_Data_Weight 0
Gb_Configuration_type 0
SGSN_Name SGSN_3
SGSN_IP_NSVC_NSEI 1


E1P4

3BK 11204 0564 DSZZA 77/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

SF 0
P34a 0
P45a 0
P46a 0
}

SGSN {
FABRIC 16778752
SGSN 3
SGSN_Name SGSN_3
SGSN_NSEI 1
SF 0
P180a 0
P180b 0
}

}
}
4.7 Current release MFS / previous release GPU: filename "GPMRES0700101"
#%npr MFS
#
{
{
MFS 102
VERSION MFSYAL25C
ITFVERSION 7
ScannerIdentity 1
STARTTIME 10:00:00
ENDTIME 11:00:00
DATE 2008-02-06

B01BTSTDM {
FABRIC 16778752
BSS 102
BTS 3
BTS_NB_EXTRA_ABIS_TS 10
SF 0
P472 0
P484 0


E1P4

3BK 11204 0564 DSZZA 78/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

}

B10cellPMUCOM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
BS_PBCCH_BLKS 0
BS_PRACH_BLKS 0
MAX_PDCH 2
MIN_PDCH 1
CSSF 0
SF 0
P10 0
P105e 0
P105f 0
P11 0
P129a 0
P129b 0
P129c 0
P129d 0
P13 0
P14 0
P15 0
P16 0
P160 0
P161 0
P162 0
P163 0
P164 0
P165 0
P200 0
P203 0
P204 0
P209 0
P210 0
P211 0
P212 0
P213 0
P214 0
P215 0
P216 0
P217 0


E1P4

3BK 11204 0564 DSZZA 79/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P218 0
P219 0
P22 0
P220 0
P221 0
P222 0
P223 0
P224 0
P225 0
P226 0
P227 0
P228 0
P229 0
P231 0
P232 0
P24 0
P26 0
P27 0
P28 0
P302b_1 0
P302b_2 0
P302c_1 0
P302c_2 0
P302c_3 0
P302c_4 0
P303a 0
P303b 0
P30a 0
P30b 0
P30c 0
P30d 0
P35 0
P36 0
P385a 0
P385b 0
P38b 0
P38c 0
P38e 0
P38f 0
P39 0
P396a 0
P396b 0
P397 0
P399 0


E1P4

3BK 11204 0564 DSZZA 80/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P40 0
P400 0
P401 0
P403b 0
P403c 0
P403d 0
P404b 0
P404c 0
P404d 0
P405a 0
P405b 0
P405c 0
P405d 0
P406a 0
P406b 0
P406c 0
P406d 0
P407a 0
P407b 0
P407c 0
P407d 0
P408a 0
P408b 0
P408c 0
P408d 0
P409 0
P410 0
P411 0
P412 0
P413 0
P414bis 0
P415bis 0
P416bis 0
P417 0
P419 0
P420 0
P422 0
P423a 0
P423b 0
P423c 0
P423d 0
P424a 0
P424b 0
P424c 0


E1P4

3BK 11204 0564 DSZZA 81/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P424d 0
P425a 0
P425b 0
P425c 0
P425d 0
P426a 0
P426b 0
P426c 0
P426d 0
P43 0
P431b 0
P431c 0
P432b 0
P432c 0
P433a 0
P433b 0
P433c 0
P433d 0
P434a 0
P434b 0
P434c 0
P434d 0
P435a 0
P435b 0
P435c 0
P435d 0
P436 0
P437a 0
P437b 0
P438a 0
P438b 0
P438c 0
P438d 0
P439 0
P43a 0
P43b 0
P43c 0
P43d 0
P44 0
P440a 0
P440b 0
P440c 0
P441a 0
P441b 0


E1P4

3BK 11204 0564 DSZZA 82/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P441c 0
P44a 0
P44b 0
P44c 0
P44d 0
P451a 0
P451b 0
P452 0
P456 0
P458 0
P460b 0
P460c 0
P461 0
P463 0
P464 0
P466 0
P480 0
P481 0
P482 0
P488 0
P489 0
P49 0
P490 0
P491 0
P492 0
P493 0
P494 0
P495 0
P496 0
P497 0
P498 0
P499 0
P501 0
P502 0
P503 0
P504 0
P505 0
P506 0
P507 0
P508 0
P509 0
P510 0
P511 0
P512 0


E1P4

3BK 11204 0564 DSZZA 83/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P513 0
P514 0
P515 0
P516 0
P518 0
P519 0
P52a 0
P52b 0
P52c 0
P52d 0
P533a_1 0
P533a_10 0
P533a_11 0
P533a_12 0
P533a_13 0
P533a_2 0
P533a_3 0
P533a_4 0
P533a_5 0
P533a_6 0
P533a_7 0
P533a_8 0
P533a_9 0
P533b_1 0
P533b_10 0
P533b_11 0
P533b_12 0
P533b_13 0
P533b_2 0
P533b_3 0
P533b_4 0
P533b_5 0
P533b_6 0
P533b_7 0
P533b_8 0
P533b_9 0
P534a_1 0
P534a_10 0
P534a_11 0
P534a_12 0
P534a_13 0
P534a_2 0
P534a_3 0
P534a_4 0


E1P4

3BK 11204 0564 DSZZA 84/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P534a_5 0
P534a_6 0
P534a_7 0
P534a_8 0
P534a_9 0
P534b_1 0
P534b_10 0
P534b_11 0
P534b_12 0
P534b_13 0
P534b_2 0
P534b_3 0
P534b_4 0
P534b_5 0
P534b_6 0
P534b_7 0
P534b_8 0
P534b_9 0
P535a_1 0
P535a_10 0
P535a_11 0
P535a_12 0
P535a_13 0
P535a_2 0
P535a_3 0
P535a_4 0
P535a_5 0
P535a_6 0
P535a_7 0
P535a_8 0
P535a_9 0
P535b_1 0
P535b_10 0
P535b_11 0
P535b_12 0
P535b_13 0
P535b_2 0
P535b_3 0
P535b_4 0
P535b_5 0
P535b_6 0
P535b_7 0
P535b_8 0
P535b_9 0


E1P4

3BK 11204 0564 DSZZA 85/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P53a 0
P53b 0
P53c 0
P558 0
P559 0
P560 0
P561 0
P562 0
P563 0
P564 0
P565 0
P566 0
P567 0
P568 0
P569 0
P570 0
P571 0
P572 0
P573 0
P574 0
P575 0
P576 0
P577 0
P578 0
P579 0
P595 0
P596 0
P597 0
P598 0
P599 0
P61 0
P61a 0
P61b 0
P62a 0
P62b 0
P62c 0
P62d 0
P65 0
P66 0
P67 0
P74 0
P75 0
P9 0
P90a 0


E1P4

3BK 11204 0564 DSZZA 86/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P90b 0
P90c 0
P90d 0
P90e 0
P90f 0
P90g 0
P91a 0
P91b 0
P91c 0
P91d 0
P91e 0
P91f 0
P91g 0
P95 0
P96 0
P97 0
P98a 0
P98b 0
P98c 0
P98d 0
P98e 0
P98f 0
P99 0
}

B11cellPMUTDM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
SF 0
P100c 0
P100d 0
P100e 0
P105c 0
P105d 0
P105g 0
P105h 0
P105i 0
P105j 0
P105k 0
P105l 0
P146 0


E1P4

3BK 11204 0564 DSZZA 87/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P147 0
P403a 0
P404a 0
P465 0
P469 0
P470 0
P471 0
}

B20cellPTUCOM {
FABRIC 16778752
BSS 102
LAC 10
CI 6
BTS 3
SF 0
P207 0
P208 0
P20a 0
P20b 0
P20c 0
P20d 0
P20f 0
P20g 0
P20h 0
P20i 0
P20j 0
P20k 0
P20l 0
P20m 0
P20n 0
P21a 0
P21b 0
P21c 0
P21d 0
P21f 0
P21g 0
P21h 0
P21i 0
P21j 0
P21k 0
P21l 0
P21m 0
P21n 0


E1P4

3BK 11204 0564 DSZZA 88/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P310a 0
P310b 0
P310c 0
P310d 0
P335 0
P336 0
P350a 0
P350b 0
P351a 0
P351b 0
P352a 0
P352b 0
P421 0
P457 0
P459 0
P462 0
P55a 0
P55b 0
P55c 0
P55d 0
P55e 0
P55f 0
P55g 0
P55h 0
P55i 0
P55j 0
P55k 0
P55l 0
P55m 0
P57a 0
P57b 0
P57c 0
P57d 0
P57e 0
P57f 0
P57g 0
P57h 0
P57i 0
P57j 0
P57k 0
P57l 0
P57m 0
P59 0
P60 0


E1P4

3BK 11204 0564 DSZZA 89/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P72c 0
P72d 0
P73c 0
P73d 0
}

B30BSCCOM {
FABRIC 16778752
BSS 102
GCSF 0
SF 0
P104 0
P106 0
P107 0
P201 0
P202 0
P391a 0
P391b 0
P392a 0
P392b 0
P402 0
P450a 0
P450b 0
P450c 0
P450d 0
P450e 0
P487 0
P500 0
P530a_1 0
P530a_2 0
P530a_3 0
P530a_4 0
P530a_5 0
P530b_5 0
P594 0
P597 0
P76a 0
P77a 0
}

B31BSCTDM {
FABRIC 16778752
BSS 102
SF 0


E1P4

3BK 11204 0564 DSZZA 90/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P100f 0
P101 0
P103 0
P383a 0
P383b 0
P384 0
P474 0
P486 0
}

B40BSSADJEXT {
FABRIC 16778752
BSS 102
LAC 205
CI 302
MNC 100
MCC 110
SF 0
P182c 0
P182d 0
P182e 0
}

B41CELLNACC {
FABRIC 16778752
BSS 156
LAC 156
CI 156
MNC 100
MCC 110
SF 0
P182a 0
P182b 0
}

BearerChannel {
TP 16778756
Bearer 3
SF 0
P33 0
P3a 0
P3b 0
P6a 0
P6b 0


E1P4

3BK 11204 0564 DSZZA 91/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

}

DistCell {
FABRIC 16778752
BSS 102
CI 6
LAC 10


E1P4

3BK 11204 0564 DSZZA 92/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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



E1P4

3BK 11204 0564 DSZZA 93/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

DSF 0
SF 0
P453a_1 0
P453a_10 0
P453a_2 0
P453a_3 0
P453a_4 0
P453a_5 0
P453a_6 0
P453a_7 0
P453a_8 0
P453a_9 0
P453b_1 0
P453b_10 0
P453b_2 0
P453b_3 0
P453b_4 0
P453b_5 0
P453b_6 0
P453b_7 0
P453b_8 0
P453b_9 0
P454a_1 0
P454a_10 0
P454a_2 0
P454a_3 0
P454a_4 0
P454a_5 0
P454a_6 0
P454a_7 0
P454a_8 0
P454a_9 0
P454b_1 0
P454b_10 0
P454b_2 0
P454b_3 0
P454b_4 0
P454b_5 0
P454b_6 0
P454b_7 0
P454b_8 0
P454b_9 0
P455a_1 0
P455a_10 0


E1P4

3BK 11204 0564 DSZZA 94/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P455a_2 0
P455a_3 0
P455a_4 0
P455a_5 0
P455a_6 0
P455a_7 0
P455a_8 0
P455a_9 0
P455b_1 0
P455b_10 0
P455b_2 0
P455b_3 0
P455b_4 0
P455b_5 0
P455b_6 0
P455b_7 0
P455b_8 0
P455b_9 0
P531a_1 0
P531a_10 0
P531a_11 0
P531a_2 0
P531a_3 0
P531a_4 0
P531a_5 0
P531a_6 0
P531a_7 0
P531a_8 0
P531a_9 0
P531b_1 0
P531b_10 0
P531b_11 0
P531b_2 0
P531b_3 0
P531b_4 0
P531b_5 0
P531b_6 0
P531b_7 0
P531b_8 0
P531b_9 0
P532a_1 0
P532a_10 0
P532a_2 0
P532a_3 0


E1P4

3BK 11204 0564 DSZZA 95/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P532a_4 0
P532a_5 0
P532a_6 0
P532a_7 0
P532a_8 0
P532a_9 0
P532b_1 0
P532b_10 0
P532b_2 0
P532b_3 0
P532b_4 0
P532b_5 0
P532b_6 0
P532b_7 0
P532b_8 0
P532b_9 0
}

LapD {
TP 16778757
BSS 101
GSL 1
SF 0
P2a 0
P2b 0
P2c 0
P2d 0
P32 0
P41 0
P42 0
}

LcsCell {
FABRIC 16778752
BSS 102
LAC 10
CI 6
SF 0
P800 0
P801 0
P802 0
P803 0
P804 0
P805 0


E1P4

3BK 11204 0564 DSZZA 96/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P806 0
P807 0
P808 0
P809 0
P810 0
P811 0
P812 0
P813 0
P814 0
P815 0
P816 0
P817 0
P818 0
P819 0
P820 0
P821 0
P822 0
P823 0
P824 0
P825 0
P826 0
P827 0
P828 0
P829 0
P830 0
P831 0
P832 0
P833 0
P834 0
P835 0
P836 0
P837 0
}

pvc {
TP 16778756
Bearer 3
PVC 1
SF 0
P23 0
P34 0
P4 0
P45 0
P46 0


E1P4

3BK 11204 0564 DSZZA 97/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

P5 0
P6c 0
P6d 0
}

SGSN_IP_NSVC {
FABRIC 16778752
SGSNIPENDPOINT 1
SGSN_IP_ADDRESS 0
SGSN_UDP_Port 0
Peer_NSE_Signalling_Weight 0
Peer_NSE_Data_Weight 0
Gb_Configuration_type 0
SF 0
P34a 0
P45a 0
P46a 0
}

SGSN {
FABRIC 16778752
SGSN 3
SGSN_Name SGSN_3
SGSN_NSEI 1
SF 0
P180a 0
P180b 0
}

}
}


E1P4

3BK 11204 0564 DSZZA 98/98

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

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

f
r
o
m

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

GLOSSARY

BSC Base Station Controler
BTS Base Transceiver Station
DSF Distribution Suspected Flag
GCSF GPU Configuration Suspected Flag
GP Granularity Period
GPM Global Performance Manager
GPRS Global Packet Radio Service
GPU GPRS Processing Unit
HW HardWare
MFS Multi BSS Fast Packet Server
NS-VC Network Service Virtual Connection
NPO Network Performance Optimization
O&M Operation and Maintenance
OMC-R Operation and Maintenance Centre for Radio
PM Performance Management
PVC Permanent Virtual Connection
RP Reporting Period
SF Suspected Flag
SW SoftWare
TPM Telecom Performance Manager

END OF DOCUMENT

3BK 11204 0564 Dszza

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

3BK 11204 0564 Dszza

Caricato da

Copyright:

Formati disponibili

ED 1 PROPOSAL 3 MFS/OMC PM file interface specification

B12 MFS-OMC PM FILE INTERFACE

Potrebbero piacerti anche