Guide To Rectification For USN9810 in The Second Half of 2013V1.0-Updated by Tim

Guide to Rectification for
USN9810 in the second half of

2013
Issue
01
Date
2013-08-28
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2013-08-28)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co.,
Ltd.
Guide to Rectification for USN9810 in the second half of

2013
About This Document
About This Document

Overview
The rectification aims to solve some problems and reduce the number of accidents on the live
network. This document provides detailed guides for the rectification and must be followed
during the rectification.
Intended Audience
This document is intended for:
Technical support engineers
Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk,
which if not avoided, could result in minor or moderate
injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or
supplement important points of the main text.
Issue 01 (2013-08-28)

Ltd.
ii

2013
Contents
Contents
About This Document.......................................................................ii
1 Rectification Guide........................................................................5
1.1 Rectification for Setting Some MML Command Parameters and Software Parameters to Their
Recommended Values in USN9810 V900R011C02................................................................................................5
A Appendix.................................................................................... 15
A.1 Rectification Scope.........................................................................................................................................15
A.2 Contact Persons...............................................................................................................................................15
B Acronyms and Abbreviations.......................................................16
Issue 01 (2013-08-28)

Ltd.
iii
A Acronyms and Abbreviations

2013
Rectification Guide
1.1 Rectification for Setting Some MML

Command Parameters and Software
Parameters to Their Recommended Values in
USN9810 V900R011C02
Involved
Versions
USN9810 V900R011C02 and its patch versions
Involved
Devices
USN9810
Applicable
Scope
All sites outside China that use the preceding versions
Completio
n Time
2013-13-31
Manpower Input
0.2 person day
Key words: MML, configuration, software parameter

Summary:
To optimize the network and improve the network reliability, you need to set some parameters
in MML commands and software parameters to their recommended values.
[Problem Description]
The USN9810 uses MML commands to control service functions and uses software
parameters to optimize the network or improve the network reliability. You need to set some
parameters in MML commands and some software parameters to their recommended values.
These recommended values have been used in many sites and proved to be risk free.
The following table lists the MML commands involved in this rectification and their
functions.
Issue 01 (2013-08-28)

Ltd.

2013
MML
Command
Paramete
r
Description
Recommend
ed Value
SET
COMPATIBILIT
Y
DOADJUST
Modification
YES
Specifies whether to change the

value of Delivery Order in the
QoS profile based on the PDP
type. It is recommended that this
parameter be set to YES(Yes). In
this case, the value of Delivery
Order is changed to No-order.
Impact
In section 6.4.3.1 in 3GPP TS

23.107 Release 6, the value of
Delivery Order is described as
follows:
Delivery order should be set to

"no" for PDP Type = "IPv4" or
"IPv6". The SGSN shall ensure
that the appropriate value is set.
The RNC may not support the
setting of Delivery Order to Order
in later versions.
When Delivery Order is set to

Order, the RNC re-sequences
the disordered packets. This
consumes RNC resources and
may lead to resource
insufficiency. RNCs from
different vendors may have
different conditions.
When Delivery Order is set to

Order, some mainstream UEs
may experience RRC
connection setup failures if they
attempt to perform PS services
after entering the idle mode.
The UEs become normal after
being deactivated and activated
again.
For RNCs from certain vendors,

setting Delivery Order to Order
may increase the single-user
UDP data rate by about 10%
when the RNC resource usage
is low.
Set this parameter based on the

customer advice after informing
customers of the impact of the
parameter setting.
Involved sites
Issue 01 (2013-08-28)

Ltd.

2013
MML
Command
Paramete
r
Description
Recommend
ed Value
All sites that use USN9810

V900R011C02
ADD
CAUSEGRP
CAUSEGRPI
D
CAUSEGRP
NM
Modification
None
CAUSEGRPID specifies the

cause value group ID.
CAUSEGRPNM specifies the
cause value group name.
These parameters need to be set
as required.
Impact
None
Involved sites
V900R011C02
ADD
CAUSEMAP
CAUSEGRPI
D
CAUSERAN
GE
BGCAUSE
EDCAUSE
TCAUSE
Modification
None
CAUSEGRPID specifies the

cause value group ID, which must
have been configured by running
ADD CAUSEGRP.
CAUSERANGE specifies the
cause value range.
BGCAUSE specifies the start
original cause value.
EDCAUSE specifies the end
original cause value.
TCAUSE specifies the target
cause value after cause value
conversion. These parameters
need to be set to different values
as required.
Impact
None
Involved sites
V900R011C02
SET
GMMPROCTRL
SET
PMMPROCTRL
SET
EMMPROCTRL
Issue 01 (2013-08-28)
PROT
Modification
This command is used to set

parameters that control mobility
management procedures in special
scenarios. Specifically, these
parameters control which cause
values to deliver in the special
scenarios. With these parameter
settings, carriers can apply
compatible control mechanisms to

Ltd.
None

2013
MML
Command
Paramete
r
Description
Recommend
ed Value
devices in the live network.

Impact
None
Involved sites
V900R011C02
SET HTR
HTRFAILPE
RCENT
HTRSUCCP
ERCENT
HTRTARGE
TDELAY
Modification
HTRFAILPERCENT specifies
the HTR flow control start
threshold. You are advised to set
HTRFAILPERCENT to 65.
See
"Modification."
HTRSUCCPERCENT specifies
the HTR flow control stop
threshold. You are advised to set
HTRSUCCPERCENT to 85.
HTRTARGETDELAY specifies
the target HTR flow control delay.
A large delay during HTR flow
control message exchange will
result in call loss, and therefore
the actual delay must be shorter
than the target HTR flow control
delay. You are advised to set
HTRTARGETDELAY to 3500.
Impact
None
Involved sites
V900R011C02
MOD
GBAUTHCIPH
MOD
IUAUTHCIPH
AUTHEVEN
T
Modification
MOD GBAUTHCIPH and
MOD IUAUTHCIPH specifies
the settings for the authentication
options. To prevent unauthorized
subscribers from accessing the
network and incorrect matching
between MSs and numbers of the
MSs, enable the following
authentication options and retain
configurations for other options:
a)
PTMSI_SIG_NOMATCH
b)
PTMSI_SIG_NO_SIG
See
"Modification."
Impact
None
Issue 01 (2013-08-28)

Ltd.

2013
MML
Command
Paramete
r
Description
Recommend
ed Value
Involved sites
V900R011C02
The following table lists software parameters involved in this rectification and their functions.
Software
Parameter
Description
Recommend
ed Value
BYTE27.BIT4
Function
Specifies whether to enable flow control on the Gr

interface.
0: Disabled
1: Enabled
For details on the average number of attached users
supported by a USPU every ten seconds after flow control,
see the description of software parameter BYTE45.
Impact
When the number of 2G/3G attach messages bursts
in certain cases such as network failure, the average
number of attached users is limited by the software
parameter BYTE45.
Involved sites
All sites that use USN9810 V900R011C02
BYTE45.All
bits
Function
250
Specifies the average number of attached users

supported by a SPP every ten seconds after flow
control is enabled on the Gr interface.
Value range: 0 to 255
Default value: 0
When this software parameter is set to 0, 50 attached
users are supported by a USPU every ten seconds.
This software parameter does not control the
procedures where authentication sets and
subscription data are not required.
Impact
When the number of 2G/3G attach messages bursts
in certain cases such as network failure, the access
data rate is limited by the software parameter
BYTE45.
Involved sites
Issue 01 (2013-08-28)

Ltd.

2013
Software
Parameter
Description
Recommend
ed Value
BYTE27.BIT6
Function
This software parameter controls whether the MM

module discards messages that have been transferred
for more than the transfer time threshold.
0: Enabled. The MM module discards messages

that have been transferred for more than 10 times.
1: Disabled.
Impact
None
Involved sites
BYTE39.BIT1
Function
Controls whether messages sent over internal

interfaces are reported in user tracing tasks.
0: Not reported.
1: Reported.
Impact
None
Involved sites
BYTE59.BIT1
Function
Controls whether to enable the SCCP log function

on the SPP process.
0: Enabled.
Other: Disabled.
Impact
None
Involved sites
BYTE78.BIT3
Function
Controls whether to endlessly resend the

SIG_RESET message to the PCU if the PCU does
not respond to this message.
0: The SIG_RESET message is resent based on the

configured time.
1: The SIG_RESET message is endlessly resent.
Impact
None
Involved sites
Issue 01 (2013-08-28)

Ltd.

2013
Software
Parameter
Description
Recommend
ed Value
BYTE120.All
bits
Function
Controls whether to enable the SCCP log function

on the SGP process.
0: Enabled.
Other: Disabled.
Impact
None
Involved sites
BYTE193.BIT
5
Function
Controls whether to enable the DDR ECC detection

function on the EPU.
0: Disabled.
1: Enabled.
Impact
None
Involved sites
BYTE193.BIT
6
Function
Controls whether to enable the cache ECC detection

function on the EPU.
0: Disabled.
1: Enabled.
Impact
None
Involved sites
DWORD19.BI
T12
Function
Whether to automatically reset the SIG entity if the

number of cells on the SGSN decreases after the SIG
entity reset.
0: Automatically resets.
1: Not automatically reset.
Impact
None
Involved sites
DWORD46.BI
T7
Issue 01 (2013-08-28)
Function
Controls whether to switch over the EPUs after the

packet discard exception is detected on GTP data
Ltd.
10

2013
Software
Parameter
Description
Recommend
ed Value
transfer module.
0: Not switch over.
1: Switches over.
Impact
None
Involved sites
BYTE_EX45.B
IT2
Function
Controls whether the SGSN requests the MSC to

detach a UE over the Gs interface when the
SIPUsubscriber index processing unit on the SDU
modulesynchronizes the UE information.
0: Requests the MSC to detach a UE.
1: Not request the MSC to detach a UE.
Impact
None
Involved sites
[Root Causes]
After being verified in various application scenarios on the live network, recommended values
are provided for some parameters in MML commands and some software parameters. Using
those recommended values can optimize the network and improve the network reliability.
[Impact and Risks]

No risks. These recommended values have been used in many sites and proved to be risk free.
For detailed impacts, see the description for each parameter.
[Measures and Solutions]

Set the mentioned parameters to recommended values.
[Rectification Scope and Completion Time]

The rectification is applicable to all sites that use USN9810 V900R11C01.
[Rectification Guide]
Run the MML commands one by one or in batches.
The operation is as follows:
Step 1 For sites where Delivery order needs to be set to No-order, run the following command:
Issue 01 (2013-08-28)

Ltd.
11

2013
SET COMPATIBILITY: DOADJUST=YES;
Step 2 In the MML Command USN9810 window, run the following commands to adjust the
system configuration and software parameter settings:
SET
MOD
1;
MOD
1;
SET
SET
SET
SET
SET
SET
SET
SET
SET
SET
HTR: HTRTARGETDELAY=3500, HTRFAILPERCENT=65, HTRSUCCPERCENT=85;

IUAUTHCIPH: SUBRANGE=ALL_USER, AUTHEVENT=PTMSI_SIG_NOMATCH-1&PTMSI_SIG_NOSIGGBAUTHCIPH: SUBRANGE=ALL_USER, AUTHEVENT=PTMSI_SIG_NOMATCH-1&PTMSI_SIG_NOSIGSOFTPARAOFBIT: DT=BYTE, PARANUM=27, VALUE=VALUE_1, POSITION=4;
SOFTPARA: DT=BYTE, PARANUM=45, VALUE="250";
SOFTPARAOFBIT: DT=BYTE, PARANUM=27, VALUE=VALUE_0, POSITION=6;
SOFTPARA: DT=BYTE, PARANUM=120, VALUE="1";
SET SOFTPARAOFBIT: DT=BYTE_EX, PARANUM=45, VALUE=VALUE_1, POSITION=2;
Step 3 In the MML Command USN9810 window, run the following commands to change the
cause values for MM rejections in GSM and UMTS networks so that CS services are not
affected if PS services of MSs are rejected:
In the commands, the cause values are changed as follows:
The cause value #3 "illegal MS" is changed to #7 "GPRS service not allowed" for Attach or RAU
rejections in GSM and UMTS networks so that CS services of MSs are not affected.
The cause value #6 "illegal ME" is changed to #7 "GPRS service not allowed" for Attach or RAU
rejections in GSM and UMTS networks so that CS services of MSs are not affected.
The cause value #9 "MS identity cannot be derived by the network" is specified for DNS query
failures in inter-SGSN RAU procedures in GSM and UMTS networks.
The cause value #14 "GPRS services not allowed in this PLMN" is changed to #7 "GPRS service
not allowed" for Attach and inter-SGSN RAU rejections in a UMTS network so that CS services of
MSs are not affected.
ADD CAUSEGRP: CAUSEGRPID=109, CAUSEGRPNM="GB-HLR-HSS-ULR-REJ-CAUSE";

ADD CAUSEMAP: CAUSEGRPID=109, CAUSERANGE=SPECIAL, BGCAUSE=1, TCAUSE=7;// here
the value 1 is the cause code: UNKNOWN_SUBSCRIBER, it will be transfer to #7
GPRS service not allowed //
SET GMMPROCTRL: PROT=UPDATE_LOCATION, ULRHLRHSSREJ=109;
ADD CAUSEGRP: CAUSEGRPID=110, CAUSEGRPNM="IU-HLR-HSS-ULR-REJ-CAUSE";
ADD CAUSEMAP: CAUSEGRPID=110, CAUSERANGE=SPECIAL, BGCAUSE=1, TCAUSE=7;// ;//
here the value 1 is the cause code: UNKNOWN_SUBSCRIBER, it is transfer to #7
GPRS service not allowed //
SET PMMPROCTRL: PROT=UPDATE_LOCATION, ULRHLRHSSREJ=110;
ADD CAUSEGRP: CAUSEGRPID=111, CAUSEGRPNM="GB-HLR-HSS-ULR-REJ-CAUSE";
ADD CAUSEMAP: CAUSEGRPID=111, CAUSERANGE=SPECIAL, BGCAUSE=1, TCAUSE=7;// for
the AIR, here 1 is the cause code UNKNOWN_SUBSCRIBER is transfer to #7 GPRS
service not allowed//
ADD CAUSEMAP: CAUSEGRPID=111, CAUSERANGE=SPECIAL, BGCAUSE=9, TCAUSE=7;// for
the AIR, here 9 is the cause code ILLEGAL_MS is transfer to #7 GPRS service
not allowed//
Issue 01 (2013-08-28)

Ltd.
12

2013
SET GMMPROCTRL: PROT=AIR, AIRHLRHSSREJ=111; // AIR is AuthenticationInformation-Request//

ADD CAUSEGRP: CAUSEGRPID=112, CAUSEGRPNM="IU-HLR-HSS-ULR-REJ-CAUSE";
ADD CAUSEMAP: CAUSEGRPID=112, CAUSERANGE=SPECIAL, BGCAUSE=1, TCAUSE=7;//same
with Gb//
ADD CAUSEMAP: CAUSEGRPID=112, CAUSERANGE=SPECIAL, BGCAUSE=9, TCAUSE=7;//same
with Gb//
SET PMMPROCTRL: PROT=AIR, AIRHLRHSSREJ=112;// AIR is AuthenticationInformation-Request//
SET SOFTPARAOFBIT: DT=BYTE, PARANUM=49, VALUE=VALUE_1, POSITION=2;
SET SOFTPARA: DT=BYTE, PARANUM=50, VALUE="7";
SET GMMPROCTRL: PROT=CHECK_IMEI, CHKIMEICHKFAIL=7;
SET PMMPROCTRL: PROT=CHECK_IMEI, CHKIMEICHKFAIL=7;
SET GMMPROCTRL: PROT=AUTHENTICATION, AUTHRESCHKFAIL=7;
SET PMMPROCTRL: PROT=AUTHENTICATION, AUTHRESCHKFAIL=7;
SET GMMPROCTRL: PROT=INTER_RAU, INTERRAUDNSFAIL=9;
SET PMMPROCTRL: PROT=ATTACH, ATTACHROAMRST=7;
SET PMMPROCTRL: PROT=INTER_RAU, INTERRAUROAMRST=7,INTERRAUDNSFAIL=9;
Step 4 In the MML Command USN9810 window, run the following commands to change the
cause values for MM rejections in 4G networks so that CS services and services in the GSM
and UMTS networks are not affected for UEs:
In the commands, the cause values #8 "EPS services and non-EPS services not allowed", #11 "PLMN
not allowed", and #7 "EPS services not allowed" are changed to #15 "No suitable cells in tracking area."
ADD CAUSEGRP: CAUSEGRPID=113, CAUSEGRPNM="S1-HLR-HSS-ULR-REJ-CAUSE";
Step 5
ADD CAUSEMAP: CAUSEGRPID=113, CAUSERANGE=SPECIAL, BGCAUSE=5001, TCAUSE=15; //

(By default DIAMETER_ERROR_USER_UNKNOWN (5001) will be transfer to #8 "EPS
services and non-EPS services not allowed", After this command it will be
transfer to #15 "No suitable cells in tracking area.")//
Step 6
ADD CAUSEMAP: CAUSEGRPID=113, CAUSERANGE=SPECIAL, BGCAUSE=5004, TCAUSE=15;//

By default DIAMETER_ERROR_ROAMING_NOT_ALLOWED (5004) will be transfer to #11
PLMN not allowed, after this command it will transfer to #15 No suitable
cells in tracking area //
ADD CAUSEMAP: CAUSEGRPID=113, CAUSERANGE=SPECIAL, BGCAUSE=4181, TCAUSE=15;
Step 7
//by default DIAMETER_AUTHENTICATION_DATA_UNAVAILABLE (4181) will be transfer

to #7 EPS services not allowed, after this command it will be transfer to 15
No suitable cells in tracking area //
Step 8
SET
SET
SET
SET
SET
SET
EMMPROCTRL:
EMMPROCTRL:
EMMPROCTRL:
EMMPROCTRL:
EMMPROCTRL:
EMMPROCTRL:
PROT=ATTACH, ATTACHROAMRST=15;
PROT=INTER_TAU, INTERTAUROAMRST=15;
PROT=AUTHENTICATION, AUTHRESCHKFAIL=15;
PROT=CHECK_IMEI, CHKIMEICHKFAIL=15;
PROT=UPDATE_LOCATION, ULRHSSREJ=113;
PROT=AIR, AIRHSSREJ=113;
Step 9 Copy and run the preceding MML commands one by one or in batches on the LMT. The batch
configuration window can be entered as follows:
Issue 01 (2013-08-28)

Ltd.
13

2013
Before you run the MML commands in batches, add USE ME:MEID=X; to the first line. X
indicates the ID of the USN9810.
----End
Issue 01 (2013-08-28)

Ltd.
14

2013
Figure 1.1
Acronyms and
Abbreviations
Numeric
3GPP
3rd Generation Partnership Project
A
APN
access point name
C
CAMEL
Customized Applications for Mobile network Enhanced Logic
CDR
charging data record
CPCI
Compact Peripheral Component Interconnect
CPI
customer product information
CS
circuit switched
CSFB
circuit switched fallback
D
DNS
domain name server
E
EPS
evolved packet system
F
FOA
first office application
G
GGSN
Issue 01 (2013-08-28)
gateway GPRS support node

Ltd.
15

2013
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communications
GTP
GPRS tunneling protocol
GTP-U
GPRS Tunneling Protocol-User plane
I
iGWB
iGateWay Bill
IMSI
international mobile subscriber identity
IP
Internet Protocol
L
LMT
local maintenance terminal
LTE
Long Term Evolution
M
MME
mobility management entity
MML
man-machine language
MS
mobile station
MSC
mobile switching center
N
NE
network element
P
PCRF
policy and charging rules function
PDF
power distribution frame
PDP
Packet Data Protocol
PS
packet switched
Q
QoS
Issue 01 (2013-08-28)
quality of service

Ltd.
16

2013
R
RAB
radio access bearer
RAU
routing area update
RCM
resource control management
RNC
radio network controller
RRC
radio resource control
S
SAAL
Signaling ATM Adaptation Layer
SGP
SIGTRAN process
SGSN
serving GPRS support node
SMS
short message service
T
TAU
tracking area update
TCP
Transmission Control Protocol
UE
user equipment
UMTS
Universal Mobile Telecommunications System
V
VLR
Issue 01 (2013-08-28)
visitor location register

Ltd.
17

Guide To Rectification For USN9810 in The Second Half of 2013V1.0-Updated by Tim

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guide To Rectification For USN9810 in The Second Half of 2013V1.0-Updated by Tim

Uploaded by

Copyright:

Available Formats

Guide to Rectification for

USN9810 in the second half of

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential