Zte 1 Config PDF

ZXUN USPP Series HLR AUC Feature Description
ZXUN USPP Series HLR AUC

Feature Description
ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. I
PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

Version Date Author Approved By Remarks
V1.00 2010-03-18 Not open to the Third Party
© 2011 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document
is subjected to change without notice.
ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. I

ZXUN USPP Series HLR AUC Feature List
TABLE OF CONTENTS
ZXUN USPP Series HLR AUC Feature List ...................................................................... I
TABLE OF CONTENTS......................................................................................................II
1 Overview ..........................................................................................................1
2 Basic Features .................................................................................................1

2.1 ZWF-05-01-001 SIM State Management ........................................................1
2.2 ZWF-05-01-002 Telephony Subscription.........................................................2
2.3 ZWF-05-01-003 R98 GPRS Service ...............................................................3
2.4 ZWF-05-01-004 2G Authentication Information Management .........................4
2.5 ZWF-05-01-005 Emergency Call.....................................................................5
2.6 ZWF-05-01-006 Short Message Services .......................................................6
2.7 ZWF-05-01-007 3G Authentication Information Management .........................6
2.8 ZWF-05-01-008 R99 GPRS Service ...............................................................7
2.9 ZWF-05-02-001 Local Subscriber Data Administration Function for 2G
Subscriber.......................................................................................................10
2.10 ZWF-05-02-003 Remote Subscriber Data Administration Functions for 2G
Subscriber.......................................................................................................11
2.11 ZWF-05-02-004 Local Subscriber Data Administration Function for 3G
Subscriber.......................................................................................................12
2.12 ZWF-05-02-005 Subscription Profile .............................................................14
2.13 ZWF-05-02-006 Remote Subscriber Data Administration Functions for 3G
subscriber .......................................................................................................15
2.14 ZWF-05-03-001 External Signaling Interfaces of CS Domain ........................16
2.15 ZWF-05-03-003 Physical Interface - E1 Interface Functions .........................17
2.16 ZWF-05-03-004 Physical Interface - T1 Interface Functions .........................18
2.17 ZWF-05-03-005 Gr Interface .........................................................................18
2.18 ZWF-05-03-006 J Interface ...........................................................................19
2.19 ZWF-05-03-007 Lh Interface .........................................................................19
2.20 ZWF-05-03-008 Gc Interface ........................................................................20
2.21 ZWF-05-04-001 2G Authentication Function .................................................20
2.22 ZWF-05-04-002 CS Location Update Function .............................................22
2.23 ZWF-05-04-003 Subscription Data Management Functions ..........................23
2.24 ZWF-05-04-004 Recovery Function ..............................................................23
2.25 ZWF-05-04-005 MS Deletion ........................................................................24
2.26 ZWF-05-04-006 MS Purging Function...........................................................25
2.27 ZWF-05-04-007 IMSI Query Based on MSISDN ...........................................26
2.28 ZWF-05-04-008 Mobile Terminated Call .......................................................26
2.29 ZWF-05-04-009 Supplementary Service Operations .....................................27
2.30 ZWF-05-04-010 Short Message Routing.......................................................28
2.31 ZWF-05-04-011 Short Message Delivery State Report .................................29
2.32 ZWF-05-04-012 Short Message Alert Service ...............................................29
2.33 ZWF-05-04-013 PS Location Update ............................................................30
2.34 ZWF-05-04-014 GPRS Routing Function ......................................................30
2.35 ZWF-05-04-015 GPRS Failure Report ..........................................................31
2.36 ZWF-05-04-016 Notification of GPRS Subscriber Present ............................31
II ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

2.37 ZWF-05-04-017 3G Authentication Function .................................................32

2.38 ZWF-05-05-001 SS7 Functions (ITU Type)...................................................33
2.39 ZWF-05-05-002 SCTP ..................................................................................34
2.40 ZWF-05-05-003 SS7 Performance Management ..........................................36
2.41 ZWF-05-05-004 Load Management ..............................................................36
2.42 ZWF-05-05-005 M3UA..................................................................................37
2.43 ZWF-05-05-006 Signaling Supervision..........................................................38
2.44 ZWF-05-06-001 HLR Operator Class Management ......................................38
2.45 ZWF-05-06-002 Log Maintenance ................................................................40
2.46 ZWF-05-06-003 Probe Function....................................................................40
2.47 ZWF-05-06-004 Report Function ..................................................................41
2.48 ZWF-05-06-005 Configuration Management .................................................42
2.49 ZWF-05-06-006 Fault Management ..............................................................42
2.50 ZWF-05-06-007 Performance And Traffic Statistics ......................................44
2.51 ZWF-05-06-008 Diagnostic Test ...................................................................44
2.52 ZWF-05-06-011 Software Management ........................................................45
2.53 ZWF-05-06-012 Clock Management .............................................................46
2.54 ZWF-05-06-013 HLR System Data Maintenance ..........................................46
2.55 ZWF-05-06-014 Dynamic Data Management ................................................47
2.56 ZWF-05-06-016 MML Administration Interface..............................................48
2.57 ZWF-05-06-017 GUI Function .......................................................................50
2.58 ZWF-05-07-001 Subscription Data Backup and Recovery ............................51
2.59 ZWF-05-07-002 Configuration Data Backup and Recovery...........................52
2.60 ZWF-05-07-003 HLR Hardware Backup .......................................................52
2.61 ZWF-05-07-004 HLR Overload Control .........................................................53
2.62 ZWF-05-07-005 Load Sharing of Signaling Link............................................54
2.63 ZWF-05-07-006 Multi-office-direction Load Sharing of Signaling Route ........55
2.64 ZWF-05-07-008 Encryption Key Management ..............................................56
2.65 ZWF-05-09-002 Clock Synchronization.........................................................56
3 Optional Features ..........................................................................................57

3.1 ZWF-05-10-001 Circuit Data Services...........................................................57
3.2 ZWF-05-10-002 Video Call ...........................................................................59
3.3 ZWF-05-10-003 Closed User Group (CUG) - Supplementary Services .........61
3.4 ZWF-05-10-004 Call Forwarding- Supplementary Services ..........................62
3.5 ZWF-05-10-005 Call Forwarding On Default .................................................65
3.6 ZWF-05-10-006 Line Identification (LI) Supplementary Services...................66
3.7 ZWF-05-10-007 Call Waiting (CW) – Supplementary Services .....................67
3.8 ZWF-05-10-008 Call Hold (CH) –Supplementary Services............................68
3.9 ZWF-05-10-009 Call Barring Supplementary Services (CB)..........................69
3.10 ZWF-05-10-010 MultiParTY (MPTY) -Supplementary Services.....................70
3.11 ZWF-05-10-011 Advice Of Charge (AOC) -Supplementary Services ............71
3.12 ZWF-05-10-012 Explicit Call Transfer (ECT) -Supplementary Services ........72
3.13 ZWF-05-10-013 Call Diversion (CD)- Supplementary Services .....................73
3.14 ZWF-05-10-014 EMLPP- Supplementary Services .......................................73
3.15 ZWF-05-10-015 Unstructured Supplementary Service Data (USSD) Phase 2
75
3.16 ZWF-05-10-016 Operator Determined Barring (ODB) Service ......................76
3.17 ZWF-05-10-017 Operator Determined Barring (ODB) for Packed Oriented
Services ..........................................................................................................78
3.18 ZWF-05-10-018 CAMEL3 Service.................................................................80
ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. III

3.19 ZWF-05-10-019 CAMEL4 Service.................................................................81

3.20 ZWF-05-10-020 LCS Service ........................................................................82
3.21 ZWF-05-10-021 Equal Access Service (Multiple Long Distance Carrier).......84
3.22 ZWF-05-10-022 Coloring Ring Back Tone (CRBT) Service...........................85
3.23 ZWF-05-10-023 Subscriber Category Service...............................................87
3.24 ZWF-05-10-024 Wireless Access Restrictions For Subscribers ....................88
3.25 ZWF-05-10-025 Access Of Subscriber Classes ............................................89
3.26 ZWF-05-10-026 IP Pre-setting Function........................................................90
3.27 ZWF-05-10-027 GPRS Charging Characteristics ..........................................91
3.28 ZWF-05-10-028 Regional Subscription Restriction (ZoneCode) Service .......93
3.29 ZWF-05-10-029 PLMN-specific Supplementary Service ...............................94
3.30 ZWF-05-10-030 OSB ....................................................................................94
3.31 ZWF-05-10-031 SMS Router ...........................................................................95
3.32 ZWF-05-10-032 Forward Number Format Transform Function .....................99
3.33 ZWF-05-10-033 STYPE(Support for Subscription Type Dependent Analysis in
HLR) ...............................................................................................................99
3.34 ZWF-05-10-034 HSCSD .............................................................................101
3.35 ZWF-05-10-035 CAMEL2 Service...............................................................102
3.36 ZWF-05-10-036 Barring of All Outgoing Calls when Roaming Outside HPLMN
Country (BORO) ...........................................................................................103
3.37 ZWF-05-10-037 CB Password under Subscriber Control ............................104
3.38 ZWF-05-10-038 CB Password under Operator Control ...............................104
3.39 ZWF-05-10-039 Authorized Calling Number Call to Incoming-barred
Subscriber.....................................................................................................104
3.40 ZWF-05-10-040 Fax Services .....................................................................105
3.41 ZWF-05-10-041 PLMN-specific Teleservice ................................................106
3.42 ZWF-05-10-042 Different Qos in different VPLMN ......................................107
3.43 ZWF-05-10-043 UMTS R99-CS Data Service -- Non-transparent (NT) Data
Service..........................................................................................................108
3.44 ZWF-05-10-044 SMS Alert Service (Miss Call) ...........................................109
3.45 ZWF-05-10-045 Black List and White List of Forward (OFA) ....................110
3.46 ZWF-05-10-046 Service Change and UDI/RDI Fallback (SCUDIF) .............111
3.47 ZWF-05-10-047 User-to-User Signaling (UUS) ...........................................112
3.48 ZWF-05-10-048 Operator Specific Barring ....................................................113
3.49 ZWF-05-10-049 Multimedia Coloring Ring Back Tone ................................114
3.50 ZWF-05-10-050 ADD (Auto Device Detect) ................................................115
3.51 ZWF-05-10-051 VBS ..................................................................................116
3.52 ZWF-05-10-052 VGCS ...............................................................................116
3.53 ZWF-05-10-053 HSDPA .............................................................................117
3.54 ZWF-05-10-054 HSUPA .............................................................................117
3.55 ZWF-05-10-055 TD-SCDMA Hand Over Function ......................................118
3.56 ZWF-05-10-056 2G/3G Roaming Mobility Managing Function ....................118
3.57 ZWF-05-10-057 CNAP................................................................................119
3.58 ZWF-05-10-058 Multicall .............................................................................119
3.59 ZWF-05-10-059 Selective Granting of Services on per VPLMN ..................120
3.60 ZWF-05-10-060 2G Softswitch Fax (Including CSD) Service Solution.........122
3.61 ZWF-05-10-061 RDI ...................................................................................122
3.62 ZWF-05-10-062 Multi-SIM...........................................................................123
3.63 ZWF-05-10-063 QoS Profile .......................................................................125
3.64 ZWF-05-10-064 ALS ...................................................................................125
3.65 ZWF-05-10-065 Authentication Gateway ....................................................128
IV ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

3.66 ZWF-05-10-066 SSET (Service Set) ...........................................................130

3.67 ZWF-05-10-067 HSDPA+ ...........................................................................131
3.68 ZWF-05-10-068 Welcome Message Service ...............................................131
3.69 ZWF-05-10-069 Short Message Forwarding ...............................................132
3.70 ZWF-05-10-070 Hot Bill ..............................................................................135
3.71 ZWF-05-10-072 CCBS................................................................................135
3.72 ZWF-05-10-073 Follow me .........................................................................138
3.73 ZWF-05-10-074 Optimized Late Call Forwarding ........................................139
3.74 ZWF-05-10-075 CDMA SIP function ...........................................................139
3.75 ZWF-05-11-001 Support for Subscriber Registration Profile Template ........140
3.76 ZWF-05-11-002 MTC ..................................................................................141
3.77 ZWF-05-11-003 Unilateral Halt ...................................................................142
3.78 ZWF-05-11-004 Configured Default NoReplyConditionTime ....................142
3.79 ZWF-05-11-005 Routing Category ..............................................................143
3.80 ZWF-05-11-006 Authentication Profile for 2G .............................................144
3.81 ZWF-05-11-007 Authentication Profile for 3G .............................................144
3.82 ZWF-05-11-008 Configurable Constant of Milenage Authentication Arithmetic
145
3.83 ZWF-05-11-009 Supporting Multiple OP/OPc .............................................146
3.84 ZWF-05-11-010 Dual IMSI ..........................................................................146
3.85 ZWF-05-12-001 Chinese Lawful Interception Function ...............................147
3.86 ZWF-05-12-002 ETSI Lawful Interception Function.....................................148
3.87 ZWF-05-12-003 Physical Interface -- FE/GE Interface Functions ................149
3.88 ZWF-05-12-004 Soap/XML Provisioning Interface ......................................149
3.89 ZWF-05-13-002 Subscriber Trace...............................................................150
3.90 ZWF-05-13-003 Any Time Interrogation (ATI) .............................................151
3.91 ZWF-05-13-004 Any Time Subscription Interrogation (ATSI) ......................151
3.92 ZWF-05-13-005 Any Time Modification (ATM) ............................................152
3.93 ZWF-05-13-006 Subscriber Data Modification Notification ..........................153
3.94 ZWF-05-13-008 Multi-number Function ......................................................153
3.95 ZWF-05-13-009 Long Forward-to Number ..................................................154
3.96 ZWF-05-13-011 SuperCharger ...................................................................155
3.97 ZWF-05-13-012 Pre-paging ........................................................................156
3.98 ZWF-05-13-013 Enhanced GPRS Support .................................................156
3.99 ZWF-05-13-014 SMS over GPRS ...............................................................157
3.100 ZWF-05-13-015 MAP Version Control.........................................................159
3.101 ZWF-05-13-016 Improvement of MAP Dialogue Between HLR and VLR ....159
3.102 ZWF-05-13-017 MAP with WHITE BOOK SCCP for Intra-PLMN Use .........160
3.103 ZWF-05-14-001 SS7 Functions (ANSI Type) ..............................................160
3.104 ZWF-05-14-002 ANSI Interfaces .................................................................163
3.105 ZWF-05-14-003 SUA ..................................................................................164
3.106 ZWF-05-14-004 M2PA ................................................................................164
3.107 ZWF-05-14-005 M2UA................................................................................165
3.108 ZWF-05-14-006 2M Signaling Link Supports Software ................................165
3.109 ZWF-05-14-007 Multi Signaling Point Function ...........................................166
3.110 ZWF-05-14-008 SCCP Screening ...............................................................167
3.111 ZWF-05-14-009 MTP Screening .................................................................168
3.112 ZWF-05-14-010 MAP Screening .................................................................169
3.113 ZWF-05-14-011 MTP Charging ...................................................................171
3.114 ZWF-05-14-012 SCCP Charging ................................................................172
3.115 ZWF-05-14-013 SCCP Load-Sharing Optimization .....................................173
ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. V

3.116 ZWF-05-14-014 SCCP Congestion Control ................................................173

3.117 ZWF-05-14-015 OMAP Functions ...............................................................174
3.118 ZWF-05-14-016 ASP-SG-ASP M3UA Application Function ........................175
3.119 ZWF-05-14-017 Coexistence of TDM and IP to One Office.........................176
3.120 ZWF-05-14-018 IPV4/IPV6 .........................................................................177
3.121 ZWF-05-14-019 Signaling Convergence Function.......................................177
3.122 ZWF-05-14-020 N*64K Signaling Link Supports Software ..........................178
3.123 ZWF-05-14-021 IP over E1/T1 ....................................................................178
3.124 ZWF-05-14-022 SCTP Multi-homing ...........................................................179
3.125 ZWF-05-14-023 SCCP GT Flexible Conversion Function ...........................179
3.126 ZWF-05-14-024 Signaling Monitor ..............................................................180
3.127 ZWF-05-14-025 Origin-based SCCP Routing .............................................180
3.128 ZWF-05-14-026 XUDT ................................................................................181
3.129 ZWF-05-14-027 ATM over E1/T1 ................................................................181
3.130 ZWF-05-14-028 Access Control Lists (ACLs) for IPv4 ................................182
3.131 ZWF-05-15-001 DBIO Log Function ...........................................................182
3.132 ZWF-05-15-002 Import/Export Tool ............................................................183
3.133 ZWF-05-15-003 HLR Service Observation ..................................................184
3.134 ZWF-05-15-004 Signaling Tracing ..............................................................184
3.135 ZWF-05-15-005 HLR/AUC Query Terminal.................................................185
3.136 ZWF-05-15-006 GT addressing according to CgPA and CdPA ...................185
3.137 ZWF-05-15-007 Automatic Change Over to New SIM Cards ......................186
3.138 ZWF-05-15-008 File Management ..............................................................186
3.139 ZWF-05-15-009 Pre-alarm Function ...........................................................187
3.140 ZWF-05-15-010 Statistic Function of Provisioning.......................................188
3.141 ZWF-05-15-011 Remote Client Function.....................................................188
3.142 ZWF-05-15-012 Telnet Function .................................................................189
3.143 ZWF-05-15-013 Alarm Forward ..................................................................189
3.144 ZWF-05-15-014 Statistic function of roaming subscribers ...........................190
3.145 ZWF-05-16-001 Querying Location information through OMM ....................190
3.146 ZWF-05-16-004 Redundancy HLR for Backup Multi-vendors' HLR .............191
3.147 ZWF-05-16-006 Redundant HLR Send RESET Message Time-sharing and
Regionally .....................................................................................................191
3.148 ZWF-05-17-001 Roaming Plan Customization ............................................192
3.149 ZWF-05-17-002 ODB Roaming Restriction .................................................193
3.150 ZWF-05-17-004 CAMEL: Roaming Subscriber Table..................................194
3.151 ZWF-05-17-005 Roaming Restrictions List of CC-NDC ...............................194
3.152 ZWF-05-17-007 CAMEL Compatibility Control ............................................195
3.153 ZWF-05-18-001 Length-variable NDC and Multiple NDCs Function ............196
3.154 ZWF-05-18-002 HLR’s Multi-MNC Function ................................................197
3.155 ZWF-05-18-003 Virtual HLR .......................................................................198
3.156 ZWF-05-18-004 HLR’s Support for Both 2G and 3G Subscribers ...............198
3.157 ZWF-05-18-007 Migration GSM Subscriber to UMTS Subscriber without
Changing SIM and MSISDN .........................................................................199
3.158 ZWF-05-18-008 MSISDN Assignment over NDC Boundaries .....................200
3.159 ZWF-05-18-010 Support of 3 Digits MNC ...................................................201
3.160 ZWF-05-18-012 MVNO (Network Sharing) .................................................201
3.161 ZWF-05-18-016 Multiple MCC ....................................................................205
3.162 ZWF-05-18-017 NTP Support .....................................................................206
3.163 ZWF-05-18-018 Network Identity and Time Zone .......................................206
VI ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

FIGURES
Figure 2-1 SIGTRAN protocol ............................................................................................ 35

Figure 2-2 BOSS interface ................................................................................................. 48
Figure 2-3 BOSS interface protocol ................................................................................... 49
Figure 2-4 Multi-SOCKET Connection ............................................................................... 50
Figure 3-1 New MT SM Delivery Message Flow in Transparent Mode ............................... 96
Figure 3-2 New MT SM Delivery Message Flow in Non-Transparent Mode ....................... 98
Figure 3-3 RDI function .................................................................................................... 123
Figure 3-4 Authentication Gateway service flow............................................................... 129
Figure 3-5 Basic forwarded MT-SMS functionality ........................................................... 133
Figure 3-6 A successful CCBS flow ................................................................................. 136
Figure 3-7 multiple core networks sharing common radio access network ....................... 202
Figure 3-8 Geographically split network using national roaming between operators......... 203
Figure 3-9 Geographically split shared radio networks scenarios with dedicated or common
core networks ..................................................................................................................... 203
Figure 3-10 Two different cases of common spectrum network sharing ........................... 204
Figure 3-11 Multiple radio access networks sharing common core network ..................... 205
ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. VII

1 Overview
This document is about the features of ZTE ZXUN USPP (HLR) system.
Here clarify that the basic features are the basic functions for the elements running, and
optional features are enhanced functions due to some operator’s demands. The basic
and optional features can be adjusted according to the operator’s demands. That means
some basic features can be optional ones, while some optional features can be basic
ones because the different requirements of different operators.
2 Basic Features
2.1 ZWF-05-01-001 SIM State Management

Specification: 3GPP TS 21.111 31.102 23.008
Implemented in: ZXUN USPP (HLR)
2.1.1 Summary
The SIM card state identifies whether the current MS/SIM card is available. The
following options are available for the SIM card state:
l Service activation
l Service halt report
l Loss report
l Defaulting
l Replication
This feature provides functions of adding, modifying and deleting SIM card state
subscription data.
2.1.2 Benefits
For operators
This feature provides operators with an effective means for management of subscribers’
SIM cards.
ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. 1

2.2 ZWF-05-01-002 Telephony Subscription

Specification: 3GPP TS 23.008 22.003
2.2.1 Summary
This feature provides a subscription for the Teleservice Telephony (TS11).
2.2.2 Benefits
For end-users
For a given mobile subscriber, it is available for the speech communication set-up in his
serving PLMN.
For Operators
Speech support is the main capability (sales object) offered by a GSM/UMTS operators.
2.2.3 Description
This feature provides a subscription for the Teleservice Telephony (TS11) in HLR.
This Teleservice provides the transmission of speech information and audible signaling
tones of the PSTN/ISDN.
In the PLMN and the fixed network processing technique appropriate for speech such as
analogue transmission, echo cancellation and low bit rate voice encoding may be used.
Hence, bit integrity is not assured.
l Transparency for telephone signaling tones is provided.
l Transparency for voice band facsimile signals is not mandatory
l Transparency for end to end speech encryption is not mandatory. If a user needs to
apply this technique an appropriate bearer service can be used.
l Transmission of DTMF is provided in the mobile to fixed direction (e.g. for

controlling voice mail boxes) during any time of an established call.
The subscription is included in the Permanent Subscriber Data for given subscriber.
2 ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

2.3 ZWF-05-01-003 R98 GPRS Service

Specification: ETSI 03.08 03.60
2.3.1 Summary
The GPRS system can be viewed as services expanded on the foundation of the
existing GSM circuit switched system for the purpose of meeting mobile subscribers’
requirements for access to the Internet or other packet data networks via packet data
mobile terminals. In UMTS, the core network (CN) consists of two parts: Circuit Switched
(CS) domain and Packet Switched (PS) domain. This network framework ensures
smooth evolution from the mobile communication network towards 2G/2.5G/3G.
HLR supports subscription of subscriber types with the network access modes of CS, PS
or both of them, thus adapting to various requirements of the end users.
2.3.2 Benefits
For Operators
With the PS network support feature of HLR, the CS and PS network management
functions can be supported in one HLR simultaneously. This saves operators’
investment in equipment.
For End-users
With the GPRS service feature, subscribers can roam on the Internet, send e-mails,
browse WWW, conduct e-business or implement remote monitoring at any time and
place free from limitation of the “network cable”. In addition, since the billing is based on
the traffic, subscribers can select to be online permanently without worrying about the
online duration.
2.3.3 Description
HLR provides the following categories of R98 GPRS-related subscription data:
PDP Context information:
Each group of PDP Context contains the following information:
PDP address type: Specifies the protocol type to be used in the MS for a certain service,
including IPV4, IPV6, x.25, PPP and OSP: IHOSS.
PDP address type: Includes the dynamic PDP address or static PDP address.

PDP address: Refers to the static PDP address.
AccessPointName: Is the external network access ID.
Whether allowing subscribers to use addresses dynamically allocated in VPLMN
The QoS (Quality of Service) contains:
Priority: Includes High Priority, Normal priority and Low priority.
Delay class: Includes 1-4.
Reliability class
Peak throughput class
Mean throughput class
PDP billing features
2.4 ZWF-05-01-004 2G Authentication Information

Management
Specification: ETSI 03.20 09.20
2.4.1 Summary
HLR and AUC are of the same physical entity. HLR/AUC supports authentication
information storage for 2G.
2.4.2 Benefits
For operators
In consideration of security, subscribers will be authenticated in cases of location

registration, call origination and short message sending during access to the
GSM/GPRS network. The system will reject access of any invalid subscriber.
2.4.3 Description
For 2G subscribers, the authentication information stored in HLR/AUC includes:

l IMSI: Is the subscriber’s IMSI number.
l Ki: Is the subscriber authentication key.
l Authentication algorithm: COMP128-1, COMP128-2, COMP128-3.
Ki stored in HLR is encrypted.
It is also encrypted before being transferred from the management center to HLR.
2.5 ZWF-05-01-005 Emergency Call

2.5.1 Summary
This feature provides a subscription for the Teleservice Telephony (TS12).
2.5.2 Benefits
For operators
This function enables operators to provide the emergency call services for Subscribers.
For end-users
This function allows a end-user to make an emergency call for help.
2.5.3 Description
Emergency call is a GSM specified teleservice allowing establishing calls to emergency

centers.
Emergency calls are characterized either by a specific key on the terminal, or by the
dialed number (112 in all countries as specified by GSM, plus possibly locally additional
numbers determined by the operator). Their processing differs from that of non-
emergency calls by the fact that:
All barring services are inhibited;
They are granted the highest level of priority in radio channel allocation.

They are routed to a centre determined according to the localization of the calling MS;
this is based on a translation mechanism of which the operator is free to determine the
parameters (which is also the case for some non emergency services).
2.6 ZWF-05-01-006 Short Message Services

2.6.1 Summary
This feature provides a subscription for the Short message MT/PP (TS21) and short
message MO/PP (TS22).
2.6.2 Benefits
For operators
This service can expand the traffic volume and increase the average revenue per user
(ARPU).
For end-users
This service diversifies the communication modes. It allows subscribers to keep contact
with others through short messages instead of speech.
2.6.3 Description
2.7 ZWF-05-01-007 3G Authentication Information

Management
Specification: 3GPP TS 32.102 43.020 35.205 29.002
2.7.1 Summary
HLR and AUC are of the same physical entity. HLR/AUC supports authentication
information storage for 3G.

2.7.2 Benefits
For operators
In consideration of security, subscribers will be authenticated in cases of location

registration, call origination and short message sending during access to the
GSM/GPRS network and WCDMA network. The system will reject access of any invalid
subscriber.
For end-users
In the UMTS system, the authentication is bidirectional, including both authentications

on subscribers by the system and on system by subscribers. The MS will reject to get
access to an invalid network, thus increasing subscribers’ security in network access.
2.7.3 Description
For 3G subscribers, the authentication information stored in HLR/AUC includes:
l IMSI: Is the subscriber’s IMSI number.
l Ki: Is the subscriber authentication key.
l Authentication algorithm: Is used to calculate the authentication vector.
l Authentication Management Field (AMF): Is a parameter input for the

authentication algorithm.
l Anonymity key ID: Identifies whether to encrypt the sequence number (SQN).
l Anonymity key ID available during re-synchronization: Identifies whether to encrypt

the sequence number (SQN) during authentication re-synchronization.
Ki stored in HLR is encrypted.
It is also encrypted before being transferred from the management center to HLR.
2.8 ZWF-05-01-008 R99 GPRS Service


2.8.1 Summary
The GPRS system can be viewed as services expanded on the foundation of the
existing GSM circuit switched system for the purpose of meeting mobile subscribers’
requirements for access to the Internet or other packet data networks via packet data
mobile terminals. In UMTS, the core network (CN) consists of two parts: Circuit Switched
(CS) domain and Packet Switched (PS) domain. This network framework ensures
smooth evolution from the mobile communication network towards 2G/2.5G/3G.
HLR supports subscription of subscriber types with the network access modes of CS, PS
or both of them, thus adapting to various requirements of the end-users.
2.8.2 Benefits
For operators
With the PS network support feature of HLR, the CS and PS network management
functions can be supported in one HLR simultaneously. This saves operators’
investment in equipment.
For end-users
With the GPRS service feature, subscribers can roam on the Internet, send e-mails,
browse WWW, conduct e-business or implement remote monitoring at any time and
place free from limitation of the “network cable”. In addition, since the billing is based on
the traffic, subscribers can select to be online permanently without worrying about the
online duration.
2.8.3 Description
HLR provides the following categories of R99 GPRS-related subscription data:
Default PDP billing features:
Including: Hot Billing, Flat Rate, Prepaid Service and Normal Billing. The default billing
features are subscription data only available for 3G subscribers.
PDP Context information:
Each group of PDP Context contains the following information:
PDP address type: Specifies the protocol type to be used in the MS for a certain service,
including IPV4, IPV6, x.25, PPP and OSP: IHOSS.
PDP address type: Includes the dynamic PDP address or static PDP address.
PDP address: Refers to the static PDP address.

AccessPointName: Is the external network access ID.
Whether allowing subscribers to use addresses dynamically allocated in VPLMN
The QoS (Quality of Service) contains:
Priority: Includes High Priority, Normal priority and Low priority.
Delay class: Includes 1-4.
Reliability class
Peak throughput class
Mean throughput class
Extended QoS: Is only available for 3G subscribers. The extended QoS contains the PS
assignment priority. This parameter is unavailable for 2G subscribers. The extended
QoS has the following options:
Traffic class: Includes Conversation class, Streaming class, Background class and
Interactive class.
Traffic handling priority
Transfer delay
Maximum bit rate for uplink
Guaranteed bit rate for uplink
Maximum bit rate for downlink
Guaranteed bit rate for downlink
Redundancy bit error rate
Service data unit error rate
Maximum service data unit length
Sending sequence: The options include sending sequence and no sending sequence.
Send error data: The options include send without check/send/not send.
PDP billing features

2.9 ZWF-05-02-001 Local Subscriber Data

Administration Function for 2G Subscriber
Specification:
2.9.1 Summary
HLR acts as the sole NE for centralized management of subscription data in the network.
One of its basic functions is subscriber service handling. The local subscriber data
administration function for subscribers refers to number allocation, number cancellation,
card renewal, number change and service data subscription etc. For subscribers via the
agent, this function is also responsible for maintenance and management of subscription
data.
2.9.2 Benefits
For operators:
This feature provides operators with an efficient means for subscription data
management.
2.9.3 Description
The local subscriber data administration of HLR provides the following sub-functions:
l Querying the subscriber registration profile list via the agent
l Querying the specific service function of a subscriber registration profile via the
agent
l Adding a subscriber registration profile via the agent
l Modifying a subscriber registration profile via the agent
l Deleting a subscriber registration profile via the agent
l SIM card information management
l Querying subscriber information via the agent
l Adding/deleting a single piece of authentication information via the agent
l Adding/deleting authentication information in batches via the agent

l Single number allocation via the agent
l Batch number allocation via the agent
l Deleting a single subscriber via the agent
l Deleting subscribers in batches via the agent
l Replacing a single SIM card via the agent
l Replacing SIM cards in batches via the agent
l Replacing a single basic number via the agent
l Replacing basic numbers in batches via the agent
l Subscribing for a single piece of subscriber service data via the agent
l Subscribing for subscriber service data in batches via the agent
l Querying a single piece of subscriber service data via the agent
l Querying subscriber service data in batches via the agent
l Modifying a single piece of subscriber service data via the agent
l Modifying subscriber service data in batches via the agent
l Synchronizing modified subscription data with the visited NE where the subscriber
is located
2.10 ZWF-05-02-003 Remote Subscriber Data

Administration Functions for 2G Subscriber
Specification:
2.10.1 Summary
HLR provides an open remote subscriber data administration interface so that the
customer care centre can access the HLR for subscription, modification and query of
each service of mobile subscribers. This facilitates operators’ secondary development of
the subscription data.

2.10.2 Benefits
For operators
Each customer care centre can conveniently access the HLR for maintenance and
management of the subscription data.
2.10.3 Description
The remote subscriber data administration of HLR includes the following sub-functions:
l Querying subscriber information via the remote interface
l Adding, modifying or deleting authentication information via the remote interface
l Subscriber registration via the remote interface
l Subscriber de-registration via the remote interface
l Service suspension via the remote interface
l Service restoration via the remote interface
l SIM card renewal via the remote interface
l Basic number renewal via the remote interface
l Subscription of subscriber service data via the remote interface
l Querying subscriber service data via the remote interface
l Modifying subscriber service data via the remote interface
l Querying available static IP addresses via the remote interface
l Querying subscriber registration profile ID list via the remote interface
l Querying subscriber registration profile data via the remote interface
2.11 ZWF-05-02-004 Local Subscriber Data

Administration Function for 3G Subscriber
Specification:

2.11.1 Summary
HLR acts as the sole NE for centralized management of subscription data in the network.
One of its basic functions is subscriber service handling. The local subscriber data
administration function for subscribers refers to number allocation, number cancellation,
card renewal, number change and service data subscription etc. For subscribers via the
agent, this function is also responsible for maintenance and management of subscription
data.
2.11.2 Benefits
For operators
management.
2.11.3 Description
The local subscriber data administration of HLR provides the following sub-functions:
l Querying the subscriber registration profile list via the agent
l Querying the specific service function of a subscriber registration profile via the
agent
l Adding a subscriber registration profile via the agent
l Modifying a subscriber registration profile via the agent
l Deleting a subscriber registration profile via the agent
l SIM card information management
l Querying subscriber information via the agent
l Adding/deleting a single piece of authentication information via the agent
l Adding/deleting authentication information in batches via the agent
l Single number allocation via the agent
l Batch number allocation via the agent
l Deleting a single subscriber via the agent
l Deleting subscribers in batches via the agent
l Replacing a single SIM card via the agent

l Replacing SIM cards in batches via the agent
l Replacing a single basic number via the agent
l Replacing basic numbers in batches via the agent
l Subscribing for a single piece of subscriber service data via the agent
l Subscribing for subscriber service data in batches via the agent
l Querying a single piece of subscriber service data via the agent
l Querying subscriber service data in batches via the agent
l Modifying a single piece of subscriber service data via the agent
l Modifying subscriber service data in batches via the agent
l Synchronizing modified subscription data with the visited NE where the subscriber
is located
2.12 ZWF-05-02-005 Subscription Profile

Specification:
2.12.1 Summary
ZXUN USPP (HLR) supports different subscription profiles such as GPRS and CSI
profile to simplify provisioning command.
2.12.2 Benefits
For operators
management.
It simplifies provisioning command and improves provisioning efficiency.
2.12.3 Description
ZXUN USPP (HLR) supports the following Subscription Profiles:
a) OCSI

b) TCSI
c) GPRS CSI
d) SMS CSI
e) UCSI
f) GPRS
2.13 ZWF-05-02-006 Remote Subscriber Data

Administration Functions for 3G subscriber
Specification:
2.13.1 Summary
HLR provides an open remote subscriber data administration interface so that the
customer care centre can access the HLR for subscription, modification and query of
each service of mobile subscribers. This facilitates operators’ secondary development of
the subscription data.
2.13.2 Benefits
For operators
Each customer care centre can conveniently access the HLR for maintenance and
management of the subscription data.
2.13.3 Description
The remote subscriber data administration of HLR includes the following sub-functions:
l Querying subscriber information via the remote interface
l Adding, modifying or deleting authentication information via the remote interface
l Subscriber registration via the remote interface
l Subscriber de-registration via the remote interface

l Service suspension via the remote interface
l Service restoration via the remote interface
l SIM card renewal via the remote interface
l Basic number renewal via the remote interface
l Subscription of subscriber service data via the remote interface
l Querying subscriber service data via the remote interface
l Modifying subscriber service data via the remote interface
l Querying available static IP addresses via the remote interface
l Querying subscriber registration profile ID list via the remote interface
l Querying subscriber registration profile data via the remote interface
2.14 ZWF-05-03-001 External Signaling Interfaces of

CS Domain
Specification:
2.14.1 Summary
HLR interacts with other NEs in the network through MAP interfaces. These MAP
interfaces include the C interface (peer entity being MSC), D interface (peer entity being
VLR) in CS domain.
2.14.2 Benefits
For operators
HLR can connect to MSC/VLR of CS domain to provide CS services.
2.14.3 Description
HLR supports complete MAP interfaces. It interacts with other NEs through these
standard interfaces to perform various service functions. HLR supports MAP versions at
all phases, including R4, R99, R98 and the previous MAP version.

The description of the specific service function performed by each interface is as follows:
C interface: Is the interface with GMSC/SMS-IW/GMSC. GMSC interacts with HLR

through this interface when requesting call routing. SMS-IW/GMSC interacts with HLR
through this interface when requesting short message routing.
D interface: Is the interface with VLR. HLR exchanges subscriber location information,
subscription information and current subscriber state with VLR through this interface.
During a call, VLR provides a roaming number for HLR through this interface.
2.15 ZWF-05-03-003 Physical Interface - E1

Interface Functions
Specification: ITU-T G.703
Ministry of Information Industry of the People’s Republic of China General Technical

Specifications for 900 MHz TDMA Digital Cellular Mobile Communications Equipment-
Switching Sub-System (SSS) Equipment
2.15.1 Summary
The system provides E1 interfaces for interconnection with other devices in the telecom
network.
2.15.2 Benefits
For operators
Operator can use E1 interface to interconnect with other devices in the telecom network.
2.15.3 Description
E1 is a universal digital transmission standard applied in Europe and China. This

standard provides an interface at the transmission rate of 2048Kb/s. The 2048Kb/s
bandwidth is divided into 32 time slots with each time slot occupying 64Kb/s. Time slot 0
is used to transmit frame synchronization signal and the other 31 time slots are used to
transmit signaling link and voice information etc. The 2048Kb/s interface (E1) provided in
ZXUN USPP (HLR) is compliant with the specifications in CCITT G.703.
To adapt to requirements in different regions, the system provides physical interfaces

supporting both 75Ω coaxial cables and 120Ω twisted pairs.

2.16 ZWF-05-03-004 Physical Interface - T1

Interface Functions
Specification: ITU-T G.703/704 ANSI T1 102/ANSI T1 107
2.16.1 Summary
The system provides T1 interfaces for interconnection with other devices in the telecom
network.
2.16.2 Benefits
For operators
Operator can use T1 interface to interconnect with other devices in the telecom network.
2.16.3 Description
T1 is a universal digital transmission standard applied in North America and Japan. This
standard provides an interface at the transmission rate of 1544Kb/s. Except the bits
used in synchronization and check, the remaining available bandwidth is 1536Kb/s,
which is divided into twenty-four 64Kb/s time slots for transmission of signaling link and
voice information etc. The 1544Kb/s interface (T1) provided in the ZXUN USPP (HLR)
system is compliant with the specifications in CCITT G703 (G.703). In addition, the
system provides physical interfaces using 100Ω twisted pairs.
2.17 ZWF-05-03-005 Gr Interface

2.17.1 Summary
HLR provides Gr Interface to interconnect with SGSN in PS domain.
2.17.2 Benefits
For operators
HLR can connect to SGSN of PS domain to provide PS services.

2.17.3 Description
Gr interface is the interface with SGSN. HLR exchanges the subscriber location
information, GPRS subscription information and current subscriber state with SGSN
through this interface.
2.18 ZWF-05-03-006 J Interface

2.18.1 Summary
HLR provides J Interface to interconnect with gsmSCF.
2.18.2 Benefits
For operators
HLR can connect to gsmSCF to provide Camel services.
2.18.3 Description
J interface is the interface with gsmSCF. For an intelligent service subscriber, gsmSCF
can query subscriber location information and state information or query or modify
subscription information through this interface at any time.
2.19 ZWF-05-03-007 Lh Interface

2.19.1 Summary
HLR provides Lh Interface to interconnect with GMLC.

2.19.2 Benefits
For operators
HLR can connect to GMLC to provide location related services.
2.19.3 Description
Lh interface is the interface with GMLC. Through this interface, GMLC can query the
number of a subscriber’s current located MSC/VLR or SGSN from HLR and locate this
subscriber.
2.20 ZWF-05-03-008 Gc Interface

2.20.1 Summary
HLR provides Gc Interface to interconnect with GGSN in PS domain.
2.20.2 Benefits
For operators
HLR can connect to GGSN of PS domain to provide PS services.
2.20.3 Description
Gc interface is the interface with GGSN. Its major purpose is to provide GPRS routing
information of subscribers during PDP reverse activation.
2.21 ZWF-05-04-001 2G Authentication Function

Specification: 3GPP TS 29.002, ETSI GSM 03.20

2.21.1 Summary
In terms of technology, wireless transmission risks easier interception and spoofing than
transmission over fixed lines. This feature prevents unauthorized users from accessing
the system and subscribers’ MS from accessing unauthorized networks by means of MS
authentication and encryption by the network, thus protecting subscribers’ privacy.
2.21.2 Benefits
For operators
Subscriber authentication by the network prevents invalid users from accessing the
network and avoids SIM card replication.
For end-users
Network authentication by subscribers prevents subscribers’ MS from accessing invalid

networks.
The data encryption and protection of subscription data consistency provided by the
wireless channel avoids invalid interception and damage of the subscription data during
transmission.
2.21.3 Description
Triplets for authentication and encryption purposes are generated in AUC. The
authentication process is as follows:
1 When VLR or SGSN requests authentication parameters from HLR, HLR requests
authentication parameter sets from AUC.
2 HLR sends triplets to VLR or SGSN. HLR can send a maximum of 5 groups of
authentication vectors at a time towards VLR or SGSN.
3 VLR or SGSN delivers authentication operations. For 2G subscribers, it will send a

random RAND to the MS.
4 MS sends the calculated number of responses SRES to VLR or SGSN.
5 In VLR or SGSN, the number of responses calculated in the MS is compared with

that calculated in AUC. If they are identical, it indicates that the corresponding
subscriber is valid.
HLR supports the following security authentication management functions:
l Supporting GSM/GPRS authentication flow

l Supporting 2G COMP128-1 algorithm
2.22 ZWF-05-04-002 CS Location Update Function

2.22.1 Summary
Due to the mobility of mobile subscribers, their locations are frequently changing. To
acquire MS location information for the call service, short message service,
supplementary services and positioning service, mobile subscribers are required to
register location information in the network and report their activation state (i.e., initiating
the location update service).
2.22.2 Benefits
For end-users
This feature provides the mobile and roaming functions so that subscribers can
communicate with any person at any time and place.
2.22.3 Description
When a subscriber roams and the location area (LA) changes, the MS actively initiates a
location update operation. If the previous and new LAs are subject to the same
MSC/VLR, the location update is quite simple: the information is modified in the VLR. If
they are subject to different MSC/VLRs, the new MSC/VLR will require HLR to provide
data of this MS. When sending the information required by the new MSC/VLR, HLR will
notify the previous MSC/VLR to delete the location information at the same time. In the
meantime, this MS will be registered in the new MSC/VLR and the number of the new
MSC/VLR will be registered in HLR. When the MS initiates location update to the new
MSC/VLR with TMSI and PLAI (Previous Location Area Identity), if the PLAI does not
exist in the new MSC/VLR, the new MSC/VLR can deduce the address of the previous
VLR (PVLR) based on TMSI and PLAI. Then, it can send a request for authentication to
PVLR and request PVLR to send the MS’s IMSI and authentication parameter sets not
used yet.

2.23 ZWF-05-04-003 Subscription Data Management

Functions
2.23.1 Summary
After a subscriber’s subscription information changes, HLR will actively initiate a

synchronization message so that the subscription data in VLR or SGSN are consistent
with those in HLR.
2.23.2 Benefits
For end-users
This feature ensures consistency of subscription data between HLR and VLR or SGSN
and normal trigger of service subscription by subscribers.
2.23.3 Description
The operations include subscription data insertion and deletion.
l Subscription data insertion
HLR will insert subscription data when subscribers’ subscription information is

added or modified.
l Subscription data deletion
HLR will delete subscription data when subscribers’ subscription information is deleted.
2.24 ZWF-05-04-004 Recovery Function

2.24.1 Summary
This feature ensures recovery and re-acquisition of subscription data in case of failure of
the VLR and HLR systems.

2.24.2 Benefits
For end-users
This feature ensures consistency of subscription data between HLR and VLR (or SGSN).
2.24.3 Description
l VLR reboot
The VLR system may stop working in case of failure or sudden power outage. The data
in VLR must be recovered after it is reboot. The following two recovery modes are
available:
i The call or short message operation etc. of a subscriber triggers the VLR
recovery operation. HLR sends data of this subscriber to VLR.
ii Location update of a subscriber triggers the recovery operation and “IMSI

attachment”.
l HLR reboot
After reboot, HLR will send RESET messages to all VLRs and SGSNs registered in
it before reboot. After receiving the messages, these VLRs and SGSNs will add an
“Uncertain” tag to subscription data subject to this HLR. Then, the VLRs and
SGSNs will perform location update to re-acquire the corresponding subscription
data whenever an MS sets up wireless connection.
2.25 ZWF-05-04-005 MS Deletion

2.25.1 Summary
Subscriber deletion is to delete subscriber records from SGSN/VLR/HLR, including both

the data deletion operation actively initiated by HLR and the data deletion notification
operation initiated by VLR (SGSN).
2.25.2 Benefits
For end-users
This feature increases the call completion ratio.

For operators
This feature reduces the network signaling and increases the call completion ratio and
customer satisfaction.
2.25.3 Description
When a subscriber roams to a new VLR (SGSN), HLR will initiate a subscriber deletion
operation towards the previous VLR (SGSN) to delete the subscription data in the
previous VLR (SGSN) after receiving a location update message from the new VLR
(SGSN). The HLR may also actively initiate the subscriber deletion operation when the
system administrator deletes this subscriber and the subscriber location information and
modify the SIM card properties via the OMC of the HLR.
If a subscriber does not perform any operation in a long period of time (set by the
system administrator flexibly; generally 24 hours) or the system administrator requires
deleting invalid subscriber records in VLR (SGSN) via the OMC, the VLR (SGSN) will
delete the corresponding subscription data and notify HLR.
2.26 ZWF-05-04-006 MS Purging Function

2.26.1 Summary
The VLR or SGSN may call the MS Purging function to notify HLR of the information that
the corresponding subscriber has been deleted in VLR or SGSN.
2.26.2 Benefits
For operators
HLR can process purge message from VLR or SGSN.
2.26.3 Description
The VLR or SGSN may call the MS Purging function in the following two conditions:
A subscriber does not perform any operation in a long period of time.

It is required to delete a subscriber with the corresponding command in some cases.
After receiving a Purging message from the VLR or SGSN, HLR sets the corresponding
subscriber in the database as “Unreachable”. Then, for any incoming call or call
termination short messages aimed at this subscriber, HLR will return a message that the
subscriber is absent.
2.27 ZWF-05-04-007 IMSI Query Based on MSISDN

2.27.1 Summary
In VLR OMC, a subscriber’s IMSI can be queried according to the subscriber’s MSISDN.
If no IMSI information is available for this subscriber in VLR, VLR will initiate a request
towards HLR for query of this subscriber’s IMSI.
2.27.2 Benefits
For operators
This feature facilitates query of operation and maintenance information.
2.27.3 Description
In VLR OMC, a subscriber’s IMSI can be queried according to the subscriber’s MSISDN.
VLR sends a message requesting IMSI to HLR. This message contains the subscriber’s
MSISDN. HLR will acquire the IMSI number based on the subscriber’s MSISDN and
send a reply message containing the subscriber’s IMSI to VLR.
2.28 ZWF-05-04-008 Mobile Terminated Call

2.28.1 Summary
This feature provides the call flow when a mobile subscriber serves as the called party.

2.28.2 Benefits
For end-users
This feature enables subscribers to receive calls in any roaming area.
2.28.3 Description
The call setup process when a mobile subscriber acts as the called party consists of two
parts: from the call origination point to the query initiation point and from the query point
to the called party.
When the called party is a mobile subscriber, the MSC that the caller is subject to will
first find the HLR of the called party and request it to provide routing information of the
called party. The HLR will request the roaming number from the VLR that the called
party is located. The VLR will allocate a roaming number to the called party and then
send it to the MSC where the caller is located. The MSC of the caller will set up a link
with the called party based on this roaming number.
In HLR, the call termination routing function is also used to further check the subscriber’s
service subscription and whether incoming call barring is activated.
2.29 ZWF-05-04-009 Supplementary Service

Operations
Specification: 3GPP TS 29.002 23.081 23.082 23.083 23.088
2.29.1 Summary
This feature involves operations like supplementary service subscription, registration,

deletion, activation, deactivation, query and password registration.
2.29.2 Benefits
For end-users
This feature provides end-users with the function of setting supplementary services via
the man-machine interface.

2.29.3 Description
In HLR, supplementary service registration/de-registration can only be performed by

operators via the service handling system instead of by mobile subscribers via their MSs.
In HLR, the supplementary service operations available on the MS include:
Supplementary service registration
Supplementary service deletion
Supplementary service activation
Supplementary service deactivation
Supplementary service query
Supplementary service password verification
2.30 ZWF-05-04-010 Short Message Routing

2.30.1 Summary
This feature enables the SMC (Short Message Center) to send a short message to a
subscriber after acquiring the subscriber’s routing information (VLR number/SGSN
number) from HLR and the subscriber’s current location.
2.30.2 Benefits
For end-users
This feature enables subscribers to receive short messages in any roaming areas.
2.30.3 Description
IW/GMSC sends a message to HLR, requesting the short message routing information.
HLR sends a reply message carrying the routing information (i.e., the MSC/VLR/SGSN
number).

2.31 ZWF-05-04-011 Short Message Delivery State

Report
2.31.1 Summary
This feature enables the SMC to report the result of short message delivery failure or
success to HLR. The related short message delivery state data are recorded in HLR.
2.31.2 Benefits
For end-users
This feature ensures that no short message is lost for subscribers under any
circumstances.
2.31.3 Description
IW/GMSC reports the result of short message delivery success or failure to HLR. HLR
modifies the flag bit of short message delivery state and returns a reply message.
2.32 ZWF-05-04-012 Short Message Alert Service

2.32.1 Summary
This feature reminds the SMS to re-send a short message when the target receiver is
able to receive it.
2.32.2 Benefits
For end-users
This feature enables the network to detect the subscriber state in time and send short
messages to them when they are reachable.

2.32.3 Description
When it is impossible to send a short message to a subscriber because this subscriber

is unreachable or the MS memory is used up, the address of the SMC where short
message delivery fails will be recorded in HLR. When the subscriber is reachable or
there is sufficient space in the MS memory, VLR will remind HLR and HLR will send an
Alert to IW/GMSC. Then, the SMC will send the short message to this subscriber again.
2.33 ZWF-05-04-013 PS Location Update

Specification: 3GPP 29.002 23.060 27.060 29.016 29.018 29.061
2.33.1 Summary
Due to the mobility of mobile subscribers, their locations are frequently changing. To
facilitate acquisition of mobile subscribers’ location information during GPRS data
service processing and increase the effective utilization ratio of the wireless resources,
mobile subscribers are required to register location information in the network and report
their activation state (i.e., initiating the location update service).
2.33.2 Benefits
For end-users
This feature provides the mobile and roaming functions so that subscribers can
communicate with any person at any time and place.
2.33.3 Description
SGSN initiates location update towards HLR. The flow is similar to the VLR update.
When the SGSN address received by HLR is inconsistent with the previous one, HLR
will initiate the location deletion service towards the previous SGSN.
2.34 ZWF-05-04-014 GPRS Routing Function

Specification: 3GPP TS 29.002 23.060 27.060 29.016 29.018 29.061

2.34.1 Summary
GGSN initiates a routing request towards HLR to request subscribers’ GPRS routing
information.
2.34.2 Benefits
For operators
HLR can provide GPRS Routing Function for PS domain.
2.34.3 Description
During reverse PDP activation, GGSN initiates a routing request towards HLR to acquire
the corresponding subscriber’s current located SGSN Number.
2.35 ZWF-05-04-015 GPRS Failure Report

2.35.1 Summary
In case of reverse PDP activation failure, GGSN notifies HLR of the GGSN number and
address with this signaling flow.
2.35.2 Description
In case the reverse PDP context activation fails, GGSN notifies HLR of the information
with this service. After receiving the failure report from GGSN, HLR will set the
corresponding subscriber as “GPRS unreachable” and save the GGSN number and
address (if available) carried in the failure report request.
2.36 ZWF-05-04-016 Notification of GPRS

Subscriber Present

2.36.1 Summary
This feature is used to support a subscriber’s data services during reverse activation at
the network.
2.36.2 Description
After receiving the Ready for SM message or during location update of a subscriber
whose GPRS unreachable flag is reset, HLR initiates a message to notify GGSN that the
subscriber is currently Present.
2.37 ZWF-05-04-017 3G Authentication Function

Specification: 3GPP TS 33.102 35.201 35.202 35.203 35.204 29.002,
ETSI GSM 03.20
2.37.1 Summary
In terms of technology, wireless transmission risks easier interception and spoofing than
transmission over fixed lines. This feature prevents unauthorized users from accessing
the system and subscribers’ MS from accessing unauthorized networks by means of MS
authentication and encryption by the network, thus protecting subscribers’ privacy.
2.37.2 Benefits
For operators
Subscriber authentication by the network prevents invalid users from accessing the
network and avoids USIM card replication.
For end-users
Network authentication by subscribers prevents subscribers’ MS from accessing invalid

networks.
The data encryption and protection of subscription data consistency provided by the
wireless channel avoids invalid interception and damage of the subscription data during
transmission.

2.37.3 Description
5-tuples for authentication and encryption purposes are generated in AUC. The
authentication process is as follows:
6 When VLR or SGSN requests authentication parameters from HLR, HLR requests
authentication parameter sets from AUC.
7 HLR sends 5-tuples to VLR or SGSN. HLR can send a maximum of 5 groups of
authentication vectors at a time towards VLR or SGSN.
8 VLR or SGSN delivers authentication operations. For 3G subscribers, it will send a

random RAND and authentication token AUTN to the MS.
9 MS sends the calculated number of responses SRES to VLR or SGSN.
10 In VLR or SGSN, the number of responses calculated in the MS is compared with

that calculated in AUC. If they are identical, it indicates that the corresponding
subscriber is valid.
HLR supports the following security authentication management functions:
l Supporting CS/PS authentication flow;
l Supporting WCDMA authentication flow;
l Supporting WCDMA authentication algorithms: milenage and XOR;
l Supporting conversion of 5-tuples to triplets.
2.38 ZWF-05-05-001 SS7 Functions (ITU Type)

Specification:
2.38.1 Summary
This feature provides a standardized general purpose No.7 Common Channel Signaling
System that meets all requirements for call control signaling applications. It satisfies ITU-
T recommendations, ETSI standards and optionally, Chinese (MPT) or Japanese (TTC)
national standards.

2.38.2 Description
The SS7 ITU type consists of the following parts:
MTP (Message Transfer Part): Consists of level 1, 2 and 3 of the SS7 system, which
correspond to the data link layer, signaling link layer and network layer respectively.
Signaling Connection Control Part (SCCP): Belongs to the user part and performs the
4th class of functions in the SS7 mode hierarchy. This part also provides MTP with
additional functions to transfer circuit-related or circuit-irrelevant information and other
types of information and set up connectionless or connection-oriented services between
the central office and dedicated center in the telecom network via the SS7 network.
SCCP and MTP constitute the Network Service Part (NSP) to meet the requirements as
defined for L3 (network layer) in the OSI reference model.
TC (Transaction Capability): Is the uniform protocol applied in transmission of circuit-

irrelevant messages. The process and message structure of this protocol are irrelevant
to the specific applications. TC consists of two parts: Transaction Capability Application
Part (TCAP) and Intermediate Service Part (ISP). Here the functions of TCAP
correspond to L7 in the OSI reference model; ISP provides L4 to L6 functions in OSI.
Aimed at different requirements, two TC structures are available: connection-oriented
and connectionless.
2.39 ZWF-05-05-002 SCTP

Specification: IETF: RFC2960
2.39.1 Summary
Transmission layer of SIGTRAN protocol
2.39.2 Benefits
SCTP is the standard IP transmission protocol, satisfying the unique transmission

demand of SCN signaling by increasing its own function: Congest control, better real
time, Multi-homing etc.
2.39.3 Description
SIGTRAN is composed of two layers: transmission layer and UA layer. Transmission

layer protocol provides a reliable message packet transmission on IP network via
Stream Control Transmission Protocol SCTP. While UA layer performs the adaptation of
each protocol in SCN signaling protocol hierarchical model, and is responsible for inter-

layer primitive transmission between the two protocols lying in SCN and IP respectively.
SIGTRAN stack protocol is shown in the Fig. below.
Figure 2-1 SIGTRAN protocol
SCCP SUA
MTP3/b M3UA
M2UA M2PA
SCTP
IP
SCTP mainly serves as the signaling bearer in IP network. It enables the signaling
message to implement the exchange, end-to-end executive traffic control and error
control on public packet switching network based on IP.
SCTP is mainly composed of the following functions:
Management of connection status and data transceiver can be divided into connection
establishing and dismantling, data transceiver handling and the connection management
and control.
The establishing and dismantling of connection include the handling of connection status
changes and handling of the abnormity.
The transmission part of data transceiver handling mainly accomplishes the receiving
and fragment of subscriber application data, buffers the data distribution, sends data
according to the current network congestion status and opposite receiving buffer status
and suspends it in the waiting confirmation queue, sets waiting timeout timing and
prepares for the measurement of Round-Trip Time (RTT). While the reception part
mainly accomplishes the buffer, restore and confirmation generation of the fragmented
data and data out of sequence sends the restored data the subscriber application
protocol. Notably, a continuously data transceiver handling is controlled by the
connection status and other control information, which are stored in the control block of
the connection and change with the operations of other function module.

The congestion control and window management in connection management and

control part implement the management to the slide-window. The entire control
mechanism for the accelerating, decelerating, slow boot and congestion is triggered by
the information carried in the opposite selection confirmation and the transmission of
timeout message, etc, during which, the output of those messages and information
affects the control information of congestion window, reception window, slow boot
threshold value and round-trip timeout timing in the connection control block.
The path management mainly implements the accessibility detection (HeartBeat) to

multiple paths of the connection, corresponding information report subscriber application
protocol and converts the main path according to the instruction.
2.40 ZWF-05-05-003 SS7 Performance Management

Specification: ANSI
2.40.1 Summary
SS7 Performance management refers to the activities of measuring the performance of

SS7.
2.40.2 Benefits
For operators:
The Feature Statistics and Traffic Measurement for SS7 network provides the operator
staff with more detailed statistics on the signaling system network.
2.40.3 Description
The feature provides Signaling Network Management, Traffic Handling and Signaling
Link Management information. This can be used to improve the total performance of the
signaling network.
2.41 ZWF-05-05-004 Load Management

Specification: CCITT

2.41.1 Summary
This object meets a very basic level of CCITT Blue Book E.411 412 functionality,
providing both information and control functions.
Network status and alarm information:
l exchange availability
l processor and exchange input load status
l route availability
l route load status
l processor load control
2.42 ZWF-05-05-005 M3UA

2.42.1 Summary
One of SIGTRAN UA layers, adaptation function of MTP3 subscriber
2.42.2 Benefits
For operators
SIGRTRAN stack protocol supports the transmission of SCN signaling protocol via IP
network. It supports the inter-layer standard primitive interface in the definition of SCN
signaling protocol hierarchical model, so as to guarantee the use of existing SCN
signaling application without any updating and simultaneously.
2.42.3 Description
l Support for the transfer of SCCP messages;
l Support for the seamless operation of SCCP protocol peers;

l Support for the management of SCTP transport associations and traffic between an
SG and one or more MGCs or IP-resident Databases;
l Support for MGC or IP-resident Database process failover and load sharing;
l Support for the asynchronous reporting of status changes to management.
In simplistic transport terms, the SG will terminate SS7 MTP2 and MTP3 protocol layers
and deliver SCCP protocol messages, as well as certain MTP network management
events, over SCTP transport associations to SCCP peers in MGCs or IP-resident
Databases.
2.43 ZWF-05-05-006 Signaling Supervision

Specification:
2.43.1 Summary
The supervision tool provides the event report and alarm output function for network
operators.
2.43.2 Benefits
For operators
Upon network congestion, error or failure, the supervision tool will timely prompt the
network operator to carry out proper handling to ensure reliable and stable operation of
the signaling network.
2.43.3 Description
The contents to be reported include events, date, time and other related information.
An alarm message may be generated in the following cases:
Association failure, link failure, link congestion, route unavailable, adjacent office not
reachable, subsystem unavailable, etc.
2.44 ZWF-05-06-001 HLR Operator Class

Management
Specification:

2.44.1 Summary
This function provides management of OMM maintenance authorities and subscription

data operation authorities. HLR provides the function of operator class management so
that different classes of operators have different operation authorities. This restricts
unauthorized and error operations, increases the system security and ensures
completeness of the subscription data.
2.44.2 Benefits
For operators
This feature increases the system security.
For end-users
This feature ensures the completeness and security of subscription data.
2.44.3 Description
The authority management function is used to manage operators’ operation authorities.

It can be used to set different operation authorities for different users for the
corresponding operations and maintenance of the system. In the authority management
function, operators are divided into different authorities groups and operators within the
same authority group are provided with the same authorities.
This function is used in management of authority groups and operators. An authority

group is a collection of some authorities. Each operator is subject to a specific authority
group and is provided with all authorities as defined in this authority group.
The operator class management function includes the following sub-functions:
Adding, modifying or deleting an authority group
Assigning the corresponding authorities to an authority group
Renaming an authority group
Adding a new user into an authority group so that this user can have the corresponding
authorities defined in this authority group
Modifying a user’s properties, such as the user name, full name, description, password
and superior authority group
Pausing or recovering a user’s authorities

Allowing valid user login and use of the system
Restricting invalid user login
Preventing any login password from being displayed on the screen
2.45 ZWF-05-06-002 Log Maintenance

Specification:
2.45.1 Summary
The HLR log maintenance function is used to record in details the system running state
and operations conducted by operators to facilitate system maintenance and
management.
2.45.2 Benefits
For operators
Operators are provided with a convenient tool for system management.
2.45.3 Description
The HLR log is divided into two categories: service handling/operation log and system
log.
The service handling/operation log records all operations made by the service handling
persons/operators. Here, the accurate and detailed information of all operations
conducted by operators is recorded, including the operation duration, involved functional
modules, operators, operation terminal IDs, operation state (successful or failed) and the
contents of all operation events. The log can be filtered or displayed according to the
operator name, operation terminal, functional module and operation duration.
The system log records the system running state.
2.46 ZWF-05-06-003 Probe Function

Specification:

2.46.1 Summary
The probe function is used to observe the configuration data in the MP memory
database in real time.
2.46.2 Benefits
For operators
2.46.3 Description
The memory database in the switching system’s module processor serves as the data
management center of the mobile switching system, which provides data for each
application in the software of the switching system. The probe program is used to
observe data in the foreground database in real time.
2.47 ZWF-05-06-004 Report Function

Specification:
2.47.1 Summary
Operators can customize query conditions and fields concerned to query and generate
reports of switching system configuration data.
2.47.2 Benefits
For operators
2.47.3 Description
This feature supports query and generation of reports of switching system configuration
data based on the customized query conditions and fields concerned. The query results
can be displayed either in the text or table format. They can also be saved as files. In
addition, the function of driving the printer for report print is also provided.

2.48 ZWF-05-06-005 Configuration Management

Specification:
2.48.1 Summary
The major purposes of HLR configuration and management are to configure and
manage various resources of the HLR NE and provide functions for creating, deleting
and modifying each configuration item of the HLR NE. The major configuration items
include:
Physical configuration
Logic function configuration
HLR system parameter configuration
The related tools for data transfer and data backup/recovery are also provided.
2.48.2 Benefits
For operators
2.48.3 Description
The major functions of HLR configuration and management are as follows:
Physical configuration: Adds, deletes or browses physical and logic resources in the
configured central office, e.g., adding or deleting a module, rack, shelf or circuit board
etc.
Logic function configuration: Configures signaling data, e.g., local office configuration,
signaling point configuration and adjacent office configuration etc.
HLR system parameter configuration: Configures system parameters needed in service

processing, e.g., office characteristic data configuration, virtual HLR data segment
configuration and configuration of services supported in HLR etc.
2.49 ZWF-05-06-006 Fault Management

Specification:

2.49.1 Summary
The major purpose of fault management is to display alarms and notifications so as to

provide operators with detailed fault information and enable users to understand the
current system state clearly at any time and locate any possible problem of the system.
2.49.2 Benefits
For operators
2.49.3 Description
In terms of severity, alarms can be divided into four levels, in which level 1 is the most
critical while level 4 is the least critical.
In terms of types, alarms can be divided into equipment, communication, service and
processor alarms. An alarm will be generated when a fault occurs and disappears when
it is recovered or the fault conditions do not exist anymore.
Notifications are messages reported when any events that need to be made known to
operators occur. They do not necessarily mean any fault. A notification needs not to be
recovered.
Fault management consists four functional parts: real-time display of current alarms and
notifications, alarm management and query, man-machine command and alarm box.
Real-time display of current alarms and notifications: All current alarms that have not
been recovered are displayed in real time in the current alarm list for users. Alarm
information includes the alarm source, alarm level, alarm generation time, alarm
contents, alarm cause, alarm type and additional information. All received notifications
are serially displayed in real time in the notification list. Notification information includes
the notification generation time, source, notification contents and additional information
etc.
Alarm management and query: Alarm management includes environment alarm

parameter setting, alarm knowledge base management, alarm filter rules and re-
classification rule management. Alarm query includes query of the history alarms and
notifications, for which query conditions can be set.
Man-machine command: With this function, operators can conduct some operations and
control over managed objects, including reset, switchover, offline setting, offline setting
removal, periodic switchover and clock configuration etc.

Alarm box: Reminds operators of existence of the current alarms and their levels in a
visible and audible way.
2.50 ZWF-05-06-007 Performance And Traffic

Statistics
Specification:
2.50.1 Summary
By means of measurement and statistics of some performance parameters and traffic

data in the system, this function is used to reflect the mobile system’s performance
indexes for references by business operation parties.
2.50.2 Benefits
For operators
2.50.3 Description
HLR provides various traffic statistics functions. It supports traffic statistics based on
“standard MAP operations” and “CPU seizure ratio” etc. Users can customize their
statistics items as needed.
Performance management provides the QoS performance monitoring function: an alarm

is generated when a certain measurement data item reaches the threshold.
Performance management also provides functions like performance query, performance

analysis, report print, real-time observation and performance data backup.
2.51 ZWF-05-06-008 Diagnostic Test

Specification:

2.51.1 Summary
The diagnostic test provides routine test and instant test for system equipment to ensure
normal and stable running of the entire system.
2.51.2 Benefits
For operators
2.51.3 Description
During daily maintenance, the diagnostic test enables users to check the physical
equipment and communication links through routine test. When the test result is close to
the abnormal value, engineering personnel may be reminded of the case so as to detect
any hidden trouble and take the appropriate measures before a fault occurs to avoid
occurrence of a fault.
When a fault occurs, the diagnostic test helps the engineering personnel to find the
cause of the fault and precisely locate the fault through instant test so as to remove the
fault as quickly as possible.
After removal of a fault, engineering personnel can also determine whether the
equipment has returned to normal running and whether the entire system is running
normally through diagnostic test.
2.52 ZWF-05-06-011 Software Management

Specification:
2.52.1 Summary
It provides a convenient tool to manage software version.
2.52.2 Benefits
For operators

2.52.3 Description
The software management provides the uploading management of the software which
running on each board of the system, and enables the querying of relevant information
including version number and version type used on each board.
2.53 ZWF-05-06-012 Clock Management

Specification:
2.53.1 Summary
It provides a convenient tool to manage clock.
2.53.2 Benefits
For operators
2.53.3 Description
The Clock management includes the following functions:
l System timer management: timer query, timer duration modification, etc;
l System clock manager: system clock query, modification, etc.
2.54 ZWF-05-06-013 HLR System Data Maintenance

Specification:
2.54.1 Summary
The system data maintenance function is used for backup and recovery of system data.
2.54.2 Benefits
For operators

2.54.3 Description
Either data of a single module or data of the entire system can be backed up and
recovered. In addition, a detailed record is provided for the backup and recovery process
in the log form.
Its sub-functions include:
Backing up data of the entire system
Backing up alarm data
Recovering alarm data
Backing up performance data
Recovering performance data
Backing up configuration data
Recovering configuration data
Backing up variable data in variable management
Recovering variable data in variable management
2.55 ZWF-05-06-014 Dynamic Data Management

Specification:
2.55.1 Summary
Dynamic Data Management provides resource data state and SS7 management
interface.
2.55.2 Benefits
For operators

2.55.3 Description
Maintenance and management are provided for dynamic data such as the resource data
state in each module of the switching system.
SS7 management interface: Provides such management functions like signaling link
activation, deactivation, block and unblock, and link state view. It also provides self-loop
and self-loop removal functions for signaling links.
2.56 ZWF-05-06-016 MML Administration Interface

Specification:
2.56.1 Summary
HLR Innovation has been designed to handle a large number of subscribers. Therefore
fast, efficient and state-of-the-art subscriber administration is a key requirement. The
MML Administration Interface fulfils this requirement and provides the following functions:
Authenticating and authorizing clients access the HLR/AUC system via the MML
interface, subsequently:
Perform HLR and AUC mobile subscriber administration:
Basic administrations (create, read, modify, and delete HLR & AUC data);
Support for managing one or more subscribers' data.
2.56.2 Description
The ZXUN USPP (HLR) system provides an open interface for the superior NM Center,
which enables BOSS system to access ZTE HLR system to execute subscription,
modification and query of MS subscription information. The communication protocol
between HLR system and BOSS system is named as HB protocol for short.
The networking structure between ZXUN USPP (HLR) system and BOSS system is
shown in Figure 2-2:
Figure 2-2 BOSS interface

The protocol stack between ZXUN USPP (HLR) system and BOSS system is composed
of three layers: HB interface protocol, TCP/IP protocol and physical connection. The
physical connection is the bottom layer, upon which the TCP/IP protocol is based and
HB interface protocol is the top layer, as is shown in Figure 2-3:
Figure 2-3 BOSS interface protocol
The HB Interface Protocol will be illustrated in the following.
For easy understanding, HLR interface processor and BOSS interface processor will be
used to replace ZXUN USPP (HLR) system and BOSS system.
BOSS interface processor has to establish SOCKET connection based on TCP/IP

protocol with HLR interface processor before it can send messages to HLR interface
processor.

11 BOSS interface processor connects to HLR interface processor by SOCKET. One

BOSS interface processor can establish one or more connections with HLR
interface processors on specified IP address.
12 HLR interface processor listens to connection at the assigned port, and

authenticates IP address of BOSS interface processor. If BOSS IP address can’t be
configured by HLR interface processor according to communication configuration
list, HLR interface processor will reject the BOSS to establish connection.
13 HLR interface processor does not send connection request to BOSS interface
processor actively.
Figure 2-4 is a sketch diagram of multi-SOCKET connection:
Figure 2-4 Multi-SOCKET Connection
2.57 ZWF-05-06-017 GUI Function

Specification: 3GPP TS: 32.
2.57.1 Summary:
The GUI function provides graphic user interface for operation and maintenance.
2.57.2 Benefits:
Friendly interface, easy operation
Direct data display, easy to be understood.

2.57.3 Description:
The O&M functions use Client-Server architecture. The client uses graphic user interface
to realize Fault Management, Performance Management, and Configuration
Management etc.
2.58 ZWF-05-07-001 Subscription Data Backup and

Recovery
Specification:
2.58.1 Summary
HLR is the central database for mobile subscribers’ subscription information.

Subscription data backup and recovery are important means ensuring subscription data
security.
2.58.2 Benefits
For operators
Operators are provided with high-reliability equipment.
For end-users
This feature reduces the loss of subscription data to the minimum level in case a fault
occurs.
2.58.3 Description
ZXUN USPP (HLR) provides two modes for subscription data backup: manual backup
and automatic backup.
l With manual backup, operators can backup subscription data with the database
backup tool provided by the database.
l Automatic backup is made possible by setting timing tasks. With timing task
customization, the system can start data backup automatically at the specified time.
The typical mode is automatic data backup by HLR once a day.
During data backup, the backed up data may be saved to either the local or another
medium depending on the actual needs.

In case of subscription data loss or damage due to a fault or disaster, the data recovery
function provided by ZXUN USPP (HLR) can be used to recover the previously backed
up data and reduce the operators’ loss to the minimum level.
Flexible and diversified data backup modes are available. The operations are simple and
the recovery process is very convenient. This function provides powerful guarantee for
security of the subscription data.
2.59 ZWF-05-07-002 Configuration Data Backup and

Recovery
Specification:
2.59.1 Summary
This feature provides the function for backup and recovery of configuration data in the
background database.
2.59.2 Benefits
For operators
Operators can recover system to normal quickly with previous data when configuration
data is configured wrong.
2.59.3 Description
The configuration data in the background database can be backed up as files in either
the SQL or BCP mode.
The configuration data backed up in files can be recovered to the background database.
The configuration data in the background database can be saved as the data files of the
corresponding data tables in the switching system’s foreground database.
2.60 ZWF-05-07-003 HLR Hardware Backup

Specification:

2.60.1 Summary
The key hardware components of HLR work in the 1+1 redundancy hot backup mode
without any single point. This high-reliability mode increases the stability of the entire
system.
2.60.2 Benefits
For operators
2.60.3 Description
Some components in the system such as the processor, board and server are all
executors of service processing. When a fault occurs, the service processing of the
entire system will be abnormal. To ensure high reliability and availability of the system,
all major boards (signaling board, power board, network board and communication
board) are all working in the 1+1 backup mode. When any major component fails, the
service processing will be automatically switched to the standby component. For the
HLR subscription database component, the CLUSTER technology is adopted to provide
1+1 backup. This enhances the security of the subscription data.
2.61 ZWF-05-07-004 HLR Overload Control

Specification:
2.61.1 Summary
HLR supports traffic control function.
2.61.2 Benefits
For operators

2.61.3 Description
HLR supports traffic control, which ensures stability of the system under high load.
When the system load reaches a certain point, HLR will restrict incoming messages to
avoid any harm caused by bursty high load and ensures the system security and stability.
HLR overload control involves multiple control layers, which are SS7 traffic control, MAP
layer traffic control and other external traffic control (e.g., traffic at the service handling
interface).
HLR overload control provides 6 levels of different control thresholds and allows
adjustment of these control thresholds according to the actual running conditions.
2.62 ZWF-05-07-005 Load Sharing of Signaling Link

Specification: ITU-T Q. 704
Communications industry standards in China: Technical Specifications for SS7 Signaling

Mode in China Telephony Network
2.62.1 Summary
All signaling links between two offices constitute a signaling link set and all signaling
links in the same signaling link set share the load.
2.62.2 Benefits
For operators
It protects the signaling link from being overloaded and prevents signaling link
breakdown caused by overload. This improves the reliability of the system.
2.62.3 Description
For MTP message transfer, it depends on the message sender to determine the route
and signaling link for transfer. On the specific route, the signaling link selector (SLS) in
the MTP message determines the specific signaling link. In ZXUN USPP (HLR), the
maximum degree of signaling link load balance is implemented by reuse of signaling
links selected with different SLSs.
The load balance of signaling links in the same signaling link set is ensured.

During switchover and switchback, the load balance of all signaling links in service can
be ensured.
2.63 ZWF-05-07-006 Multi-office-direction Load

Sharing of Signaling Route
Specification: ITU-T Q. 704
Communications industry standards in China: Technical Specifications for SS7 Signaling

Mode in China Telephony Network
2.63.1 Summary
This feature enables load sharing for quasi-associated office signaling messages among
signaling links in the signaling link set between two associated offices. Load sharing
transfer to a quasi-associated office direction is available via multiple associated office
directions.
2.63.2 Benefits
For operators
It enables load sharing for quasi-associated office signaling messages among signaling
links in the signaling link set between two associated offices
2.63.3 Description
Signaling load sharing from ZXUN USPP (HLR) to a quasi-associated office is available
via multiple associated office directions. One signaling route may consist of a maximum
of two link sets and such a signaling route contains all links in the two signaling link sets.
The signaling link seizure sequence can be set as needed. At present, the system
supports the following modes:
l Any sequence
l Link set selection based on SLS bit0

l Manually specified sequence
Users can customize the signaling link seizure sequence.
2.64 ZWF-05-07-008 Encryption Key Management

Specification:
2.64.1 Summary
The function is re-encryption of Ki and encryption key management.
2.64.2 Benefits
For operators
It ensures Ki security.
2.64.3 Description
The keys needed for safe storage of subscriber individual keys (ki) in the AUC can be
managed. For this a new Kx is calculated locally and used to re-encrypt Ki.
2.65 ZWF-05-09-002 Clock Synchronization

Specification:
G.810 Definitions and terminology for synchronization networks (1995).
G.811 Timing MS_VIE_Auirements of primary clocks suitable for use as node

clocks INPUT synchronization networks.
G.812 Timing MS_VIE_Auiements of slave clocks suitable for use as node clocks
INPUT synchronization networks.
G.813 Timing characteristics of SDH equipment slave clocks (SEC).

2.65.1 Summary
ZXUN USPP supports 8K Hz clock signal or 2MHz/2Mbits clock signal.
2.65.2 Benefits
For operators
It is used in TDM network.
2.65.3 Description
Two CLKG boards, which are hot active-standby backup mechanism and can be swap
smoothly, are used in the equipment to process clock signal. Its reference clock source
can be 8K Hz clock signal abstracted from trunk, which have E1 access interfaces, or
2MHz/2Mbits clock signal directly incoming clock source through BITS. The CLKG
boards keep synchronization to the upper layer network nodes, and distribute its clock
signal to other boards in the equipment. Thus, the Network Timing synchronization can
be realized in mobile network.
3 Optional Features
3.1 ZWF-05-10-001 Circuit Data Services

Specification: 3GPP 23.008 22.002
3.1.1 Summary
Bearer services are communication services that provide transmission capabilities

between subscribers and the network. HLR supports all data services specified in the
GSM/3GPP recommendations, including the fax service, data CDA service, data CDS
service, PAD access CA service, data PDS service, voice/data alternation service and
voice followed by data service etc.
3.1.2 Benefits
For operators
With the development of the communication market, diversified data services are
provided to meet the requirements for market development and increase operators’
competitiveness.

For end-users
This feature allows a subscriber to subscriber for multiple data services and meet
different communication requirements, e.g., use of WAP, Internet access and remote
access to Intranet etc.
3.1.3 Description
HLR supports subscription and management of both 2G and 3G subscribers’

subscription data. For 2G subscribers, HLR supports the following data services:
Data CDA service (asynchronous duplex circuit data): Supports asynchronous duplex
circuit data, transparent/non-transparent and 3.1kHz audio/UDI data services at the
transmission rates of 300bit/s (BS21), 1200bit/s (BS22), 1200/75bit/s (BS23), 2400bit/s
(BS24), 4800bit/s (BS25) and 9600bit/s (BS26).
Data CDS service (synchronous duplex circuit data): Supports basic packet access,
synchronization, non-transparent and 3.1K audio/UDI data services at the transmission
rates of 1200 bits/s (BS31), 2400 bits/s (BS32), 4800 bits/s (BS33) and 9600 bits/s
(BS34).
PADAccessCA (asynchronous PAD access circuit service): Supports PAD access,

circuit asynchronization, transparent/non-transparent and 3.1k audio/UDI data services
at the transmission rates of 300 bits/s (BS41), 1200 bits/s (BS42), 1200/75 bits/s (BS43),
2400 bits/s (BS44), 4800 bits/s (BS45) and 9600 bits/s (BS46).
Data PDS service (synchronous PDS access circuit service): Supports packet access,
synchronization, UDI and non-transparent data PDS services at the transmission rates
of 2.4k bits/s (BS51), 4.8k bits/s (BS52) and 9.6k bits/s (BS53).
Voice data alternation service: Supports the alternate voice/data service (BS61).
Voice+data service: Supports the data service of voice followed by data (BS81).
PLMN-specific bearer service: Supports PLMN-specificBS1-PLMN_specificBSF.
For 3G subscribers, HLR supports the following data services:
Asynchronous universal data service: Supports asynchronous universal circuit,

transparent/non-transparent and 3.1kHz audio/UDI/multimedia call data services.
Synchronous universal data service: Supports synchronous universal circuit,

transparent/non-transparent and 3.1kHz audio/UDI/multimedia call data services.
PLMN-specific bearer service: Supports PLMN-specificBS1-PLMN_specificBSF.

3.2 ZWF-05-10-002 Video Call

Specification: 3GPP TS: 22.001 22.002 23.910, 23.972, 27.001 29.007
3.2.1 Summary
The feature provides support for sending and receiving circuit-switched multimedia for
both WCDMA and GSM. Circuit-switched multimedia is based on the 3G.324M standard,
which is a 3G-variant of H.324, an ITU-T recommendation for low bit-rate multimedia
communication.
3.2.2 Benefits
For end-users
Subscribers using 3G.324M capable terminal can use applications, which use any
combination of voice, video and data simultaneously, such as real-time video telephony,
video show or still image while talking.
For operators
The ability to support multimedia applications is seen as one of the main benefits of a
WCDMA network.
The support of multimedia in GSM networks is needed for two reasons:
l WCDMA network coverage is not complete in the beginning. WCDMA subscribers,

who need full coverage, will use dual mode (WCDMA/GSM) terminal. In order to
provide these subscribers with improved multimedia coverage, the support is also
needed in GSM network.
l GSM only. Operators need ways to compete with WCDMA operators and need
possibility to offer multimedia for their customers. Circuit-switched multimedia offers
a new source of revenue and a possibility to gain a profile as a technology leader.
This can be regarded as an important intermediate step towards more extensive
use of mobile multimedia, regardless of if circuit or packet switched. Possibility to
provide multimedia promotes early multimedia awareness, which can be essential
for operator’s business.
3.2.3 Description
Circuit-switched multimedia supports mobile users with a 3G.324M capable terminal to

communicate in real-time through audio and video conferences and to send still images

from digital photo cameras, share data, files and active applications through data
conferencing.
For a multimedia call Bearer Service BS30 is used, which provides guaranteed quality of
service for multimedia communication. In the case of WCDMA, the Synchronous
transparent service is used in combination with Unrestricted Digital Information (UDI)
which provides a rate of 64 kbps or 32 kbps, or Restricted Digital Information (RDI) with
a rate of 56 kbps. UDI and RDI provide digital transmission end-to-end and are used for
data calls over ISDN networks. Thus, the multimedia calls using UDI/RDI can be set up
between WCDMA subscribers, as well as between WCDMA subscribers and ISDN
subscribers.
Bearer Service BS30 in transparent mode is also used for GSM/WCDMA multimedia
calls. In this case the capability of the call is set to "3.1 kHz audio" which means that the
call is treated as an analogue call using modems for transfer over PSTN. The user rate
will be 28.8 kbps. In case of GSM this is obtained by using High Speed Circuit Switched
Data (HSCSD) and optionally also 14.4 kbps channel coding. Either two radio channels
at 14.4 kbps can be used, or three channels at 9.6 kbps.
The GSM subscriber can make multimedia calls to other GSM subscribers, but also to
PSTN subscribers by using the 3.1 kHz audio (modem) service. However, multimedia
calls between WCDMA and GSM subscribers are not possible. Likewise, it’s not possible
to make multimedia calls between WCDMA subscribers and PSTN subscribers over
modems, nor is it possible to set up calls between GSM subscribers and ISDN
subscribers using UDI/RDI as a bearer.
A mobile subscriber with a 3G.324M terminal can get video, data and audio
communication with another 3G.324M terminal or with a terminal that is compatible with
3G.324M e.g. H.324I+M terminal, which is the mobile adapted ISDN multimedia terminal.
The other terminal could also be a Video Content Server, acting in accordance to the
3G.324M standard. Interworking with H.320, H.323 or SIP compatible terminals is not
supported.
The HLR provides the administrative means to provide mobile subscribers, holding their
subscription in HLR, with the appropriate basic service (Synchronous General Bearer
Service. BS30) to handle multimedia calls.
On reception of a mobile terminating call with multimedia characteristics, HLR analyses

the ISDN signaling information received and checks the subscription to the
corresponding General Bearer Service.
In case a mobile terminating call is received indicating a 56 kbps transfer requiring V.110,
I.460/X.30 rate adaptation by means of an Unrestricted Digital connection, HLR sends
the stored PLMN Bearer Capability information associated with the mobile subscriber if
this Bearer Capability indicates an UDI/RDI multimedia service.
In case a mobile terminating call is received indicating a 28.8 kbps transfer requiring a
V.34 modem connection, HLR sends the stored PLMN Bearer Capability information

associated with the mobile subscriber if this Bearer Capability indicates a 3,1 kHz audio
multimedia service.
In case that no signaling information is received, and provided that the multi numbering
scheme is to be used, HLR sends the stored PLMN Bearer Capability information
associated with the mobile subscriber.
The HLR provides the administrative capability of defining PLMN Bearer Capabilities
including multimedia-related values.
3.3 ZWF-05-10-003 Closed User Group (CUG) -

Supplementary Services
3.3.1 Summary
Closed User Group (CUG) is a standard supplementary service defined in 3GPP

recommendations, which provides functions like intra-group call permission and out-
group call barring. This feature saves a lot of communication costs for group enterprises.
HLR provides users with the standard CUG service.
3.3.2 Benefits
For operators
The CUG service attracts big users like group enterprises. It exploits new income growth
points for operators and enhances their competitiveness.
For end-users
Subscription of the CUG service can save a lot of communication expenses for group
enterprise users and facilitate intra-group communication.
3.3.3 Description
One user can register a maximum of 10 CUGs with each CUG being able to register all
basic services except emergency calls. At present, we only provide four basic services:
voice, fax, asynchronous data and synchronous data.
In a CUG, the following intra-group calls barring options are provided:

l No barring
l Barring of incoming calls
l Barring of outgoing calls
A CUG also provides the following external call barring options:
l Only out-group incoming calls allowed
l Only out-group outgoing calls allowed
l Both out-group incoming and outgoing calls allowed
l Barring of both out-group incoming and outgoing calls
These intra-CUG and out-group call barring options provide more flexible means for
management of users’ communication authorities.
The CUG functions supported in HLR are as follows:
l The HLR agent provides functions of registering, querying, modifying and deleting
CUG-related data.
l The HLR remote handling interface provides functions of registering, querying,

modifying and deleting CUG-related data.
l Downloading a subscriber’s CUG information to VLR/MSC during location update
l Downloading a subscriber’s CUG information to VLR/MSC during Restore
l Synchronizing a subscriber’s CUG data to MSC/VLR after data modification
l After all the CUG of a subscriber are deleted, HLR runs the MAP command to
delete CUG data in MSC/VLR.
l Checking whether any CUG call barring setting is enabled for a subscriber in HLR
when the subscriber is called
l HLR sends the related CUG information of a subscriber to GMSC with the MAP
command when the subscriber is called
3.4 ZWF-05-10-004 Call Forwarding-


3.4.1 Summary
The standard call forwarding supplementary services include Call Forwarding

Unconditional (CFU), Call Forwarding on Busy (CFB), Call Forwarding on No Reply
(CFNRy) and Call Forwarding Unreachable (CFNRc).
3.4.2 Benefits
For end-users
This feature allows setting of flexible call options to ensure that no incoming call is
missed.
3.4.3 Description
HLR provides subscription and maintenance of call forwarding supplementary service

data and checks whether to forward a call.
Call Forwarding Unconditional (CFU): After CFU be provisioned, different CFU

addresses, long CFU addresses and CFU sub-addresses can be registered and
activated according to different basic service groups.
For CFU, the available extended options for subscription include: Caller notification
during call forwarding and called number display during call forwarding.
The basic service groups supporting CFU subscription include:
The provided basic service groups include:
l Voice
l Fax
l Asynchronous data
l Synchronous data
Call Forwarding on Busy (CFB): After subscription of CFB, different CFB addresses/long
CFB addresses and CFB sub-addresses can be registered and activated according to
different basic service groups.
For CFB, the available extended options for subscription include: Forward-to party
notification during call forwarding, caller notification during call forwarding and called
number display during call forwarding.
The basic service groups supporting CFB subscription are the same as those for CFU.

Call Forwarding on No Reply (CFNRy): After CFNRy be provisioned, different CFNRy

addresses/long CFNRy addresses and CFNRy sub-addresses can be registered and
For the CFNRy service, the CFNRy time can be registered, which can only be 5, 10, 15,
20, 25 or 30 seconds.
For CFNRy, the available extended options for subscription include: Forward-to party
notification during call forwarding, caller notification during call forwarding and called
number display during call forwarding.
The basic service groups supporting CFNRy subscription are the same as those for CFU.
Call Forwarding Unreachable (CFNRc): After CFNRc be provisioned, different CFNRc

addresses/long CFNRc addresses and CFNRc sub-addresses can be registered and
For CFNRc, the available extended options for subscription include: Caller notification
during call forwarding and called number display during call forwarding.
The basic service groups supporting CFNRc subscription are the same as those for CFU.
The call forwarding supplementary services supported in HLR include the following
functions:
l The HLR agent provides functions like subscription/de-subscription, registration/de-

registration, activation/deactivation, query and modification of data related to call
forwarding supplementary services.
l The HLR remote handling interface provides functions like subscription/de-

subscription, registration/de-registration, activation/deactivation, query and
modification of data related to call forwarding supplementary services.
l HLR supports operations on call forwarding supplementary services via the MS.
These operations include registration/de-registration, activation/deactivation and
query. The query operation in HLR via the MS is only aimed at the CFU service.
Query on other call forwarding supplementary services can only be performed in
VLR.
l Downloading a subscriber’s call forwarding supplementary service information to

VLR/MSC during location update
l Downloading a subscriber’s call forwarding supplementary service information to

VLR/MSC during Restore
l Synchronizing a subscriber’s call forwarding supplementary service information to

MSC/VLR after data modification

l After all the call forwarding supplementary service data of a subscriber are deleted,
HLR runs the MAP command to delete call forwarding supplementary service data
in MSC/VLR.
l When a subscriber is called, HLR will check whether the CFU or CFNRc applies.
l When a subscriber is called, during Support Optimal Route (SOR) forwarding query,
HLR will check whether the CFNRy, CFNRc or CFB service applies.
l When a subscriber is called, HLR will send the related call forwarding information
(the forward-to number, forwarding options etc.) to GMSC with the MAP command.
3.5 ZWF-05-10-005 Call Forwarding On Default

Specification:
3.5.1 Summary
Call Forward on Default is not a standard service defined in the related protocol. It is a
personalized service provided in ZXUN USPP (HLR) for operators.
3.5.2 Benefits
For end-users
The subscriber will not any longer have to change the C-number every time he wants to
have Call Forwarding to either the Voice Mail system or to another C-number. The Call
forwarding to e.g. the Voice Mail is always there as default if no other Call Forwarding is
active. This will simplify the procedures for the subscriber to a large extent.
For operators
The operator can offer a simplified Call Forwarding service towards its subscribers. The
availability of its subscribers will increase since the subscriber is always reached at least
to his Voice Mail.
3.5.3 Description
The purpose of the feature Default Call Forwarding (DCF) is to provide the mobile
subscriber with a default forwarded-to number, which is registered by the operator. The
operator can do so independently of the call forwarding services and the subscriber
does not have to subscribe to any call forwarding service. This means that the call
completion rate will increase.

The feature cannot be operated by the subscriber. This means that the subscriber
cannot activate, deactivate or interrogate the service.
The purpose is also that the call forwarding services will be more simplified for the
subscribers. The subscriber does not have to set the forwarded-to number to for
example his voice mail.
The feature does not affect the MSC/VLR due to that the MSC/VLR sees the feature as
a normal call forwarding service. The feature is applicable to all Basic Service Groups
(BSGs) except SMS. This also means that a specific forwarded-to number can be set
per BSG, for example speech is forwarded to voice mail and terminating fax is sent to a
fax mail box.
Different subscription options can be created:
l The calling subscriber can receive notification that the call has been forwarded
l The DCF service can be provided as default of the call forwarding on busy and/or
l As default of the call forwarding on no reply and/or
l As default of the call forwarding on not reachable
The call forwarding services takes precedence over DCF and the DCF interacts with
other supplementary services as the call forwarding services do.
3.6 ZWF-05-10-006 Line Identification (LI)

3.6.1 Summary
Line identification services provide control over MS number display during subscribers’
call processes.
3.6.2 Benefits
For operators
With the diversified supplementary services provided, this feature meets the
requirements for communications market development and increases operators’
competitiveness.

For end-users
This feature enables subscription of multiple supplementary services and customization

of personal communication property list to satisfy personalized requirements.
3.6.3 Description
Five line identification services are available, which are Calling Line Identification
Presentation (CLIP), Calling Line Identification Restriction (CLIR), COnnected Line
identification Presentation (COLP) and COnnected Line identification Restriction (COLR)
and Calling NAme Presentation (CNAP). The purposes of these services are as follows:
l The CLIP service enables the called party to see the calling number on his or her
MS. For example, if subscriber B has registered the CLIP service, when A calls B,
subscriber B will be able to see the number of subscriber A on MS with the CLIP
function.
l With the CLIR service, a subscriber can prevent his or her number from being
displayed on the called party’s MS. For example, if subscriber has registered the
CLIR service and subscriber B has registered the CLIP service, when A calls B,
subscriber B will be unable to see subscriber A’s number since subscriber A has
registered the CLIR service.
l The COLP service enables the caller to display the connected subscriber’s number.
Instead of checking caller dial-up, the COLP service is used to display the currently
connected subscriber’s number for the caller. For example, if subscriber A has
registered the COLP service, when A calls B but B forwards the call to C, the
number of subscriber C can be displayed in subscriber A’s MS with the COLP
function.
l The COLR service enables the connected subscriber to prevent his or her number
from being displayed on the caller’s MS. For example, if A has registered the COLP
and subscriber C has registered the COLR service, when A calls B but B forwards
the call to C, the number of subscriber C will not be displayed on subscriber A’s MS
since subscriber C has registered the COLR service.
3.7 ZWF-05-10-007 Call Waiting (CW) –


3.7.1 Summary
The CW service is used to notify a mobile subscriber in the connected or CH state of

any incoming call.
3.7.2 Benefits
For operators
competitiveness.
For end-users
This feature reminds a busy mobile subscriber of an incoming call to avoid missing of
any important call.
3.7.3 Description
When in the connected or CH state, a mobile subscriber has no channel available to

receive any incoming call. The CW service can provide the mobile subscriber with the
incoming call notification function. In this case, the caller will receive a call wait
notification. After receiving an incoming call notification, the called party can select to
receive, reject or ignore the incoming call.
Only one incoming call is allowed to be in the waiting state at a time. This service is
unable to provide notification for any subsequent incoming calls at one moment.
3.8 ZWF-05-10-008 Call Hold (CH) –Supplementary

Services
3.8.1 Summary
The CH service enables a subscriber to pause and hold the currently connected call.
3.8.2 Benefits
For operators

competitiveness.
For end-users
This feature reminds a busy mobile subscriber of an incoming call to avoid missing of
any important call.
3.8.3 Description
Call hold indicates that a mobile subscriber can interrupt the currently connected call
temporarily and hold it to prevent it from being released. The subscriber is allowed to
resume this call. After call hold, the mobile subscriber can also originate new calls. The
mobile subscriber can receive an incoming call if he or she has registered the CW
service in the meantime. After originating or receiving a call, the mobile subscriber can
switch between the currently active call and the held one and terminate one or all the
calls.
When the call hold operation is triggered, the communication on the current traffic
channel will be interrupted and released from the current call but it will still be reserved
for the corresponding subscriber. In one call hold operation, the subscriber can only
seize one traffic channel.
3.9 ZWF-05-10-009 Call Barring Supplementary

Services (CB)
3.9.1 Summary
This feature provides functions of barring outgoing and incoming calls.
3.9.2 Benefits
For operators
competitiveness.

3.9.3 Description
Call barring supplementary services can be divided into two categories: One category is
used to bar outgoing calls while the other is used to bar incoming calls. The call barring
degree varies with different call barring services.
l Barring of All Outgoing Calls (BAOC): After activation of BAOC, all outgoing calls of
a subscriber will be barred.
l Barring of Outgoing International Calls (BOIC): After activation of BOIC, all

international calls of a subscriber will be barred.
l Barring of Outgoing International Calls beyond HPLMN (BOICE): After activation of

BOICE, all outgoing international calls originated by a subscriber except those
towards HPLMN will be barred.
l Barring of All Incoming Calls (BAIC): After activation of BAIC, all incoming calls to a
subscriber will be barred.
l Barring of Incoming Calls Roaming beyond HPLMN Country (BICR): After

activation of BICR, a mobile subscriber will not be able to receive all calls when
roaming beyond the HPLMN country. In this case, all incoming calls originated
towards this subscriber will fail.
Calls barring services are set with password protection. A subscriber needs to input the
corresponding password for check when performing call barring service operations. The
system will allow the subscriber to perform operations like activating or deactivating the
call barring supplementary services only after successful password check. Two states
are available for call barring: controlled by subscriber and controlled by operator. When
call barring is controlled by the operator, subscribers will not be able to perform call
barring supplementary services via their MSs.
During call barring operation, if a subscriber input the wrong password for three times
continuously, the call barring will switch to the state of controlled by operator. In this
case, the subscriber will not be able to perform call barring supplementary services via
MS. Instead, the subscriber has to go to the accounting center for handling.
3.10 ZWF-05-10-010 MultiParTY (MPTY) -


3.10.1 Summary
This feature provides a mobile subscriber with the capability of connecting multiple calls
simultaneously, i.e., allowing a subscriber to talk to multiple other subscribers at the
same time.
3.10.2 Benefits
For operators
competitiveness.
For end-users
This feature provides mobile subscribers with the capability of connecting multiple calls.
3.10.3 Description
After registering the multiparty function, a mobile subscriber first adds the subscriber in
call hold into the currently active call to form a multiparty call. Then, the subscriber can
select to add more subscribers into the call to form a conference call. In a conference
call, the subscriber having registered the MPTY service is the controller, who can
remove an added subscriber from the conference call without disconnecting the call or
disconnect that subscriber directly. During a conference call, the controller can select to
hold the current call. In this case, the other subscribers in the conference call can still
talk to each other. In addition, the controller can also originate new calls or receive other
incoming calls.
During a conference call, the controller can add or delete conference participants.
The controller can hold and exit the conference call. Then, the next controller can
originate new calls or receive incoming calls.
3.11 ZWF-05-10-011 Advice Of Charge (AOC) -


3.11.1 Summary
The AOC supplementary service is further divided into Advice of Charge Charging
(AOCC) and Advice of Charge Information (AOCI), which are used to remind subscribers
of the current service charges.
3.11.2 Benefits
For operators
competitiveness.
3.11.3 Description
AOCI is used to generate charging information for subscribers’ call services. The
charging information includes the charge rate of a call, call duration and amount of data
transmitted etc.
AOCC is used to generate charging information for use of services. It is primarily used
for service users (not mobile subscribers) to pay charges to mobile subscribers after
using the related services. Similar to AOCI, AOCC does not support generation of AOCs
for non-call related transactions, e.g., some supplementary services.
3.12 ZWF-05-10-012 Explicit Call Transfer (ECT) -

3.12.1 Summary
This feature allows a serviced subscriber to hang up after setting up a call between two
other subscribers connected with him or her at the same time.
3.12.2 Benefits
For operators
competitiveness.

3.12.3 Description
When connected with two other subscribers at the same time, the serviced subscriber
can trigger the ECT service to disconnect him or her from the two remote subscribers
while setting up a normal call between the two remote subscribers. Then, the serviced
subscriber will have no control right over the call between these two remote subscribers.
3.13 ZWF-05-10-013 Call Diversion (CD)-

3.13.1 Summary
This feature allows the serviced subscriber to transfer an incoming call to another
number before the call is set up.
3.13.2 Benefits
For operators
competitiveness.
For end-users
This feature enables subscribers to forward calls flexibly.
3.14 ZWF-05-10-014 EMLPP- Supplementary

Services

3.14.1 Summary
This feature provides subscribers with differentiated services and subscribers can
register different priorities (4 levels in total). In this way, services will be first provided for
subscribers with higher priorities when the resources are limited.
3.14.2 Benefits
For operators
This service allows operators to provide differentiated services for subscriber groups of
different levels. When the network resources are limited, the service can help operators
to maximize benefits.
For end-users
This service enables subscribers of different eMLPP priorities to enjoy differentiated

services.
3.14.3 Description
The eMLPP service is a supplementary service, and complies with GSM02.67,

GSM03.67, and GSM04.67 protocols. This service allows high-priority subscribers to
enjoy quicker call connection setup, and seize the resources (including circuit resources
of interface A and trunk circuit resources) of low-priority calls when the network sources
are rather limited. As a result, carriers provide differentiated services
for the subscribers, and enable the connections of high-priority calls to be established
first.
The eMLPP service provides 7 priorities: A, B, 0, 1, 2, 3, and 4. The two highest

priorities (priority A and priority B) are for the internal use within carriers, for example,
emergency calls or special VGCS/VBS calls. The two priorities are only effective
within one MSC/VLR, and are treated as priority 0 in other MSCs/VLRs. Other five
priorities are for the subscribers only, and are applicable in ISDN networks supporting
the eMLPP service. When subscribing to the eMLPP service, the subscriber can specify
a priority in the HLR as the top priority. In addition, the subscriber can also specify the
default priority, which cannot be higher than the subscriber's top priority.
Through the MS (provided that the MS supports the service), the subscriber can modify
the default priority. When the MS's location is updated, the HLR sends a message with
the subscriber's top priority and default priority to the VLR.

The eMLPP service allocates one or multiple priority rights to a subscriber. The
subscriber can select a priority for every call according to the own rights. The network
allocates resources to every call according to the priority of the call. Every call of a
certain priority can select a call connection setup mode.
The eMLPP service involves quick call connection setup and queuing & preemption.
Quick call connection setup
Every call of a certain priority can determine whether to adopt quick call setup flow.
Queuing & preemption
When the network resources (including trunk circuits, signaling channels, and service
channels) are limited, the network holds calls of high priority and offers preferential
treatment for these calls in queuing, and even allows these calls to seize the resources
of low-priority calls.
3.15 ZWF-05-10-015 Unstructured Supplementary

Service Data (USSD) Phase 2
Specification: 3GPP TS 22.090 23.090 24090
3.15.1 Summary
This feature holds the wireless connection during a session and provides a transparent
channel instead of a store-and-forward system. Therefore, for the USSD service, it is
unnecessary to set up a channel again each time when a message is sent. In addition,
in terms of response time, USSD provides higher response speed than the short
message service.
3.15.2 Benefits
For operators
This feature enriches the supplementary services and attracts more subscribers.
Support of USSD at the network side facilitates network management. In addition, more
services can be developed on the basis of the USSD service.
USSD Phase 2 improves the operator's revenue in an indirect way. As stated above, it
allows for the development of PLMN specific supplementary services that do not need to
be standardized but rely on a standardized transport mechanism. Therefore USSD
Phase 2 decouples the application layer from the transport layer. Due to the enhanced

functionality of USSD Phase 2 more innovative and enhanced applications can be

offered to the subscribers.
For end-users
Subscription of the USSD service allows subscribers to deal with some special matters
in some cases.
From the subscribers point of view USSD Phase 2 offers an improved interface to
access information sources. Additionally, depending on the introduction of new services
by the operator, the subscriber can benefit from these services, e.g. CAMEL, WAP,
information services.
3.15.3 Description
The application scopes of the USSD system are similar to those of the Short Message
System (SMS) and WAP platforms. However, there are also some differences compared
with SMS and WAP. For SMS, only a store-and-forward system instead of a session
channel is available at the physical bearer layer. A subscriber needs multiple session
processes to complete a query. Similar to USSD, WAP holds a session process during
interactions. However, influenced by the speed of the WAP server and Internet, its
current response speed is even lower than that of SMS. In CAMEL3, U-CSI of the USSD
service is defined. A USSD session can be initiated from MS and the corresponding
SCF can be found according to the configuration information in CSI. The SCF
determines the subsequent service logic. Similarly, SCF can also actively initiate a
USSD session towards MS via HLR.
With USSD Phase 2 the following additional functionality will be implemented:
l Network initiated USSD (NI USSD) means that the USSD function is invoked by the
network entities/application. In this case the network sends requests to an MS, e.g.
when certain parameters have changed.
l USSD Dialogs allow for more than one USSD request/response. Real dialog
sessions with questions and answers between the MS and a network entity /
application can be initiated.
3.16 ZWF-05-10-016 Operator Determined Barring

(ODB) Service

3.16.1 Summary
This feature provides operators with the capability of end-user management and control.
HLR provides five categories of ODB functions: Barring of ODB calls, barring of ODB
roaming, barring of ODB call transfer, barring of ODB forward-to number registration and
barring of ODB supplementary services.
3.16.2 Benefits
For operators
This feature provides operators with the capability of end-user management and control.
3.16.3 Description
HLR provides five categories of ODB functions: Barring of ODB calls, barring of ODB
roaming, barring of ODB call transfer, barring of ODB forward-to number registration and
barring of ODB supplementary services.
Barring of ODB calls includes:
Barring of all outgoing calls
Barring of all outgoing international calls
Barring of all outgoing international calls beyond HPLMN country
Barring of all outgoing calls when roaming is beyond HPLMN country
Barring of outgoing international regional calls
Barring of outgoing international regional calls beyond HPLMN country
Barring of outgoing international and international regional calls beyond HPLMN country
Barring of outgoing information inquiry calls at high charge rates
Barring of outgoing entertainment calls at high charge rates
Barring of outgoing information inquiry and entertainment calls at high charge rates
Barring of all incoming calls
Barring of all incoming calls when roaming is beyond HPLMN country
Barring of international toll calls (HPLMN user-defined type 1)
IP unauthorized (HPLMN user-defined type 4)

Barring of ODB roaming includes:
Barring of roaming beyond HPLMN
Barring of roaming beyond HPLMN country
Barring of ODB forward-to number registration includes:
Barring of forward-to number registration
Barring of international forward-to number registration
Barring of international forward-to number registration beyond HPLMN country
Barring of international regional forward-to number registration
Barring of international regional forward-to number registration beyond HPLMN country
Barring of ODB call transfer includes:
Barring of call transfer
Barring of call transfer when call charge is to be paid for at least one in two calls
Barring of call transfer when international toll charge is to be paid for at least one in two
calls
Barring of call transfer when international regional call charge is to be paid for at least
one in two calls
Barring of call transfer when call charge is to be paid for both of two calls
Barring of call transfer when a subscriber is using call transfer in the same MSC/VLR
Barring of ODB supplementary services includes:
Barring of all supplementary service operation access of a subscriber
3.17 ZWF-05-10-017 Operator Determined Barring

(ODB) for Packed Oriented Services
Specification: 3GPP 23.060, 22.041, 23.015, 29.002

3.17.1 Summary
This feature provides the operator with a set of barring options to control subscriber’s
use of packet switched services.
The following Operator Determined Barring options are available with this feature:
l Barring of all Packet Oriented Services
l Barring of Packet Oriented Services provided by Access Points within the Home
Public Land Mobile Network (HPLMN) while the subscriber is roaming in a Visited
Public Land Mobile Network (VPLMN)
l Barring of Packet Oriented Services provided by Access Points within the roamed
to VPLMN
Only one out of the barring options above mentioned can be activated at the same time.
Only the operator may activate and deactivate the different barring options.
3.17.2 Benefits
For end-users
End users’ subscription for packet switched services can fit each user’s calling habits
and economy.
The end-user can keep control of the expenses for the packet switched use of his/her
mobile subscription and avoid unpleasantly high telephone bills.
For operators
The feature provides an operator with further means for restricting subscriber activities in
the packet domain.
Operator Determined Barring of Packet Oriented Services gives the operator control
over the usage of packet switched services.
The operator can offer service packages to subscribers of various calling habits. The
feature is also a powerful tool to prevent and/or control fraud.
3.17.3 Description
The subscriber record in HLR contains information which points out which barring option
is active for the subscriber. This information may be set by the operator.

The HLR provides the SGSN with that information upon location updating from the
SGSN or when it is changed by administrative means, using the MAP message Insert
Subscriber Data.
The operator has the possibility of applying (or not) an action whenever the SGSN
reports that it does not support ODB-PS. The action consists of, instead of performing a
complete barring of roaming in that area, still allow the subscriber to be located in that
area with at least the possibility of receiving/generating SMS.
3.18 ZWF-05-10-018 CAMEL3 Service

3.18.1 Summary
CAMEL (Customized Applications for Mobile network Enhanced Logic) is a network

feature contained in the GSM and IN network entities. When a subscriber having
registered the CAMEL service is roaming or called, these feature data will be transferred
between HPLMN and VPLMN to trigger the corresponding intelligent services for the
subscriber.
On the foundation of CAMEL 2, more subscription data and trigger detection points and
service control flows are added into CAMEL 3.
3.18.2 Benefits
For operators
With support of the CAMEL service in HLR, operators can start subscription of intelligent
service subscribers immediately, use the flexible IN service configuration modes, make it
more flexible and convenient to add new services or features, and make use of many
existing IN features (e.g., familiarity number, prepaid feature and information desk
services) immediately to reduce the subsequent equipment investment costs.
Based on CAMEL 3 functions, operators can provide more diversified intelligent services
for subscribers.
For end-users
Subscribers benefit from the diversified intelligent services provided by HLR. Based on
the CAMEL3 functions, subscribers can enjoy more abundant intelligent services.

3.18.3 Description
HLR supports the following CAMEL 3 functions:
l Supporting subscription data at CAMEL Phase 3, including:
O-CSI (Originating CAMEL Subscription Information)
T-CSI (Terminating CAMEL Subscription Information)
U-CSI (USSD CAMEL Subscription Information)
SS-CSI (Supplementary service invocation CAMEL Subscription Information)
TIF-CSI (Translation Information Flag)
GPRS-CSI (GPRS CAMEL Subscription Information)
SMS-CSI (Short Message Service CAMEL Subscription Information)
D-CSI (Dialed Service CAMEL Subscription Information)
M-CSI (Mobility Management event CAMEL Subscription Information)
VT-CSI (VMSC Terminating CAMEL Subscription Information)
l Supporting download and synchronization of CAMEL3 subscription data to the

visited network
l Supporting the J interface signaling flow with gsmSCF, including:
Any Time Interrogation (ATI)
Any Time Subscription Interrogation (ATSI)
Any Time Modification (ATM)
Subscriber data modification notification
l Supporting trigger and detection of the related static trigger detection points by the
call termination routing process
l Supporting compatibility with CAMEL2 functions

Specification: 3GPP 29.002 23.078 29.078

3.19.1 Summary
On the foundation of CAMEL 3, more subscription data and trigger detection points and
service control flows are added into CAMEL 4.
3.19.2 Benefits
For operators
Based on CAMEL 4 functions, operators can provide more diversified intelligent services
for subscribers.
For end-users
Based on the CAMEL4 functions, subscribers can enjoy more abundant intelligent
services.
3.19.3 Description
In CAMEL4, the CAMEL features apply to the following services:
l CS service: Controls MO, MT, VT, MF, NP and NC calls.
l SMS service: Controls the MO_SMS and MT_SMS services as well as the CS and
PS SMS services.
l PS service: Controls subscribers’ MM and PDP contexts.
l IMS service: Controls subscriber-initiated MO and MT transactions.
The following new features are added in CAMEL4:
l Providing location information of called parties
l Adding operations on ODB data into ATM operations
l Enhanced ATI and PSI operations applicable to the PS domain
l Supporting compatibilities with functions of CAMEL3 and CAMEL2
3.20 ZWF-05-10-020 LCS Service


3.20.1 Summary
HLR provides the LCS service subscription function and supports the following four
standard subscription modes: Universal, Call related, Non-call related and PLMN
operator. HLR also supports the Lh interface with GMLC and provides the LCS routing
function.
3.20.2 Benefits
For operators
Providing the LCS service, this feature allows operators to work together with SPs to
develop diversified location-based applications to attract subscribers and increase
business income.
For end-users
After registering the LCS service, subscribers can query the related location information
through the mobile IN or Internet supporting this service and use the location information
based applications provided by a third party. For example, subscribers can know where
they are located currently and whether there is any supermarket around and ask the way
etc. They can also designate other subscribers so that the designated persons can
locate them and get information about where they are going.
3.20.3 Description
The LCS data registered in HLR include:
Gateway Mobile Location Center (GMLC): Refers to GMLCs available for subscriber
location. Each subscriber can register with a maximum of 5 GMLCs.
User Equipment (UE) location type: Includes “Universal”, “Call related”, “Non-call related”
and “PLMN operator”.
Call related external LCS client: Refers to the LCS client available for subscriber location.
Each subscriber can register with a maximum of 40 calls related external LCS clients.
Each client may provide the following information: External LCS client address, GMLC
restriction and whether to notify type selection information of a subscriber during location.
Non-call related external LCS client: Refers to the LCS client available for subscriber
location. Each subscriber can register with a maximum of 40 non-call related external
LCS clients. Each client may provide the following information: External LCS client
address, GMLC restriction and whether to notify type selection information of a
subscriber during location.

3.21 ZWF-05-10-021 Equal Access Service (Multiple

Long Distance Carrier)
Specification: 3GPP TS 29.002
3.21.1 Summary
The equal access mechanism (multiple long distance carrier function) enables
subscribers to select the toll operators freely and toll operators to develop telecom
services equally.
3.21.2 Benefits
For operators
This feature enables equal development of telecom services and introduction of healthy
competition.
For end-users
This feature enables subscribers to select toll operators freely so that they can enjoy
services of higher quality.
3.21.3 Description
With the coexistence of multiple toll operators, each toll operator is assigned with an
operator ID (CIC hereafter) to enable mobile subscribers to freely select networks of
different toll operators and toll operators to develop telecom services equally. After
signing an agreement with the corresponding toll operator, a mobile subscriber can dial
the CIC of this operator to select the toll network of this operator originate a call.
Besides dialing of a CIC to select a toll network, a mobile subscriber can also add the
preset network selection function to select a toll operator. After such presetting, the
mobile subscriber can select a preset operator’s toll network to originate a toll call
without dialing the operator’s CIC. The mobile subscriber having made such presetting
can still dial another operator’s CIC to select a non-preset toll operator. A subscriber
having neither dialed a CIC nor made operator presetting can be connected to the
default toll network of the corresponding operator.
The equal access data registered in HLR include:
NAEA (North America Equal Access)
Mapping of NAEA in MSC/VLR to CIC

HLR also provides the following equal access functions:
After a subscriber registers the equal access service data, HLR inserts NAEA into VLR
during location update or Restore. When the subscriber registers abroad, HLR will not
send NAEA parameters into VLR.
When the equal access service of a subscriber is deleted in HLR, HLR will delete this
subscriber from VLR with the corresponding MAP command.
When a subscriber having registered the equal access service is called, HLR will return
NAEA to GMSC with the corresponding MAP command.
3.22 ZWF-05-10-022 Coloring Ring Back Tone

(CRBT) Service
Specification:
3.22.1 Summary
CRBT as defined by China Mobile and China Unicom can be provided respectively.
3.22.2 Benefits
For operators
This feature provides CRBT to attract more subscribers, exploit new incoming growth
points for operators and increases operators’ competitiveness.
For end-users
This feature enables subscribers to use CRBT.
3.22.3 Description
After applying for the personalized ring-back tone service via the special service hotline,
voice interactions, business hall or WAP, a called subscriber can customize
personalized ring-back tones by means of WWW, WAP or dial-up of the access code.
Then, when this subscriber is called, the customized personalized music or DIY
recording that replaces the ordinary ring-back tone can be played to the caller according
to such conditions as different calling numbers, called home area and specific time set
by the called party. The ZXUN USPP (HLR) system supports the following CRBT
solutions:

l IN mode CRBT
In this mode, the called subscriber registers CRBT as T-CSI in HLR, triggers CRBT via
SCP, returns to the CRBT center number to GMSC, and then connects to the CRBT
center to play CRBT.
l Calling switch mode CRBT
The calling switch mode indicates that the MSC or GMSC where the caller is located is
responsible for connecting the CBRT of the called subscriber to the caller.
In the related subscriber’s home network, a user-defined supplementary service is used

as the CRBT subscription flag. After receiving a call routing indication, HLR will return
SS-CODE to GMSC after inserting it in the SSLIST parameters of routing response if
HLR finds that the called party has registered CRBT and this route is to return the
roaming number.
l Called switch mode CRBT
The called switch mode indicates that the MSC or GMSC where the called party is
located is responsible for connecting the called party’s CRBT to the switch of call
origination so that the caller can hear the CRBT.
When the called party’s MS is powered on or during location update, HLR will insert the
CRBT subscriber flag bit into the called VMSC/VLR by the operation of subscription data
insertion.
l Called mode 2 CRBT
In this mode, the CRBT subscriber needs to register SSCODE and SSET in HLR. During
subscriber location update or data recovery, HLR will insert SSCODE and SSET into
MSCVLR. When there is an incoming call, SSET will be checked to see whether the
called party is a CRBT subscriber. If so, the call will be connected to the CRBT center for
CRBT playback to the caller.
l Calling mode 2 CRBT
In this mode, when a CRBT subscriber is called, GMSC will initiate routing query toward
HLR. HLR will extract the GMSC number from the routing indication and judge whether
the current GMSC supports CRBT trigger according to the configured CRBTGMSC
number table. If so, after checking the roaming number, HLR will change the NPI filed in
the roaming number from 1 to 2 and then return the roaming number to GMSC. After
receiving the roaming number, GMSC will determine that the called party is a CRBT
subscriber if it finds that the NPI field is 2. Then, it will change the NPI field to 1 and
send IAM to MSC. GMSC will connect the CRBT center for CRBT playback to the caller
after receiving ACM.

3.23 ZWF-05-10-023 Subscriber Category Service

Specification:
3.23.1 Summary
This feature provides subscriber category service subscription data: “CS

Allocation/Retention Priority (CARP)” and “Allocation/Retention Priority (ARP)” to satisfy
operators’ requirements of providing differentiated services for different subscribers.
3.23.2 Benefits
For operators
After construction of the 3G network, the subscriber category service should be adopted
for 3G subscribers. The primary purposes are:
l The market development and competition environments require operators to

subdivide end-users.
l The network functions should be able to support market subdivision.
l At the initial phase of 3G network deployment, a comprehensive way of

consideration, overall planning and definite requirements are needed.
3.23.3 Description
The subscriber category service is implemented by defining subscriber priority
identifications in the corresponding equipment and then sending them to RNC for
execution.
Subscriber priority identification:
CS domain: Is identification based on “CS Allocation/Retention Priority (CARP)” in

subscription data of HLR.
PS domain: Is identification based on “Allocation/Retention Priority (ARP)” in

subscription data of HLR.
VLR/SGSN acquires the CARP/ARP definition through the MAP ISD message. Then,
every time when a call is set up, MSC/SGSN will send CARP/ARP in the “RAB
ASSIGNMENT REQUEST” message to RNC.

RNC executes some restriction strategy to provide services at different levels for
subscriber with different priorities.
3.24 ZWF-05-10-024 Wireless Access Restrictions

For Subscribers
Specification:
3.24.1 Summary
In HLR, the Access Restriction information identifications are added to indicate

accessible properties of subscribers for access restriction over CS and PS domains.
During location update, the ARD information is transmitted to MSC/VLR or SGSN
through the extended ISD operation. After receiving the Access Restriction information
in ISD, VLR/SGSN should permit or reject a subscriber’s login request based on the
logic judgment relationship according to the wireless access system that the subscriber
is to log in currently.
3.24.2 Benefits
For operators
At the initial phase of service/3G network development, 2G/3G subscribers should be

differentiated with different identifications to flexibly control the use of the BSS or
UTRAN network by 2G/3G subscribers. The major purposes of this feature are:
l Differentiation of subscribers for each other with different identifications, i.e., to

follow the principle of registration before service activation for 3G subscribers so
that operators can acquire 3G subscriber information conveniently. This is
conducive to planning, business operation and customer service.
l Clear management of 3G subscribers and 3G network resources to facilitate

accumulation of experiences in network operation and 3G network optimization
l Avoidance of evident quality difference experience and account disputes after 2G

subscribers start to use 3G UE, especially when the 3G network is incomplete at
the initial phase, thus ensuring that the customer satisfaction will not be affected
l Enhancement of the concept of 3G subscribers or the new brand to bring

differentiators in commercial advertising and embody differentiated services

3.24.3 Description
The ARD (Access Restriction Data) field is added in HLR to provide CS and PS access
restriction. In addition, Access Restriction Data management is also added.
The MAP ISD operation provides transfer of ARD data between HLR and VLR or SGSN
through extension of access restriction parameters.
VLR/SGSN needs to process the extended ISD operation to provide logic control of the
current login wireless access system in combination with the ARD information.
When access is rejected, VLR/SGSN should return a NAS cause value as specified.
This cause value should be configured as any value in the range of 11~15 by operators.
If the Access Restriction Data change, HLR will start the ISD operation to synchronize
with the access restriction data in VLR/SGSN. Since the Access Restriction Data is set
on the basis of IMSI, after loading of this function, the ARD data corresponding to IMSI
will be modifiable only instead of being deleted and it will be impossible to start
MAP_Delete_Subscrber_Data to delete the ARD data.
3.25 ZWF-05-10-025 Access Of Subscriber Classes

Specification: China Mobile Technical Plan of Priority Access Service (PAS)
for High-end User
3.25.1 Summary
The subscribers are divided into three levels. The subscribers at higher levels will be
assigned with wireless resources in precedence.
3.25.2 Benefits
For operators
This feature brings differentiators in commercial advertising and embodies differentiated

services.
3.25.3 Description
The subscribers are divided into three levels:
Level 1: Some dedicated resources will be reserved for subscribers at this level in
hotspot areas. During resource allocation, subscribers at this level will be assigned with

dedicated resources in the first place. If all the dedicated resources are seized,
subscribers at this level will share the public resources with those at the other two levels
but subscribers at this level will be given the first priority.
Level 2: No dedicated resources will be reserved for subscribers at this level, who will
share the public resources with those at other levels. The resource seizure priority for
subscribers at this level is lower than that for subscribers at level 1.
Level 3: No dedicated resources will be reserved for subscribers at this level, who will
share the public resources with those at other levels. The resource seizure priority for
subscribers at this level is lower than that for subscribers at the other two levels. When
the system resources are insufficient, subscribers at this level can be switched to other
cells so that the resources can be vacated for subscribers at other level.
The subscriber priority feature only affects the local end of priority subscribers. In the
calling flow, the priority of wireless resource seizure depends on the caller’s priority; in
the called flow, the priority of wireless resource seizure depends on the called party’s
priority.
Subscribers’ priorities are differentiated from each other according to different categories.
In comprehensive consideration of priority access and 17951 IP Pre-setting, the
following subscriber types are defined for different subscriber categories based on value
ranges:
l Subscriber type of category 1 subscribers: 10-31 (17951IP presetting), 76-97 (no

17951IP Pre-setting).
l Subscriber type of category 2 subscribers: 32-53 (17951IP presetting), 98-B9 (no

l Subscriber type of category 3 subscribers: 54-75 (17951IP presetting), BA-DB (no

3.26 ZWF-05-10-026 IP Pre-setting Function

Specification:
3.26.1 Summary
With IP pre-setting, when a subscriber applies for a certain service or originates a toll
call, the system will automatically insert the corresponding operator’s IP prefix (e.g.,
17951) to save the call charge.

3.26.2 Benefits
For operators
This feature brings differentiators in commercial advertising.
For end-users
This feature makes it easier end-users to use the IP service.
3.26.3 Description
HLR uses the Category field as the IP Pre-setting identification. When a subscriber
registers this service, HLR will deliver this field to VLR after inserting it into the
subscription data. During subscriber location update or data recovery, HLR will insert
this field into VLR.
After judging that a subscriber has registered IP Pre-setting, MSC will further check the
number dialed by this subscriber. If it is a local number, no operation will be performed.
If it is a toll number, an IP prefix (e.g., 17951) will be automatically added before the
number dialed.
Subscriber type: 10-75 (hexadecimal) indicates a subscriber has registered IP Pre-

setting.
Subscriber type: 76-DB (hexadecimal) indicates a subscriber has not registered IP Pre-
setting.
3.27 ZWF-05-10-027 GPRS Charging Characteristics

Specification: 3GPP TS: 23.060, 32.215, 32.015 29.002
3.27.1 Summary
The GSM and WCDMA networks support a range of packet based services. In order to
enable operators the ability to provide a commercially viable service there is a need to
handle charging functions. Charging should be flexible and allow to bill according to the
amount of data transferred, the QoS supported and the duration of the connection.
This feature provides the operators with means for applying, on subscription basis,
different kind of charging characteristics to its GPRS subscribers.

3.27.2 Benefits
For end-users
The end-user will benefit from the improved efficiency in the operator’s Billing chain.
Additionally, end-users with a prepaid solution will be able to roam outside their Home
PLMN.
For operators
The Operators will benefit from a completely standard solution according to 3GPP
Release 4 specifications. In comparison with previous standard solutions, this one
provides the operators with further and more flexible means for the definition of its
network charging functions.
3.27.3 Description
The HLR provides the administrative means to provide mobile subscribers, holding their
subscription in HLR, with the appropriate charging characteristics for his/her packet
oriented services.
The GPRS subscriber record contains information which points out the charging
characteristics assigned to the subscriber. A subscriber may have charging
characteristics assigned to his/her subscription (Subscriber Charging Characteristics)
and/or his/her subscribed Access Points (Packet Data Protocol Context Charging
Characteristics).
The Charging Characteristics to be subscribed in HLR refer to charging profiles and the
expected behavior associated with each profile.
A profile consists of different charging triggering criteria for each Charging Data Record
(CDR) type and, optionally, the address of a Charging Gateway Function. The
interpretation of the profiles and their associated behaviors can be different for each
Public Land Mobile Network (PLMN) operator and are not subject to standardization.
Neither the profile contents nor its behavior are defined in HLR. Only the identifier for
these data is defined and stored in HLR.
The HLR supplies the SGSN with the complete charging characteristics data (Subscriber
and/or PDP Context Charging Characteristics) and, upon activation of a PDP Context,
the SGSN forwards this information to the GGSN. The Charging Characteristics data is
used in the GSNs to activate and control the CDRs.
This feature has been enhanced as follows:
The Charging Characteristics to be currently subscribed in HLR explicitly points out to

one or any combination of the below charging methods:
l Normal charging

l Prepaid charging
l Flat rate charging
l Hot billing
This data will be now substituted by the reference to a profile, where the charging criteria
for each CDR type are defined. It is the responsibility of the operator to exactly define
the meaning of the profile bits making them compatible with the above handling of the
charging data in HLR.
Furthermore, it is possible to subscribe a reference to a specific behavior in the GSN in

connection with the subscribed charging profile.
The enhancement of this feature will provide the operator with a powerful tool to control
charging functions within its Home PLMN.
3.28 ZWF-05-10-028 Regional Subscription

Restriction (ZoneCode) Service
3.28.1 Summary
This feature is also called fixed cellular subscriber. This feature enables operators to
restrict network access of a subscriber to a certain location area.
3.28.2 Benefits
For operators
This feature provides effective control over subscriber access.
3.28.3 Description
For this function, the CCNDC allowing/restricting subscriber roaming and the ZoneCode
are set. Each subscriber in HLR can register a maximum of 10 CCNDCs and 10
ZoneCodes for each CCNDC.
At HLR level, the data for regional subscription are fully re-used.
The subscriber is created with a regional subscription by attaching one Regional

Subscription Zone Identity List (RSZIL) to the subscriber.

The RSZIL is defined by a PLMN code and a list of Zone Codes (ZC). In this case the
PLMN code is the country code of the HPLMN and the ZC shall be unique: this ZC will
be the subscriber's Fixed Zone. The standard controls for regional subscription are done
on the RZSZIL in the HLR.
The HLR sends the regional subscription data to the VLR as usual.
3.29 ZWF-05-10-029 PLMN-specific Supplementary

Service
3.29.1 Summary
The feature supports the subscription of supplementary service of operator specific, so

that the operator can provides the customized supplementary service that is non-
specification defined.
3.29.2 Benefits
For operators
Operator can customize some simple logic supplementary services.
3.29.3 Description
There are 15 of reserved operator specific supplementary service Code (SSCode) in

GSM specification for the operator defining own supplementary service. The range of
SScode is between 241 and 255. The feature supports the subscription information
management of supplementary services customized by the Operator. And that provides
simple service logic configuration for the operator provisioning customized
supplementary service logic.
3.30 ZWF-05-10-030 OSB

Specification:

3.30.1 Summary
The fourfold of the OSB Service is supported by the HLR, for each PLMN specific ODB
service, it is corresponding to the calling right and a calling number list respectively,
which lists an allowed calling number range of the PLMN specific ODB service.
3.30.2 Benefits
For operators
The operator can customize own calling number list for subscribers to control the calling
range of the subscriber.
3.30.3 Description
Total of fourfold OSB service can be subscribed by service provision interface, each
subscriber can own multi OSB service of the fourfold simultaneously.
For each calling number list, the Query, Add, Delete, Modification can be performed by
the configuration in HLR. The capacity of the calling number list is items of 1000, the
calling numbers in each of fourfold OSB calling number list either can be allowed or be
barred.
When a subscriber roams into a VPLMN, the OSB service information is also inserted
into the VLR of the VPLMN. If the VPLMN doesn’t support the OSB service, the OSB
service attribute value, which is corresponding to the subscriber who has subscribed the
OSB service, is void and the subscriber roaming barring is implemented in VPLMN
which doesn’t support the OSB by using roaming schema.
When the subscriber who has subscribed the OSB service attempts calling forward, if
the forward calling number matches the calling number listed in the OSB calling number
list which calling attribute has set as “Allowed Number”, then calling forward is
successful.
When the subscriber who has subscribed the OSB service attempts calling forward, if
the forward calling number doesn’t match the calling number listed in the OSB calling
number list which calling attribute has set as “Prohibited Number”, then calling forward is
successful.
3.31 ZWF-05-10-031 SMS Router

Specification: TS 29.002 23.840

3.31.1 Summary
ZXUN USPP (HLR) supports SMS Router function. HLR can transfer SRI_For_SM
message to SMS Router according to the follow preconditions:
1. SRI_For_SM message comes from a specific SMSC;
2. If needed, subscriber can subscribe this service.
3.31.2 Benefits
For operators
Operators can deploy a SMS Router in the network to monitor short message which
comes from specific SMSCs and gives good service to end-users.
For end-users
End user can subscribe such service to get more valued services, such as SMS transfer,
Prevention of SMS Fraud,etc.
3.31.3 Description
HLR supports Transparent Mode and Non-Transparent Mode MT SM Delivery Message.
Figure 3-1 New MT SM Delivery Message Flow in Transparent Mode

VPLMN of Recipient HPLMN of Recipient HPLMN of Originator
MSC/VLR SMS
MS HLR SMS-GMSC SMS
or SGSN Router
Short Message
(3GPP TS 23.040 [4])
MAP_SRI_FOR_SM
(3GPP TS 29.002 [5])
1
MAP_SRI_FOR_SM
(3GPP TS 29.002 [5])
MAP_SRI_FOR_SM
(3GPP TS 29.002 [5])
MAP_SRI_FOR_SM
ack
(3GPP TS 29.002 [5])
MAP_Inform_SC
(3GPP TS 29.002 [5])
MAP_SRI_FOR_SM ack
(3GPP TS 29.002 [5])
MAP_Inform_SC
(3GPP TS 29.002 [5])
MAP_MT_Forward_Short_Message
(3GPP TS 29.002 [5])
(See Note)
4
MAP_MT_Forward_
Short_Message
Page (3GPP TS 29.002 [5])
(3GPP TS 48.008 [6])
Page response
(3GPP TS 48.008 [6])
Short Message
(3GPP TS 24.011 [7])
Short Message ACK

(3GPP TS 24.011 [7]) MAP_MT_Forward_
Short_Message ACK
(3GPP TS 29.002 [5])
5
MAP_MT_Forward_Short_Message ACK
(3GPP TS 29.002 [5])
Short Message ACK
(3GPP TS 23.040 [4])
MAP_Report_SM_
Delivery_Status
(3GPP TS 29.002 [5])

ÿÿ
Figure 3-2 New MT SM Delivery Message Flow in Non-Transparent Mode
VPLMN of Recipient HPLMN of Recipient HPLMN of Originator
MSC/VLR SMS
MS HLR SMS-GMSC SMS
or SGSN Router
Short Message
(3GPP TS 23.040 [4])
MAP_SRI_FOR_SM
(3GPP TS 29.002 [5])
MAP_SRI_FOR_SM
(3GPP TS 29.002 [5])
2
MAP_SRI_FOR_SM
(3GPP TS 29.002 [5])
MAP_SRI_FOR_SM ACK
(3GPP TS 29.002 [5])
3
MAP_SRI_FOR_SM ACK
(3GPP TS 29.002 [5])
MAP_MT_Forward_Short_Message
(3GPP TS 29.002 [5])
(See Note)
4
MAP_MT_Forward_Short_Message ACK
MAP_MT_Forward_ (3GPP TS 29.002 [5])
Short Message ACK
Short_Message
(3GPP TS 23.040 [4])
Page (3GPP TS 29.002 [5])
(3GPP TS 48.008 [6])
Page response
(3GPP TS 48.008 [6])
Short Message
(3GPP TS 24.011 [7])
Short Message ACK

(3GPP TS 24.011 [7]) MAP_MT_Forward_
Short_Message ACK
(3GPP TS 29.002 [5])
5
MAP_Report_SM_
Delivery_Status
(3GPP TS 29.002 [5])
(Conditional)
MAP_Report_SM_
Delivery_Status ACK
(3GPP TS 29.002 [5])
(Conditional)

ÿÿ
3.32 ZWF-05-10-032 Forward Number Format

Transform Function
Specification:
3.32.1 Summary
ZXUN USPP (HLR) support forward number format transform function.
3.32.2 Benefits
For Operators
Provide flexible call forward service for the operators.
For end users
Provide simple method for the user to register the forward number, improve user
experience.
3.32.3 Description
When the user register national format forward number, HLR transform the number to
international format forward number automatically. HLR add different CC to the number
according the number prefix.
When the user register PSTN forward number, HLR add CC and region code to the
number automatically. IF there are multi-local network subscribers in the HLR, HLR add
different region code to the PSTN forward number according the different local network
that the user resides.
3.33 ZWF-05-10-033 STYPE(Support for

Subscription Type Dependent Analysis in HLR)
This feature is: OPTIONAL
Specification:

Commercial Attention: V3.0
Dependencies: NULL
3.33.1 Summary
The aim of this feature is to introduce a mechanism to enable support for subscription
type dependent analysis in the MSC/VLR, GMSC and HLR. This function can be used
by the network operator to implement various operator specific services.
3.33.2 Benefits
The Operators
The operator can have service differentiation capabilities without using the
IMSI/MSISDN series, so IMSI/MSISDN numbers are not wasted for this purpose.
The operator can offer different types of charging for different types of subscribers at any
time.
The feature offers an extra branching per subscriber in routing and charging analysis.
The feature can be used in both IN and non IN calls.
For End-users
Great value for the end-users because they can get different tariff types according to
their subscription types and those tariffs can be easily changed without involving
MSISDNs.
3.33.3 Description
The new Subscription Type has the value range 0 - 127. It is possible to assign and
store any of the values to each subscriber.
HLR will store and update the Subscription Type in the MSC/VLR by the operations
InsertSubscriberData and DeleteSubscriberData.
HLR will transfer the Subscription Type to the GMSC at routing interrogation by the
operation SendRoutingInformation_response.

HLR provides the mechanism to control the delivery of Subscription Type while updating
the subscriber data to the subscriber’s located VLR, depending on the defined
Subscription Type capabilities of the VLR in the HLR.
3.34 ZWF-05-10-034 HSCSD

3.34.1 Summary
HLR supports HSCSD service.
3.34.2 Description
Currently the GSM Bearer Services are only available for fixed user rates. For instance
the Bearer Service BS 26 is an asynchronous data service with a user rate of 9600 bps.
A subscriber wanting to subscribe to different asynchronous data services needs to
subscribe to a set of these bearer services, e.g. BS 21, BS 24 and BS 26.
The General Bearer Services are defined independent of a fixed nominal user rate.
These General Bearer Services are defined in the scope of "High Speed Circuit
Switched Data" to cover all user rates including the already existing ones. Therefore the
General Bearer Services are also applicable to user rates up to 9600 bps and can also
be provided without implementing higher user rates.
The General Bearer Services are a mandatory prerequisite for the introduction of
HSCSD. By administrating the subscriber with General Bearer Services in the HLR the
subscriber gets access to the higher data rates provided by HSCSD, which range up to
28.8 Kbit/s.
The General Bearer Services supported with this sales feature are:
BS 20 for asynchronous data services
BS 30 for non-transparent synchronous data services
BS 40 for dedicated PAD services
The General Bearer Services also cover the existing Bearer Services, which are already
implemented via the following mapping:
BS 20 covers the asynchronous data services BS 21-26

BS 30 covers the non-transparent synchronous data services BS 32-34 NT
BS 40 covers the dedicated PAD services BS 41-46
A user subscribed to a General Bearer Service is also subscribed to all individual single
services of the group as listed above.

3.35.1 Summary
CAMEL (Customized Applications for Mobile network Enhanced Logic) is a network

feature contained in the GSM and IN (Intelligent Network) network entities. When a
subscriber having registered the CAMEL service is roaming or called, these feature data
will be transferred between HPLMN and VPLMN so that SSP can trigger the
corresponding intelligent services for the subscriber.
3.35.2 Benefits
For operators
With support of the CAMEL functions in HLR, operators can start subscription of
intelligent service subscribers immediately, use the flexible IN service configuration
modes, make it more flexible and convenient to add new services or features, and make
use of many existing IN features (e.g., familiarity number, prepaid feature and
information desk services) immediately to reduce the subsequent equipment investment
costs.
For end-users
The end users benefit from the diversified intelligent services provided by HLR, such as
the familiarity number, information desk services and AOC.
3.35.3 Description
HLR supports the following CAMEL2 functions:
l Supporting CAMEL Phase 2 subscription data, including:
O-CSI (Originating CAMEL Subscription Information)

T-CSI (Terminating CAMEL Subscription Information)
U-CSI (USSD CAMEL Subscription Information)
SS-CSI (Supplementary service invocation CAMEL Subscription Information)
TIF-CSI (Translation Information Flag)
l Supporting CAMEL2 subscription data download and synchronization to/with the

visited network.
l Supporting the J interface signaling flow with gsmSCF, including:
Any Time Interrogation (ATI)
Supporting trigger detection of the related static trigger detection point by the call
termination routing process
3.36 ZWF-05-10-036 Barring of All Outgoing Calls

when Roaming Outside HPLMN Country (BORO)
Specification: 3GPP 29.002 ETSI 12.08
3.36.1 Summary
When a subscriber of the service roams outside HPLMN country, the service bars all
outgoing calls.
3.36.2 Benefits
For operators
Through the BORO service, the carrier can conveniently bar all outgoing calls.
3.36.3 Description
When a subscriber roams within the HPLMN country, the activated BORO service has
no impact on the subscriber. When the subscriber roams outside the HPLMN country,
the activated BORO, similar to the activated BAOC service, bars all outgoing calls of the
subscriber.

The BORO service is not a standard supplementary service. There is no allocated

supplementary service code for it. The subscription, registration, and deregistration
operations for the service can only be accomplished by the operator.
3.37 ZWF-05-10-037 CB Password under Subscriber

Control
3.37.1 Summary
This feature gives the possibility to determine, at subscription, if a password is required

for enabling or disabling call barring at the MS level.
3.38 ZWF-05-10-038 CB Password under Operator

Control
Specification: 3GPP22.088 23.088
3.38.1 Summary
This feature gives the possibility at subscription time and for each barring category,
whether call barring may be active/deactived at the operator level.
3.39 ZWF-05-10-039 Authorized Calling Number Call

to Incoming-barred Subscriber
Specification:
3.39.1 Summary
If a subscriber is barred from incoming call because of ODB or SS CB, some authorized
calling number can call to him successfully.

3.39.2 Benefits
For operators
Operators can call to these subscribers by some authorized calling number to inform him
when he is no charge or else.
3.39.3 Description
GMSC should include calling number in SRI message.
HLR sets a list of authorized calling numbers which can call to such subscribers. When
HLR receives SRI message from GMSC, it judges the calling number is in the authorized
calling numbers list, whether the subscriber is barred, HLR continues the call procedure
forever.
3.40 ZWF-05-10-040 Fax Services

Specification: 3GPP 23.008 22.003 22.001 22.003 27.001 27.003 29.007
ITU-T T.30, T4
3.40.1 Summary
This feature makes it possible to subscribe to the Fax Service.
Two different subscription alternatives are supported:
l Teleservice 62 (TS62), the Automatic Facsimile Group 3 Transparent Service
l Teleservice 61 (TS61), alternation between speech and fax within one call
3.40.2 Description
This feature makes it possible to add or remove fax subscription data in the subscriber
profile, along with other Bearer, Tele- or Supplementary Services that are stored in the
HLR. Two different subscription alternatives are supported, Teleservice 61 and
Teleservice 62.
Teleservice 62 (TS62) allows transparent fax group 3 connections between GSM

subscribers and group 3 machines in any network (GSM, PSTN, and ISDN).

Teleservice 61 (TS61) supports transparent fax group 3 calls and alternation between
speech and fax. With speech/fax alternation, subscribers can start with a speech or fax
call, switch to either fax or speech and then switch back to the original call type.
Both mobile originated and terminated fax calls are supported.
In order to support fax calls, the network must have an Interworking Function (IWF) that
handles fax adaptation between the GSM network and external networks, including the
provision of fax modems.
Normally, one individual Additional MSISDN (AMSISDN) has to be allocated in the HLR
for each subscriber requiring fax services. The AMSISDN is connected to the specific fax
service and has to be used for all terminating fax calls. This means that a mobile user
with both voice and fax subscription needs two MSISDN and the person calling the
subscriber must know both numbers.
For incoming fax calls from a pure ISDN network, the ISDN Bearer Capability (BC) is
included in the ISUP set-up message. The ISDN BC indicates that the call is a fax call,
which makes it possible for the GSM network to allocate the needed fax resources, i.e.
the DTI. However, in a normal situation where the fax call is originated from a PSTN
subscriber, the ISDN BC does not contain any information about the call type. This
means that the GSM network has no indication whether this is a fax call or a normal
voice call. For this reason an Additional MSISDN must be allocated for fax services.
The HLR takes part in the call set-up for mobile terminating calls, while the MSC handles
the call set-up for mobile originating calls. In the case of a MT call, the receiving GMSC
sends a request for routing information to the HLR in order to locate the subscriber. In
the HLR a check is made to determine if the received B-number is an Additional
MSISDN. If so, the HLR checks which BC it is connected to. When the call is ISDN
initiated, the received ISDN-BC is translated into a GSM-BC. A check is made to
determine if the called subscriber has a subscription for this service.
3.41 ZWF-05-10-041 PLMN-specific Teleservice

3.41.1 Summary
HLR supports PLMN-specific TS1 to PLMN-specific TSF.

3.41.2 Description
This feature makes it possible to subscribe to PLMN-specific telecom services:
PLMN-specific TS1;
PLMN-specific TS2;
PLMN-specific TS3;
PLMN-specific TS4;
PLMN-specific TS5;
PLMN-specific TS6;
PLMN-specific TS7;
PLMN-specific TS8;
PLMN-specific TS9;
PLMN-specific TSA;
PLMN-specific TSB;
PLMN-specific TSC;
PLMN-specific TSD;
PLMN-specific TSE;
PLMN-specific TSF
3.42 ZWF-05-10-042 Different Qos in different

VPLMN
Specification:
3.42.1 Summary
ZXUN USPP(HLR) inserts different Qos to different SGSN according to the system
configuration.

3.42.2 Benefits
For operators:
Operators can design different Qos control scheme according to their agreement.
3.42.3 Description
A Qos mapping table is designed in ZXUN USPP(HLR) to perform such function.When

subscriber roams to a VPLMN,HLR inserts new Qos to SGSN according the table and
which Qos is subscripted by the subscriber.
3.43 ZWF-05-10-043 UMTS R99-CS Data Service --

Non-transparent (NT) Data Service
Specification:
3.43.1 Summary
The NT data service requires the support of the BS20 asynchronous transparent bearer
service group as defined in GSM standards. In GSM, the operator can attribute specific
data bearer services to the subscriber, such as the BS22 or BS31 service. For UMTS
services however, operators do not attribute individually defined bearer services. UMTS
operators attribute NT data bearer services to subscribers as a group of services
(GBS20).
Bearer Mode FNUR Information Transfer Quality of
Service Capability Service
BS20 Asynchronous 9.6 Kbit/s 3.1 kHz UDI NT
14.4 Kbit/s 3.1 kHz UDI
38.4 Kbit/s UDI
BS20, in 3.1 kHz audio, provides autobauding for Fixed Network User Rate (FNUR) from
9.6 to 28.8 Kbit/s, with modem V.32, V.32bis and V.34, by the mean of the Inter-Working
Function.
In another form:
In UDI: FNUR=9.6, 14.4, 19.2, 28.8 and 38.4kbit/s.

In 3.1kHz audio ex. PLMN:
modem V.32, FNUR=9.6kbit/s
modem V.32bis, FNUR= 9.6, 14.4 kbit/s
modem V.34, FNUR= 9.6, 14.4, 19.2, 28.8kbit/s
autobauding: FNUR=2.4 to 33.6kbit/s
3.44 ZWF-05-10-044 SMS Alert Service (Miss Call)

3.44.1 Summary
If a called subscriber is power off or out of service area, when the subscriber is power on,
network can initiates a short message to calling subscriber to notice the called
subscriber has been power on.
3.44.2 Benefits
A subscriber can get the power status information about the called subscriber, who
needn’t to re-attempt to call the called subscriber. The function can provide much better
service experience to subscribers and make revenue increase of the operator.
3.44.3 Description
The service flow of the called subscriber status notice service is described as below:
The calling subscriber initiates a call to a called subscriber;
the calling party MSC requires the subscriber status information to called party HLR
if the called subscriber is power off or out of service area and no forward number is
subscribed, the calling party MSC reroute the call to the “Global Calling Platform” by the
forward number returned by HLR/AUC;
in the “Global Calling Platform”, it fetches the calling number from the “IMA” message
and identify whether the subscriber has subscribed the “called party status notice”
service or not, if not, the Platform identify called subscriber whether who has subscribed

the “Global Calling” service or not and decides whether “Global Calling” service
procedure is triggered or not; if the calling party has subscribed the “called party status
notice” service, the service platform send the specific short message “0X40” to called
party SMC and play announcement to calling subscriber, such as “Your dialed
subscriber has been power off, if he or she is power on, we shall send a short message
to you”;
Called Party SMC sends the specific short message “0X40” to called MS;
if Called MS receives the specific short message, it returns its status information to the
Called Party SMC;
Called Party SMC forwards the status information to the service platform;
after received the status information from the Called Party SMC, it generate a “status
information notice” message and send to the Calling Party SMC;
The Calling Party SMC sends the “status information” to the calling subscriber.
3.45 ZWF-05-10-045 Black List and White List of

Forward (OFA)
3.45.1 Summary
Black list and white list of forward define the allowable forward number and the barring
forward number of subscriber.
3.45.2 Description
Using Black list and white list of forward, operator can control the subscriber forwarding
number.
The allowable forward number list and the barring forward number list have been
configured in the HLR. Providing the black list and white list to the subscriber will be
controlled.
The HLR support 255 black lists and white lists.

3.46 ZWF-05-10-046 Service Change and UDI/RDI

Fallback (SCUDIF)
3.46.1 Summary
HLR supports Service Change and UDI/RDI Fallback (SCUDIF).
3.46.2 Benefits
For operators
This service can automatically convert a video call into a common call when the
conditions of a video call cannot be satisfied. It can improve the call completion
rate between 3G subscribers and the subscriber's satisfaction level.
End-users
This service can automatically convert a video call into a common call when the
conditions of a video call cannot be satisfied, simplifying the subscriber's
multi-media service operation.
3.46.3 Description
The Service Change and UDI Fallback (SCUDIF) is a function which applies to UDI/RDI
multimedia calls, and shall support the following:
l Fallback to speech during call setup: allow a user to attempt to set up a multimedia
call, and try a speech connection if the former doesn't succeed;
l Fallback to the less preferred service (speech or multimedia) during call setup:
allow the terminating side via specific settings for this service in the terminal to
accept or reject a multimedia call, without interrupting the call setup;
l Fallback to the preferred service (speech or multimedia) or speech during call setup:
allow the call setup to proceed with a single service if the transit network does not
support the signaling of this functionality;

l BC negotiation at the terminating side: allow the terminating side via specific
settings for this service in the terminal to turn a speech call (with service change)
into a multimedia call and vice-versa;
l Service change: allow a speech call to be turned to multimedia by either of parties,

and back to speech, through a successful in call modification procedure;
l Allow any of the users to reject a multimedia request from the other party while in
speech mode.
l Network-initiated service change: The network shall initiate a service-change from

multimedia to speech during the active call if a multimedia call can no longer be
supported. If a multimedia call can again be supported at a later point in time, the
network may initiate a service change from speech to multimedia.
This functionality is not supported for multimedia with Fixed Network User Rate set to 32
Kbit/s. In this case, the MSC shall revert to a multimedia only call.
3.47 ZWF-05-10-047 User-to-User Signaling (UUS)

3.47.1 Summary
The UUS supplementary service allows the served subscriber to send/receive a limited
amount of subscriber generated information to/from another user in association with a
call to the user. This information shall be passed transparently (i.e. without modification
of contents) through the network. Normally, the network shall not interpret or act upon
this information.
3.47.2 Description
The served subscriber can send and receive UUI in different phases of the call
depending on the service(s) to which the subscriber subscribes. These services are:
l Service 1: UUI can be sent and received during the origination and termination of
a call, with UUI embedded within call control messages. The service 1 can be
activated implicit by inserting UUI when set-up a call or explicit with an appropriate
procedure.
l Service 2: UUI can be sent and received after the served subscriber has
received an indication that the remote party is being informed of the call and prior to

the establishment of the connection. UUI sent by the served subscriber prior to
receiving the acceptance of the call by the remote party, may as a network option
be delivered to the remote party after the call has been established. The service 2
shall be activated explicitly.
l Service 3: User-to-user-information can be sent and received only while the

connection is established. The service 3 shall be activated explicitly.
Service 1, service 2 and service 3 shall allow the transmission of UUI with the maximum
length of 128 octets per message.
3.48 ZWF-05-10-048 Operator Specific Barring

3.48.1 Summary
The feature supports the subscription of operator specific barring, so that the operator
can provide customized barring that is non-specification defined.
3.48.2 Benefits
For operators
Operator can customize some simple logic barring.
3.48.3 Description
There are four operator specific barring defined in GSM specification.
u When registered in the HPLMN, Operator Specific Barring (Type 1);
u When registered in the HPLMN, Operator Specific Barring (Type 4).
The implementation of operator specific barring is defined by operator.
For example, it may be applied to barring certain outgoing calls or barring of registration
of a call forwarded-to number, etc.

If operator specific barring is used for barring certain outgoing calls, it is invoked in the
VLR. Specific numbers that should be barred are defined in VLR. HLR inserts the
subscription to VLR during location update. While the subscriber makes an outgoing call,
VLR checks if the dialed number is permitted, if not, the outgoing call is barred.
If operator specific barring is used for barring of registration of forwarded-to number, it is

invoked in HLR, Specific forwarded-to numbers that can be registered or can not be
registered are defined in HLR. If the subscriber registers a forwarded-to number, HLR
checks the number is in the permissive list, if not, the registration is failed.
3.49 ZWF-05-10-049 Multimedia Coloring Ring Back

Tone
Specification:
3.49.1 Summary
ZXUN USPP (HLR) support multimedia Coloring Ring Back Tone defined by CMCC.
3.49.2 Benefits
For operators
Provide users with multimedia Coloring Ring Back Tone, can increase income of
operators.
For end-users
Can use multimedia Coloring Ring Back Tone.
3.49.3 Description
After applying for the personalized ringback tone service via the special service hotline,
voice interactions, business hall or WAP, a called subscriber can customize
personalized ringback tones by means of WWW, WAP or dial-up of the access code.
Then, when this subscriber is called, the customized personalized music or DIY
recording that replaces the ordinary ringback tone can be played to the caller according
to such conditions as different calling numbers, called home area and specific time set
by the called party

ZXUN USPP (HLR) support use SS_CODE (252) to identify multimedia Coloring Ring
Back Tone service.
3.50 ZWF-05-10-050 ADD (Auto Device Detect)

Specification:
3.50.1 Summary
The ADD server stores the type and configuration of user equipment (UE). If the HLR
detects the change of the IMEISV, IMSI, or subscription data, it sends the subscriber
information and UE information to the ADD server, which then automatically sends the
configuration data to the UE.
3.50.2 Benefits
For operators
The ADD function simplifies the operations of the subscribers who use the data services,
and thus increases the customer satisfaction.
End-users
The ADD function facilitates subscribers to use new services. Instead of conducting the
complicated network setting, subscribers can use services directly after they change
their SIM or USIM cards or UEs. For example, the ADD function allows the GPRS
service data to be automatically set on the MS before a subscriber uses the GPRS
service. As a result, subscribers are more willing to use new data services.
3.50.3 Description
HLR store IMEIsv in HLR data base. When HLR receive location update message, HLR
compare the IMEIsv of location update message with the IMEIsv of data base. If there is
an IMEIsv mismatch or first time occurrence of IMEIsv for the subscriber then a
MML/SOAP will be composed and sent to OTA server. The MML will contain
IMSI/IMEIsv/MSISDN, etc.
HLR provide query MML. OTA server can query IMEIsv information from HLR using
query MML/SOAP.

3.51 ZWF-05-10-051 VBS

Specification:
3.51.1 Summary
HLR supports VBS Service.
3.51.2 Benefits
For operators
With this service supported, the operator can provide the group-call service to exploit
new latency customers.
For end-users
The VBS service enables the customer to call as a broadcast call to.
3.51.3 Description
The VBS enables a calling subscriber to send speech unidirectional and simultaneously
to all entitled dispatchers and to destination subscribers belonging to a predefined group
call area who have a subscription to the applicable group ID.
3.52 ZWF-05-10-052 VGCS

Specification:
3.52.1 Summary
HLR supports VGCS service.
3.52.2 Benefits
For operators
Operators can develop some real-time-charge services based on the hot billing function,
such as line lease service.

For end-users
The VGCS service enables the customer to call not only one subscriber simultaneity.
3.52.3 Description
VGCS (Voice Group Call Service) makes one or more groups a subscriber may be a
member of for voice group calls. And it allows speech conversation of a predefined
group of service subscribers in half duplex mode on the radio link taking into account
multiple subscribers involved in the group call per cell.
3.53 ZWF-05-10-053 HSDPA

3.53.1 Summary
HLR support Maximum bit rate for downlink of QoS in GPRS profile to be extended to
16Mbps. HLR support Guaranteed bit rate for downlink of QoS in GPRS profile to be
extended to 16Mbps.
3.54 ZWF-05-10-054 HSUPA

3.54.1 Summary
ZXUN USPP (HLR) support HSUPA.
HLR support Maximum bit rate for uplink of QoS in GPRS profile to be extended to
8640Kbps. HLR support Guaranteed bit rate for uplink of QoS in GPRS profile to be
extended to 8640Kbps.

3.55 ZWF-05-10-055 TD-SCDMA Hand Over

Function
Specification:
3.55.1 Summary
ZXUN USPP (HLR) support TD-SCDMA hand over function. If the subscriber has two
handsets, one is TD-SCDMA handset, the other is GSM handset. TD-SCDMA USIM
card register in TD-SCDMA network. GSM SIM card register in GSM network. When TD-
SCDMA handset roams into GSM wireless network cover area, the on-going call will be
handed over to GSM handset.
3.56 ZWF-05-10-056 2G/3G Roaming Mobility

Managing Function
Specification:
3.56.1 Summary
ZXUN USPP (HLR) support 2G/3G Roaming Mobility Managing Function.
3.56.2 Description
When the subscriber roaming into visited network, HLR can distinguish number rang of
VMSC Server/VLR belong to 3G or 2G. When 3G subscriber roam to GSM network, ISD
message not include subscription information of 3G, for example CSARP/BS20/BS30.
When HLR insert BS17 (general-dataCDA) into VLR, if GSM VLR unsupport BS17, the
VLR will return BS17 to HLR in ISD response message. HLR should replace BS17 with
BS16 (dataCDA-9600bps), and insert BS16 into VLR again.

3.57 ZWF-05-10-057 CNAP

Specification:
3.57.1 Summary
The CNAP supplementary service enables the called party to receive the calling name
information of the calling party.
This supplementary service provides for the ability to indicate the name information of
the calling party to the called party at call set-up time for all incoming calls.
3.57.2 Benefits
For operators
This service helps operators to attract more subscribers and improve competitive edge.
End-users
Subscribers can learn about the information about the calling party without setting the
Contact on the MSs.
3.57.3 Description
The CNAP service is a supplementary service provided to the called subscribers.When

the CNAP service is provided to a subscriber, the service data is sent to the VLR.When
the subscriber is called, the contact information about the calling party is presented to
the subscriber.
3.58 ZWF-05-10-058 Multicall

Specification:
3.58.1 Summary
HLR supports Multicall service.

3.58.2 Benefits
For operators
Operators can provide the MC service as a value-added supplementary service for

subscribers.
End-users
When both the MS of a subscriber and the network support the MC service, the
subscriber can set up multiple ongoing calls in the CS domain. The number of calls is
jointly determined by the parameters set on the MS, mobile network and the parameters
set by the carrier and the subscriber. A maximum of seven calls can be set up.
3.58.3 Description
The Multicall supplementary service enables a mobile subscriber to have several

simultaneous CS calls, each call using its own dedicated bearer.
Only one CS bearer can be used for speech at any one time.
A speech call is one of TS11 (Telephony), TS12 (Emergency Calls), and TS61
(Alternate speech/fax).
It shall be possible for each CS call to use a dedicated bearer of independent traffic and
performance characteristics. It shall be possible to release each active CS call
independently of any other CS calls.
3.59 ZWF-05-10-059 Selective Granting of Services

on per VPLMN
Specification:
3.59.1 Summary
The ZXUN USPP (HLR) provides different services in different VPLMN.
3.59.2 Benefits
For operators
Operators can design different services in different VPLMN according their agreement.

3.59.3 Description
HLR can set a service control scheme for each subscriber, each service control scheme
can set different service to be controlled in different VPLMN. HLR allows or forbids such
service according to the scheme.
The services to be controled are as follows:
1. speech,outgoing
2. speech,ingoing
3. emergence call
4. MO SMS
5. MT SMS
6. Fax
7. CDS
8. CDA
9. PDS
10. padAccessCA
11. allAlternateSpeech-DataCDA、allAlternateSpeech-DataCDS、
allSpeechFollowedByDataCDA、allSpeechFollowedByDataCDS
12. ODB
13. ARD
14. CFU
15. CCF（including CFB,CFNRc,CFNRy）
16. CUG
17. LCS
18. RCTYPE
19. STYPE
20. eMLPP
21. USSD
22. specific subscriber type
23. CS-ARP
24. CD
25. CLIP
26. CLIR
27. COLP
28. COLR
29. CW
30. HOLD

31. MPTY
32. UUS
33. ECT
34. AOCC
35. AOCI
36. ARP（default value will be inserted when it is controlled）
37. CNAP
38. MultiCall
39. GPRS
40. different CSI
3.60 ZWF-05-10-060 2G Softswitch Fax (Including

CSD) Service Solution
Specification:
3.60.1 Summary
In traditional TDM network, the voice and fax among VMSCs adopts G.711 code.
According to the uniform technical requirements from China Mobile, voice beared by IP
in CN shall adopt AMR2 12.2k code, which is compressed code and cannot be used for
fax (or CSD) service. The 2G soft switch fax (including CSD) solution aims to realize
smooth introduction from fax (including CSD) in TDM network to R4 soft switch network
After HLR receives SRI, it should add TS62 subscription to SRI_ACK message which
returns to the originated VMSC.
VMSC shall judge the call as fax service (TS62) according to subscription information in
SRI_ACK returned by HLR, apply IWF and select TDM outgoing circuit.
3.61 ZWF-05-10-061 RDI

Specification:

3.61.1 Summary
HLR supports RDI service. The function of RDI (redirection index): When postpaid
subscriber is out of charge, RDI flag will be set for the subscriber, HLR inserts RDI to
MSC/VLR. When the subscriber makes a call, he will be informed that he is out of
charge. Then the platform will delete RDI for the user, the user can make call as usual.
3.61.2 Description
Figure 3-3 RDI function
ZXUN USPP (HLR) supports:
l Set/Delete RDI for a user;
l Insert RDI to VLR through Location_update, Insert_Subscriber_Data, Restore Data;
l RDI can be sent to VLR only when user is roaming in HPLMN.
3.62 ZWF-05-10-062 Multi-SIM

Specification:

3.62.1 Summary
ZTE HLR supports Multi-SIM which allows 1-5 SIMs sharing one common MSISDN.
3.62.2 Description
The main feature for Multi-SIM includes:
l Each subscribers/account may have 1-5 SIMs in different handset; Each SIM can
be actived/deactived by standalone. Each SIM can own different services.
l One of the SIM's MRT will be defined as Primary MRT;
l Primary MRT will be defined as common MSISDN in all other SIMs in HLR;
l Primary MRT will be the CLI in MOC in local network (It cannot work in outbound
case, this is a known issue as it is proprietary feature);
l Whenever the subscriber picks up one of the handset, he is required to declare

"on-duty" by sending a special USSD code to USSD server. While USSD server will
use RCF platform to setup a CFU in Primary MRT to forward all calls to “on-duty”
SIM;
l SMS call forward within Multiple SIM cards / group is allowed. It means that all
SMS will be delivered to “active” SIM card;
l When Multi-SIM subscriber roams in HPLMN, ZTE HLR inserts two MRT to VLR
and SGSN;
l When Multi-SIM subscriber roams out of HPLMN, ZTE HLR only inserts its own
MRT to VLR and SGSN, doesn’t insert its common MRT;
l Primary MRT subscriber can register CFU using his own mobile; in this case, this
CFU information will override Multi-SIM information;
l The subscribers in the same Multi-SIM group can be distributed to the same or
different HLR.

3.63 ZWF-05-10-063 QoS Profile

Specification:
3.63.1 Summary
ZTE HLR Supports QoS profile;
3.63.2 Description
Same user with different APN can correspond to different QoS Profile.
Different user with same APN can correspond to different QoS Profile.
When the QoS is changed for a user, it needs only to change its QoS Profile ID.
3.64 ZWF-05-10-064 ALS

Specification:
3.64.1 Summary
HLR supports ALS function(also called Auxiliary Speech).
3.64.2 Benefits
For operators
This functionality is not standardized by GSM, and represents a value to the operator in
competition: an operator concerned about their attractiveness and image towards the
business end-user segment.
This service will result in more traffic, some to a high charge, some to a lower, and in
more subscribers, attracted by the opportunity of combining business and private phone
calls on the same mobile telephone.
For end-users

The end-user will have the possibility to use the same mobile station subscription for two
different purposes, meaning two separate accounts. This could for instance be of great
interest for subscribers using one business account and one private account.
When two people use the same subscription, the account could be separated per user.
This could for instance be useful in companies, where a common mobile station is used.
3.64.3 Description
The feature Alternate Line Service (ALS) allows a subscriber to have two different
MSISDNs and according user profiles by using only one handset.
The handsets need to support the functionality to distinguish such different calls and can
send out different signals to the subscriber.
The mobile which supports ALS has two Lines (Line1/Line2), user can use any one of
Lines to call out. When he uses Line1 or Line2, the ISDN displayed to the other side is
different. It can be billed by each ISDN.
Line2 is only used for voice, not for short message, data services, etc.
The teleservice defined for Line2 is called 'Auxiliary Speech', the basic service code is
TSD1.
The services that Line2 can subscript includes:
Supplement services:
l CLIP
l CLIR
l COLP
l COLR
l CFU
l CFB
l CFNRy
l CFNRc
l CFD
l CT
l CD

l CW
l HOLD
l MultiCall
l MPTY
l CUG
l AOCI
l AOCC
l UUS1
l UUS2
l UUS3
l BOAC
l BOIC
l BOICE
l BAIC
l BICR
l PLMNSpecificSS
ODB:
l barring of outgoing calls
l barring of premium rate calls
l barring of incoming calls
l operator specific barring category
l barring of supplementary service management
l barring of registration of forwarded-to number
l barring of invocation of call transfer

CAMEL:
l OCSI
l TCSI
l TIFCSI
l SSCSI
l DCSI
l VTCSI
Others:
l SSET
l RDI
The basic service included in Insert_subscriber_data message for Line2 is TSD1.
When ALS user roams to the network that doesn’t support ALS, Line2 data don’t be
included in Insert_subscriber_data message. In such case, someone call the user uses
Line2 number, ZTE HLR returns FacilityNotSupported error in SRI_Ack.
ALS service applies to MAP version 2 or above.
3.65 ZWF-05-10-065 Authentication Gateway

Specification:
3.65.1 Benefits
For operators
When the operator wants to swap the HLR/AUC that is used in the network, but the
operator can’t provide all ki information that is used in the network because the existing
AUC encrypt the Ki with the proprietary arithmetic. ZXUN USPP (HLR) supports the
function of authentication Gateway for resolving this problem. The unknown-ki is kept in

the existing HLR/AUC. ZXUN USPP (HLR) Authentication Gateway transfers the
authentication message between the existing HLR/AUC and MSC/VLR, so the SIM card
with unknown-ki can be authenticated.
3.65.2 Description
When all the subscriber data of existing HLR are migrated to the new HLR, all MAP
services except for authentication are processed by the new HLR. When the new HLR
receives authentication service, it judges whether ki is known by the new HLR. If ki is
known, the new HLR processes this authentication message. If ki is unknown, the new
HLR forwards this message to the existing HLR/AUC; it will be processed by the existing
HLR/AUC. In this case, the behavior of the new HLR is as a VLR. The messages that
need be transformed to the existing HLR include:
MAP_SEND_AUTHENTICATION_INFO,
MAP_AUTHENTICATION_FAILURE_REPORT, MAP_SEND_PARAMETER.
The service flows are as follows:
Figure 3-4 Authentication Gateway service flow

3.66 ZWF-05-10-066 SSET (Service Set)

Specification:
3.66.1 Benefits
For operators
With the SSET feature, the operator can define mobile intelligent network categories
services flexibly. For example, supports two Ringback Tone systems working in parallel.
SSET can be used to differentiate which Ringback Tone system is serving the user.
3.66.2 Description
SSET (Service Set) is a feature by which the operator can define mobile intelligent
network categories services flexibly. For example, supports two Ringback Tone systems
working in parallel. SSET can be used to differentiate which Ringback Tone system is
serving the user.
ZXUN USPP (HLR) supports:
l Assign different SSET value for different user;
l SSET can be sent to VLR through Location_update, Insert_Subscriber_Data,

Restore Data;
l SSET can be sent to VLR only when user is roaming in HPLMN.

3.67 ZWF-05-10-067 HSDPA+

Specification: 3GPP TS 23.060/23.107
3.67.1 Summary
ZXUN USPP (HLR) support HSDPA+.
HLR support Maximum bit rate for downlink of QoS in GPRS profile to be extended to
256Mbps. HLR support Guaranteed bit rate for downlink of QoS in GPRS profile to be
extended to 256Mbps.
3.67.2 Benefits
3.67.3 Description
3.68 ZWF-05-10-068 Welcome Message Service

Specification:
3.68.1 Summary
In out-bound roaming scenario, when UE starts Update Location Request, ZXUN USPP
(HLR) will detect whether the subscriber is in out-bound roaming. If HLR finds the
subscriber has already roamed abroad, it will generate the corresponding record in the
log file as per pre-set policy. HLR will send this log information to VAS via FTP. And VAS
sends the welcome message to the out-bound roamer.
3.68.2 Benefits
It ensures the operator to implement the welcome message service.

3.68.3 Description
HLR will generate the corresponding record in the log file as per pre-set policy. When
the number of records reaches 60, HLR will send this log information to VAS via FTP.
The threshold value of records is configurable by operator.
When UE is roaming aboard, there are 2 optional methods to catch the information:
(1) Detection based on CC, means for one overseas country, HLR only generates one
record;
(2) Detection based on CC+NDC, means for different VPLMN, the HLR generates
records;
(3) Detection based on VLR of VPLMN in the overseas country, means in out-bound
roaming scenario, when VLR of VPLMN is changed, the HLR in HPLMN will generate
one record. In this way, when subscriber travels from one city to another city in a foreign
country, it will receive another SMS again. The weakness of this solution is that the user
will receive a little more short message.
When the number of records in log file is reach up 60, or the file creating time is reach
up 60 minutes, the log file would be send to welcome message server.
3.69 ZWF-05-10-069 Short Message Forwarding

Specification:
3.69.1 Summary
ZXUN USPP (HLR) supports short message forwarding function.
3.69.2 Benefits
It ensures the operator to perform the short message forwarding function, it realizes
forwarding to C number, forwarding to SMS platform, or forwarding to a VAS service
platform to filtering short message jam.
3.69.3 Description
The HLR support subscription based SMS forwarding feature with Characteristics:
Upon provisioning of SMS Forwarding to a subscriber, it shall allow the setup of a

dedicated "Virtual VMSC address" in individual subscriber profile; if the dedicated Virtual

VMSC address is not available in the provisioning command, a system default “Virtual
VMSC address” shall be used;
With SMS Forwarding provisioned to the subscriber, instead of the true VMSC address
where the subscriber is currently located, HLR shall always return in the SRI_SM_Ack
the virtual VMSC address to the interrogating SMSC upon reception of SRI_SM towards
this subscriber; in avoidance of doubt, the HLR shall always return the true IMSI of the
subscriber;
But if SRI_SM is sent from operator specified calling addresses (can be defined in HLR),
HLR will response as normal with the true VMSC address.
Customers is not allow to change/interrogate/erase this virtual VMSC settings by

handset
The virtual VMSC address is a customer based record and can be defined by MML
The feature shall support AC Alert and Delivery Report while prevents all kinds of
looping
Subscribers can set short message service forwarded unconditional to another mobile
subscriber in the HPLMN.
For routing retrieving, if SMS forwarding is active, HLR will provide the location
information of the forwarded-to party to SMSC.
Subscribers can define the number to which the SM is forwarded via USSD command.
Another short message forwarding method is following:
Figure 3-5 Basic forwarded MT-SMS functionality

When subscriber A sends an SM to subscriber B, this SM can be forwarded to

subscriber C under the following conditions:
l subscriber B has SMS CFU active to subscriber C;
l the feature is active in subscriber B's HLR;
l SMS forwarding is allowed to subscriber C's network. Subscriber C must belong to

the same network with subscriber B or to one of the additional networks defined by
the operator;
l The subscriber C's HLR should also support the SMS forwarding feature.
Otherwise there are some restrictions in the functionality, especially when
subscriber C is not reachable.
The maximum number of forwarding is one. This means that subscriber B can forward
the SMS to subscriber C, but subscriber C is not allowed to forward it further.
The procedure is the following:
l HLR-B receives SendRoutingInfoForSM operation.
l It notices that subscriber B has CFU active and the request should be forwarded to
HLR-C.
l Before forwarding, HLR-B checks that forwarding is allowed to the destination

PLMN by requesting subscriber C's IMSI from the HLR.

l If forwarding is allowed, SendRoutingInfoForSM is sent to HLR-C.
l HLR-C acknowledges the operation to the GMSC with subscriber C's information.
The Inform-SC operation contains the MSISDN-C number, and inform-SC is always sent
from HLR-C.
3.70 ZWF-05-10-070 Hot Bill

Specification:
Implemented in: ZXUN USPP (HLR) (USPP)
3.70.1 Summary
The feature can be used for implementing the CDR identification of the pre-paid service
on the supplement service by the operator custom defined, which aids that Billing Center
filters CDR generated by pre-paid subscriber.
3.70.2 Benefits
It ensures the operator provide pre-paid service for subscribers simply.
3.70.3 Description
The PLMN Specific SS code is between 241 and 255, each of them can be defined by
the Operator, for Example, specifies 241 as the flag of “HotBill”, when normal call is
released or a SMS is released, a CDR is generated for the Call instance in MSC
Server/VLR and MSC Server/VLR sets the Hot bill Flag value by the Configuration in
OMC.
3.71 ZWF-05-10-072 CCBS

Specification: TS 29.002 23.093 24.093

3.71.1 Summary
ZXUN USPP (HLR) supports the Completion of Calls to Busy Subscriber (CCBS)
service.
3.71.2 Benefits
For operators
Operators can provide value-added services to subscribers.
For end-users
This service helps to enhance end-users' experience.
3.71.3 Description
The CCBS service allows the network to automatically originate a call to the calling
and called parties when both parties are available. If subscriber B is busy when
subscriber A, who has CCBS active, calls B, a call is automatically originated to B
and A when B and A are available.
ZXUN USPP (HLR) adopts the SSAP protocol to implement the CCBS service.
Figure 3-6 A successful CCBS flow

1. A calls B. When B is busy, A requires CCBS, MSC A sends MAP_Register_CC_Entry to HLR

A.
2. HLR A saves calling CCBS list, sends CCBS Request to HLR B.
3. After HLR B receiving CCBS Request, HLR B saves called CCBS list.
4. HLR B sends MAP_Set_Reporting_State Request to MSC B, asks MSC B to begin monitoring
B’s status.
5. MSC B returns MAP_Set_Reporting_State Ack to HLR B.
6. HLR B returns CCBS Request Ack to HLR A ,indicates CCBS request is successful；
7. HLR A returns MAP_Register_CC_Entry Ack to MSC A to close the dialog.
8. When B is free,MSC B sends MAP_Status_Report request to HLR B to inform HLR B that B is
free.
9. HLR B sends Remote User Free message to HLR A to inform that calling party can make
CCBS call. At the same time, HLR B returns MAP_Status_Report Ack to MSC B to close the
dialog and asks MSC B continue to monitor.
10. After HLR A receiving Remote User Free, HLR A sends MAP_Remote_User_Free to MSC A
to inform that A and B are free.
11. MSC A asks A to CCBS: MSC A sends MAP_Remote_User_Free Ack to HLR A when
receiving CCBS call request.
12. A call to B successfully；
13. MSC A sends MAP_Status_Report to HLR A to get CCBS success report, informing HLR A
CCBS is successful. HLR A returns MAP_Status_Report Ack and deletes calling CCBS dialog

ÿÿ
list.
14. MSC B sends MAP_Status_Report to HLR B to ask reporting CCBS calling event, HLR B
sends TC_END to HLR A to inform HLR A to close CCBS dialog, HLR B deletes called CCBS
list.HLR B sends MAP_Status_Report Ack to MSC B.HLR B sends
MAP_Set_Reporting_State request to MSC B to ask stopping monitoring B, HLR B returns
MAP_Set_Reporting_State Ack to close the dialog.
15. CCBS flow is over.
3.72 ZWF-05-10-073 Follow me

Specification: TS 29.002 23.094
3.72.1 Summary
ZXUN USPP (HLR) supports Follow me function as defined in TS 23.094.
3.72.2 Benefits
For operators:
HLR can be used as GSM-R or provides end-users with customized services.
3.72.3 Description
Follow me (FM) enables an initiating mobile subscriber A to have control over the Follow
Me data of a remote party B. The remote party B is characterized by the remote number
which is defined in the numbering plan of a PLMN operator. Initiating Subscriber A shall
be able to manipulate the Follow Me data of remote party B such that subsequent calls
destined for remote party B are forwarded to initiating subscriber A. In the case of
Forced Erasure by an FM service supervisor, the initiating subscriber is allowed to erase
the Follow Me data of a remote party who has been registered to a different initiating
subscriber for the Follow Me application.
Follow me is a PLMN specific feature and the control operations of FM are based on
USSD. All the messages between the MS and the mobile network are USSD messages.
The USSD service code is usually as 214.

3.73 ZWF-05-10-074 Optimized Late Call Forwarding

Specification:
3.73.1 Summary
When subscribers roams out his HPLMN, late-forward doesn’t bring out on roaming
MSC.GMSC in his HPLMN performs late-forward call.
3.73.2 Benefits
For operators:
International inter-office circuit will not be occupied when subscriber has a late call
forwarding and he does a international roaming.
For end-users:
End-users will not pay additional charge for long distance call.
3.73.3 Description
This function should be done accompany with GMSC.
In general, subscriber sets the late call forwarding service and the forwarded number is
the voice mail box, when subscriber A does a international roaming and is called, the
call will be connected to the VMSC. When A is busy, the call be route to the voice mail
box, but international inter-office circuit will be occupied.
ZXUN USPP (HLR) optimizes such call flow. It doesn’t sends Late Call Forwarding
number to VMSC when A does a international roaming. When A is called, Late Call
Forwarding number will be inserted to SRI response to GMSC.
3.74 ZWF-05-10-075 CDMA SIP function

Specification:
3.74.1 Summary
ZXUN USPP (HLR) supports CDMA SIP function to support CDMA PPS service.

3.74.2 Benefits
For operators:
If operator provides G/U and CDMA network simultaneously, it can provide SIP function
to support PPS service to G/U subscribers.
3.74.3 Description
G/U HLR provides SIP function to support PPS service for U/G subscribers. This
function is follow by CDMA network solution. SIP information includes AccessCodeList
which includes service type and PPS address. HLR inserts AccessCodeList to
MSCS.MSCS processes SIP message with PPS platform.
3.75 ZWF-05-11-001 Support for Subscriber

Registration Profile Template
Specification:
3.75.1 Summary
HLR provides subscriber registration service profiles to increase operators’ operation

efficiency during subscriber registration.
HLR allows authorized operators to query, add, delete (suspend) or modify subscriber
registration service profiles.
3.75.2 Benefits
For operators
This feature increases operators’ operation efficiency during subscriber registration and
facilitates management of the subscription data by operators.
Introducing this feature the MML-command processing effort to be spent in the customer
care centre for the administration of new subscribers decreases remarkably. Thus the
introduction of large numbers of subscribers into the network is made much easier. This
feature helps the operator to follow the market trend of continuously increasing mobile
subscriber numbers.
Less effort for administration of Mobile subscribers with similar service profiles.

3.75.3 Description
This feature enables the operator to create mobile subscribers in the HLR by a single
command only. The previous procedure of using 6 - 11 MML commands for the
administration of one mobile subscriber now applies for the definition of so-called
templates of virtual subscriber with representative profiles only. These templates define
standard subscriber profiles to be used to create real subscribers in the HLR. Differing
from the previous procedure the real subscriber is now created with one command and
all additional services are automatically copied from a template available in the HLR.
3.76 ZWF-05-11-002 MTC

Specification:
3.76.1 Summary
For the protection against malicious extra balance of PPS (Per-Paid Subscriber), it is
needed that HLR determines whether TCSI is triggered or not when HLR routines a call.
3.76.2 Benefits
For operators
It is can protect against malicious extra balance of PPS (Per-Paid Subscriber), the
originating requirements comes from the SPICE, India.
3.76.3 Description
For the protection against malicious extra balance of PPS (Per-Paid Subscriber), it is
needed that HLR determines whether TCSI is triggered or not when HLR routines a call.
l When a subscriber is within the VPLMN, the TCSI is triggered at each Call.
l When a subscriber is within the HPLMN and has an extra balance, TCSI is
triggered when the subscriber originates a call.
l When a subscriber is within the HPLMN and has normal balance, the TCSI is not
triggered when the subscriber originates a call.
It is requirement that HLR provision interface can supports the attributes of modification
triggering TCSI controlled by HLR, so that the operator can determine the triggering
TCSI by the subscriber whether has an extra balance or not.

3.77 ZWF-05-11-003 Unilateral Halt

Specification:
3.77.1 Summary
The feature can provide the subscription of Extra Balance (Calling Out Barring) and
Extra Balance (Calling In Barring) function respectively.
3.77.2 Benefits
For operators
According the requirement of the service provision, the operator can perform the policy
of the Calling Out Barring or Calling In Barring.
3.78 ZWF-05-11-004 Configured Default

NoReplyConditionTime
Specification:
3.78.1 Summary
The feature provides that the configurable time setup of the “No answer forwarding
default” function.
3.78.2 Benefits
For operators
It is easy to the operator provisioning their services.
3.78.3 Description
When a subscriber enables a cfnry service, if the “no answer forwarding time” has not
been set, the system will assign a default time as the no answer forwarding time for the

triggering service automatically time threshold. The default time threshold can be ranged
in seconds of (5, 10, 15, 20, 25, and 30).
When a subscriber subscribes a “no answer forwarding” service who has no assign a
“no answer forwarding time”, the system will assign a default “no answer forwarding time”
threshold.
3.79 ZWF-05-11-005 Routing Category

Specification:
3.79.1 Summary
The feature provides “Routing Category” function to the operator, which makes it easy
for operator’s providing flexible Routing plan, Charging scheme and Radio Resource
allocation to the subscribers.
3.79.2 Benefits
For operators
Operator can provide flexible Routing plan, Charging scheme and Radio Resource
allocation to the subscribers.
3.79.3 Description
The routing category parameter can be set for each subscriber in the HLR. This routing
category is used in mobile-originating, mobile-terminating and forwarded calls.
The operator can assign a routing category to each subscriber when creating a user in
the HLR database. If the parameter is not given, the default "N", meaning "not used", is
assigned. The operator can output and modify the routing category as any other
subscriber information.
The value of the parameter is transferred to the VLR with the MAP operation ISD in the
location update, restore data and stand alone ISD.
The VLR transfers the routing category to the Call Control when it provides information
for the outgoing call. If the called subscriber is busy, does not respond to paging or does
not answer and has a corresponding call forwarding supplementary service set, the VLR
transfers the routing category of the forwarding subscriber to the call control.

The HLR always provides the Call Control with the routing category of the subscriber
whose roaming number was asked. This applies both to the case where a roaming
number is returned and the cases where a call forwarding service is invoked.
That can be configured witch “Routing Category” insert to VLR and witch “Routing
Category” return to GMSC in SRI ACK.
The PLMN that use “Routing Category” can be configured.
3.80 ZWF-05-11-006 Authentication Profile for 2G

Specification:
3.80.1 Summary
With authentication profile for 2G function, ZXUN USPP (HLR) can configure different
authentication arithmetic and authentication parameters for the subscriber.
3.80.2 Benefits
For operators
With authentication profile, the system authentication configuration policy is more flexible.
3.80.3 Description
Authentication profile for 2G function includes items as follows:
the subscriber can subscribe different authentication parameters: Ki;
The subscriber can subscribe different authentication arithmetic: COMP128-1/

COMP128-2/ COMP128-3.
3.81 ZWF-05-11-007 Authentication Profile for 3G

Specification:

3.81.1 Summary
With authentication profile for 3G function, ZXUN USPP (HLR) can configure different
authentication arithmetic and authentication parameters for the subscriber.
3.81.2 Benefits
For operators
With authentication profile, the system authentication configure policy is more flexible.
3.81.3 Description
Authentication profile for 3G function includes items as follows:
the subscriber can subscribe different authentication parameters: Ki /OPC /AMF

/Anonymity key ID;
the subscriber can subscribe different authentication arithmetic: COMP128-1/

COMP128-2/ COMP128-3//Milenage and XOR.
3.82 ZWF-05-11-008 Configurable Constant of

Milenage Authentication Arithmetic
Specification:
3.82.1 Summary
ZXUN USPP (HLR) support configurable Constant of Milenage authentication arithmetic.
Value of r1, r2, r3, r4, and r5 can be configured. Value is integer within 0-127. Value of
c1, c2, c3, c4, and c5 can be configured. Numbers of “1” within “c1” is even. Numbers of
“1” within c2, c3, c4, and c5 is odd.
3.82.2 Benefits
For operators
With authentication profile, the system authentication configure policy is more flexible.

3.83 ZWF-05-11-009 Supporting Multiple OP/OPc

Specification:
3.83.1 Summary
OP/OPc, Operator Variant Algorithm Configuration Field, is a parameter in UMTS

authentication algorithm. The operator can customize the authentication algorithm by
selecting different OP/OPc. OP/OPc is stored in HLR and USIM card. ZXUN USPP (HLR)
supports multiple OP/OPc and supports different OP/OPc for different IMSI Number
range.
3.83.2 Benefits
For operators
Different IMSI Number range takes different OP/OPc, the system security is enhanced.
3.84 ZWF-05-11-010 Dual IMSI

Specification:
Implemented in: ZXUN USPLP (HLR)
3.84.1 Summary
Generally, MVNO (A) has no capability or willing to sign international roaming

agreement with many RPs. In order to ensure the complete service for its subscribers at
the same time, this MVNO always take advantage of big MNO(B)' existing international
roaming agreement to provide international service to its subscribers.
In this situation, operator B (MNO) assign an IMSI range to MVNO (A), MVNO A
produce dual IMSI SIM cards for its subscribers, one IMSI-A is among the IMSI range
specifically assigned for MVNO (A), and other IMSI-B is among the IMSI range assigned
by MNO (B) to MVNO (A). IMSI-A has no international roaming right, while IMSI-B has
the right to do international roaming.
During LU of IMSI (B), the message will go through the signaling gateway of MNO (B)
which will judge that this IMSI range belong to MVNO (A), then the message will be
forwarded to MNVO (A)' HLR.

There will be two authentications per subscriber in HLR, which is IMSI-A and IMSI-B.
Those two IMSIs share same subscription data and same MSISDN-A.
These features are integrated into the HLR application and are therefore completely
transparent to the other network elements and to the end-user.
3.84.2 Benefits
For Operators
Different IMSI Number range takes different OP/OPc, the system security is enhanced.
With Dual IMSI feature, Operators can expediently provide international roaming service
without signing international roaming agreement with many RPs..
3.85 ZWF-05-12-001 Chinese Lawful Interception

Function
Specification: Specifications for Police Interface Support in 900/1800MHz
TDMA Digital Cellular Mobile Communication System of the People’s Republic of China
3.85.1 Summary
The lawful interface is set for legal institutions for the country to monitor activities of the
specific subscribers.
3.85.2 Benefits
For operators
By tracing subscribers’ behaviors on the Internet, operators can collect reliable

information for network optimization.
With this service, simple subscriber behavior monitoring and tracing can be provided.
3.85.3 Description
ZXUN USPP (HLR) supports X1 and X2 police interfaces. The X1 interface is used to
process some instructions from the police center while the X2 is used for HLR to report

activities of subscribers under control to the police center. The X1 interface in HLR
provides the following functions:
l Management of the X1 interface TCP/IP link between HLR and the police
information center
l Activation of numbers under control (IMSI, MSISDN)
l Cancellation of numbers under control (IMSI, MSISDN)
l Query of number control state (IMSI, MSISDN)
l Listing of numbers under control (IMSI, MSISDN)
l Number state query (IMSI, MSISDN)
l NE time query
The HLR X2 interface supports the following functions:
l Management of the X2 interface TCP/IP link between HLR and the police
information center
l Sending location update event reports of numbers under control to the police
information center
l Sending routing event reports of numbers under control to the police information
center
l Sending supplementary service operation event reports of numbers under control

to the police information center
l Sending police interface running failure alarm information to the police information
center
Note: The police center development must conform to the Specifications for Police
Interface Support in 900/1800MHz TDMA Digital Cellular Mobile Communication System
of the People’s Republic of China.
3.86 ZWF-05-12-002 ETSI Lawful Interception

Function
Specification: TS 33.107, 33.108, ETSI 201 158

3.86.1 Summary
ZXUN USPP (HLR) supports ETSI Lawful Interception Function.
3.86.2 Benefits
For operators:
This function enables operators to provide lawful interception services.
3.86.3 Description
ZXUN USPP (HLR) supports service system reports and location update
notifications according to specification.
3.87 ZWF-05-12-003 Physical Interface -- FE/GE

Interface Functions
Specification: IEE802.3/ IEE802.3u
3.87.1 Summary
The system provides FE/GE interfaces for interconnection with other devices in the
telecom network.
3.87.2 Description
The system provides FE/GE interfaces for interconnection with other NEs via the IP
network. The FE/GE interface provides a transmission rate of 10/100/1000BaseTx.
The system provides physical interfaces using twisted pairs.
3.88 ZWF-05-12-004 Soap/XML Provisioning

Interface
Specification:
Implemented in: ZXUN USPP

3.88.1 Summary
ZXUN USPP supports SOAP/XML provisioning interface. BOSS could use SOAP/XML
interface to add, modify, delete and query subscriber information stored in ZXUN USPP
database.
3.88.2 Benefits
For operators
It ensures the operator use the SOAP/XML interface.
3.88.3 Description
ZXUN USPP supports SOAP/XML provisioning interface, based on HTTP/SOAP

protocol, adopts XML as semantic depicted language, and the character set code is
UTF-8.
BOSS performs SOAP Client function; ZXUN USPP performs SOAP Server function.
BOSS sends SOAP request to ZXUN USPP which includes authentication information
(username/password). ZXUN USPP receives the message, verify, and finish the related
operation and response the message.
3.89 ZWF-05-13-002 Subscriber Trace

Specification: ETSI 12.08
3.89.1 Summary
In HLR, trace of a subscriber can be activated/deactivated. The operator can select to

activate subscriber trace in HLR only or in HLR/VLR/SGSN simultaneously.
If the operator selects to activate subscriber trace in HLR/VLR/SGSN simultaneously

from HLR OMC, HLR will send a MAP message Active-Trace-Module-Req to
VLR/SGSN. The subscriber trace will be activated in VLR/SGSN. In the meantime,
subscriber trace records will also be generated in HLR. When the traced subscriber
roams to a new VLR/SGSN, HLR will re-activate trace of the subscriber in the new
VLR/SGSN and deactivate trace of the subscriber in the previous VLR/SGSN.

3.89.2 Benefits
For operators
By tracing subscribers’ behaviors on the Internet, operators can collect reliable

information for network optimization.
With this service, simple subscriber behavior monitoring and tracing can be provided.
3.90 ZWF-05-13-003 Any Time Interrogation (ATI)

3.90.1 Summary
This feature is a CAMEL2 function. The trigger of some intelligent services needs the
related subscriber’s location information or state information. Through the subscriber
information related signaling, gsmSCF can acquire the subscriber’s current location
information and state information from HLR.
3.90.2 Description
ZXUN USPP (HLR) supports subscriber information related MAP signaling and active
information interrogation initiated by gsmSCF towards HLR. When receiving the ATI
message from gsmSCF, if the corresponding subscriber is reachable, HLR will initiate
subscriber information interrogation towards VLR and return the interrogation result to
gsmSCF. When an intelligent subscriber is called, if it is required to provide subscriber
information in the subscriber’s subscription information, HLR will also initiate subscriber
information interrogation towards VLR.
3.91 ZWF-05-13-004 Any Time Subscription

Interrogation (ATSI)

3.91.1 Summary
This feature is a CAMEL3 function. The trigger of some intelligent services needs the
related subscriber’s subscription information. Through subscriber information related
signaling, gsmSCF can acquire the subscriber’s subscription information from HLR.
3.91.2 Description
A subscriber’s subscription information that gsmSCF can acquire from HLR includes:
l Supplementary service data: CF, CB
l CAMEL subscription data
l ODB subscription data
l CAMEL phases supported by VLR or SGSN
3.92 ZWF-05-13-005 Any Time Modification (ATM)

3.92.1 Summary
This feature is a CAMEL3 function. The trigger of some intelligent service needs
modification of the corresponding subscriber’s subscription information. Through the
subscriber information related signaling, gsmSCF can modify the subscriber’s
subscription information.
3.92.2 Description
A subscriber’s subscription data that can be modified by gsmSCF includes:
l Supplementary service data: CF, CB
l CAMEL subscription data: Various CSI

3.93 ZWF-05-13-006 Subscriber Data Modification

Notification
3.93.1 Summary
This feature is a CAMEL3 function. After modifying the CF, CB, ODB and CSI
subscription data registered by a subscriber, HLR can notify gsmSCF of the modified
data.
The subscriber can select whether to notify gsmSCF of the modified CF, CB, ODB and
CSI data by registering notification options. CF, CB, ODB and CSI can be set with
notification options respectively.
3.94 ZWF-05-13-008 Multi-number Function

Specification: 3GPP 29.002 29.007 23.018
3.94.1 Summary
HLR provides the function of allowing one subscriber to register multiple MSISDN
numbers so that an SIM card subscriber can have multiple MSISDN numbers at the
same time. In addition, each number can be registered with different basic services. For
example, one number is registered with the telephone service, one is registered with the
fax service, and another is registered with another data service. This facilitates
subscribers’ use of services.
3.94.2 Benefits
For operators
This feature provides the multi-MSISDN service to attract end users with special
requirements and thus enhance operators’ competitiveness in the market.
For end-users
A subscriber registering multiple MSISDN numbers can use different numbers to

represent different services, thus facilitating their use of services.

3.94.3 Description
This feature allows one SIM card to have multiple MSISDN numbers at the same time. In
addition, each number can be registered with different basic services to facilitate
subscribers’ use of services.
HLR supports number allocation to both 2G and 3G subscribers. Each 2G subscriber

can have a maximum of 12 telephone numbers (including the basic number). Each 3G
subscriber can have a maximum of 11 telephone numbers (including the basic number).
The multi-number function provided by HLR includes the following sub-functions:
The HLR agent provides subscribers with functions of adding multiple numbers and
modifying or deleting registered multiple numbers.
The HLR remote handling interface provides subscribers with functions of adding
multiple numbers and modifying or deleting registered multiple numbers.
When a subscriber is called, HLR will check whether the subscriber has registered
multiple numbers and complete the call termination routing process corresponding to the
called number.
3.95 ZWF-05-13-009 Long Forward-to Number

3.95.1 Summary
This feature increases the length of a forward-to number to 28 bits and breaks the
previous 15-bit restriction to a forward-to number.
3.95.2 Benefits
For operators
This feature provides more diversified call forwarding supplementary services to attract
subscribers and increase competitiveness.
For end-users
This feature enables end-users to set call forwarding supplementary services more
flexibly.

3.95.3 Description
HLR provides subscription of long forward-to numbers and checks whether other NEs
support long forward-to numbers.
HLR supports the following long forward-to numbers:
l Supporting long forward-to number subscription during subscription of call

forwarding supplementary services
l Supporting long forward-to number registration via MS
l Supporting default forward-to number configuration: when a GMSC does not

support the long forward-to number function, the default forward-to number is sent
to the GMSC with the MAP command.
l If MSC/VLR supports the long forward-to number function, during download of call
forwarding supplementary service data to MSC/VLR, the registered long forward-to
number is also downloaded to MSC/VLR.
l After modification of a long forward-to number, if VLR/MSC supports the long

forward-to number function, HLR synchronizes the modified long forward-to number
to VLR/MSC with the MAP command.
l When a subscriber is called and the call is forwarded to another number, if GMSC
supports the long forward-to number function, HLR sends the long forward-to
number to GMSC with the MAP command.
l When a subscriber is called and the call is forwarded to another number, if GMSC
does not support the long forward-to number, HLR sends the default long forward-
to number to GMSC with the MAP command.
3.96 ZWF-05-13-011 SuperCharger

3.96.1 Summary
Super-Charger provides a mechanism to reduce the mobility-related signaling traffic

during subscriber location update between VLRs or SGSNs.
3.96.2 Benefits
For operators

This feature reduces the mobility-related signaling traffic and the network load.
3.96.3 Description
In a network supporting Super-Charger, when a subscriber roams from one network

entity to another, the previous network entity will reserve the subscription date related to
this subscriber. Here, the network entity refers to MSC/VLR or SGSN.
In a network supporting Super-Charger, when a subscriber roams from PVLR to a new

VLR, HLR will initiate a MAP_CANCEL_LOCATION Request only when the PVLR does
not support Super-Charger. If the current VLR reserves the subscription data of this
subscriber (reserved during last visit by the subscriber), HLR will initiate a MAP-INSERT-
SUBSCRIBER-DATA Request message to VLR/SGSN only when the subscriber data in
VLR/SGSN are inconsistent with those stored in HLR. If HLR does not send any MAP-
INSERT-SUBSCRIBER-DATA Request message to VLR/SGSN, it may be considered
that the subscription data reserved in the current VLR/SGSN are valid.
3.97 ZWF-05-13-012 Pre-paging

3.97.1 Summary
This feature is to initiate Page towards a subscriber at the phase of routing information
acquisition during call termination. In this way, the call setup time is shortened and
CFNRc can be triggered in advance.
3.97.2 Benefits
For operators
This feature optimizes network resource utilization.
3.97.3 Description
3.98 ZWF-05-13-013 Enhanced GPRS Support

Specification:

3.98.1 Description
The support for enhanced GPRS covers the following sub-functions:
l When a subscriber only registers R98 QoS, no matter whether SGSN supports the
enhanced GPRS function, HLR will only synchronize R98 QoS to SGSN without
QoS conversion.
l When a subscriber only registers R99 QoS, if SGSN supports the enhanced GPRS
function, HLR will not convert QoS. Otherwise, it will convert R99 QoS into R98
QoS before synchronizing it to SGSN.
l When a subscriber registers both R98 and R99 QoS, if SGSN supports the
enhanced GPRS function, HLR will insert R99 QoS into SGSN. Otherwise, HLR will
insert R98 QoS into SGSN.
l R98 QoS includes the reliability class, delay class, priority, peak throughput and
mean throughput.
Besides the reliability class, delay class, priority, peak throughput, mean throughput,
R99 QoS also includes the PS assignment priority, whether to send error data, whether
a sending sequence is available, extended QoS traffic class, maximum service data unit
length of extended QoS, service data unit error rate of extended QoS, redundancy bit
error rate of extended QoS, traffic handling priority of extended QoS, extended QoS
transfer delay, maximum bit rate for uplink of extended QoS, maximum bit rate for
downlink of extended QoS, guaranteed bit rate for uplink of extended QoS and
guaranteed bit rate for downlink of extended QoS.
3.99 ZWF-05-13-014 SMS over GPRS

Specification:
3.99.1 Summary
The feature provides a subscriber with the possibility to send and receive Mobile
Terminated and Mobile Originated Short Message Services (SMS) over the General
Packet Radio Service (GPRS) in a GSM network.

3.99.2 Benefits
For end-users
End-users who formerly had access to the non-GPRS network only, and now have been
given access to the GPRS network, are able to keep SMS-related services (SMS-MT
and SMS-MO) and SMS-based applications and use them when they are attached to the
GPRS network. The user interface for these services will be the one that the end-user is
accustomed to.
An end-user who is only attached to the GPRS network will be able to send and receive
short messages and, for example, send and receive short messages to/from subscribers
with access only to the non-GPRS network only.
For operators
The non-GPRS part of the network, previously used for SMS, is then free for other non-
GPRS signaling.
The operator can offer existing services using SMS to GPRS subscribers without having
to redesign those services.
The operator has the possibility to have the SMS traffic sent over the GPRS channels or
over non-GPRS channels. By choosing the GPRS channels the utilization of the radio
resources will be more efficient, thus getting higher capacity per radio channel.
As the radio resource utilization will be more efficient, i.e. with more subscribers/traffic
per radio resource, it will increase the SMS capacity of the network.
3.99.3 Description
The Short Messages are delivered through the Serving GPRS Support Node (SGSN),
which is at the same hierarchical level as the MSC/VLR and a part of the GPRS network.
When a Short Message is being sent to a mobile subscriber, the HLR checks if the
service is provisioned, if any barring functionality is active, and if the subscriber is absent
from VLR/SGSN coverage.
In case of an unsuccessful delivery of a Short Message, the service Message-Waiting

will provide the HLR with the information that there is a message in the SMS-C waiting
to be delivered to the mobile station. The information located in HLR, Message-Waiting-
Data (MWD), contains a list of SMS-C addresses which have made unsuccessful
delivery attempts. HLR informs the SMS-C when the mobile is able to receive SM again.
The SMS-MT standard solution in MAP V3 is implemented. It means that subscribers

having access to both GPRS and non-GPRS networks will be able to receive MT-SMS
when roaming in PLMN not supporting GPRS although their SMS transfer option
indicates via GPRS.

3.100 ZWF-05-13-015 MAP Version Control

Specification:
3.100.1 Summary
MAP is the GSM/3GPP standardized protocol for dialogue between the NSS
components inside the network or between a network entity and a foreign PLMN.
Different entities may have different versions of this MAP protocol, which may lead to
unsuccessful dialogue attempts. In such a situation, the entity that has initiated the first
attempt tries a second attempt with the immediately lower level of MAP protocol.
MAP version control avoids the loss of time by allowing the entity having the highest
level of MAP protocol to determine which appropriate version of MAP should be used to
initialize the dialogue.
The entity having the higher level of MAP protocol receiving a lower MAP phase
dialogue will answer in appropriate version of MAP protocol.
3.100.2 Benefits
For operators:
Operators can design MAP version to different VPLMN according their agreement.
3.100.3 Description
ZXUN USPP (HLR) sets different MAP version according to different VPLMN and
different Application Contexts to meet the network agreement requirement between
different VPLMNs.
3.101 ZWF-05-13-016 Improvement of MAP Dialogue

Between HLR and VLR
Specification:

3.101.1 Summary
When subscribed teleservices and bearer services information is sent from the HLR to
the VLR, if the VLR does not support some of the teleservices/bearer services, the result
message which is sent by the VLR include the complete teleservice/bearer service
information regarding the non supported features.
Bytes 1 to 5 instead of byte 1 are returned to the HLR.
3.102 ZWF-05-13-017 MAP with WHITE BOOK SCCP

for Intra-PLMN Use
Specification:
3.102.1 Summary
This feature gives the possibility to use the segmentation at SCCP level of the MAP
messages, but only for Intra-PLMN use.
The concerned messages can be the following:
l Insert Subscriber Data (between HLR and VMSC)
l Send Routing Information – Result (between HLR and GMSC)
l Forward Short Message (between VMSC and SMS-GMSC).
3.103 ZWF-05-14-001 SS7 Functions (ANSI Type)

Specification: ANSI T1.110 T1.111 T1.112 T1.118 T1.114
3.103.1 Summary
Common Channel Signaling (CCS), ANSI Type, provides the platform for inter exchange
signaling according to the American National Standards Institute (ANSI) and Bellcore
standards.

3.103.2 Benefits
The feature is a prerequisite for all applications based on ANSI No.7 signaling. Some of
these are MTP users, for example, ANSI ISUP. Others are SCCP or TCAP users
(Intelligent Network Application Parts, Application Parts for Wireless Networks, such as
IS-41, etc.)
SCCP allows its users to share services such as Global Title Routing, which enables
flexible inter- and intra-network signaling.
TCAP provides its users with transaction related services, allowing seamless
communication with their peer applications in the network.
This implementation of ANSI CCS has the following benefits:
l High level of compliance to latest standards
l High traffic capacity
l Extensive operation and maintenance facilities
3.103.3 Description
Common Channel Signaling (CCS), ANSI Type comprises the following:
l Message Transfer Part (MTP)
l Signaling Connection Control Part (SCCP)
l Transaction Capabilities (TCAP)
The Message Transfer Part serves as a connectionless transport system that provides
reliable transfer and delivery of signaling messages across a signaling network.
MTP includes:
l Cluster routing and management
l Congestion control
l MTP restart procedures
l DS0-A and V.35 signaling data link interfaces
l Traffic and maintenance measurement statistics
l Signaling Network Monitor
l Looping of signaling traffic per destination

l Traffic and maintenance measurement statistic
l Event reporting
The Signaling Connection Control Part is an MTP User that provides additional routing
capabilities for the transport of non-circuit and circuit related signaling information
between exchanges and databases. These capabilities are provided according to ANSI
and Telcordia standards.
The services provided by SCCP are grouped into connection-less and connection
oriented services. The connection-less service provides a message transfer facility
where there is no relationship between two or more messages for the same user. The
connection oriented services involve the set up of logical signaling connections between
the SCCP users, the exchange of data using these connections, and the release of the
signaling connections.
There are three classes of service provided:
Class 0 Basic connection-less class
Class 1 Sequenced (MTP) connection-less class
Class 2 Basic Connection Oriented Class
SCCP includes:
Global Title Translation
l Local number Portability Message Relay Function
l Reporting of Signaling Network On Occurrence Events
l Traffic and Maintenance measurement statistics
The Transaction Capabilities Application Part (TCAP) uses a SS7 network for the
implementation of distributed applications. TCAP provides non-circuit related information
transfer capabilities and generic services to application, yet remains independent of the
application. The TCAP Platform provides a common interface, through which peer
applications may exchange information, initiate processes etc. via TCAP Messages.
TCAP interfaces directly with SCCP, making use of the SCCP connection-less service.
The services are provided according to ANSI and Telcordia Standards.
CCS-7 TCAP ANSI TYPE includes:
l Transaction handling services
l Administration of Application Parts
l Traffic and Maintenance measurement statistics

The Common Channel Signaling ANSI Type is a basic function for any exchange that
requires ANSI No.7 signaling. It is generic to all ANSI applications and user parts, and
can be used in any type of network - PSTN, ISDN, IN or mobile, and can interwork in a
multivendor environment.
Common Channel Signaling, ANSI Type, can coexist in the same exchange with
Common Channel Signaling, ITU Type.
Common Channel Signaling No. 7, ANSI Type complies with:
ANSI T1.111 (1992) and Bellcore Technical Requirements
GR-246-CORE
Bellcore Specification of Signaling System Number 7
GR-82-CORE
Signaling Transfer Point Generic Requirements
GR-606-CORE
LSSGR, Section 6.5, Common Channel Signaling
GR-310-CORE
SEASTM Interface Specification
3.104 ZWF-05-14-002 ANSI Interfaces

Specification:
3.104.1 Summary
The HLR has built in interfaces to be able to support seamless connection to both
existing and new nodes in the network. The HLR supports the American National
Standards Institute (ANSI) SONET interfaces.
3.104.2 Benefits
The build-in interfaces in the HLR enable easy interfacing between the HLR and other
network elements thus saving the cost of external interfacing equipment.

3.104.3 Description
This feature supports the following interfaces:
ANSI channelized SONET STS-3, carrying TDM traffic, which is a 155 Mbit/s
synchronous interface according to Bellcore GR-253-CORE.
ANSI T1, a 1544 kbit/s synchronous interface according to the ITU-T standards TI.403
and G.704 carrying TDM traffic
3.105 ZWF-05-14-003 SUA

draft-ietf-sigtran-sua-13.txt
3.105.1 Description
SUA(Streamlines Transaction Transport) is optimized to carry transactional content

signaling, replacing the SS7 stack up to and including SCCP. SUA acts as a carrier for
SCCP and TCAP payloads. Although M3UA can also carry SCCP payloads, SUA
eliminates more of the SS7 stack while making better use of IP-based routing.
SUA decreases network management complexity. SUA can co-reside with M3UA for the
universal SIGTRAN signaling solution. Parallels functionality found in IP-based DNS
routing, but for telephony applications. SUA offers substantial flexibility in reducing
dependence on fixed network addresses through SCCP-based routing, reducing links
and bandwidth concerns in network architecture design, also provides support for
network management via SNMP.
3.106 ZWF-05-14-004 M2PA

Specification: IETF: draft-ietf-SIGTRAN-M2PA-12.txt
3.106.1 Summary
M2PA: Lowers Network Operation and Management Costs

3.106.2 Description
Essentially acting as a link replacement layer for MTP2, M2PA enables network
engineers to flexibly size signaling bandwidth allowing services to scale as necessary.
When utilized through Signalware, M2PA allows developers to simplify their network
engineering.
Enables service providers to maintain their current SS7 network topology while taking
advantage of the benefits of SS7 over IP. IP-enables existing IN equipment in the
network. Utilizes peer-to-peer communication since they can now communicate directly.
Provides support for network management via SNMP. Increases the available bandwidth,
enabling scalable, IP-based, high speed link capabilities.
3.107 ZWF-05-14-005 M2UA

Specification: RFC: 3331
3.107.1 Summary
M2UA (MTP2 User Adaptation Layer)
3.107.2 Benefits
Regarding to build-in signaling gateway enhanced function, this feature provides

signaling forward function in MTP2 layer, being a signaling gateway, signaling point
resource is not necessary. It provides one more signaling gateway option for operators.
3.107.3 Description
As M2UA realized signaling gateway function, message comes from No7 network, and
passes SG, which is adapted to IP signaling network through M2UA, which adopt SCTP
bearer mode, deliver to IP network node with destination signaling point.
3.108 ZWF-05-14-006 2M Signaling Link Supports

Software
Specification:

3.108.1 Summary
With the incessant growth of the HLR capacity and increase of its processing capability,
the signaling link processing will become a bottleneck. The single link rate of 2M high-
speed signaling links are 31 times as higher as that under the previous SS7 framework,
which can better meet the requirements for HLR link load by mobile service
development.
3.108.2 Benefits
For operators
This feature supports higher HLR capacity and processing capability, thus bringing more
benefits to operators.
3.108.3 Description
With the switching equipment developing towards the trend of higher capacity, the
signaling traffic between switching offices is also increasing accordingly and there are
higher requirements for the inter-equipment signaling bandwidth. Due to the SLS
restriction of the SS7 system, a maximum of only sixteen 64Kb/s signaling links can be
configured between two SPs. In actual applications, such capacity is unable to meet the
requirements. ZXUN USPP (HLR) supports 2Mb/s high-speed signaling links and the
bandwidth is 31 times as higher as 64Kb/s links. It provides a foundation for operators to
develop services and large-capacity applications.
3.109 ZWF-05-14-007 Multi Signaling Point Function

Specification:
3.109.1 Summary
Due to restriction of the SS7 MTP layer protocol, a maximum of only 16 signaling links
can be provided between two adjacent SPs. When the subscriber capacity exceeds a
certain level, the 16 signaling links between HLR and the peer adjacent SP cannot meet
the requirements for signaling data transmission, thus leading to link congestion.
Without any requirement on the peer network entity, the multi-SP technology enables
configuration of multiple SPs in HLR to expand the number of links between two
adjacent physical signaling entities and meet the requirements for signaling transmission.

3.109.2 Benefits
For operators
The multi-SP technology breaks the bottleneck of link quantity for HLR and increases
the signaling processing capability of a single HLR without imposing any requirement on
the peer network entity.
3.109.3 Description
ZXUN USPP (HLR) supports the multi-SP function. One HLR can be configured with a
maximum of 64 SPs. The multi-SP function serves the following purposes:
l To resolve the problem of inter-office signaling bandwidth insufficiency. The SS7

system allows a maximum of sixteen 64Kb/s signaling links to be configured
between two SPs. When the load between two SPs is quite high, a bottleneck may
form in the signaling link bandwidth. The number of signaling links that can be
configured between two NEs can be doubled by configuring multiple SPs for the
NEs.
l To meet some special requirements, e.g., configuration of different SPs for different
office directions
3.110 ZWF-05-14-008 SCCP Screening

Specification:
3.110.1 Summary
SCCP traffic is screened according to the message field contents.
3.110.2 Benefits
For operators
This feature improves the security of the signaling network by restricting the SCCP traffic
that is allowed access to the nodes.
Signaling network dimensioning can be based on own signaling figures. Overload from
other telecom administrations´ unauthorized traffic is prevented.

3.110.3 Description
The SCCP Policing (or Screening) function lets a network operator support (multi-)
bilateral service agreements among operators, as well as protecting network integrity
from intrusions.
The SCCP Policing function is applicable to any node within the SCCP network, where
incoming messages from other networks (either terminating or to be routed to other
nodes) must be "allowed" or "discarded", depending on the specific policing criteria set
by the network operator.
It is possible to define any policing criteria as a specific set of parameters and/or

parameter fields received in an SCCP message, the particular values to match, as well
as the actions to perform in case of matching /mismatching /missing such a parameter
and /or parameter field.
Any of the following SCCP message fields are examined as a basis for screening: Link
Set (LS), Originating Point Code (OPC), Destination Point Code (DPC), calling party
address, Message Type Code, Hop Counter and Protocol Class. Messages are allowed,
discarded or returned depending on the action set for each combination.
Violation reporting is used to register and report messages violating the policing
restrictions.
3.111 ZWF-05-14-009 MTP Screening

Specification:
3.111.1 Summary
This feature can be used when more than one administration operates in a CCITT NO.7
signaling network.
This MTP function ensures that there is no unauthorized use of a STP and enables the
reporting of messages violating the defined restrictions.
The MTP policing feature is divided into three parts:
l STP policing, intended to restrict the use of an STP
l Signaling network management policing, used to support the STP policing by

restriction of certain signaling network management messages
l Violation reporting, used to register and report messages violating the policing
restrictions

3.111.2 Benefits
For operators
This feature improves the security of the own network. No unauthorized administration is
able to use the nodes as STPs.
The dimensioning of the signaling network can be based on own signaling figures.
Overload from other administrations are prevented.
3.111.3 Description
This feature allows for discarding Message Signaling Units (MSUs) on the basis of
incoming link set identities and some or all of the following MSU fields:
l Originating Point Code (OPC)
l Destination Point Code (DPC)
l Service Indicator (SI)
l Destination field of Network Management Message
l Heading Code of Network Management Message
Service Indicators (SI), as well as OPC and DPC, can be used as criteria to discard
messages on any specified link set (LS). LS (or OPC, DPC, etc.) can be grouped
together and give the same policing method.
All network management messages can be policed.
The number of policed LS (or OPC, DPC, etc.) is unlimited, and the number of
combinations possible (LS * OPC * DPC etc.) is very large (16 million).
3.112 ZWF-05-14-010 MAP Screening

Specification: ITU-T Rec. Q.714
3.112.1 Summary
The feature MAP Policing provides the operator the possibility to protect his GSM
network from unauthorized access. The feature allows the HLR to accept or reject one
or more MAP operations depending on the originating SCCP address.

3.112.2 Benefits
For end-users
The subscriber information will be protected from unauthorized access so that the
information cannot be tampered with. This gives the subscriber confidents in the
reliability of the mobile network.
For operators
The strictly confidential subscriber information stored in HLR must be rigorously

protected. The feature will protect subscriber information from unauthorized access and
will also protect authentication information. The feature shall be seen to complement
existing GSM measures such as authentication, EIR checking, ciphering and TMSI.
This feature enables the operator to enforce that all mobile terminating calls to
subscribers registered in the HLR enter the GSM network in the operators GMSCs. This
is done by allowing the MAP operation Send Routing Information only from GSMC of the
home PLMN. By this application of the function it is ensured that all mobile terminating
calls to subscribers registered in the HLR are routed via the own network and thus be
charged by the operator.
3.112.3 Description
Whenever an incoming MAP operation is received, it is checked whether policing

restrictions exists for it. If that is the case, it is verified whether the originating application
address is allowed to perform this operation and if it is restricted the operation shall not
proceed. An abort message is returned to the originating application. If no policing
restriction applies to the operation, it proceeds.
The following operations are possible to police:
l Update Location
l Set message waiting data
l Routing Information Request
l Note MS present
l Operate SS (activate SS, deactivate SS, register SS, erase SS, and interrogate SS)
l Begin Subscriber activity
l Restore Data
l Register Password

l Send Parameters
l Send Routing Information
An operation is identified by its operation code, destination SSN and protocol version
number. Different protocol versions will be considered as a different operation from the
policing point of view.
Each operation to be policed will be assigned one or more allowed addresses. Any
allowed address must:
l belong to a Global Title number series, or
l be a Signaling Point Code (SPC)
Since it is unknown which of the above addressing the originating application uses, each
part present in the originating application address is compared with the corresponding
allowed addresses until a match is achieved. If a match is not found, the operation will
be considered restricted.
Means for the administration of the allowed originating addresses and policed operations
are provided.
For operations rejected by MAP Policing it is possible, by using Event Reporting

functions, to generate a report in which originating application address, operation
identification and the time of the event.
All incoming MAP operations received in a TC-BEGIN dialogue primitive for the different
supported MAP operation versions can be policed.
3.113 ZWF-05-14-011 MTP Charging

Specification:
3.113.1 Summary
This function will enable the registration by the receiving operator of the number of MTP
message or octets for which payment is to be received. Also the number of messages or
octets sent to an operator is counted in order to verify payment is to be made.
3.113.2 Benefit
The function lets a telecom administration charge other telecom administrations using
nodes within their network as STP’s for routing of MTP messages.

3.113.3 Description
The accounting method is based on the principle that the originating node pays the
operator of the next signaling point in the message’s path for delivering the messages
towards its destination. The operator of the next signaling point on the message’s path
pays the operator of the signaling point after that node, and so on.
The measurement can be divided into two sub-functions allowing for remuneration and
remuneration verification
Separate measurements are made on the basis of link set, service indicator, and DPC,
as specified in recommendation Q.75.
The accounting data shall be collected at fixed time periods and shall be stored in an
output file. From this output file accounting data, Cascade Remuneration Accounting can
be calculated
3.114 ZWF-05-14-012 SCCP Charging

Specification:
3.114.1 Summary
SCCP Accounting makes it possible to count and register the number of SCCP
messages and octets relayed on behalf of other network operators. It also allows
messages originating in the own network and sent to another network to be counted and
registered.
3.114.2 Benefit
SCCP Accounting allows an operator to charge another network operator for relaying
SCCP messages. SCCP Accounting also allows an operator to verify that charges
claimed by another operator for SCCP relay are correct.
3.114.3 Description
SCCP Accounting allows counting and registering of SCCP messages and octets. The
operator can specify certain criteria that a message must meet in order to be counted.
The criteria are for incoming messages Originating Point Code, Global Title and Sub-
System Number. For outgoing messages, the criteria are Destination Point Code and
Sub-System Number.

The registered information is periodically stored on local persistent media and can be
fetched by a post-processing system, e.g. a billing system, using FTP.
3.115 ZWF-05-14-013 SCCP Load-Sharing

Optimization
Specification:
3.115.1 Summary
Load sharing is implemented for the signaling on the SCCP.
3.115.2 Benefits
This feature helps to optimize and increase signaling load of the SCCP.
3.115.3 Description
The GT is translated into a DPC. Based on the DPC, load sharing can be done among
total 16 office directions.
3.116 ZWF-05-14-014 SCCP Congestion Control

Specification: ITU-T Rec. Q.714
3.116.1 Summary
The signaling load in mobile networks is steadily growing due to the increased usage of
services such as Intelligent Network Services and Short Message Services (SMS). This
may lead to abnormal load situations which sometimes could result in loss of calls.
The SCCP Congestion Control feature increases the robustness of the signaling network
in overload situations as specified in ITU-T recommendation Q.714.
3.116.2 Benefits
For operators

In cases of overload, traffic is queued, resources become busy and an increasing part of
the processor capacity is employed in rejecting calls. In order to avoid a collapse of the
congested nodes, messages can be prioritized and only those messages with a high
priority can be allowed to be transferred.
The feature increases the robustness of the signaling network by providing better
handling of abnormal overload situations. This improves the In Service Performance.
3.116.3 Description
This feature manages MTP congestion, own HLR congestion and local and remote
SCCP congestion. The HLR is able to inform adjacent nodes about congestion situation
by means of SCCP management messages as well as handling congestion reports from
adjacent nodes. The advantage is that not only problems in the MTP network are
detected, but also lack of resources at the own or remote nodes are detected and
handled, and situations of processor overload are addressed.
The Signaling Connection Control Part (SCCP) of SS7 provides the congestion control
measures to reduce traffic towards a congested network node. The congestion control is
based upon establishing a relationship between the congestion level towards a
destination node and the importance of the messages to be sent to that node. If
congestion occurs, congestion control provides a means by which the SCCP selectively
discards messages basing the decision on the importance of a message.
The mechanism for SCCP congestion control is based on the use of SCCP Restriction
Levels per destination and the use of Importance Values for messages on TCAP, SCCP
and MAP level. The Restriction Level, together with the importance of the message to be
sent, allows the reduction of the traffic towards a congested node by discarding a portion
of the traffic concerned.
It is the Message Transfer Part (MTP) in the sending HLR, which informs the SCCP
about the congestion situation towards a destination. SCCP uses this information to
increment or decrement the Restriction Level for the destination concerned.
When routing a message, the importance of the message is compared with the
restriction level of the destination. If the importance value is lower than the restriction
level then the message is discarded.
3.117 ZWF-05-14-015 OMAP Functions

Specification: International standard: ITU-T Recommendation Q.750–Q.759,
Q.780-Q.799
Communications industry standards in China: Technical Requirements for SS7

Monitoring System and Technical Specifications for Domestic SS7 System-Operation &
Maintenance Management Part (OMAP).

3.117.1 Summary
The major functions of signaling network running, maintenance and management are:
Signaling network monitoring and measurement, signaling network management and
dynamic monitoring of signaling networks.
3.117.2 Description
The signaling network management consists of three parts: Configuration management,

fault management and performance management.
Signaling network monitoring and measurement include real-time measurement of the

related indexes of MTP and SCCP. The minimum measurement unit is 5 minutes.
Dynamic monitoring of signaling networks is to perform graphic display and data

analysis of measurement data.
Characteristics:
The man-machine interfaces for configuration management, fault management and

performance measurement are all completely graphic, which are easy to learn and use.
Performance measurement accompanies service running all the time.
Data statistics and analysis are offline so they will not affect the service.
Various print reports can be generated conveniently.
The alarm generator supports audible and visible alarms.
3.118 ZWF-05-14-016 ASP-SG-ASP M3UA Application

Function
Specification:

3.118.1 Summary
Supporting the M3UA signaling network management function and procedure for using
in IPSEP-IPSTP-IPSEP. These functions isn’t defined in M3UA specification, but these
functions is needed in actual IP network
3.118.2 Benefits
For operators
These functions help to realize the signaling network management and message
transferring for IPSEP-IPSTP-IPSEP scene.
3.118.3 Description
l Supporting the M3UA signaling network management function
l Extend the DUPU message code
l Supporting M3UA message transferring in HLR
3.119 ZWF-05-14-017 Coexistence of TDM and IP to

One Office
Specification:
3.119.1 Summary
Simultaneously support TDM and IP between two SPs. The Feature can fulfill TDM and
IP mixed network. Supporting following case:
l Two SPs are associated: associated method can use TDM and/or IP.
l Two SPs are quasi-associated and associated: associated method between

SPs/STPs can use TDM and/or IP.
l Two SPs are quasi-associated: associated method between SPs/STPs can use
TDM and/or IP.
3.119.2 Benefits
For operators

The Feature can fulfill TDM and IP mixed network and can increase network organizing
flexibility.
3.119.3 Description
3.120 ZWF-05-14-018 IPV4/IPV6

Specification:
3.120.1 Summary
HLR support IPV4/IPV6.
HLR support:
l IPV4
l IPV6
l IPV4/IPV6
The case can be configured.
3.121 ZWF-05-14-019 Signaling Convergence

Function
Specification:
3.121.1 Summary
ZXUN USPP (HLR) support Signaling convergence function. Signaling convergence

function provide centralized signaling monitor. SS7 signaling links compound to
signaling meter through SPB. Signaling convergence function doesn’t affect signaling
links to other network elements.

3.121.2 Benefits
For operators
Signaling convergence function reduces the signaling links accessing to signaling meter.
So it economizes the E1.
3.122 ZWF-05-14-020 N*64K Signaling Link Supports

Software
Specification:
3.122.1 Summary
This feature provides N*64K signaling link processing.
3.122.2 Benefits
For operators
It is traditional signaling link enhanced function, which provides N*64K bandwidth

narrowband signaling link, N: 8-25.
3.122.3 Description
Compared with the signaling link that all frame of the E1 use the same signaling link,
Signaling can achieve higher bandwidth.
3.123 ZWF-05-14-021 IP over E1/T1

Specification:
3.123.1 Summary
The IP packet of control and media can be transported over E1/T1.

3.123.2 Benefits
The function of IP over E1/T1 provides another link mode of two SP.
3.123.3 Description
IP over E1/T1 function is performed by transporting IP packet of control and media plane.
3.124 ZWF-05-14-022 SCTP Multi-homing

Specification: RFC: 2960
3.124.1 Summary
An SCTP end point is considered multi-homed if it has more than one transport address
that can be used as a destination address (DA) to reach that end point.
3.124.2 Benefits
This feature helps to provide the network level redundancy.
3.124.3 Description
HLR provides one association 4 transport address.
3.125 ZWF-05-14-023 SCCP GT Flexible Conversion

Function
Specification:
3.125.1 Summary
The feature can change GT type or GT route mode, also change some numbers of the
destination GT.

3.125.2 Benefits
GT conversion is more flexible.
3.125.3 Description
Commonly, GT can translate the DPC or DPC + new GT, while operation want to
change some numbers of the many GT, it must configuration many new GT, workload is
huge, but SCCP GT flexible conversion function can do it easy. The feature flexibly
changes GT according to configuration.
3.126 ZWF-05-14-024 Signaling Monitor

Specification:
3.126.1 Summary
Signaling monitoring is to monitor the signaling protocol messages received and sent by
a device. Special commands are used to start and stop the monitoring function. The
monitoring result can be displayed on the terminal or saved in a file. The following types
of signaling can be monitored: MTP, TUP, ISUP, BICC, SCCP, etc.
3.126.2 Benefits
This feature can be used to analyze the signaling interworking flow during the
interworking.
3.126.3 Description
Use the monitoring tool to start the signaling monitoring function and the monitored
contents will be output and displayed on the terminal or be recorded in a file. These
contents include the signaling message date and time, signaling transmission direction,
message type, message data, and code stream.
3.127 ZWF-05-14-025 Origin-based SCCP Routing

Specification: ANSI T1.110, T1.111, T1.112, T1.118, T1.114

3.127.1 Summary
It can do the GTT translation based on CgPA and CdPA.
3.128 ZWF-05-14-026 XUDT

Specification:
3.128.1 Summary
ZXUN USPP (HLR) support SCCP XUDT message.
3.128.2 Description
XUDT message can be sent according to different VPLMN.
3.129 ZWF-05-14-027 ATM over E1/T1

Specification:
Implemented in: ZXUN USPP （HLR）
3.129.1 Summary
The ATM packet of Signal can be transported over E1/T1.
3.129.2 Benefit
The function of ATM over E1/T1 provides another link mode.
3.129.3 Description
ATM over E1/T1 function is performed by SPB board.

3.130 ZWF-05-14-028 Access Control Lists (ACLs)

for IPv4
Specification: 3GPP 23.401, 23.060, and related RFC
3.130.1 Summary
Access Control Lists for IPv4 offer an important tool for controlling traffic on the IP
network. These lists are used to filter IPv4 package flow into or out of ZXUN USPP
interfaces.
3.130.2 Benefits
ACLs provide an important network security function for IPv4 based interface.
3.130.3 Description
ACLs for IPv4 provide an important network security function for ZXUN USPP. With
ACLs for IPv4, IPv4 packages on inbound and outbound interfaces could be classified
and filtered.
ACLs could check the source and destination addresses, source and destination port
numbers, protocol types (E.g. TCP, UDP, ICMP etc).
ZXUN USPP support ACLS on all IPv4 based interface.
3.131 ZWF-05-15-001 DBIO Log Function

Specification:
3.131.1 Summary
The HLR system can record all handling operations on subscriber information by the
service handling terminals to facilitate future query and provide important information for
HLR problem analysis.

3.131.2 Benefits
For operators
This feature allows operators to conveniently query all handling operations on subscriber
information by the service handling terminals through the DBIO log. In the meantime, it
also provides important information for HLR problem analysis when a fault occurs.
3.131.3 Description
The system can record all serviced handling operations except the query operation.
The system provides the log query function. The query results will be displayed in the
table form. The message contents of each service handling operation can be displayed
in a comprehensible format. More specifically, the log query can be based on either IMSI
or MSISDN.
The service handling log can be exported as text files.
The service handling log can be saved for a period of time. For the active HLR, it can be
saved for about one month; for the disaster tolerance HLR, it can be saved for two
weeks.
The message contents in the log are displayed in the command line mode to facilitate
understanding and confirmation of the command line accuracy.
The log contains plenty of information, including the serial number, event number,
subscriber ID (IMSI or ISDN), operation time, operator, terminal ID, DBIO process, DBIO
module ID, operation result (success or failure error code), location of failed function call,
location of bottom layer function failure and message contents etc.
3.132 ZWF-05-15-002 Import/Export Tool

Specification:
3.132.1 Summary
Import/export tools are needed in subscription data cutover or move between HLRs.
3.132.2 Benefits
For operators

This feature facilitates move of a large amount of subscription data.
3.132.3 Description
An import tool is provided to import the Ericsson subscription data to ZTE HLR.
An import tool is provided to import the Siemens subscription data to ZTE HLR.
An import tool is provided to import the Alcatel subscription data to ZTE HLR.
An import tool is provided to import the HW subscription data to ZTE HLR.
3.133 ZWF-05-15-003 HLR Service Observation

Specification:
3.133.1 Benefits
For operators
3.133.2 Description
Service observation is to trace and display errors in the service processing process. The
detailed error codes can be reported with this function to facilitate error location by the
process and technical personnel.
Service observation is also responsible for statistics and analysis of some resources
used in service handling, e.g., data area use and session ID use.
3.134 ZWF-05-15-004 Signaling Tracing

Specification:

3.134.1 Benefits
For operators
3.134.2 Description
The signaling tracing function enables users to trace the signaling information of the
specific equipment, module, signaling link or subscriber. It is used to analyze the
accuracy of the transferred signaling. It provides operators with signaling content tracing
and display in telecom running and maintenance and technical personnel with
convenient means for problem location to find any error in signaling interworking for
further handling.
The signaling tracing system can trace the SS7 (MTP3 and above), MAP signaling and
remote interface machine messages etc.
The signaling tracing system can also filter signaling to be traced based on the specific
link or subscriber.
3.135 ZWF-05-15-005 HLR/AUC Query Terminal

Specification:
3.135.1 Benefits
For operators
Provide an abundant of queries method to the operator.
3.135.2 Description
It is a standalone maintenance tool that either can be resident in the server or be in the
any client who is connected to the Database server, the tool provides variety of
subscription statistics data of the subscriber database.
3.136 ZWF-05-15-006 GT addressing according to

CgPA and CdPA
Specification:

3.136.1 Summary
ZXUN USPP (HLR) supports the function of GT addressing according to CgPA and
CdPA
3.136.2 Benefits
For operators:
For different setting CgPA and CdPA, HLR can point to different bureau, so operators
can design their network flexibly.
3.136.3 Description
GT addressing in SCCP is determined not only by CdPA, but also by CgPA.
3.137 ZWF-05-15-007 Automatic Change Over to New

SIM Cards
Specification:
3.137.1 Summary
Automatic change to new SIM card allows to change the subscribers security
parameters by giving him a new system internal identity (IMSI, authentication algorithm,
Ki) while keeping his old MSISDN(s).
3.138 ZWF-05-15-008 File Management

Specification:

3.138.1 Benefits
For operators
3.138.2 Description
File management is a background tool for management of the foreground board files.
Through interactions with the foreground file system, the file management tool sends
instructions to the foreground file system. The latter then conducts the corresponding
operations on the specific files as instructed and returns the results to the file
management tool for management of the foreground files.
The following operations on foreground files are supported in file management:
File: Includes file copy, paste (between boards), upload, download, deletion and
renaming and display of related information.
Directory: Includes directory creation and deletion.
Volume: Includes volume information display.
Equipment: Includes equipment information display.
3.139 ZWF-05-15-009 Pre-alarm Function

Specification:
3.139.1 Summary
ZXUN USPP (HLR) support pre-alarm function. Pre-alarm function can collect fault
information of HLR and send alarm information to R&C of ZTE before fault occur.
3.139.2 Benefits
For operators
Pre-alarm function insures HLR high reliability and security.

3.140 ZWF-05-15-010 Statistic Function of

Provisioning
Specification:
3.140.1 Summary
Statistic function of provisioning measures BOSS interface performance. Statistic

function of provisioning measures success rate of provisioning.
3.140.2 Benefits
For operators
Operator can evaluate the provisioning performance exactly.
3.141 ZWF-05-15-011 Remote Client Function

3.141.1 Summary
The O&M server supports the remote client function. Operator can access the O&M data
through a remote client to manage the HLR/AUC.
3.141.2 Benefits
The remote client mode makes the construction and management of an HLR/AUC
convenient.
3.141.3 Description
The ZXUN USPP (HLR) O&M server adopts the Client-Server (CS) mode. In this way,
multiple sets of equipment can adopt one O&M server for management, which can be
done through multiple clients independently. Operator can access the O&M server
through the remote client.

3.142 ZWF-05-15-012 Telnet Function

3.142.1 Summary
The ZXUN USPP (HLR) O&M server supports the telnet function. Users can access the
HLR/AUC O&M server through telnet client.
3.142.2 Benefits
convenient.
3.142.3 Description
The ZXUN USPP (HLR) O&M server adopts the Telnet mode. Operator can access the
O&M server through the telnet client.
3.143 ZWF-05-15-013 Alarm Forward

3.143.1 Summary
The ZXUN USPP (HLR) O&M server supports the alarm forwarding function. Alarms
could be forward by e-mail or short message.
3.143.2 Benefits
convenient.
3.143.3 Description
Alarms could be forward through 2 ways:
l Email forwarding: Alarms could be sent to the operator’s email;

l Message forwarding: Alarms could be sent to the operator’s phone.
3.144 ZWF-05-15-014 Statistic function of roaming

subscribers
Specification:
3.144.1 Summary
With this feature, HLR can measure roaming subscribers and where the subscribers
visit.
3.144.2 Benefits
For Operators
With Statistic function of roaming subscribers, Operator can analyze the subscribers
roaming behavior and utilize the analysis result to establish management strategy.
3.145 ZWF-05-16-001 Querying Location information

through OMM
Specification:
3.145.1 Summary
ZXUN USPP (HLR) supports querying subscriber location information through OMM.
3.145.2 Benifits
For operators:
It provides operators a means to acquire specific subscriber’s location information.

3.145.3 Description
It can only be used by authorized operator. He can query the specific subscriber’s
current status and location information including detail zone information through OMM.
3.146 ZWF-05-16-004 Redundancy HLR for Backup

Multi-vendors' HLR
Specification:
3.146.1 Summary
With the feature “Redundancy HLR for Backup Multi-vendors' HLR”, the backup of HLR
data from several vendors' HLRs to the ZTE Backup HLR can be provided, to be able to
take-over the HLR service by the ZTE Backup HLR for one of the several vendors’ HLRs.
3.147 ZWF-05-16-006 Redundant HLR Send RESET

Message Time-sharing and Regionally
Specification:
3.147.1 Summary
After N+1 static redundant HLR(for Backup Multi-vendors' HLR) take over the service,
HLR send RESET message according to the customization. HLR send RESET message
to the specified MSC/VLR/SGSN list time-sharing.
Redundant HLR send Reset message automatically or manually. GUI is for stopping to
send reset message at any moment.
3.147.2 Benefits
For Operators
Provide method to control sending reset message for operator. Reduce impact about
SS7 because sending mass reset message.

3.148 ZWF-05-17-001 Roaming Plan Customization

Specification:
3.148.1 Summary
This feature is to specify a range of VLRs/SGSNs where subscriber roaming is allowed

so as to form a roaming plan as part of the subscribers’ subscription data. In this way,
operators are provided with flexible subscriber roaming restriction services.
The HLR system allows customization of a maximum of 10 roaming plans.
3.148.2 Benefits
For operators
This feature enables operators to provide roaming restriction services such as WLL
(Wireless Local Loop) or provide roaming restriction services for an end user separately,
thus increasing operators’ competitiveness.
For end-users
Compared with ordinary subscribers, a subscriber registering a roaming restriction

service such as WLL may enjoy a lower charge rate and save some expenses. In
addition, if an operator provides an end user with a roaming restriction service
separately, the end user can specify the regions where roaming and network access are
allowed, thus protecting his or her benefits.
3.148.3 Description
This feature provides operators with flexible subscriber roaming restriction services.
Without adding any additional network devices, operators can control end users so that
they can only roam and access the network in some specified VLR regions. The
subscribers will not be allowed to roam beyond these regions.
This feature also supports the profile setting function. Operators can specify some VLR
numbers as roaming restriction profiles. Then, end users having registered the roaming
plan restriction service just need to use these profiles indiscriminately, thus increasing
operators’ work efficiency.

The widest application of the VLR roaming restriction service is the WLL service. If the
operator specifies all local VLR numbers as a regional profile allowing subscriber
roaming, all end users having registered this roaming profile are only allowed to roam in
the specified region, such as a district, province or city.
3.149 ZWF-05-17-002 ODB Roaming Restriction

Specification:
3.149.1 Summary
This feature offers the ability to use the Operation Determined Barring feature (making
use specifically of Operator Determined Barring of Roaming) to restrict roaming outside
the Home PLMN or outside the Home PLMN country. This restriction is valid per
subscriber.
If the VLR number corresponds to a restricted region, the subscriber will be marked as
being in a restricted region. The subscriber is barred from roaming as a result in the
whole visiting PLMN.
3.149.2 Benefits
For operators
The operator will be able to avoid roaming of subscribers outside the Home
PLMN/Home PLMN country in a per subscriber basis (i.e., assigning this characteristic
like a subscriber service).
3.149.3 Description
When LOCATION UPDATING/LOCATION GPRS UPDATING message reception, HLR

checks the received VLR/SGSN address. If Operator Determined Barring of Roaming is
assigned to given subscriber and the barring condition is fulfilled (outside HPLMN or
outside Home PLMN country) the operation is refused and subscriber location is set to
"barred".
If assignation of Operator Determined Barring of Roaming is performed for a given

subscriber and he/she is located in a VLR/SGSN, this address is checked to see if the
barring condition is fulfilled (outside HPLMN or outside Home PLMN country). If so,
subscriber location is set to "barred" and a CANCEL LOCATION is sent to VLR/SGSN.

3.150 ZWF-05-17-004 CAMEL: Roaming Subscriber

Table
Specification:
3.150.1 Summary
This feature allows the control of international roaming for CAMEL subscribers inside
every VLR/SGSN of an operator PLMN based on CAMEL roaming agreements. The
GSM roaming is not affected by this feature.
During the location update procedure of foreign PLMN CAMEL subscribers, the CAMEL
roaming agreement status with the subscribers Home PLMN will be checked in the
visited VLR/SGSN. The network operator can enter all foreign PLMNs whose roaming
subscribers are allowed to subscribe to CAMEL in the operator's PLMN (White List for
CAMEL supporting foreign PLMNs) in the CAMEL Roaming subscriber Table in the HLR.
CAMEL subscribers can be restricted in their use of CAMEL services to VPLMNs which
are listed in the CAMEL Roaming Subscriber Table.
3.150.2 Benefits
For operators
GSM network operators can introduce special CAMEL roaming agreements including all
technical and commercial consequences. To technically control CAMEL roaming
operators can use this feature as a tool to limit the CAMEL service subscription by
international roaming subscribers according to valid CAMEL roaming agreements.
3.151 ZWF-05-17-005 Roaming Restrictions List of

CC-NDC
Specification:
3.151.1 Summary
Generally, most operators provide the international roaming service and roaming
between different operators. This feature allows operators to control subscriber roaming
so that subscribers can only roam within the range specified by them.

3.151.2 Description
Roaming area control is made possible by configuring the CC (Country Code) and NDC
(Network Destination Code) of the VPLMN network where subscribers are allowed to
roam. During location update of a subscriber, if the VLR’s CC and NDC are within the
allowed CC and NDC list, the subscriber is allowed to roam in that area. Otherwise, the
location update will be rejected and the subscriber will fail in login to the network.
Configuration of the roaming area control function is very flexible. The maximum number
of allowed CCs and NDCs is 2048.
This feature is aimed at all subscribers in HLR, which cannot be set for a single
subscriber.
The roam restriction above may apply on option for CS domain only, for PS only or for
both CS and PS.
3.152 ZWF-05-17-007 CAMEL Compatibility Control

Specification:
3.152.1 Summary
There two factors affect the CAMEL service application when subscriber roams out of
local PLMN or HPLMN, one is interoperability of network entity involved, another is
CAMEL agreement of the operators involved. CAMEL compatibility control feature
enables operator to flexibly configure CAMEL service processing in HLR based on
subscriber according their requirements. For example, operator can specify that the
CAMEL logic is invoked only when subscriber is roaming in specific area based on
servicekey, operator also can specify whether subscriber is allowed to roam when
VMSC doesn’t support CAMEL and can specify whether subscriber is allowed to be
called when GMSC doesn’t support CAMEL.
3.152.2 Benefits
For operators
CAMEL compatibility control feature enables operator to flexibly configure CAMEL

service processing in HLR based on subscriber according their requirements.

3.152.3 Description
ZTE HLR provides the following implementation:
l ZTE HLR allows pre-paid subscribers to register in networks supporting only CAP
Ph.1. All mobile originated and all mobile terminating services - voice services as
well as non-voice services - are barred.
l ZTE HLR sends Subscriber Status “Operator Determined Barring” and ODB
“barring of all outgoing calls” to the VLR to bar mobile originated services including
speech and MO-SMS for outbound roaming pre-paid subscribers if the VLR
supports only CAP Ph.1. Because ODB “barring of all outgoing calls” is set,
subscribers can’t register CF and use any CF services.
l If ODB is not supported by the VLR, ZTE HLR sends "Roaming Restriction Due To
Unsupported Feature" to bar mobile originated services including speech and MO-
SMS for outbound roaming pre-paid subscribers. Because of "Roaming Restriction
Due To Unsupported Feature", subscribers can’t register CF and can’t use any CF
services.
l ZTE HLR supports CAP Ph.2 and CAP Ph.3.
The CAP Ph.2 trigger information that is stored in the HLR is related to voice
services and to circuit switched data services. The CAP PH.2 trigger information is
sent to the VLR if the VLR supports CAP Ph.2 or higher and if voice service or
circuit data service is allowed in the VPLMN.
The CAP Ph.3 trigger information that is stored in the HLR is related to packet data
services. The CAP Ph.3 trigger information is sent to the SGSN if the SGSN
supports CAP Ph.3 and if packet data service is allowed in the VPLMN.
CAP Ph.3 trigger information for SMS is sent to the SGSN/VLR if the SGSN/VLR
supports CAP Ph.3 and if SMS is allowed in the VPLMN.
3.153 ZWF-05-18-001 Length-variable NDC and

Multiple NDCs Function
Specification:
3.153.1 Benefits
For operators

This feature allows an operator to have multiple NDCs of different length. This resolves
the problem of NDC length inconsistency for some operators. For example, some
operators having no mobile business operation right cannot get the corresponding NDCs.
They can use toll area codes to replace these NDCs or some virtual operators can
cooperate with multiple other operators to use the latter’s NDCs for service development
(the NDC length of these operators varies).
3.153.2 Description
HLR supports the length-variable NDC function. More specifically, it supports

configuration of length-variable local and all domestic Network Access Codes (NDCs) to
meet some operators’ requirements for length-variable NDCs.
ZXUN USPP (HLR) allows one operator to have a maximum of 192 NDCs (maximum 64
(local) + maximum 128 (domestic)). Variable length of these NDCs is allowed between
one to 4 digits.
3.154 ZWF-05-18-002 HLR’s Multi-MNC Function

Specification:
3.154.1 Benefits
For operators
This feature enables an operator to have multiple MNCs. In reality, one operator may
have multiple MNCs. For example, some large operators have a large amount of
subscribers. When the IMSI number resources are insufficient, IMSI number segments
of different MNCs have to be used. In addition, some virtual operators working together
with multiple operators to develop services may use other operators’ IMSIs to develop
subscribers. This requires that IMSI numbers in HLR have different MNCs. The multi-
MNC function allows one operator to have a maximum of 10 different MNCs.
3.154.2 Description
HLR supports the multi-MNC function and number allocation to SIM cards of different
MNCs. One operator can have different MNCs to meet the requirements for centralized
management of different MNCs’ SIM cards and subscription data.

3.155 ZWF-05-18-003 Virtual HLR

Specification:
3.155.1 Summary
This feature provides a solution for operators to save the investment cost in regions with
sparsely distributed mobile subscribers.
3.155.2 Benefits
For operators
This feature enables operators to reduce the number of physical HLRs and the
investment cost by combining subscription data in different regions. The virtual HLR is
very applicable to the initial stage of network construction when the subscriber quantity
is low but the required coverage area is wide and regions where subscribers are
sparsely distributed. In addition, the data of subscribers with different access network
codes can be saved to the same physical HLR to provide centralized management and
maintenance of subscription data.
3.155.3 Description
If the traditional HLR construction plan is adopted for regions where mobile subscribers
are sparsely distributed, it may be unable to fully utilize the capabilities of each HLR
device. To save the business operation investment, the virtual HLR technology can be
adopted to save subscription data of multiple such regions to one physical HLR and
divide this physical HLR into multiple virtual HLRs logically according to the
administrative region division. Then, by means of authority division, the maintenance
personnel in each region can transparently process subscriber information in the
corresponding virtual HLR.
HLR supports a maximum of 255 virtual HLRs. This fully satisfies operators’
requirements.
3.156 ZWF-05-18-004 HLR’s Support for Both 2G and

3G Subscribers
Specification:

3.156.1 Summary
This feature facilitates network planning and NE setting.
3.156.2 Benefits
For operators
This feature facilitates network planning and NE setting by operators. In addition, at the
initial stage of 3G service development, the quantity of 3G subscribers is low. In this
case, HLR’s support for 2G subscribers saves the equipment investment for operators at
the initial stage of network construction.
3.156.3 Description
This feature includes the following sub-functions:
Supporting authentication information storage for 2G subscribers
Supporting GSM/GPRS network authentication algorithm
Supporting GSM/GPRS network authentication flow
Supporting service subscription and data storage for 2G subscribers
Supporting service subscription and data storage for 3G subscribers
Supporting WCDMA network authentication algorithm
Supporting WCDMA network authentication flow
Supporting roaming of 2G subscribers to GSM/GPRS network
Supporting roaming of 2G subscribers to WCDMA network
Supporting roaming of 3G subscribers to GSM/GPRS network
Supporting roaming of 3G subscribers to WCDMA network
3.157 ZWF-05-18-007 Migration GSM Subscriber to

UMTS Subscriber without Changing SIM and
MSISDN
Specification:

3.157.1 Summary
The feature provides the functionality that migrates the 2G subscriber into 3G subscriber
neither change the SIM card nor change the original phone number, it is helpful that
operator migrates their 2G subscriber to 3G network and raises the service satisfaction
and subscriber’s faithfulness
3.157.2 Benifits
For operators
It provides feasibility to Operator owned 3G license that migrates 2G subscribers to 3G

networks and raises the service satisfaction and subscriber’s faithfulness
For end-users
It provides feasibility to Subscribers that subscriber can enjoy 3G service by doing

nothing but dialing the Call-Center number.
3.158 ZWF-05-18-008 MSISDN Assignment over NDC

Boundaries
Specification:
3.158.1 Summary
This feature enables the HLR operator to assign MSISDNs with different NDCs to a
mobile subscriber, e.g. the MSISDN assigned to “Telephony” may contain another NDC
than the MSISDN assigned to the “Fax-Service”.
In general each NDC makes it possible to manage a certain range of MSISDNs. If this
amount of MSISDNs is distributed to the subscribers and one of these subscribers may
want to use Fax Service in addition, he needs a MSISDN for that Service. But there is no
chance to get a MSISDN within the same NDC range the Service Telephony is provided.
Without this feature it's necessary to assign two new MSISDNs for this mobile subscriber
within the next NDC range the operator is able to administer, because until now it's not
possible to assign different NDCs to a single mobile subscriber.
With this feature it is possible to assign for the same mobile subscriber a new MSISDN
for the additional Service, e.g. Fax with a different NDC than the Service Telephony.
Possible Applications:

In many countries it is a normal behavior to assign MSISDNs for the mobile network out
of the numbering plan of the fixed network. Therefore the mobile network operator has to
be able to assign MSISDNs with different NDCs to a single subscriber in parallel, as
NDCs are just indicating numbering blocks of the fixed network.
3.158.2 Benefits
For operators
Operators who are allowed to assign their mobile subscribers to more than one NDC
now are no longer forced to administer one mobile subscriber within the same NDC
range. This means it's not necessary to “take care” about the NDC he distributes to
whom.
The operator can use his range of MSISDN according to the NDC more flexible.
For Subscriber
Subscribers are not affected by a change of their MSISDN due to a shortage of free
additional numbers within their own NDC range when subscribing to fax or data services
which require additional MSISDNs.
3.159 ZWF-05-18-010 Support of 3 Digits MNC

Specification:
3.159.1 Summary
A PLMN is characterized by a Mobile Country Code (MCC) and a Mobile Network Code
(MNC).
MNC on 2 or 3 digits are supported, according to GSM recommendations evolution.
3.160 ZWF-05-18-012 MVNO (Network Sharing)

Specification: 3GPP 22.951

3.160.1 Summary
Network sharing is becoming more and more popular as a mean to provide coverage
quickly and in a cost efficient way. The high price paid for the license in some countries
as well as mergers, acquisitions have raised recently high interest in this topic.
This feature enables the MVNO (Mobile Virtual Network Operator) to deployment HLR.
This feature enables the MNO (Mobile Network Operator) to deployment HLR also.
3.160.2 Description
Network Sharing Scenarios:
Scenario1: Multiple core networks sharing common radio access network. For operators
that have multiple frequency allocations it is possible to share the RAN elements, but not
to share the radio frequencies. In this case the operators connect directly to their own
dedicated carrier layer in the shared RNC in the shared RAN. This solution is possible
with 3GPP Release 99 and is illustrated below in Figure 3-7 for the case when two
operators have one license each.
Figure 3-7 multiple core networks sharing common radio access network
Operator one Shared RNC Shared Node B
Frequency one MNC

Operator two Frequency one
one
Frequency two Frequency two MNC

two
Figure 3-7: The figure illustrates how it is possible to within the 3GPP Release 99
framework have dedicated carrier layers in the RAN for multiple operators. The
operators transmit their own mobile network code (MNC) on their dedicated carrier
Scenario2: Geographically split networks sharing:
This scenario can be divided into following cases:
u When two (or more operators) employ national roaming for the users, which
implies that only one core network will be associated with each radio access
network. Care is obviously needed when coverage regions overlap, which makes
this a valid shared-networks scenario. This case is shown in Figure 3-8.

u The operators can have their individual core networks connected to both radio
access networks throughout the entire coverage area, but utilizing the different
operator’s allocated spectrum in different parts of the coverage area. There will
thus be multiple core network operators in each of the shared radio access
networks. The connection of the core networks to the radio access networks can
either be done by connecting the radio network controllers to both operators' core
network elements or by sharing parts of the core network, e.g. SGSNs and/or
MSCs. The work on shared networks in Rel-6 should not make any of these
possibilities mandatory and it should be the choice of the operator which one is
implemented. Additionally it should, be possible to introduce Iu-flex functionality
between the common core network parts and the radio access network for purely
load-sharing purposes. Shown in Figure 3-9.
Figure 3-8 Geographically split network using national roaming between operators
Core Network Core Network

A B
Radio Access Radio Access

Network Network
A B
Figure 3-9 Geographically split shared radio networks scenarios with dedicated or
common core networks

A B

Network Network
A B

A B
Common core
A+B

Network Network
A B
Scenario 3: Common network sharing
PDF 文件使用 "pdfFactory" 试用版本创建昳ÿ

www.fineprint.cn
昳ÿ
In this scenario, one operator will deploy coverage in a specific geographical area, and
other operators will be allowed to use this coverage for their subscribers. Outside this
geographical area, coverage is provided by each of the operators.
Scenario 4: Common spectrum network sharing
Common spectrum network sharing is applicable when:
l One operator has a 3G license and shares the allocated spectrum with other
operators.
l A number of operators decide to pool their allocated spectrums and share the total
spectrum (operators without allocated spectrum may also share this pooled
spectrum).
The scenario can be realized as follows.
l Connecting each operator’s core networks and to the shared radio access
network(s), sees case 1 in Figure 3-10 below (only 1 radio network controller for
simplicity). In this case it should be possible that one or more of the core network
operators use Iu Flex between their core network and the shared radio access
network. The technical realization of this scenario may reuse some of the
mechanisms already specified in REL-5 Iu-Flex. Described in the figure below are
three network operators, A, B and C. Operators A and C are not using multiple core
network nodes (CN) and therefore may not need to use Iu-Flex. Operator B is using
multiple CNs and has decided to use Iu-Flex to enable the intra-domain sharing of
CNs
l The core network entities connected to radio access network can be shared, see
case 2 in Figure 3-10 below.
Figure 3-10 Two different cases of common spectrum network sharing
Operator B's CN nodes

No Iu Flex using Iu Flex No Iu Flex
Operator A Op. B's Op. B's Op. B's Operator C

CN node CN node CN node CN node CN node
Iu Flex
Iu interface
Radio Network Controller

Operator X

席ù席ù

A B
Common Core
A+B
Radio Access
Network
A
Scenario 5: Multiple radio access networks sharing common core network:
In this scenario multiple radio access networks share a common network. The multiple
RANs can belong to different PLMNs and network operators. Due to operators’
deployment different nodes or part of the common core network i.e. HSS/HLR, SGSN
etc can be shared.
The scenario is depicted in the Figure 3-11 below:
Figure 3-11 Multiple radio access networks sharing common core network
Common Core Network

A+B+C
Radio Access Radio Access Radio Access

Network Network Network
A B C
3.161 ZWF-05-18-016 Multiple MCC

Specification:
3.161.1 Summary
ZXUN USPP (HLR) supports multiple MCC. The IMSI of different country could be
stored, provisioned and processed by ZXUN USPP.

3.161.2 Benefits
It serves for MNVO who run the network cover many countries.
3.162 ZWF-05-18-017 NTP Support

Specification: RFC1305
3.162.1 Summary
Provide the function of network time proofing.
3.162.2 Benefit
By means of external universal network clock server that provides precise time, clocks of
each module and unit in the system can be adjusted into precisely universal so that the
system’s time universality can be ensured.
3.162.3 Description
System, as NTP client, interacts with NTP server through NTP protocol, is promptly time
synchronized by NTP server and synchronizes other modules in the system. It ensures
that each component in the system is precise and time universal.
3.163 ZWF-05-18-018 Network Identity and Time

Zone
Specification: 3GPP TS: 22.042, 23.038, 24.008, 29.018
3.163.1 Summary
This feature provides the means for the serving PLMNs to transfer current Network
Identity, Universal Time (UT), Local Time Zone (LTZ) and Daylight Saving Time (DST) to
Mobile Stations/User Equipments (MS/UE). The identity consists of the short network
name and the long network name.

3.163.2 Benefit
This feature enhances roaming by permitting accurate indication of PLMN identities that
are either newer than the MS/UE has changed their name since the MS/UE was sold.
Additionally the Universal Time, Local Time Zone and the Daylight Saving Time
information can be utilized by MSs/UEs as desired. For instance, when the subscriber
travels and changes the time zone, the MS/UE can show the local time on the display.
By including the Daylight Saving Time component in the NITZ message other
applications in the MS/UE (mainly the Calendar application), can distinguish between
the two parameters, LTZ and DST.
3.163.3 Description
The NITZ information will be send after Location Updating procedure, either via A, Iu, or
Gs interface. When the subscriber registers in the MSC/VLR or performs a location
updating indicating IMSI attach, the NITZ information is provided to the MS/UE.
The change of the network identity or time adjustments in the MSC/VLR will not initiate
any immediate update procedures towards the MS/UE but the update of the information
depends on the user activities (power on/off, subscriber changes the MSC/VLR area).
This is done to avoid sudden bursts of network signaling.
The NITZ information will be provided to the MS/UE, either using the new MM
INFORMATION (TS.24.008) message when the procedure was initiated over the A or Iu
interface, or using the new MM INORMATION REQUEST (TS 29.018) procedure when
the procedure was initiated over the Gs interface. All information elements are included
in the message, if they are available in the MSC/VLR:
l Long name for the network
The coding scheme “Cell Broadcast data coding scheme, GSM default alphabet,
language unspecified” is used.
l Short name for the network
The coding scheme “Cell Broadcast data coding scheme, GSM default alphabet,
language unspecified” is used.
l Local Time Zone
Universal Time and Local Time Zone
l Daylight Saving Time.
This optional information element is included if the Local Time Zone is included in the
message. If no summer time adjustment applies, the Daylight Saving Time shall indicate
‘no adjustment’.

l IMSI (Gs interface only)
This information element is included only if the interface is Gs.
The NI and TZ information can be displayed separately.
The NITZ information can be displayed according to IMSI range.

Zte 1 Config PDF

Uploaded by

Copyright:

Available Formats

Zte 1 Config PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Zte 1 Config PDF

Uploaded by

Copyright:

Available Formats

ZXUN USPP Series HLR AUC Feature Description

ZXUN USPP Series HLR AUC

ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. I

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

ZXUN USPP Series HLR AUC Feature Description

Version Date Author Approved By Remarks

V1.00 2010-03-18 Not open to the Third Party

© 2011 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. I

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

ZXUN USPP Series HLR AUC Feature List ...................................................................... I

2 Basic Features .................................................................................................1

II ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

2.37 ZWF-05-04-017 3G Authentication Function .................................................32

3 Optional Features ..........................................................................................57

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

3.19 ZWF-05-10-019 CAMEL4 Service.................................................................81

IV ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

3.66 ZWF-05-10-066 SSET (Service Set) ...........................................................130

ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. V

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

3.116 ZWF-05-14-014 SCCP Congestion Control ................................................173

VI ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

Figure 2-1 SIGTRAN protocol ............................................................................................ 35

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

2.1 ZWF-05-01-001 SIM State Management

Implemented in: ZXUN USPP (HLR)

l Service halt report

ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. 1

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

2.2 ZWF-05-01-002 Telephony Subscription

Implemented in: ZXUN USPP (HLR)

This feature provides a subscription for the Teleservice Telephony (TS11).

l Transparency for telephone signaling tones is provided.

l Transparency for voice band facsimile signals is not mandatory

l Transmission of DTMF is provided in the mobile to fixed direction (e.g. for

2 ©2011 ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

2.3 ZWF-05-01-003 R98 GPRS Service

Implemented in: ZXUN USPP (HLR)

HLR provides the following categories of R98 GPRS-related subscription data:

PDP Context information:

Each group of PDP Context contains the following information:

ZTE Confidential Proprietary © 2011 ZTE CORPORATION. All rights reserved. 3

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

PDP address: Refers to the static PDP address.

AccessPointName: Is the external network access ID.

Whether allowing subscribers to use addresses dynamically allocated in VPLMN

The QoS (Quality of Service) contains:

Priority: Includes High Priority, Normal priority and Low priority.

Delay class: Includes 1-4.

Peak throughput class

Mean throughput class

PDP billing features

2.4 ZWF-05-01-004 2G Authentication Information

Implemented in: ZXUN USPP (HLR)