Professional Documents
Culture Documents
V300R006C10
CLI Interface Instruction
Document
Version 1.130
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
Website: http://www.huawei.com
Telephone: 4008302118
Email: Support@huawei.com.
Purpose
This document describes the man-machine language (MML) commands managed on the
command line interface (CLI) of the Unified Policy and Charging Controller (UPCC). The
commands are used to manage the following objects: Condition Group, Action Group, Service
Flow, Notification, Rating, Rule, Policy, Service Provider, Quota, Account, Accumulation,
Service, Service Package, Mutex Group, Application Service Mapping, Domain, Charging
Server, Subscriber Group, Terminal Type, Roam Region, PLMN, Service Zone, and Message
Template. This document provides guides to obtain the information about each command,
such as parameters, parameter types, value ranges of parameters, and command results.
Intended Audience
This document is intended for:
Technical support engineers
Maintenance engineers
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Update PROFILEUPDATE to
PROFILEUPDATEACTION
Update parameter name of subscribers
extend attribute under
PROFILEUPDATEACTION.
Add error code 94586 for ADD/MOD
SERVICE
2011-07-19 v1.04 Deleted error codes 1001, 1003, 1004, Kong Sanwen
1009, 1010, 1118 and added error code
8201 mapping those deleted error codes.
2011-07-19 v1.03 Revised parameters and MML command Xu Hu
format of the account and quota based on
the trouble ticket DTS2011071501009.
2011-07-19 v1.02 Added description that UNICODE Zhang Xiaolin
characters are not supported by MML 00257401
commands based on the trouble ticket
DTS2011062305047.
2011-07-19 v1.01 Revised the format of time based on the Xu Hu
trouble ticket DTS2011071602302.
2011-06-29 v1.00 Initial release.
2012-11-16 v1.01 Modify ADD QUOTA and MOD Cheng Zhi
QUOTA commands to support Sy Quota.
2012-11-16 v1.02 Added the Liu Hongyan
RECHARGENOTIFICATION
parameter in the ADD QUOTA and
MOD QUOTA commands.
2012-12-13 v1.03 Revised based on the trouble ticket Yang Ming
DTS2012091107995. 00267273
2012-12-22 v1.04 Deleted error codes 94564and revised Yang Ming
description for error code 00267273
94562,94563,94565,94566,94567 based
on the trouble ticket
DTS2012122007515.
2012-12-22 v1.05 Add SERVICEFLOWDETECTION Yang Ming
action 00267273
2013-11-19 v1.06 Added ADD AUXILIARYAREA and Liu Kaiwei
RMV AUXILIARYAREA in the service 00257350
zone management.
2013-11-28 v1.07 Added description about error codes Liu Kaiwei
12609 in the output of ADD 00257350
SERVICEQUOTA and RMV
SERVICEQUOTA based on the trouble
ticket DTS2013112603365.
2013-12-03 v1.08 Added ADD/MOD/RMV Guan Zehui
TDFAPPLICATIONIDENTIFIERAD 00257400
D/MOD/RMV MUTENOTIFICATION
and ADD/MOD/RMV
REDIRECTINFORMATION in the
action group zone management.
Contents
2 Operation List................................................................................................................................9
3 Object List.....................................................................................................................................10
3.1 Condition Group Management........................................................................................................................10
3.2 Action Group Management..............................................................................................................................10
3.3 Service Flow Management...............................................................................................................................11
3.4 Notification Management................................................................................................................................11
3.5 Rating Management.........................................................................................................................................12
3.6 Rule Management............................................................................................................................................12
3.7 Policy Management.........................................................................................................................................12
5.14.4 Result....................................................................................................................................................56
5.15 Delete Redirection Action (RMV REDIRECTION).....................................................................................56
5.15.1 Command Description..........................................................................................................................56
5.15.2 Command Parameter............................................................................................................................56
5.15.3 Command Format.................................................................................................................................56
5.15.4 Result....................................................................................................................................................57
5.16 Add AFChargingIdentifier Action (ADD AFCHARGINGIDENTIFIER)....................................................57
5.16.1 Command Description..........................................................................................................................57
5.16.2 Command Parameter............................................................................................................................57
5.16.3 Command Format.................................................................................................................................58
5.16.4 Result....................................................................................................................................................58
5.17 Modify AFChargingIdentifier Action (MOD AFCHARGINGIDENTIFIER)..............................................59
5.17.1 Command Description..........................................................................................................................59
5.17.2 Command Parameter............................................................................................................................59
5.17.3 Command Format.................................................................................................................................59
5.17.4 Result....................................................................................................................................................59
5.18 Delete AFChargingIdentifier Action (RMV AFCHARGINGIDENTIFIER)................................................60
5.18.1 Command Description..........................................................................................................................60
5.18.2 Command Parameter............................................................................................................................60
5.18.3 Command Format.................................................................................................................................60
5.18.4 Result....................................................................................................................................................61
5.19 Add AFMediaFlowsNumber Action (ADD AFMEDIAFLOWSNUMBER)................................................61
5.19.1 Command Description..........................................................................................................................61
5.19.2 Command Parameter............................................................................................................................61
5.19.3 Command Format.................................................................................................................................62
5.19.4 Result....................................................................................................................................................62
5.20 Modify AFMediaFlowsNumber Action (MOD AFMEDIAFLOWSNUMBER)..........................................63
5.20.1 Command Description..........................................................................................................................63
5.20.2 Command Parameter............................................................................................................................63
5.20.3 Command Format.................................................................................................................................64
5.20.4 Result....................................................................................................................................................64
5.21 Delete AFMediaFlowsNumber Action (RMV AFMEDIAFLOWSNUMBER)............................................65
5.21.1 Command Description..........................................................................................................................65
5.21.2 Command Parameter............................................................................................................................65
5.21.3 Command Format.................................................................................................................................65
5.21.4 Result....................................................................................................................................................65
5.22 Add UsageReport Action (ADD USAGEREPORT)......................................................................................66
5.22.1 Command Description..........................................................................................................................66
5.22.2 Command Parameter............................................................................................................................66
5.22.3 Command Format.................................................................................................................................66
5.22.4 Result....................................................................................................................................................66
5.23 Modify UsageReport Action (MOD USAGEREPORT)................................................................................67
5.56.4 Result..................................................................................................................................................124
5.57 Delete TDFAPPLICATIONIDENTIFIER <RMV TDFAPPLICATIONIDENTIFIER >...........................124
5.57.1 Command Description........................................................................................................................124
5.57.2 Command Parameter..........................................................................................................................124
5.57.3 Command Format...............................................................................................................................125
5.57.4 Result..................................................................................................................................................125
5.58 Add MUTENOTIFICATION<ADD MUTENOTIFICATION>.................................................................125
5.58.1 Command Description........................................................................................................................125
5.58.2 Command Parameter..........................................................................................................................125
5.58.3 Command Format...............................................................................................................................126
5.58.4 Result..................................................................................................................................................126
5.59 Modify MUTENOTIFICATION <MOD MUTENOTIFICATION >.........................................................127
5.59.1 Command Description........................................................................................................................127
5.59.2 Command Parameter..........................................................................................................................127
5.59.3 Command Format...............................................................................................................................128
5.59.4 Result..................................................................................................................................................128
5.60 Delete MUTENOTIFICATION <RMV MUTENOTIFICATION >...........................................................128
5.60.1 Command Description........................................................................................................................128
5.60.2 Command Parameter..........................................................................................................................129
5.60.3 Command Format...............................................................................................................................129
5.60.4 Result..................................................................................................................................................129
5.61 Add REDIRECTINFORMATION<ADD REDIRECTINFORMATION>.................................................129
5.61.1 Command Description........................................................................................................................129
5.61.2 Command Parameter..........................................................................................................................130
5.61.3 Command Format...............................................................................................................................131
5.61.4 Result..................................................................................................................................................131
5.62 Modify REDIRECTINFORMATION <MOD REDIRECTINFORMATION >.........................................132
5.62.1 Command Description........................................................................................................................132
5.62.2 Command Parameter..........................................................................................................................132
5.62.3 Command Format...............................................................................................................................133
5.62.4 Result..................................................................................................................................................134
5.63 Delete REDIRECTINFORMATION<RMV REDIRECTINFORMATION >............................................134
5.63.1 Command Description........................................................................................................................134
5.63.2 Command Parameter..........................................................................................................................134
5.63.3 Command Format...............................................................................................................................135
5.63.4 Result..................................................................................................................................................135
5.64 Add PROFILEUPDATEACTION<ADD PROFILEUPDATEACTION >.................................................135
5.64.1 Command Description........................................................................................................................135
5.64.2 Command Parameter..........................................................................................................................135
5.64.3 Command Format...............................................................................................................................137
5.64.4 Result..................................................................................................................................................138
5.65 Modify PROFILEUPDATEACTION <MOD PROFILEUPDATEACTION >..........................................139
7 Notification Management........................................................................................................155
8 Rating Management..................................................................................................................163
8.1 Add Rating (ADD RATING).........................................................................................................................163
8.1.1 Command Description..........................................................................................................................163
8.1.2 Command Parameter............................................................................................................................163
8.1.3 Command Format.................................................................................................................................164
8.1.4 Result....................................................................................................................................................164
8.2 Modify Rating (MOD RATING)...................................................................................................................165
8.2.1 Command Description..........................................................................................................................165
8.2.2 Command Parameter............................................................................................................................165
8.2.3 Command Format.................................................................................................................................165
8.2.4 Result....................................................................................................................................................166
8.3 Delete Rating (RMV RATING).....................................................................................................................166
8.3.1 Command Description..........................................................................................................................166
8.3.2 Command Parameter............................................................................................................................166
8.3.3 Command Format.................................................................................................................................166
8.3.4 Result....................................................................................................................................................167
9 Rule Management.....................................................................................................................168
9.1 Add Rule (ADD RULE)................................................................................................................................168
9.1.1 Command Description..........................................................................................................................168
9.1.2 Command Parameter............................................................................................................................168
9.1.3 Command Format.................................................................................................................................172
9.1.4 Result....................................................................................................................................................173
9.2 Modify Rule (MOD RULE)..........................................................................................................................174
9.2.1 Command Description..........................................................................................................................174
9.2.2 Command Parameter............................................................................................................................174
9.2.3 Command Format.................................................................................................................................178
9.2.4 Result....................................................................................................................................................179
9.3 Delete Rule (RMV RULE)............................................................................................................................180
9.3.1 Command Description..........................................................................................................................180
9.3.2 Command Parameter............................................................................................................................180
9.3.3 Command Format.................................................................................................................................180
9.3.4 Result....................................................................................................................................................180
9.4 ADD Rule Condition Group <ADD RULECONDITIONGROUP>.............................................................181
9.4.1 Command Description..........................................................................................................................181
9.4.2 Command Parameter............................................................................................................................181
9.4.3 Command Format.................................................................................................................................181
9.4.4 Result....................................................................................................................................................182
9.5 Delete Rule Condition Group <RMV RULECONDITIONGROUP>..........................................................182
9.5.1 Command Description..........................................................................................................................182
9.5.2 Command Parameter............................................................................................................................182
9.5.3 Command Format.................................................................................................................................183
9.5.4 Result....................................................................................................................................................183
10 Policy Management.................................................................................................................184
10.1 Add Policy (ADD POLICY)........................................................................................................................184
10.1.1 Command Description........................................................................................................................184
10.1.2 Command Parameter..........................................................................................................................184
10.1.3 Command Format...............................................................................................................................184
10.1.4 Result..................................................................................................................................................185
10.2 Modify Policy (MOD POLICY)..................................................................................................................185
10.2.1 Command Description........................................................................................................................185
10.2.2 Command Parameter..........................................................................................................................185
10.2.3 Command Format...............................................................................................................................186
10.2.4 Result..................................................................................................................................................186
10.3 Delete Policy (RMV POLICY)....................................................................................................................186
10.3.1 Command Description........................................................................................................................186
10.3.2 Command Parameter..........................................................................................................................186
10.3.3 Command Format...............................................................................................................................187
10.3.4 Result..................................................................................................................................................187
10.4 Add Policy Trigger (ADD POLICYTRIGGER)..........................................................................................187
10.4.1 Command Description........................................................................................................................187
10.4.2 Command Parameter..........................................................................................................................187
10.4.3 Command Format...............................................................................................................................188
10.4.4 Result..................................................................................................................................................188
10.5 Delete Policy Trigger (RMV POLICYTRIGGER)......................................................................................188
10.5.1 Command Description........................................................................................................................188
10.5.2 Command Parameter..........................................................................................................................189
10.5.3 Command Format...............................................................................................................................189
10.5.4 Result..................................................................................................................................................189
10.6 Add Policy Rule (ADD POLICYRULE).....................................................................................................190
10.6.1 Command Description........................................................................................................................190
10.6.2 Command Parameter..........................................................................................................................190
10.6.3 Command Format...............................................................................................................................190
10.6.4 Result..................................................................................................................................................190
10.7 Delete Policy Rule (RMV POLICYRULE).................................................................................................191
10.7.1 Command Description........................................................................................................................191
10.7.2 Command Parameter..........................................................................................................................191
10.7.3 Command Format...............................................................................................................................191
10.7.4 Result..................................................................................................................................................191
12 Quota Management.................................................................................................................197
12.1 Add Quota (ADD QUOTA).........................................................................................................................197
12.1.1 Command Description........................................................................................................................197
12.1.2 Command Parameter..........................................................................................................................197
12.1.3 Command Format...............................................................................................................................204
12.1.4 Result..................................................................................................................................................206
12.2 Modify Quota (MOD QUOTA)...................................................................................................................206
12.2.1 Command Description........................................................................................................................206
12.2.2 Command Parameter..........................................................................................................................207
12.2.3 Command Format...............................................................................................................................213
12.2.4 Result..................................................................................................................................................214
12.3 Delete Quota (RMV QUOTA).....................................................................................................................216
12.3.1 Command Description........................................................................................................................216
12.3.2 Command Parameter..........................................................................................................................216
13 Account Management.............................................................................................................217
13.1 Add Account (ADD ACCOUNT)................................................................................................................217
13.1.1 Command Description........................................................................................................................217
13.1.2 Command Parameter..........................................................................................................................217
13.1.3 Command Format...............................................................................................................................220
13.1.4 Result..................................................................................................................................................221
13.2 Modify Account (MOD ACCOUNT)..........................................................................................................221
13.2.1 Command Description........................................................................................................................221
13.2.2 Command Parameter..........................................................................................................................221
13.2.3 Command Format...............................................................................................................................224
13.2.4 Result..................................................................................................................................................225
13.3 Delete Account (RMV ACCOUNT)............................................................................................................226
13.3.1 Command Description........................................................................................................................226
13.3.2 Command Parameter..........................................................................................................................226
13.3.3 Command Format...............................................................................................................................226
13.3.4 Result..................................................................................................................................................226
14 Accumulation Management..................................................................................................227
14.1 Add Accumulation (ADD ACCUMULATION)..........................................................................................227
14.1.1 Command Description........................................................................................................................227
14.1.2 Command Parameter..........................................................................................................................227
14.1.3 Command Format...............................................................................................................................232
14.1.4 Result..................................................................................................................................................233
14.2 Modify Accumulation (MOD ACCUMULATION)....................................................................................233
14.2.1 Command Description........................................................................................................................233
14.2.2 Command Parameter..........................................................................................................................234
14.2.3 Command Format...............................................................................................................................238
14.2.4 Result..................................................................................................................................................239
14.3 Delete Accumulation (RMV ACCUMULATION)......................................................................................239
14.3.1 Command Description........................................................................................................................239
14.3.2 Command Parameter..........................................................................................................................239
14.3.3 Command Format...............................................................................................................................239
14.3.4 Result..................................................................................................................................................240
14.4 Add Accumulation Quota (ADD ACCUMULATIONQUOTA)..................................................................240
14.4.1 Command Description........................................................................................................................240
14.4.2 Command Parameter..........................................................................................................................240
14.4.3 Command Format...............................................................................................................................241
14.4.4 Result..................................................................................................................................................241
14.5 Delete Accumulation Quota (RMV ACCUMULATIONQUOTA)..............................................................242
14.5.1 Command Description........................................................................................................................242
15 Service Management...............................................................................................................244
15.1 Add Service (ADD SERVICE)....................................................................................................................244
15.1.1 Command Description........................................................................................................................244
15.1.2 Command Parameter..........................................................................................................................244
15.1.3 Command Format...............................................................................................................................248
15.1.4 Result..................................................................................................................................................249
15.2 Modify Service (MOD SERVICE)..............................................................................................................250
15.2.1 Command Description........................................................................................................................250
15.2.2 Command Parameter..........................................................................................................................251
15.2.3 Command Format...............................................................................................................................254
15.2.4 Result..................................................................................................................................................255
15.3 Delete Service (RMV SERVICE)................................................................................................................257
15.3.1 Command Description........................................................................................................................257
15.3.2 Command Parameter..........................................................................................................................257
15.3.3 Command Format...............................................................................................................................257
15.3.4 Result..................................................................................................................................................257
15.4 Add Service Policy (ADD SERVICEPOLICY)..........................................................................................258
15.4.1 Command Description........................................................................................................................258
15.4.2 Command Parameter..........................................................................................................................258
15.4.3 Command Format...............................................................................................................................258
15.4.4 Result..................................................................................................................................................258
15.5 Delete Service Policy (RMV SERVICEPOLICY)......................................................................................259
15.5.1 Command Description........................................................................................................................259
15.5.2 Command Parameter..........................................................................................................................259
15.5.3 Command Format...............................................................................................................................259
15.5.4 Result..................................................................................................................................................259
15.6 Add Service Quota (ADD SERVICEQUOTA)............................................................................................260
15.6.1 Command Description........................................................................................................................260
15.6.2 Command Parameter..........................................................................................................................260
15.6.3 Command Format...............................................................................................................................260
15.6.4 Result..................................................................................................................................................260
15.7 Delete Service Quota (RMV SERVICEQUOTA)........................................................................................261
15.7.1 Command Description........................................................................................................................261
15.7.2 Command Parameter..........................................................................................................................261
15.7.3 Command Format...............................................................................................................................261
15.7.4 Result..................................................................................................................................................262
16 Package Management.............................................................................................................263
16.1 Add Package (ADD PACKAGE).................................................................................................................263
19 Domain Management.............................................................................................................284
19.1 Add Domain (ADD DOMAIN)...................................................................................................................284
19.1.1 Command Description........................................................................................................................284
19.1.2 Command Parameter..........................................................................................................................284
19.1.3 Command Format...............................................................................................................................284
19.1.4 Result..................................................................................................................................................285
19.2 Modify Domain (MOD DOMAIN).............................................................................................................285
19.2.1 Command Description........................................................................................................................285
19.2.2 Command Parameter..........................................................................................................................285
19.2.3 Command Format...............................................................................................................................285
19.2.4 Result..................................................................................................................................................286
19.3 Delete Domain (RMV DOMAIN)...............................................................................................................286
19.3.1 Command Description........................................................................................................................286
19.3.2 Command Parameter..........................................................................................................................286
19.3.3 Command Format...............................................................................................................................286
19.3.4 Result..................................................................................................................................................287
23.1.4 Result..................................................................................................................................................325
23.2 Modify Roam Region (MOD ROAMREGION).........................................................................................325
23.2.1 Command Description........................................................................................................................325
23.2.2 Command Parameter..........................................................................................................................325
23.2.3 Command Format...............................................................................................................................325
23.2.4 Result..................................................................................................................................................326
23.3 Delete Roam Region (RMV ROAMREGION)...........................................................................................326
23.3.1 Command Description........................................................................................................................326
23.3.2 Command Parameter..........................................................................................................................326
23.3.3 Command Format...............................................................................................................................326
23.3.4 Result..................................................................................................................................................326
23.4 Add Roam Region PLMN (ADD ROAMREGIONPLMN)........................................................................327
23.4.1 Command Description........................................................................................................................327
23.4.2 Command Parameter..........................................................................................................................327
23.4.3 Command Format...............................................................................................................................327
23.4.4 Result..................................................................................................................................................328
23.5 Delete Roam Region PLMN (RMV ROAMREGIONPLMN)....................................................................328
23.5.1 Command Description........................................................................................................................328
23.5.2 Command Parameter..........................................................................................................................328
23.5.3 Command Format...............................................................................................................................328
23.5.4 Result..................................................................................................................................................329
24 PLMN Management................................................................................................................330
24.1 Add PLMN (ADD PLMN)..........................................................................................................................330
24.1.1 Command Description........................................................................................................................330
24.1.2 Command Parameter..........................................................................................................................330
24.1.3 Command Format...............................................................................................................................331
24.1.4 Result..................................................................................................................................................331
24.2 Modify PLMN (MOD PLMN)....................................................................................................................332
24.2.1 Command Description........................................................................................................................332
24.2.2 Command Parameter..........................................................................................................................332
24.2.3 Command Format...............................................................................................................................332
24.2.4 Result..................................................................................................................................................333
24.3 Delete PLMN (RMV PLMN)......................................................................................................................333
24.3.1 Command Description........................................................................................................................333
24.3.2 Command Parameter..........................................................................................................................333
24.3.3 Command Format...............................................................................................................................333
24.3.4 Result..................................................................................................................................................334
24.4 Add PLMN SGSN (ADD PLMNSGSN).....................................................................................................334
24.4.1 Command Description........................................................................................................................334
24.4.2 Command Parameter..........................................................................................................................334
24.4.3 Command Format...............................................................................................................................335
24.4.4 Result..................................................................................................................................................335
24.5 Modify PLMN SGSN (MOD PLMNSGSN)...............................................................................................336
24.5.1 Command Description........................................................................................................................336
24.5.2 Command Parameter..........................................................................................................................336
24.5.3 Command Format...............................................................................................................................337
24.5.4 Result..................................................................................................................................................337
24.6 Delete PLMN SGSN (RMV PLMNSGSN).................................................................................................338
24.6.1 Command Description........................................................................................................................338
24.6.2 Command Parameter..........................................................................................................................338
24.6.3 Command Format...............................................................................................................................338
24.6.4 Result..................................................................................................................................................339
24.7 Add PLMN ANGW (ADD PLMNANGW).................................................................................................339
24.7.1 Command Description........................................................................................................................339
24.7.2 Command Parameter..........................................................................................................................339
24.7.3 Command Format...............................................................................................................................340
24.7.4 Result..................................................................................................................................................340
24.8 Modify PLMN ANGW (MOD PLMNANGW)...........................................................................................341
24.8.1 Command Description........................................................................................................................341
24.8.2 Command Parameter..........................................................................................................................341
24.8.3 Command Format...............................................................................................................................342
24.8.4 Result..................................................................................................................................................342
24.9 Delete PLMN ANGW (RMV PLMNANGW).............................................................................................343
24.9.1 Command Description........................................................................................................................343
24.9.2 Command Parameter..........................................................................................................................343
24.9.3 Command Format...............................................................................................................................343
24.9.4 Result..................................................................................................................................................343
25.3.4 Result..................................................................................................................................................347
25.4 Add Service Zone Area (ADD SERVICEZONEAREA).............................................................................347
25.4.1 Command Description........................................................................................................................347
25.4.2 Command Parameter..........................................................................................................................347
25.4.3 Command Format...............................................................................................................................348
25.4.4 Result..................................................................................................................................................349
25.5 Modify Service Zone Area (MOD SERVICEZONEAREA).......................................................................349
25.5.1 Command Description........................................................................................................................349
25.5.2 Command Parameter..........................................................................................................................349
25.5.3 Command Format...............................................................................................................................350
25.5.4 Result..................................................................................................................................................350
25.6 Delete Service Zone Area (RMV SERVICEZONEAREA).........................................................................352
25.6.1 Command Description........................................................................................................................352
25.6.2 Command Parameter..........................................................................................................................352
25.6.3 Command Format...............................................................................................................................352
25.6.4 Result..................................................................................................................................................352
25.7 Add Auxiliary Area (ADD AUXILIARYAREA).........................................................................................353
25.7.1 Command Description........................................................................................................................353
25.7.2 Command Parameter..........................................................................................................................353
25.7.3 Command Format...............................................................................................................................353
25.7.4 Result..................................................................................................................................................354
25.8 Delete Auxiliary Area (RMV AUXILIARYAREA)....................................................................................354
25.8.1 Command Description........................................................................................................................354
25.8.2 Command Parameter..........................................................................................................................355
25.8.3 Command Format...............................................................................................................................355
25.8.4 Result..................................................................................................................................................355
26.3.4 Result..................................................................................................................................................362
27 Login Management.................................................................................................................364
27.1 User Login (LGI).........................................................................................................................................364
27.1.1 Command Description........................................................................................................................364
27.1.2 Command Parameter..........................................................................................................................364
27.1.3 Command Format...............................................................................................................................364
27.1.4 Result..................................................................................................................................................364
27.2 User Logout (LGO).....................................................................................................................................365
27.2.1 Command Description........................................................................................................................365
27.2.2 Command Parameter..........................................................................................................................365
27.2.3 Command Format...............................................................................................................................365
27.2.4 Result..................................................................................................................................................365
34.2.4 Result..................................................................................................................................................394
34.3 Delete Quota Status Map (RMV QUOTASTATUSMAP)...........................................................................395
34.3.1 Command Description........................................................................................................................395
34.3.2 Command Parameter..........................................................................................................................395
34.3.3 Command Format...............................................................................................................................395
34.3.4 Result..................................................................................................................................................395
1 Description
//Add all the CLI client IP address to ACL rule group to permit the CLI client to access port 7780
//Apply the ACL rule group to the CLI service network card
ADD ACLFILTER: SRN=[UPPDU board1 subrack number], SN=[UPPDU board1 slot number], PORT=[CLI service network card
name], ACLGRPNUM=3000;
ADD ACLFILTER: SRN=[UPPDU board2 subrack number], SN=[UPPDU board2 slot number], PORT=[CLI service network card
name], ACLGRPNUM=3000;
1.1.3 Other
When CLI client connect to UPCC server, after TCP/IP three times handshakes, UPCC will
send a response message as RETCODE = 0 Operation is successful to the client if the
number of the CLI client is not exceed the system limitation. The figure is as follow:
If the number of the CLI client is exceed the system limitation, UPCC will send a response
message as RETCODE = 1062 Maximum clients are connected. No more connection after
TCP/IP three times handshakes.
For example, if you want to add a condition group with Condition Group Name set to abcd
and Description set to abcd Condition Group, run the following command:
ADD CONDITIONGROUP: CONDITIONGROUPNAME = "abcd", DESCRIPTION =
"abcd Condition Group";
1.3.1 String/Characters
The value of the parameter is a string of characters from A to Z, from a to z, from 0 to 9, or
other characters in the formats that the Windows operating system supports except for
symbols such as a colon (:), comma (,), equal sign (=), and semicolon (;).
Table 1.1 lists the characters that are not supported by the parameters of the string/characters
type.
FF (form feeding) \f
LF (line feed) \n
CR (carriage return) \r
HT (tab) \t
VT (home) \v
Comma ,
Less than <
More than >
Percentage %
Number sign #
Ampersand &
Plus sign +
Left square bracket [
Right square bracket ]
Semicolon ;
Slash /
Equal sign =
Double quotation mark "
Single quotation mark '
Characters that is not allowed in 0x00 - 0x08,0x0b - 0x0c, and 0x0e - 0x1f
the XML specifications
1.3.2 HexString
The value of the parameter consists of digits from 0 to 9 and characters from a to f or A to F,
for example, 98AF.
1.3.3 Number
The value of the parameter is an Arabic number consisting of digits from 0 to 9.
1.3.4 Boolean
The value of the parameter is TRUE or FALSE.
1.3.5 Enumerated
The values of the parameter are enumerated names or values.
1.3.6 DateTime
The value of the parameter has the following three formats:
YYYY&MM&DD&HH&MM&SS, YYYY&MM&DD, and HH&MM&SS. Add a zero in
front of the month, day, hour, minute, or second if the month, day, hour, minute, or second is
a one-digit number. Values in the YYYY&MM&DD&HH&MM&SS, YYYY&MM&DD,
and HH&MM&SS format are strings of 19, 10, and 8 characters respectively.
1.4.4 Result
The UPCC will return the output of each command after processing the command, no matter
whether the command execution succeeds or not. There are two types of execution results:
successful and failed.
If the operation is successful, code 0 is displayed:
If the operation is not successful, the related non-0 error code with error description is
displayed.
UTF8String All characters are supported. The value length depends on the
length of the object attribute.
Enumerated The value depends on the enumerated values of the object
attribute.
Unsigned32 [0, 4294967295]
Integer32 [0, 2147483647]
Float32/Float64 [0, 10000000.0000], accurate to four digits after the decimal
point
IPv4Address The format is D.D.D.D [/MaskLength]. D is an 8-digit decimal
number. The value of MaskLength is less than or equal to 32.
IPv6Prefix The format is X:X:X:X:X:X:X:X [/PrefixLen]. X is a 16-digit
hexadecimal number. The value of PrefixLen is less than or
equal to128.
The X:X:X:X:X:X:D.D.D.D format with an IPv4 address
(D.D.D.D) inserted can also be used. X is a 16-digit
hexadecimal number, and D is an 8-digit decimal number.
One or any number of consecutive groups of 0 value may be
replaced with two colons (::). Therefore, the address
X:X:X:0:0:0:X:X can be further simplified and expressed as
X:X:X::X:X.
IPv6Address Same as IPv6Prefix
OctetString The value contains only numbers or characters A(a)-F(f). The
value length depends on the length of the object attribute.
DateTime abs|2011-06-15 00:00:00#2011-06-22 00:00:00
(System.DateTime) or
rel|year(*) mon(1:2:3:4:5:6:7:8:9:10:11:12)
date(1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20:21:22
:23:24:25:26:27:28:29:30:31) week(1:2:3:4:5:6:7)
starttime(03:32:00) last(12)
Note: Ranging from 1970-01-01 00:00:00 to 2037-12-31
23:59:59.
Format of last is HH:MM or HH.
Unit of HH is hour and range is from 0 to 24.
Unit of MM is minute and range is from 0 to 59.
When HH is 24, MM must be 0.
BearerRequestedQCI [1, 255]
2 Operation List
3 Object List
Condition Group Name cannot be the same as an existing condition group name.
A maximum of 3,072 condition groups and 3,072 conditions can be configured in the system. Each
condition group can be configured with a maximum of 16 conditions.
CONDITIONGROUP:
{CONDITIONGROUPNAME } = <Condition Group Name>,
{DESCRIPTION} = <Description>,
{RELATION} = <Relation>;
Example:
ADD CONDITIONGROUP: CONDITIONGROUPNAME = "abcd", DESCRIPTION =
"abcd Condition Group." ,RELATION=AND;
4.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12440: The condition group already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Condition Group Name must be the same as an existing condition group name.
4.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12441: The condition group does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
4.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12441: The condition group does not exist
12448: The condition group is associated with a rule
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94511:The condition group is associated with a subscriber group
Condition Group Name must be the same as an existing condition group name. Condition Name
cannot be the same as an existing condition name.
A maximum of 3,072 condition groups and 3,072 conditions can be configured in the system.
Each condition group can be configured with a maximum of 16 conditions.
[ADD]
CONDITION:
{CONDITIONGROUPNAME} = <Condition Group Name>,
{CONDITIONNAME} = <Condition Name>,
{OBJECTATTRIBUTE} = <Object Attribute >,
{OBJECTINSTANCE} = <Object Instance>,
{OPERATOR} = <Operator>,
{RIGHTVALUETYPE} = <Right Value Type>,
{RIGHTOBJECTATTRIBUTE} = <Right Object Attribute>,
{DESCRIPTION} = < Description>;
Example:
ADD CONDITION: CONDITIONGROUPNAME = "abcd", CONDITIONNAME =
"condition", OBJECTATTRIBUTE = "Quota.QuotaStatus", OBJECTINSTANCE = "quota",
OPERATOR = Equal, RIGHTVALUETYPE = Value, RIGHTVALUE = "Level1",
DESCRIPTION = "abcd quota condition.";
ADD CONDITION: CONDITIONGROUPNAME = "abcd", CONDITIONNAME =
"condition1", OBJECTATTRIBUTE = "Subscriber.MSISDN", OPERATOR = Equal,
RIGHTVALUETYPE = Attribute, RIGHTOBJECTATTRIBUTE= "IPSession.MSISDN";
4.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12431: The object attribute dictionary does not exist
12441: The condition group does not exist
12486: The number of conditions in the condition group exceeds the maximum value
(16)
12503: The number of conditions exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94226: The condition already exists
94228: The object instance does not exist
94271: Operator not logged in
94333: The source PCEF does not exist
94519:The condition group is associated with a subscriber group and the element
conflict.
12457: The objectattribute dos not exist
Condition Group Name must be the same as an existing condition group name.
Object Attribute and Object Instance must exist in the system.
If Object Attribute is specified, Operator and Right Value Type must be specified, and Right
Value and Right Object Attribute are specified according to the value of Right Value Type.
{DESCRIPTION} = <Description>;
Or:
[MOD]
CONDITION:
{CONDITIONGROUPNAME} = <Condition Group Name>,
{CONDITIONNAME} = <Condition Name>,
{OBJECTATTRIBUTE} = <Object Attribute>,
{OBJECTINSTANCE} = <Object Instance>,
{OPERATOR} = <Operator>,
{RIGHTVALUETYPE} = <Right Value Type>,
{RIGHTOBJECTATTRIBUTE} = <Right Object Attribute>,
{DESCRIPTION} = <Description>;
Example:
MOD CONDITION: CONDITIONGROUPNAME = "abcd", CONDITIONNAME =
"condition", OBJECTATTRIBUTE = "Quota.QuotaStatus", OBJECTINSTANCE = "quota",
OPERATOR = Equal, RIGHTVALUETYPE = Value, RIGHTVALUE = "Level2",
DESCRIPTION = "abcd quota condition.";
MOD CONDITION: CONDITIONGROUPNAME = "abcd", CONDITIONNAME =
"condition1", OBJECTATTRIBUTE = "Subscriber.MSISDN", OPERATOR = Equal,
RIGHTVALUETYPE = Value, RIGHTVALUE = "123456789123456", DESCRIPTION =
"abcd quota condition.";
4.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12441: The condition group does not exist
12442: The condition does not exist
94209: Processing timeout
94210: PAU system processing failed
94228: The object instance does not exist
94271: Operator not logged in
94333: The source PCEF does not exist
94519:The condition group is associated with a subscriber group and the element conflict
Condition Group Name must be the same as an existing condition group name.
4.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
Action Group Name cannot be the same as an existing action group name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
Example:
ADD ACTIONGROUP: ACTIONGROUPNAME = "abcd", DESCRIPTION = "abcd Action
Group.";
5.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12451: The action group already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name. Action Group Name cannot be
modified but Description can be modified.
5.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12453: The action group cannot be deleted because it is associated with a rule
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an existing
action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each action
group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be both specified, for example, QCI Type and QCI
Value.
The default description of QoSAction is "To set the QoS policy as a default action and can not be
deleted or configured.".
If Value Type is set to Value, the value range of the parameters is as follows:
Preemption Vulnerability Value can be set to Enabled or Disabled.
Preemption Capability Value can be set to Enabled or Disabled.
The value of ARP Level Value ranges from 1 to 15.
The value of GBRUL Value ranges from 0 to 4294967 (unit: kbit/s).
The value of GBRDL Value ranges from 0 to 4294967 (unit: kbit/s).
The value of MBRUL Value ranges from 0 to 4294967 (unit: kbit/s).
The value of MBRDL Value ranges from 0 to 4294967 (unit: kbit/s).
The value of QCI Value ranges from 1 to 255.
If MBRUL Value and GBRUL Value are both specified, the value of MBRUL Value must be
greater than that of GBRUL Value. If MBRDL Value and GBRDL Value are both specified, the
value of MBRDL Value must be greater than that of GBRDL Value.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
If an optional parameter is not specified in the command, this parameter must be set to a default
value. The default value of Preemption Vulnerability Value is Enabled. The default value of
Preemption Capability Value is Disabled. The default value of GBRUL Value or GBRDL Value
is blank.
5.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94257: The QCI value must between 1-255
94258: The value range is 0 to 4294967 for MBRUL, MBRDL, GBRUL, GBRDL,
AMBRUL, and AMBRDL
94259: GBRUL should not bigger than MBRUL and GBRDL should not bigger than
MBRDL
94260: The ARPLevel value must between 1-15
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an existing
action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each action
group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The value type and the value must be both specified.
The default description of GateAction is "To set the gating policy as a default action and can not be
deleted or configured.".
If Value Type is set to Value, the value range of Flow Status Value is as follows: Enable Uplink,
Enable Downlink, Enabled, or Disabled.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
5.8.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist.
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.9.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The value type and the value must be both specified.
The default description of ChargingAction is "To set the charging action as a default action and
can not be deleted or configured.".
If Value Type is set to Value, the value range of the parameters is as follows:
Offline Value can be set to DisableOffline, EnableOffline, or Null.
Online Value can be set to DisableOnline, EnableOnline, or Null.
Metering Method Value can be set to Duration, Volume, DurationVolume, or Nocharging.
Reporting Level Value can be set to Service Identifier Level or Rating Group Level.
Charging Correlation Indicator Value can be set to Charging Identifier Required or Null.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
If an optional parameter is not specified in the command, this parameter must be set to a default
value. Metering Method Value can be set to Duration. Reporting Level Value can be set to
Service Identifier Level. The default value of Offline Value, Online Value, or Charging
Correlation Indicator Value is blank.
CHARGINGACTION:
{ACTIONGROUPNAME} = <Action Group Name>,
{RATINGGROUPTYPE} = <Rating Group Type>,
{RATINGGROUPVALUE} = <Rating Group Value>,
{SERVICEIDENTIFIERTYPE} = <Service Identifier Type>,
{SERVICEIDENTIFIERVALUE} = <Service Identifier Value>;
Example:
ADD CHARGINGACTION: ACTIONGROUPNAME = "abc", RATINGGROUPTYPE =
Value, RATINGGROUPVALUE = "10", SERVICEIDENTIFIERTYPE = Value,
SERVICEIDENTIFIERVALUE = "1";
5.10.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.11.4 Result
A code is returned, indicating the operation result.
Action Group Name must be the same as an existing action group name.
5.12.4 Result
A code is returned, indicating the operation result.
The action group and actions have been configured. Action Name cannot be the same as an
existing action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The value type and the value must be both specified.
The default description of Redirection is"To set the redirection-related parameters as a default
action and can not be deleted or configured."
If Value Type is set to Value, the value range of the parameters is as follows:
Redirect Address Type Value can be set to IPv4 Address, IPv6 Address, URL, or SIP URIS.
The value of Redirect Server Address Value is in dotted decimal format.
Oneshot Redirection Value can be set to Enable, Disable, or Null.
Redirect Times Value can be 1 to 255.
Redirect Report Value can be Null, Enable or Disable.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
If an optional parameter is not specified in the command, this parameter must be set to a default
value. The default value of Redirect Address Type Value is IPv4 Address.
5.13.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.14.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.15.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an existing
action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each action
group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The default description of AFChargingIdentifier is "To set the charging identifier of the application
layer as a default action and can not be deleted or configured."
5.16.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.17.4 Result
A code is returned, indicating the operation result.
Action Group Name must be the same as an existing action group name.
5.18.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The value type and the value must be both specified.
The default description of AFMediaFlowsNumber is "To set the media flow identifier of the
application layer as a default action and can not be deleted or configured."
If Value Type is set to Value, the value range of the parameters is as follows:
The value of Media Component Number Value ranges from 0 to 4294967295.
The value of Flow Number Value ranges from 0 to 4294967295.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.19.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.20.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.21.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an existing
action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each action
group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The default description of UsageReport is "To set the monitor key as a default action and can not be
deleted or configured."
5.22.4 Result
A code is returned, indicating the operation result.
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.23.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.24.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an existing
action name in the action group. One action group can be configured with a maximum of 10
IndicateServiceName actions.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each action
group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The default description of IndicateServiceName is "To set the service name as a default action and
can not be deleted or configured."
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.25.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
If the number of IndicateServiceName Action in the action group is more than one, it cannot be
modified, and will return error "94552: More than one IndicateServiceName Action exist".
5.26.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94552: More than one IndicateServiceName Action exist
Action Group Name must be the same as an existing action group name.
5.27.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an existing
action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each action
group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
If Activation Time Type or Deactivation Time Type is set to Value, the value is in
YYYY&MM&DD&HH&MM&SS format. For example, if a rule is activated at 01:01:01 on 2011-
06-24, the value is in "2011&06&04&01&01&01" format.
The default description of RuleTimeRange is "To set the Activation-Time and the Deactivation-Time
for the Rule as a default action and cannot be deleted or configured.".
The activation time must be earlier than the deactivation time.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.28.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
If Activation Time Type or Deactivation Time Type is set to Value, the value is in
YYYY&MM&DD&HH&MM&SS format. For example, if a rule is activated at 01:01:01 on 2011-
06-24, the value is in "2011&06&04&01&01&01" format.
5.29.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94262: The DeactivationTime cannot be earlier than (or equal to) the ActivationTime
94271: Operator not logged in
Action Group Name must be the sane as an existing action group name.
5.30.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The value type and the value must be both specified.
The default description of DefaultBearerQoS is "To set the QoS for EPS default Bearer and APN-
AMBR as a default action and cannot be deleted or configured.".
If Value Type is set to Value, the value range of the parameters is as follows:
The value of ARP Level Value ranges from 1 to 15.
Preemption Capability Value can be set to Enabled or Disabled.
Preemption Vulnerability Value can be set to Enabled or Disabled.
The value of AMBRDL Value ranges from 0 to 4294967 (unit: kbit/s).
The value of AMBRUL Value ranges from 0 to 4294967 (unit: kbit/s).
The value of QCI Value ranges from 1 to 255.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
DEFAULTBEARERQOS:
{ACTIONGROUPNAME} = <Action Group Name>,
{QCITYPE} = < QCI Type>,
{QCIVALUE} = < QCI Value>,
{ARPLEVELTYPE} = <ARP Level Type>,
{ARPLEVELVALUE} = <ARP Level Value>,
{PREEMPTIONCAPABILITYTYPE} = <Preemption Capability Type>,
{PREEMPTIONCAPABILITYVALUE} = <Preemption Capability Value>,
{PREEMPTIONVULNERABILITYTYPE} = <Preemption Vulnerability Type>,
{PREEMPTIONVULNERABILITYVALUE} = <Preemption Vulnerability Value>,
{AMBRDLTYPE} = <AMBRDL Type>,
{AMBRDLVALUE} = <AMBRDL Value>,
{AMBRULTYPE} = <AMBRUL Type>,
{AMBRULVALUE} = <AMBRUL Value>;
Example:
ADD DEFAULTBEARERQOS: ACTIONGROUPNAME = "abcd", QCITYPE = Value,
QCIVALUE = "5", ARPLEVELTYPE = Value, ARPLEVELVALUE = "1",
PREEMPTIONCAPABILITYTYPE = Value, PREEMPTIONCAPABILITYVALUE =
"Disabled", PREEMPTIONVULNERABILITYTYPE = Value,
PREEMPTIONVULNERABILITYVALUE = "Enabled", AMBRDLTYPE = Value,
AMBRDLVALUE = "200", AMBRULTYPE = Value, AMBRULVALUE = "100";
5.31.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.32.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94258: The value range is 0 to 4294967 for MBRUL, MBRDL, GBRUL, GBRDL,
AMBRUL, and AMBRDL
94260: The ARPLevel value must between [1-15]
94261: The QCI value must between 1-255
94271: Operator not logged in
Action Group Name must be the sane as an existing action group name.
5.33.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be both specified.
The default description of CmdChargingAction is "To set the CmdChargingAction as a default
action and cannot be deleted or configured.".
If Value Type is set to Value, the value range of the parameters is as follows:
Offline Value can be set to DisableOffline, EnableOffline, or Null.
Online Value can be set to DisableOnline, EnableOnline, or Null.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
If an optional parameter is not specified in the command, this parameter must be set to a default
value. The default value of Offline Value or Online Value is blank.
5.34.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
The value type and the value must be both specified.
5.35.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
5.36.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be both specified.
The default description of FBBAction is "To set the FBB policy as a default action and cannot be
deleted or configured."
If Value Type is set to Value, the value range of the parameters is as follows:
FBB Service Type value can be set to BOD, DPI, or DAA.
The value of Interim Interval Value ranges from 0 to 3292100.
The value of MSGRP Name Value ranges from 1 to 31.
The value of ACLGRP Name Value ranges from 1 to 31.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.37.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94325: FBB Service type must be DPI, BOD, or DAA
94326: The INTERIMINTERVALVALUE value must between 0-3932100
94327: FBB group name length is invalid
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
If Value Type is set to Value, the value range of the parameters is as follows:
FBB Service Type value can be set to BOD, DPI, or DAA.
The value of Interim Interval Value ranges from 0 to 3292100.
The value of MSGRP Name Value ranges from 1 to 31.
The value of ACLGRP Name Value ranges from 1 to 31.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.38.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
5.39.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be both specified.
The default description of URLFiltering action is "To set the URLFiltering as a default action and
cannot be deleted or configured.".
If the value of URLFILTERINGSWITCH parameters is Enabled, the URLFILTERINGNAME
cannot be configured.
If Value Type is set to Value, the value range of the parameters is as follows:
URL Filtering Switch can be set to Null or Enabled.
URL Filtering Name can be set to a string of up to 31 characters.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.40.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
The action group and actions have been configured. Action Name must be the same as an existing
action name in the action group.
If the value of URLFILTERINGSWITCH parameters is Enabled, the URLFILTERINGNAME
cannot be configured.
If Value Type is set to Value, the value range of the parameters is as follows:
URL Filtering Switch can be set to Null or Enabled.
URL Filtering Name can be set to a string of up to 31 characters.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.41.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94551: The URLFilteringSwitch and URLFilteringName configuration conflicts
5.42.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be specified in pairs.
The default description of SCE is: "To set the predefined parameter for the Cisco SCE peer.".
If Value Type is set to Value, the value of Cisco SCA BB Package Install Value ranges from 0 to
4294967295.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.43.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs.
5.44.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
Action Group Name must be the same as an existing action group name.
5.45.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be specified in pairs.
The default description of SCEPsInformation is: "To set the PS parameter for the Cisco SCE peer
in multi-PCEF scenario.".
If Value Type is set to Value, the value range of the parameters is as follows:
The value of Called Station ID Value must be a string of 1 to 64 characters.
RAT Type Value can be set to UTRAN, GERAN, WLAN, GAN, HSPAEvolution, EUTRAN,
CDMA2000_1X, or HRPD.
The value of User Location Info Value must be a string of 1 to 32 characters.
The value of SGSN Address Value must be an IPv4 address in dotted decimal notation as follows:
SGSNADDRESSTYPE=Object Attribute,
SGSNADDRESSVALUE="IPSession.SGSNAddress";
5.46.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs.
5.47.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.48.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be specified in pairs.
The default description of SERVICEFLOWDETECTION is: " To set the service flow detection
policy as a default action and cannot be deleted or configured.".
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
enabled for the PCEF that supports the SFD redirection service. The value of Service flow
detection Value only can be set to Enable.
5.49.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs.
The SERVICEFLOWDETECTION specifies whether the service flow detection function is enabled
for the PCEF that supports the SFD redirection service. The value of Service flow detection Value
only can be set to Enable.
5.50.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.51.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be specified in pairs.
The default description of CMDSUBPROFILEACTION is: " To set the CmdSubProfileAction
as a default action and cannot be deleted or configured. ".
If Value Type is set to Value,the maximum length of the value must less or equal to 15 bytes.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.52.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs..
5.53.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.54.4 Result
A code is returned, indicating the operation result.
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be specified in pairs.
The default description of TDFAPPLICATIONIDENTIFIER is: " To set the
TDFApplicationIdentifier as a default action and cannot be deleted or configured. ".
If Value Type is set to Value,the maximum length of the value must less or equal to 64 bytes.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.55.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs..
Example:
MOD TDFAPPLICATIONIDENTIFIER: ACTIONGROUPNAME = "abc",
APPIDENTIFIERTYPE = Value, APPIDENTIFIERVALUE = "facebk";
5.56.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.57.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The element type and element value must be specified in pairs.
The default description of MuteNotification is: " To set the MuteNotification as a default action
and cannot be deleted or configured. ".
If Value Type is set to Value, the value range of Mute Notification Value is as follows:
MUTE_REQUIRED.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.58.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12454: The action already exists
12487: The number of actions in the action group exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs..
5.59.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.60.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The action group and actions have been configured. Action Name cannot be the same as an
existing action name in the action group.
A maximum of 1,024 action groups and 3,072 actions can be configured in the system. Each
action group can be configured with a maximum of 64 actions.
Different action groups can be configured with the same actions.
The value type and the value must be both specified.
The default description of Redirection is"To set the redirection-related parameters as a default
action and can not be deleted or configured."
If Value Type is set to Value, the value range of the parameters is as follows:
Redirect support Value can be set to REDIRECTION_ENABLED or
REDIRECTION_DISABLED.
Redirect Address Type Value can be set to IPv4 Address, IPv6 Address, URL, or SIP URIS.
The value of Redirect Server Address Value is in dotted decimal format.
If Value Type is set to Object Attribute, the data type of the value must be the same as that of the
action element.
5.61.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
The action group and actions have been configured. Action Name must be the same as an existing
action name.
The element type and element value must be specified in pairs..
Example :
MOD REDIRECTINFORMATION: ACTIONGROUPNAME = "11",
REDIRECTSUPPORTTYPE = value, REDIRECTSUPPORTVALUE =
"REDIRECTION_ENABLED", REDIRECTADDRESSTYPETYPE = value,
REDIRECTADDRESSTYPEVALUE = "IPv4 Address",
REDIRECTSERVERADDRESSTYPE = value, REDIRECTSERVERADDRESSVALUE =
"10.85.169.12";
5.62.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Action Group Name must be the same as an existing action group name.
5.63.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
5.64.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12312: Incorrect action attribute
12431: The object attribute dictionary does not exist
5.65.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12434: The action element dictionary does not exist
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94232: The right value invalid
Action Group Name must be the same as an existing action group name.
5.66.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Service Flow Name cannot be the same as an existing service flow name.
A maximum of 1,024 service flows and 1,024 flow filters can be configured in the system.
Each service flow can be configured with a maximum of two filters in different directions. Different
service flows can be configured with the same flow filters.
6.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12443: The service flow already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Service Flow Name must be the same as an existing service flow name.
Only the description of a service flow can be modified.
SERVICEFLOW:
{SERVICEFLOWNAME} = <Service Flow Name>,
{DESCRIPTION} = <Description>;
Example:
MOD SERVICEFLOW: SERVICEFLOWNAME = "abcd", DESCRIPTION = "abcd Service
Flow";
6.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12444: The service flow does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Service Flow Name must be the same as an existing service flow name.
SERVICEFLOW:
{SERVICEFLOWNAME} = <Service Flow Name>;
Example:
RMV SERVICEFLOW: SERVICEFLOWNAME = "abcd";
6.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12444: The service flow does not exist
12447: The service flow cannot be deleted because it is associated with a rule
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Service Flow Name must be the same as an existing service flow name. The flow filter name cannot
be duplicated in a service flow.
A maximum of 1,024 service flows and 1,024 flow filters can be configured in the system.
Each service flow can be configured with a maximum of two filters in different directions. Different
service flows can be configured with the same flow filters.
The values of Max Destination Port 1, Max Destination Port 2, Max Source Port 1, and Max
Source Port 2 must be greater than or equal to the values of Min Destination Port 1, Min
Destination Port 2, Min Source Port 1, and Min Source Port 2, respectively.
Min Destination Port 1, Max Destination Port 1, Min Destination Port 2, and Max Destination
Port 2 can be configured to specify two port segments. For example, if Min Destination Port 1 is 1,
Max Destination Port 1 is 80, Min Destination Port 2 is 100, and Max Destination Port 2 is 120,
ports ranging from 1 to 80 and ports ranging from 100 to 120 are configured. This rule applies to
configuration of source ports and destination ports.
6.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12444: The service flow does not exist
12481: Invalid IP address. The value must be an IPv4 address in D.D.D.D format, an
IPv6 address in X:X:X:X:X:X:X:X format, or an IPv6 address embedded with an IPv4
address, that is, in X:X:X:X:X:X:D.D.D.D format. D is an 8-bit decimal number, X is a
16-bit hexadecimal number. If two or more consecutive Xs are 0, the 0s can be replaced
by ::. For example, X:X:X:0:0:0:X:X can be replaced by X:X:X::X:X. Only one :: is
allowed
12620: Invalid subnet mask. If the IP address is in IPv4 format, the subnet mask must be
in D.D.D.D format (where D is an 8-bit decimal number) or a decimal number ranging
from 0 to 32. If the IP address is in IPv6 format, the subnet mask must be in
Service Flow Name and Flow Filter Name must be defined in the system.
The value of Filter Direction cannot be modified.
6.5.4 Result
A code is returned, indicating the operation result.
Service Flow Name and Flow Filter Name must be defined in the system.
6.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12444: The service flow does not exist
12446: The flow filter does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
7 Notification Management
7.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
7.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12431: The object attribute dictionary does not exist
12436: The object dictionary does not exist
90108: The Notification does not exist
90121: Please choose one between SMS and EMAIL
90177: The associated short message template does not exist
90178: The associated email template does not exist
90179: The associated short message and email templates do not exist
94209: Processing timeout
94210: PAU system processing failed
94228: The object instance does not exist
94271: Operator not logged in
90193: The notification has been associated with an quota item and the type of interval
cannot be updated to account cycle
90194: The notification has been associated with an account item and the type of interval
cannot be updated to quota cycle
98334: The related template for SOAP notification does not exist
7.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90108: The Notification does not exist
90109: The Notification is associated with a Rule
90160: The Notification is associated with an Account
90161: The Notification is associated with a Quota
90162: The Notification is associated with a Service
90167: The notification is associated with a service package and cannot be deleted
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
8 Rating Management
8.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
90110: The Rating already exists
94209: Processing timeout
94210: PAU system processing failed
{PRICE} = <Price>,
{VOLUME} = <Volume>,
{EXCHANGERATE}=<Exchange Rate>,
{DESCRIPTION} = <Description>;
Example:
MOD RATING: RATINGNAME= "abcd", MONITORKEY= 1, PRICE = "0.5", VOLUME =
100, EXCHANGERATE = "100", DESCRIPTION= "abcd rating.";
8.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90111: The Rating does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
RATING:
{RATINGNAME } = <Rating Name>;
Example:
RMV RATING: RATINGNAME = "abcd";
8.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90111: The Rating does not exist
90112: The Rating is associated with a Rule
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
9 Rule Management
{TRIGGER}=<Trigger>,
{NOTIFICATIONRECEIVER}=<Notification Receiver>;
Example:
ADD RULE:RULENAME="25611_0104_R02",OPERATION=Change
Rule,TYPE=Predefined,CONDITIONGROUPNAME="25611_0104_CG02",ACTIONGROU
PNAME="25611_0104_AG01",PREDEFINEDNAME="BBBB",VOLUMEUSAGEROUND
ING=No,EDR=OFF,RELATION=AND,DELAYTIME=300,
PREDEFINEDNAMEDURINGDELAY="BBBBDELAY";
9.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control started
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12304: The service does not exist
12441: The condition group does not exist
12444: The service flow does not exist
12452: The action group does not exist
90108: The Notification does not exist
90111: The Rating does not exist
94209: Processing timeout
94210: PAU system processing failed
94222: The destination PCEF does not exist
94267: The value of Rounding Threshold cannot exceed 1024*(value of Rounding Unit)-
1
94271: Operator not logged in
94573: The parameters DELAYTIME and ACTIVATIONTCYCLE configuration
conflicts
Example:
MOD RULE:RULENAME="25611_0104_R02",OPERATION=Change
Rule,TYPE=Predefined,CONDITIONGROUPNAME="25611_0104_CG02",ACTIONGROU
PNAME="25611_0104_AG01",PREDEFINEDNAME="BBBB",VOLUMEUSAGEROUND
ING=No,EDR=OFF,RELATION=AND,DELAYTIME=30,
PREDEFINEDNAMEDURINGDELAY="CCCCDELAY";
9.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
12444: The service flow does not exist
12450: The rule does not exist
12452: The action group does not exist
90108: The Notification does not exist
90111: The Rating does not exist
94209: Processing timeout
94210: PAU system processing failed
94222: The destination PCEF dos not exist
94267: The value of Rounding Threshold cannot exceed 1024*(value of Rounding Unit)-
1
94271: Operator not logged in
94573: The parameters DELAYTIME and ACTIVATIONTCYCLE configuration
conflicts
9.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12449: The rule is associated with a policy
12450: The rule does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
9.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
9.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12441:The condition group does not exist
12450:The rule does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94520: The condition group does not exist in the rule
10 Policy Management
10.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12427: The policy already exists
12429: The trigger does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
10.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12426: The Policy does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
10.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12426: The Policy does not exist
12456: The policy is associated with a service
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
10.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12426: The Policy does not exist
12429: The trigger does not exist
90153: The trigger type does not match the rule type
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94506: The trigger already exists
94507: The number of triggers exceeds the maximum value (10)
10.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12426: The Policy does not exist
12429: The trigger does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94521:The trigger does not exist in the policy
10.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12426: The Policy does not exist.
12450: The rule does not exist.
12488: The number of rules in the policy exceeds the maximum value (64).
90153: The trigger type does not match the rule type
94209: Processing timeout
94210: PAU system processing failed
94225: The rule has been associated with the policy.
94271: Operator not logged in
Policy Name and Rule Name must be defined in the system, and rules must have been added to the
policy.
10.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
11.1.4 Result
A code is displayed, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Example:
MOD SP: SPNAME = "abcd", DESCRIPTION = "abcd";
11.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8217: This item cannot be configured
12308: The SP does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
11.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8199: This item cannot be deleted
8201: Invalid parameter
12308: The SP does not exist
12309: The SP cannot be deleted because it is associated with a service
12381: The SP is associated with a subscriber
12400: The SP cannot be deleted because it is associated with a service package
12401: The SP cannot be deleted because it is associated with a mutex group
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
12 Quota Management
42. QUOTA Quota Slice This parameter specifies the Enumerated Percent C
SLICET Type Quota Slice Type. Value
YPE
Default value:
Percent
43. QUOTA Quota Slice This parameter specifies the Number 1-2147483645 C
SLICEV Value Quota Slice Value.
ALUE
44. CUMUL Cumulative This parameter specifies the Number 1-100 C
ATIVEP Percent percentage based on which the
ERCEN remaining quota is
T accumulated to the reset quota
when
BALANCERESETMETHO
D is set to Cumulate.
12.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
12423: Quota Service Identifier and Monitor Key already exist
53199: The number of records exceeds the maximum value
90108: The Notification does not exist
90180: The interval cycle does not match the notification
94209: Processing timeout
94210: PAU system processing failed
94222: The destination PCEF dos not exist
94268: Threshold values cannot be duplicated
94271: Operator not logged in
94582: The value of MONITORKEY can't set to a specific value.
Quota Class and Accumulation Type and Reset Time Type cannot be modified.
If the manager of the quota is Sy, Only DEFAULTSTATUS and DESCRIPTION parameters can be
modified. If the manager of the quota is not Sy, DEFAULTSTATUS parameters cannot be modified.
If the VRM_CLIMODIFYCTRL software parameter value is 0, Type and Monitor Key cannot be
modified.
If QUOTASLICETYPE is set to Percent, QUOTASLICE must be configured; if
QUOTASLICETYPE is set to Value, QUOTASLICEVALUE must be configured.
Parameter MONITORKEY and MKSTRING cannot exist at the same time.
{LEVEL10} = <Level10>,
{CUSTOMLEVEL1} = <CustomLevel1>,
{CUSTOMLEVEL2} = <Customlevel2>,
{CUSTOMLEVEL3} = <Customlevel3>,
{SERVICEIDENTIFIER} = <Service Identifier>,
{ TYPE }=<Type>,
{ MONITORKEY }=<Monitor key>,
{CYCLEUNIT} = <Cycle Unit>,
{ HOURS} = <Hours>,
{STARTMINUTE} = <Start Minue>,
{QUOTASLICETYPE} = <Quota Slice Type>,
{QUOTASLICEVALUE} = <Quota Slice Value>,
{CUMULATIVEPERCENT} = <Cumulative Percent>,
{MAXCUMULATION} = <Max Cumulation Value>,
{USERSTATUSAUTORESET} = < User Status Automatic Reset >,
{BILLINGCYCLEMODE} = <Billing Cycle Mode>,
{CUSTOMERSTRATTR} = <Customer Attribute> ;
Example:
MOD QUOTA: QUOTANAME="abcd", QUOTAVALUE=1000, QUOTASLICE=10,
NOTIFICATION="abcd", EDR= NotRecord, DESCRIPTION="Quota1", RESETTYPE=Day,
RESETTIME=01&00&00, BALANCERESETMETHOD=Reset, LEVEL1=10, LEVEL2=20,
LEVEL3=30, LEVEL4=40, LEVEL5=50, LEVEL6=60, LEVEL7=70, LEVEL8=80,
LEVEL9=90;
12.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12303: The quota does not exist
12344: The attribute cannot be configured dynamically
12423: Quota Service Identifier and Monitor Key already exist
90108: The notification does not exist
90180: The interval cycle does not match the notification
12.3.4 Result
A code is displayed, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12303: The quota does not exist
12424: The quota is associated with a service
90117: The Quota is associated with a Subscriber
90131: The quota has been associated with an accumulation item and cannot be deleted
90166: The quota has been associated with a condition group and cannot be deleted
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94608: The quota has been referenced by notification template and cannot be deleted
13 Account Management
{LEVEL6} = <Level6>,
{LEVEL7} = <Level7>,
{LEVEL8} = <Level8>,
{LEVEL9} = <Level9>,
{LEVEL10} = <Level10>,
{CUSTOMLEVEL1} = <CustomLevel1>,
{CUSTOMLEVEL2} = <Customlevel2>,
{CUSTOMLEVEL3} = <Customlevel3>;
Example:
ADD ACCOUNT: ACCOUNTNAME = "abcd", ACCOUNTVALUE = "1000.0",
ACCOUNTSLICE = 10, DESTINATIONPCEF = 1, NOTIFICATION = "abcd",
DESCRIPTION = "abcd", BILLINGCYCLEMODE = CALENDAR, RESETTYPE =
MONTH, RESETDATE = 15, RESETTIME = 01&00&00, BALANCERESETMETHOD =
Reset, LEVEL1 = 10,EDR = ON;
13.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
94223: Account value invalid
90108: The Notification does not exist
90181: The interval cycle does not match the notification
94209: Processing timeout
94210: PAU system processing failed
94268: Threshold values cannot be duplicated
94271: Operator not logged in
{LEVEL8} = <Level8>,
{LEVEL9} = <Level9>,
{LEVEL10} = <Level10>,
{CUSTOMLEVEL1} =<CustomLevel1>,
{CUSTOMLEVEL2} = <Customlevel2>,
{CUSTOMLEVEL3} = <Customlevel3>;
Example:
MOD ACCOUNT: ACCOUNTNAME = "abcd", ACCOUNTVALUE = "1000.0",
ACCOUNTSLICE = 10, DESTINATIONPCEF = 1, NOTIFICATION = "abcd",
DESCRIPTION = "abcd", RESETTYPE = MONTH, RESETDATE = 15, RESETTIME =
01&00&00, BALANCERESETMETHOD = Reset, LEVEL1 = 10,EDR = ON;
13.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12600: The account does not exist
90108: The notification does not exist
90181: The interval cycle does not match the notification
94209: Processing timeout
94210: PAU system processing failed
94239: The parameter BILLINGCYCLEMODE cannot be modified
94242: If parameter BILLINGCYCLEMODE is set to DailyService, NotReset or
Provisioning Assign, the parameter BALANCERESETMETHOD cannot be modified.
94243: If the parameter BILLINGCYCLEMODE is not set to Subscriber Billing Cycle
or Monthly Service, the value of BILLINGCYCLETIME cannot be modified
94244: If the parameter BILLINGCYCLEMODE is not set to Calendar, the parameters
RESETTYPE, RESETDAY, RESETDATE, and RESETTIME cannot be modified
94245: If the parameter RESETTYPE is set to Day, the parameter RESETDAY,
RESETDATE cannot be modified
94246: If the parameter RESETTYPE is set to Week, the parameter RESETDATE cannot
be modified
94247: If the RESETTYPE is set to Week from other resettype, the parameter
RESETDAY must be specified
94248: If the parameter RESETTYPE is set to Month, and the parameter RESETDAY
cannot be modified
94249: If the RESETTYPE is set to Month from other resettype, the parameter
RESETDATE must be specified
94250: Threshold value must be increased by degree
94268: Threshold values cannot be duplicated
94271: Operator not logged in
13.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12600: The account does not exist
90114: The account is associated with Service
90116: The account is associated with a Subscriber
94209: Processing timeout
94210: PAU system processing failed
14 Accumulation Management
14.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90124: The accumulation item already exists
90126: The number of accumulation items reaches the maximum value (255)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Accumulate Class, Accumulate Type, Billing Cycle Mode, Reset Time Type and Slide Type cannot
be modified.
{DEVIATION} = <Deviation>,
{CONTROLINTERVAL}=<Control Interval>;
Example:
MOD ACCUMULATION: ACCUMULATENAME="Accum_1", RESETTIME=07&00&00,
WINDOWLENGTH=6, STEPLENGTH=3, CHECKTYPE=Total Usage,
HEAVYTOTALVALUE=10000, LIGHTTOTALVALUE=10000;
14.2.4 Result
A code is returned, indicating the operation result. If the operation is successful, the following
code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90125: The accumulation item does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
14.3.4 Result
A code is returned, indicating the operation result. If the operation is successful, the following
code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90125: The accumulation item does not exist
90128: The accumulation item has been provided to a subscriber and cannot be deleted
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
14.4.4 Result
A code is returned, indicating the operation result. If the operation is successful, the following
code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12303: The quota does not exist
90125: The accumulation item does not exist
90127: The number of quotas associated with the accumulation item reaches the
maximum value (6)
90130: The accumulation item type does not match the quota type
90132: The accumulation item cannot be associated with multiple quotas with the same
monitor key
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94272: The quota is already associated with the accumulation item
98309: The quota managed by an external entity cannot be associated with the
accumulation item
14.5.4 Result
A code is returned, indicating the operation result. If the operation is successful, the following
code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12303: The quota does not exist
90125: The accumulation item does not exist
90128: The accumulation item has been provided to a subscriber and cannot be deleted
90135: The accumulation item has been associated with a condition group and cannot be
deleted
15 Service Management
26. DURATIONT Duratio This parameter specifies how the Enume Hour C
YPE n Type duration is calculated. rated Day
27. DURATIONV Duratio This parameter specifies the service Numbe 1-8784 C
ALUE n duration. r
28. DESCRIPTIO Descrip This parameter provides additional String 1-256 O
N tion information about the service.
29. PROBILLDA Provide This Parameter specifies the service Enume Yes C
TE d till expiry on the next bill date. rated No
Bill
Date
30. ENDTIME End This Parameter specifies the service DateTi 8 C
Time expiry time. me
31. QUOTAALL Quota This Parameter specifies the quota Enume None O
OCATIONMO Allocati allocation mode when the service has rated Days Proration
DE on been subscribed to.
Mode
32. CUSTOMERA Custom This Parameter specifies the service Numbe 0-2147483645 O
TTRIBUTE er customer attribute r
Attribut
e
33. ISSETSHARE Is Set This Parameter specifies whether set Enume Yes C
DMODE Shared shared mode of the service. rated No
Mode
34. SHAREDMO Shared This Parameter specifies the shared Enume Shared C
DE Mode mode of the service. rated NotShared
35. ISGROUPSER Is This Parameter specifies the group Enume Yes O
VICE Group attribute of the service. rated No
Service
36. NOTIFYCOD Notify This Parameter specifies the notify String 120 O
E code sender code of the notification of this
service.
37. QRYNOTIFIC SMS II. This parameter specifies the String 132 O
ATION Query notification when its triggered by the
Notifica SMS query message.
tion
15.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12308: The SP does not exist
12600: The Account does not exist
12628: Invalid datetime
11. ABSVA Absolute This parameter specifies the time when a String 19 O
LIDSTA valid start subscriber starts to use a service.
RTTIME time
12. ABSVA Absolute This parameter specifies the time when a String 19 O
LIDEN valid end subscriber stops using a service.
DTIME time
13. DISPLA Display This parameter specifies the name of a String 1-32 C
YNAME Name service. The parameter takes precedence
over Service Name if Service Type is
set to MULTI_SERVICE_APN.
14. DEFAU Default This parameter specifies whether to Enumerated No O
LTACTI Activate activate a service by default upon Yes
VATE subscription. The parameter is valid if
Service Type is set to
MULTI_SERVICE_APN.
15. PATUN Portal This parameter specifies whether to Enumerated Yes C
ABLE Tunable allow subscribers to activate or No
deactivate the services on the Portal (PA
represents Portal). The parameter is valid
if Service Type is set to
MULTI_SERVICE_APN or
BOD_SERVICE.
16. SERVIC Service This parameter specifies the URL String 1-128 C
EURL URL associated with a service. The parameter
is valid if Portal Tunable is set to Yes.
17. NEEDA Need This parameter specifies whether to Enumerated Yes C
DDITIO Additional authenticate the account name and No
NALAU Auth password if a subscriber requests to
TH update the service information on the
Portal. The parameter is valid if Portal
Tunable is set to Yes.
18. SUBSC Subscripti This parameter specifies the notification string 1-32 O
RIPTIO on to be sent when the service has been
NNOTIF Notificatio subscribed to.
ICATIO n
N
19. MODIFI Modificati This parameter specifies the notification String 1-32 O
CATION on to be sent when the service has been
NOTIFI Notificatio modified.
CATION n
20. START Start This parameter specifies the notification String 1-32 O
NOTIFI Notificatio to be sent when the service takes effect.
CATION n
21. ENDNO End This parameter specifies the notification String 1-32 O
TIFICA Notificatio to be sent when the service expires.
TION n
22. Before This parameter specifies the notification String 1-32 O
BEFOR Expiry sent before the service expires.
EEXPIR Notificatio
YNOTIF n
ICATIO
N
23. BEFOR BeforeExp This parameter specifies the number of Number 30-43200 C
EEXPIR iry minutes before a service expiration
YINTER Interval notification is sent. The parameter is
VAL valid only when Before Expiry
Notification is specified.
24. CALCU Calculate This parameter specifies the time to start Enumerated Subscribut O
LATETI Time calculating the service validation e_Calculat
ME duration. e
25. DURATI Duration This parameter specifies the unit used to Enumerated Hour C
ONTYP Type measure the service validation duration. Day
E
26. DURATI Duration This parameter specifies the service Number 1-8784 C
ONVAL validation duration.
UE
27. DESCRI Descriptio This parameter provides additional String 1-256 O
PTION n information about the service.
28. PROBIL Provided This Parameter specifies the service Enumerated Yes C
LDATE till Bill expiry on the next bill date. No
Date
29. ENDTI End Time This Parameter specifies the service DateTime 8 C
ME expiry time.
30. QUOTA Quota This Parameter specifies the quota Enumerated None O
ALLOC Allocation allocation mode when the service has Days
ATION Mode been subscribed to. Proration
MODE
31. CUSTO Customer This Parameter specifies the service Number 0- O
MERAT Attribute customer attribute 21474836
TRIBUT 45
E
32. ISSETS Is Set This Parameter specifies whether set Enumerated Yes C
HARED Shared shared mode of the service. No
MODE Mode
33. SHARE Shared This Parameter specifies the shared Enumerated Share C
DMODE Mode mode of the service. d
NotS
hared
34. ISGRO Is Group This Parameter specifies the group Enumerated Yes O
UPSER Service attribute of the service. No
VICE
35. NOTIFY Notify This Parameter specifies the notify String 120 O
CODE code sender code of the notification of this
service.
36. QRYNO SMS This parameter specifies the notification String 132 O
TIFICA Query when its triggered by the SMS query
TION Notificatio message.
n
Duration Type and Duration must be specified or left blank at the same time. If Duration Type is
set to Day, the value of Duration ranges from 1 to 366. If Duration Type is set to Hour, the value
of Duration ranges from 1 to 8784. For details, see the product documentation.
Provided till Bill Date cannot be set to Yes when Duration is specified.
Cannot set the Shared Mode and Is Set Shared Mode when Is Group Service is be set to
YES.When Is Group Service is YES,the Shared Mode is Shared and Is Set Shared Mode is No.
15.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
12308: The SP does not exist
12525: The service has been subscribed by subscriber group, sp, account,quota and
IsGroupService cannot be modified
12600: The Account does not exist
12628: Invalid datetime
90168: The Start Notification does not exist
90169: The End Notification does not exist
90183: The All notifications do not exist
90184: The Subscription Notification does not exist
90185: The Mod Service Notification does not exist
90192: The expiry notification does not exist
94209: Processing timeout
94210: PAU system processing failed
94253: If parameter SERVICETYPE is not set to MULTI-SERVICE-APN, the
parameters of DEFAULTACTIVATE, DISPLAYNAME, PATUNABLE, SERVICEURL,
and NEEDADDITIONALAUTH cannot be specified
94254: If parameter SERVICETYPE is set to MULTI-SERVICE-APN or
BOD_SERVICE, the parameters of DEFAULTACTIVATE and PATUNABLE must be
specified, and the parameters of APN and VPN cannot be specified
94255: If parameter PATUNABLE is set to yes, the
parameterNEEDADDITIONALAUTH must be specified, and if the parameter
PATUNABLE is set to no, the parameters of NEEDADDITIONALAUTH and
SERVICEURL cannot be specified
94256: If parameter BEFOREEXPIRYNOTIFICATION is not specified, the parameter
BEFOREEXPIRYINTERVAL cannot be specified
94263: The service that is activated by default cannot be configured with authentication
information
94264: The MULTI-SERVICE APN cannot be activated by the AF
94271: Operator not logged in
94328: If parameter SERVICETYPE is set to BOD_SERVICE, the parameters of APN,
DISPLAYNAME, VPN, SERVICEURL, and NEEDADDITIONALAUTH
94332: The Default Activate mode of BOD service can not be modified
94523: If parameter PROBILLDATE is set to yes, the parameter Duration cannot be
specified
94524: The parameters PROBILLDATE and ENDTIME configuration conflicts
12609: The service has been subscribed by subscriber, sp, account,quota and
IsGroupService cannot be modified
94581: Mismatched service type
94583: The Service with notify code NULL is already exist
15.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12299: The service has been ordered
12304: The service does not exist
12383: The service cannot be deleted because it is associated with an application service
mapping
12384: The service cannot be deleted because it is associated with a service package
12385: The service cannot be deleted because it is associated with a mutex group
15.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
15.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
15.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
15.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12303: The quota does not exist
12304: The service does not exist.
94209: Processing timeout
94210: PAU system processing failed
94220: The quota does not exist in service
94271: Operator not logged in
12609: The service has been subscribed by subscriber, sp, account,quota and
IsGroupService cannot be modified
16 Package Management
A maximum of 1024 service packages can be configured in the system. Each service package can be
configured with a maximum of 32 services.
16.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12308: The SP does not exist
12361: The service package already exists
90168: The Start Notification does not exist
90169: The End Notification does not exist
90183: The All notifications do not exist
90184: The Subscription Notification does not exist
90185: The Mod Service Notification does not exist
90192: The expiry notification does not exist
94209: Processing timeout
94210: PAU system processing failed
94256: If parameter BEFOREEXPIRYNOTIFICATION is not be specified, the
parameter BEFOREEXPIRYINTERVAL cannot be specified
94271: Operator not logged in
94581: Mismatched service type
16.2.4 Result
A code is returned, indicating the operation result. If the operation is successful, the following
code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
16.3.4 Result
A code is returned, indicating the operation result.
16.4.4 Result
A code is returned, indicating the operation result.
16.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
12512: The service package is associated with a subscriber
94209: Processing timeout
94210: PAU system processing failed
94214: The service does not exist in service package
94271: Operator not logged in
A maximum of 128 mutex groups can be configured in the system. Each mutex group can be configured
with a maximum of 512 services.
17.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12308: The SP does not exist
12364: The mutex group already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
17.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12365: The mutex group cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
17.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12365: The mutex group cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
17.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
12365: The mutex group cannot be found
12366: The services of mutually exclusive groups belong to the same service package
12491: The number of services in the mutex group exceeds the maximum value (512)
12526: The mutex groups of same types but different operation attributes can have only
one identical service
12527: If Type is set to Subscribe and Operation is set to any value of Overwrite, Extend
Validity, Accumulate Quota, Extend Validity and Accumulate Quota for a mutex group,
this mutex group cannot use any identical service with the mutex group of other
subscribe types
90149: The services subscribed by the same subscriber group cannot be added into the
same mutex
94209: Processing timeout
94210: PAU system processing failed
94217: The service already exists in mutex group
94269: Services in the same mutex group must associated with quotas of same class and
same number
94271: Operator not logged in
98310: The quota managed by an external entity cannot be associated with a mutex
group with Operation set to Accumulate Quota or Extend Validity and Accumulate Quota
98402: Shared service and not-shared service can not exist in the same mutex group
which type is subscribe
17.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
12365: The mutex group cannot be found
94209: Processing timeout
94210: PAU system processing failed
94216: The service does not exist in mutex group
94271: Operator not logged in
The combination of Application Identifier and Service Class is unique. It maps to only one service.
A maximum of 100 application service mapping records can be configured in the system.
APPLICATIONSERVICEMAPPING:
{APPID} = <Application Identifier>,
{SERVICECLASS} = <Service Class>,
{SERVICENAME} = <Service Name>;
Example:
ADD APPLICATIONSERVICEMAPPING: APPID = "abcd", SERVICECLASS = "1",
SERVICENAME = "abcd";
18.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12358: The mapping to the application service already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
3. SERVICENAME Service Name This parameter specifies the service String 1-32 O
that maps to a combination of
application identifier and service
class.
18.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
12357: The mapping to the application service cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
18.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12357: The mapping to the application service cannot be found
94209: Processing timeout
94210: PAU system processing failed
19 Domain Management
A maximum of 1,024 domains can be configured in the system. Each domain can be configured with a
maximum of 512 services and a maximum of 512 service packages.
19.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The domain that has Domain Name set to default1 cannot be modified.
Example:
MOD DOMAIN: DOMAINNAME = "abcd", DESCRIPTION = "abcdef";
19.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8217: This item cannot be configured
12306: The domain does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
The domain that has Domain Name set to default1 cannot be deleted.
19.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8199: This item cannot be deleted
8201: Invalid parameter
12306: The domain does not exist
12386: The domain is associated with a subscriber, a subscriber group, or a device
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
19.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8217: This item cannot be configured
12304: The service does not exist
12306: The domain does not exist
12492: The number of services of the domain exceeds the maximum value (512)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94274: The service already exists in the domain
This command cannot be used to delete a service for the domain that has Domain Name set to default1.
19.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8199: This item cannot be deleted
12304: The service does not exist
12306: The domain does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94275: The service does not exist in the domain
19.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8217: This item cannot be configured
12306: The domain does not exist
12362: The service package cannot be found
12493: The number of service packages of the domain exceeds the maximum value (512)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94276: The service package already exists in the domain
This command cannot be used to delete a service package associated with the domain that has Domain
Name set to default1.
19.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8199: This item cannot be deleted
12306: The domain does not exist
12362: The service package cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94277: The service package does not exist in the domain
Charging Server Group Name cannot be the same as an existing charging server group name.
A maximum of 1,024 charging server groups can be configured in the system.
20.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94222: The destination PCEF does not exist
94271: Operator not logged in
94500: The charging server group already exists
94502: The number of charging server group exceeds the maximum value.(1024)
20.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94222: The destination PCEF does not exist
94271: Operator not logged in
94501: The charging server group does not exist
20.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94501: The charging server group does not exist
94503: The charging server group cannot be deleted because it is associated with
subscriber group
Charging Server Name cannot be the same as an existing charging server name. A maximum of
1,024 charging servers can be configured in the system.
Before setting the parameters of the charging servers, you must configure the primary online server
or primary offline server. The secondary server can be configured only after the primary server is
configured. At least one of the Primary Online URI and Primary Offline URI parameters must be
specified.
The format of the URI can be:
aaa://host.example.com:1813;transport=udp;protocol=radius or
aaas://host.example.com:1813;transport=udp;protocol=radius
20.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12463: The charging server already exists
12464: You cannot configure the secondary URI because the primary URI is empty
12465: You must configure at least one primary URI
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94501: The charging server group does not exist
94504: The number of charging server exceeds the maximum value.(1024)
94505: The format is incorrect. The value must be in the format of [aaa|
aaas]://hostname[:port][;transport=tcp|sctp|udp][;protocol=diameter|radius|tacacs+]. If
transport is not specified, the default value sctp is used. If protocol is not specified, the
default value diameter is used. When protocol is set to diameter, transport cannot be set
to udp. When protocol is set to radius, transport can only be set to udp
20.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12461: The charging server does not exist
12464: You cannot configure the secondary URI because the primary URI is empty
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94501: The charging server group does not exist
94505: The format is incorrect. The value must be in the format of [aaa|
aaas]://hostname[:port][;transport=tcp|sctp|udp][;protocol=diameter|radius|tacacs+]. If
transport is not specified, the default value sctp is used. If protocol is not specified, the
default value diameter is used. When protocol is set to diameter, transport cannot be set
to udp. When protocol is set to radius, transport can only be set to udp
20.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12461: The charging server does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94501: The charging server group does not exist
16. APPLYTYPE Apply Type This parameter specifies the Enumerated Default O
application type of a For-
subscriber group. Existent-
Subscrib
er
For-Non-
existent-
Subscrib
er
For-Non-
Subscrip
tion
For-DB-
Error
IMS_Eme
rgency
17. DYNSUBMA DynSubMaxO This parameter specifies the Number 0-30 C
XOFFLINEDA fflineDays data storage duration for a
YS dynamically generated
subscriber who is in an
offline mode. The parameter
is valid if Apply Type is set
to For-Non-existent-
Subscriber.
18. DESCRIPTIO Subscriber This parameter provides String 1-256 O
N Group additional information
Description about the subscriber group.
19. IPv6ADDRES IPv6 Address This parameter specifies the String 1-40 O
S IPv6 address of a subscriber
group.
20. IPv6PREFIXL IPv6 Mask or This parameter specifies the String 1-40 O
ENGTH Prefix Length IPv6 mask of a subscriber
group or prefix length of the
mask.
21. CUSTOMERA Subscriber This parameter specifies the O
TTR customized customized subscriber Number 0-65535
attributes attribute.
A maximum of 128 dynamic subscriber groups can be configured in the system. Each group is
configured with a maximum of 10 services.
The values of Access MCC MNC and MSISDN Prefix must be digits. The values of IP Address
and Mask must be in IPv4 format.
21.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12308: The SP does not exist
12359: The Subscriber Group already exists
12360: The subscriber group cannot be found
12441: The condition group does not exist
12459: The number of dynamic subscriber groups reaches the upper limit (128)
12461: The charging server does not exist
12481: Invalid IP address. The value must be an IPv4 address in D.D.D.D format, an
IPv6 address in X:X:X:X:X:X:X:X format, or an IPv6 address embedded with an IPv4
address, that is, in X:X:X:X:X:X:D.D.D.D format. D is an 8-bit decimal number, X is a
16-bit hexadecimal number. If two or more consecutive Xs are 0, the 0s can be replaced
by ::. For example, X:X:X:0:0:0:X:X can be replaced by X:X:X::X:X. Only one :: is
allowed
12620: Invalid subnet mask. If the IP address is in IPv4 format, the subnet mask must be
in D.D.D.D format (where D is an 8-bit decimal number) or a decimal number ranging
from 0 to 32. If the IP address is in IPv6 format, the subnet mask must be in
X:X:X:X:X:X:X:X format (where X is a 16-bit hexadecimal number) or a decimal
number ranging from 0 to 128
90150: The priority of dynamic subscriber group already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94501: The charging server group does not exist
94509: The number of condition groups exceeds the maximum value (1)
SUBSCRIBERGROUP:
{SUBSCRIBERGROUPNAME} = <Subscriber Group Name>,
{PRECEDENCE} = <Precedence>,
{CHARGINGSERVER} = <Charging Server Group >,
{ACCESSMCCMNC} = <Access MCC MNC>,
{IMSIPREFIX} = <IMSI Prefix>,
{MSISDNPREFIX} = <MSISDN Prefix>,
{IPADDRESS} = <IPv4 Address>,
{MASK} = <IPv4 Mask or Prefix Length>,
{PCEFHOSTNAME} = <PCEF Host Name>,
{PCEFDOMAINNAME} = <PCEF Domain Name>,
{APN} = <APN>,
{PAIDTYPE} = <Paid Type>,
{CATEGORY} = < Category>,
{ROAMINGSTATUS} = <Roaming Status>,
{DYNSUBMAXOFFLINEDAYS} = <DynSubMaxOfflineDays>,
{DESCRIPTION} = <Subscriber Group Description>,
{IPv6ADDRESS} = <IPv6 Address>,
{IPv6PREFIXLENGTH} = < IPv6 Mask or Prefix Length>,
{CUSTOMERATTR}=<Subscriber customized attributes>;
Example:
MOD SUBSCRIBERGROUP: SUBSCRIBERGROUPNAME="SUBSCRIBERGRP3",
PRECEDENCE = 8, ACCESSMCCMNC="123", IMSIPREFIX="123",
MSISDNPREFIX="123", IPADDRESS="1.2.3.4", MASK="255.0.0.0",
PCEFHOSTNAME="pcef.com", PCEFDOMAINNAME="pcef.huawei.com",
APN="huawei", PAIDTYPE = NULL, CATEGORY = "3", ROAMINGSTATUS=NULL,
DESCRIPTION="subscriber3", IPv6ADDRESS = "1:2:3:4::", IPv6PREFIXLENGTH = "64",
CUSTOMERATTR = 1;
21.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
SUBSCRIBERGROUP:
{SUBSCRIBERGROUPNAME} = <Subscriber Group Name>;
Example:
RMV SUBSCRIBERGROUP: SUBSCRIBERGROUPNAME = "UserGrp1";
21.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12360: The subscriber group cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
21.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12360: The subscriber group cannot be found
12440: The condition group already exists
12441: The condition group does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94509: The number of condition groups exceeds the maximum value (1)
94510: The element of the condition group does not match the subscriber group
21.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12360: The subscriber group cannot be found
12441: The condition group does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94522: The condition group does not exist in the subscriber group
21.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
21.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12304: The service does not exist
94209: Processing timeout
94210: PAU system processing failed
94235: The service is not associated with the subscriber group, and therefore it cannot be
deleted
94271: Operator not logged in
22.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90136: The terminal type already exists
90146: The number of the terminal type cannot exceed max (128)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
22.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90137: The terminal type does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
22.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90137: The terminal type does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
22.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90137: The terminal type does not exist
90144: The IMEI prefix already exist
90147: The number of the terminal cannot exceed max (2048)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
22.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90137: The terminal type does not exist
90145: The IMEI prefix does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
TERMINAL:
{TERMINALTYPENAME} = <Terminal Type Name>,
{IMEIPREFIX} = <IMEI Prefix>;
Example:
RMV TERMINAL: TERMINALTYPENAME = "abcd", IMEIPREFIX= "456";
22.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
90137: The terminal type does not exist
90145: The IMEI prefix does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Roam Region Identity cannot be the same as an existing roaming region identity.
A maximum of 128 roaming regions can be configured in the system
23.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12498: The number of PLMNs in the roaming region exceeds the maximum value (512)
12610: The RoamRegion already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
23.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12611: The RoamRegion cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
23.3.4 Result
A code is returned, indicating the operation result.
The PLMN to be associated with the roaming region must already exists in the system.
A PLMN can be homed to a maximum of 10 roaming regions.
23.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12498: The number of PLMNs in the roaming region exceeds the maximum value (512)
12625: The PLMN already exists in roaming region
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94576: One of the PLMNs has already been joined in ten Roam Region
ROAMREGIONPLMN:
{ROAMREGIONIDENTITY} = <Roam Region Identity>,
{PLMNIDENTITY} = <PLMN Identity>;
Example:
RMV ROAMREGIONPLMN: ROAMREGIONIDENTITY = "ROAM1", PLMNIDENTITY
= "PLMN1";
23.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
24 PLMN Management
24.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8196: The name already exists
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12356: The PLMN already exists
12497: The MCC and MNC must both exist or both not exist
12611: The RoamRegion cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
24.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12356: The PLMN already exists
12497: The MCC and MNC must both exist or both not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
24.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12611: The RoamRegion cannot be found
12614: The PLMN has been referenced
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
24.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
24.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12481: Invalid IP address. The value must be an IPv4 address in D.D.D.D format, an
IPv6 address in X:X:X:X:X:X:X:X format, or an IPv6 address embedded with an IPv4
address, that is, in X:X:X:X:X:X:D.D.D.D format. D is an 8-bit decimal number, X is a
16-bit hexadecimal number. If two or more consecutive Xs are 0, the 0s can be replaced
by ::. For example, X:X:X:0:0:0:X:X can be replaced by X:X:X::X:X. Only one :: is
allowed
12613: The SGSN does not exist
12618: The SGSN does not exist
12620: Invalid subnet mask. If the IP address is in IPv4 format, the subnet mask must be
in D.D.D.D format (where D is an 8-bit decimal number) or a decimal number ranging
from 0 to 32. If the IP address is in IPv6 format, the subnet mask must be in
X:X:X:X:X:X:X:X format (where X is a 16-bit hexadecimal number) or a decimal
number ranging from 0 to 128
12629: The IP address and mask configured for an SGSN must be unique
12630: The subnet addresses configured for an SGSN must be unique
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
98307: The SGSN number (or SGSN number prefix) already exists
24.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12613: The SGSN does not exist
12618: The SGSN does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
24.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12481: Invalid IP address. The value must be an IPv4 address in D.D.D.D format, an
IPv6 address in X:X:X:X:X:X:X:X format, or an IPv6 address embedded with an IPv4
address, that is, in X:X:X:X:X:X:D.D.D.D format. D is an 8-bit decimal number, X is a
16-bit hexadecimal number. If two or more consecutive Xs are 0, the 0s can be replaced
by ::. For example, X:X:X:0:0:0:X:X can be replaced by X:X:X::X:X. Only one :: is
allowed
12620: Invalid subnet mask. If the IP address is in IPv4 format, the subnet mask must be
in D.D.D.D format (where D is an 8-bit decimal number) or a decimal number ranging
from 0 to 32. If the IP address is in IPv6 format, the subnet mask must be in
X:X:X:X:X:X:X:X format (where X is a 16-bit hexadecimal number) or a decimal
number ranging from 0 to 128
94209: Processing timeout
94210: PAU system processing failed
94271 Operator not logged in
94320: The number of ANGWs exceeds the maximum value
94321: The number of ANGWs in the PLMN exceeds the maximum value.(512)
94322: The IP address and mask configured for an ANGW must be unique
94324: The ANGW Identify must be unique
94331: The subnet addresses configured for an ANGW must be unique
24.8.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
12481: Invalid IP address. The value must be an IPv4 address in D.D.D.D format, an
IPv6 address in X:X:X:X:X:X:X:X format, or an IPv6 address embedded with an IPv4
address, that is, in X:X:X:X:X:X:D.D.D.D format. D is an 8-bit decimal number, X is a
16-bit hexadecimal number. If two or more consecutive Xs are 0, the 0s can be replaced
by ::. For example, X:X:X:0:0:0:X:X can be replaced by X:X:X::X:X. Only one :: is
allowed
12620: Invalid subnet mask. If the IP address is in IPv4 format, the subnet mask must be
in D.D.D.D format (where D is an 8-bit decimal number) or a decimal number ranging
from 0 to 32. If the IP address is in IPv6 format, the subnet mask must be in
X:X:X:X:X:X:X:X format (where X is a 16-bit hexadecimal number) or a decimal
number ranging from 0 to 128
94209: Processing timeout
94210: PAU system processing failed
94271 Operator not logged in
94322: The IP address and mask configured for an ANGW must be unique
94323: The ANGW does not exist
94331: The subnet addresses configured for an ANGW must be unique
24.9.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
12355: The PLMN cannot be found
94209: Processing timeout
94210: PAU system processing failed
94271 Operator not logged in
94323: The ANGW does not exist
Service Zone Identity cannot be the same as an existing service zone identity.
A maximum of 1,024 service zones can be configured in the system.
25.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12475: The service zone already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Example:
MOD SERVICEZONE: SERVICEZONEIDENTITY = "abcd", DESCRIPTION =
"SERVICEZONE description";
25.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12474: The service zone does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
25.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12474: The service zone does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
25.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12474: The service zone does not exist
12477: The area already exists
12479: A maximum of 3072 areas can be set for a service zone
12508: The number of areas exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94553: A maximum of five service zones per area can be joined in
94554: The area has been joined in this service zone
25.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
25.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12474: The service zone does not exist
12476: The area does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Each service zone can be configured with a maximum of 200 auxiliary areas.
A maximum of 8,192 auxiliary areas can be configured in the system.
A maximum of 200,000 associations between auxiliary areas and service zones can be configured in
the system.
Area Identity identifies an area. The value of this parameter varies according to the area type:
If Area Type is set to CGI, the value is a decimal number of 15 or 16 digits.
If Area Type is set to SAI, the value is a decimal number of 15 or 16 digits.
If Area Type is set to RAI, the value is a decimal number of 15 or 16 digits.
If Area Type is set to SGSNAddress or ANGWAddress, the value of Area Identity is an IP address. If
the IP address is in IPv4 format, its format is D.D.D.D. If the IP address is in IPv6 format, its format is
X:X:X:X:X:X:X:X. If the IP address is in IPv6 format with an IPv4 address inserted, its format is
X:X:X:X:X:X:D.D.D.D. (D is an 8-digit decimal number, and X is a 16-digit hexadecimal number.) One
or any number of consecutive groups of 0 value may be replaced with two colons (::). Therefore, the
address X:X:X:0:0:0:X:X can be further simplified and expressed as X:X:X::X:X.
If Area Type is set to TAI, the value is a decimal number of 10 or 11 digits.
If Area Type is set to ECGI, the value is a decimal number of 14 or 15 digits.
If Area Type is set to BSID, the value is a hexadecimal number of 12 digits.
If Area Type is set to LAI, the value is a decimal number of 10 to 11 digits. The value of LAC Value
ranges from 0 to 65535.
25.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12474: The service zone does not exist
94209: Processing timeout
94210: PAU system processing failed
25.8.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12474: The service zone does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
98327:The auxiliary area does not exists
Message Template Name cannot be the same as an existing message template name.
If you need to add an attribute to the content of a template, the message content is in
{OBJ.object.attribute} format. For example, if the MSISDN of the subscriber needs to be contained in a
message, enter {OBJ.Subscriber.MSISDN} for the Content.
If the Message Type is set to JMS, the valid message content can be selected only from the following
message contents:
{OBJ.IPSession.IMSI}
{OBJ.Subscriber.MSISDN}
{OBJ.Subscriber.Status}
{OBJ.Subscriber.HomeServiceZone}
{OBJ.Subscriber.PaidType}
{OBJ.Subscriber.Category}
{OBJ.Subscriber.Station}
{OBJ.Subscriber.MasterIdentifier}
{OBJ.Subscriber.EmailAddress}
{OBJ.Subscriber.ContactMethod}
{OBJ.Subscriber.BillCycleDate}
{OBJ.System.EventDate}
{OBJ.Quota.QuotaName}
{OBJ.Quota.QuotaValue}
{OBJ.Quota.QuotaBalance}
{OBJ.Quota.QuotaConsumption}
{OBJ.Subscription.ServiceName}
{OBJ.Subscription.UsageStatus}
{OBJ.Subscription.SrvStartDateTime}
{OBJ.Subscription.SrvEndDateTime}
{OBJ.Subscription.SrvRoamingType}
{OBJ.Subscription.SrvPkgName}
{OBJ.Subscription.SrvPkgStartDateTime}
{OBJ.Subscription.SrvPkgEndDateTime}
{OBJ.Subscription.SrvPkgRoamingType}
{OBJ.Subscription.LimitType}
{OBJ.Subscription.LimitId}
A maximum of 512 templates can be configured in the system.
26.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
16442: The message template already exists
94209: Processing timeout
94210: PAU system processing failed
26.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
26.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
27 Login Management
27.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8201: Invalid parameter
8195: Database error
20485: Incorrect user name or password
20487: The system user does not exist
94209: Processing timeout
94210: PAU system processing failed
27.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
8201: Invalid parameter
94271: Operator not logged in
APN List Name cannot be the same as an existing APN list name.
A maximum of 32 APN lists can be configured in the system.
28.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94512: The APN list already exists
94514: The number of APN list exceeds the maximum value (32)
Example:
MOD APNLIST: APNLISTNAME = "abcd", DESCRIPTION = " APNLISTNAME
description";
28.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94513: The APN list does not exist
28.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94513: The APN list does not exist
APN Name cannot be the same as an existing APN name. An APN name belongs to only one APN
list. The APN names are different no matter whether the APN names are in the same or different
APN lists.
Each APN list can be configured with a maximum of 256 APNs.
A maximum of 1,024 APNs can be configured in the system.
28.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94513: The APN list does not exist
94515: The APN already exists
94517: The number of APN in the APN list exceeds the maximum value (256)
94518: The number of APN exceeds the maximum value (1024)
28.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94516: The APN does not exist
28.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94516: The APN does not exist
29.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94526: The language ID already exists
29.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
29.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
30.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94544: The redirection URL already exists
94546: The number of redirection URLs exceeds the maximum value(1024)
30.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94545: The redirection URL does not exist
94547: The redirection URL has been referenced
Example:
abs|2011-06-15 00:00:00#2011-06-22 23:59:59,
or
rel|year(*) mon(1:2:3:4:5:6:7:8:9:10:11:12)
date(1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20:21:22:23:24:25:26:27:28:29
:30:31) week(1:2:3:4:5:6:7) starttime(00:00:00) last(24)
or
rel|year(*) mon(1:2:3:4:5:6:7:8:9:10:11:12)
date(1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20:21:22:23:24:25:26:27:28:29
:30:31) week(1:2:3:4:5:6:7) starttime(00:00:00) last(24:00).
31.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
16448:The holiday define already exists
94209: Processing timeout
94210: PAU system processing failed
Example:
abs|2011-06-15 00:00:00#2011-06-22 23:59:59,
or
rel|year(*) mon(1:2:3:4:5:6:7:8:9:10:11:12)
date(1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20:21:22:23:24:25:26:27:28:29
:30:31) week(1:2:3:4:5:6:7) starttime(00:00:00) last(24)
or
rel|year(*) mon(1:2:3:4:5:6:7:8:9:10:11:12)
date(1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20:21:22:23:24:25:26:27:28:29
:30:31) week(1:2:3:4:5:6:7) starttime(00:00:00) last(24:00).
31.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
16450:The holiday define does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
31.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
8195: Database error
8201: Invalid parameter
16450:The holiday define does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
32.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94548: The service map already exists
94550: The number of service map exceeds the maximum value(2048)
32.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94549: The service map does not exist
{ ARP } = <ARP>;
Example:
ADD RPMAP: RESERVATIONPRIORITY = Default, ARP = 15;
33.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94580: The Reservation-Priority mapping already exists
33.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94588: Reservation priority is not exist
33.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94588: Reservation priority is not exist
34.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
98329: The policy counter status already exists
34.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation fails, one of the following error codes may be displayed:
5002: Flow control enabled
34.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
35.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
98331: The Subscriber Segment already exists
98332: The number of Subscriber Segment reaches the upper limit (512)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
35.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98320: The Subscriber Segment does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
35.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98320: The Subscriber Segment does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
35.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98320: The Subscriber Segment does not exist
98321: The Number Prefix already exists
98322: The number of Number Prefix reaches the upper limit (2048)
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
35.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98320: The Subscriber Segment does not exist
98323: The Number Prefix does not exist
94209: Processing timeout
94210: PAU system processing failed
Pray time indicates the time period during which people in Muslim countries pray. A day is divided into
five pray periods with each period lasing 15 to 40 minutes. People in Muslim countries pray every day in
a year.
Pray time is divided into 12 segments. The requirements fort the first three segments is as follows:
Segment 1: Indicates a city name.
Segment 2: Indicates a city code defined in the carrier's system.
Segment 3: Indicates the start pray time and end pray time. The format of the time is
YYYYMMDDhhmmss. The back flash (\) muse be added in front of a comma (,).
For example:
ADD
PRAYTIME:PRAYTIME="Riyadh\,RUH\,20130101051500\,20130101055500\,2013010111
5700\,20130101122200\,20130101145700\,20130101152200\,20130101171700\,2013010117
3200\,20130101184700\,20130101191700";
36.1.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
94610: [PrayTime]The record is invalid.
94611: [PrayTime]The city code is invalid.
94612: [PrayTime]The datetime is invalid.
94613: [PrayTime]The year record exists, please delete that record firstly.
94614: [PrayTime]The YYYYMMDD record exists, please delete that record firstly.
36.2.4 Result
A code is returned, indicating the operation result.
This parameter
Enumeration specifies the
1 ENUMNAME String 1-32 M
Name name of an
enumeration.
37.1.4 Result
A code is returned, indicating the operation result.
This parameter
Enumeration specifies the
1 ENUMNAME String 1-32 M
Name name of an
enumeration.
37.2.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98369: The enumeration does not exist
98372: The enumeration cannot be deleted beause it is not custom
98358: The enumeration cannot be deleted beause it is associated with a enumeration
member
98374: The enumeration cannot be deleted because it is associated with a action
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
This parameter
Enumeration specifies the
1 ENUMNAME String 1-32 M
Name name of an
enumeration.
2 ENUMELEMNAME Enumeration This parameter String 1-256 M
Member specifies the
Name name of an
enumeration
member.
3 VALUE Enumeration This parameter Number 0-4294967295 M
Member specifies the
Value value of an
enumeration
member.
37.3.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
98369: The enumeration does not exist
98370: The enumeration member already exists
98376: The enumeration member cannot be added because the enumeration is not
custom
98377: Invalid enumeration member name
98384: Invalid enumeration member value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
This parameter
Enumeration specifies the
1 ENUMNAME String 1-32 M
Name name of an
enumeration.
2 ENUMELEMNAME Enumeration This parameter String 1-256 M
Member specifies the
Name name of an
enumeration
member.
37.4.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98371: The enumeration member does not exist
98373: The enumeration member cannot be deleted beause it is not custom
98375: The enumeration member cannot be deleted because it is associated with a action
98369: The enumeration does not exist
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
37.5.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
98385: Invalid group AVP mapped action
98387: The action already exists
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
37.6.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98391: The action cannot be deleted beause it is not custom
98388: The action does not exist
98394: The action cannot be deleted because it is associated with a action group
98397: The action cannot be deleted because it is associated with a action element
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
CUSTOMACTIONELEMDICT:
{ACTIONNAME} = <Action Name>,
{ACTIONELEMNAME} = <Element Name>,
{DATATYPE} = <Element Data Type>,
{MAPPEDAVP} = <Element MAP AVP >,
{ISOPTIONAL} = <Is Optional>,
{ENUMNAME} = <Enumeration Name> ;
Example:
ADD CUSTOMACTIONELEMDICT:
ACTIONNAME="customaction",ACTIONELEMNAME="elemname",DATATYPE=Integer3
2,MAPPEDAVP=100,ISOPTIONAL=Yes;
37.7.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
98369: The enumeration does not exist
98385: Invalid group AVP mapped action
98386: Invalid AVP mapped action element
98387: The action already exists
98389: The action element already exists
98393: The action element cannot be added because the action is not custom
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
37.8.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
98388: The action does not exist
98390: The action element does not exist
98392: The action element cannot be deleted beause it is not custom
98395: The action element cannot be deleted because it is associated with a action group
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
37.9.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
37.10.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
98391: The action cannot be deleted beause it is not custom
98397: The action cannot be deleted because it is associated with a action element
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
37.11.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
8204: The number of records exceeds the maximum value
12452: The action group does not exist
12455: The action does not exist
12312: Incorrect action attribute
98390: The action element does not exist
98393: The action element cannot be added because the action is not custom
98398: The action element cannot be added because the action already exists in action
98400: Invalid action element value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
MOD CUSTOMACTIONELEM:
ACTIONGROUPNAME="groupname",ACTIONNAME="actionname",ACTIONELEMNA
ME="elemname",VALUETYPE=Value,VALUE="0";
37.12.4 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
12312: Incorrect action attribute
98357: The action element cannot be modified because it is not custom
98390: The action element does not exist
98400: Invalid action element value
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in
Command Format
[RMV]
CUSTOMACTIONELEM:
{ACTIONGROUPNAME} = <Action Group Name> ,
{ACTIONNAME} = <Action Name> ,
{ACTIONELEMNAME} = <Action Element Name>;
Example:
RMV CUSTOMACTIONELEM:
ACTIONGROUPNAME="groupname",ACTIONNAME="actionname",ACTIONELEMNA
ME="elemname";
37.13.3 Result
A code is returned, indicating the operation result.
If the operation is successful, the following code is displayed:
0: Operation is successful
If the operation is not successful, one of the following error codes may be displayed:
5002: Flow control enabled
8195: Database error
8201: Invalid parameter
12452: The action group does not exist
12455: The action does not exist
98390: The action element does not exist
98392: The action element cannot be deleted beause it is not custom
94209: Processing timeout
94210: PAU system processing failed
94271: Operator not logged in