HSS9860 KPI Analysis and Optimization

HSS9860 KPI Analysis
and Optimization
www.huawei.com
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Describe the definitions of the service running quality
KPIs for the HSS9860
 Describe the methods of assessing the service running q
uality KPIs for the HSS9860
 Describe the ideas for assessing and optimizing the ser
vice running quality KPIs for the HSS9860

Page3
Contents
1. KPI Analysis Overview
2. Analysis of SRI Success Rate
3. Analysis of Authentication Success Rate
4. Analysis of Location Update Success Rate
5. Analysis of SMS SRI Success Rate
6. Successful Response Rate of ULR Messages
7. Successful Response Rate of AIR Messages
8. Successful Response Rate of IMS Messages

Page4
Overview
Service Quality
Service Location update success rate
Accessing
SRI routing success rate
SMS routing success rate
Provide roaming number success rate
Insert subscriber data success rate
GPRS location update success rate
Cancel location success rate
SMS alert success rate
Supplementary service operation success rate
Service Authentication success rate
Security

Page5
General Methods of Analysis
Check the alarm
– for all KPIs contents in the alarm
browse window
Alarm&Capability
assessment
Calculate the success

rate based on
Compared Lower than measurement indexes
with the the baseline Traffic statistics
baseline value -> assessment
value Optimization
Select all the user
interfaces by creating a user
interface trace task
User interface
trace assessment
Data configuration
assessment
Log assessment

Page 7
Contents

Page7
Definition of SRI Success Rate
 SRI success rate is a key index for measuring the ser
vice access of mobile networks, and directly reflects
the access capabilities of mobile networks.
 Calculation formulas
SRI success rate = ((Operation requests - Operation abort - Operation tim
eout - Unknown subscriber - Roaming not allowed - System failure - Data m
issing - Unexpected data value - Call barred - Forwarding violation - CUG
Reject - Absent subscriber)/Operation requests) x100%
A (Excellent) B (Acceptable) C (Fair) D (Poor) E (Very Poor)

98% 96% 92% 90% < 90%

Page8
Definition of SRI Success Rate
Index Name SRI success rate
Index The proportion of SRI requests processed successfully by HLR
definition
Index Measurement Unit MAP Operation Measurement
collection Measurement Object SendRoutingInformation (15)
Measurement Index Operation Requests
Operation Abort
Operation Timeout
Unknown Subscriber
Roaming not Allowed
System Failure
Data Missing
Unexpected Data Value
Call Barred
Forwarding Violation
CUG Reject
Absent Subscriber

Page9
Definition of SRI Success Rate (Co
nt.)
GMSC HLR VLR
PSTN
IAI
MAP_SEND_ROUTING_INFORMATION
MAP_PROVIDE_ROAMING_NUMBER
MAP_PROVIDE_ROAMING_NUMBER
ack
MSC MAP_SEND_ROUNTING_INFORMATION
ack
IAI

Page10
Definition of SRI Success Rate (Co
nt.)
Network Gateway
MSC HLR VLR
IAM
MAP_SEND_ROUTING
INFORMATION MAP_PROVIDE_SUBSCRI
MSC BER INFORMATION
MAP_PROVIDE_SUBSCRI
BER INFORMATION ack
MAP_SEND_ROUTING
INFORMATION ack
MAP_SEND_ROUTING
INFORMATION MAP_PROVIDE_ROAMING
NUMBER
MAP_PROVIDE_ROAMING
NUMBER ack
MAP_SEND_ROUTING
INFORMATION ack
IAM
Intelligent Subscribers

Page 6
Alarm Assessment
 Based on various link failure alarms and resource overload alarm, determi
ne whether resources are insufficient. The alarms to be noted are as foll
ows:
 TDM Networking IP Networking
Alarm ID Alarm Description Alarm ID Alarm Description
1701 MTP DSP Inaccessible 1809 M3UA Link Congestion
1705 MTP Link Failed 1811 M3UA Link Fault
1707 MTP Buffer Congestion 1815 M3UA Route Unavailable
1709 MTP L2 Congestion 1817 M3UA Destination Entity
Inaccessible

Page12
Log Check
 Log in to the PGW client and run the LST LOG command
 Check whether operation log(within 1 week) contain SET MAPCONF and SET MAPSERV
configuration.
Check whether these operations are correct.
Example, the COMAP parameter controls whether the calling number is contained on the MAP layer in the
roaming number retrieval request message. If this parameter is set to FALSE, unexpected data is returne
d for all the calls that contain the calling number.

Page13
Tracing & Traffic Statistics Analysis-Failure
GMSC HLR VMSC
SRI request message
TeleserviceNotProvisioned LST TS/BS in PGW client

command to check whether the
user subscribes to the related voice
BearerServiceNotProvisione service.
d
MOD ODBIC to unsubscribe from the ODB
CallBarred
incoming call barring for the user.
Powers off and powers on the MS again to

AbsentSubscriber re-initiates a location update
User trace NoRoamingNumberAvailable VLR problem

TCAP User trace
SCCP DPC trace SystemFailure HLR internal processing is incorrect.

Page14
Case
 Problem Description
After an office is cut over, certain services are blocked during the call test.
 Analysis
 1. MAP Operation Measurement Result Analysis
 Authentication message routing success rate - Normal
 SMS routing success rate - Normal
 SRI message success rate decreases to 80% - System Failure.
 Roaming number success rate decreases to 80% - Message Timeout.
Therefore, the cause for SRI message failure is that the roaming number retrieval proc
ess (child process of the SRI process) failed.
 2. Analyze alarms
a large number of CPU overload alarms - GUFEU board (BSG Module 220)
Other GUFEU boards are in normal state

Page15
Case(Cont.)
 CPU Usage Measurement and Link Traffic Measurement - FE
 CPU Usage Measurement task
 CPU Usage 85% - Board of module 220
 CPU Usage 5% - Other boards
 Link Traffic Measurement of the FE Boards
 There are 2 TDM 2M links in total.
 After cut over, Link load increases to 0.2 ERL (normal)
 Check Configuration, both of the 2M links are configured on module 220.
- The board load is unbalanced.
 As a result, the load of the board (running module 220) exceeds the threshold after cutover, an
d therefore certain messages are discarded.
 Solution
Distribute the link load equally to all the service boards. After that, all the services are in
normal state during the dialing test, and the problem is solved.

Page16
Contents

Page17
Definition
 Authentication is an important security measure taken on 2G/3G n
etworks to prevent unauthorized users from accessing the networks
, and prevent the private data of authorized users from being sto
len by unauthorized users. Authentication success rate helps unde
rstand the security status of services on networks.
 Calculation formulas
Successful authentications = Operation requests - Operation abort - Operation timeo
ut - Unknown subscriber - System failure - Data missing - Unexpected data value
Authentication success rate = Successful authentications / Operation requests x 100
%

99% 98% 95% 90% < 90%

Page18
Definition (Cont.)
Index Name Authentication success rate
Index The ratio of authentication requests processed
definition successfully by HLR.
collection Measurement SendAuthenticationInfo (26)
Object
Operation Abort
Operation Timeout
Unknown Subscriber
System Failure
Data Missing

Page19
GSM Authentication
A B D
MS BS MSC VLR HLR
MAP_PROCESS_ACCESS_REQUEST
MAP_UPDATE_LOCATION
MAP_SEND_AUTHENTICATION_INFO
MAP_SEND_AUTHENTICATION ack
MAP_AUTHENTICATE
MAP_AUTHENTICATE ack
MAP_SET_CIPHERING_MODE
CIPHER_MODE_COMMAND
CIPHER_MODE_COMPLETE

Page20
WCDMA Authentication

Page21
VLR/SGSN HLR
Authentication request
LST KI to check whether the KI

UnknownSubscriber
data of the user exists.
Illegal data in the message

UnexpectedDataValue recieved, and therefore cannot be
processed by the HLR.
The data in the message sent by

DataMissing the remote NE is incomplete.
User trace The HLR internal processing is
TCAP User trace SystemFailure
incorrect.
SCCP DPC trace

Page 24
Check Signaling Data Configuration
 When to check the Signaling Data Configuration
 Response to the "SendAuthenticationInfo process" message is not found on the SCCP la
yer
 What to check
focus on the following points:
 Check whether the GT data configuration on the SCCP layer is correct
 Check whether the SSN data configuration on the SCCP layer is correct.

Page23
Check Authentication Parameter
 Incorrect authentication parameter configuration is a common caus
e for authentication failure.
 Check Global Parameters If the parameter is set to
TRUE, Phase3 is not degraded
Configuration Parameter Name
to Phase2.
Command
SET MAPCONF SUPPAUTHPHASE3:
whether to support The value of this parameter must
authentication requests be consistent with the setting on the
of version 2/3 MSC.
SET MAPCONF AKSWITCH:
authentication
encryption switch MAP Phase 3
Authentication Request
initiated by the VLR/SGSN

Page24
Check Authentication Parameter
 Check whether authentication parameter configuration is consistent with MS.
 Check whether the network encryption is enabled.(The protocol requires 3G network encryption.)
Algorithm Applicable Parameter Required Algorithm

Type Card Type by Algorithm Configuration
COMP128_1 SIM None ADD KI
COMP128_2
COMP128_3
CUSTOM_1 USIM Custom r1–r5
Custom c1–c5
Parameter Configuration
XOR SIM None Name Command
MILENAGE SIM and r1–r5 and c1–c5 K4 ADD K4
USIM
KI ADD KI
OP or OPc ADD OP/ADD KI
Case: 3G network encryption Card type: SIM or ADD KI
Some NEC MSs do encryption. USIM
Some MOTO MSs do not do encryption.

Page 30
Case
 Problem Description
Assessment of traffic statistics (3 days’ statistics), More than
1000 authentication failure reports are generated per hour.
 Optimization Methods
 Check the device health status
 Trace analysis
 Check signaling data configuration
 Check authentication parameter configuration

Page26
Case (Cont.)
 Processing
 Check the device health status: OK (device panel, service panel, alarm subsystem)
 Trace analysis:
HLR sends a quintuplet (Failed user3G user) for authentication.
-----------For normal user, HLR sends a triplet for authentication.(2G user)
Conclusion: failed users are 3G users located on 2G networks
 Check signaling data configuration: OK (The SAI process is in normal state)
 Check authentication parameter configuration
According to the protocol, when 3G users roam to 2G networks, authentication is based on a trip
let. The HLR, however, sends a quintuplet. Analysis of the authentication request message from
MSC/VLR shows that the MSC/VLR initiates an SAI request of the MAP3 version. If the MSC/VLR ini
tiates an SAI request of the MAP3 version, the HLR sends a quintuplet to the MSC/VLR.(failed: M
SC/VLR(2G) need the reply of triplet)
 Solution
Set the MAP version of the MSC to MAP2 so that the MSC initiates an authentication request messag
e of the MAP2 version.

Page27
Contents

Page28
Definition
 Calculation formulas are as follows:
Number of successful location updates = Operation Requests - Operation Abort - Oper
ation Timeout - Unknown Subscriber - Roaming Not Allowed - System Failure - Data Mi
ssing - Unexpected Data Value
Success rate of location update = (Successful location updates / Location update re
quests) x 100%
 The following table lists the baseline values of location update success rate defin
ed by Huawei.
98% 96% 92% 90% < 90%

Page29
Definition (Cont.)
Index Name Location update success rate
Index The proportion of location update requests processed
definition successfully by HLR.
collection Measurement UpdateLocation (0)
Object
Operation Abort
Operation Timeout
Unknown Subscriber
Roaming not Allowed
System Failure
Data Missing

Page30
Location Update Process
A B D
MS BSS MSC VLR HLR
G D
PVLR
A_LU_REQUEST MAP_UPDATE_
LOCATION_ARE
A MAP_SEND_IDENTIFICATION
MAP_SEND_IDENTIFICATION
ack
MAP_UPDATE_LOCATION
MAP_CANCEL_
LOCATION
MAP_CANCEL_
LOCATION ack
MAP_INSERT_SUBSCRIBER_
DATA
MAP_INSERT_SUBSCR._DAT
A ack
MAP_UPDATE_LOCATION_AR
MAP_UPDATE_ EA ack
LOCATION_AREA
A_LU_CONFIRM ack

Page 38
VLR/SGSN HLR
Location update request message
IMSI not defined

Unknown subscriber Deregistered SIM card
Comparing with the

normal stream Unexpected data value LST DYNSUB
LST NONSUPHND
Roaming not allowed LST HLRRR

LST CSI LST VSRR
LST ODBDAT LST VSLIST
LST LICENSE LST RSZI
System LST RRTPL
failure
See Chapter 2
Same as SRI

Page 41
Contents

Page33
Definition
 Calculation formulas are as follows:
 Number of successful SMS routings = Operation Requests - Operation Ab
ort - Operation Timeout - Unknown Subscriber - Roaming Not Allowed -
System Failure - Data Missing - Unexpected Data Value - Called Barred
- Absent Subscriber
 SMS routing success rate = Number of successful SMS routings / Number
of SMS routing requests x 100%
The following table lists the baseline values of SMS routing success rate
defined
A by Huawei
(Excellent) B (Acceptable) C (Fair) D (Poor) E (Very Poor)
99% 98% 95% 90% < 90%

Page34
Definition (Cont.)
Index Name SMS routing success rate
Index The proportion of SMS routing requests processed successfully
definition by HLR.
collection Measurement Object SendRoutingInfoForShortMessage (22)
Operation Abort
Operation Timeout
Unknown Subscriber
Roaming not Allowed
System Failure
Data Missing

Page35
Definition (Cont.)
MS MSC VLR HLR SMC
1.SEND_ROUTING_INFO_FOR_SM
2.SEND_ROUTING_INFO_FOR_SM_ACK
3.MT_FORWARD_SHORT_MESSAGE
4.SEND_INFOR_FOR_MT_SMS
5.PAGE/
SEARCH_FOR_MOBILE_SUBSCRIBER
6.Page
7.Page Response 8.PROCESS_ACCESS_REQUEST_ACK/

SEARCH_FOR_MOBILE_SUBSCRIBER_
ACK
9.SEND_INFO_FOR_MT_SMS_ACK
10.Short Message
11.Short Message
Acknowledgement
12.MT_FORWARD_SHORT_MESSAGE_ACK

Page36
Related Data Configuration
 Service data check items
Table Name Query Command

SMS Configuration Information table LST MAPCONF/LST MAPSERV
Subscriber Information table LST TS/CBAR/LST ODBDAT
 Signaling data check items
Table Name Query Command

SCCP GT table LST SCCPGT
SCCP DSP table LST SCCPDSP
SCCP SSN table LST SCCPSSN

Page37
Trace Analysis for SMS Routing
 Log in to the OMU client, and choose Maintenance > Service > Tracing
> HSS9860 > User Message Trace > Subscriber 2G/3G/4G Message T
race to perform user message trace.
 The steps for identifying the problem are as follows:
 Step 1: Create a user interface trace based on the IMSI of the complaining user.
 Step 2: Perform dialing test to check whether the SMS routing request message can arri
ve at the D interface.
If the request message cannot arrive at the D interface, the problem is related to the M3
UA or SCCP layer, or the MSC. In this case, check whether the link load on the HLR is i
n normal state. If yes, analyze the MSC. If the request message can arrive at the D inter
face, go to step 3.

Page 66
Trace Analysis for SMS Routing(Cont.)
 Step 3: Analyze the response to the SMS routing message, and check the cause values
for the error in the response. The possible causes are as follows:
 systemFailure: After the gateway sends an MAP_SEND_ROUTING_INFO_FOR_SM request to th
e HLR, the session is aborted.
 dataMissing: The primitive does not contain the required parameters and data. An optional param
eter required in the context is missing.
 unexpectedDataValue: The related parameter and data in the primitive are of incorrect format. Th
e current context contains the parameter whose data type is correct, but whose value is incorrect,
or should not contain the parameter.
 facilityNotSupported: The location registration of the mobile subscriber indicates that the VLR/SG
SN on the VPLMN does not support the MT SMS.
 teleserviceNotProvisioned: The given subscriber does not subscribe to the SMS.
 absentSubscriber: The MNRF flag is set on the HLR, indicating that the subscriber is not in the se
rvice area.
 unknownSubscriber: The HLR cannot identify the MSISDN of the given subscriber, that is, the sub
scriber is not registered.

Page 66
SMC HLR
SEND_ROUTING_INFO_FOR_SM
IMSI not defined

Unknown subscriber Deregistered SIM card
Unexpected dataValue
Comparing with the
normal stream
DataMissing
Service not defined
TeleserviceNotProvisioned
MS Out of Service area
absentSubscriber
facilityNotSupported SM not supported by

VLR/SGSN
System
failure See Chapter 2
Same as SRI

Page 41
Contents

Page41
Successful Response Rate of ULR
Messages
 This measurement entity measures the ratio of ULR messages that the HSS
successfully responds with the ULA messages to total ULR messages received in a
measurement period.
 Formula:
Successful Response Rate of ULR Messages = Number of Successful ULA Messages/

Number of Received ULR Messages x 100%
 The baseline of the Successful Response Rate of ULR Messages is follows:
A B (Acceptable) C (Poor) D (Very poor) E (Unacceptable)

(Excellent)
99% 98% 95% 90% <90 ％

Page42
Successful Response Rate of ULR Me
ssages
Measurement Successful Response Rate of ULR Messages
Entity Name
Description This measurement entity measures the ratio of ULR messages that the HSS
successfully responds with the ULA messages to total ULR messages received in a
measurement period.
Related Counters Measurement Unit ULR and ULA Measurement
Measurement Object Diameter local entity ID
Measurement Entities •Number of Received ULR Messages

•Number of Sent ULA Messages
•Number of Successful ULA Messages
•Number of Unsuccessful ULA Messages
•Number of ULA Messages with DIAMETER
ERROR USER UNKNOWN
ERROR UNKNOWN EPS SUBSCRIPTION
ERROR ROAMING NOT ALLOWED
ERROR RAT NOT ALLOWED

Page43
Signaling Flow

Page44
Analysis on Failed Update Location
Messages
MME/S4SGSN SAE
Update Location Request

The IMSI is not defined int eh HSS
DIAMETER ERROR
or the SIM card has been
USER UNKNOWN
deregistered.
The EPS services have not been

DIAMETER ERROR
provided for the subscriber.
UNKNOWN EPS
SUBSCRIPTION
The subscriber is restricted from

DIAMETER ERROR
ROAMING NOT roaming to the area.
ALLOWED
Message tracing of
Diameter links DIAMETER ERROR The subscriber is not provided with
2G/3G/4G subscriber RAT NOT ALLOWED the ARD service.
message tracing

Page45
Case Analysis
Description
A subscribers at a site fails to attach to a network.
Analysis
1. View the traced messages. The error code contained in the ULA message is DIAMETER_UNABLE_
TO_DELIVER (3002). This fault occurs because the ULA message cannot be sent to the destination
host and therefore cannot be forwarded to other hosts.
2. Possible causes are as follows:
(1) The ULR message contains an incorrect host name.
(2) The ULR message does not contain a host name and instead, contains an incorrect realm name.
3. The ULR processing mechanism is as follows:
(1) If the ULR message contains a host name, the HSS first checks whether the host name is correct
. If yes, the HSS forwards the message to the related host without checking the realm name. If the h
ost name is incorrect, the HSS returns error code 3002.
(2) If the ULR message does not contain the host name, the HSS checks the validity of the realm na
me.

Page46
Case Analysis
Solution
 (1) On the SAE-HSS, check the configured HSS realm name and host name.
 (2) Check whether the realm name and host name contained in the ULR message are
consistent with that configured on the SAE-HSS. If no, modify the realm name and host
name on the MME.
 (3) On the MME, check whether the realm name added using ADD IMSIHSS is correct
and whether a host name consistent with that on the HSS is added.
Summary
 The host name may be incorrectly configured on the MME if a configuration file is used t
o configure the host name and the host name is not configured in the original configurati
on file.
 When modifying the host name or realm name at site, check that not only the Diameter l
ink configuration is modified, but the related parameters in the ADD IMSIHSS command
have been modified.

Page47
Contents

Page48
Successful Response Rate of AIR
Messages
 This measurement entity measures the ratio of AIR messages that the HSS
successfully responds with the AIA messages to total AIR messages received in a
measurement period.
 Formula:
Successful Response Rate of AIR Messages = Number of Successful AIA Messages/

Number of Received AIR Messages * 100%
 The baseline of the Successful Response Rate of AIR Messages is as follows:
A (Excellent) B C (Poor) D (Very poor) E

(Acceptable) (Unacceptabl
e)
99% 98% 95% 90% <90 ％

Page49
Successful Response Rate of AIR Me
ssages
Measurement Successful Response Rate of AIR Messages
Entity Name
Description This measurement entity measures the ratio of AIR messages that the HSS
successfully responds with the AIA messages to total AIR messages
received in a measurement period.
Related Counters Measurement Unit AIR and AIA Measurement
Measurement Object Diameter local entity ID
Measurement Entity Number of Received AIR Messages
Number of Sent AIA Messages
Number of Successful AIA Messages
Number of Unsuccessful AIA Messages
Number of AIA
Messages with DIAMETER ERROR USER UNKNOWN
Number of AIA
Messages with DIAMETER ERROR UNKNOWN EPS S
UBSCRIPTION
Number of AIA
Messages with DIAMETER ERROR MISSED
PARAMETE
Number of AIA Messages with
DIAMETER_AUTHORIZATION_REJECTED
Number of AIA Messages with
DIAMETER_AUTHENTICATION_DATA_UNAVAILABLE

Page50
Signaling Flow

Page51
Analysis on Failed Authentication Infor
mation Request
MME/S4SGSN SAE
AIR
The IMSI is not defined in the HSS

DIAMETER ERROR or the SIM card has been
USER UNKNOWN deregistered.
The EPS service is not provided for

DIAMETER ERROR UNKNOWN the subscriber.
EPS SUBSCRIPTION
An IE is lost in the service message.

DIAMETER ERROR
MISSED PARAMETE
Message tracing of Diameter links HSS rejects to authenticatie the

2G/3G/4G subscriber message tracing DIAMETER_AUTHORI
SIM card attempting to access an
ZATION_REJECTED
LTE network.
DIAMETER_AUTHE HSS fails to query the database.

NTICATION_DATA_
UNAVAILABLE
Page52
Case
Symptom
The response message to the AIR message contains DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION
(5420).
Cause and Verification

The subscriber is not a 3GPP subscriber or does not subscribe to the EPS services.
1. Log in to the PGW and run LST SUB to check whether the user type is 3GPP or non-3G
PP.
2. Run LST OPTGPRS and check whether the subscriber has APN information.
Solution:
1. For a non-3GPP subscriber, perform either of the following two operations:
(1) Run MOD NAM to modify the network access mode.
(2) Run RMV SUB to delete the subscriber and run ADD SUB to add the subscriber.
2. If the subscriber does not have the APN information, run MOD OPTGPRS to add APN data
.
Page53
Contents

Page54
Successful Response Rate of IMS Reque
sts
 This measurement entity counts the success response rate of IMS messages.
 Formula:
Successful Response Rate of IMS Messages = Number of successful IMS Requests /

Number of IMS Requests × 100%
 The baseline of the Successful Response Rate of IMS Requests is as follows:
A (Excellent) B C (Poor) D (Very poor) E

(Acceptable) (Unacceptabl
e)
99% 98% 95% 90% <90 ％

Successful Response Rate of IMS Re
quests
Measurement Success Response Rate of IMS Requests
Entity Name
Description This measurement entity counts the success response rate of IMS messages.
Related Counters Measurement Unit Diameter Operation Measurement
Measurement Entity IMS-HSS
Measurement Entity •Successful Response Rate of LIR Messages

•Successful Response Rate of UAR Messages
•Successful Response Rate of MAR Messages
•Successful Response Rate of SAR Messages
•Successful Response Rate of SAR Messages
•Successful Response Rate of RTR Messages
•Successful Response Rate of PPR Messages
•Successful Response Rate of PUR Messages
•Successful Response Rate of UDR Messages
•Successful Response Rate of SNR Messages
•Successful Response Rate of PNR Messages

Page56
Signaling Flow 1

Page57
Signaling Flow 2

Page58
IMS Message Tracing and Analysis
1. View the measurement results and check whether t

he success response rate decreases.
2. Log in to the OMU client. On the Maintenance tab
, choose Service > Tracing > HSS9860 > User Int
erface Trace > Subscriber IMS Message Trace. Cr
eate a message tracing task and check the traci
ng result.
3. Determine the possible causes based on the traci
ng result.

Page59
IMS Message Tracing and Analysis
CSCF/ATS IMS-HSS
IMS service request
LST HSUB DIAMETER_ERROR_I Check the private and

LST HPSI DENTITIES_DONT_MA public user identities.
TCH
LST HVNTPL
DIAMETER_ERROR_
LST HVNTPLID Check the network
ROAMING_NOT_ALL
LST HVNTPLADDR template.
OWED
Data contained in the
LST DMPECAP User Data Cannot Be request is inconsistent
Modified with the service
LST permission in PGW.
HREGAUTH Authentication
LST HBAR Rejected The subscriber is barred.
Diameter link
No Response Communication
tracing between the HSS and
IMS user tracing the USCDB is
abnormal.
Page60
Case
Symptom
The LIA message contains an error indicating that the subscriber has not been defined for a subscriber define
d in the HSS.
Verification
1. Check whether the value of Number of Successful LIA Messages decrease.

2. Check whether the code contained in the LIA message sent from the HSS to the CSCF is 5003.
3. Run LST HDYNDATA to check the registration status of the subscriber.
Cause Analysis:
The causes for this fault are as follows:
(1) The value of the parameter CSCFDISASRSWITCH is 1.

(2) The LIR message contains the AVP Originating-Request whose value is 255.
(3) The tables H_TBLSBACKUPDATA and H_TBLSTDSBACKUPDATA on the HSS do not contain the C
SCF redundancy data.
Solution
(1) For a non-redundancy network, set CSCFDISASRSWITCH to 0.
(2) For a redundancy network, check the CSCF configuration and initiate a first registration process.

Page61
Summary
 KPI Analysis to improve the QoS
Traffic statistics
Performance assessment
Measurement Alarm&Capability
Monitoring assessment
Lower than
User interface
the baseline
trace assessment
value -> Data configuration
Optimization assessment
Log assessment
Page62
Thank you
www.huawei.com

HSS9860 KPI Analysis and Optimization

Uploaded by

Document Information

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

HSS9860 KPI Analysis and Optimization

Uploaded by

Copyright:

Available Formats

HSS9860 KPI Analysis

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Calculate the success

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

A (Excellent) B (Acceptable) C (Fair) D (Poor) E (Very Poor)

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

GMSC HLR VMSC

SRI request message

TeleserviceNotProvisioned LST TS/BS in PGW client

Powers off and powers on the MS again to

User trace NoRoamingNumberAvailable VLR problem

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

A (Excellent) B (Acceptable) C (Fair) D (Poor) E (Very Poor)

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

LST KI to check whether the KI

Illegal data in the message

The data in the message sent by

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Algorithm Applicable Parameter Required Algorithm

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

98% 96% 92% 90% < 90%

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Location update request message

IMSI not defined

Comparing with the

Roaming not allowed LST HLRRR

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

7.Page Response 8.PROCESS_ACCESS_REQUEST_ACK/

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Table Name Query Command

 Signaling data check items

Table Name Query Command

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

IMSI not defined

facilityNotSupported SM not supported by

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.