Traffic Data RecordingTraffic Data Recording

SPOTS FunctionsSPOTS Functions

Traffic ReportsTraffic Reports

Do you know call completion rates,answer seizure ratios,

traffic volumes,busy hours,

congestion rates,and many other performance indicators?

Fig. 1 Motivation (MN3510EU10MN_0002 Traffic Data Recording, 3)

SIEM ENSN IXDOR F

O M C

N E 1 N E 2 N E n

B C T

S P O T S

T ra fficD a ta

Fig.

2 D

ata

colle

ctio

n (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 5

)

Fig.

3 C

all f

low

with

traf

fic

mea

sure

men

t cou

nter

s (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 7

)

Fig.

4 T

raff

ic ty

pes

(MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 13)

Abbr. Explanation of Abbreviation

CC Calls carried

CCS Calls carried successful (in the SN)

CCS-WA Calls carried successful with answer

CCU Calls carried unsuccessful

COF Overflow calls

CU Calls unsuccessful (loss mode)

CW Calls waiting (delay mode)

MHT Mean holding time tm (sec)

MHT-WA Mean holding time for calls with answer (sec)

MWT Mean waiting time tw (sec) : Waiting Volume / Calls Waiting

MWT* Mean waiting time twq (sec) : Waiting Volume / Call Attempts

N Number of trunks / circuits /servers

P(>0) Probability of delay

P(>t) Probability of delay exceeding waiting time t

T Observation time

TC Traffic carried (Erl)

TC-WA Traffic carried with answer

TCCU Traffic carried for calls unsuccessful (Erl)

TCOF Overflow carried (Erl)

TO Traffic offered (Erl)

TU Traffic unsuccessful for exchange (Erl)

TV Traffic volume (Erls)

TV-WA Traffic volume for calls with answer (Erls)

TVO Traffic volume offered (Erls)

TVOF Overflow traffic volume (Erls)

TVU Traffic vol. unsucc. (Erls)

Fig.

5 O

verv

iew

of

traf

fic

vari

able

s (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 1

5)

BSS MSC BSS

HLR

Connection request

TCH request

TCH allocation

Setup

Paging

Paging Response

TCH request

TCH allocation

Connect

Connection request

TCH request

TCH allocation

Started Interrogation

Completed Interrogation

Fig. 6 Mobile to mobile call (MN3510EU10MN_0002 Traffic Data Recording, 19)

MSC - VLR - CP Data SW-Vers. Date: 01-07-24

Exchange ID: MSC11 SR8 Time: 19:00

ORIG / INC MSC Interv. 4MORTR

CR (Compl. L3 Info) CALL_ATTEMPTS (MORTR) 61.905

1 UNS_CONGESTION

0 UNS_OVERLOAD

SET UP (MSISDN) Digit Analysis 5.808 Call Forw. or REL A

194 UNS_SERV_CHECK

216 UNS_REQ_DEST_ERR

Delta = 6.219 10,0%

DT1 ASS_REQ GEN_TRAFF_CHAN_REQ 55.686 MOBILE_ORIGIN

BSS

Delta = 1.474 2,6%22.112

DT1 ASS_COMPL. CALL_TCH_ALLOCATION 54.212 PSTN or others

Mob. To Mob. Calls

MICTR

IAM incoming CALL_ATTEMPTS (MICTR) 48.104

217 UNS_OVERLOAD

Digit Analysis IAM (Loop LTG)

REL_COM 693 REL_BEFORE_ACM_MICTR

ORIG = PLMN

(Gateway MSC or ORIG = PSTN or PLMN foreign

Transit MSC)

MORTR STARTED_INTERROGATIONS 33.348 SEND ROUTING

MICTR STARTED_INTERROGATIONS 12.206 INFO

HLR

Delta = 424 0,9%

MORTR COMPL_INTERROGATIONS 32.737 SEND ROUTING

MICTR COMPL_INTERROGATIONS 11.898 INFO

386 UNS_MS_DETACHED (MORTR)

109 UNS_MS_DETACHED (MICTR)

Digit Analysis

18.991 CALL_ATTEMPTS (PLMN_OUT)

from MORTR MOUT_PLMN

7.596 with Interogation

34.988 PSTN / MSRN 3.889 PLMN

MSRN 31.099 11.485 MOBILE TRANSIT

13.965 Interrog. PSTN

UNS 4.083

MOBILE TERMINATING 45.064

B

A

D

C

D

D

D

Fig.

7 M

SC m

easu

rem

ent f

or m

obile

ori

gina

ting

and

inco

min

g tr

affi

c (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 2

1)

Fig.

8 M

SC m

easu

rem

ent f

or m

obile

term

inat

ing

traf

fic

(MT

ER

) (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 2

3)

Fig.

9 I

NT

RA

MSC

han

dove

r (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 2

5)

BSS-A MSC_A MSC-B

Handover Required

HANDOVER_ATTEMPTS 9287 HANDOVER_UPLINK_QUALITY 684 HANDOVER_UPLINK_STRENGTH 0 HANDOVER_DOWNLINK_QUALITY 4095 HANDOVER_DOWNLINK_STRENGTH 0 HANDOVER_DISTANCE 0 HANDOVER_BETTER_CELL 3674 HANDOVER_RESP_TO_MSC 0 HANDOVER_OP_MAINT_INIT 0 HANDOVER_DIRECTED_RETRY 0

HO_MSC_MSC_OG_ATTEMPTS 3636

PREPARE HANDOVER

SUBSEQ_MSC_MSC_HO_MSCA 1889

HO_MSC_MSC IC_ATTEMPTS

Handover canceled internal

UNS_HO_LACK_RESOURCE 0

Handover Command

HO_CONFERENCE 9114 HO_OLD_CELL 8787 Note: These Counters include Inter + Intra HO

HO Request

Ackn.

SUCC_MSC_MSC_HO_MSCA 5016 INTER_HO SUCCESS Rate 90.8%

Send End Signal

Fig.

10

INT

ER

MSC

han

dove

r (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 2

7)

Fig.

11

Loc

atio

n up

date

(M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 2

9)

TV Traffic VolumeN N N Number of TrunksO O CC Calls CarriedD D CR Calls RejectedE E ATBT All Trunk Busy Time

ATBN All Trunk Busy Number1 2 CCSWA Calls With Answer

Measurement Data: T = 3600 s

TV 21605 Erls TC = y = TV / T = 21605 Erls / 3600 s = 6.00 Erl

N 10 Trunks TCTrunk = TC / N = 6.00 Erl / 10 = 0.6 Erl

CC 228 Calls MHT = TV / CC = 21605 Erls / 228 Calls = 94.76 s

CR 13 Calls B = CR / CA = 13 / ( 228 + 13 ) * 100% = 5.4 %

ATBT 204 s ATBR = ATBT / T = 204 s / 3600 s * 100% = 5.6%

ATBN 15 Calls ATBm = ATBT / ATBN = 204 s / 15 = 13.60 s

CCS-WA 169 Calls ASR = CWA / CC = 169 / 228 * 100% = = 74.12 %

Verification with ERLANG_B - Formula:

A, R, B = f ( y, N ) y = TC = 6.0 Erl, N = 10 Trunks

Traffic offered A = 6.34 Erl

Traffic Rejected R = 0.34 Erl

Loss B B = 5.43 %

N =

10

Tru

nk

s

Fig.

12

Tru

nk g

roup

mea

sure

men

t (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 4

1)

Fig.

13

Tru

nk g

roup

mea

sure

men

t dat

a (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 4

3)

Measurement L2 Info L2 Info Bytes

FLAG (End)

CRC 2 Bytes

SIF n Bytes

SIO 1 Byte

LI

1 Byte

FSN 1 Byte

BSN

1 Byte

FLAG (Begin) 1 Byte

Fig. 14 MSU format (MN3510EU10MN_0002 Traffic Data Recording, 44)

Fig.

15

CC

S7 li

nk lo

ad (

MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 45)

Case Octets /

MSU ALL5 Padding ATM Cells ATM Oct.

Load Factor

1 60 12 24 2 106 1.47

2 84 12 0 2 106 1.10

3 100 12 32 3 159 1.59

4 120 12 12 3 159 1.33

Fig. 16 Load factor for high speed link (MN3510EU10MN_0002 Traffic Data Recording, 46)

Link Load for High Speed Links (HSL)

Given: Number of Octets = 8 568 / Sec

Number of PDU’s = 84 / Sec

ATM Octets: PDU_Octets + ALL5 + Padding

Step 1: Calculate: Number of ATM Octets =

[(N’ Octets + N’ PDUs * ( AAL5 + Padding)] * 53 / 48

[( 8 568 + 84 * ( 12 + 23.5 )] * 53 / 48 = 12 753

Step 2: Calculate: Load Factor

= N’ ATM Octets / N’ PDU Octets = 12 753 / 8 568 = 1.49

Step 3: Calculate: HSL Link Load

= [ (N’ PDU Octets * Load Factor / 53 + Poll & Status Cells ] / 4300

= [ (8 568 * 1.49) / 53 + 20 ] /4300 = 6.0%

Fig. 17 Signaling link load for high-speed links (MN3510EU10MN_0002 Traffic Data Recording, 47)

Fig.

18

Proc

esso

r lo

ad (

MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 49)

Function: BAPS + CAP Load A (NL) Load B (HL)

Operating System OS 100 mErl 100 mErl

System Idle 150 mErl -

Call Processing CALLP 750 mErl 900 mErl

Example: N' CAP's = 6 CALLP Load max (Load A) = (1 + 6) * 750 mErl = 5 250 mErl

N' CAP's = 6 CALLP Load max (Load B) = (1 + 6) * 900 mErl = 6 300 mErl

Fig. 19 CALLP budget for BAPS and CAPS (MN3510EU10MN_0002 Traffic Data Recording, 50)

Function: BAPS + CAP Load A (NL) Load B (HL)

Operating System OS 100 mErl 100 mErl

Operation & Maintenance 600 mErl 720 m Erl

System Idle 150 mErl -

Call Processing CALLP 150 mErl 180 mErl

Example: N' CAP's = 4 CALLP Load max (Load A) = (1 + 4) * 750 + 150 = 3 900 mErl N' CAP's = 4 CALLP Load max (Load B) = (1 + 4) * 900 + 180 = 4 680 mErl

Fig. 20 CALLP budget for BAPM (Base Processor Master) (MN3510EU10MN_0002 Traffic Data Recording, 50)

N'CAPSN'PROC

BAP + CAPAverage

Load

Compare with

670 mErl

Load A(NL)

Nr Nr mErl Perc. mErl mErl Perc. mErl Perc.

0 2 625 -6,7% 1.250 750 60,0% 500 40,0%

1 3 633 -5,5% 1.900 1.500 78,9% 400 21,1%

2 4 650 -3,0% 2.600 2.250 86,5% 350 13,5%

3 5 640 -4,5% 3.200 3.000 93,8% 200 6,3%

4 6 650 -3,0% 3.900 3.750 96,2% 150 3,8%

5 7 657 -1,9% 4.600 4.500 97,8% 100 2,2%

6 8 656 -2,1% 5.250 5.250 100,0% 0 0,0%

7 9 667 -0,5% 6.000 6.000 100,0% 0 0,0%

8 10 675 0,7% 6.750 6.750 100,0% 0 0,0%

9 11 682 1,8% 7.500 7.500 100,0% 0 0,0%

10 12 688 2,6% 8.250 8.250 100,0% 0 0,0%

BAPS + CAPusage for

CALLP

CALLP Loadon BAPM

Fig. 21 CALLP load A (NL) for CP113 (MN3510EU10MN_0002 Traffic Data Recording, 51)

Fig. 22 Traffic flow in an exchange (MN3510EU10MN_0002 Traffic Data Recording, 53)

Measurement: REC GOS Date Busy Hour No of Intervals

Training Exchange 98-03-11 10:15 11:15 51

CALL's CALL's [%]

Internal

CA_ORIG = 30.799 CC_IT = 9.874 23,54%

CCS WA 5.754 58,27%CCS unall. Num 318 3,22%

CC No Dial A 2 0,01% CCS SB busy 609 6,17%CCU Incom. Dial 54 0,18% CCS TR busy 166 1,68%CCU unall. Num 13 0,04% CCU SB busy 0 0,00%CCU Techn. IRR. 4 0,01% CCU TR busy 0 0,00%CCU TGRP block 0 0,00% CCS compl. DIAL 1.905 19,29%CCU NO AUTH 0 0,00% CCS incom. DIAL 696 7,05%

0,00% Else 426 4,31%

CCU Else 1 0,00% Outgoing

CCU Total 74 0,24% CC_OO = 20.851 49,71%

CCS WA 13.478 64,64%CCS unall. Num 1.172 5,62%CCS SB busy 2.775 13,31%CCS TR busy 311 1,49%CCU Techn. IRR. 0 0,00%CCU TR busy 0 0,00%CCS compl. DIAL 1.811 8,69%CCS incom. DIAL 823 3,95%Else 481 2,31%

CA_EX = 41.949Terminating

CA_INC = 11.150 CC_TE = 6.422 15,31%

CCS WA 3.565 55,51%CCS unall. Num 600 9,34%

CC No Dial A 0 0,00% CCS SB busy 541 8,42%CCU Incom. Dial 2 0,02% CCS TR busy 181 2,82%CCU unall. Num 40 0,36% CCU SB busy 0 0,00%CCU Techn. IRR. 0 0,00% CCU TR busy 0 0,00%CCU TGRP block 0 0,00% CCS compl. DIAL 1.047 16,30%CCU DPC Overl. 0 0,00% CCS incom. DIAL 216 3,36%

0 0,00% Else 272 4,24%

CCU Else 1 0,01% Transit

CCU Total 43 0,39% CC_TR = 4.685 11,17%

CCS WA 3.116 66,51%CCS unall. Num 154 3,29%CCS SB busy 486 10,37%CCS TR busy 92 1,96%CCU Techn. IRR. 0 0,00%CCU TR busy 0 0,00%CCS compl. DIAL 492 10,50%CCS incom. DIAL 155 3,31%Else 190 4,06%

CCU Total 117 0,28% CC_EX = 41.832 99,72%

Fig.

23

Cal

l flo

w (

MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 55)

Fig.

24

Mea

sure

men

t cou

nter

RE

C G

OS

part

1 (

MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 56)

Fig.

25

Mea

sure

men

t cou

nter

RE

C G

OS

part

2 (

MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 57)

Fig.

26

Mea

sure

men

t cou

nter

RE

C G

OS

part

3 (

MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 58)

Fig. 27 Measurement counter REC GOS part 4 (MN3510EU10MN_0002 Traffic Data Recording, 59)

Fig.

28

Tra

ffic

dat

a co

llect

ion

(MN

3510

EU

10M

N_0

002

Tra

ffic

Dat

a R

ecor

ding

, 63)

Fig.

29

Ove

rvie

w o

f th

e nu

mbe

r of

traf

fic

mea

sure

men

t job

s (M

N35

10E

U10

MN

_000

2 T

raff

ic D

ata

Rec

ordi

ng, 6

5)

O p t i m i z a t i o n K n o w H o w

S P O T S

N e t w o r k A n a l y s i s / O p t i m i z a t i o n

Siemens

Support for Planning,

Operation & Maintenance and Traffic

Analysis.

Fig. 1 Network analysis/optimization with SPOTS (MN2534EU10MN_0002 SPOTS Functions, 3)

NE 1 NE 2 NE 3 NE n

Data CollectionDCN (X 25)

MeasurementData

SPOTS: Application

PMC

PMS

SPOTS: Data Base

Client Compoment

Fig.

2 P

erfo

rman

ce a

naly

sis

(MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 5)

Fig.

3 S

ingl

e se

rver

con

figu

ratio

n (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 7

)

Node 1Node 2

Node 3

North

Node 4Node 5

Node 6

South

Middle

Middle E

Node 10 Node 9

Middle W

Node 7 Node 8

Network

Fig. 4 Network management domains (MN2534EU10MN_0002 SPOTS Functions, 9)

Root

- John- PMadmin

SIEMENS

- Kevin- PMuser

- Steven- PMadmin

North

Middle

MiddleE - Karl- PMuser

- Marie- PMuser

SIEMENS

MiddleW

- Julie- PMadmin

SIEMENS

South

SIEMENS

SIEMENS

SIEMENS

Fig. 5 User access control (MN2534EU10MN_0002 SPOTS Functions, 11)

Network Element NEDaily / Cyclic / Log / Counter - Files

Switch Commander SC: PDCPerformance Data Collector Services

CFS Common File StoreTransmission Files

SPOTSPMS Command: Collector

SASPM - Data Files (xxx.spf)

SPOTSData Loading

Data Base Management SystemORACLE

Fig. 6 Data collection and loading (MN2534EU10MN_0002 SPOTS Functions, 13)

SPOTS

Fig. 7 Performance data collector (MN2534EU10MN_0002 SPOTS Functions, 15)

Name ofTransmission File

PM_QOSALARM PM_QOS file

PM_SCANREPQOS PM_SCANREP file and filtering FirstAndIntervalCurrentData

PM_SCANREP PM_SCANREP file (at NE) with all scan report records or alternatively to

PM_SCANREP, if not all measurement data are requested for further evaluation

TS_MPLOAD PM_SCANREP file and filtering performance data of MP_LOAD measurements

TS_MTP PM_SCANREP file and filtering performance data of MTP measurements

TS_SCCP PM_SCANREP file and filtering performance data of SCCP measurements

TS_ATM PM_SCANREP file and filtering performance data of ATM measurements

MT_GPRS PM_SCANREP file and filtering performance data of GPRS specific measurements

MT_CS PM_SCANREP file and filtering performance data of CS specific measurements

Transmission of:

Fig. 8 Names of Q3 transmission files (MN2534EU10MN_0002 SPOTS Functions, 17)

Fig. 9 Configuration menu for data collection (MN2534EU10MN_0002 SPOTS Functions, 17)

Fig.

10

File

nam

e sy

ntax

for

FT

AM

tran

smis

sion

file

s (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 1

9)

Detailed Data (96 x 15 Minutes Interval per day) from 00:15 to 24:00

1 2 3 4 5 . . . . 91 92 93 94 95 96

Daily Totals

Sum of 96 Intervals

1 . . . . 9611:00 - 12:00

45 46 47 48 . . . .

Daily Peak

Peak Busy Hour on day

PBH: Mo PBH: Tu PBH: We PBH: Th PBH: Fr

Max Peak

Maximum (e.g. from Mo to Fr)

Fig.

11

Dat

a or

gani

zatio

n (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 2

1)

Fig. 12 User Login window is presented over the SPOTS client splash screen (MN2534EU10MN_0002 SPOTS Functions, 25)

Fig. 13 User login (MN2534EU10MN_0002 SPOTS Functions, 25)

Fig.

14

SPO

TS

mai

n w

indo

w (

MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 27)

Fig.

15

Nod

e co

nfig

urat

ion

(MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 31)

Fig. 16 Software version (MN2534EU10MN_0002 SPOTS Functions, 33)

Fig. 17 Resource deletion (MN2534EU10MN_0002 SPOTS Functions, 35)

Fig.

18

Dom

ains

con

figu

ratio

n (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 3

7)

Fig. 19 Data loading (MN2534EU10MN_0002 SPOTS Functions, 39)

Fig.

20

Dat

a de

letio

n (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 4

1)

Fig.

21

Mak

e hi

stor

y (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 4

3)

Fig.

22

Dat

a ag

greg

atio

n (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 4

5)

MSC SSNC

NE NE

trf - format Q3 format

PeDaCo

trf - format spf - format

SPOTSCommand

SPOTSWindow

TRFFileConvertertrf ==> spf

DbLoaderData

Loading

DbAggregatorData

Aggregation

DbCalcStat

MkHistoryMake

History

DbRemoverData

Deletion

Reporter

Deletion of old traffic data records

Generation of reportsin HTML format

Loading of detailed datainto SPOTS data base

Optimization ofdata base access

Aggregation of detaileddata into higher

granularity ( 5 ==> 15 )

Generation of historydata log

File Transfer NE ==> SPOTS Server NE ==> PeDaCo ==> PMS

SPOTS PMS

Convert trf-format tospf-format

Fig.

23

Tra

ffic

dat

a ha

ndlin

g (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 4

7)

Function: Collector

-h provides detailed help information.

-e NMS environment from which data are collected.

The possible values are:• SC (Switch Commander);• RC (Radio Commander), used for both GERAN (BSS) and UTRAN

environments — they can be distinguished only by the RC name (see -n switch);• OMCB (OMC-B).

-n Name of the NMS platform from which data are collected. It must be followed either by an NMS name registered in

$SPOTS_DIR/data/element_managers.cfg (refer to the SPOTS Installation Guide

(for information on this file and on the setting of the SPOTS_DIR environment variable) or by the keyword ALL, to select all registered NMSs that belong to the environment specified by the -e switch.

-t Used only with the -e SC option (SC environment). The usage of the –t switch in this environment is mandatory and it specifies the type of data to be collected. The possible options are:• q3 files with data retrieved from the node Q3 interface (i.e. dataproduced by Q3 scanners);• cyclic files produced by REC jobs on the node (cyclic files);• daily files produced by REC jobs on the node (daily files);• snmp files with data from the node SNMP MIBs, uploaded to the SC using the SNMP protocol;• ftp files with data from the node SNMP MIBs, for the specific case of SP:BSSGP MIBs, which

are periodically dumped to files anduploaded to the SC using FTP protocol.

-g Used only with the -e OMCB option (OMC-B environment). The usage of the -g switch in this environment is mandatory and it specifies the time interval of the data to be collected. The possible options are:

1, 2, 3, 4, 5 for 5, 15, 30, 60 Minutes and the last for 24 hours. Fig.

24

PMS

com

man

d: C

olle

ctor

(M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 4

9)

Fig. 25 File type directory and extension (MN2534EU10MN_0002 SPOTS Functions, 51)

Fig. 26 Ad-hoc report input window (MN2534EU10MN_0002 SPOTS Functions, 57)

Fig. 27 Ad-hoc report: Object and counter selection (MN2534EU10MN_0002 SPOTS Functions, 59)

Fig. 28 Selection of objects instances (MN2534EU10MN_0002 SPOTS Functions, 61)

Fig. 29 Object filtering (MN2534EU10MN_0002 SPOTS Functions, 63)

Fig. 30 Counter selection (MN2534EU10MN_0002 SPOTS Functions, 65)

Fig. 31 Report properties - general (MN2534EU10MN_0002 SPOTS Functions, 67)

Fig. 32 Report properties - appearance (MN2534EU10MN_0002 SPOTS Functions, 69)

Fig. 33 TGRP report – detailed 15 min (MN2534EU10MN_0002 SPOTS Functions, 71)

Fig. 34 Ad-hoc TGRP report - peak busy hour (MN2534EU10MN_0002 SPOTS Functions, 73)

Exchange

TGNO 1

TGNO 2

TGNO 3

SET of

Objects

CC_IC CC_OO CS_IC_WA CS_OO_WA

SET of

Counters

Virtual Conters VC: TG_CC = TGRP:CC_IC + TGRP:CC_OO

Fig. 35 PM entities (MN2534EU10MN_0002 SPOTS Functions, 75)

GW 31

GW 33

GW 32

GW 21

GW 22

GW 11

GW 12

Object Class:

EXCHOC, TGRPOC

SO NW_1

SO NW_2

SO NW_3

OC = Object Class SO = Set of Objects

NW = Network GW = Gateway

Fig.

36

Set o

f ob

ject

s (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 7

7)

Fig. 37 Define name and comment (MN2534EU10MN_0002 SPOTS Functions, 78)

Fig. 38 Select objects (MN2534EU10MN_0002 SPOTS Functions, 79)

Fig. 39 Save set of objects (MN2534EU10MN_0002 SPOTS Functions, 79)

TgrpTrafficMetrics = VC!TG_TC_IC, VC!TG_TC_OO,VC!TG_MHT,VC!TG_ASR

Note:Virtual Counters (VC) are arithmetical expressions.Before using these VC’s in a set of counters (SC), the VC must be defined first.

TgrpCallMetrics = TGRP:CC_IC, TGRP:CC_OO,

TGRP:CS_WA_IC,TGRP:CS_WA_OO

Fig. 40 Set of counters (MN2534EU10MN_0002 SPOTS Functions, 81)

Fig. 41 Define name and comment (MN2534EU10MN_0002 SPOTS Functions, 82)

Fig. 42 Measurement and counter selection (MN2534EU10MN_0002 SPOTS Functions, 83)

Fig. 43 Save set of counters (MN2534EU10MN_0002 SPOTS Functions, 83)

VCname: TG_TVVCobject_class: XTPSGVCdescription:Traffic Volume of a Trunk GroupVCexpression: TGRP:TV_OO + TGRP:TV_ICVCunit: ERL.S VCname: TG_CCVCobject_class: XTPSGVCdescription: Carried Calls of a Trunk GroupVCexpression: TGRP:CC_OO + TGRP:CC_ICVCunit: NR VCname: TG_MHTVCobject_class: XTPSGVCdescription: Mean Holding Time of a Trunk GroupVCexpression: TG_TV / TG_CCVCunit: SEC VCname: TG_TCVCobject_class: XTPSGVCdescription: Traffic Intensity of a Trunk GroupVCexpression: TG_TV / GRANULARITY()VCunit: ERL Fi

g. 4

4 V

irtu

al c

ount

ers

(cal

cula

ted

vari

able

s) (

MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 85)

Fig. 45 Define name, comment, class and counters (MN2534EU10MN_0002 SPOTS Functions, 86)

Fig. 46 Select measurement and counters (MN2534EU10MN_0002 SPOTS Functions, 87)

Fig. 47 Define expression (MN2534EU10MN_0002 SPOTS Functions, 87)

Fig. 48 Save virtual counters (MN2534EU10MN_0002 SPOTS Functions, 88)

SPBH Max Peak The report focuses on the maximum peak hour for the specified date interval. Only one sample is presented for each selected object.This report type uses the history log.

 

SPBH Daily Peaks The report focuses on the peak hour for each day on the specified date interval. One sample per day is presented for each selected object. This report type uses the history log.

 

DTOT The report focuses on the total amounts for each day on the specified date interval. This report type uses the history log.

 TEVL The report focus on the detailed time evolution, based on 15min samples,

for the specified date interval. This report type uses the detailed log.

 

Fig. 49 Predefined reports (MN2534EU10MN_0002 SPOTS Functions, 89)

Fig. 50 Pre-defined report: CP load SPBH daily peaks (MN2534EU10MN_0002 SPOTS Functions, 91)

Fig. 51 MSC call flow part 1 (MN2534EU10MN_0002 SPOTS Functions, 92)

Fig. 52 MSC call flow part 2 (MN2534EU10MN_0002 SPOTS Functions, 93)

Fig. 53 Mobile terminating call analysis: MALAP (MN2534EU10MN_0002 SPOTS Functions, 95)

Fig. 54 Mobile terminating call analysis: MSALM (MN2534EU10MN_0002 SPOTS Functions, 95)

Fig. 55 Handover analysis (MN2534EU10MN_0002 SPOTS Functions, 97)

Fig. 56 TGRP load type report: SPBH daily peaks (part 1) (MN2534EU10MN_0002 SPOTS Functions, 99)

Fig.

57

TG

RP

load

type

rep

ort:

SPB

H d

aily

pea

ks (

part

2)

(MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 101

)

Fig. 58 TGRP load max SPBH part 1 (MN2534EU10MN_0002 SPOTS Functions, 102)

Fig.

59

TG

RP

load

max

SPB

H p

art 2

(M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 1

03)

Fig. 60 Reports editor (MN2534EU10MN_0002 SPOTS Functions, 107)

// 1 Input Variables// Input variables of a report call // 2 Request Sectionrequest tgrp_request{ classname = “TGRPOC”; objects = $OBJECTS; counters = “TGRP:CC_IC;TGRP:CC_OO”; periodbegin = $PERIOD_BEGIN; periodend = $PERIOD_END; granularity = HOUR_QUARTERLY; datatype = DETAILED;} // 3 Result Sectionresult tgrp_result{} // 4 Method Sectionmethod CallsCarried_BW (column cc_ic, column cc_oo) return column{ return cc_ic + cc_oo;}  // 5 Report Sectionreport r1(){ int i; column c_aux; for ( i = 0; i < tgrp_request.getNumberOfObjects(); i=i+1 ) { c_aux=CallsCarried_BW (tgrp_request.getColumn(“TGRP:CC_IC”,i), tgrp_request.getColumn(“TGRP:CC_OO”,i));  tgrp_result.addColumn(“CC_BW”, tgrp_request.getObjectReference(i), “Nr”, c_aux.getResultColumn()); }}

Fig.

61

Bas

ic e

xam

ple

for

SRL

sou

rce

code

(M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 1

09)

CC_ICCC_OOCS_WA

ICCS_WA

OO

Mo

Tu

We

Th

Fr

Z

Y

X

i = 1: TGNO 02i = 0: TGNO 01

Z = Objects Sheet (e.g. TGNO)Y = Time Sample Row (e.g. Monday)X = Counter Columns (e.g. Calls Carried CC_IC)

Fig.

62

Req

uest

for

dat

abas

e (M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 1

11)

method CallsCarried_BW (column cc_ic, …etc.)  {return cc_ic + cc_oo;} --------------------------------------------------------------------------------------------------report r1(){ c_aux = CallsCarried_BW (rp_request.getColumn …etc.)

Fig. 63 Call of method "CallsCarrie_BW" (MN2534EU10MN_0002 SPOTS Functions, 112)

TGRP:FRA0T0

Day CC_IC CC_OO

Mo 317 6 813

Tu 256 4 705

We 218 4 631

Th 250 4 137

Fr 59 4 988

Method:´CallsCarried_BW

Return: CC_BW = CC_IC+CCOO

Day CC_BW

Mo 7 130

Tu 4 961

We 4 849

Th 4 387

Fr 5 047

c_aux = return column Fig.

64

Met

hod:

Cal

lsC

arri

ed_B

W (

MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 113

)

Fig.

65

Tru

nk g

roup

rep

ort f

or C

C_B

W (

MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 115

)

for ( i = 0; i < tgrp_request.getNumberOfObjects(); i=i+1 ){ // Begin of Loop

// NumberOfObjects = 2

} // End of Loop

Fig. 66 Loop for number of objects (MN2534EU10MN_0002 SPOTS Functions, 117)

DATA CUBEx = Counter: CC_IC, CC_OO

y = Date:2001 – 03 – 18 to 22

z = TGNO (Index i = 0): FRA0T0

1. Copy CC_IC from Data Cube to auxiliary variable a_aux

c_aux = tgrp_request.getColumn(“TGRP:CC_IC”, i ) ;

2. Add Column to Output Sheet

tgrp_result.addColumn(“CC_IC”, tgrp_request.getObjectReference(i), “Nr”, c_aux.getResultColumn() );

Fig.

67

Out

put s

heet

for

tabl

e fo

rmat

(M

N25

34E

U10

MN

_000

2 SP

OT

S Fu

nctio

ns, 1

19)

Create a file with the report source code and save it :

e.g. C:\Custom \ Reports \ Source \ <file name>.sc

Compile source code:

Reports Editor Reports Compile

If no error exist in the source code, then proceed

Insert new report to graphical user interface:

Reports Editor Reports Add Report to Server

Fig. 68 Process of creation of a new report (MN2534EU10MN_0002 SPOTS Functions, 121)

// Training: TGRP Report // Trunk Group Load SPBH Report // Source File: TGRP_MN2534.sc request tgrp_request{ classname = "TGRPOC"; objects = $OBJECTS; counters = "TGRP:CONLI;TGRP:BLOLI;TGRP:TBLOLI;TGRP:ATBT; TGRP:CC_IC;TGRP:CC_OO;TGRP:TV_IC;TGRP:TV_OO"; periodbegin = $PERIOD_BEGIN; periodend = $PERIOD_END; granularity = DAILY; datatype = HISTORICAL_SPBH;}

// Result expectedresult tgrp_load_spbh_daily_result { // empty }

Fig. 69 Request and result section (MN2534EU10MN_0002 SPOTS Functions, 123)

method CalcLoss(column TrafCarr, column ServLines) return column{

column c_Loss;double val;int i;

 // initializec_Loss = TrafCarr;c_Loss = NO_DATA_VALUE;

 for (i=0; i < TrafCarr.nelem() ; i=i+1){

if ((TrafCarr[i]==0)||(ServLines[i]==0)) c_Loss[i]=0;else{

val = traffic_lib.Loss(TrafCarr[i], ServLines[i]);if ( val != NO_DATA_VALUE) c_Loss[i] = val * 100;

}}

 return c_Loss;

  }

Fig. 70 Calculate loss B (MN2534EU10MN_0002 SPOTS Functions, 125)

 report r1(){

column c_TC, c_SL, c_CC_BW, c_MHT, c_ATBR, c_ServLines, c_B;int i, j;bool flag_control;

 for ( i = 0; i < tgrp_request.getNumberOfObjects(); i=i+1 )

{ 

c_CC_BW = tgrp_request.getColumn("TGRP:CC_IC",i) + tgrp_request.getColumn("TGRP:CC_OO",i);

 c_SL = ServLines( tgrp_request.getColumn("TGRP:CONLI", i),

tgrp_request.getColumn("TGRP:BLOLI", i), tgrp_request.getColumn("TGRP:TBLOLI", i) );

 c_TC = (tgrp_request.getColumn("TGRP:TV_IC",i) + tgrp_request.getColumn("TGRP:TV_OO",i)) / HOURLY;

 c_MHT = (tgrp_request.getColumn("TGRP:TV_IC",i)

+ tgrp_request.getColumn("TGRP:TV_OO",i)) / c_CC_BW; 

c_ATBR = (tgrp_request.getColumn("TGRP:ATBT",i)) / HOURLY * 100; 

c_B = CalcLoss(c_TC, c_SL);

Fig. 71 Report section (5) part 1 (MN2534EU10MN_0002 SPOTS Functions, 127)

flag_control = false;for ( j = 0; j < c_CC_BW.nelem(); j=j+1 ){if (c_CC_BW[j] > 0) flag_control = true;}

 if (flag_control){

 tgrp_load_spbh_daily_result.addColumn("ServLines",tgrp_request.getObjectReference(i), "Nr", c_SL.getResultColumn());

tgrp_load_spbh_daily_result.addColumn("TrafCarr", tgrp_request.getObjectReference(i), "Erl", c_TC.getResultColumn());

tgrp_load_spbh_daily_result.addColumn("MHT", tgrp_request.getObjectReference(i), "sec",c_MHT.getResultColumn());

 tgrp_load_spbh_daily_result.addColumn("ATBR",tgrp_request.getObjectReference(i), "%",c_ATBR.getResultColumn());

 // tgrp_load_spbh_daily_result.addColumn("Loss B",// tgrp_request.getObjectReference(i), "%", c_B.getResultColumn());

}}}

Fig. 72 Report section (5) part 2 (MN2534EU10MN_0002 SPOTS Functions, 129)

• Date Selected Measurement Period • Time Begin of Peak Busy Hour• Object Exchange ID and Trunk Group Name

• ServLines (Nr) Number of Lines in Service• TraffCarr (Erl) Traffic Carried• MHT (sec) Mean Holding Time• ATBR (%) All Trunk Busy Relativ

Parameters derived from Report INPUT

Measurement Counters

Fig. 73 Report parameters (MN2534EU10MN_0002 SPOTS Functions, 130)

Fig. 74 TGRP report training (MN2534EU10MN_0002 SPOTS Functions, 131)

Fig.

75

STA

RT

of

user

rep

orts

: TG

RP_

Tra

ffic

_SPB

H (

MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 132

)

Fig. 76 Trunk group report at peak busy hour (MN2534EU10MN_0002 SPOTS Functions, 133)

request tgrp_request{ classname = "TGRPOC"; objects = $OBJECTS; counters = "TGRP:CONLI;TGRP:BLOLI;TGRP:TBLOLI;TGRP:TV_IC; TGRP:TV_OO;TGRP:CC_IC;TGRP:CC_OO"; periodbegin = $PERIOD_BEGIN; periodend = $PERIOD_END; granularity = HOUR_QUARTERLY; datatype = DETAILED;} 

 

// Result expectedresult TGRP_TRAFFIC_DAILY { }

Fig. 77 Request and result section (MN2534EU10MN_0002 SPOTS Functions, 135)

method CalcLoss(column TrafCarr, column ServLines) return column{

column c_Loss;double val;int i;

 // initializec_Loss = TrafCarr;c_Loss = NO_DATA_VALUE;

 for (i=0; i < TrafCarr.nelem() ; i=i+1){

if ((TrafCarr[i]==0)||(ServLines[i]==0)) c_Loss[i]=0;else{

val = traffic_lib.Loss(TrafCarr[i], ServLines[i]);if (( val != NO_DATA_VALUE)&& (TrafCarr[i] < ServLines[i]))

c_Loss[i] = val * 100;else c_Loss[i] = 100;

}}return c_Loss;

}

Fig. 78 Method section (calculate loss B) (MN2534EU10MN_0002 SPOTS Functions, 136)

Fig. 79 Method section (calculate traffic offered) (MN2534EU10MN_0002 SPOTS Functions, 137)

report r1(){column c_SL, c_B_BW, c_TO_BW, c_TC_BW;

column c_aux;int i;

 for ( i = 0; i < tgrp_request.getNumberOfObjects(); i=i+1 ){c_SL = tgrp_request.getColumn("TGRP:CONLI",i)-

tgrp_request.getColumn("TGRP:TBLOLI",i)- tgrp_request.getColumn("TGRP:BLOLI",i); TGRP_TRAFFIC_DAILY.addColumn("N_SL", tgrp_request.getObjectReference(i), "Erl", c_SL.getResultColumn()); 

// Traffic Bothwayc_TC_BW = (tgrp_request.getColumn("TGRP:TV_IC",i) +

tgrp_request.getColumn("TGRP:TV_OO",i)) / HOUR_QUARTERLY;

c_aux = c_TC_BW;TGRP_TRAFFIC_DAILY.addColumn("TC_BW",

tgrp_request.getObjectReference(i), "Erl", c_aux.getResultColumn());

// ini_valuesc_TO_BW = c_TC_BW;

// calculate Loss Bc_B_BW = CalcLoss (c_TC_BW, c_SL);

// Traffic offered TOc_TO_BW = TrafOff (c_TC_BW, c_B_BW, c_SL);

TGRP_TRAFFIC_DAILY.addColumn("TO_BW", "TGRPOC", tgrp_request.getObjectReference(i), "Erl", c_TO_BW.getResultColumn()); 

// Loss B TGRP_TRAFFIC_DAILY.addColumn("Loss B", tgrp_request.getObjectReference(i), "%", c_B_BW.getResultColumn() );

}} Fi

g. 8

0 R

epor

t sec

tion

(mai

n pr

ogra

m)

(MN

2534

EU

10M

N_0

002

SPO

TS

Func

tions

, 138

)

N’ Trunks

Traffic offered

Traffic carried

Blocking Rate B

Fig. 81 Trunk group report traffic (detailed data) (MN2534EU10MN_0002 SPOTS Functions, 139)

Fig. 1 SPOTS reports (MN2534EU10MN_0002 Traffic Reports, 3)

Start Date: Mo 05.02.2001

End Date: Mo 05.02.2001 CALLP Load Total Load

Date Time Object CP:TC_CP(mErl) CP:TC_TI(mErl) CP:OS, O&M (mErl)

2001-02-05 19:15 MSLAP:BAPM 466.8 826.3 359.5

2001-02-05 19:15 MSLAP:BAPS 754.8 806.5 51.8

2001-02-05 19:15 MSLAP:CAP0 752.0 803.5 51.5

2001-02-05 19:15 MSLAP:CAP1 754.0 806.0 52.0

2001-02-05 19:15 MSLAP:CAP2 755.3 807.3 52.0

2001-02-05 19:15 MSLAP:CAP3 752.8 804.5 51.8

2001-02-05 19:15 MSLAP:CAP4 755.5 807.3 51.8

2001-02-05 19:15 MSLAP:CAP5 759.8 811.5 51.8

2001-02-05 19:15 MSLAP:CAP6 760.5 812.5 52.0

2001-02-05 19:15 MSLAP:CAP7 753.3 805.0 51.8

2001-02-05 19:15 MSLAP:CAP8 755.5 807.5 52.0

2001-02-05 19:15 MSLAP:CAP9 757.0 809.0 52.0

Sum = 8777.0 mErl

Average Load = 731.4 mErl

Load A (NL) = 670.0 mErl

CALLP Usage = 109.2%

Fig. 2 CP113 load (table format) (MN2534EU10MN_0002 Traffic Reports, 5)

Fig. 3 CALLP load BAPM, BAPS and CAP's (MN2534EU10MN_0002 Traffic Reports, 6)

Fig. 4 CALLP load (average) (MN2534EU10MN_0002 Traffic Reports, 7)

Fig. 5 MSC call flow on SPBH (part 1) (MN2534EU10MN_0002 Traffic Reports, 9)

Fig. 6 MSC call flow on SPBH (part 2) (MN2534EU10MN_0002 Traffic Reports, 10)

Fig. 7 Ad hoc report for mobile originating calls (MN2534EU10MN_0002 Traffic Reports, 11)

Fig. 8 MSC handover report (total HO) (MN2534EU10MN_0002 Traffic Reports, 13)

Fig.

9 T

runk

gro

up r

epor

t - c

alls

and

traf

fic

at P

BH

(pa

rt1)

(M

N25

34E

U10

MN

_000

2 T

raff

ic R

epor

ts, 1

7)

Fig.

10

Tru

nk g

roup

rep

ort -

cal

ls a

nd tr

affi

c at

PB

H (

part

2)

(MN

2534

EU

10M

N_0

002

Tra

ffic

Rep

orts

, 18)

Trunk Group Load

0

10

20

30

40

50

60

70

80

90

100

00:30 02:30 04:30 06:30 08:30 10:30 12:30 14:30 16:30 18:30 20:30 22:30

Time

Traffic [Erl]

0

10

20

30

40

50

60

70

80

90

100

N' Available

TGRP xxxx TC:I + TC:O

TGRP xxxx TC:I

TGRP xxxx TC:O

Number of Trunks

Fig. 11 Traffic carried and mean holding time (trunk group) (MN2534EU10MN_0002 Traffic Reports, 19)

Transit1

Dest 1

Trunk GroupMeasurement

Transit2

Dest 2

Dest n

Orig

1

Orig

2

Orig

n

DestinationMeasurement

Transit3

Fig.

12

Des

tinat

ion

load

mea

sure

men

t (R

EC

DE

ST)

(MN

2534

EU

10M

N_0

002

Tra

ffic

Rep

orts

, 27)

Part 1

GENERAL CALLS TRAFFIC STA-TISTICS

CCS Part1

Code LAC Orig. Zdig PBH CC(NR)

CSWA(NR)

TC(Erl)

TCWA(Erl)

ASR(%)

MHT(Sec)

CCSCCS7CF

(NR)

CCSCONG(NR)

CCSINCLDIAL(NR)

6512 @ @ @ 11:00 9 4 0.76 0.71 44.4 305 0 0 0

6517 @ @ @ 12:45 24 12 0.99 0.74 50.0 149 0 3 1

6524 @ @ @ 00:45 34 30 1.99 1.97 88.2 211 0 0 2

7324 @ @ @ 14:30 157 139 6.69 4.66 89.5 153 0 0 3

Part 2

CCS CCU LNP

CCSEXT

TECHIrreg.(NR)

CCSINT

TECHIrreg.(NR)

CCSLINKFAIL(NR)

CCSOper.REL(NR)

CCSRELOrig.ETE(NR)

CCSSUBBUSY(NR)

CCSunall.NUM(NR)

CCSun-

answ.(NR)

CCUCONG(NR)

CCUNM

CodeBlock(NR)

CCUNMNTRKBLK(NR)

CCUTECHIrreg.(NR)

CCLQA(NR)

CCLQS(NR)

0 0 0 0 0 1 1 3 0 0 0 0 0 0

0 0 0 0 0 0 0 6 0 0 0 1 0 0

0 0 0 0 0 0 0 1 0 0 0 0 0 0

0 0 0 0 0 6 2 12 0 0 0 1 0 0

Fig.

13

Des

tinat

ion

repo

rt (

MN

2534

EU

10M

N_0

002

Tra

ffic

Rep

orts

, 29)

1. Interval 2. Interval 3. Interval 4. IntervalPBH

T = 3600 s

CC

(NR)132 291 538 119 1080

CC_WA

(NR)38 93 309 168 608

TC

(Erl)14.7 32.3 59.8 13.2 30.0

TC_WA

(Erl)6.8 16.5 54.9 29.9 27.0

ASR

(%)28.8 % 31.9 % 57.4 % 141.2 % 56.3 %

ASR > 100 %

Fig.

14

Des

tinat

ion

load

(M

N25

34E

U10

MN

_000

2 T

raff

ic R

epor

ts, 3

1)

Fig. 15 CCNC signaling link load report (MN2534EU10MN_0002 Traffic Reports, 41)

Number ATM Octets = [ N´Octets + N´PDUs * ( AAL5 + Padding )] * 53 / 49

ATM Load Factor = Number ATM Octets / N´Octets

HSL Link Load = [( N´Octets * ATM Load Factor / 53) + Status&Polling] / 4 300

Example:

N'PDU = 15.38 Signaling messages received per Second

N' Octets = 146.98 Octets received per SecondNumber ATM Octets = [ 146.98 + 15.38 * ( 12 + 23.5 )] * 53 / 49 = 765.15

ATM Load Factor = 765.15 / 146.98 = 5.21

HSL Link Load = [( 146.98 * 5.21 / 53 ) + 20 ] / 4 300 * 1000 = 8.01 mErl

Fig. 16 Formulas for HSL load (MN2534EU10MN_0002 Traffic Reports, 42)

Fig. 17 SSNC signaling link load report (MN2534EU10MN_0002 Traffic Reports, 43)