21/5/22 Security Level:

UMTS Full Parameter Check:

Check Rules + Cases + Tool +
Deliverables
Prepared by: UMTS Maintenance
Dept/UMTS Design Dept www.huawei.com
Reviewed by: Qi Haofeng

August 18, 2012

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Abstract

To support global UMTS office delivery and reduce the number of online problems caused by
incorrect parameter settings, the UMTS Maintenance Dept issues the UMTS Full Parameter
Check so that field engineers can check parameters in a routine manner to prevent problems
caused by incorrect parameter settings and field engineers, product support engineers, and R&D
personnel can improve the parameter check efficiency when handling online problems.
At present, 698 parameters are collected and sorted out, which cover 16 categories. The parameters
can be checked for their reasonableness, dependency, and consistency. The parameter check
tool can check most parameters. For details, see the UMTS Full Parameter Check Rule Table.
Most of the cases involved in this presentation slide do not go through parameter check first, and
parameter problems are found through analysis based on symptoms. We hope parameter check
to be performed first subsequently before performing other operations to improve the
troubleshooting efficiency. It takes much less time and energy to solve problems after parameter
check is performed first.
From now on, so long as problems are found, a few hours should be spent checking parameters first.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

R&D Support
For UMTS full parameter check rules and questions you may have
during use of the parameter check tool, the UMTS Maintenance Dept
provides training and 7x24-hour technical support services.

 R&D support personnel:

Name Supported Item Employee ID Tel Mailbox

Chen Requirement for parameter See Huawei phone

00159220 [email protected]
Yiwen check rules or tool book.

See Huawei phone book

Xie Meng Parameter check rules 00139580 [email protected]
.

Tool improvement See Huawei phone book

Sun Chao 00139690 [email protected]
(improvement/license) .

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Change History

Date Version Description Reviewer Author

Qi Haofeng, Zeng Yongjun, Tang Yuanxian, Cui
Chengxiao, Gong Jie, Zheng Jianhua, He Enhua, Chen
2012-8-11 1.0 Completed V1.0. Hu Wensu, Qian Jin, Liu Yingchun, Yang Bangquan, Yiwen, Xie
Chen Yiwen, Zhu Peng, Zhou Yang, Xia Da, Su Meng
Zhan, Xie Meng

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

Contents
A. Applicable Scenarios
B. Parameter Check Principle
C. Parameter Categories
01. Access core parameters 02. Call drop core parameters
03. PS data transmission core parameters 04. Voice quality core parameters
05. Network coverage core parameters 06. Paging core parameters
07. RF channel core parameters 08. Capacity core parameters
09. Peer vendor IUR parameters 10. Interoperability core parameters
11. Core network core parameters12. Transmission core parameters
13. Equipment core parameters 14. License core parameters
15. Terminal compatibility core parameters 16. Other core parameters
D. Tool
Tool guide
Manual check method
E. Appendixes
Maturity of function commercialization
Summary of deliverables

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Applicable Scenarios
 New network
 You are advised to use the baseline values and check parameters before
equipment are online to prevent low-level problems caused by incorrect
parameter settings.

 Swapped network
 Some parameters use the original network values mapped, and some use
baseline values. Check parameters before equipment are online to prevent low-
level problems caused by incorrect parameter settings.

 Legacy network
 You are advised to record parameter optimization and regularly check
parameters to prevent low-level problems caused by incorrect parameter settings.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

Contents
A. Applicable Scenarios
B. Parameter Check Principle
C. Parameter Categories
01. Access core parameters 02. Call drop core parameters
03. PS data transmission core parameters 04. Voice quality core parameters
05. Network coverage core parameters 06. Paging core parameters
07. RF channel core parameters 08. Capacity core parameters
09. Peer vendor IUR parameters 10. Interoperability core parameters
11. Core network core parameters12. Transmission core parameters
13. Equipment core parameters 14. License core parameters
15. Terminal compatibility core parameters 16. Other core parameters
D. Tool
Tool guide
Manual check method
E. Appendixes
Maturity of function commercialization
Summary of deliverables

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

Principle of Parameter Check
 Background:
Full parameter check is intended to draw
enough attention to parameters so that
incorrect parameter settings can be
discovered earlier and online problems
can be avoided.

 Plan:
Compare parameter settings (MML files)
of the live network with the baseline
scripts and check the reasonable
ranges, dependency, and consistency.
Analyze the parameters that are not in
the reasonable ranges or do not meet
the dependency or consistency
requirement and find out causes:
incorrect settings, improper rules, or
others. That is, explain why the
parameters fail parameter check and
modify improper configurations.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

Contents
A. Applicable Scenarios
B. Parameter Check Principle
C. Parameter Categories
01. Access core parameters 02. Call drop core parameters
03. PS data transmission core parameters 04. Voice quality core parameters
05. Network coverage core parameters 06. Paging core parameters
07. RF channel core parameters 08. Capacity core parameters
09. Peer vendor IUR parameters 10. Interoperability core parameters
11. Core network core parameters12. Transmission core parameters
13. Equipment core parameters 14. License core parameters
15. Terminal compatibility core parameters 16. Other core parameters
D. Tool
Tool guide
Manual check method
E. Appendixes
Maturity of function commercialization
Summary of deliverables

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 All Parameters Involved in UMTS Full Parameter Check
 At present, 698 parameters are collected and sorted out, which cover 16 categories. The parameters can be checked for
their reasonableness, dependency, and consistency. For details, see the UMTS Full Parameter Check Rule Table.
 385 RNC-level parameters, 286 cell-level parameters, 17 NodeB-level parameters, 9 parameters about RNC and
NodeB, and 1 parameter about CN of peer vendors
 332 MUST parameters (which must be modified when they are inconsistent with the baseline values) and 336
SHOULD parameters (which should be explained when they are inconsistent with the baseline values)
 640 parameters can be checked for their reasonableness by the tool and 58 need to be checked manually.
Parameters are checked for their dependency and consistency only in manual mode.
Peer
RNC and No. UMTS Parameter Category Total MUST SHOULD
No. UMTS Parameter Category Total RNC Cell NodeB Vendor
NodeB
CN 　 Total 698 332 366
　 Total 698 385 286 17 9 1
1 Access core parameters 115 33 82
1 Access core parameters 115 61 54 0 0 0
2 Call drop core parameters 241 131 108 1 0 1 2 Call drop core parameters 241 114 127
3 PS data transmission core parameters 69 45 16 8 0 0 3 PS data transmission core parameters 69 50 19
4 Voice quality core parameters 12 12 0 0 0 0 4 Voice quality core parameters 12 5 7
5 Network coverage core parameters 84 29 55 0 0 0 5 Network coverage core parameters 84 41 43
6 Paging core parameters 24 17 7 0 0 0 6 Paging core parameters 24 16 8
7 RF channel core parameters 5 0 0 5 0 0
7 RF channel core parameters 5 5 0
8 Capacity core parameters 52 39 11 2 0 0
8 Capacity core parameters 52 0 52
9 Peer vendor IUR core parameters 8 7 1 0 0 0
9 Peer vendor IUR core parameters 8 0　 8
10 Interoperability core parameters 43 21 22 0 0 0
10 Interoperability core parameters 43 42 1
11 Core network core parameters 3 2 1 0 0 0 11 Core network core parameters 3 3 0
12 Transmission core parameters 12 3 0 0 9 0 12 Transmission core parameters 12 11 1
13 Equipment core parameters 2 2 0 0 0 0 13 Equipment core parameters 2 1 1
14 Terminal compatibility core parameters 8 8 0 0 0 0 14 Terminal compatibility core parameters 8 8 0
15 License core parameters 5 5 0 0 0 0 15 License core parameters 5 0 5
16 Other core parameters 15 3 11 1 0 0 16 Other core parameters 15 3 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

01. Access Core Parameters
 Totally, there are 115 access core parameters. Based on the factors affecting basic performance, for
example, networking policy, initial resource consumption for access, process timer, feature, and
special terminal compatibility, the access core parameters are classified into 11 subcategories.
 61 RNC-level parameters, 54 cell-level parameters, and 0 NodeB-level parameter
 33 MUST parameters and 82 SHOULD parameters
 111 parameters can be checked for their reasonableness by the tool and 4 need to be checked manually.

Category RNC Cell

No. Subcategory of Access Total
Subtotal MUST SHOULD Subtotal MUST SHOULD
Parameters
　 Total 115 61 27 34 54 6 48
1 RLC layer parameters 2 2 2 0 0 0 0
2 Timer parameters 11 10 7 3 1 1 0
3 Coverage parameters 3 1 0 1 2 0 2
4 Power control parameters 8 0 0 0 8 0 8
5 Initial access rate parameters 22 22 10 12 0 0 0
6 Process optimization parameters 4 4 1 3 0 0 0
7 Feature parameters 2 2 2 0 0 0 0
8 Cell reselection parameters 8 0 0 0 8 1 7
Terminal compatibility optimization
9 1 1 1 0 0 0 0
parameters
10 Access control parameters 19 0 0 0 19 0 19
11 Networking policy parameters 35 19 4 15 16 4 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

Case 1: Disconnection Occurs Because the RB
Reassignment Timer Is Set to a Large Value

 Overview
The customer of O office in country A complains that iPad users are often offline and cannot use PS services.

 Problem analysis
Step 1: Determine the scope of access. The customer uses other terminals to perform a test. The problem also
exists. Analysis on the collected problems shows that the problems are not in a centralized area.
Step 2: Analyze the cause of access failure. No traffic statistics are provided for disconnection. Therefore,
analyze the core network tracing logs provided by the customer. After the core network sends an RAU Reject
message to the UE, the UE becomes offline.
Step 3: Check parameters. If parameters are not checked, it takes a long time to analyze the problem.
Step 4: Check equipment and transmission: N/A
Step 5: Check the version. No known problems cause disconnection.
Step 6: Check RF channels: N/A
It takes two days and lots of manpower to
Step 7: Check coverage: N/A analyze and locate the problem. If
Step 8: Analyze the long-term traffic trend: N/A parameters are checked first for their
reasonableness, the problem can be
Step 9: Analyze emergent factors: N/A solved in a minute.
Step 10: Analyze exceptions on the CN side: N/A

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

Case 1: Disconnection Occurs Because the RB
Reassignment Timer Is Set to a Large Value
Step 11 Analyze complaints and abnormal access.
1.Tracing and analysis on the user RNC side and core network side show that the core network sends an RAU Reject
message because the RNC does not respond to the context request message sent by the core network.
2.Tracing on the RNC side shows that the RNC does not respond to the context request message sent by the core
network in a long time during F2P RB reassignment.
3.Further analysis on configuration shows that the RB reassignment timer is set to 60s, which is greater than the
baseline value and regular setting (10s).
4.Root cause: In a poor coverage scenario, when the UE does not respond to an RB reassignment message, the RNC
waits 60s. In this case, the state machine of the RNC is unstable and does not process any received context request
message. As a result, timeout occurs on the core network side. In addition, the network side does not release the IU
interface connection in a long time. As a result, call drop occurs on the UE side and an access request is initiated on the
2G network, but the request is rejected by the core network.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

Case 1: Disconnection Occurs Because the RB
Reassignment Timer Is Set to a Large Value

Solution: Modify the duration of the RB reassignment timer to 10s.

After the duration of the RB reassignment timer is modified to 10s, signaling flow shows that
the RNC correctly processes the context request message sent by the core network 10s
after RB reassignment is performed. Feedback from the customer shows that the problem
disappears.
Conclusion: Parameter check must be performed unconditionally. The check on
access core parameters will find similar problems.
Parameter
Baseline Value Parameter Check
Parameter Reasonableness Handling
Type Subtype (Provided in Rule Impact
Name Check Suggestion
R13) (Reasonableness)
Requirement

1. If the
parameter is set
to a value greater
You are advised to than 15000, state
set the parameter to transition may
10000 in a poor result in long-term
RBRECFGRS Access core Timer
coverage scenario unstable state
PTMR parameter parameter
and retain the and the UE fails
baseline value in to transmit
other scenarios messages. As a
result,
disconnection
may occur.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

02. Call Drop Core Parameters
 Totally, there are 241 call drop core parameters, which cover 14 subcategories. Based on the property of parameters
affecting call drop, the parameters are first categorized and then subdivided based on parameter attributes.
 131 RNC-level parameters, 108 cell-level parameters, 1 NodeB-level parameter, and 1 peer vendor CN-level parameter
 114 MUST parameters and 127 SHOULD parameters
 232 parameters can be checked for their reasonableness by the tool and 9 need to be checked manually.

Category RNC Cell NodeB Peer Vendor CN

No. Total
Subcategory of Call Drop Parameters Subtotal MUST SHOULD Subtotal MUST SHOULD MUST SHOULD

　 Total 241 131 69 62 108 44 64 1 1

1 CN coordination parameter 1 0 0 0 0 0 0 0 1

2 IUR interconnection parameters 1 1 1 0 0 0 0 0 0

3 Timer parameters 22 22 20 2 0 0 0 0 0

4 Power control parameters 14 6 5 1 7 4 3 1 0

5 Activation time parameters 4 1 0 1 3 0 3 0 0

6 Link reestablishment parameters 9 9 0 9 0 0 0 0 0

7 Handover parameters 125 59 29 30 66 27 39 0 0

8 Algorithm parameters 15 12 5 7 3 2 1 0 0
Synchronization/loss of synchronization
9 5 2 1 1 3 3 0 0 0
parameters
10 Cell reselection parameters 24 0 0 0 24 8 16 0 0
Whether call drop is measured in abnormal
11 4 4 4 0 0 0 0 0 0
scenarios
12 User plane parameters 5 5 3 2 0 0 0 0 0

13 Terminal compatibility optimization parameters 1 1 1 0 0 0 0 0 0

14 Combined service call drop parameters 11 9 0 9 2 0 2 0 0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

Case 2: The Call Drop Rate Deteriorates Due to
Incorrect RNC Parameter Settings

 For operator A in country I, after RNCs are upgraded, KPIs including

RRC establishment success rate, CS/PS RAB establishment success
rate, and CS/PS call drop rate deteriorate.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

Case 2: The Call Drop Rate Deteriorates Due to
Incorrect RNC Parameter Settings
 Problem analysis
Step 1: Determine the scope of call drop. After RNCs are upgraded, the call drop rate of the entire network deteriorates, which is
unrelated to top cells.
Step 2: Determine the causes of call drop. The call drop rate deteriorates because RF call drops increase, including SRB reset, UL
loss of synchronization, and Uunoreply.
Steps 3, 4, 5…
The analysis on operation logs shows that at 15:25 March 11, 2011, DL inner loop power control was disabled. As a result, the DL NodeB no
longer performs inner loop power control and RF call drops increase.
242414,'admin','10.188.41.101',13615,'/*HWHandle=1686*/SET UCORRMALGOSWITCH:
DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-1&DRA_HSUPA_STATE_TRANS_SWITCH-1,
PcSwitch=PC_DL_INNER_LOOP_PC_ACTIVE_SWITCH-0, MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1,
PsSwitch=PS_BE_IU_QOS_NEG_SWITCH-1, CmcfSwitch=CMCF_DL_HLS_SWITCH-0&CMCF_UL_HLS_SWITCH-0,
ReservedU32Para0=0;','2011-03-11 15:25:05','2011-03-11 15:25:05',1,0,'Execution succeeded.','10.188.41.101---O&M System','','',2,0,1,0,''
If parameter check is performed first, the problem can be quickly found. Otherwise, it will take one person several days
to locate the problem.

Parameter
Baseline Value Parameter Check Reasonableness Handling
Device Parameter Name Type Subtype (Provided in Rule Impact
R13) (Reasonableness) Check Suggestion
Requirement

When the
parameter must
be set to ON,
DL_INNER_LO the inner loop
OP_PC_ACTIV Call drop core Power control This parameter downlink power
E_SWITCH parameter parameter must be set to ON. control state is
set to Active.
Otherwise, it is
set to Inactive.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

03. PS Data Transmission Core Parameters
 Totally, there are 69 PS data transmission core parameters, which cover 4
subcategories. The parameters are subdivided in terms of equipment, air interface,
channel, and capacity.
 45 RNC-level parameters, 16 cell-level parameters, and 8 NodeB-level parameters
 50 MUST parameters and 19 SHOULD parameters
 55 parameters can be checked for their reasonableness by the tool and 14 need to be
checked manually.
Category RNC Cell NodeB
No. Total
Subcategory of PS data
Subtotal MUST SHOULD Subtotal MUST SHOULD Subtotal MUST SHOULD
transmission parameters
　 Total 69 45 31 14 16 12 4 8 7 1

1 Equipment parameters 1 1 1 　 0 　 0 0　 0　 0　 　 0 0　

2 Radio bearer parameters 12 10 9 1 2 2 0　 　 0 　 0 0　

3 Channel parameters 36 32 21 11 3 1 2 1 1 0　
Resource control
4 20 2 0　 2 11 9 2 7 6 1
parameters

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

Case 3: The Throughput of M Office in a Drive Test Does
Not Meet Requirements
Problem description: After equipment of E/// is replaced in M office, the HSDPA drive test
results do not meet requirements.
Problem analysis:
Step 1: Confirm the problem and problem type.
Confirm that the throughput does not meet requirements and that field engineers perform a
drive test on more than 100 sites of one replaced RNC.
Step 2: Perform a check in the forward direction.
Required Action Check Result Executed Action
Action 1: Check for abnormal OK
operations.
Action 2: Check alarms. OK

2ms warnings are not Take preventive measures for

Action 3: Check warnings.
executed. warnings.

Not checked Not executed

Action 4: Check parameters.

Action 5: Check transmission OK

configuration specifications.

It takes a long time to analyze the problem because parameters are not checked.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

Case 3: The Throughput of M Office in a Drive Test Does Not Meet Requirements
(Continued)
Step 3: Perform a check in the reverse direction and take measures.
The results of resource analysis, traffic model analysis, and drive test data analysis in the reverse check
are as follows:
Required Action Check Result Executed Action
Uplink power congestion and downlink 1. Modify the uplink threshold of cells with
power congestion occur. high RTWP to 85%.
Action 6: Analyze
2. Change the maximum transmit power of
resources.
downlink congested cells to 40 W from 30
W.
Action 7: Analyze traffic The traffic volume is increased by 1.8 Optimize the HSUPA 2ms policy. Long-term
models. times compared with that before swap. policy: Expand dual carriers.
Action 8: Analyze coverage. OK
Action 9: Analyze L3. OK
SCCH scheduling is less likely 1. Enable the TPE function. 2. Enable
Action 10: Analyze L1.
performed, and the BLER is high. dynamic BLER CQI correction.
Action 11: Analyze L2. OK
Action 12: Analyze the Scheduling is less likely performed due Enable the TPE function.
application layer. to shortage of upper-layer data sources.

Action 6: Analyze resources.

The network assessment report of the OMStar shows that uplink and downlink power congestion is
severe.
ULPower DLPower CODE DLIUBBand ULIUBBand
ULCE Cong DLCE Cong
RNCID Cong Cong Cong Cong Cong
Times Times
Times Times Times Times Times
11 11810 1257 477 0 328 5 2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

Case 3: The Throughput of M Office in a Drive Test Does Not Meet Requirements (Continued)

Action 7: Analyze traffic models.

For network swap, data needs to be obtained from the operator before network swap and from OMStar traffic
measurement data after network swap.

Analyze distribution of online users through the OMStar network assessment function. The ratio of uplink 2ms users to
uplink 10ms users is about 7:3. Most terminals support the uplink 2ms services. In the live network configuration, the
HSUPA 2ms policy does not comply with the baseline configuration and needs to be optimized.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

Case 3: The Throughput of M Office in a Drive Test Does Not Meet Requirements (Continued)

Actions 10 and 12: Analyze L1 and application layer.

1. Scheduling probability: The scheduling probability of Huawei equipment is 40%, which is 15% lower
than that of Ericsson equipment. The scheduling probability is low because upper-layer data cannot be
sent. The TPE function helps improve the data transmission efficiency of the TCP layer and increase
scheduling probability of the physical layer.
2. BLER: The BLER of Huawei equipment is 40%, which is 27% higher than that of Ericsson equipment.
Huawei enables dynamic BLER CQI correction to reduce the BLER.

Scheduling probability before swap: 55% Scheduling probability after swap: 40%

BLER before swap: 13% BLER after swap: 40%

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

Case 3: The Throughput of M Office in a Drive Test Does Not Meet Requirements (Continued)

Step 4: Confirm that the problem is solved.

Perform reverse analysis and take check measures. After that, the gain obtained from the drive test is 10.
Action Throughput Throughput
Required Action Execution before the after the
Date Action Action
Action 1: Check for
abnormal operations.
Action 2: Check alarms.
Action 3: Check
warnings.
Action 4: Check 2012-5-21 689.1 kbps 707.4 kbps
parameters.
Action 5: Check
transmission
configuration
specifications.
Action 6: Analyze
resources.
Action 7: Analyze traffic
models.
Action 8: Analyze
coverage. 2012-5-22 707.4 kbps 776.5 kbps
Action 9: Analyze L3.
Action 10: Analyze L1.
Action 11: Analyze L2.
Action 12: Analyze the
Parameter application layer.
SET MACHSPARA (field configuration)
comparative Baseline
LOCELL=7328
analysis result RSCALLOCM=CODE_PRI POWERCODE_BAL
PWRMGN=20 PWRMGN=5
MXPWRPHUSR=70 MXPWRPHUSR=100
Recommendation in the drive test scenario:
CQIADJALGOFNONCON=NO_CQI_ADJ
CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER

Compare the gain with the baseline value and inform field engineers to change the parameter value to the
baseline value. The gain obtained through a drive test is 3% to 4%, which meets the requirement.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23
04. Voice Quality Core Parameters
 Totally, there are 12 voice quality core parameters, which cover one subcategory.
 12 RNC-level parameters, 0 cell-level parameter, and 0 NodeB-level parameter
 5 MUST parameters and 7 SHOULD parameters
 9 parameters can be checked for their reasonableness by the tool and 3 need to be
checked manually.

Category
RNC
No. Subcategory of voice quality Total
parameters Subtotal MUST SHOULD
　 Total 12 12 5 7

1 Voice quality parameters 12 12 5 7

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

Case 4: The 3G MOS Deteriorates by 0.2 Points after Office D in
Country G Is Swapped, Affecting FSA
Step 1: Check the test method. The test method meets the test specifications.
Step 2: Check the equipment version. The equipment version is normal.
Step 3: …After transmitted packets are checked, the root cause is not found in a long time. A complaint is filed
to the higher level, and a problem tackling appointment is prepared and is to be issued.

[INTERNAL]
Appointment of the Problem Tackling Team for Deterioration of 3G MOS after Swap in Office D of Country G
1. Background
Problem description:
The first FSA was completed at the end of July. After the equipment of MSN is swapped, the MOS drops by 0.2 points after the customer
performs a test by dialing a fixed-line number on a mobile phone using the Probe test tool in the quipment room. The test performed by
frontline engineers shows that the MOS also drops by 0.2 points after calls are made between mobile phones. This problem affects the
acceptance of the FSA.

Check packet loss during transmission. No exception is found.

Progess of the check on packet loss:
The CDT data check shows that a few packets are lost on the RNC side, whereas packet loss does not occur on the NodeB. Therefore, packet loss occurs during intermediate
transmission or at the bottom layer.
Time point of packet loss on the RNC

Liuming's analysis conclusion:

In the same time point:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

Case 4: The 3G MOS Deteriorates by 0.2 Points after Office
D in Country G Is Swapped, Affecting FSA
Check on equipment shows that equipment is normal.
During this period, NodeB sends packets normally.

After lots of time and manpower are used, the root cause is found in the end: The dynamic power control
function is disabled: SET UCORRMPARA: ReservedSwitch0=RESERVED_SWITCH_0_BIT24-0; The
baseline BLER is set to -20, which is equivalent to 1%. Because the dynamic power control function is
disabled (the uplink BLER value is not corrected), the MOS deteriorates. After the dynamic power control
function is enabled, the MOS meets the requirement.
It takes lots of time and manpower to locate this problem, and a complaint is even filed to the higher level. If
parameter check is performed, it takes only a few minutes to locate the problem.
Known Unknown Unknown Baseline Parameter Parameter Parameter Parameter
Device Constraint of Constraint of Constraint Parameter Type Subtype Value Check Rule Reasonable Check Rule Check Rule Handling Impact
the Basic the Basic of the Live Name (Provided (Reasonable ness Check (Dependency) (Consistency) Suggestion
Network Network Network in R13) ness) Requirement

Voice You are The baseline

quality Voice advised to BLER is set to
a core quality use the –20, which is
parameter parameter baseline equivalent to
value. 1%.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

 05. Network Coverage Core Parameters
 Totally, there are 84 network coverage parameters, which cover five subcategories, including switch,
power control, access, handover, and cell reselection. Switch parameters involve algorithm switches
and have great impacts. Therefore, they are listed separately. The procedure parameters associated
with other parameters basically cover procedures involved in networking.
 29 RNC-level parameters, 55 cell-level parameters, and 0 NodeB-level parameter
 41 MUST parameter and 43 SHOULD parameters
 84 parameters can be checked for their reasonableness by the tool and no parameters need to be
checked manually.
Category RNC Cell
No. Subcategory of network Total
Subtotal MUST SHOULD Subtotal MUST SHOULD
coverage parameters

　 Total 84 29 17 12 55 24 31

1 Power control 5 0 0 0 5 1 4

2 Access 11 5 0 5 6 0 6

3 Switch 2 1 1 0 1 0 1

4 Handover 47 23 16 7 24 16 8

5 Cell reselection 19 0 0 0 19 7 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

Case 5: After Swap of an Office in a Country, the Number of Inter-RAT CS
Handovers Increases
 Step1 Confirm coverage problems.
 After the swap, the number of inter-RAT CS handovers increases.
 After the interoperability problem is handled, confirm that coverage problems result in increase
of handovers.
 Analyze the drive test data before and after swap.
 Step2 Execute required actions.
Required Data Analysis and Symptom Conclusion Handling Result
Action Analysis
Modify the power The downlink coverage
1. The mapping of swap parameters is
Power parameters parameter settings changes because the
normal.
Parameter do not match those so that they match power does not match.
2. Parameter check shows that handover
check of the original the parameters of After the power
parameters are normal. Power parameters
network. the original matches, KPIs become
do not match those of the original network.
network. normal.
Coverage This item is used to provide information
Normal None N/A
information about a swapped office.
Traffic This item is used to provide information
Normal None N/A
information about a swapped office.
Problems such as missed neighboring cell
PCHR analysis configuration and pilot pollution are not Normal None N/A
found.
Check whether
Compare the RSCP/ECIO values obtained
Drive test The DELTA-RSCP power matches by The downlink coverage
through a drive test before and after the
analysis becomes poor. combining changes.
swap.
parameter check.

Note: In this case, drive test analysis rather than parameter check is performed first, which delays problem locating.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28

 Case 5: After Swap of an Office in a Country, the Number
of Inter-RAT CS Handovers Increases
 Specific analysis 1 – drive test analysis
 Drive test analysis rather than parameter check is performed first.
 Drive test analysis shows that after swap EcNo becomes poorer than that of the original network but RSCP becomes better.

RSCP HW ER
EcNo  Huawei Ericsson EcNo
(-65 to -30) 4530 (48%) 4529 (46%)
EcNo
EcNo>-10 62.61% 73.47% (-75 to -65) 2698 (29%) 2798 (28%)
-14<EcNo<-10 33.87% 25.13% (-85 to -75) 1721 (18%) 2000 (20%)
-16<EcNo<-14 2.58% 1.17% (-95 to -85) 366 (4%) 476 (5%)
EcNo<-16 0.94% 2.23% (-105 to -95) 26 (0%) 31 (0%)
(-115 to -105) 3 (0%) 2 (0%)
 Note: This is partly because of mapping of CS service inter-system 2D/2F threshold.

 Perform Delta pilot (the RSCP after swap minus the

RSCP before swap). Analysis shows that RSCP
distribution is improved but Delta RSCP becomes poor.
In the figure on the right, the parts in blue indicate
RSCP in the parts is lower than that of the original
network. Obviously most parts are in blue.

 It can be seen, although the coverage in some areas becomes good (new sites are added
after swap), that the overall coverage is becomes poor.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 29

Case 5: After Swap of an Office in a Country, the
Number of Inter-RAT CS Handovers Increases
 Specific analysis 2 – parameter check
 The problem is found through drive test analysis and the root cause is found out through
parameter check.
 As mentioned in the swap SOP, the power mapping principle of Huawei is as follows:
PCPICHPower[HUAWEI]=primaryCpichPower+dlAttenuation(AntFeederCable)[E///].
 After the swap, some sites of Huawei are distributed sites and some are macro NodeBs. If
NodeBs after swap are distributed NodeBs, the power mapping has little impact; if the
NodeBs after swap are macro NodeBs, power mapping has a great impact.
 The dlattenuation of most cells in the original network is 1 to 2.5 dB. The pilot suffers a
loss of 1 to 2.5 dB, resulting in poor coverage. The sites with this problems account for
about 62%.
 Step 3 Solve the problem and output a summary report.
 After the power parameters match those of the original network, the number of CS inter-
RAT handovers is almost the same as that of the original network.

Root cause: Parameters are set incorrectly (the power does not match).
Locating method: Check parameters and analyze drive test data.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

06. Paging Core Parameters
 Totally, there are 24 paging core parameters, which cover 1 subcategory.
 17 RNC-level parameters, 7 cell-level parameters, and 0 NodeB-level parameter
 16 MUST parameters and 8 SHOULD parameters
 24 parameters can be checked for their reasonableness by the tool and no parameters need to be
checked manually.

Category RNC Cell

No. Subcategory of paging Total
Subtotal MUST SHOULD Subtotal MUST SHOULD
core parameters
Total 24 17 11 6 7 5 2

1 Timer parameters 1 1 0 1 0 0 0

2 Power control parameters 2 0 0 0 2 0 2

3 Access parameters 1 1 0 1 0 0 0

4 Switch parameters 3 3 2 1 0 0 0

5 Threshold parameters 6 6 6 0 0 0 0

6 Cell reselection parameters 5 0 0 0 5 5 0

7 Channel parameters 1 1 0 1 0 0 0

8 Paging parameters 5 5 3 2 0 0 0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

 Case 6: The Paging Success Rate Drops After Dual
Carriers of Office U in Country Z Are Expanded
 After the dual carriers of office U in country Z are expanded, the paging success rate on the CN side and the
UTRAN side drops.
Problem description: After dual carriers were deployed for RNC01/02/09 on April 9 in office U of country Z, the PS
RAB establishment success rate drops and the paging success rate on the CN side and the UTRAN side drops
obviously.

Paging problem locating process:

1. The air interface quality of new carriers may be poor. Guide field engineers to check
and optimize the air interface environment.
2. Field user tracing shows that the PS RAB success rate is low because of RB setup
failure.
3. Check on the configuration after user tracing shows that the PS RAB success rate
and the paging success rate drop because DRD rollback is not enabled in the case of
RB setup failure.

Solution: Enable DRD rollback in the case of RB setup or reconfiguration failure.

SET URRCTRLSWITCH:
PROCESSSWITCH2=RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH-
1&RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH-1;
Note: In this case, drive test analysis rather than parameter check is performed first, which
delays problem locating.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 32

07. RF Channel Core Parameters
 Totally, there are 5 RF channel core parameters, which cover 1 subcategory. The
configuration parameters that are directly related to RTWP are provided. These
parameters directly affect the RTWP value. The specific parameter settings depend
on actual conditions. For other information, see the RF channel topics: 1. RF
channel parameter check script; 2. RTWP analysis tool
 0 RNC-level parameter, 0 cell-level parameter, and 5 NodeB-level parameters
 5 MUST parameters and 0 SHOULD parameter
 No parameters can be checked for their reasonableness by the tool and 5
parameters need to be checked manually.

Category NodeB
No. Total
RF channel core parameters Subtotal MUST
　 Total 5 5 5
1 RF channel parameters 5 5 5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 33

Case 7: Multiple Sites Report that RTWP Is Too Low
 Overview
An office complains that multiple sites report that the alarm indicating RTWP is too low is generated after site deployment.
Analysis process (analysis on lots of data shows that no fault occurs and parameter check shows that parameter settings
are incorrect):
Action 1: Determine symptoms of the RTWP problem. Analyze multiple sites where the problem occurs during site deployment.
The problem lies in multiple carriers. The sites where this problem occurs are macro NodeBs that are irregularly distributed and are
unrelated to busy or idle hours.
Action 2: Analyze operation logs of the RNC/NodeB. This scenario is not involved.
Action 3: Check emergent factors. This scenario is not involved.
Action 4: Check equipment faults and alarms. The alarm indicating that RTWP is too low is generated.
Action 5: Analyze traffic statistics of the RTWP problem. The analysis on traffic statistics data of RTWP shows that MinRTWP is –
121.1 dBm, which indicates that the RTWP is actually low.

Action 6: Analyze main and diversity RTWP. The traced values show that the
main RTWP values of the cells are around –106 dBm, which is in the normal
range, and the diversity RTWP values are below –114 dBm and does not
fluctuate, which indicates that the alarm is not a false alarm. Incorrect
configuration (cross-connect mode) or RF module failure may cause this
problem.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 34

 Case 7: Multiple Sites Report that RTWP Is Too Low
Action 7 ： Check parameter settings: Check parameter settings by combining networking scenarios.
Required Action Analysis Data Analysis and Symptom Conclusion Handling Result
Confirmation on site shows that the
Modify the sector configuration
Action 7: Check parameter common networking mode is used, but An incorrect networking
and confirm that the correct
settings. the networking mode is set to cross- mode is set.
networking mode is set.
connect mode.

Field problem solving result: Field engineers determine that the problem is caused by the CME
template and do not execute subsequent actions.

Parameter Query Analysis Conclusion

Result
Sector configuration (detailed information) 射频通道衰减 0 No tower-mounted amplifiers are
值 provided and the configuration is
correct.
Site No.=1
Sector No.=0
Sector type=local sector
Transmit diversity mode=common
RTWP 初始校 0 The parameter is generally set to 0.
Number of available RRUs/RFUs=1
RRU1 cabinet No.=0 准值
RRU1 subrack No.=4
RRU1 slot No.=0
RRU2 cabinet No.=0
RRU2 subrack No.=0 射频去敏值 0 The parameter is generally set to 0.
RRU2 slot No.=0
Number of receive antennas=0
Amplifier

小区去敏值 0 The parameter is generally set to 0.

RF interconnect mode=TRUE
Antenna connector 1 cabinet No.=0

This configuration Antenna connector 1 subrack No.=4

makes the diversity

Antenna connector 1=ROA
互联模式 TRUE The networking mode is not the cross-
channel an Uplink delay 1 (ns)=100
Downlink delay 1 (ns)=100
connect mode but is set to the cross-
interrupted path. Antenna connector 2 cabinet No.=0
connect mode.
Antenna connector 2 subrack No.=4
Antenna connector No.2=ROA

Uplink delay 2 (ns)=100

Downlink delay 2 (ns)=100

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 35

08. Capacity Core Parameters
 Totally, there are 52 capacity core parameters, which cover 3 subcategories. The
parameters are subdivided based on parameter features and usage description.
 39 RNC-level parameters, 11 cell-level parameters, and 2 NodeB-level parameters
 0 MUST parameter and 52 SHOULD parameters
 50 parameters can be checked for their reasonableness and 2 need to be checked
manually.

Category RNC Cell NodeB

No. Subcategory of capacity Total
Subtotal SHOULD Subtotal SHOULD Subtotal SHOULD
core parameters
　 Total 52 39 40 11 10 2 2

1 Timer parameters 4 4 4 　 0 0　 0 0

2 Function parameters 27 21 21 4 4 2 2

3 Threshold parameters 21 14 14 7 7 0 0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 36

Case 8: The RTWP Is High Because Power Control
Parameters Are Set Incorrectly
Network KPIs are poor; the network RTWP is high in some idle hours or busy hours; after the main antenna is
disconnected, the diversity RTWP fluctuates abnormally. Tracing on the RTWP of three sectors of a site shows that the
fluctuation trend is the same: the RTWP often becomes abnormal for about 30s.

Problem analysis:
1.After channels are checked, the RTWP is still abnormal. Field engineers perform many interference tests and still cannot
find the root cause several days later.
2.During the check on power control parameters, comparison of different network logs shows that power control
BETAC/BETAD is set to an incorrect value. If parameter check is performed in advance, the problem can be located within
several minutes.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 37

09. Peer Vendor IUR Core Parameters
 Totally, there are 8 peer vendor IUR core parameters, which cover 1 subcategory.
 7 RNC-level parameters, 1 cell-level parameter, and 0 NodeB-level parameter
 0 MUST parameter and 8 SHOULD parameters
 7 parameters can be checked for their reasonableness by the tool and 1 needs to
be checked manually.

Category RNC Cell

No. Total
Subcategory of peer
Subtotal SHOULD Subtotal SHOULD
vendor IUR parameters

　 Total 8 7 7 1 1

1 Process parameters 8 7 7 1 1

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 38

Case 9: CS Call Drop Occurs Because Compatibility
Parameters of a Peer Vendor Are Set Incorrectly
 Overview
The live network of operator B in country J includes E// CN, HW SRNC, and HW DRNC. When E// CN, HW SRNC, and HW
DRNC are migrated in static mode, CS call drop occurs.
 It takes about nearly two weeks to analyze the problem.
 After field engineers provide data the first time, the problem cannot be located because tracing in debug mode is not
available. Field engineers are required to perform a drive test again and trace data in debug mode, which takes about
more than one week.
 More than one week later, field engineers provide data as required. R&D engineers analyze output information obtained
in tracing and code and find that E// CN, HW SRND, and HW DRNC support the IUUP2 scenario. E// assignment
messages carry four rates (rate 0 is not available). When HW SRNC processes the messages, rate 0 is added. Five
rates are provided when DRLs are created. After the devices are migrated, the CN assigns four rates. When the DRNC
determines that the TFS used currently differs from that assigned (five rates are available but four rates are assigned
after migration), the system rolls back to IUUP1 establishment. Because E// CN does not support IUUP1, the ISSUP
fails to be established. As a result, call drop occurs. The check on scripts shows that rollback is not enabled.
SET URRMCDLCFG:INNERSWITCH1=FRC_RELOCIN_IUUP2_NOT_CHANGED_SWITCH_14-0; Parameter check requires
that the item must be checked.
Baseline Parameter Parameter Parameter Parameter
Device Parameter Type Subtype Value Check Rule Reasonablene Check Rule Check Rule Handling Impact
Name (Provided in (Reasonablen ss Check (Dependency) (Consistency) Suggestion
R13) ess) Requirement

Process
parameter

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 39

10. Interoperability Core Parameters
 Totally, there are 43 interoperability core parameters, which cover 4
subcategories. The parameters are subdivided based on parameter property, for
example, switch parameters, threshold parameters, and timer parameters.
 21 RNC-level parameters, 22 cell-level parameters, 0 NodeB-level parameter
 42 MUST parameters and 1 SHOULD parameter
 42 parameters can be checked for their reasonableness by the tool and 1 needs to
be checked manually.

Category 　 Total RNC Cell

No. Subcategory of
　 Subtotal MUST Subtotal MUST SHOULD
interoperability parameters
　 Total 43 21 21 22 21 1

1 Delay parameters 5 2 2 3 2 1

2 Switch parameters 4 4 4 0　 0　 0　

3 Threshold parameters 30 15 15 15 15 0　
Network planning
4 4 　0 　0 4 4 0　
parameters

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 40

Case 10: The Handover Success Rate of the Original Network Does Not
Meet the Requirement Because Version Parameters Do Not Match
 Overview:
After the 3G network of operator M in country S is swapped, the number of inter-RAT PS handovers increases sharply and
the inter-RAT PS handover success rate does not meet the requirement.

 Problem analysis
Step 1: Confirm the scope and causes. After the 3G network is swapped, the number of handovers on the entire network
increases sharply, which is unrelated to top cells. Handover failures are caused by other reasons, which account for more
than 55%.
Step 2: Check parameters. (Parameters are not checked.)
Step 3…
Required Action Data Analysis and Conclusion Handling Result
Analysis Symptom
Parameter check The inter-RAT The setting of the inter-RAT handover Enable the The number of inter-
handover attribute attribute parameter does not match that of handover RAT handovers
parameter is set tothe original network. More than 384,000 attribute. restores to the number
off. users are allowed to hand over to the 2G before the swap.
network.
Caution: After the 3G network is swapped, field engineers do not perform parameter mapping or check
parameters. The field engineers responsible for locating this problem do not check parameters in time, which
extend the problem locating duration.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 41

11. Core Network Core Parameters
 Totally, there are 3 core network core parameters, which cover 1
subcategory.
 2 RNC-level parameters, 1 cell-level parameter, and 0 NodeB-level parameter
 3 MUST parameters and 0 SHOULD parameter
 3 parameters can be checked for their reasonableness and no parameters
need to be checked manually.

Category RNC Cell

No. Subcategory of core Total Subtota
MUST Subtotal MUST
network parameters l
　 Total 3 2 2 1 1

1 Core network parameters 3 2 2 1 1

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 42

Case 11: Calls Are Released Immediately After Being Connected
When RTCP Is Disabled
 Overview
Operator B in country F complains that, after calls from 3G users are connected, the calls are
released quickly (it seems that call drop occurs).

 Problem analysis
Step 1: Determine the scope of call drop. The analysis on traffic measurement data shows
that the call drop rate is normal.
Step 2: Determine the specific causes of call drop. Because this problem always occurs in
3G calls, field engineers directly trace VIP signaling. The tracing results show the following law:
The interval from call setup to call release initiated by the core network ranges from 5s to 10s;
the RB/RAB is established successfully on the RNC side; the UE interworks with the core
network at the NAS layer through direct messages normally; after calls are connected
successfully, the core network sends a disconnect message (an NAS layer message
transparently transmitted by the RNC) within 5s to 10s to release the calls.

Steps 1 and 2 are associated with Action 1.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 43

 Case 11: Calls Are Released Immediately After Being Connected
When RTCP Is Disabled

Step 3: Analyze required actions.

Category Data Analysis and Symptom Conclusion

Action 1: Determine the causes of Analyze this problem by using CHR

The traffic measurement data is normal
call drop based on traffic tracing because this problem always
because the core network releases calls.
measurement and CHR analysis. exists.

Action 2: Check all parameters. Parameter check is not performed.

Actions 3 to 15: See previous

These actions do not need to be taken. These actions do not need to be taken.
descriptions.
Analyze complaints and abnormal The core network sends a disconnect The core network is abnormal. Ask the
call drops by using the CHR. message. peer vendor to check the core network.

This problem is actually caused by incorrect parameter settings and incompatibility with the core
network of a peer vendor and can be located through parameter check. In problem locating, however,
parameters are not checked. Instead, signaling is analyzed to locate the problem. Because the core
network sends a disconnect message, the problem lies in the core network. Then ask the peer vendor
to check the core network. Pushed by field engineers, NSN explains why calls are released. Later, after
NSN disables strict check on RTCP packets, the problem is solved.
Clarification
for RTCP Issue

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 44

Case 11: Calls Are Released Immediately After Being Connected
When RTCP Is Disabled
Root cause: NSS CS core network has the following configuration for RTCP: When NSN CS
core network uses mode “3” in the following figure, if RTCP packets are not received, the core
network considers errors exist in RTCP packets and directly releases calls.
Real time transport protocol (RTP) is used to transmit
information about real-time features. Real-time transport
control protocol (RTCP) is used to monitor service quality
and information about members in transport sessions. RTP
is a transport layer protocol, over which service data is
transmitted. RTCP monitors transmission quality. If the
RTCP flag bit is set to off, RTCP detection is disabled but
RTP transmission is normal. The purpose of RTCP is to
monitor transmission and receiving of RTP packets on the
transmitting side and receiving side and periodically
exchange RTP packet transmission and receiving
information between the sender and the receiver. RTCP is
responsible for sending and receiving the reports about RTP
packet sending and receiving, and the application layer
processes the reports.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 45

12. Transmission Core Parameters
 Totally, there are 12 transmission core parameters, which cover 1 subcategory.
 3 RNC-level parameters and 9 RNC-level and NodeB-level parameters
 11 MUST parameters and 1 SHOULD parameter
 No parameters can be checked for their reasonableness by the tool and 12
parameters need to be checked manually.

Category RNC RNC and NodeB

No. Transmission core Total
Subtotal MUST SHOULD Subtotal MUST
parameters
　 Total 12 3 2 1 9 9
Transmission
1 12 3 2 1 9 9
parameters

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 46

Case 12: KPIs Become Abnormal Because a Transmission
Parameter Is Set Improperly
 For operator D in country L, the SCTP retransmission rate is high.
 Problem description: Operator D in country L complains that SCTP retransmission
rate is high in all results of RAC RNC(RNC131), including IuCS, IuPS, and IUR.

After the problem occurs, parameter check is not performed. Instead, lots of alarms, traffic
measurement data, and tracing data are analyzed. It takes field engineers one week to locate the
problem: a parameter is not set to the recommended value.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 47

Case 12: KPIs Become Abnormal Because a Transmission
Parameter Is Set Improperly
The analysis on traffic measurement data shows that lots of retransmissions occur.

The analysis on SCTP tracing data captured by field engineers shows that (assume the packet length is
52): The RNC sends a piece of data with TSN 74370857 at 13:25:24(38) and another piece of data with
TSN 74370858 140 ms ((52 – 38) x 10) later. Because no SACK message is received, the RNC
retransmits the two pieces of data 160 ms later.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 48

Case 12: KPIs Become Abnormal Because a
Transmission Parameter Is Set Improperly
Because no SACK message is received from the peer end before the local retransmission timer expires, the
RNC retransmits the two pieces of data after the timer expires. Then a SACK message is received.
Therefore, a SACK message is not sent to the RNC in time possibly because of transmission delay. The
check on whether the SACK messages whose lengths are 56, 60, and 68 are received using the same
method shows that the SACK message is still being transmitted when the local end retransmits the data.

The RNC receives the data 2831696010 at 16:54:16(30) and 16:54:16(46). The interval is 160 ms.
The duration of the peer retransmission timer is 150 ms. Therefore, the MGW retransmits the data
after the retransmission timer expires.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 49

Case 12: KPIs Become Abnormal Because a
Transmission Parameter Is Set Improperly
 Tracing data shows that the interval between sending of the SACK message and
receiving of the first data is about 160 ms. Site configuration shows that RTOMIN is set
to 150 ms, whereas the recommended value of this parameter is 1000 ms.
 After RTOMIN is set to 1000 ms at both ends, the problem disappears.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 50

13. Equipment Core Parameters
 Totally, there are 2 equipment core parameters, which cover 1 subcategory.
 2 RNC-level parameters, 0 cell-level parameter, and 0 NodeB-level parameter
 1 MUST parameter and 1 SHOULD parameter
 No parameters can be checked for their reasonableness by the tool and 2
parameters need to be checked manually.

Category RNC
No. Equipment core Total
Subtotal MUST SHOULD
parameters
　 Total 2 2 1 1
1 Equipment parameters 2 2 1 1

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 51

Case 13: The Service Fails to Be Established Because
an Equipment Parameter Is Set Improperly

 Problem overview
An emergent problem occurs in an office in country S. The service cannot be established when a
subrack is added.
Problem analysis
An emergency plan is available for this type of problem. First check related configurations. The
check on configuration scripts shows that the SCU port between the new subrack and subrack 0
is not enabled. As a result, the new subrack is disconnected from subrack 0. Heartbeat messages
cannot be received from the SCU port, the new subrack resets repeatedly, and the service cannot
be established. After the SCU port is enabled, the service recovers.

Because parameter check is performed first, the problem is solved within 5 minutes with R&D
engineer support by telephone.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 52

14. Terminal Compatibility Core Parameters
 Totally, there are 8 terminal compatibility core parameters, which cover 1
subcategory. These parameters are subdivided based on parameter property, for
example, switch parameters, threshold parameters, and timer parameters.
 8 RNC-level parameters, 0 cell-level parameter, and 0 NodeB-level parameter
 8 MUST should parameters and 0 SHOULD parameter
 8 parameters can be checked for their reasonableness by the tool and no
parameters need to be checked manually.

Category RNC
No. Total
Subcategory of terminal
Subtotal MUST
compatibility parameters

　 Total 8 8 8

1 Switch parameters 8 8 8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 53

Case 14: Sony W995 Mobile Phones Cannot Use 3G PS
Services in Office E in a Country
 Problem description: Field engineers complain that Sony W995 mobile phones cannot use 3G
PS services of the operator but can use 3G CS services and 2G services (on the PS side, 3G and
2G use the same SGSN and GGSN). After the SIM card is inserted on mobile phones of other
brands, 3G PS services of the operator can be used normally. If SIM cards of other operators are
inserted on Sony W995 test mobile phone, 3G PS services can be used normally.
 Problem Analysis (It takes nearly one month to analyze the problem.)
2012-5-7
Current progress: The analysis on traced signaling provided by field engineers shows that the control
plane is normal. It is initially determined that errors occur on the user plane, which causes
network access failure. The RNC CDT (with L2 tracing), NodeB CDT, and MML configuration
scripts must be obtained to perform further analysis. At present, field engineers are informed to
reoccur the problem and capture related information.
Next-step plan: Wait for data from field engineers.
Expected completion date: May 9, 2012
Current difficulty: An RNC LMT is needed for tracing so that data of the live network can be obtained
for analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 54

Case 14: Sony W995 Mobile Phones Cannot Use
3G PS Services in Office E in a Country
 2012-5-14
 Current progress: The DNS response code stream received by the RNC from the SGSN/GGSN is
normal, but an error occurs during transmission of the DNS response code stream from the RNC
to the UE. As a result, the UE cannot initiate a Get Http request. On the RNC side, both
usUlSufiListNum and the number of uplink/downlink retransmission times are 0, which cannot
prove that error codes exist on the RNC side or UE side. The RNC adds a frame header for direct
messages and does not perform other operations. Analysis needs to be performed on the NodeB
side to determine whether any problem exists. In addition, field engineers mention the problem of
another Sony mobile phone on the ETL network, which is caused by incorrect QoS parameter
settings, was handled one month ago.
 Next-step plan: Learn the details of the problem about Sony mobile phone reported by field
engineers and analyze whether code streams are correctly transmitted from the NodeB to the UE.
 Expected completion date: 2012-5-15

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 55

Case 14: Sony W995 Mobile Phones Cannot
Use 3G PS Services in Office E in a Country
 2012-5-16
 Current progress: The analysis on code streams shows that an error occurs in the DNS response
message when the RNC sends a message to the UE. As a result, the UE cannot correctly resolve the
DNS response message, and the network access process is terminated. The DNS response message is
a user plane message. The RNC and NodeB process all user plane messages in the same way (user
plane messages are also processed in the same way on other devices): the RNC and NodeB
transparently transmit user plane messages and do not process data. On May 15, field engineers
reported that Sony W995 could access the network of another operator under the Huawei RNC of the
same version.
 Next-step plan: Wait until field engineers provide the tracing messages and latest data configuration of
the Huawei RNC in another operator, where Sony W995 can access the network.
 Expected completion date: 2012-5-17
 Current difficulty: None
 2012-6-4
 Current progress: Field engineers reported that this problem does not exist on ZTE network. Field
engineers have not captured network access data of ZTE RNC. Core network engineers confirm that the
signaling on the core network side is normal. This problem does not reoccur in the lab at present.
 Next-step plan: Urge field engineers to provide the network access data of ZTE RNC and ask the
problem tackling team to discuss about the problem.
 Expected completion date: 2012-6-5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 56

Case 14: Sony W995 Mobile Phones Cannot Use 3G PS Services
in Office E in a Country
 2012-6-7
 Current progress: The problem is located and needs to be verified after field engineers modify parameter
settings online. Comparative test and data analysis show that the RB_Setup messages are different in two
RNCs:
Abnormal RB_setup message Normal RB setup message

Set up the test environment. After MacD PDU size is set to 1296, the problem reoccurs. After field
engineers modify MacD PDU size to 656, the problem is solved. If parameter check is performed
first, the problem can be solved within several minutes.
Parameter Parameter Check Parameter Check
Device Known Constraint of Unknown Constraint Parameter Name Type Subtype Baseline Value Parameter Check Rule Reasonableness Rule Rule Handling Impact
the Basic Network of the Basic Network (Provided in R13) (Reasonableness) Check (Dependency) (Consistency) Suggestion
Requirement

If the parameter
is set to a large
HS-DSCH value, the
MAC-D PDU size You are advised performance of
PS data to use the weak coverage
1 transmission Channel baseline value. areas is affected
core parameter parameter and terminals
may be
incompatible.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 57

15. License Core Parameters
 Totally, there are 5 license core parameters, which cover 1
subcategory.
 5 RNC-level parameters, 0 cell-level parameter, and 0 NodeB-level parameter
 0 MUST parameter and 5 should parameter
 No parameters can be checked for their reasonableness by the tool and 5 such
parameters need to be checked manually.

Category RNC
No. Subcategory of license Total
Subtotal SHOULD
parameters
　 Total 5 5 5

1 License parameter 5 5 5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 58

Case 15: PS Services Cannot Be Established Because the
License Is Not Activated during IP Transmission on the RNC
 In office V of country S, PS services cannot be established because the license is not activated during IP
transmission on the RNC.
 Problem description:
 During commissioning of the RNC in an auto show in country S, UEs can attach to the PS domain but the PS RAB
assignment procedure fails because transmission on the Iu interface fails. The check on site shows that the IUPS IP path
configured on the RNC can be pinged and no alarm is generated on the RNC.
 Problem analysis: Analysis on tracing data shows that, after the CN sends a RANAP_RAB_ASSIGNMENT_REQ
message, the RNC quickly returns a RANAP_RAB_ASSIGNMENT_RSP message, indicating that PS RAB fails to be
established because transmission on the Iu interface fails.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 59

Case 15: PS Services Cannot Be Established Because the License Is
Not Activated during IP Transmission on the RNC

 Query the configuration scripts of RNC. The RNC IUPS interface is configured with two IP paths, the
IP path ping function is enabled, and alarms about IP path are not reported on the RNC side, which
indicates that the IP paths are normal. In addition, field engineers ping the IP path and find the peer
address of the IP path can be pinged.

 Analyze the peer IP address carried in the RANAP_RAB_ASSIGMENT_REQ message sent by the CN
to the RNC and convert the IP address into a decimal IP address. The decimal IP address is
consistent with the peer IP address 172.15.3.3, which indicates that the peer IP address is sent
normally.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 60

 Case 15: PS Services Cannot Be Established Because the License Is
Not Activated during IP Transmission on the RNC
 Further analyze the signaling procedure and the PS RAB establishment process. Resources fail to be transmitted on the IUPS
interface, with the cause value al-l3-TRM-IP-LICENSE-DISABLE. Ask field engineers to query the license and confirm that the license
status is OFF. Therefore, the PS services fail to be established because the license used for transmission over IP is not activated.

It takes a long time to locate the problem. Later, R&D engineers check tracing logs and, based
on codes, find that the license is not activated. Then field engineers confirm that the PS services
fail to be established because the IP license is not activated on the Iu interface.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 61

16. Other Core Parameters
 Totally, there are 15 other core parameters, which cover 2 subcategories.
 3 RNC-level parameters, 11 cell-level parameters, and 1 NodeB-level parameter
 3 MUST parameters and 12 SHOULD parameters
 15 such parameters can be checked for their reasonableness by the tool and no parameters
need to be checked manually.

　 RNC Cell NodeB

No. Total SHOUL
Row label Subtotal Subtotal MUST SHOULD Subtotal MUST
D
　 Total 15 3 3 11 2 9 1 1
Timer
1 2 2 2 0　 0　 0　 0　 0　
parameters
Power
2 control 13 1 1 11 2 9 1 1
parameters

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 62

 Case 16: A Public Transmission Channel Fails to Be Established
Because the Pilot and Cell Transmit Power Are Set Improperly

 Problem overview: An alarm indicating that a public transmission channel fails to be established on the NodeB. Trace messages on
the Iub interface. The NBAP_COMM_TRANSP_CH_SETUP_FAIL message is found, with the cause value power-level-not-
supported(2).

 Problem analysis: The cause value power-level-not-supported occurs because the remaining
power is not enough to establish a transmission channel. The power of channels is based on the
power offset of pilots. Therefore, when the pilot configuration is similar to the power configuration of
logical cells, the remaining power is not enough to establish a transmission channel.
 After confirming the problem by tracing data, the analysis personnel first query the pilot configuration
and the power configuration of logical cells. The difference between the two is smaller than 53
(0.1dbm). After the difference between the two is increased, the problem is solved.

After the problem occurs, first check parameters, which helps quickly solve the problem.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 63

Contents
A. Applicable Scenarios
B. Parameter Check Principle
C. Parameter Categories
01. Access core parameters 02. Call drop core parameters
03. PS data transmission core parameters 04. Voice quality core parameters
05. Network coverage core parameters 06. Paging core parameters
07. RF channel core parameters 08. Capacity core parameters
09. Peer vendor IUR parameters 10. Interoperability core parameters
11. Core network core parameters 12. Transmission core parameters
13. Equipment core parameters 14. License core parameters
15. Terminal compatibility core parameters 16. Other core parameters

D. Tool
Tool guide
Manual check method

E. Appendixes
Maturity of function commercialization
Summary of deliverables

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

How to Obtain the FMA Tool
 http://hi3ms.huawei.com/hi/group/4173/files.html?cid=24731

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 65

How to Install the FMA Tool
 Step 1: Read the FMA Tool Guide.CHM to learn subsequent two
steps, which are described in this document in detail.
 Step 2: Click FMA.exe.
 Step 3: Apply for a license. For details, see Chapter 4 “License
Description” in the FMA Tool Guide.CHM.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 66

Tool Guide
 See the UMTS Full Parameter Check Tool Guide.docx.

UMTSÈ«²ÎÊý¼ì²é
¹¤¾ß²Ù×÷Ö¸µ¼.docx

 Input: script on the live network

 Output: .csv file

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 67

 Manual Check Method (1)
 Input: columns A to R in UMTS Full Parameter Check Rule Table
 Output: columns S to AD in UMTS Full Parameter Check Rule Table
 Three basic steps
 Step 1: Use column C “Parameter ID” as the main key to search in live network scripts.
If a unique value can be found, fill the value in column Y Live Network Configuration. If
you cannot determine the unique value, go to step 2.

 Step 2: In the result obtained in step 1, search in the live network scripts based on
column B MML Command. If a unique value can be found, fill the value in column Y
Live Network Configuration. If you cannot determine the unique value, go to step 3.

 Step 3: In the result obtained in step 2, search in live network scripts based on column
D Known Constraint of Basic Network and fill the searched value in column Y Live
Network Configuration.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 68

 Manual Check Method (2)
 1. Compare the value on the live network with the baseline value.
 Step 4: Compare the value in column X Live Network Configuration with the value in
column J Baseline Value (Provided in R13). If the values are the same, enter OK in
column Y Baseline Value Check Result. If the values are different, enter NOK.
 2. Compare the value on the live network with the reasonable range of the parameter
value.
 Step 5: Compare the value in column Y Live Network Configuration with column K
Parameter Check Rule (Reasonableness). If the value is in the range of Parameter
Check Rule (Reasonableness), enter OK in column Z Reasonableness Check
Result. Otherwise, enter NOK.
 Step 6: According to the results in column Z, find the rows with NOK and determine
whether modification is required based on the value on the live network, reasonableness
check range, baseline value, and reasonableness check requirement. If modification is
required, enter Modify in column Aal. Otherwise, enter Not Modify.
 Step 7: If modification is not required, explain the reasons in column AB. If modification
is required, provide the new value.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 69

Manual Check Method (3)
 1. Compare the value on the live network with the baseline value.
 Step 8: Compare the value in column X Live Network Configuration with the value in column J
Baseline Value (Provided in R13). If the values are the same, enter OK in column Y Baseline
Value Check Result. If the values are different, enter NOK.
 2. Compare the value on the live network with the parameter reasonableness range.
 Step 9: Compare the value in column Y Live Network Configuration with column K Parameter
Check Rule (Reasonableness). If the value is in the range of Parameter Check Rule
(Reasonableness), enter OK in column Z Reasonableness Check Result. Otherwise, enter
NOK.
 3. Compare the value on the live network with the dependency rule.
 Step 10: Compare the value in column Y Live Network Configuration with column M Parameter
Check Rule (Dependency). If the value complies with the Parameter Check Rule (Dependency)
rule, enter OK in column AC Dependency Check Result. Otherwise, enter NOK.
 4. Compare the value on the live network with the consistency rule.
 Step 11: Compare the value in column Y Live Network Configuration with column N Parameter
Check Rule (Consistency). If the value complies with the Parameter Check Rule (Consistency)
rule, enter OK in column AD Consistency Check Result. Otherwise, enter NOK.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 70

 Example: Analysis on Parameter Check
Results in the Swap Project in Country P
 Parameter check results of the swap project on the live network

Cause of NotPass Final Parameter Check Result

You are advised to use the baseline

value.

You are advised to use the baseline

If the parameter is set to OFF, RTWP update is not performed in time, affecting access and call drop. value.

If this parameter is set to ON, more code reshuffling procedures will be initiated. The failure of the procedures You are advised to use the baseline
results in a higher call drop rate. value.

CE congestion becomes severe.

You are advised to use the baseline

This parameter works with CIO of neighboring cells. value.
You are advised to use the baseline
value.

You are advised to set the parameter

value in a reasonable range.
When the paramter is set to a smaller value, the power used by HSPA services is lower, which ensures the You are advised to set the parameter
access success rate. value in a reasonable range.

The result may differ, depending on specific scenario.

You are advised to set the parameter

value in a reasonable range.
You are advised to use the baseline
value.
You are advised to use the baseline
value.
You are advised to use the baseline
value.
You are advised to use the baseline
value.

Use the mapped

value.
You are advised to use the baseline
value.
You are advised to use the baseline
value.

You are advised to use the baseline

value.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 71

Contents
A. Applicable Scenarios
B. Parameter Check Principle
C. Parameter Categories
01. Access core parameters 02. Call drop core parameters
03. PS data transmission core parameters 04. Voice quality core parameters
05. Network coverage core parameters 06. Paging core parameters
07. RF channel core parameters 08. Capacity core parameters
09. Peer vendor IUR parameters 10. Interoperability core parameters
11. Core network core parameters 12. Transmission core parameters
13. Equipment core parameters 14. License core parameters
15. Terminal compatibility core parameters 16. Other core parameters

D. Tool
Tool guide
Manual check method

E. Appendixes
Maturity of function commercialization
Summary of deliverables

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 How to Obtain Maturity Information About
Commercial Use of Features (1)
 Commercial use maturity of features
 You are advised to enable the features that are commercialized on site as
required to indicate whether a feature supports commercial use.
 Link on 3ms website: http://3ms.huawei.com/3ms/unionSearch/unionSearch.do

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 73

 How to Obtain Maturity Information About
Commercial Use of Features (2)
 Contact person of Solution Testing Dept: Tao Chuanhui (employee ID: 00119320)
 Link on support website:
http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=
detailProductSimple&web_doc_id
=SC0000628054&doc_type=123-2&doc_type=123-2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 74

 Deliverables

UMTSÈ«²ÎÊý¼ì²é CFGMML-RNCxxx
20120820-È˹¤¼ì²é½»¸¶¼þ .rar

Output results of manual check Output results of the check using the tool

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 75

 How to Update the Parameter
Baseline?
1. The UMTS Parameter Optimization Manual.xls includes parameters about 16 topics, which are distinguished through the
existing Type field.
2. The UMTS Parameter Optimization Manual.xls includes parameter value ranges, check scenarios, and impacts. The
parameter principles, successful cases/failure cases, and other parameters related to these parameters are described in the
UMTS Parameter Optimization Manual.doc.
3. The UMTS Parameter Optimization Manual.xls is used as the input of parameters. Parameter topics focus on platform-based
comparison. The baseline owner (Huang Xiangrong/00137761) is responsible for updating the document.
4. The same parameters in different topics need to be processed based on certain rules, which are defined by the parameter
baseline owner.
5. The update cycle is temporarily set to once a week. Release Object Maintenance Dept (Chen Yiwen/00159220, Xie
Meng/00139580, Zhou Yang/00145062), AMS (Jiao Anqiang/00160716), and new product support (Hu Wensu/00129549). The
UMTS Full Parameter check Rule Table.xls and UMTS Parameter Optimization Manual.doc will be issued by the parameter
baseline owner by email and RMS.
6. The topic team and parameter baseline owner are jointly responsible for missing parameters. They handle the requests for
modifying and adding parameters.
7. The parameters that are beyond the recommended ranges but still in the parameter setting ranges must be described in the
UMTS Parameter Optimization Manual.doc.
8. In phase 1, collect and sort out all parameters. In phase 2, optimize and update the parameters.
9. The UMTS Full Parameter Check Rule Table.xls is issued before August 31, 2012 and the UMTS Parameter Optimization
Manual.doc will be issued depending on the workload.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 76

 Thank you
www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 77