Академический Документы
Профессиональный Документы
Культура Документы
XXXX
Project Manager: XXXX
Prepared for: XXXX
Prepared By: XXXX
www.aircominternational.com
Page | 1 of 90
Table of Contents
1
INTRODUCTION .............................................................................................................................................. 9
NETWORK OVERVIEW..................................................................................................................................... 9
2.1
2.2
CAPACITY ANALYSIS...................................................................................................................................... 11
3.1
3.2
3.3
3.4
3.5
4.1
Introduction ....................................................................................................................................... 14
4.2
Concepts ............................................................................................................................................ 14
4.3
Availability.......................................................................................................................................... 18
4.3.1
System Downtime....................................................................................................................... 18
4.3.2
4.4
Accessibility........................................................................................................................................ 19
4.4.1
Authentication........................................................................................................................... 19
4.4.2
4.4.3
4.4.4
Location Update........................................................................................................................ 21
4.4.5
Mobile IN Calls............................................................................................................................ 23
4.4.6
Channel Assignment................................................................................................................. 23
4.4.7
4.4.8
4.4.9
4.4.10
Page | 2 of 90
4.4.11
4.4.12
4.4.13
Paging........................................................................................................................................ 30
4.4.14
4.5
Retain-ability ...................................................................................................................................... 35
4.5.1
5
FINDING ........................................................................................................................................................ 36
5.1
Roaming ............................................................................................................................................. 36
5.2
5.2.1
Overview ................................................................................................................................... 36
5.3
5.4
5.5
5.6
B Number Table.................................................................................................................................. 42
5.7
5.8
5.9
5.10
5.11
5.12
System Logs........................................................................................................................................ 46
5.13
5.14
5.15
Unused Route..................................................................................................................................... 47
5.16
Naming Standard................................................................................................................................ 47
5.17
SIGTRAN ....................................................................................................................................................... 49
6.1
6.2
6.3
Page | 3 of 90
6.4
7
M-MGW KPI.................................................................................................................................................. 51
7.1
Scope ................................................................................................................................................. 52
7.2
Introduction ....................................................................................................................................... 52
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.11
7.12
7.13
Retainability ....................................................................................................................................... 61
7.14
Integrity ............................................................................................................................................. 62
7.14.1
7.14.2
7.14.3
7.14.4
7.14.5
7.14.6
SCTP .......................................................................................................................................... 65
7.14.7
7.14.8
M3UA ......................................................................................................................................... 67
7.15
7.15.1
7.15.2
7.15.3
7.15.4
Page | 4 of 90
7.15.5
7.15.6
7.15.7
7.15.8
7.15.9
7.15.10
Processor Load...................................................................................................................... 79
7.15.11
7.15.12
8.1
8.2
9.1
Documentation .................................................................................................................................. 87
9.2
Procedures ......................................................................................................................................... 88
9.3
Recommendations ............................................................................................................................. 88
10 CONCLUSION ................................................................................................................................................ 89
11 APPENDIX ..................................................................................................................................................... 90
Page | 5 of 90
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Page | 6 of 90
List of Tables
Table 1 Core Hardware Location Per City .......................................................................................... 9
Table 2 BSS Hardware Location per City ......................................................................................... 10
Table 3 VLR Subscriber Register Capacity ....................................................................................... 11
Table 4 Clock Reference in XXXX Network ...................................................................................... 37
Table 5 HW FAULT MSC ............................................................................................................... 44
Table 6 HW FAULT BSC ................................................................................................................ 45
Table 7 Unused Cell ID Definitions ................................................................................................. 46
Table 8 Software Level Integrity .................................................................................................... 48
Table 9 SIGTRAN-1 ...................................................................................................................... 49
Table 10 SIGTRAN-2 .................................................................................................................... 49
Table 11 SIGTRAN-3 .................................................................................................................... 50
Table 12 SIGTRAN-4 .................................................................................................................... 50
Page | 7 of 90
RELEASE DATE
XXXX
PURPOSE
FINAL DRAFT
DISTRIBUTION LIST
NAME
POSITION / DEPARTMENT
APPROVALS
APPROVED BY
SIGNATUR
DATE
XXXX
AIRCOM INTERNATIONAL
XXXX COUNTRY
Page | 8 of 90
1 INTRODUCTION
Aircom has conducted a Technical Audit of XXXX Network between the dates of XXXX and XXXX. This Audit
project comprises of a combination of collecting data; discussion with XXXX technical teams; desk based
research; detailed interviews and analysis of documentation and information supplied by the XXXX. This NSS
audit report has been prepared based on the data provided by the Core planning & O&M responsible personal of
XXXX
2 NETWORK OVERVIEW
Following are the core network entities and sites of XXXX
2.1
Location
Node Name
MSC
CITY5
XXMSC1
CITY4
XXMSC1
CITY3
XXMSC1
CITY6
XXMSC1
CITY2
XXMSC1
CITY1
Technical Villa
XXMSC3
CITY1
Technical Villa
XXMSC4
CITY1
Park plaza
XXMSC
CITY1
Park plaza
MSCS2
HLR
CITY1
HLR1
CITY1
HLR2
MGW
CITY1
Technical Villa
MGW11
CITY1
Technical Villa
MGW12
MGW21
MGW31
CITY2
CITY1
Park plaza
Total
Page | 9 of 90
2.2
Location
BSC Name
BSC
Total Node in
City
CITY7
BGNRBSC
CITY8
GZNRBSC
CITY5
HEBSC1
CITY4
JABSC1
CITY9
JZNRBSC
CITY3
KDBSC1
CITY10
KHRBSC1
CITY6
KUBSC1
CITY2
MABSC1
CITY2
MABSC2
CITY11
NEBSC1
1
5
CITY1
Technical Villa
KABSC1
CITY1
Technical Villa
KABSC2
CITY1
Park plaza
KABSC3
CITY1
Park plaza
KABSC4
CITY1
Technical Villa
KABSC5
Total
16
16
Page | 10 of 90
3 CAPACITY ANALYSIS
This section contains the outcomes of capacity audits.
3.1
TOTNSUB REGISTERD
VLR CAPACITY
Available Capacity
XXMSC1
197380
600000
402620
XXMSC1
283839
600000
316161
XXMSC1
58407
600000
541593
XXMSC1
328894
600000
271106
XXMSC1
437078
1000000
562922
XXMSC3
120015
1000000
879985
XXMSC4
536274
1000000
463726
XXMSC
346476
1000000
653524
MSCS2
267511
1000000
732489
Page | 11 of 90
3.2
Below is the VLR subscriber capacity utilization. Threshold is showing to be 54% No expansion required at this
time.XXXX can add more BSC/BTS to improve radio coverage.
Page | 12 of 90
3.4
Below is the HLR subscriber capacity utilization. Threshold is reached to be 95% it is highly recommended to
perform reconciliation schedule on monthly basis to efficiently utilize HSD memory and avoid its expansion.
License capacity is enough for current traffic load; XXXX can add more equipment without any expansion of MGW
Page | 13 of 90
4 PERFORMANCE INDICATORS
4.1
Introduction
This section defines switching system performance indicators for the MSC and MSC Server. The MSC is the call
control handling node in layered and non-layered architecture. All counter descriptions in this section are used for
information. The Application Informations shall be used for latest and more detailed counter descriptions.
4.2
Concepts
Performance indicators defined in this section focus on reliability and how a service is executed in the MSC/VLR
Server.
Page | 14 of 90
Page | 15 of 90
Figure 3-3
Availability
Availability is defined as the ability of an item to be in a state to perform a required function at a given point of
time or at any instant of time within a given time interval, assuming that the external resources, if required, are
provided.
Severability
The ability of a service to be obtained - within specified tolerances and other given conditions - when requested
by the user and continue to be provided without excessive impairment for a requested duration. Serve-ability
performance is subdivided into the service accessibility performance, service retain-ability performance and the
service integrity performance.
Page | 16 of 90
Accessibility
The ability of a service to be obtained, within specified tolerances and other given conditions, when requested by
the end-user.
Retain-ability
Retain-ability reflects the ability of the user to keep a service once it was accessed under given conditions for a
requested period of time.
Integrity
Integrity reflects the ability of a user to receive requested service at desired quality. No Integrity PIs are defined
for the MSC.
Page | 17 of 90
4.3
Availability
Page | 18 of 90
Link unavailbity due to the Transmission fluctuation, XXXX should resolve this issue to improve healthy KPI
4.4
4.4.1
Accessibility
Authentication
The average successful Authentication results for the complete XXXX network are shown in the figures below
Figure 7 Authentication
Recommendations:
The Authentication Success rate is indicating normal conditions in all the network; the values are currently around
97% which is in par with the world average according the previously mentioned benchmark and above the
minimum recommended value of 95%
4.4.2
Ciphering, GSM
The average Ciphering results are shown in the table and figures below for the complete XXXX network:
Page | 19 of 90
CP Processor Load
Page | 20 of 90
Recommendations:
The central processor load in all the nodes were considered normal and the peak load in the busy hour did not
reach the maximum recommended limit (75%).
4.4.4
Location Update
Page | 21 of 90
Page | 22 of 90
Channel Assignment
Page | 23 of 90
Page | 24 of 90
4.4.8
Absent Subscriber: The receiving user is either powered off or out of the service area.
System Failure: Mostly related to the radio network and the MS, such as assignment failure of SDDCH,
call drop when receiving SMS, etc
Page | 25 of 90
4.4.9
Page | 26 of 90
Page | 27 of 90
Dimensioning rules are allowing utilization 30% load in a non-failure situation and 60% load in a load in
a failure situation.
It is very important that load limits are maintained within the range, as when the SS7 links reaches a
certain load level, the message success rate decreases dramatically.
Page | 28 of 90
Page | 29 of 90
4.4.13 Paging
Figure 20 Paging
Suss_GSM_First Page Recommended KPI Minimum Value 84%
Succ_GSM_Paging Recommended KPI Minimum Value 88%.
Recommendations: (Suss_GSM_First Page)
The XXMSC3, XXMSC, XXMSC and XXMSC1 paging results show a normal behavior and in accordance to the
global values.
In the other hand, for the XXMSC1,XXMSC1,XXMSC1 located outside of CITY1 the values could be improved a bit
with improvements to radio coverage e.g. an attached mobile out of coverage will not be able to receive or
respond to a page.
Check the parameter settings of the network; it can often improve the paging performance especially if coverage
is not the main problem.
The time between periodic registrations, the function Implicit IMSI detach, the Nr. of LAs and the size of the LAs
are the key issues. TMSI should be used at least for the first page.
Page | 30 of 90
Recommendations: (Succ_GSM_Paging)
The XXMSC1, XXMSC1 XXMSC1 and XXMSC1 MSCs are showing a slightly lower average results that the global
benchmark (around 88%) mentioned above.
As for the other MSCs, there seem to be problems as the number of repeated page attempts to a location area
over A-interface is high. The following causes might explain the low paging success rate:
LA dimensioning should be carried out in order to have proper Nr. of LA in 1 MSC. If LA is under dimensioned,
then it will affect paging success rate, on the other hand if LA is over dimensioned, then it will increase LU load,
and affect LU success rate.
Low paging success rate could be explained with coverage problems or that the function Implicit IMSI detach is
not used or that T3212 is set too high.
Paging performance is mainly depending on radio performance, especially radio coverage, radio capacity, cell
planning and frequency planning to reduce as much interference as possible.
Figure 1: Paging of a MS
Page | 31 of 90
Page | 32 of 90
Other strategies than those recommended affect the paging load as follows:
No second page: No second page reduces the paging load in both the BTS and the BSC. The
disadvantage is risk of more unsuccessful MS paging.
Global second page: Compared to a local second page, a global second page increases the
paging load. The advantage is that MSs that, for some reason, have the wrong LA status in the
VLR stand a better chance of being successfully paged.
TMSI for second pages: If the second page is global, IMSI must be used to identify the MS. If the
second page is local, either IMSI or TMSI can be used to identify the MS. Using TMSI increases
the paging capacity in the BTS. The drawback is that some pages may be unsuccessful if an MS
has the wrong TMSI in the VLR, for example, immediately after having crossed an LA boarder.
The major failure in the ORG-Setup is due to subscriber missed calls or early disconnects and wrong
dialing.
In XXMSC1 area the wrong dialing ratio is high. Call testing is required to identify the missing routes.
Page | 33 of 90
In this audit it is observed that in the areas where the MT-SUCC% is low the major cause of degradation is low
paging success rate. Relationship of MT-SUCC% and MT-Subscriber unreachable is also presented to give a
picture of radio coverage impact of MT calls.
Page | 34 of 90
4.5
4.5.1
Retain-ability
Inter MSC Handover /Intra-MSC Handover
This performance indicator reflects the successful incoming and outgoing inter-MSC handover attempts including
subsequent handovers. Events are counted for each neighboring MSC.
Observe in many directions the Inter MSS handover (In and out) success rates are low. The external LAC
definition needs to be verified by the help of radio team. In few cases the intra MSS handover is also low. This
should be checked by BSS team, because in intra MSS handover procedure MSS does not play any role.
Page | 35 of 90
5 FINDING
5.1
Roaming
The ROAMWARE version XXXX is using is only capable of retaining the users i.e., it will only hold the user which
are already on the XXXX network or after they are registered for the first time due to better radio coverage. This
is not helping to attract new incoming roamers registration in XXXX network.
In order to capture maximum number of incoming new roamers with priority to XXXX, newer version of
ROAMWARE should be used in which the capturing feature is available. (See Attached file for more detail).
5.2
5.2.1
Network synchronization deals with the distribution of common time and frequency references to all the nodes in
a network, in order to align the time and frequency scales of all the clocks employed in the network.
Time synchronization in particular ensures that all nodes share the same time reference, which is important for
charging and O&M functions. For example, it may be crucial to know exactly when (in terms of
day/hour/minute/second/millisecond) a certain event has occurred, so that events from different nodes can be
correlated. Event correlation is of fundamental importance not only for trouble shooting and charging but also
for services as the XXXX Revenue Assurance Solution.
Time synchronization is achieved through time servers, which provide Time-of-Day (ToD) information and deliver
it over an IP network to the clients, i.e., the network nodes, by means of the Network Time Protocol (NTP) or its
simplified version Simple Network Time Protocol (SNTP). (More details are available in attached file below)
REFERENCE1
0ETM2,MS-0
REFERENCE2
0ETM2,MS-1
REFERENCE3
GZNRBSC
0ETM2,MS-0
0ETM2,MS-1
EX,SB
HEBSC1
0ETM2,MS-0
0ETM2,MS-1
EX,SB
JABSC1
0ETM2,MS-0
0ETM2,MS-1
ABL,EX
JZNRBSC
0ETM2,MS-0
0ETM2,MS-1
EX,SB
KABSC1
0ETM2,MS-0
9ETM2,MS-0
EX,SB
KABSC2
0ETM2,MS-0
3ETM2,MS-0
EX,SB
KABSC3
0ETM2,MS-0
4ETM2,MS-0
EX,SB
KABSC4
0ETM2,MS-0
4ETM2,MS-0
EX,SB
STATE
EX,MBL
URC1 (NTP)
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
Page | 36 of 90
KABSC5
0ETM2,MS-0
1ETM2,MS-0
EX,SB
NEBSC1
0ETM2,MS-0
0ETM2,MS-1
EX,UPD
KHRBSC1
0ETM2,MS-0
0ETM2,MS-1
EX,SB
KUBSC1
0ETM2,MS-0
0ETM2,MS-1
EX,ABL
MABSC1
1ETM2,MS-0
3ETM2,MS-0
EX,SB
MABSC2
0ETM2,MS-0
4ETM2,MS-0
EX,SB
KDBSC1
1ETM2,MS-0
1ETM2,MS-1
EX,ABL
HLR1
0E1551,MS-0
0E1551,MS-1
SB,EX
HLR2
0E1551,MS-0
0E1551,MS-1
SB,EX
XXMSC3
XXMSC1
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
1E1551,MS-0
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
1E1551,MS-1
RCM-0
MBL,MBL,EX
XXMSC1
0E1551,MS-0
0E1551,MS-1
RCM-0
MBL,MBL,EX
XXMSC1
1E1551,MS-0
1E1551,MS-1
RCM-0
EX,SB,SB
XXMSC1
0E1551,MS-0
0E1551,MS-1
RCM-0
MBL,MBL,EX
XXMSC4
XXMSC
XXMSC
XXMSC1
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
NOT
CONNECTED
Page | 37 of 90
5.3
The recommended SAE utilization is between 40% - 50% during normal traffic behavior. If utilization persistently
high for a duration of more than a week, then SAE individual increment is advisable, Use Ericsson Formula in Alex
for Increment
SDATE
4/7/11
4/7/11
4/7/11
4/8/11
4/8/11
4/8/11
4/9/11
4/9/11
4/9/11
4/10/11
4/10/11
4/11/11
4/11/11
4/11/11
4/11/11
4/12/11
4/12/11
4/12/11
4/12/11
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
NODE
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
HLR
BLOCK
HMAPTC
HSUDAP2
HUEXAP2
HMAPTC
HSUDAP2
HUEXAP2
HMAPTC
HSUDAP2
HUEXAP2
HSUDAP2
HUEXAP2
HMAPTC
HSD
HSUDAP2
HUEXAP2
HMAPTC
HSD
HSUDAP2
HUEXAP2
SAE
500
500
500
500
500
500
500
500
500
500
500
500
786
500
500
500
786
500
500
SAE_Utilization
60%
67%
67%
50%
56%
56%
51%
56%
56%
53%
53%
52%
86%
59%
59%
54%
96%
62%
62%
Page | 38 of 90
SDATE
4/7/11
4/7/11
4/7/11
4/7/11
4/7/11
4/7/11
4/8/11
4/8/11
4/8/11
4/8/11
4/9/11
4/9/11
4/9/11
4/9/11
4/9/11
4/12/11
4/12/11
4/12/11
4/12/11
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
PM
NODE
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
JAMSC1
BLOCK
COMAIN
MMM
MRRM
MRRMH
MSCCO
SHMM
COMAIN
MMM
MRRM
MSCCO
COMAIN
MMM
MRRM
MSCCO
SHMM
COMAIN
MMM
MRRM
MSCCO
SAE
1130
1132
1139
1053
500
604
1130
1132
1139
500
1130
1132
1139
500
604
1130
1132
1139
500
SAE_Utilization
61%
60%
60%
58%
60%
59%
60%
58%
58%
58%
60%
59%
59%
59%
58%
59%
58%
58%
58%
PM
PM
PM
PM
PM
NODE
KAMSC1
KAMSC1
KAMSC1
KAMSC1
KAMSC1
BLOCK
SHEC
SHEC
SHEC
SHEC
SHEC
SAE
604
604
604
604
604
SAE_Utilization
72%
69%
70%
68%
72%
SDATE
NODE
BLOCK
4/11/11 7:00 PM KAMSC2 COHW
SAE
500
SAE_Utilization
54%
SDATE
4/7/11
4/8/11
4/9/11
4/10/11
4/11/11
4/12/11
BLOCK
UPPC4S
UPPC4S
UPPC4S
UPPC4S
UPPC4S
UPPC4S
SAE
500
500
500
500
500
500
SAE_Utilization
64%
60%
60%
60%
61%
64%
BLOCK
MSMMCAH
MSMMCAH
MSMMCAH
SAE
287
287
287
SAE_Utilization
51%
50%
51%
SDATE
4/7/11
4/8/11
4/9/11
4/11/11
4/12/11
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
7:00
PM
PM
PM
PM
PM
PM
NODE
KUMSC1
KUMSC1
KUMSC1
KUMSC1
KUMSC1
KUMSC1
SDATE
NODE
4/9/11 7:00 PM MAMSC1
4/10/11 7:00 PM MAMSC1
4/11/11 7:00 PM MAMSC1
Page | 39 of 90
SDATE
4/7/11
4/8/11
4/9/11
4/10/11
4/11/11
4/12/11
5.4
7:00
7:00
7:00
7:00
7:00
7:00
PM
PM
PM
PM
PM
PM
NODE
MSCS1
MSCS1
MSCS1
MSCS1
MSCS1
MSCS1
BLOCK
UPMHS4S
UPMHS4S
UPMHS4S
UPMHS4S
UPMHS4S
UPMHS4S
SAE
647
647
647
647
647
647
SAE_Utilization
56%
56%
56%
56%
56%
56%
Page | 40 of 90
Observation & Recommendation: Analysis of alternate routing case in XXMSC1, XXMSC2 and XXMSC3, There
is some branching not defined properly for over flow traffic.
Observed occurrence of EOS codes in XXMSC1, XXMSC1, XXMSC1 and XXMSC1. The reason for the errors is
improper CIC assignment which includes Cross Connections of E1s, due to this the subscriber received Wrong
(ambiguous) calls and Cross Talk. To rectify the issue it is recommended to check all Interconnect routes
individually with TCTDI command to make sure all CIC are integrated properly
Page | 41 of 90
5.5
Analysis of routing data leads to the conclusion that the switching equipment congestion (resources not utilized
optimally) is due to the incorrect Echo Canceller settings. These setting will also adversely contribute to increased
processor load and excessive use of ECs in other switches which will degrade the performances other connected
switches.
With the recommended setting mentioned below users will observe improved voice call quality with no delay.
5.6
B Number Table
In Analysis of B Number Table of all MSCs, all parameters were found correctly defined with the exception of
XXMSC3 where there should be no Charging Case on Announcement Route
The Value should be set as below:
ANBSI:B=99-8,RC=94,L=4;
ANBSI:B=99-9,RC=95,L=4;
5.7
Announcement Data
In the analysis announcement route highly congested and blocked devices were found in XXMSC1, XXMSC1 and
XXMSC1.
In order to reduce congestion all blocked devices should be fixed and more HW to be added. This will increase
the QOS for the subscriber
Page | 42 of 90
Page | 43 of 90
5.9
Page | 44 of 90
In this section the comparison of MSC and BSS defined cells is presented. The main objective of this practice was
to identify the extra cells defined on the MSC & to remove the junk data for making space available in cells table
and to organize cells tables. Mentioned below is the list of cells which are identified as extra on MSC by
comparing with BSS data.
Notice:
Please do not dilute any cell from the MSC side prior to the final confirmation from BSS Team. BSS should double
check the traffic on these cells. The cells ID dilution should take place with the cooperation of BSS and NSS
teams.
Page | 45 of 90
MSC NODE
XXMSC1
HRT084A
HEBSC1
HRT084B
HEBSC1
HRT084C
HEBSC1
HRT085A
HEBSC1
HRT085B
HEBSC1
HRT085C
HEBSC1
KNR009A
BSC1JA
KNR009B
BSC1JA
KNR009C
BSC1JA
SMN023C
MABSC1
KBL211X
KABSC3
KBL211Y
KABSC3
KBL261C
KABSC3
KBL261A
KABSC3
KBL261B
KABSC3
KBL261C
KABSC3
Table 7: Unused Cell ID Definitions
XXMSC1
XXMSC1
XXMSC
XXMSC
BSC NODE
System log defined in all MSCs is of fixed size which eventually results in loss of data after reaching its maximum
limit because the new data coming is over written on the previous data. Therefore it is recommended to define
transfer queue for direct data transfer to the OSS in order to avoid data loss.
The Signaling error reports from the nodes were analyzed after which it was concluded that data coming from the
nodes have some necessary information missing which help in identifying/rectifying the problem occurred. The
missing information issue is resolved for accurate fault fixing in future. (See attached file)
Analysis of Alarms on the APG leads to the fact that on some nodes the APG Drive is almost full, and once it is
completely filled the APG will be down and no statistical data will come forward thus no performance reports
could be generated for the management of the network. Therefore it is recommended to have proper
maintenance of the APG drive.
Page | 46 of 90
A lot of unused route data is defined in BSCs as well in the MSCs. This results in High CP load and increased Call
Setup Time. To avoid this situation this data should be removed and proper size alteration to be done for
enhanced CP performance.
Page | 47 of 90
System Build
IPA
Missing Corrections
BGNRBSC
GZNRBSC
HEBSC1
JABSC1
JZNRBSC
KABSC1
KABSC2
KABSC3
KAMSC4
KABSC5
KDBSC2
KHRBSC1
KUBSC1
MABSC1
MABSC2
NEBSC1
21230/33
21230/33
APG40
APG40
08B
08B
10
10
21250
21230/33
21230/33
21230/33
21230/33
21250
21250
21250
21250
21230/33
21230/33
21250
21230/33
APG43
APG40
APG40
APG40
APG40
APG43
APG43
APG43
APG43
APG40
APG40
APG43
APG40
08B
08B
08B
08B
08B
08B
08B
08B
08B
08B
08B
08B
08B
10
10
10
10
10
10
10
10
10
10
10
10
10
Page | 48 of 90
6 SIGTRAN
6.1
Out of Blue packets are received with correct format, right checksum,
but the receiver is not able to identify the association to which the packet belongs.
Those packets will be discarded.
Node Name
XXMMS3
XXMSC4
XXMSC
XXMSC
XXMSC1
11
Table 9: SIGTRAN-1
6.2
Node Name
Asso. Unavail.
(sec.)
Object
XXMSC3
12
55
M3_NI2_XXMSC
XXMSC4
XXMSC
XXMSC
16
67
XXMSC1
M3_NI2_XXMGW11
Page | 49 of 90
6.3
Node Name
Dest. Unreach.
(sec.)
XXMSC3
3033
121639
XXMSC4
375
14007
XXMSC
162
14575
XXMSC
160
11606
Node Name
Routing Errors
XXMSC3
4994181
XXMSC4
135894
XXMSC
127
XXMSC
XXMSC1
965390
Table 12: SIGTRAN-4
Recommendation: Check Event Record properly, Time out somewhere in the network
Page | 50 of 90
7 M-MGW KPI
Page | 51 of 90
7.1
Scope
This study cover the request of XXXX for list the KPI needed on M-MGW. It can be used for:
7.2
Introduction
XXXX has M-MGW R5 on ATM backbone and the KPI suggested in this study are relative to ATM network and MMGW R5.
Normally the KPI used in MGW are:
In addition to these KPI mentioned above it is important to know also the traffic/load.
Page | 52 of 90
MSC
M-MGw
AddReq
AddReq received
Step counter termReq
Check licensed capacity
Accessibility
(internal)
Ratio of successful
Termination
reservations/term.
No
Ok?
requests
Yes
Reserve internal
resources
AddRsp (NOK).
Rsp?
No
Ok?
Yes
NOK
AddRsp (OK).
Respond to MSC
OK
Bearer establishment
Step counter external
accessibility failure.
Release resources.
NotifyReq
No
Ok?
Yes
Through connected.
(QoS related counters
are stepped.)
NotifyReq
NotifyReq?
Yes
No
Accessibility
(external)
Integrity
(BER/BLER/..)
Retainability
Failure*
Normal**
SubReq**
Ratio of mature
released connections/
all connections
SubRsp (OK).
1000
999
997
996
Connection attempts
I.e. AddReqs
Successful attempts
I.e AddRsp OK
Bearer establisments
OK =>accessibility
(external)
997/999*100% = 99,8%
=>accessibility
(internal) = 99,9%
Example case of KPI calculation. Note that successive measurement is based on number of connections
that have reached that particular phase.
Page | 53 of 90
Accessibility
Retainability
Retainability should it be just one KPI that cover the following measurement:
Internal Retainability measurement
Measurement starts after external bearer is up i.e. where external accessibility ends.
Considers failures of internal resources e.g. MSB or ET in MGw that lead to that call is disconnected
abnormally.
External retainability
GCP commands that are replied with error code due to external failure.
can be left on lower priority as those can be assumed to be covered by other nodes contributing the network
retainability.
Integrity
The integrity is the ability of an external connection to maintain requested service at desired quality.
Traffic load
This category provides information about the current status of a node, mainly from resource usage point of view.
Following items should be considered for daily measurement:
Page | 54 of 90
The following KPI should be considered for check the traffic during special events (High Traffic) or after some
network change.
7.3
The internal accessibility is the ability to obtain requested service from the system between the reception of a
GCP Add message and the sending of a GCP AddReply message.
This KPI can be used for example monitoring the utilization and congestion rate of resources.
MGW Accessibility
MGW11
MGW21
MGW31
99.35%
92.95%
99.57%
Page | 55 of 90
7.4
Check if the event 80 % Capacity Limit Met for Media Stream Channels or the event 100 % Capacity
Limit Met for Media Stream Channels is issued.
Check software capacity licenses.
Analyze the following PIs to see if the problem concerns ATM, IP or TDM traffic, AAL2 Termination
Seizure Success Rate, IP Termination Seizure Success Rate and TDM Termination Reservation Success
Rate.
Identify and redimension (if possible) the congested resources in the node.
Check the status of related resources and devices.
Check the counter MgwApplication.pmNrOfRejsByStaticAdmCtrl.
This chapter specifies the PIs for external accessibility that are supported by the M-MGw. The external
accessibility is the ability to obtain requested service from the system between the sending of a GCP AddReply
message and the completion of a bearer setup.
The major KPI to monitor is Incoming AAL2 Connection Reservation Success Rate:
The Incoming AAL2 Connection Reservation Success Rate measurement is used for calculating the incoming AAL2
connection reservation success rate initiated by the adjacent node. This measurement is made for AAL2 Access
Point (Aal2Ap).
Successful Rate in AAL2AP
MGW11
MGW21
MGW31
100%
100%
100%
7.5
Page | 56 of 90
MGW11
Aal2 Rejection = 16466
Aal2 Request = 15917054851
Aal2 Termination success Rate = 99.98%
Healthy value range: 99.7 100%
MGW21
Aal2 Rejection = 13202
Aal2 Request = 3245811935
Aal2 Termination success Rate = 99.95%
Healthy value range: 99.7 100%
MGW31
Aal2 Rejection = 52290
Aal2 Request = 13450554991
Aal2 Termination success Rate = 99.96%
Healthy value range: 99.7 100%
7.6
MGW11
TDM Rejection = 2247053
TDM Request = 24816959645
TDM Termination success Rate = 99.09%
Healthy value range: 99.7 100%
MGW21
TDM Rejection = 7057901
Page | 57 of 90
7.7
7.8
MGW11
Nb Init Fault = 0
Nb Init
= 4486564122
MGW21
Nb Init Fault = 0
Nb Init = 75132256
Nb Connection Initialization Success Rate= 100 %
Healthy value range: 99.7 100%
MGW31
Page | 58 of 90
Nb Init Fault = 0
Nb Init = 5027045203
Nb Connection Initialization Success Rate= 100 %
Healthy value range: 99.7 100%
7.9
MGW11
Stream Channels Rejection= 0
Stream Channel request = 35791661320
Channel Seizure Success Rate = 100%
Healthy value range: 99.7 100%
MGW21
Stream Channels Rejection= 0
Stream Channel request = 14008237011
Channel Seizure Success Rate = 100%
Healthy value range: 99.7 100%
MGW31
Stream Channels Rejection= 0
Stream Channel request = 24743543905
Channel Seizure Success Rate = 100%
Healthy value range: 99.7 100%
Page | 59 of 90
MGW11
Call Attempt = 5614692755
Call Rejection = 0
Message composition success Rate = 100%
Healthy value range: 99.7 100%
MGW21
Call Attempt = 3095522565
Call Rejection = 0
Message composition success Rate = 100%
Healthy value range: 99.7 100%
MGW31
Call Attempt = 4019940232
Call Rejection = 0
Message composition success Rate = 100%
Healthy value range: 99.7 100%
MGW11
Succ Out Conns Remote Qos ClassA= 3922201
UnSucc Out Conns Remote Qos ClassA=2087
Aal2 connection success rate = 99.94%
Page | 60 of 90
MGW21
Data Not Available
MGW31
Succ Out Conns Remote Qos Class A= 2543085
UnSucc Out Conns Remote Qos ClassA= 2069
Aal2 connection success rate = 81.29%
7.13 Retainability
It shall be possible to measure retainability on a M-MGw node level. In addition it shall be ensured that external
faults and problems, independent from M-MGw, are excluded from M-MGw retainability result.
The external part is can be left on lower priority as those can be assumed to be covered by other nodes
contributing the network retainability.
Note: the core network level retainability shall be measured in MSC server.
The Service Retainability measurement shows the M-MGw ability to retain the services, once obtained, for the
desired duration. The measurement is made for physical M-MGw.
Reatinabilty
MGW11
MGW21
MGW31
100%
100%
100%
Page | 61 of 90
pmNrOfGcpNotifyCsdFaultAEst
The total number of encountered Circuit Switched Data (CSD) termination faults after bearer establishment
(between establishment of bearer and reception of Gateway Control Protocol (GCP) Sub, resulting in the sending
of a GCP Notify message towards the MGC.
Condition: The counter is incremented when a notify message is sent for CSD calls (both internal and external
reasons counted) between establishment of bearer and GCP Sub (tear down of connection).
pmNrOfGcpNotifySpeechFaultAEst
The total number of encountered speech termination faults after bearer establishment (between
establishment of bearer and reception of Gateway Control Protocol (GCP) Sub that result in the sending of a GCP
Notify message towards the Media Gateway controller (MGC).
Condition: The counter is incremented when a notify message is sent for speech calls (both internal and external
reasons counted) between establishment of bearer and GCP Sub (tear down of connection).
7.14 Integrity
The integrity is the ability of an external connection to maintain requested service at desired quality.
It shall be possible to measure integrity on a M-MGw node level. Even though it might be difficult to get an
objective view on what level of integrity (=quality of service) is still normal and acceptable M-MGw shall have
indicators for data handling quality.
The possible measures integrity on a connection type level are:
Page | 62 of 90
PI Integrity
Healthy
99,9%
99,9%
99,9%
99,9%
99,9%
99,9%
Traffic over ATM, except broadband signalling, is left out since quality related measurements on ATM would
cause considerable high load on the node.
Due to the same reason all current ATM quality supervision measurements have to be set ON separately and
number of them is limited. Besides, ATM is considered very reliable and robust and would not be meaningful to
be monitored (except when building up the network or debugging specific problems).
7.14.1 SS7 over ATM QoS
The SS7 over ATM QoS measurement is used for calculating the SS7 broadband signalling quality (over ATM). It
shows the ratio of successfully handled signalling packets. The measurement is made for physical M-MGw.
Formulas
SS7 Broad Band Signalling Quality
MGW11
MGW21
MGW31
99.99%
99.99%
100%
Page | 63 of 90
The SS7 over TDM QoS measurement is used for calculating the incoming and outgoing SS7 narrowband
signalling quality (over TDM). It shows the ratio of successfully handled signalling packets. The measurement is
made for physical M-MGw.
Narrow Band Signalling Quality
MGW11
MGW21
MGW31
99.97%
99.98%
99.98%
Page | 64 of 90
MGW11
MGW21
MGW31
MGW21
MGW31
MGW21
MGW31
95.97%
100%
99.99%
7.14.6 SCTP
Page | 65 of 90
Number of SCTP packets received from the peers, with an invalid checksum
MGW11
MGW21
MGW31
0
MGW11
MGW21
MGW31
Not Zero
Not Zero
MGW21
MGW31
Not Zero
Not Zero
MGW11
MGW21
MGW31
MGW11
MGW21
MGW31
0.0328
0.0030
0.0034
Page | 66 of 90
MGW
Sent
Receive
Cong
MGW11
420059165.5
381350197.8
1.67
MGW22
207794070.8
202341239.7
MGW33
425233858.3
413335803
Here Congestion is not the formula but it is calculated on average basis, so very slight congestion in MGW11 it is
ignorable as it in peak hours only, but recommendation is to increase the association. It was observed quite
often ,the disturbance in the IP backbone. Mention below is the time when disturbance was seen in MGW11 and
MGW22
MGW21(Time)
'20110317001500
'20110317003000
'20110317004500
'20110317010000
'20110317011500
'20110317013000
'20110317014500
'20110317020000
'20110317021500
'20110317023000
'20110317024500
'20110317030000
'20110317031500
'20110317033000
'20110317034500
'20110317040000
'20110317041500
'20110317043000
'20110317044500
'20110317050000
'20110317051500
'20110317053000
Sent
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Receive
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
MGW11(Time)
'20110317001500
'20110317003000
'20110317004500
'20110317010000
'20110317011500
'20110317013000
'20110317014500
'20110317020000
'20110317021500
'20110317023000
'20110317024500
'20110317030000
'20110317031500
'20110317033000
'20110317034500
'20110317040000
'20110317041500
'20110317043000
'20110317044500
'20110317050000
'20110317051500
'20110317053000
Sent
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Receive
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Page | 67 of 90
'20110317054500
'20110317060000
'20110317061500
'20110317063000
'20110317064500
'20110317070000
'20110317071500
'20110317073000
'20110317074500
'20110317080000
'20110317081500
'20110317083000
'20110317084500
'20110317090000
'20110317091500
'20110317093000
'20110317094500
'20110317100000
'20110317101500
'20110317103000
'20110317104500
'20110317110000
'20110317111500
'20110317113000
'20110317114500
'20110317120000
'20110317121500
'20110317123000
'20110317124500
'20110317130000
'20110317131500
'20110317133000
'20110317134500
'20110317140000
'20110317141500
'20110317143000
'20110317144500
'20110317150000
'20110317151500
'20110317153000
'20110317154500
'20110317160000
'20110317161500
'20110317163000
'20110317164500
'20110317170000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
'20110317054500
'20110317060000
'20110317061500
'20110317063000
'20110317064500
'20110317070000
'20110317071500
'20110317073000
'20110317074500
'20110317080000
'20110317081500
'20110317083000
'20110317084500
'20110317090000
'20110317091500
'20110317093000
'20110317094500
'20110317100000
'20110317101500
'20110317103000
'20110317104500
'20110317110000
'20110317111500
'20110317113000
'20110317114500
'20110317120000
'20110317121500
'20110317123000
'20110317124500
'20110317130000
'20110317131500
'20110317133000
'20110317134500
'20110317140000
'20110317141500
'20110317143000
'20110317144500
'20110317150000
'20110317151500
'20110317153000
'20110317154500
'20110317160000
'20110317161500
'20110317163000
'20110317164500
'20110317170000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Page | 68 of 90
'20110317171500
'20110317173000
'20110317174500
'20110317180000
'20110317181500
'20110317183000
'20110317184500
'20110317190000
'20110317191500
'20110317193000
'20110317194500
'20110317200000
'20110317201500
'20110317203000
'20110317204500
'20110317210000
'20110317211500
'20110317213000
'20110317214500
'20110317220000
'20110317221500
'20110317223000
'20110317224500
'20110317230000
'20110317231500
'20110317233000
'20110317234500
'20110318000000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
'20110317171500
'20110317173000
'20110317174500
'20110317180000
'20110317181500
'20110317183000
'20110317184500
'20110317190000
'20110317191500
'20110317193000
'20110317194500
'20110317200000
'20110317201500
'20110317203000
'20110317204500
'20110317210000
'20110317211500
'20110317213000
'20110317214500
'20110317220000
'20110317221500
'20110317223000
'20110317224500
'20110317230000
'20110317231500
'20110317233000
'20110317234500
'20110318000000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Healthy
0-80%
NA
0-80%
Page | 69 of 90
PI Traffic optional
Healthy
M-MGW Node
0-80%
NA
NA
NA
NA
NA
NA
Q.2630
AAL2 Pipe Utilization Rate
0-80%
GCP
See RefError!
Reference source not
found.
SCCP
SCCP Policing
SCCP Relay
NA
MTP3/MTP3b/M3UA
NA
NA
Page | 70 of 90
MTP2
MTP2 Signalling Link Usage
0-80%
SCTP
NA
NA
AAL2
Number of Busy AAL2 Terminations
NA
ATM
Received and Transmitted ATM Cells per Second on an ATM Port
NA
NA
NA
NA
NA
NA
0-80%
0-80%
0-80%
IP
Number of Busy IP terminations
NA
NA
NA
NA
NA
Page | 71 of 90
Ethernet Interface)
Number of Received and Sent IP Datagrams for SS7 over IP (Gigabit
Ethernet Interface)
NA
NA
NA
NA
TDM
TDM Termination Group Utilization Rate
NA
Page | 72 of 90
MGW11
MGW21
MGW31
56 %
99.62%
64.32%
Page | 73 of 90
MGW21
MGW31
55.89%
99.70%
59.82
MGW21
MGW31
99.99%
99.89
99.99%
COUNTER
256505
256505
MGW21
MGW31
17.02
15.59
16.67
Page | 74 of 90
MGW21
MGW31
0.99
0.99
0.99
Healthy value range: while the relative difference (NrOfSentMessages / ReceivedMessages) is not changing
significantly between different measurements.
Value in healthy range no action required
7.15.5 MTP2 Link usage
The MTP2 Signaling Link Usage measurements are used to show the number of received and sent Message Signal
Units (MSUs) per second, as well as kbps, during the measurement period. The measurement is made for
signaling link.
MGW11
Received
Sent
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc2
950744.60
936077.79
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc0
950881.59
936071.61
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc2
950806.33
936138.88
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc0
950943.35
936132.47
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc2
950870.25
936202.23
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc1
950939.71
936072.26
951007.46
936195.77
Mtp3bSpItu=3-4121,Mtp3bSls=3-
Page | 75 of 90
4200_27,Mtp3bSlItu=3-4200_slc0
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc2
950934.80
936265.73
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc1
951003.15
936135.81
Mtp3bSpItu=3-4121,Mtp3bSls=34200_27,Mtp3bSlItu=3-4200_slc0
951071.71
936259.06
MGW31
Received
Sent
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc3
678397.49
673986.69
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc1
678426.09
674006.83
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc3
678444.72
674033.70
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc1
678473.05
674052.26
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc3
678490.42
674079.21
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc1
678519.10
674097.53
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc3
678536.12
674124.59
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc1
678564.51
673980.82
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc3
678581.20
674142.05
Mtp3bSpItu=3-4120,Mtp3bSls=3-4204-1,Mtp3bSlItu=34204_slc1
678609.56
674169.19
Page | 76 of 90
MGW22
Receive
Sent
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301030.09
403715.10
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301039.49
403735.61
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301052.57
403763.61
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301060.23
403781.02
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301068.13
403798.68
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301075.64
403815.37
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301083.12
403831.99
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301091.04
403849.47
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301099.20
403867.80
Mtp3bSpItu=2-4122,Mtp3bSls=24400,Mtp3bSlItu=Slc0
301106.78
403885.00
This sample is taken for top10 send and receive links it can be seen only one or 2 link being used In case if only
these link are there then further link should be added, in case of more link are available then load sharing should
be enable in local and remote node .
7.15.6 Mtp3b Link usage
Load sharing should be implemented from local side and the remote side .It was observed other SLCs does not
have any traffic at all
Link congestion recorded in MGW11
Mtp3bSpItu=2-4121,Mtp3bSls=2-4105_30,Mtp3bSlItu=2-4105_slc1
1768
Page | 77 of 90
Mtp3bSpItu=2-4121,Mtp3bSls=2-4105_30,Mtp3bSlItu=2-4105_slc1
1768
Mtp3bSpItu=2-4121,Mtp3bSls=2-4105_30,Mtp3bSlItu=2-4105_slc1
L
i Mtp3bSpItu=2-4121,Mtp3bSls=2-4105_30,Mtp3bSlItu=2-4105_slc1
n Mtp3bSpItu=2-4121,Mtp3bSls=2-4105_30,Mtp3bSlItu=2-4105_slc1
k
congestion Recorded in MGW21
1768
Mtp3bSpItu=3-4122,Mtp3bSls=3-4202,Mtp3bSlItu=Slc0
391
Mtp3bSpItu=2-4122,Mtp3bSls=2-4400,Mtp3bSlItu=Slc0
391
Mtp3bSpItu=2-4122,Mtp3bSls=2-4400,Mtp3bSlItu=Slc0
391
Mtp3bSpItu=2-4122,Mtp3bSls=2-4400,Mtp3bSlItu=Slc0
391
Mtp3bSpItu=2-4122,Mtp3bSls=2-4400,Mtp3bSlItu=Slc0
391
141
Mtp3bSpItu=2-4120,Mtp3bSls=2-4122,Mtp3bSlItu=Slc0
141
Mtp3bSpItu=2-4120,Mtp3bSls=2-4122,Mtp3bSlItu=Slc0
141
Mtp3bSpItu=2-4120,Mtp3bSls=2-4122,Mtp3bSlItu=Slc0
141
Mtp3bSpItu=2-4120,Mtp3bSls=2-4122,Mtp3bSlItu=Slc0
141
Mtp3bSpItu=2-4120,Mtp3bSls=2-4122,Mtp3bSlItu=Slc0
141
Page | 78 of 90
1768
1768
MGW11
MGW21
MGW31
22.62%
22.16%
17.07%
MGW11
MGW21
MGW31
39.05%
20.41%
53.93%
MGW11
MGW21
MGW31
100%
100%
100%
Page | 79 of 90
MGW11
Time
Board
Pload
1545
Subrack=1Slot=11PlugInUnit=1
53
1415
Subrack=1Slot=6PlugInUnit=1
54
1430
Subrack=1Slot=6PlugInUnit=1
59
1400
Subrack=1Slot=6PlugInUnit=1
61
MGW21
Time
Board
Pload
1545
Subrack=1,Slot=10,PlugInUnit=1
23
1415
Subrack=1,Slot=10,PlugInUnit=1
22
1515
Subrack=1,Slot=10,PlugInUnit=1
22
1530
Subrack=1,Slot=10,PlugInUnit=1
22
MGW31
Time
Board
Pload
1400
Subrack=3,Slot=2,PlugInUnit=1
49
1415
Subrack=3,Slot=2,PlugInUnit=1
49
1400
Subrack=4,Slot=3,PlugInUnit=1
48
1400
Subrack=4,Slot=2,PlugInUnit=1
48
Page | 80 of 90
Decreased traffic handling capacity of overloaded resources, which may eventually result in restarts.
H.248 Load Control function may be activated, making the MSC server rerouting traffic to other VMGws in
other nodes.
Event Overload in VMGw Pool is issued when there is an overload situation in a VMGw pool.
Page | 81 of 90
Page | 82 of 90
TRH Overload
It has been noticed that mostly TRH overload problems are due to under dimensioning of the TRHs, ie. too many
TRXs per TRH. Although the recommended load levels for TRHs are given, LAPD signaling can also affect the load
handling efficiency of the TRH, and this must be considered when dimensioning the BSC.
The main contributors to the loading of the TRHs are: processing of the paging messages, processing of the
measurement reports from the MSs, signalling caused by call handling, processing of the location updates and
processing of the SMS messages. If the traffic intensity and/or level becomes too high, the TRHs could become
overloaded
Objectype LAPD counters
'CLINKFAIL' (Link failure)
'COVERLOAD' (Link overload)
Page | 83 of 90
Recommendations:
Dimensioning rules are allowing utilization 30% load in a non-failure situation and 60% load in a load in
a failure situation.
It is very important that load limits are followed, as when the SS7 links reaches a certain load level, the
message success rate decreases dramatically.
This load limit is a function of the message length (Location Updates to being one of the worst)
Page | 84 of 90
This command is used to initiate a printout of the transcoder pool data for one, several or all defined transcoder
pools. Most RNOTRA should be equal to POOLACT, if not, the number of TRA demux devices should be checked
again
<RRTPP:TRAPOOL=ALL;
RADIO TRANSMISSION TRANSCODER POOL DETAILS
TRAPOOL CHRATE SPV RNOTRA POOLACT POOLIDLE POOLTRAF
AMRHR
HR
SUBPOOL
3456
3456
1293
2163
3456
1293
2163
FR
SUBPOOL
3456
3456
2611
845
3456
2611
845
HR
SUBPOOL
768
768
708
60
768
708
60
FR
768
744
744
744
END
Check TRA supervision definition:
RRISP:TRAPOOL=ALL;
This command is used to initiate a printout of transcoder pool idle level supervision data for one, several or all
defined transcoder pools. Each limit has its own alarm class. The given alarm class is assigned to limit 2. Limit 1
Page | 85 of 90
is assigned to the nearest alarm class below the alarm class of limit 2. If the alarm class A2 is given in the
command, limit 1 will be assigned to alarm class A3. This means that limit 2 is a more serious limit.
The limits are given as a percentage of the required number of transcoder resources in the transcoder pool.
Values given for reference:
TRAPOOL
ACL
LIM1
LIM2
FR
A2
20
10
<RRISP:TRAPOOL=ALL;
RADIO TRANSMISSION TRANSCODER POOL IDLE LEVEL SUPERVISION DATA
TRAPOOL SUPSTATUS ACL LIM1 LIM2
AMRHR OFF
EFR
OFF
HR
ON
A2
FR
ON
A2
END
2
2
1
1
RRMSP:TRAPOOL=ALL;
This command is used to initiate a printout of transcoder pool mean hold time supervision data for one, several or
all transcoder pools.
The alarm level for a transcoder pool is a percentage of the transcoder pool mean hold time. If the mean hold
time for any of the transcoder resources in the transcoder pool falls below the current pool alarm level the RADIO
TRANSMISSION TRANSCODER POOL MEAN HOLD TIME SUPERVISION alarm is issued. We suggest that ALPERC
be 40 in most cases.
<RRMSP:TRAPOOL=ALL;
RADIO TRANSMISSION TRANSCODER POOL MEAN HOLD TIME SUPERVISION DATA
TRAPOOL SUPSTATUS ACL ALARMLEV ALPERC
AMRHR
OFF
EFR
OFF
HR
ON
A1
20
FR
ON
A1
20
END
Page | 86 of 90
Documentation
During the process of information gathering it was found that there is no centralized database available for
reference, which comprises of all the details and information regarding the network. The information available
was scattered and most of the time it was incomplete. It is recommended to have standard documentations for
large networks like XXXX, this will not only help to track as well facilitate the process of network planning,
optimization and operations & maintenance. In order to built the documentation database Aircom recommends
XXXX to ask the vendor for documented details for the following.
Page | 87 of 90
Aircom generated all the KPIs manually by extracting the raw data reports from the APG and processing them
according to the Ericsson standard formula for the audit purposes. This KPIs generation process was very time
consuming.
Lack of training:
On interviewing/discussing it was realized that the daily activities and procedures followed by the XXXX team are
not efficient and productive. As an example there are no periodic report generated automatically by performance
tool for the Busy Hour, the way this BH performance is taken into account by the XXXX team is inaccurate and
have maximum probability of errors; this is because they are calculating it manually. Besides this after
understanding the procedures followed by XXXX team in details it was concluded that they require proper training
for troubleshooting and tackling the problem occurring in the network. Currently the way the problems are being
handled it is doubted that the root cause for problem occurred can be traced quickly.
9.2
Procedures
Aircom interacted with the XXXX team and developed understanding of processes and procedures
followed.
9.3
The XXXX does not have a dedicated Planning and Optimization team of its own. The entire planning and
design activities are conducted by the vendor and this has a drawback that provides it provides maximum
privileges to the vendor for the BOQs and makes the vendor itself is a demand generating organization.
Besides this in this process networks secret information is disclosed to the vendor as it extensive
knowledge about the network.
Currently KPI Reporting for core is done with the help of excel sheet and besides this the KPI information
provided in them are not complete thus cannot be used extensively for analysis. In addition to it is very
difficult to maintain/retrieve the records from excel sheets. Currently all the KPIs available with XXXX are
provided by the vendor only when demanded as XXXX is completely dependent on the vendor and cannot
carry out its maintenance and optimization processes individually.
Recommendations
1. SCTP Associations & Signaling links: : Observed one LIP (Local IP) caring high unit of SCTP
association load and other LIP caring small load unit, this is unbalance of signaling load. As the signaling
load is not balanced a complete through redesign for signaling aspects of core network is required, in
which all signaling should optimally dimensioned
2. Over dimensioned HLR/VLR: to improve the performance of the HLR reconciliation should be done for
the VLR performance route optimization activity to be performed. In addition to better performance of
Page | 88 of 90
these network elements these process will help to save the expansion cost to meet the commercial
demands.
3. Planning and Design Team: XXXX should built an experienced design, planning and optimization team
in place dedicated to evaluate network status, planning, design and dimensioning to meet future network
expansion requirements and optimally used the current available hardware resources best suited to the
interest of XXXX network.
4. Performance Management Tool: It is strongly recommended that all Core Network KPIs and
counters should be available in the performance management tool. This will speed up the maintenance
process and most importantly a true picture of network performance can be seen at different levels.
5. Technical Training of Employees: Aircom recommends that XXXX work force should be organized
according to industry best practice. And all relevant staff shall be trained in specific domains. The below
mentioned specialized team are of pivotal importance in any organization:
10 CONCLUSION
The above document has been prepared in order to serve as a reference document mentioning all the control
points in Core network in terms of process failure and (or) in terms of Configuration and dimensioning.
Care has been taken to report the issues in terms of factual data, after applying all standard calculation, wherever
applicable.
Purpose of this document is to be shared as a knowledge base, and act upon all the Recommendations
mentioned.
Page | 89 of 90
11 APPENDIX
In this appendix the files are attached with flowing detail.
C7 Link Detail for XXXX Core Network
Sigtran Link Detail for XXXX Core Network
MSC/BSC Cell Miss Mach Data
Roaming Documentations
C7 Link NBL Overload
C7 Link HSL Overload
EOS error codes and SAE congestion
Core KPI Detail Sheet
Preventive maintenance for Core Network
Page | 90 of 90