Guidelines For ASR Improvement Security Level

Guidelines for ASR Improvement
Security Level
Contents
1 2 Purpose Scope
3 Reasons of ASR DIP and Solutions 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 4 5 6 Dual Seizure Circuit Status EOS(End of Selection) MSC Utilization B Table routing POI Trunk route Utilization Subscriber behavior Release cause
Counter for ASR: Requirement for Analysis Recommendations
2012-06-25
Huawei Proprietary - Restricted Distribution
Page2, Total23
Security Level
Purpose
This document describes the guidelines for Selecting the ASR Strategy for a Network keeping in View the Traffic Profile of the Network.
Scope
This document describes the guidelines for Selecting the ASR Strategy keeping in view the Traffic Profile of the Network and ASR capacity of different interface in the Network.
Reasons of ASR DIP and Solutions

The Answer Success Rate can be optimize by adjusting the Call Answer strategy through the following parameters:
Dual Seizure Equipment Congestion Circuit Channel Call Rejection -
2012-06-25
Page3, Total23
Security Level
3.1 Dual Seizure

Dual seizure substitutes in ASR dip as the call may fail. The calls that are failing due to Dual Seizure will be recorded in the field DUAL SEIZURE_CV44 in the performance measurement task Failure Reason Traffic. If the field is 0 then, it implies no call failing due to Dual Seizure though in the TKGRP Outgoing Traffic you can find lot of Dual Seizure. The call failing happens only if the time for IAM/IAI message time outs in the CIC reselection process (In case of non-controlling or salve Dual Seizure) or in IAM/IAI sending delay (In case of controlling or Master Dual seizure). For eg: If MSC A is configured as controlling office and MSC B as non-controlling office then if MSC B sends an IAM message to MSCA while its is trying to send the IAM message using the same CIC then MSC A will reject the IAM/IAI message from MSC B. MSC B will then try to select another free CIC towards MSC A for sending the IAM/IAI message. This is called controlling Dual Seizure with respect to MSC A and non-controlling Dual Seizure with respect of MSC B. For non-controlling Dual Seizure the fields DUAL SEIZURE TIMES SLAVE and TK RETRY TIMES are increased by 1. However in case of controlling Dual Seizure as there is no circuit reselection involved only the DUAL SEIZURE TIMES MASTER field is increased by 1 for every controlling Dual Seizure not the TK RETRY TIMES filed like non-controlling Dual Seizure. Huawei MSCs are designed to retry 5 times after dual seizure happens. Actually the circuit reselection times isnt confined by any protocol constraint and is open for the vendor. This CIC reselection times isnt controlled by any software parameter or timer. It is defined while coding the software of MSC i.e. CIC reselection is controlled as an embedded function of MSC and cant be modified through timer or software parameter. Screen shot for Dual seizure details as per ITU standards attached below .
2012-06-25
Page4, Total23
Security Level
2012-06-25
Page5, Total23
Security Level
3.2 Circuit Status
Primary status: Not installed, faulty, manually blocked, peer blocked, idle, and busy Combined status: Peer manually blocked, manually blocked and faulty, peer blocked and faulty, manually blocked in the busy hour, peer blocked in the busy hour, and peer manually blocked in the busy hour Basic principles and illustration of circuit status: Except for not installed, other states can be combined; only idle circuits can turn to busy; the manual blocking and peer blocked options can be applied to busy circuits, and calls will not be affected; when faults occur, a busy circuit releases calls immediately and enters into faulty status. The original book status and coexistence of busy and faulty states do not exist any more. Major state transitions are illustrated in the following figure:
2012-06-25
Page6, Total23
Security Level
B_FAULT HWOK
HWOK
B_UNINSTALL
OAM BLOCK
B_OAM _BLOCK
B_IDLE
PEERBLOCK
B_PEER_BLOCK
OAM BLOCK BOOK PEER-BLOCK OAM BLOCK
B_OAM _PEER_BLOCK
B_BUSY_OAM _BLOCK
B_BUSY
PEERBLOCK
B_BUSY_PEER_BLOCK
OAM BLOCK PEER-BLOCK
B_BUSY_OAM _PEER_BLOCK
When faults occur on the circuit, three combined faulty states will be added
B_IDLE
HWFAULT
B_FAULT
B_OAM _BLOCK
HWFAULT
B_OAM_BLOCK_FAULT
B_PEER_BLOCK
HWFAULT
B_PEER_BLOCK_FAULT
B_OAM _PEER_BLOCK
HWFAULT
B_OAM_PEER_BLOCK_FAULT
B_BUSY
HWFAULT
B_FAULT
B_BUSY_OAM _BLOCK
HWFAULT
B_OAM_BLOCK_FAULT
B_ BUSY_PEER_BLOCK
HWFAULT
B_PEER_BLOCK_FAULT
B_ BUSY_OAM_PEER_BLOCK
HWFAULT
B_OAM_PEER_BLOCK_FAULT
2012-06-25
Page7, Total23
Security Level
3.2.1
Collecting Basic Information

Use the following MML commands on the MSOFTX3000 to collect only the information about the circuits in faulty status a certain BSC: LST MGW, DSP MGW: MGW-related configuration information and the status of each MGW LST MCLNK, DSP MCLNK: Configuration information and status of the H248 link LST N7LNK, DSP N7LNK: Configuration information and status of the BSC destination signaling point LST ACPOOL: Configuration information of circuit pools LST AIETG,N7TG: Configuration information of A-interface and POI trunk groups LST TKC,N7TKC: Circuit configuration information. Select YES to all options. LST CIC: Circuit configuration information on each module LST BSC: Configuration information of the processing modules reaching a certain BSC DSP AIETKC,N7TKC: To query A-interface and POI circuit status. Use the parameter A-interface and POI circuit number, which can be queried using the LST TKC command. DSP OFTK: To make statistics on A-interface and POI circuit status by office Save all these results and Check.
2012-06-25
Page8, Total23
Security Level
Use the following MML commands on the UMG8900 to collect only the information about the circuits in faulty status on a certain BSC: DSP VMGW: VMGW configuration information and status DSP H248LNK: H248 link configuration information and status DSP E1PORT: E1 port configured or not LST TDMIU: VMGW correctly configured or not for the E1 link with specific TID DSP TDMSTAT: Timeslots normal or not LST TDMSPC: If there is a semi-permanent connection, use the DSP TDMSPC command. Save all these results and Check.
2012-06-25
Page9, Total23
Security Level
3.3 3.3.1
EOS(End of Selection) Definition:
For every failed call one End of Selection is generated by the switch with respect to the reason of the failure of the call.
3.3.2
KPI Target:
The End of Selection should be as minimum as possible and should be consistent for every circle.
3.3.3

Reasons of High EOS(End of Selection):

Incorrect Definition of EOS(End of Selection) Table. Incorrect mapping of announcement with EOS(End of Selection) Table. C7 Signaling Congestion Trunk route congestion. Failures due to subscriber reasons.
3.3.4

Improvement Plans:
EOS(End of Selection) should be analyzed on daily basis. In case of some major variation in EOS(End of Selection) for a particular circle, the reason for the same should be analyzed and RCA(Route Cause Analysis) for the same should be get. Service Quality report or Traces can be used to get the EOS(End of Selection) for a particular time, but the trace should not be used if there is not any major problem and without the consultation of Back Office.
3.4
MSC Utilization
2012-06-25
Page10, Total23
Security Level
3.4.1
Definition:
MSC Utilization is the utilization of all the MSC w.r.t to to its designed value in Erlang at a specific Processor Load in busy hour. This parameter is calculated for Busy Hour.
3.4.2
KPI Target:
MSC Utilization should be equal to or less than ----------%.
3.4.3
Formula:
MSC Utilization% = 100*Switch NBH Traffic(Erls) / Switch Capacity (Erls)
3.4.4
Reasons of High MSC Utilization:

Trunk route Congestion. Internal Congestion Hardware fault. Delay in MSC Deployment as per plan. Uneven distribution of BSCs traffic for the MSCs. Wrong forecast of subscriber behavior. Subscriber abnormal behavior.
Transit Traffic. 3.4.5 Improvement Plans:

All the BSCs should be evenly distributed to MSCs as per the BSC Traffic. No. of BTS should be evenly distributed to MSCs as per the Traffic. Trunk route utilization should not go above ------% and there should not be any congestion in the trunk route
2012-06-25
Page11, Total23
Security Level
There should not be any internal congestion in the switch. 3.5 POI Trunk route Utilization 3.5.1 Definition:
Trunk route Utilization is the Utilization of the circuits(Time Slots) in a given route w.r.t. to No. of Available circuits(Time Slots) in that route. This parameter is calculated for Busy Hours.
3.5.2
KPI Target:
Trunk route Utilization should be equal to or less than 70%
3.5.3
Formula:
Trunk route Utilization% = No. of circuits(Time Slots) Utilized / No. of Available circuits(Time Slots)
3.5.4
Reasons of High Trunk route Utilization:

POI Connectivity issue Transmission Media Unavailability Trunk route Dimensioning is not optimized and the Load is not evenly distributed to routes as per traffic requirement.
3.5.5
Improvement Plans:
Trunk route dimensioning should be done properly and the load should be distributed as per traffic requirement. POI Connectivity issue and Transmission Media unavailability situation should be avoided by taking the preventive action before the crises situation arises.
2012-06-25
Page12, Total23
Security Level
3.6 B-Table Routing
Check the routing of NLD/ILD and Local calls as per routing priority
All codes to be routed as per routing plan Delete all the unnecessary codes from the switch Alternate routes to be defined in MSC wherever applicable Split the level where required e.g. 033-3 -Routed to RIL NLD and 022-4 Routed to BTSOL Fixed the length of the codes(Min - Max Value ) Time Based routing can be implemented for congested routes, if possible Put all major codes under observation
2012-06-25
Page13, Total23
Security Level
3.7 Subscriber behavior

Calling party Subscriber disconnect the call Dialing patterns -Check all the dailing patterns Called party Subscriber not Answer the call Called party Subscriber Make busy the call
3.8 Release cause

S.N. Cause code Release cause
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
2012-06-25
CAUSE013 CAUSE014 CAUSE015 CAUSE016 CAUSE019 CAUSE020 CAUSE023 CAUSE025 CAUSE027 CAUSE030 CAUSE031 CAUSE038 CAUSE042 CAUSE043 CAUSE044 CAUSE045 CAUSE060 CAUSE062 CAUSE070 CAUSE075 CAUSE083 CAUSE093 CAUSE097 CAUSE098
switch equipment congestion no dialing in long time no answer in long time temporary failure no alerting in long time no release in long time exceed maximum reattempt times release before answer switch equipment failure ST BUSY SL BUSY Exchange Route Error remote equipment congestion call failure dual seizure invalid directory number CPU congestion or overload no CCB resource partial dial time out signalling error no A interface circuit call release time out of call limitation time termination apply error
Page14, Total23
Security Level
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
CAUSE100 CAUSE105 CAUSE107 CAUSE108 CAUSE110 CAUSE129 CAUSE130 CAUSE131 CAUSE133 CAUSE134 CAUSE137 CAUSE145 CAUSE146 CAUSE147 CAUSE149 CAUSE151 CAUSE155 CAUSE156 CAUSE158 CAUSE166 CAUSE169 CAUSE170 CAUSE172 CAUSE175 CAUSE186 CAUSE209 CAUSE210 CAUSE216 CAUSE219 CAUSE230 CAUSE239 CAUSE254
callee do not exist do not dial area code when call local Subscriber mobile callee is busy callee power off dial 0 when call PLMN user in other area unallocated DN no route to the selected transit network no route to the callee dial wrong prefix of long distance call route unacceptable preemption circuit reserved for reuse user decide to busy no response from callee no answer from callee call rejected no free circuit termination error invalid DN format response to status enquiry network error temporary error device congestion no route or circuit applied available no resource available no available bearer capability invalid call reference route identified do not exist incompatible terminal invalid transit network selection recovery of time out protocol error interwork
2012-06-25
Page15, Total23
Security Level
4 Counter for ASR: ASR (Answer to Seizure Ratio)

Formula: ( Incoming Traffic over A Interface Trunk Groups (Answer Times) +Outgoing Traffic over A Interface Trunk Groups (Answer Times) ) / (Incoming Traffic over A Interface Trunk Groups (Seizure Times ) + Outgoing Traffic over A Interface Trunk Groups (Seizure Times ) Trunk Group Traffic (MCA Call Attempt) ) * 100
4.1
Incoming Traffic over A Interface Trunk Groups (Answer Times)
4.1.1 Description This measurement entity counts the number of times mobile originated (MO) calls are answered. It provides a basis for calculating the call answer rate about which carriers are concerned.
4.1.2 Application Scenario When you need to analyze the call answer rate and call answer traffic, create a measurement task with this measurement entity to count the number of answered MO calls. 4.1.3 Measurement Point In an MO call flow, the measurement is performed when the MSCa receives the Connect message from the callee or the ANM message from the peer office. For details, see Figure 1. For a multi-connection call, supplementary measurement is performed. For example, in an intraMSC call flow, subscriber A calls subscriber B and the A-B call is connected. If subscriber A holds the A-B call and calls subscriber C and subscriber C is alerted, the MSC adds the answer times counted in the A-C call to that counted in the A-B call. For details, see Figure 2.
Figure 1 Measurement point of Answer Times
2012-06-25
Page16, Total23
Security Level
Figure 2 Supplementary measurement point of Answer Times
4.2
Outgoing Traffic over A Interface Trunk Groups (Answer Times)
4.2.1 Description This measurement entity counts the number of times the 2G mobile terminated (MT) calls are answered, when the MSC receives the Connect message from the callee. It provides a basis for calculating the call completion rate about which carriers are concerned.
4.2.2 Application Scenario
When you need to analyze the call completion rate and call completion traffic, create a measurement task with this measurement entity to count the number of answered 2G MT calls.
4.2.3 Measurement Point
In a 2G MT call flow, the measurement is performed when the MSC receives the Connect message from the callee. For details, see Figure 1. For a multi-connection call, supplementary measurement is performed. For example, in an intraMSC call flow, subscriber A calls subscriber B who has subscribed to the call waiting (CW) service and the A-B call is connected. Then, if subscriber C calls subscriber B and subscriber B answers the calls, the MSC adds the number of answered calls counted in the A-C call to that counted in the A-B call. For details, see Figure 2.
2012-06-25
Page17, Total23
Security Level
Figure 1 Measurement point of Answer Times
Figure 2 Supplementary measurement point of Answer Times
4.3
Incoming Traffic over A Interface Trunk Groups (Seizure Times )
4.3.1 Description
This measurement entity counts the number of times the circuits in the A-interface incoming trunk group are seized during the mobile originated (MO) calls.
4.3.2 Application Scenario
This measurement entity counts the number of seize the circuits in the A-interface incoming trunk group during the 2G MO calls. Create a measurement task with this measurement entity when you need to learn the number of times the access bearer is seized in different traffic models.
4,3.3 Measurement Point
In a 2G MO call flow, the MSC hunt a circuit in the A-interface incoming trunk group successfully. Then, the measurement is performed. For details, see Figure 1.
2012-06-25 Huawei Proprietary - Restricted Distribution Page18, Total23
Security Level
For a multi-connection call, supplementary measurement is performed. For example, in an intraMSC call flow, subscriber A calls subscriber B and the A-B call is connected. If subscriber A holds the A-B call and calls subscriber C and subscriber C is alerted, the MSC adds the seizure times counted in the A-C call to that counted in the A-B call. For details, see Figure 2.
Figure 1 Measurement point of SEIZURE TIMESSeizure Times
Figure 2 Supplementary measurement point of SEIZURE TIMESSeizure Times
4.4
4.4.1
Outgoing Traffic over A Interface Trunk Groups (Seizure Times )

Description
This measurement entity counts the number of times circuits in the A-interface outgoing trunk group are seized during the 2G mobile terminated (MT) calls. The measurement is performed when the MSC successfully prepares the terrestrial resources.
2012-06-25
Page19, Total23
Security Level
4.4.2
Application Scenario
This measurement entity counts the number of seize the circuits in the A-interface outgoing trunk group during the 2G MT calls. Create a measurement task with this measurement entity when you need to learn the number of times the access bearer is seized in different traffic models.
4.4.3 Measurement Point
In a 2G MT call flow, the MSC hunt a circuit in the A-interface outgoing trunk group successfully. Then, the measurement is performed. For details, see Figure 1. For a multi-connection call, supplementary measurement is performed. For example, in an intraMSC call flow, subscriber A calls subscriber B who has subscribed to the call waiting (CW) service and the A-B call is connected. Then, if subscriber C calls subscriber B and subscriber B is alerted, the MSC adds the seizure times counted in the A-C call to that counted in the A-B call. For details, see Figure 2.
Figure 1 Measurement point of Seizure Times
Figure 2 Supplementary measurement point of Seizure Times
2012-06-25
Page20, Total23
Security Level
5 Requirement for Analysis Reports required for analysis is given below

S.N. 1 2 3 4 5 6 7 8 9 10 11 Details POI Report BICC / SIP report A-Interface Report Ater interface Report All Link utilization report Signaling report EOS Report MSC Hourly report C7 traffic report Source DATA Capacity report Dest code report
Logs required for analysis is given below
S.N. 1 2 3 4 5 6 7 8 9
Details Circuit Selection detail ALL Circuit detail Announcement mapping Dump Signaling circuits detail Command Logs Event Logs Alarm Logs Call logs
CP load
2012-06-25
Page21, Total23
Security Level
Traces required for analysis is given below
S.N. 1 2 3 4 5
Details POI Sig Traces BICC/SIP Sig Trace C7 Sig Trace A,C,D Interface Traces Looping
Configuration Data required for analysis is given below

S.N. 1 2 3 4 Details B-Table dump New Augmentation Details MSC Dump Circuit Seizure/Hunting detail for both END
Connecting Node detail required for analysis is given below

S.N. 1 2 3 4 Details Code Routing Plan Routine change tracker GT Dump STP LRN dump STP
2012-06-25
Page22, Total23
Security Level
6 Recommendations
Identification of major rejection causes for outing call failures Audit of MSC- As per the action plan Circuit selection mode should be kept as per the standards at both POI ends in order to avoid call failure due to dual EOS and Announcement mapping must be done as per the NOC guidelines, make sure correct announcements are Remove congestion on all the POIs Start Dest Code monitoring on top 25 codes Further identification of low ASR codes/Routes and modification of routing plan Removal of crank bank feature on local POIs Time based routing of low ASR codes identify the codes rejected with release cause and check the route and take up with the concerned operator
2012-06-25
Page23, Total23

Guidelines For ASR Improvement Security Level

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guidelines For ASR Improvement Security Level

Uploaded by

Copyright:

Available Formats

Guidelines for ASR Improvement

Counter for ASR: Requirement for Analysis Recommendations

Huawei Proprietary - Restricted Distribution