Traffic Report Siemens

Traffic Report

Inhalt
1 MSC Report (Mobile Switching Center) 3
1.1 CP Report 4
1.2 Call Flow 6
1.3 Procedure Runtimes and Subscriber Load 8
1.4 Handover 10
1.5 Location Update 10
1.6 Handover Report 12
2 Exchange Data 15
2.1 GOS Report 16
2.2 Explanation of the GOS Report Counters (EWSD Vers.12) 20
3 Trunk Group Data 25
3.1 TGRP Report 26
3.2 Explanation of the TGRP Report Counter 30
4 Destination Area Report 35
4.1 DEST Report 36
4.2 DEST Parameters 38
4.3 Analysis of the Destination Data 40
4.4 Explanation of the DEST Report Counter 42
5 C7 Link Load Report 49
5.1 Feature Description 50
5.2 Description of the Evaluation Results 52

MN2534EU07AL_03
1
 Siemens Traffic Report

2 MN2534EU07AL_03
Traffic Report Siemens

1 MSC Report (Mobile Switching Center)

Ä...SPOTS Report Generator offers a set of pre-defined

reports, allows for fast customisation and the definition of
completely new ones.

ü Pre-defined Reports are designed for the

instant use of SPOTS and answer the most
common network operator needs.
ü Generation of user-defined Reports
ü Automatic execution by scheduling
ü Office Integration
ü Web Access
ü Data warehouse Integration

Fig. 1 SPOTS Reports

MN2534EU07AL_03
3
 Siemens Traffic Report

1.1 CP Report
The CP report shows the load of the coordination processors CP 113. The table and
the bar chart show the load of the individual processors (BAPM, BAPS,
CAPO...CAP5).

The processor load comprises of the following areas:

BAPM: l Operational system
l Service- and maintenance jobs
l Switching technology

BAPS, l Operational system

BAPS, l Switching technology
CAP0 ...CAP5:

The "Callp Load" only contains the switching information load, that is in the hours of
the night this counter is able to go towards zero, if only a small number of
connections are switched through.
The "Callp Load" of the BAPM always lies lower, because all of the administrative
tasks are executed exclusively from this processor. The switching information jobs
are shared between the remaining processors. If there are no administrative jobs,
then the BAPM also executes the switching jobs.

The proportional utilization of the switching computer capacity is worked out with the
following formula:

Callp Load [%] = Callp Load Average / 670 * 100%

Example: Callp Load = 154 mErl

Callp Load = 154 mErl / 670 mErl * 100% = 22.99%

Note: The average value of 670 mErl* of the processor load corresponds to
100% "Callp Load" è Normal Load

4 MN2534EU07AL_03
Traffic Report Siemens

Fig. 2 CP report

MN2534EU07AL_03
5
 Siemens Traffic Report

1.2 Call Flow

The MSC report in the form of a call flow provides information about the distribution
of call within a mobile switching center (MSC). The traffic counters are divided
according to traffic types:
MORTR: Mobile Originating Traffic
MICTR: Mobile Incoming Traffic

MOUT_NOT_PLMN: Mobile Outgoing not PLMN (PSTN or others)

MOUT_PLMN: Mobile Outgoing (own PLMN)
MTERM: Mobile Terminating Traffic
MTRAN: Mobile Transit Traffic

The above mentioned counters specify the origin and the destination respectively of
the connection. During the connection setup, different reasons can cause a
disconnection such as:
l Calling subscriber releases
l Blockage in the radio network
l Blockage in the fixed network
l Subscriber busy or not contactable
l No service authorization etc.

In opposite example 85% of the connections were switched through. The MSC report
gives a first overview of how the connections and indications of eventual problems
are distributed within the network.
The exact reason is not always clearly identified from the measurement. Further
measurements e.g. trunk measurements and also cell measurement, supply further
details which lead to solving the problem.
The following causes can cause to premature disconnection:
l Irregular customer behavior
l False network dimensioning (fixed network, POI)
l Insufficient full coverage within the radio network
l Data base software or hardware errors in the system
l Protocol errors in the signaling program
l Breakdown of the transmission routes

6 MN2534EU07AL_03
Traffic Report Siemens

Fig. 3 MSC report

MN2534EU07AL_03
7
 Siemens Traffic Report

1.3 Procedure Runtimes and Subscriber Load

The system's performance is characterized by the following runtimes and traffic
values:
l Mean Allocation Time for a Traffic Channel
The runtime is measured from arrival of the message “SETUP (MSISDN)“ to
acknowledgment “ASS_COMPL“. These times are between 1.5 and 3 seconds.
l Mean Runtime for Location Update (MSC – VLR) The
processing time between CR ( Compl._L3_INFO [LOC_UPD_REQ] ) and
LOC_UPD_ACCEPTED produces the runtime for location update. Measurements
have shown that the times are shorter with a stand alone HLR than with an
integrated HLR. In the latter case, the coordination processor must also carry out
call-processing tasks for the location update.

l Average Runtime for Paging

The time between “STARTED_PAGING_PROC“ and “RECEIVED_PAG_RESP“
depends upon the availability of the subscriber. This time becomes longer as soon
as the repetitions for paging (STARTED_PAG_RETRY_PROG) increase.

l Traffic per Subscriber

The standard value for mobile subscribers is 25 mErl. This value depends on the
region's tariff structure. If the difference between a fixed network and a mobile
network is low, then values of up to 50 mErl can be achieved.

l Calls per Subscriber

The average value is 1.3 calls per hour and the mean holding time is 70 seconds.
The values of this measurement are higher because this MSC is located in a
business area and a large volume of traffic is handled via the mobile network.

8 MN2534EU07AL_03
Traffic Report Siemens

1. T im e fro m S ET UP Mes sa g e to A SS _C O M

TIME _ C A L L _S E T _U _S E R V 1 4 3 .4 4 4
tm T C H-A llo c a tio n = = = 1 ,6 9 Sec
N U M_C A L L _S E T _U P _C ON T R IB 8 4 .8 1 5

2. T im e fro m L o c a tio n Up d ate R eq u es t to L o c atio n UP d ate a cc ep ted

TIME _L U P _S E R V 5 4 .8 8 3
tm L o c a tio n Up d a te = = = 0 ,9 2 Sec
N U M_L U P _C ON TR IB 5 9 .5 0 8

3. T im e fro m S ta rt P a g in g to R ec e iv e d P a g in g R es p o n s e

T R A F F _V O L _S U C C _ P A GIN G 1 .6 6 3 .2 0 5
tm P a g in g = = = 2 ,1 9 Sec
R E C E IV E D _ P A G_ R E S P 3 7 .9 8 3

4. T raffic p er Su b s c rib er [E rl]

Traffic MOR T R + T raffic MT C 1 .7 6 0

T r a ffic p e r S u b . = = = 0 ,0 4 4 E rl
N u m b er o f ac tive S u b s crib ers 3 9 .5 6 8

5. C a lls p er Su b s c rib er [B HC A] M HT = 6 0 ,1 9 Sec

C alls MOR T R + C alls M TC 1 0 5 .2 9 3

C a lls p e r S u b . = = = 2 ,6 6 B HC A
N u m b er o f ac tive S u b s crib ers 3 9 .5 6 8

Fig. 4 Calculation of Mean Processing Time and Subscriber Load

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

MN2534EU07AL_03
9
 Siemens Traffic Report

1.4 Handover

MSC A MSC B

BSC 1 INTRA BSC 2 INTER BSC 3

MSC HO MSC HO

Fig. 5

This report only contains the handovers which are controlled by the MSC.
If the old and new cells are in the same MSC area (BSC 1 ==> BSC2), then this is
described as an INTRA-MSC HO. However, should the MSC area (BSC 2 ==> BSC
3) be changed, then we are talking about an INTER-MSC HO. If a HO has already
been preceded by a HO, then it is treated as a subsequent HO. Success rates of
72.3% for INTRA-MSC HO and 66.9% for INTER-MSC HO indicate a network with a
very heavy load. Additionally, the coverage of the network area is not sufficient.
Testing with detailed records is absolutely necessary in this case.

1.5 Location Update

The high number of location update requests = 69 272 indicates high GSM
subscriber mobility. This in turn causes a high signaling and computer load. The
success rate of 94.2% lies at the lower limit. Comparisons with other networks result
in values of between 95% and 98%.

10 MN2534EU07AL_03
Traffic Report Siemens

Handover Attempts
HO_ATTEMPTS (total) 22.144
Intra MSC HO 14.052
SUBSEQ_MSC_MSC_HO_MSCB 2.893
HO_MSC_MSC_OG_ATTEMPTS 5.199
7.666
SUBSEQ_MSC_MSC_HO_MSCA 2.467

Successfull INTER MSC Handover 66,9%

SUCC_MSC_MSC_HO_MSCA 5.126

Successfull INTRA MSC Handover 72,3%

SUCC_COMPLETED_HO 10.110 10.164
INTRA - HO
after SUCC_HO_SEC_
INTER-MSC
54
MSC_MSC_HO_MSCB
HO

Location Update
REQUESTS_LOCUPD 69.272

REQUESTS_LOCUPD_INTRA_VLR 22.804
REQUESTS_LOCUPD_INTER_VLR 46.468

REQUESTS_PERIODIC_LOCUPD 2.184
REQUESTS_LOCUPD_WITH_IMSI_ATT 6.636

Successfull Location Update

SUCC_REQUESTS_LOCUPD 59.036
SUCC_LOCUPD_WITH_IMSI_ATTACH 6.244
65.280 94,2%

Fig. 6 Report for Handover and Location Update

MN2534EU07AL_03
11
 Siemens Traffic Report

1.6 Handover Report

Global Cell Identity (CGI) of origin cell:

l Local Area Code of the origin cell.

LACOD (origin) = LAC_ ORIGIN
l Cell Identity code of the origin cell.
CELL ID (origin) = CELL_ID_ORIGIN

Global Cell Identity (CGI) of target cell:

l Local Area Code of the target cell.
LACOD (target) = LAC_TARGET
l Cell Identity code of the target cell.
CELL ID (target) = CELL_ID_TARGET

Evaluation results per origin cell:

Number of MSC controlled handover attempts per target cell. The background
displayed with each value follows a greyscale that implies darker backgrounds for the
target cells that receive more handovers from the origin cell. The rule uses for
brightness decision the percentage of the total handover attempts by the origin cell
that have the analyzed cell as target. The below rectangles show each percentage
interval with the respective brightness:

This rule is also shown as footnote in the report’s layout.

l Number of HO Attempts = CA_HO
l Success rate of the MSC controlled handovers performed per target cell.
Suc. Rate = 100 x CC_HO / CA_HO
Reference (default value): >80%

12 MN2534EU07AL_03
Traffic Report Siemens

xxxx@yyyy

Fig. 7 Handover Report

MN2534EU07AL_03
13
 Siemens Traffic Report

14 MN2534EU07AL_03
Traffic Report Siemens

2 Exchange Data

MN2534EU07AL_03
15
 Siemens Traffic Report

2.1 GOS Report

The GOS report offers an overview of the traffic flow at the exchange. The total traffic
volume is divided into originating traffic (OR) and incoming calls (IC). The originating
traffic is divided into internal traffic (IT) and outgoing traffic (OO), and the incoming
traffic into terminating traffic (TE) and transit traffic (TR).
The calls with SN path setup (CCS) and without SN path setup (CCU) are listed
under these counters.

Attention: According to ITU, the description "successful calls" (CCS) contains the
number of answered calls. With EWSD traffic measurement, CCS refers
to SN path setup, i.e. all calls which involve SN path setup are counted
as CCSs. This also applies if, during the further course of call setup,
there is a termination at one of the subsequent exchanges due to a busy
line or subscriber, or if other technical problems arise.

The GOS report counters are chosen in such a manner that usually approx. 95% of
the calls are contained in these counters. When there are large deviations (> 10%) in
the ELSE branch, the counters not displayed here must be examined to be able to
resolve the particular problem cases.
The graphics for the GOS report include a display of all calls (CC) and the mean
holding time (MHT) during the course of the day. This traffic load is typical for
business traffic with the peak busy hour (PBH) at 10:00 a.m. and a mean holding
time of MHT » 100 seconds. In the evening, the mean holding time increases to
between 5 and 7 minutes, which is the result of lower call charges for private traffic.

16 MN2534EU07AL_03
Traffic Report Siemens

Calls and Traffic at PBH (Daily Report)

NE: Demo1 Date: 2000/03/01

Data Type: Historical (SPBH) PBH: 10:15

CC_EXCH (NR) = 41 832 ASR TC_EXCH = 1 045.30 Erl

CCS_WA_EXCH (NR) = 25 913 62% TC_WA_EXCH = 864.23 Erl

Originating Calls
OR
CC (NR) 30 799
CC_NO_DIAL (NR) 2
CCU_INC_DIAL (NR) 54
CCU_UNALL_NUM (NR) 13
CCU_TECH_IRREG (NR) 4
CCU Else (NR) 1
Sum (NR) 74

Internal Outgoing
IT OO
CC (NR) 9 874 20 851

CCS_WA (NR) 5 754 [58%] 13 478 [46.3%]

CCS_CMP_DIAL (NR) 1 905 1 811
CCS_SUB_BUSY (NR) 609 2 775
CCS_INC_DIAL (NR) 696 823
CCS_UNALL_NUM (NR) 318 1 172
CCS_TGRP_BUSY (NR) 166 311
CCS_TECH_IRREG (NR) 186 178
CCU_SUB_BUSY (NR) 0 -
CCU_INC_DIAL (NR) 0 0
CCU_UNALL_NUM (NR) 0 0
CCU_TGRP_BUSY (NR) 0 0
CCU_TECH_IRREG (NR) 0 0
Else (NR) 240 [2.4%] 303 [1.45%]
TC 235.73 Erl 560.13 Erl
TC_WA 175.58 Erl 478.83 Erl

Fig. 8 GOS Report for Originating Traffic (Part 1)

MN2534EU07AL_03
17
 Siemens Traffic Report

Incoming Calls
IC
CC (NR) 11 150
CC_NO_DIAL (NR) 0
CCU_INC_DIAL (NR) 2
CCU_UNALL_NUM (NR) 40
CCU_TECH_IRREG (NR) 0
CCU Else (NR) 1
Sum (NR) 43

Terminating Transit
TE TR
CC (NR) 6 422 4 685

CCS_WA (NR) 3 565 [90.9%] 3 116 [56.3%]

CCS_CMP_DIAL (NR) 1 047 492
CCS_SUB_BUSY (NR) 541 486
CCS_INC_DIAL (NR) 216 155
CCS_UNALL_NUM (NR) 600 154
CCS_TGRP_BUSY (NR) 181 92
CCS_TECH_IRREG (NR) 151 15
CCU_SUB_BUSY (NR) 0 -
CCU_INC_DIAL (NR) 0 0
CCU_UNALL_NUM (NR) 0 0
CCU_GRP_BUSY (NR) 0 0
CCU_TECH_IRREG (NR) 0 0

Else (NR) 121 [1.88%] 175 [3.73%]

TC 132.20 Erl 117.25 Erl

TC_WA 106.25 Erl 103.58 Erl

Fig. 9 GOS Report for Incoming Traffic (Part 2)

18 MN2534EU07AL_03
Traffic Report Siemens

Exchange Traffic
Traffic [Erl] MHT [Sec]

1200,0 Traffic Exch [Erl] 200,0

MHT_Exch
180,0

1000,0
160,0

140,0
800,0

120,0

600,0 100,0

80,0

400,0
60,0

40,0
200,0

20,0

0,0 0,0
06:00 07:00 08:00 09:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00
Tim e

Fig. 10 Calls Carried and Mean Holding Time (Exchange)

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

MN2534EU07AL_03
19
 Siemens Traffic Report

2.2 Explanation of the GOS Report Counters

(EWSD Vers.12)
CC
Calls carried, number of seizures accepted by the CP.

CCS
Calls Carried Successful, number of successful seizures within the own network node
(with SN path setup, i.e. speech channel and outgoing line successfully seized in the
CP or ISDN subscriber traffic speech channel seized in the CP (user channel to the
called subscriber not yet seized)).

CCU
Calls carried unsuccessful, number of unsuccessful seizures within the own network
node, premature call termination before SN path setup, e.g. due to "subscriber busy"
before SN path setup.

TC
Traffic carried, traffic value in Erl.

General Information

NE
Network element, name of the exchange

DATE
Date of measurement

PBH
Peak busy hour

20 MN2534EU07AL_03
Traffic Report Siemens

2.2.1 Exchange Statistics Counter

CC_EXCH (NR)
Total number of calls (CC) at the exchange

CCS_WA_EXCH (NR)
Number of answered calls (CCS) of the called subscriber terminal equipment (e.g.
calls).

TC_EXCH (ERL)
Traffic value for the total number of calls (CC EXCH) at the exchange

TC_WA_EXCH (ERL)
Traffic value of the answered calls (CCS) of the called subscriber terminal equipment.

2.2.2 Statistics Counter of the Generated (OR) and Incoming

Traffic (IC)

CC (NR)
Total number of calls (CC)

CC_NO_DIAL (NR)
Number of calls (CC) without the calling subscriber dialing (e.g. going off-hook and
then subsequently going on-hook) (only OR)

CCU_NO_DIAL (NR)
Number of calls (CCU) without the calling subscriber dialing (e.g. going off-hook and
then subsequently going on-hook) (only IC)

CCU_INC_DIAL (NR)
Number of calls (CCU) due to incomplete dialing (timeout or the calling subscriber
going on-hook)

MN2534EU07AL_03
21
 Siemens Traffic Report

CCU_UNALL_NUM (NR)
Number of calls (CCU) due to unknown directory number.

CCU_TECH_IRREG (NR)
Number of calls (CCU) due to technical faults.

CCU ELSE (NR)

Number of calls (CCU) for reasons other than those listed.

Total
Total number of calls (CCU, with OR also CC NO DIAL)

2.2.3 Counter for Internal (IT), Outgoing (OO), Terminating (TE)

and Transit (TR) Traffic

CC (NR)
Total number of calls (CC)

CCS_WA (NR)
Number of answered calls (CCS) of the called subscriber terminal equipment (e.g.
calls).

CCS_SUB_BUSY (NR)
Number of calls (CCS) with called subscriber busy.

CCS_INC_DIAL (NR)
Number of calls (CCS) with incomplete dialing.

CCS_UNALL_NUM (NR)
Number of calls (CCS) with unknown directory number.

CCS_TGRP_BUSY (NR)
Number of calls (CCS) with TGRP busy.

CCS_TECH_IRREG (NR)
Number of calls (CCS) due to technical faults.

22 MN2534EU07AL_03
Traffic Report Siemens

CCU_SUB_BUSY (NR)
Number of calls (CCU) due to called subscriber busy.

CCU_INC_DIAL (NR)
Number of calls (CCU) due to incomplete dialing.

CCU_UNALL_NUM (NR)
Number of calls (CCU) due to unknown directory number.

CCU_TGRP_BUSY (NR)
Number of calls (CCU) due to TGRP busy.

CCU_TECH_IRREG (NR)
Number of calls (CCU) due to technical faults.

TC (ERL)
Traffic value for all calls (CC).

TC_WA (ERL)
Traffic value of answered calls (CCS WA) of the called subscriber terminal equipment
(e.g. call).

MN2534EU07AL_03
23
 Siemens Traffic Report

24 MN2534EU07AL_03
Traffic Report Siemens

3 Trunk Group Data

MN2534EU07AL_03
25
 Siemens Traffic Report

3.1 TGRP Report

For network dimensioning, the trunk group measurement is of great importance. The
network analysis can be carried out in connection with the destination load
measurement and the routing information. Firstly we want to obtain an overview of
the network load with the TGRP report. The peak busy hour (PBH) for each trunk
group is determined separately.
The following counters must be checked firstly when analyzing the trunk group data:
l The number of available and required lines:
The number of required lines is almost twice as high as the number of available
lines at tgno 8 and 9 .
l Loss or overflow:
The CCU_SUM_OVFL and CCU_LOST_CALLS counters provide information
about the routing of the calls. 3,532 calls are rejected at tgno 8 but switched to an
alternative route because the CCU_LOST_CALLS counter = 0. The trunk group
dimensioning must however be checked because the value of the overflow traffic
(36.6%) is indeed too high and economical handling of the traffic is in question.
l Mean holding time(MHT):
The mean holding time in trunk groups 8 and 9 is within normal levels. This also
confirms that the calls are also being successfully switched to the alternative route.
However there is a problem with trunk groups 6 and 7. The values of 53.37 and
59.67 seconds indicate blockings with automatic redialing. The CCU_SUM_OVFL
and CCU_LOST_CALLS counters both read zero, so the problem is at one of the
subsequent exchanges.
The CCS_CCS7_CALL_FAIL and CCS_CONG counters show very high values
for both trunk groups. The exact cause cannot be determined with the traffic
measurement. Therefore further examinations with the signaling tracer must be
carried out to find the Reason for Call Failure (RCF).
l Answer Seizure Rate (ASR):
The low ASR values (33.24% and 40.97%) for trunk groups 6 and 7 result from the
high blocking rate. The remaining trunk groups have an ASR of 65% to 70%,
standard mean values.

26 MN2534EU07AL_03
Traffic Report Siemens

Incoming and Outgoing

TGRP Data
Mean
Lines Traffic Calls
Values

CCS
Conn. Serv. Req. Traffic Traffic Traffic Calls
OP Loss WITH ASR MHT
TGRP PBH Lines Lines Lines Off Carr. / Line Carr.
MOD (%) ANS (%) (Sec)
(NR) (NR) (NR) (Erl) (Erl) (Erl) (NR)
(NR)

tgno
BW 11:00 558 558 271 230.7 230.7 0.41 0.00 9 053 5 973 65.98 91.73
1
tgno
BW 10:45 558 558 268 228.2 228.2 0.41 0.00 8 919 5 843 66.51 92.09
2
tgno
BW 10:45 464 464 185 151.1 151.1 0.33 0.00 5 754 3 791 65.88 94.51
3
tgno
BW 11:00 464 464 214 177.5 177.5 0.41 0.00 6 856 4 514 65.84 93.18
4
tgno
BW 11:00 496 496 194 159.5 159.5 0.34 0.00 5 522 3 724 67.44 104.0
5
tgno
BW 15:00 371 371 259 219.2 219.2 0.59 0.00 14 786 4 915 33.24 53.37
6
tgno
BW 14:00 495 495 175 142.3 142.3 0.29 0.00 8 585 3 517 40.97 59.67
7
tgno
BW 11:00 123 123 228 191.3 121.3 0.99 36.6 4 267 2 957 69.30 102.4
8
tgno
BW 10:15 123 123 223 185.9 121.2 0.99 34.8 4 623 3 134 67.79 94.38
9

Fig. 11 Trunk Group Report - Calls and Traffic at PBH (Part1)

MN2534EU07AL_03
27
 Siemens Traffic Report

Incoming Outgoing

Calls Calls Calls CCU Calls CCS

CCU
CCU CCS CCS
CCS LOST CCS CCS
CCS SUM CCS7 SUM
CC_IC ANS_I CC_OG CALL SUM CON
TGRP ANS_OG OVFL/ CALL TECH
NR C (NR) (NR) S SUB G
LOSS FAIL IRR
(NR) REJ (NR) (NR)
(NR) (NR) (NR)
(NR)
tgno
5 219 3 392 3 834 2 581 0 0 42 1 152 10 41
1
tgno
4 987 3 211 3 932 2 632 0 0 40 1 194 22 45
2
tgno
4 070 2 666 1 684 1 125 0 0 12 523 6 17
3
tgno
5 220 3 436 1 636 1 078 0 0 19 513 5 15
4
tgno
3 949 2 661 2 573 1 063 0 0 7 489 2 13
5
tgno
0 0 14 786 4 915 0 0 5 069 3 667 53 1 073
6
tgno
0 0 8 585 3 617 0 0 537 3 731 146 723
7
tgno
0 0 4 267 2 957 3 532 0 24 1 228 3 59
8
tgno
0 0 4 623 3 134 3 493 0 25 1 331 13 126
9

Fig. 12 Trunk Group Report - Calls and Traffic at PBH (Part 2)

28 MN2534EU07AL_03
Traffic Report Siemens

Trunk Group Load

N' Available
Traffic [Erl]
100 100

Number of
90 90
Trunks

80 80

70 70

60 60
TGRP xxxx TC:I + TC:O
50 TGRP xxxx TC:I 50
TGRP xxxx TC:O
40 40

30 30

20 20

10 10

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

Fig. 13 Calls Carried and Mean Holding Time (Trunk Group)

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

MN2534EU07AL_03
29
 Siemens Traffic Report

3.2 Explanation of the TGRP Report Counter

Abbreviations

CC
Calls carried, number of trunk group seizures

CCS
Calls Carried Successful, number of successful seizures (trunk group seizure)

CCU
Calls carried unsuccessful, number of unsuccessful seizures (no trunk group seizure)

TC
Traffic carried, traffic value in Erl.

3.2.1 General Information per Trunk Group

TGRP
Trunk group name (trunk group number)

OPMOD
Trunk group operating mode
IC = incoming
OG = outgoing
BW = bothway

PBH
Time of the peak busy hour

30 MN2534EU07AL_03
Traffic Report Siemens

3.2.2 Counter per Incoming, Outgoing or Bothway Trunk Group

CONN_LINES (NR AVG)

Number of connected lines; the information for bothway trunk groups refers to the
total number of installed lines for incoming and outgoing traffic. The information is
given as a mean value for the period under review.

SERV_LINES (NR AVG)

Number of in-service lines. The information is given as a mean value for the period
under review.

REQ_LINES (NR)
Calculated number of theoretically required lines (input parameters are TRAFFIC
OFFERED and admissible loss=0.1%). The information only applies for only-choice
route trunk groups with no overflow configuration and is a reference value.

TRAF_OFF (ERL)
Calculated traffic offered (input parameters are SERVICING LINES and total traffic
intensity).

TRAF_CARR (ERL)
Calculated trunk group traffic value.

TRAF_CARR_LINE (ERL)
Calculated traffic value for each line of the trunk group.

LOSS (%)
Calculated trunk group loss. Here only the only-choice route is considered, i.e. calls
which have been counted as losses can be successful in the second-choice route.

CALLS_CARR (NR)
Total of all calls with trunk group seizure.

CCS_WITH_NS (NR)
Total number of successful answered calls of the called subscriber terminal
equipment (e.g. calls) following trunk group seizure.

MN2534EU07AL_03
31
 Siemens Traffic Report

ASR (%)
Calculated ratio (answer seizure ratio) between CALLS CARRIED and CCS WITH
ANSWER.

MHT (SEC)
Calculated mean holding time of all calls.

3.2.3 Counter per Incoming Trunk Group and Counter per BW

Trunk Group in Incoming Traffic

CC_IC(NR)
Number of seizures accepted in the CP in the incoming traffic.

CCS_ANS_IC (NR)
Number of successful incoming answered calls.

3.2.4 Counter per Outgoing Trunk Group and Counter per BW

Trunk Group in Outgoing Traffic

CC_OG (NR)
Number of seizures accepted by the trunk group (CP database) in the outgoing traffic
(there is SN path setup).

CCS_ANS_OG (NR)
Number of successful answered calls of the called subscriber terminal equipment
(e.g. calls) following trunk group seizure (CC O).

CCU_SUM_OVFL_LOSS (NR)
Number of unsuccessful attempts to seize the trunk group. This is the total of
overflowed seizures (overflow) and rejected seizures (loss). For high-usage route
trunk groups and the last-choice trunk group, this is the total number of lost calls.

32 MN2534EU07AL_03
Traffic Report Siemens

CCU_LOST_CALLS_REJ (NR)
Number of unsuccessful calls without trunk group seizure (lost call) after hunting all
routes.

CCS_CCS7_CALL_FAIL (NR)
Number of call terminations following trunk group seizure (CC O) due to receipt of the
CALL_FAILURE (TUP) line signal or with ISUP following receipt of certain line
signals (IUC) of the SS7 messages, from which the RCF CALL FAILURE is then
formed.

CCS_SUM_SUB (NR)
= CCS_INCMP_DIAL + CCS_UNALL_NUM + CCS_SUB_BUSY + CCS_
UNANSWERED
Number of call terminations following trunk group seizure (CC_OG) caused by
subscriber behavior.
l CCS_INCMP_DIAL (NR)
Number of call terminations following trunk group seizure (CC_OG) caused by the
calling subscriber.
goes on-hook after incomplete dialing (i.e. status in the own exchange is still
"incomplete dialing") or dial tone delay timeout.
l CCS_UNALL_NUM (NR)
Number of call terminations following trunk group seizure (CC_OG) because the
dialed number is not set up or the call is not permitted as a destination for the
calling subscriber (SPV, CUG and Service).
l CCS_SUB_BUSY (NR)
Number of call terminations following trunk group seizure (CC_OG) due to receipt
of the backward signal "subscriber busy".
l CCS_UNANSWERED (NR)
Number of call terminations following trunk group seizure (CC_OG) because the
called subscriber does not answer (ringing time supervision timeout) or because
the calling subscriber releases the connection, after the status "end of pulsing" has
been reached in the own exchange and before the called subscriber answers.

MN2534EU07AL_03
33
 Siemens Traffic Report

CCS_SUM_TECH (NR)
= CCS_INT_TECH_IRREG + CCS_EXT_TECH_IRREG + CCS_RELORIG
ENDTOEND + CCS_LINK_FAILURE
Number of call terminations following trunk group seizure (CC O) caused by technical
faults.
l CCS_INT_TECH_RREG (NR)
Number of call terminations following trunk group seizure (CC O) due to technical
faults in the own exchange. The switching network was switched within the own
network node.
l CCS_EXT_TECH_IRREG (NR)
Number of call terminations following seizure of the outgoing line (e.g. CC O) due
to technical faults in the network outside the own network node.
l CCS_RELORIG_ENDTOEND (NR)
Number of call terminations following trunk group seizure (CC O) from the
originating network node "clear forwarding" without the actual reason for the
release in the transit network node being known. The counter is only routed in
transit network nodes if originating and destination network nodes signal in end-to-
end.
l CCS_LINK_FAILURE (NR)
Number of call terminations following trunk group seizure (CC O) because the
access to the outgoing line (LTG output) was not possible. The call is terminated
by the called party's LTG.

CCS_CONG (NR)
Number of call terminations following trunk group seizure (CC O) due to receipt of the
backward signal for "all trunks busy" from the subsequent network nodes (transit or
destination network nodes).

34 MN2534EU07AL_03
Traffic Report Siemens

4 Destination Area Report

MN2534EU07AL_03
35
 Siemens Traffic Report

4.1 DEST Report

The already familiar trunk group measurement supplies the load between two
exchanges. However, if the traffic from transit 1 to destination 1, 2 or n is to be
determined, then the destination load measurement (REC DEST) must be used. This
way the traffic from transit 1 to destination 1 (without originating point code) can be
measured, independent of how the connection is switched through the network.
Five routes are possible with the configuration shown, in which the traffic from all
originating exchanges (orig 1,2.. n) is included.

Route 1: Transit 1 è Dest 1

Route 2: Transit 1 è Transit 2 è Dest 1
Route 3 Transit 1 è Transit 3 è Dest 1
Route 4 Transit 1 è Transit 2 è Transit 3è Dest 1
Route 5 Transit 1 è Transit 3 è Transit 2 è Dest 1

The measurement can also be initiated with originating point code (ORIG 1). This
way we obtain the traffic values of Orig1 via Transit1 and via the various routes
Transit 2/3) to destination 1,2 .. n.
Creating a complete traffic matrix for the network planning is only possible for very
small networks because the number of destination codes is limited to 512 digit
combinations. This figure becomes exhausted very quickly for comprehensive
destination load measurements.
Additionally, the destination load measurement represents an additional dynamic
load for the central processor CP 113 because the digit combination for the
destination measurement must be evaluated separately.
In practice this measurement is therefore only used selectively to determine the traffic
flows at network bottlenecks.

36 MN2534EU07AL_03
Traffic Report Siemens

Orig n
Orig 1 Orig 2

Destination
Transit
Measurement
1
Trunk Group
Measurement

Transit Transit
2 3

Dest 1 Dest 2 Dest n

Fig. 14 Destination Load Measurement (REC DEST)

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

MN2534EU07AL_03
37
 Siemens Traffic Report

4.2 DEST Parameters

The available destination area measurement does not indicate any problem cases.
The general parameters are explained in more detail for proper analysis of the data:

General:
l Code This is the digit combination of the destination code for the destination
that is being measured.
l LAC If the local area code is required for unique selection of subscriber
number, then the Local Area Code = LAC is specified.
l ORIGIN The originating point code is required with incoming trunk groups and
subscribers for an originating destination load.
l ZDIG The language digit is specified with international operator traffic so that
the operator with the appropriate language is selected in the
destination country.
l @ If no values are specified for the above-mentioned parameters, then
the padding character "@" is output in the table.
Attention: The parameters for ORIGIN and ZDIG can only be used for the REC
DEST measurement if the database is created with these values.

38 MN2534EU07AL_03
Traffic Report Siemens

Part 1

STA-
GENERAL CALLS TRAFFIC CCS Part1
TISTICS
CCS CCS
CS TC CCS
CC TC ASR MHT CCS7 INCL
Code LAC Orig. Zdig PBH WA WA CONG
(NR) (Erl) (%) (Sec) CF DIAL
(NR) (Erl) (NR)
(NR) (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

CCS CCS CCS CCU CCU
CCS CCS CCS CCS CCS CCU
EXT INT REL CCU NM NMN CC CC
LINK Oper. SUB unall. un- TECH
TECH TECH Orig. CONG Code TRK LQA LQS
FAIL REL BUSY NUM answ. Irreg.
Irreg. Irreg. ETE (NR) Block BLK (NR) (NR)
(NR) (NR) (NR) (NR) (NR) (NR)
(NR) (NR) (NR) (NR) (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. 15 Destination Report

MN2534EU07AL_03
39
 Siemens Traffic Report

4.3 Analysis of the Destination Data

During analysis, under certain load situations, the results initially appear implausible,
for example when the traffic significantly increases within one hour and then
decreases just as significantly again shortly afterwards. The table in Fig. 27 should
demonstrate this more clearly. This problem occurs in the fourth interval because
here fewer new calls are set up (CC = 119), but more calls from the previous
intervals are released (CC_WA = 168). This leads to an answer seizure rate of ASR
= 141.2%.
This effect is greater with small traffic currents (TC <= 10 Erl) because the traffic
shows larger fluctuations. This can also be observed with extreme load peaks such
as televoting. However, if the mean value is calculated from the four 15-minute
intervals, then normal values for the answer seizure rate (ASR = 56.3%) result.
As with the trunk group measurement, by separating CCU and CCS, it can be
immediately recognized whether the problem lies in the own or in the subsequent
exchange.
If the CCU_CONG counter shows values > 0, then all routes to the dialed destination
were blocked. The counter CCS_CONG > 0 states that the call setup was blocked on
a subsequent route section. However, the destination load measurement does not
state the route where the block occurred.

40 MN2534EU07AL_03
Traffic Report Siemens

PBH
1. Interval 2. Interval 3. Interval 4. Interval
T = 3600 s

CC
132 291 538 119 1080
(NR)

CC_WA
38 93 309 168 608
(NR)

TC
14.7 32.3 59.8 13.2 30.0
(Erl)

TC_WA
6.8 16.5 54.9 29.9 27.0
(Erl)

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

ASR > 100 %

Fig. 16 Destination Load

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

MN2534EU07AL_03
41
 Siemens Traffic Report

4.4 Explanation of the DEST Report Counter

Abbreviations

CC
Calls carried, number of seizures

CCS (CS)
Calls Carried Successful, number of successful seizures

CCU
Calls carried unsuccessful, number of unsuccessful seizures

TC
Traffic carried, traffic value in Erl

4.4.1 General Information

The counter code, LAC, origin and zdig are specified depending on the chosen
parameter each time the REC DEST measurement is initiated. Empty fields contain a
"@".

Code
Destination code, for which the traffic is measured.

LAC
Location area code

ORIGIN
Originating code. The destinations can be measured independent of origin (source ®
destination), i.e. traffic from one or several origins to one destination.

42 MN2534EU07AL_03
Traffic Report Siemens

ZDIG
Language code (language digit) to address the operator. This digit modifies for
example the destination directory number, i.e. by entering this digit into the
destination directory number, the traffic to the operator position dialed via the
language digit is measured.

PBH
Time of the peak busy hour

4.4.2 Counter per Destination (Outgoing)

CC (NR)
Number of seizures accepted for the destination within the own network node, i.e.
there has been SN path setup within the own network node (speech channel and
outgoing line busy at the called end) and for example CMD:SETUP_C and
SEIZURE_C_BT have been transmitted from the CP to the LTG of the calling and
called end.
CC =
CCS WITH ANSWER+
CCS SS7 VERB FAULT+
CCS ATB+
CCS INCOMPLETE DIALING+
CCS SIG FAILURE+
CCS DIR NUMBER UNAVAILABLE+
CCS OPR RELEASE+
CCS FROM ORIG ENDTOEND+
CCS SUBSCR BUSY+
CCS EXT TECH REASONS+
CCS INT TECH REASONS+
CCS NO ANSWER

MN2534EU07AL_03
43
 Siemens Traffic Report

CS_WA (NR)
Number of answered calls of the called subscriber terminal equipment (e.g. calls).
This event is only counted at the end of the call.

TC (ERL)
Total holding times; traffic value TC [Erl].

TC_WA (ERL)
Total duration for answered calls of the called subscriber terminal equipment, e.g. call
duration; traffic value TC WITH ANSWER [Erl]. The answer duration is only added at
the end of the call and with long-duration calls additionally for example every 1,800
seconds. This time can be administered in the CP.

ASR (%)
Calculated ratio (answer seizure ratio) between CC and CS WA.

MHT (SEC)
Calculated average call duration (mean holding time) of all calls (CC).

CCS_CCS7_CF (NR)
Number of calls which were rejected by a subsequent network node via the line
signal CALL FAILURE following successful SN path setup (speech channel and
outgoing line busy) within the own network node.

CCS_CONG (NR)
Number of call terminations which were rejected by a subsequent network node or a
private branch exchange with DID via the line signal for ATB following successful SN
path setup.

CCS_INC_DIAL (NR)
Number of call terminations following SN path setup because the calling subscriber
releases the connection after incomplete dialing or there is dial tone delay timeout in
the own network node.

CCS_EXT _TECH IRREG (NR)

Number of call terminations following SN path setup due to technical faults in the
network outside the own network node.

44 MN2534EU07AL_03
Traffic Report Siemens

CCS_INT TECH_IRREG (NR)

Number of rejected seizures following SN path setup within the own network node
due to technical faults in the own network node.
Number of call terminations following SN path setup (CC) because the called
subscriber's terminal equipment does not answer (ringing time supervision timeout in
the LTG of the own network node or the incoming line releases the call in the calling
state.

CCS_LINK_FAIL (NR)
Number of calls which were terminated by the LTG following SN path setup because
the GS in the LTG of the called subscriber was not switchable or because no timeslot
in the DIU was seizable at the called end.

CCS_OPER_REL (NR)
Number of call terminations by the operator following SN path setup, for example due
to receipt of an audible signaling tone for "busy". The counter is only active with
outgoing operator traffic (OPR ® calling subscriber or OPR ® called subscriber).

CCS_RELORIG_ETE (NR)
Number of call terminations following SN path setup within in the own network node
from the originating network node via CLEAR FORWARDING without the actual
release reason, e.g. ATB, in the transit network node, being known. The counter is
only active in transit network nodes if originating and destination network nodes
signal end-to-end in MFC.

CCS_SUB_BUSY (NR)
Number of call terminations following SN path setup within the own network node due
to:
l ”subscriber busy” in the destination network node.
l ”subscriber busy” in a PABX with direct inward dialing of the own network node.
l ”subscriber busy” of an ISDN subscriber of the own network node.
l ”subscriber busy” of an analog subscriber within the own network node which uses
features such as call waiting, three party service or automatic callback.

CCS_UNALL_NUM (NR)
Number of call terminations following SN path setup (within the own network node)
due to ”unobtainable directory number” in a subsequent network node. Note: if an
ISDN called subscriber of a PABX with DID is measured as the traffic destination,
then this counter is updated when an unobtainable directory number is dialed.

MN2534EU07AL_03
45
 Siemens Traffic Report

CCS_UNANS (NR)
Number of calls for which the switching network is successfully switched within the
own network node but the called subscriber's terminal equipment does not answer.

CCS_CONG (NR)
Number of calls which were prematurely terminated within the own network node
before SN path setup due to "trunk group busy" or "subscriber busy" or due to CCNC
overload of the own network node or DPC overload of the destination network node.
The subscriber busy scenario of an ISDN subscriber within the own network node is
predominantly recognized by the called end's LTG and is recorded in the counter
CCS_SUB BUSY.

CCS_NM CODE_BLK (NR)

Number of calls which were rejected within the own network node before SN path
setup due to network management measures. The traffic to destinations is gradually
reduced or completely rejected by these measures.

CCS_NM_TR BLK (NR)

Number of calls which were rejected within the own network node before SN path
setup due to access not permitted (e.g. trunk reservation) to the outgoing trunk
group.

CCS_TECH_IRREG (NR)
Number of calls which are prematurely terminated within the own network node
before SN path setup due to internal SN blocking, unobtainable directory number or
internal technical faults or external technical faults from the originating network node.

46 MN2534EU07AL_03
Traffic Report Siemens

CC_LQA (NR)
Number of calls with inquiries to an LNP server (LNP-local number portability). The
counter registers the number of calls for which an inquiry has been made to an
internal or external LNP server. Inquires about the query on release procedure and
the query on digit analysis procedure are counted. The counter is only increased
once, even if several inquires for a call are directed at the server. The counter is
increased for the original number (the dialed number).

CC_LQS (NR)
Number of successful inquiries to an LNP server (LNP local number portability), i.e. a
new routing number has been received from the LNP server. The successful inquires
about the query on release procedure and the query on digit analysis procedure are
counted. The counter is only increased once, even if several inquires for a call are
directed at the server. The counter is increased for the original number (the dialed
number).

MN2534EU07AL_03
47
 Siemens Traffic Report

48 MN2534EU07AL_03
Traffic Report Siemens

5 C7 Link Load Report

MN2534EU07AL_03
49
 Siemens Traffic Report

5.1 Feature Description

Evaluations are based on historical data. It is performed for the Daily Totals or for the
Daily Peak Busy Hour (PBH) of the evaluation period. The PBH is the hour that
registered the maxim value of the total traffic in the Link Set.
The source data for this report is collected in the C7LL measurement.

The reports can be requested for one NE or for a group of NEs of the SSS Network.
It’s also possible to apply constraints to the Link Sets selected by forcing its names to
match a certain pattern imputed as a parameter.
The evaluation results are grouped by NE and sorted by alphanumeric order of the
Link Set name.

Execution parameters:
l NE Identification: (SPOTS “internal” id.).
l Link Set: (Name that identifies each CCS7 Link Set)
l Data Type: (“1” for PBH of each day or “0” for Daily Totals).
l Minimum Load: (The resulting table report will only include Links with higher value
than the specified Minimum Load)
Evaluation period.

50 MN2534EU07AL_03
Traffic Report Siemens

Fig. 17 C7 Link Load Report

MN2534EU07AL_03
51
 Siemens Traffic Report

5.2 Description of the Evaluation Results

l The name of the Link Set.
Link Set = LSNAM

l A signaling link code from 0 to 15. (Enable the univocal identification of each link
belonging to a Link Set).
Link Code = LCOD

l A number from 0 to 255. (Enable the univocal identification of each link belonging
to a NE).
Link Number = LINKNO

l Date in case the report was requested for the Daily Global values, or date and
PBH in case the report was requested for the PBH.

Link Load:
Each signaling link is in fact two 64 kbps links, one for transmission and the other for
reception of the MSUs. Each MSU has an information field of variable length
(concatenation of SIF and SIO bytes) and a layer two header with fixed length of 6
bytes. The load is calculated for both directions separately. The higher value must
not exceed the Reference that has the default value of 0.2 [Erl]. This value is set so
low because measurement only produces mean load. It is possible that the load rises
to quite higher values for several seconds.

Period = 3600 [sec] (in case the report was requested for the PBH) or 86400 [sec] (in
case the report was requested for the Daily Global)
l Traffic carried by the transmitting link in the evaluation period in Erlangs.
Link Load Recv [Erl] = (6 ´ NUM_MRC + NUM_SSRC) / (8000 ´ Period)
Reference (default value): >0.2 [Erl]
l Traffic carried by the receiving link in the evaluation period in Erlangs.
Link Load Trans [Erl] = (6 ´ NUM_MTR + NUM_SSTR) / (8000 ´ Period)
Reference (default value): >0.2 [Erl]
l Indicates the number of links out of service due to overload.
Cong. Links [Nr] = NUM_LINK_CON
l Indicates the duration of link congestion in seconds.
Cong. Duration [sec] = DUR_LINK_CON

52 MN2534EU07AL_03
Traffic Report Siemens

Received MSUs:
l Indicates the number of received MSUs.
Recv. MSUs [Nr] = NUM_MRC

l Indicates the average size of the received MSUs in bytes.

Average MSU Size [bytes] = (6 ´ NUM_MRC + NUM_SSRC) / NUM_MRC

Transmitted MSUs:
l Indicates the number of transmitted MSUs.
Trans. MSUs [Nr] = NUM_MTR

l Indicates the average size of the transmitted MSUs in bytes.

Average MSU Size [bytes] = (6 ´ NUM_MTR + NUM_SSTR) / NUM_MTR

l Percentage of the discarded MSUs due to overload from the total transmission
attempts.
Discarded MSUs due to Overload [%] = 100 ´ MSU_CON / (NUM_MTR +
MSU_CON)

l Percentage of the transmitted information bytes that are in fact retransmissions.

SIF & SIO Retrans. [%] = 100 ´ OCT_RET / NUM_SSTR

l Weight of the transmitted MSUs in the total number of MSUs transmitted

expressed in a percentage.
Balance (Trans / Total) [%] = 100 ´ NUM_MTR / (NUM_MTR + NUM_MRC)

MN2534EU07AL_03
53
 Siemens Traffic Report

54 MN2534EU07AL_03