GSM R Hlr9820

GSM-R HLR9820 V900R003 Feature
Description

Issue 1.0
Date 2013-02-25
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other
trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the commercial contract made
between Huawei and the customer. All or partial products, services and features described in this
document may not be within the purchased scope or the usage scope. Unless otherwise agreed by
the contract, all statements, information, and recommendations in this document are provided AS
IS without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in
the preparation of this document to ensure accuracy of the contents, but all statements, information,
and recommendations in this document do not constitute the warranty of any kind, express or
implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

Huawei HLR9820 V900R003
Feature Description

Issue 1.0 (2013-02-25)
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Page 3 of 177

Contents
1 Basic Features ....................................................................................................................... 4
1.1 WHFD-020000 Teleservices ................................................................................................................ 4
1.2 WHFD-030000 Supplementary Services ............................................................................................. 8
1.3 WHFD-040000 Operator Determined Barring (ODB) ....................................................................... 24
1.4 WHFD-050000 Other Services .......................................................................................................... 37
1.5 WHFD-060000 Mobility Services ..................................................................................................... 41
1.6 WHFD-070000 Call Handling Services ............................................................................................. 51
1.7 WHFD-080000 SS-Specific Services ................................................................................................ 54
1.8 WHFD-090000 Subscriber Data Management .................................................................................. 60
1.9 WHFD-100000 Protocol Interfaces .................................................................................................... 71
1.10 WHFD-110000 Operation and Maintenance Functions ................................................................... 75
1.11 WHFD-120000 Reliability Functions .............................................................................................. 88
2 Optional Features ............................................................................................................ 111
2.1 WHFD-510000 CS Data Services .................................................................................................... 111
2.2 WHFD-520000 GPRS Services ....................................................................................................... 112
2.3 WHFD-030000 Supplementary Services ......................................................................................... 116
2.4 WHFD-530000 CAMEL Services ................................................................................................... 121
2.5 WHFD-540000 Location Services (LCS) ........................................................................................ 125
2.6 WHFD-050000 Other Services ........................................................................................................ 126
2.7 WHFD-060000 Mobility Services ................................................................................................... 129
2.8 WHFD-090000 Subscriber Data Management ................................................................................ 131
2.9 WHFD-560000 Networking Functions ............................................................................................ 132
2.10 WHFD-570000 Enhanced Functions ............................................................................................. 137
2.11 WHFD-130000 Authentication Centre Functions .......................................................................... 164
2.12 WHFD-570403 Redundancy Functions ......................................................................................... 171

Feature Description

Issue 1.0 (2013-02-25)
Page 4 of 177

1 Basic Features
This document briefly describes the functions of the HLR9820, and is intended to help
the user understand the functions of the product.
1.1 WHFD-020000 Teleservices
The HLR9820 supports basic teleservices, which consist of the speech service
(WHFD-020100) and the short message service (WHFD-020200).
The speech service is the elementary feature of a telecom network. This service
consists of the following functions:
Telephony, that is, TS11 (WHFD-020101)
Emergency call, that is, TS12 (WHFD-020102)
The length of information sent in the short messages is short. Specified by ETSI GSM
03.40 and ETSI GSM 03.41 in ETSI GSM, a point to point (PTP) short message (SM)
can have a maximum of 140 bytes in size, that is, 160 ASCII characters or 70 Chinese
characters. A broadcast SM can have 82 bytes per page, that is, 92 ASCII characters or
41 Chinese characters. A macro broadcast message can have a maximum of 15 pages
that are sent continuously.
The broadcast SMS allows subscribers to receive public information periodically and
selectively. The PTP SMS allows subscribers to send or receive SMs at any time. The
PTP SMSs can be categorized as follows:
Short Message MT/PP, that is, TS21 (WHFD-020201)
Short Message MO/PP, that is, TS22 (WHFD-020202)
1.1.1 WHFD-020101 Telephony (TS11)
Availability
This service is inherited from HLR9820 V600.

Feature Description

Issue 1.0 (2013-02-25)
Page 5 of 177

Specification
3GPP29002 and 3GPP22003
Summary
This function enables mobile subscribers to communicate with the subscribers in the
PSTN, ISDN and PLMN over telephones.
Benefits
For carriers
The function allows carriers to add subscribers to different basic service groups,
and increase network traffics volume, thus increasing the revenue.
For subscribers
The function allows the subscriber to enjoy basic voice service.
Description
The HLR9820 supports subscription and modification of this service. When a
subscriber subscribes to the service and updates his/her location, the HLR sends the
data of the service to the VLR. When a subscriber withdraws the service, the HLR
initiates the subscriber data deletion flow to the VLR.
Dependency
The HLR9820 implements the function independently. There is no special requirement
for other NEs.
1.1.2 WHFD-020102 Emergency Call (TS12)
Availability
Specification
3GPP29002 and 3GPP22003
Summary
The function allows a subscriber to make an emergency call,112 and 119 for example.
When a subscriber is not registered or calls into/from the subscriber are barred, the
subscriber can make an emergency call.
Benefits
For carriers
The function allows a subscriber to make an emergency call,

Feature Description

Issue 1.0 (2013-02-25)
Page 6 of 177

For subscribers
The function allows the subscriber to make an emergency call for helps.
Description
By default, the HLR provides the emergency call service to the subscriber. When the
location of a subscriber is updated, the HLR sends the service data to the VLR.
Dependency
for other NEs.
1.1.3 WHFD-020201 Short Message MT/PP (TS21)
Availability
Specification
3GPP29002, 3GPP23039, 3GPP23040, 3GPP23041, 3GPP24011, and 3GPP24012
Summary
The Short Message MT/PP service refers to the service that enables the short message
center (SMC) to send short messages to the MS.
Benefits
For carriers
This service can expand the traffic volume and increase the average revenue per
user (ARPU).
For subscribers
This service diversifies the communication modes. When voice conversation is
inconvenient, the subscriber can keep contact with others through short messages.
Description
The HLR enables a subscriber to receive short messages. When the subscriber serves
as the callee, that is, another subscriber intends to send a short message to the
subscriber and the SMC sends a message to the HLR, requesting it to provide the MSC
number or SGSN number of the callee. Upon receiving the request, the HLR returns a
message based on the subscription information and status of the subscriber.
Enhancement
To improve the success rate in receiving short messages, the HLR9820 allows you to
configure the short message transmission route for subscribers adopting the network

Feature Description

Issue 1.0 (2013-02-25)
Page 7 of 177

access mode of MSC or SGSN (the subscribers can access the network in the CS and
PS domains). In the case of SGSN, the HLR carries the SGSN address in the response
message to the short message routing request. In the case of MSC, the HLR only
carries the MSC address in the response message.
Dependency
The HLR9820 implements the function in compliance with standard protocols. The
SMC equipment for the service is required.
1.1.4 WHFD-020202 Short Message MO/PP (TS22)
Availability
Specification
3GPP29002, 3GPP23039, 3GPP23040, 3GPP23041, 3GPP24011, and 3GPP24012
Summary
The Short Message MO/PP service refers to the service that enables the MS to send
short message to the SMC.
Benefits
For carriers
user (ARPU).
For subscribers
Description
The HLR enables the MS to send short messages. When the location of a subscriber is
updated, the HLR sends the related subscription data to the VLR. When the subscriber
sends short messages, the VLR provides Short Message MO/PP service for the
subscriber according to the subscription information of the subscriber.
Dependency
The HLR9820 implements the function in compliance with standard protocols. The
SMC equipment for the service is required.

Feature Description

Issue 1.0 (2013-02-25)
Page 8 of 177

1.2 WHFD-030000 Supplementary Services
The HLR9820 provides standard supplementary services, including:
Call Forwarding (CF) Services(WHFD-030100)

Call Barring Services(WHFD-030200)
Number Identification Services(WHFD-030300)
The supplementary services of the optional function include:
Call Waiting/Call Hold (CW/CH)
Multi Party (MPTY)
Unstructured Supplementary Service Data (USSD)
Closed User Group (CUG)
PLMN Specific Supplementary Services (PLMNSS)
CF services consist of the following services:
Call Forwarding Unconditional (CFU) (WHFD-030101)
Call Forwarding on Mobile Subscriber Busy (CFB) (WHFD-030102)
Call Forwarding on No Reply (CFNR) (WHFD-030102)
Call Forwarding on Mobile Subscriber Not Reachable (CFNRc) (WHFD-030104)
ODB services consist of BAOC and BAIC services. The HLR9820 provides standard
CB services.
Barring of All Outgoing Calls (BAOC) (WHFD-030201)
Barring of Outgoing International Calls (WHFD-030202)
Barring of Outgoing International Calls Except Those Directed to the Home
PLMN Country (BOIC-exHC) (WHFD-030203).
Barring of All Incoming Calls (BAIC) (WHFD-030204)
Barring of Outgoing Calls when Roaming Outside the Home PLMN Country
(BICROAM) (WHFD-030205)
The Number Identification Services includes:
Calling Line Identification Presentation (CLIP) (WHFD-030301)
Calling Line Identification Restriction (CLIR) (WHFD-030302)
Connected Line Identification Presentation (COLP) (WHFD-030303)
Connected Line Identification Restriction (COLR) (WHFD-030304)
Override Calling Line Identification Restriction (OVER-CLIR) (WHFD-030305)
Override Connected Line Identification Restriction (OVER-COLR)
(WHFD-030306)

Feature Description

Issue 1.0 (2013-02-25)
Page 9 of 177

1.2.1 WHFD-030101 Call Forwarding Unconditional (CFU)
Availability
Specification
3GPP29002, 3GPP22082, 3GPP23082, and 3GPP24082
Summary
When a mobile subscriber serves as the callee, all calls are forwarded to a third party,
regardless of status of the subscriber's MS. The third party can be either a
PLMN/PSTN/ISDN subscriber or a service console (such as voice mailbox).
Benefits
For carriers
Carriers can forward calls more flexibly and increase call completion rate, thus
boosting the revenue.
For subscribers
When the subscriber cannot use his/her MS, or does not want to use the MS, the
subscriber can forward an incoming call to another MS without affecting the
conversation. This service provides more options for the subscriber to enjoy the
telecommunication service.
Description
The HLR supports subscribing/withdrawing and activating/deactivating the service.
Meanwhile, the HLR stores the forwarded-to number (FTN) registered by the
subscriber, and carries the FTN in the response message to the routing message from
the GMSC. The subscriber can activate the service through his/her mobile phone or in
the business hall of carriers.
Dependency
for other NEs.
1.2.2 WHFD-030102 Call Forwarding on Mobile Subscriber Busy
(CFB)
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 10 of 177

Specification
Summary
Based on the forwarding cause, the CFB is classified into network determined user
busy (NDUB) and user determined user busy (UDUB). When a mobile subscriber
serves as the callee, if the subscriber is in a conversation (the line is busy due to
network cause) or the subscriber rejects the incoming call (the line is busy due to the
subscriber's cause), the call is forwarded to a third party. The third party can be either a
PLMN/PSTN/ISDN subscriber or a service console (such as voice mailbox).
Benefits
For carriers
For subscribers
When the subscriber cannot use his/her MS, or does not want to use the MS, the
Description
The HLR supports subscription or withdrawal, and activation or deactivation of this
service. The HLR stores the FTNs. If the location of a subscriber changes, the HLR
sends the FTN to the VLR. If the subscriber receives a call when the subscriber's line
is busy, the VLR of the callee, knowing that the subscriber has subscribed to the call
forwarding service, initiates a route setup request to the corresponding HLR according
to the FTN, and establishes a connection to the MSC of the third-party subscriber. The
subscriber can activate the service through his/her mobile phone or in the business hall
of carriers.
Dependency
for other NEs.
1.2.3 WHFD-030103 Call Forwarding on no Reply (CFNRy)
Availability
Specification

Feature Description

Issue 1.0 (2013-02-25)
Page 11 of 177

Summary
A service that allows an incoming call to be forwarded to a third party when a mobile
subscriber does not answer after being alerted for a long time and the timer expires.
The third party can be either a PLMN/PSTN/ISDN subscriber or a service console
(such as voice mailbox).
Benefits
For carriers
For subscribers
When the subscriber cannot use the MS, or does not want to use the MS, the
Description
service. The HLR stores the FTNs. If the location of a subscriber changes, the HLR
sends the FTN to the VLR. Meanwhile, the HLR also sends a message with no-reply
time length to the VLR. When the subscriber's line is busy, if a call to the subscriber
remains unanswered for a period exceeding the specified time length, the VLR of the
callee initiates a route setup request to the corresponding HLR according to the FTN,
and establishes a connection to the MSC of the third-party subscriber. The subscriber
can activate the service through his/her mobile phone or in the business hall of carriers.
The subscriber can activate the service through his/her mobile phone or in the business
hall of carriers.
Dependency
for other NEs.
1.2.4 WHFD-030104 Call Forwarding on Mobile Subscriber not
Reachable (CFNRc)
Availability
Specification

Feature Description

Issue 1.0 (2013-02-25)
Page 12 of 177

Summary
The third party can be either a PLMN/PSTN/ISDN subscriber or a service console
(such as voice mailbox).
Benefits
For carriers
For subscribers
If the MS of a subscriber is turned off or the quality of the signals received by the
MS is poor, the subscriber can forward an incoming call to another MS without
affecting the conversation.
Description
service. To use the service, the subscriber must register the service in the business hall
of carriers, and then activate the service. The subscriber can activate the service
through his/her mobile phone or in the business hall. When a subscriber is unreachable,
it involves two occasions:
The HLR has stored the information on the unreachable subscriber. For example,
when a subscriber remains offline for a long time, the HLR reconfigures the flag
bit of the subscriber to indicate that the subscriber is unreachable.
The HLR does not know the reason why the subscriber is unreachable. For
example, the subscriber's MS is turned off or cannot receive any signals.
If the HLR knows the reason why the subscriber is unreachable, the MSC of the caller
carries the FTN in the response message to the HLR's routing request message. In this
case, the MSC of the caller initiates a route request to the third-party subscriber
according to the FTN in the returned message. If the HLR does not know the reason
why the subscriber is unreachable, it does not send the FTN to the MSC of the caller.
The MSC of the caller firs establishes a call connection to the MSC of the callee, and
the MSC of the callee then initiates a call route request to the HLR of the third-party
subscriber.
Dependency
for other NEs.
1.2.5 WHFD-030105 Forwarded-to Number Analysis and
Regulation
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 13 of 177

Specification
None.
Summary
This function allows you to configure the forwarding service data in the HLR. When a
subscriber registers the forwarding service, FTNs of correct format can be generated
and stored in the databases of the HLR.
Benefits
For carriers
The function allows carriers to configure the call forwarding service flexibly.
For subscribers
The function helps the subscriber to set a forwarded-to number.
Description
The request for registering the call forwarding service received by the HLR contains
FTNs. These FTNs adopt the following formats:
Unknown format (or domestic format): 81 + FTN inputted by the subscriber:
81 + fixed telephone number
81 + 0 + area code + fixed telephone number
81 + PLMN number
International format
91 + country code (CC)+ area code (AC)+ fixed telephone number
91 + PLMN number
Currently, the FTN registered in the MS adopts the unknown format. The HLR
regulates the received FTNs. The FTNs saved in the database and those sent to the MS
adopt the international format. You can only judge the attribute of a regulated FTN, for
example, check whether the FTN is in the homeland or the FTN is in the local network.
To regulate the FTNs, you need to configure the related data in the HLR.
Enhancement
To enable the HLR to regulate the FTNs, you need to configure the following data:
Local office information
The table contains only one record, which describes the country code of the area
where the HLR is located and HLR number. When it is necessary to know the
country code of an FTN but the FTN does not carry a country code, the HLR uses
the country code in the table as the country code of the regulated FTN.
Mapping of IMSIs and area codes
The table contains multiple records, with each record describing an IMSI prefix
and its corresponding area code. For example, the area code corresponding to the
IMSI prefix of 46000755 is 755. When it is necessary to know the area code of an

Feature Description

Issue 1.0 (2013-02-25)
Page 14 of 177

FTN but the FTN does not carry an area code, the HLR uses the area code in the
table as the area code of the regulated FTN.
Called number analysis
The table contains multiple records. Every record has four fields: prefix of the
FTN, attribute of the FTN, number of information station or not, and number of
entertainment station or not. There are four options for the FTN attribute: local
number, domestic toll call number, international toll call number, and PLMN
number. For example, 139 indicates PLMN number; 0 indicates domestic toll call
number; 00 indicates international toll call number; 19 indicates local number.
In the FTN regulating process, the HLR compares the prefix of an FTN with
records of the CALLEDNUM_ANALYSIS table to find a matched record, and
then regulates the FTN according to the record.
Area code
The table contains multiple records, with each record describing an area and its
corresponding area code, for example, the area code of Shenzhen city is 755.
Mapping of MSISDNs and area codes
The table contains multiple records, with each record describing an MSISDN
prefix and its corresponding area code. When analyzing a PLMN FTN, the HLR
queries the table to check whether the FTN exceeds area limitation imposed on
the call forwarding.
Country code
The table contains multiple records, with each record describing a country and its
corresponding country code. For example, the country code of China is 86. When
analyzing an FTN of international format, the HLR queries the table to verify
whether the FTN is a domestic number.
Forbidden forwarded-to number
The table contains multiple records, with each record describing a number that is
prohibited to be forwarded, for example, 110. When the HLR judges that a
number is a local number, it can query the table to verify whether the number is
allowed to serve as an FTN.
Dependency
for other NEs.
1.2.6 WHFD-030201 Barring of All Outgoing Calls (BAOC)
Availability
Specification

Feature Description

Issue 1.0 (2013-02-25)
Page 15 of 177

Summary
When the service is activated, the subscriber cannot make any call except emergency
calls.
Benefits
For carriers
The back end distributed deployment function enables carriers to provide more
services, attracting more subscribers for carriers.
For subscribers
The back end distributed deployment function allows a subscriber to bar calls in
different ways.
Description
To bar all outgoing calls from a subscriber, the HLR stores the service code and status
information of the BAOC service, and sends them to the VLR of the subscriber. The
MSC implements the barring of outgoing calls from the subscriber. The HLR supports
subscribing/withdrawing and activating/deactivating the service in the MS. The
subscriber can modify and query the status of the service. Meanwhile, the HLR can
specify whether the right of configuring the BAOC service is under the control of the
subscriber or carriers. If the right is under the control of the subscriber, the subscriber
can activate/deactivate the service through his/her MS, as long as the HLR provides
the service. Before activating/deactivating the service, the subscriber needs to input a
password. The password can be modified in either the MS or the HLR. The password
can be modified in either the MS or the HLR.
Dependency
for other NEs.
1.2.7 WHFD-030202 Barring of Outgoing International Calls
(BOIC)
Availability
Specification
Summary
When the service is activated, if the subscriber roams in the home PLMN country, the
subscriber is prohibited to make an international call.

Feature Description

Issue 1.0 (2013-02-25)
Page 16 of 177

Benefits
For carriers
The back end distributed deployment function enables carriers to provide more
services, attracting more subscribers for carriers.
For subscribers
different ways.
Description
To bar all outgoing calls from a subscriber, the HLR stores the service code and status
information of the BAOC service, and sends them to the VLR of the subscriber. The
MSC implements the barring of outgoing calls from the subscriber. The HLR supports
subscribing/withdrawing and activating/deactivating the service in the MS. The
subscriber can modify and query the status of the service. Meanwhile, the HLR can
password. The password can be modified in either the MS or the HLR.
Dependency
for other NEs.
1.2.8 WHFD-030203 Barring of Outgoing International Calls
Except Those Directed to the Home PLMN Country
(BOIC-exHC)
Availability
Specification
Summary
When the service is activated, the subscriber cannot make any international call except
calls to the home PLMN country.
Benefits
For carriers
This service expands the business scope of carriers and increases service benefits.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 17 of 177

different ways.
Description
To bar all outgoing international calls (except calls to the home PLMN country) from a
subscriber, the HLR stores the code and status information of the BOIC-exHC service,
and sends them to the VLR of the subscriber. This service is based on basic services,
including teleservices and bearer services. The MSC implements the barring of
outgoing calls from the subscriber. The HLR supports subscribing/withdrawing and
activating/deactivating the service in the MS. The subscriber can modify and query the
status of the service. Meanwhile, the HLR can specify whether the right of configuring
the BAOC service is under the control of the subscriber or carriers. If the right is under
the control of the subscriber, the subscriber can activate/deactivate the service through
his/her MS, as long as the HLR provides the service. Before activating/deactivating
the service, the subscriber needs to input a password. The password can be modified in
either the MS or the HLR.
Dependency
for other NEs.
1.2.9 WHFD-030204 Barring of All Incoming Calls (BAIC)
Availability
Specification
Summary
When the service is activated, the subscriber cannot receive any incoming call.
Benefits
For carriers
This service expands the business scope of carriers and increases service benefits.
For subscribers
different ways.
Description
The HLR activates the basic service groups and stores the code of the BAIC service,
data of the basic service groups, and the status information. When the subscriber
serves as the callee and receives a routing request from the caller, the HLR judges

Feature Description

Issue 1.0 (2013-02-25)
Page 18 of 177

whether the subscriber has activated the BAIC service. If yes, the HLR sends an error
message to the GMSC, indicating that the callee has barred all incoming calls. The
HLR supports subscribing/withdrawing and activating/deactivating the service in the
MS. The subscriber can modify and query the status of the service. Meanwhile, the
HLR can specify whether the right of configuring the BAOC service is under the
control of the subscriber or carriers. If the right is under the control of the subscriber,
the subscriber can activate/deactivate the service through his/her MS, as long as the
HLR provides the service. Before activating/deactivating the service, the subscriber
needs to input a password. The password can be modified in either the MS or the
HLR.
Dependency
for other NEs.
1.2.10 WHFD-030205 Barring of Incoming Calls when
Roaming Outside the Home PLMN Country (BIC-ROAM)
Availability
Specification
Summary
If the service is activated, when the subscriber roams outside the home PLMN country,
the subscriber cannot receive any call from other subscribers.
Benefits
For carriers
This service is based on basic service groups. It provides additional way of
barring incoming calls for carriers, and allows carriers to provide customized
services.
For subscribers
This service allows subscribers engaged in MS lease business to limit the
incoming call by controlling the call barring function.
Description
The HLR activates the basic service groups and stores the code of the BAIC service,
data of the basic service groups, and the status information. When the subscriber
serves as the callee and receives a routing request from the caller, the HLR judges
whether the subscriber has activated the BAIC service. If yes, the HLR sends an error
message to the GMSC, indicating that the callee has barred all incoming calls. The
HLR supports subscribing/withdrawing and activating/deactivating the service. The

Feature Description

Issue 1.0 (2013-02-25)
Page 19 of 177

subscriber can query the status of the service in his/her MS. Meanwhile, the HLR can
password. The password can be modified in either the MS or the HLR.
Dependency
for other NEs.
1.2.11 WHFD-030301 Calling Line Identification Presentation
(CLIP)
Availability
Specification
Summary
The CLIP service is a supplementary service for the called mobile subscriber. When
the mobile subscriber receives a call, the network presents the number of the caller to
the caller.
Benefits
For carriers
This service provides a way for carriers for attracting more subscribers.
For subscribers
This service allows a subscriber to know the calling number, and takes actions
accordingly. For example, the subscriber can decide whether to receive the
incoming call. Some subscribers are busy and do not want to receive incoming
calls; some subscribers hope to avoid calls from specified callers; some
subscribers want to call back later on; some subscribers want to distinguish
business calls from personal calls.
Description
The HLR stores the CLIP data of the subscriber. If the location of the subscriber
changes or the subscriber modifies data of the service, the HLR sends the data to the
VLR. This following describes an application scenario of the service: Subscriber B has
subscribed to the service. When subscriber B receives a call from subscriber A, the
network presents the number of subscriber A to subscriber B.

Feature Description

Issue 1.0 (2013-02-25)
Page 20 of 177

Dependency
for other NEs.
1.2.12 WHFD-030302 Calling Line Identification Restriction
(CLIR)
Availability
Specification
Summary
Calling line identification Restriction (CLIR): A supplementary service provided for
calling VoBB subscribers. When a mobile subscriber serves as the caller, the service
prohibits the network from displaying the calling number to the callee.
Benefits
For carriers
This service can protect the privacy of the subscribers, and help carriers to attract
more subscribers.
For subscribers
This service can protect the privacy of the subscriber.
Description
The HLR stores the CLIR service data for the subscriber. When subscribing the
service, the subscriber can select a restriction mode for the service:
Permanent restriction: In this mode, the service is activated for all outgoing calls.
The network does not display the calling number for the callee.
Temporary permission: In this mode, the CLIR service is activated only when the
mobile subscriber precedes the called number with #31#.
Temporary restriction: In this mode, the CLIR service is activated automatically
unless the mobile subscriber precedes the called number with *31#. If the
location of the subscriber changes or after the subscriber subscribes to the service,
the HLR sends the data to the VLR. When a mobile subscriber initiates a call, the
network decides whether to display the calling number to the callee according to
the restriction mode.
If the location of the subscriber changes or the subscriber modifies data of the service,
the HLR sends the data to the VLR. This following describes an application scenario
of the service: Subscriber A has subscribed to the CLIR service and has selected the
permanent restriction mode for the service. Subscriber B has subscribed the CLIP

Feature Description

Issue 1.0 (2013-02-25)
Page 21 of 177

service. When subscriber A calls subscriber B, the calling number is not displayed in
the MS of subscriber B.
Dependency
for other NEs.
1.2.13 WHFD-030303 Connected Line Identification
Presentation (COLP)
Availability
Specification
Summary
If a call from a mobile subscriber is forwarded, the network displays the forwarded-to
number (FTN) to the mobile subscriber.
Benefits
For carriers
This service enlarges the number identification scope and increases the business
benefit opportunities.
For subscribers
This service enables the caller to have a clear idea of the call connection status
and have more choices.
Description
VLR. The following describes an application scenario of the function: Subscriber A
initiates a call to subscriber B, and subscriber B forwards the call to subscriber C. The
network displays or does not display the number of subscriber C for subscriber A,
depending on whether subscriber A has subscribed to the COLP service.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 22 of 177

1.2.14 WHFD-030304 Connected Line Identification
Restriction (COLR)
Availability
Specification
GPP29002, 3GPP22081, 3GPP23081, and 3GPP24081
Summary
When a mobile subscriber serves as the subscriber to whom a call is forwarded, this
service prohibits the network from displaying the number of the mobile subscriber to
the caller.
Benefits
For carriers
For subscribers
This service can prevent the number of a third-party subscriber from being
displayed in the MS of the caller. It can protect the privacy of the subscriber.
Description
VLR. The following describes an application scenario of the service: Subscriber C has
subscribed to the COLR service. When subscriber A calls subscriber B, subscriber B
forwards the call to subscriber C. In this case, the number of subscriber C is not
displayed in the MS of subscriber A, even though subscriber A has subscribed to the
COLP service.
Dependency
for other NEs.
1.2.15 WHFD-030305 Override Calling Line Identification
Restriction (OVER-CLIR)
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 23 of 177

Specification
GPP29002, 3GPP22081, 3GPP23081, and 3GPP24081
Summary
The function is based on the callee, is an attribute of the CLIP service, and is intended
to override the CLIR service subscribed by the caller.
Benefits
For carriers
For subscribers
Some subscribers have strong demands for the calling number. After a subscriber
subscribes to the OVER-CLIR service, the subscriber can obtain the information
on the caller and callee, and is capable of identifying callers who initiate calls out
of malicious purpose.
Description
When the callee subscribes to the CLIP service, he/she can select whether to override
the calling number display restriction imposed by the caller. The CLIP and the CLIR
are repulsive to each other. When the callee activates the CLIP service and the caller
activates the CLIR service, since the priority of the CLIR is higher than that of the
CLIP, the network does not display the calling number for the callee. However, when
the CLIP service of the callee supports the OVERRIDECATEGORY attribute, the
priority of the CLIP is higher than that of the CLIR. In this case, the network displays
the calling number for the callee.
Dependency
for other NEs.
1.2.16 WHFD-030306 Override Connected Line Identification
Restriction (OVER-COLR)
Availability
Specification

Feature Description

Issue 1.0 (2013-02-25)
Page 24 of 177

Summary
The function is based on the caller, is an attribute of the COLP service, and is intended
to override the COLR service subscribed by the callee.
Benefits
For carriers
For subscribers
Some subscribers have strong demands for the called number. After a subscriber
subscribes to the OVER-COLR service, the subscriber can obtain the information
on the callee, and prevent call forwarding out of malicious purpose.
Description
When the caller subscribes to the COLP service, he/she can select whether to override
the called number display restriction imposed by the callee. The COLP and the COLR
are repulsive to each other. Provided that the caller activates the COLP service, and the
call to the callee is forwarded to a third-party subscriber who has activated the COLR
service. Since the priority of the COLR is higher than that of the COLP, the network
does not display the calling number for the callee. However, when the COLP service
of the caller supports the OVERRIDECATEGORY attribute, the priority of the COLP
is higher than that of the COLR. In this case, the network displays the number for the
third-party subscriber.
Dependency
for other NEs.
1.3 WHFD-040000 Operator Determined Barring
(ODB)
ODB means that the call barring is under the control of carriers. Carriers controls the
subscriber's capability of initiating and receiving calls.
The ODB is applicable to all terminal services and bearer services except the
emergency calls. Compared with other supplementary service, the ODB has higher
priority. That is, when the ODB contradicts with other supplementary services, other
supplementary services are disabled.
Similar to call restriction supplementary services, the ODB realizes call barring.
However, they have the following differences:
The status of the ODB service can only be controlled by carriers. The status of other
call restriction supplementary service can be controlled by either carriers or the
subscriber.

Feature Description

Issue 1.0 (2013-02-25)
Page 25 of 177

The ODB becomes applicable once it is provided for the subscriber. Before other call
restriction supplementary services become applicable, they must be activated by either
carriers or the subscriber's terminal.
The HLR9820 mainly provides three categories of ODB functions.
ODB Call Barring (WHFD-040100)
ODB Barring of Supplementary Services Management (WHFD-040201)
ODB Barring of Roaming (WHFD-040300)
The HLR9820 provides diversified ODB call barring services, allowing carriers to
manage the subscribers conveniently. The ODB call barring services consist of the
following:
ODB: Barring of Outgoing Calls(WHFD-040101)
ODB: Barring of Outgoing International Calls (WHFD-040102)
ODB: Barring of Outgoing Calls when Roaming Outside the Home PLMN
Country (WHFD-040104)
ODB: Barring of Domestic Toll Calls (HPLMN Self-Defined Type 1)
(WHFD-040105)
ODB: Barring of Incoming Calls (WHFD-040106)
ODB: Barring of Incoming Calls when Roaming Outside the Home PLMN
Country (WHFD-040107)
ODB: Barring of Outgoing Premium Rate Calls (Information) (WHFD-040108)
ODB: Barring of Outgoing Premium Rate Calls (Entertainment)
(WHFD-040109)
The HLR9820 supports the ODB: barring of supplementary services, including:
Barring of supplementary services management (WHFD-040201)
The HLR9820 provides Barring of Roaming, including:
ODB: Barring of Roaming Outside the Home PLMN (WHFD-040301)
ODB: Barring of Roaming Outside the Home PLMN Country (WHFD-040302)
1.3.1 WHFD-040101 ODB: Barring of Outgoing Calls
(ODB-BAOC)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service can bar all outgoing calls.

Feature Description

Issue 1.0 (2013-02-25)
Page 26 of 177

Benefits
For carriers
This service provides carriers with an additional way of controlling the
subscribers, and allows carriers to bar outgoing calls from a defaulting subscriber
and avoid loss in call charge.
For subscribers
This service allows the subscriber to select a conversation mode based on his/her
financial status, and avoids unnecessary waste in call charge.
Description
The subscription data of the service is stored in the HLR. When the location of a
subscriber is updated or the subscription data of the subscriber is modified, the HLR
sends the subscription data of the subscriber to the VLR of the subscriber. The MSC
realizes call barring.
Dependency
for other NEs.
1.3.2 WHFD-040102 ODB: Barring of Outgoing International
Calls (ODB-BOIC)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service can bar all international outgoing calls.
Benefits
For carriers
subscribers, and allows carriers to control the call scope of the subscriber and
provide call packages.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 27 of 177

Description
realizes barring of international outgoing calls from the subscriber.
Dependency
for other NEs.
1.3.3 WHFD-040103 ODB: Barring of Outgoing International
Calls Except Those Directed to the Home PLMN Country
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service can bar all outgoing international calls except those directed to the home
PLMN country.
Benefits
For carriers
For subscribers
Description
realizes barring of international outgoing calls except those directed to the home
PLMN country.

Feature Description

Issue 1.0 (2013-02-25)
Page 28 of 177

Dependency
The HLR9820 achieves the function in compliance with the standard protocol. There
is no special requirement for other NEs.
1.3.4 WHFD-040104 ODB: Barring of Outgoing Calls when
Roaming Outside the Home PLMN Country (ODB- BOCROAM)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service bars all outgoing calls from a subscriber when the subscriber roams
outside the country of the HPLMN.
Benefits
For carriers
For subscribers
Description
sends the subscription data of the subscriber to the VLR of the subscriber. When the
subscriber roams outside the home PLMN country and initiates a call, the MSC bars
the call from the subscriber.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 29 of 177

1.3.5 WHFD-040105 ODB: Barring of Domestic Toll Calls
(HPLMN Self-Defined Type 1)
Availability
Specification
3GPP29002, 3GPP220413GPP29002, and 3GPP22041
Summary
This service realizes barring of domestic toll calls (HPLMN self-defined type 1).
Benefits
For carriers
For subscribers
Description
The HLR defines four ODB services (ODBPB1, ODBPB2, ODBPB3, and ODBPB4):
ODBPB1 is for barring domestic toll calls, and other three ODB services are defined
by carriers to realize special call barring functions. The cooperation from the MSC is
necessary. The subscription data of the service is stored in the HLR. When the location
of a subscriber is updated or the subscription data of the subscriber is modified, the
HLR sends the subscription data of the subscriber to the VLR of the subscriber.
Dependency
for other NEs.
1.3.6 WHFD-040106 ODB: Barring of Incoming Calls
(ODB-BAIC)
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 30 of 177

Specification
3GPP29002 and 3GPP22041
Summary
This service realizes barring all incoming calls.
Benefits
For carriers
For subscribers
None.
Description
The subscription data of the service is stored in the HLR, but is not sent to the VLR.
The HLR realizes barring of all incoming calls to the subscriber. When the HLR
receives a routing request message from the GMSC, it judges whether the subscriber
has subscribed to the ODB-BAIC service. If yes, the HLR returns a message to the
GMSC to indicate that the calls to the subscriber are barred.
Dependency
for other NEs.
1.3.7 WHFD-040107 ODB: Barring of Incoming Calls when
Roaming Outside the Home PLMN Country
(ODB-BICROAM)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service bars all incoming calls when a subscriber roams outside the home PLMN
country.

Feature Description

Issue 1.0 (2013-02-25)
Page 31 of 177

Benefits
For carriers
For subscribers
None.
Description
The subscription data of the service is stored in the HLR, but is not sent to the VLR.
The HLR realizes barring of all incoming calls to the subscriber. When the HLR
receives the routing request message from the GMSC, it judges whether the subscriber
has subscribed to the ODB-BICROAM service. If the subscriber has subscribed to the
service, when the subscriber roams outside the country of HPLMN, the HLR returns a
message to the GMSC to indicate that incoming calls to the subscriber are barred.
Dependency
for other NEs.
1.3.8 WHFD-040108ODB: Barring of Outgoing Premium Rate
Calls (Information)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service realizes barring of outgoing premium rate calls (information).
Benefits
For carriers
For subscribers
This service helps subscribers to avoid unnecessary call charges resulting from
ignorance of the call rate of some services.

Feature Description

Issue 1.0 (2013-02-25)
Page 32 of 177

Description
realizes barring of outgoing premium rate calls (information).
Dependency
for other NEs.
1.3.9 WHFD-040109 Barring of Outgoing Premium Rate Calls
(Entertainment)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service realizes barring of outgoing premium rate calls (entertainment).
Benefits
For carriers
For subscribers
This service helps subscribers to avoid unnecessary call charges resulting from
ignorance of the call rate of some services.
Description
sends the subscription data of the subscriber to the VLR. The MSC realizes barring of
outgoing premium rate calls (entertainment).
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 33 of 177

1.3.10 WHFD-040201 ODB: Barring of Supplementary
Services Management
Availability
Specification
3GPP29002 and 3GPP22041
Summary
The HLR9820 provides supplementary services barring management, and supports
subscribing and withdrawing the service.
Benefits
For carriers
For subscribers
None.
Description
This service is subscribed and activated in the HLR. The subscription data of the
service is stored in the HLR. When the location of a subscriber is updated or the
subscription data of the subscriber is modified, the HLR sends the subscription data of
the subscriber to the VLR of the subscriber. The MSC realizes barring of
supplementary services management. The subscriber can operate the supplementary
services in many ways, for example, activate the call barring services through the MS,
and perform other USSD operations. If the subscriber has subscribed to the service, the
subscriber is unable to perform the above operations through the MS.
Dependency
for other NEs.
1.3.11 WHFD-040301 ODB: Barring of Roaming Outside the
Home PLMN
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 34 of 177

Specification
3GPP29002 and 3GPP22041
Summary
This service realizes barring of roaming outside the home PLMN.
Benefits
For carriers
This service allows carriers to control the roaming scope of the subscriber and
For subscribers
This service can avoid unnecessary loss of call charges resulting from roaming.
Description
sends the subscription data of the subscriber to the VLR of the subscriber. The HLR
realizes barring of roaming outside the home HPLMN. If the subscriber has subscribed
to the service, when the subscriber roams outside the home HPLMN, the location
updating fails.
Dependency
for other NEs.
1.3.12 WHFD-040302 ODB: Barring of Roaming Outside the
Home PLMN Country (ODB- BROHPLMNC)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service realizes barring of roaming outside the home PLMN country.
Benefits
For carriers

Feature Description

Issue 1.0 (2013-02-25)
Page 35 of 177

This service allows carriers to control the roaming scope of the subscriber and
For subscribers
This service can avoid unnecessary loss of call charges resulting from roaming.
Description
realizes barring of roaming outside the home HPLMN country. If the subscriber has
subscribed to the service, when the subscriber roams outside the home HPLMN
country, the location updating fails.
Dependency
for other NEs.
1.3.13 WHFD-040400 ODB: Barring of Registration of
Forwarded-to Number (ODBRCF)
Availability
Specification
3GPP29002 and 3GPP22041
Summary
This service can restrict a subscriber's right of registering the FTNs. It can bar the
registration of All FTNs, International FTNs, and International FTNs except those
destined to the home HPLMN country.
Benefits
For carriers
This service allows carriers to control the registration of FTNs and provide call
packages.
For subscribers
This service can prevent FTN registration due to mistaken operations.
Description

Feature Description

Issue 1.0 (2013-02-25)
Page 36 of 177

realizes barring of registration of FTNs. If the subscriber has subscribed to the service,
when the subscriber registers an FTN through the terminal, the registration fails.
Enhancement
This service complies with standard protocols. The HLR sends data of the service to
the VLR. The MSC realizes the function. Meanwhile, the HLR can also restrict the
registration of FTNs. For example, the HLR can control whether a subscriber can
forward calls to the same area, whether the subscriber can forward international calls,
and whether the registered FTNs can carry country code. The HLR can realize these
functions through configuration of data or subscription of the related template. This
service allows carriers to provide different forwarding policies for different subscriber
groups.
Dependency
for other NEs.
1.3.14 WHFD-040500 ODB: Barring of Call Transfer
(ODBECT)
Availability
Specification
3GPP22041 and 3GPP29002
Summary
This service can restrict a subscriber's call transfer rights.
Benefits
For carriers
This service allows carriers to control the call transfer and provide various call
packages.
For subscribers
None.
Description
sends the subscription data of the subscriber to the VLR. The MSC realizes barring of
call transfer on one of the following occasions:
Barring all explicit call transfers

Feature Description

Issue 1.0 (2013-02-25)
Page 37 of 177

Barring explicit call transfer when the served subscriber pays for either or both of
the incoming and outgoing calls
Barring explicit call transfer when the served subscriber roaming abroad pays for
either or both of the incoming and outgoing calls
Barring of explicit call transfer when the served subscriber roaming in another
zone pays for either or both of the incoming and outgoing calls
Barring of explicit call transfer when the served subscriber pays for both of the
incoming and outgoing calls
Barring explicit call transfer when in the same MSC/VLR, there is an ongoing
transferred call for the served subscriber and at the same time, another subscriber
originates a call to this subscriber
Dependency
for other NEs.
1.4 WHFD-050000 Other Services
Other services include:
Liable Subscriber Suspension by Lock (WHFD-050100)
Subscriber Applied Suspension (WHFD-050200)
Subscriber Category Setting (Subscriber Category) (WHFD-050300)
Multi-NDC (WHFD-571600)
1.4.1 WHFD-050100 Liable Subscriber Suspension by Lock
Availability
Specification
None.
Summary
This service allows carriers to suspend the service of the subscriber (by lock) flexibly.
Benefits
For carriers
Carriers can suspend the telephone service, short message service, and GPRS
service of a subscriber to avoid loss of call charges and defaulting of the
subscriber.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 38 of 177

The timely suspension of services by carriers can prevent the call charge of the
subscriber from exceeding the limit.
Description
This service provides locking operation, allowing carriers to suspend the service of the
defaulting subscriber and avoid loss of call charges.
When carriers performs locking operations for the subscriber, it can control separately:
Whether to allow the subscriber to receive incoming calls.
Whether to allow the subscriber to make outgoing calls.
Whether to allow the subscriber to use the GPRS service.
Through the above control mechanisms, carriers can restrict the subscriber's services
flexibly.
Enhancement
The HLR provides two types of locks for suspending services of the defaulting
subscribers: lock for the MSC domain and lock for the PS domain. Select the desired
lock according to the network access mode (NAM) of the subscriber. If the NAM of
the subscriber is MSC and SGSN, after the subscriber's line is locked, the subscriber
can only register service in the CS domain and is unable to initiate/receive a call and
perform USSD/GPRS operations. If the NAM of the subscriber is SGSN, after the
subscriber's line is locked, the subscriber is unable to access the PS domain.
Dependency
for other NEs.
1.4.2 WHFD-050200 Subscriber Applied Suspension
Availability
Specification
None.
Summary
This service allows a subscriber to apply for service suspension.
Benefits
For carriers
Carriers can provide the lock function for the subscriber.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 39 of 177

The subscriber can use the service to reduce unnecessary call charges.
Description
The HLR provides call barring service, allowing the subscriber to apply for service
suspension. When applying for service suspension, the subscriber must go to the
business hall to finish the related formalities. When applying for canceling the service
suspension, the subscriber must go to the business hall to finish the related formalities.
Enhancement
In the HLR, the Liable Subscriber Suspension by Lock service differs from the
Subscriber Applied Suspension service in that:
Different targets: The former targets at carriers, and the later targets at the
subscriber.
Different functioning principles: The former is realized through the ODB service;
the later is realized through the call baring mechanism of the supplementary
services.
Dependency
for other NEs.
1.4.3 WHFD-050300 Subscriber Category Setting
Availability
Specification
3GPP29002, 3GPP23008
Summary
This service is for defining subscriber category. Every subscriber is allocated with a
subscriber category.
Benefits
For carriers
This service allows carriers to configure various subscriber categories and divide
the subscribers into different groups.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 40 of 177

Description
Every IMSI is allocated with a subscriber category. The HLR supports configuring and
managing subscriber categories. The subscriber categories supported by the HLR
include UNKNOWN, FRENCH, ENGLISH, GERMAN, RUSSIAN, SPANISH,
SPECIAL, RESERVE, COMMON, SUPERIOR, DATACALL, TESTCALL, SPARE,
PAYPHONE, and COIN. In the location update flow, the HLR sends the data of
subscriber categories to the VLR so that the VLR can handle the calls and call charges
according to the subscriber categories.
Dependency
for other NEs.
1.4.4 WHFD-571600 Multi-NDC
Availability
Specification
None.
Summary
The multi-NDC service enables a network to have multiple network numbers.
Benefits
For carriers
This service allows carriers to perform network planning and data configuration
conveniently.
For subscribers
None.
Description
When a subscriber initiates a call to a subscriber in the public land digital cellular
mobile network, the subscriber needs to dial the MSISDN of the callee. The MSISDN
consists of CC-NDC-SN. National Destination Code (NDC) is a part of the MSISDN,
is also called network number, and is used to distinguish carriers to which the
subscriber numbers belong. The length of the NDC ranges from 1 to 3. An HLR
supports multiple NDCs and provides equal services for subscribers with different
NDCs.

Feature Description

Issue 1.0 (2013-02-25)
Page 41 of 177

Dependency
for other NEs.
1.5 WHFD-060000 Mobility Services
The HLR provides standard protocol-compliant mobility services, including: Location
management services (WHFD-060100) Authentication management services
(WHFD-060200) Subscriber management services (WHFD-060300) Fault recovery
services (WHFD-060400)
The HLR9820 provides standard protocol-compliant location management services,
including:
Location Update (WHFD-060101)
Location Cancellation (WHFD-060102)
MS Purge (WHFD-060103)
The authentication is an important function in the mobile communication system. It is
intended to prevent illegal MSs from enjoying the wireless communication through
unlawful means. During the authentication process, the MS and the network perform
calculations using the same algorithm based on the shared parameters (generally
provided by the network) and their respective keys. If the calculation results are the
same, that is, they hold the same key, it means that the MS passes the authentication
successfully.
The HLR9820 provides standard protocol-compliant authentication management
services, including:
Authentication Information Provision
Authentication Failure Report
The HLR9820 provides standard protocol-compliant subscriber management services,
including:
Subscriber Data Insertion (WHFD-060301)
Subscriber Data Deletion (WHFD-060302)
The HLR9820 provides standard protocol-compliant fault recovery services,
including:
HLR Fault Recovery (Reset) (WHFD-060401)
VLR Fault Recovery (Restore) (WHFD-060402)
Check SS Indication (Check SS indication) (WHFD-060403)
1.5.1 WHFD-060101 Location Update
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 42 of 177

Specification
3GPP29002
Summary
The location update service is a flow initiated by the subscriber's terminal for
maintaining subscriber data consistency between the VLR and the HLR.
Benefits
For carriers
This service provides a basic network function.
For subscribers
None.
Description
The subscription data, location information, and status information of the subscriber
are stored in the HLR. In this flow, the HLR sends all subscription data of the
subscriber to the VLR.
Enhancement
Location update is the major process of the location management, and is triggered by
the MS. In the GSM system, the HLR, VLR, and MS (or the SIM card) must know the
location information of the subscriber. When the location information changes, it is
necessary to maintain consistency among the HLR, VLR, and the MS.
When the MS finds a location area that can provide better service, it notifies the
MSC/VLR of the new location area (generally, the MSC and the VLR are integrated
into a function entity). If the original location area and the new location area belong to
the same MSC/VLR, modify the location area information of the MS in the VLR; if
they belong to different MSC/VLR, the new MSC/VLR must send a message to the
HLR for obtaining the data of the MS. The HLR sends the information to the new
MSC/VLR, and notifies the original MSC/VLR to delete the registration data of the
MS, and registers the MS in the new MSC/VLR. Meanwhile, the HLR also updates
the MSC/VLR number of the MS.
By checking whether the new MSC/VLR contains the records of the MS, the network
can tell whether the new location area and the original location area belong to the same
MSC/VLR. But the network must know the IMSI number of the MS. The IMSI
number can be obtained from the original VLR(PVLR) of the MS or the MS.
The following lists the several situations of location update:
Normal location update. It triggers location update flow.
Periodic location update
IMSI attached/detached
The VLR receives the service operation instruction from the MS when the flag bit
of the VLR indicates fault. It triggers location update flow.

Feature Description

Issue 1.0 (2013-02-25)
Page 43 of 177

Dependency
for other NEs.
1.5.2 WHFD-060102 Location Cancellation
Availability
Specification
3GPP29002
Summary
This service enables the HLR to initiate a flow to clear the subscriber data in the VLR.
Benefits
For carriers
This service provides a basic network function.
For subscribers
None.
Description
To ensure that the subscriber data in the network is always unique and the
most-up-to-date, when a subscriber roams from one VLR to another VLR, the HLR
sends a location cancellation request to the original VLR to instruct the original VLR
to clear the subscriber data. When a subscriber is deregistered or adopts a new SIM
card, the HLR initiates the location cancellation flow to the VLR of the subscriber.
Dependency
for other NEs.
1.5.3 WHFD-060103 MS Purge
Availability
Specification
3GPP29002

Feature Description

Issue 1.0 (2013-02-25)
Page 44 of 177

Summary
If a subscriber is offline for a long time, the VLR sends a notice to the HLR through
the Purge MS service. The HLR then labels the status of the subscriber as being
unreachable for a long time.
Benefits
For carriers
This service can reduce traffic volume.
For subscribers
None.
Description
When a subscriber remains offline for a certain period (controlled by the VLR), the
VLR triggers the Purge MS flow by sending a message to the HLR. After receiving the
message, the HLR sets the Purge flag bit of the subscriber to indicate that the
subscriber is unreachable currently.
Enhancement
In some flows, the HLR needs to know the current status of a subscriber. The HLR can
obtain the subscriber's status from the VLR by triggering a flow (such as the
Provide_Subscriber_Info). The VLR can also trigger a flow to notify the HLR of the
change of the subscriber's status. The Purge MS flow is triggered by the VLR, and is
intended to notify the HLR of the subscriber's being offline for a long time. After
receiving the purge flow request from the VLR, the HLR records the subscriber's
status. When other flow needs to check the subscriber's status, the HLR does not have
to query the subscriber's status from the VLR, thus reducing the process time and
unnecessary network traffics.
Dependency
for other NEs.
1.5.4 WHFD-060201 Authentication Information Provision
Availability
Specification
3GPP29002

Feature Description

Issue 1.0 (2013-02-25)
Page 45 of 177

Summary
This service enables the VLR to initiate a flow to obtain the subscriber authentication
set.
Benefits
For carriers
This service can prevent illegal MS from enjoying telecommunication services
and protect the interests of carriers.
For subscribers
This service can prevent the theft of the subscriber number. The 3G system
supports the authentication of the network, reducing the chance of network
fraudulence against the subscriber.
Description
The HLR9820 supports authentication of 2G subscribers and 3G subscribers, and
supports authentication triplet for 2G subscribers and authentication quintuple for 3G
subscribers. The HLR provides the following authentication algorithms:
Authentication algorithms for subscribers holding SIM cards: XOR, COMP128_1,
COMP128_2, COMP128_3, and MILENAGE
Authentication algorithm for subscribers holding USIM cards: MILENAGE
Meanwhile, the HLR adopts active and standby subscriber authentication data reuse
counters. The maximum reuse counter allowed for every authentication set (five
authentication triplets) is 3. If the active reuse counter is not 0, the HLR sends a MAP
message to the VLR as a response to its authentication request through the
authentication set of the active reuse counter, and reduces the active reuse counter by 1.
If the reuse counter is 0 and the standby reuse counter is not 0, the HLR sends a MAP
message to the VLR as a response to its authentication request through the
authentication set of the standby reuse counter, and reduces the standby reuse counter
by 1. If the two counters are 0, the HLR calculates the authentication through the
function of the Authentication Center (AuC), adjusts the reuse counter to the
maximum, and then returns a message to the VLR as the response to its authentication
request.
Enhancement
The HLR9820 supports both 2G authentication and 3G authentication. In the case of
2G authentication, the HLR returns authentication triplets (SRES, KC, and RAND); in
the case of 3G authentication, the HLR returns authentication quintuples (MAC,
XRES, CK, IK, and AK). Meanwhile, the 3G authentication allows the terminal to
initiate the authentication to the network. The following introduces the 2G
authentication and 3G authentication respectively:
In the 2G GSM system, the authentication flow is as follows:
1. The VLR/SGSN receives the registration request from the MS, sends the IMSI of
the subscriber to the HLR/AuC of the MS, and requests them to authenticate the
subscriber

Feature Description

Issue 1.0 (2013-02-25)
Page 46 of 177

2. The HLR/AuC receives the authentication request from the VLR/SGSN,
generates the RAND, calculates the authentication vector (SRES, KC, and
RAND), and sends it to the VLR/SGSN.
3. The MSC/VLR sends an authentication command (containing the RAND) to the
MS. The MS calculates the SRESms based on the RAND and its own KI, and
sends a message with the SRESms as the response to the authentication request to
the MSC/VLR. If SRESms is equal to SRESauc, the subscriber is considered as a
legal subscriber and passes the authentication. Otherwise, the subscriber fails to
pass the authentication, and is refused to access the network.
In the 3G GSM system, the authentication flow is as follows:
1. The VLR/SGSN receives the registration request from the MS, sends the IMSI of
the subscriber to the HLR/AuC of the MS, and requests them to authenticate the
subscriber
2. The HLR/AuC receives the authentication request from the VLR/SGSN,
generates the SQN and RAND, calculates the authentication vectors (MAC,
XRES, CK, IK, and AK), and sends them to the VLR/SGSN.
Among the authentication vectors generated by the HLR/AuC, the MAC is used
to enable the MS to verify the legality of the network; the XRES is used to enable
the network to verify the legality of the MS; the CK and the IK are used to
encrypt the air interface and verify the integrity of the authentication data; the AK
is used to encrypt the SQN.
The role of the SQN is to ensure the freshness of the authentication vector
between the MS and the VLR/SGSN. The authentication before every
communication adopts different authentication vector to ensure that the CK and
IK adopted in every communication event are calculated based on different
RAND. The MAC used in every authentication uses the incremental SQN as one
of its input variables to ensure the freshness of the key and prevent attacks. The
AMF participates in the calculation of authentication vector as a parameter. Every
vendor adopts a default value for it. The AMF of Huawei's HLR is set to 0x762C.
3. The VLR/SGSN receives the authentication vectors, sends RAND||AUTN to the
MS, and requests the MS to generate authentication data and verify SQN.
4. The MS receives the authentication request. It calculates the XMAC, and then
compares the XMAC with the MAC of the AUTN. If they are different, it sends a
refuse authentication message to the VLR, and gives up the authentication
process.
5. The MS verifies whether the received SQN falls within the valid range. If not, the
MS sends a synchronization failure message to the VLR, and gives up the
authentication process.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 47 of 177

1.5.5 WHFD-060202 Authentication Failure Report
Availability
Specification
3GPP29002
Summary
This service enables the VLR to initiate the flow of notifying the HLR of subscriber
authentication failure.
Benefits
For carriers
This service allows carriers to identify and collect statistics on authentication
failure events.
For subscribers
None.
Description
The HLR supports reporting authentication failure events. When the authentication set
is sent to the VLR and the subscriber authentication in the VLR fails, the VLR sends
the authentication failure report to the HLR. The authentication failure report carries
the cause value of authentication failure, including subscriber response error and
network signature error. Upon receipt of the message, the HLR returns a response.
Dependency
for other NEs.
1.5.6 WHFD-060301 Subscriber Data Insertion
Availability
Specification
3GPP29002

Feature Description

Issue 1.0 (2013-02-25)
Page 48 of 177

Summary
When the subscriber data in the HLR is modified, the HLR sends the modified
subscriber data to the VLR to ensure the subscriber data consistency between the HLR
and the VLR.
Benefits
For carriers
This service can ensure the subscriber data consistency between the VLR and the
HLR, and maintain the service availability.
For subscribers
None.
Description
The HLR9820 supports inserting subscriber data in the following flows:
In the location update flow, the HLR sends the subscription data of the subscriber
to the VLR.
When the subscription data is modified by the subscriber, the HLR sends the
modified subscription data to the VLR.
When the VLR initiates the data recovery flow request, the HLR reinserts the
data of the subscriber to ensure the subscriber data consistency between the VLR
and the HLR.
Enhancement
In the data insertion flow, the HLR9820 supports sending replacement data if the VLR
does not support the original data. When the VLR does not support the service data
sent by the HLR, the HLR sends the replacement data according to the related
configuration. For example, when the HLR sends ODB-BAOC, the VLR returns a
response to indicate that it does not support the data. In this case, the HLR rejects the
configuration data or sends supplementary service BAOC, depending on the related
configuration data.
Dependency
for other NEs.
1.5.7 WHFD-060302 Subscriber Data Deletion
Availability
Specification
3GPP29002

Feature Description

Issue 1.0 (2013-02-25)
Page 49 of 177

Summary
When the data of a subscriber in the HLR is deleted, the HLR sends a request of
deleting subscriber data to the VLR to maintain subscriber data consistency between
the HLR and the VLR.
Benefits
For carriers
This service can ensure the subscriber data consistency between the VLR and the
HLR, and maintain the service availability.
For subscribers
None.
Description
When a subscriber cancels the subscription of a service, the HLR triggers the
subscriber data deletion flow and requests the VLR to delete the related data.
Dependency
for other NEs.
1.5.8 WHFD-060401 HLR Fault Recovery
Availability
Specification
3GPP29002
Summary
When the HLR is faulty, it initiates the Reset flow to the VLR. The VLR initiates the
location update flow as instructed by the VLR, and regains the subscriber data to
ensure the subscriber data consistency between the VLR and the HLR.
Benefits
For carriers
This service has enhanced the network fault recovery capability and ensured the
network data consistency.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 50 of 177

Description
The HLR9820 supports the standard fault recovery flow, namely the Reset flow. When
the HLR is restarted due to faults, the subscriber data in the HLR may be inconsistent
with that in the VLR. In this case, the HLR initiates the Reset flow to instruct the VLR
to initiate the location update flow so that the VLR can regain the subscriber data from
the HLR and maintain the subscriber data consistency between the HLR and VLR. For
the VLR, the Reset flow is of system level. The VLR supports obtaining data from the
HLR to update all subscriber data. The HLR supports initiating the Reset flow
automatically and manually. In the subscriber data cutover, it is required to initiate the
Reset flow manually.
Dependency
for other NEs.
1.5.9 WHFD-060402 VLR Fault Recovery
Availability
Specification
3GPP29002
Summary
When the VLR is faulty and initiates the data recovery flow, the HLR9820 supports
resending subscriber data to the VLR.
Benefits
For carriers
This service has enhanced the network fault recovery capability and ensured the
network data consistency.
For subscribers
None.
Description
When receiving the Restore request from the VLR, the HLR9820 supports resending
subscriber data to the VLR to ensure the subscriber data consistency between the VLR
and HLR. When the data of a subscriber in the VLR is labeled as untrustworthy or the
VLR receives a request from the HLR for obtaining the roaming number of an
unknown subscriber, the VLR initiates the data restore flow. For the VLR, the data
restore flow is of user level. The VLR supports initiating the data restore flow for a
subscriber.

Feature Description

Issue 1.0 (2013-02-25)
Page 51 of 177

Dependency
for other NEs.
1.5.10 WHFD-060403 Check SS Indication
Availability
Specification
3GPP29002
Summary
The HLR9820 supports the flow of notifying the subscriber of the changes to his/her
supplementary services. This service is mainly intended to notify the subscriber of the
possible changes to data of a supplementary service.
Benefits
For carriers
user (ARPU).
For subscribers
Description
The flow is mainly intended to notify the subscriber of the possible changes to a
supplementary service. For example, after the HLR is restarted, if the VLR receives
the MAP_FORWARD_CHECK_SS_INDICATION message from the HLR, the VLR
forwards the message to the MSC, and the MSC notifies the terminal. After the HLR
restarts, if the subscriber updates his/her location, the flow is incorporated into the
location update flow. The flow is unidirectional.
Dependency
for other NEs.
1.6 WHFD-070000 Call Handling Services
The call processing service is the basic service of the mobile network. When a
subscriber initiates a call to another subscriber, the MSC of the caller must know the

Feature Description

Issue 1.0 (2013-02-25)
Page 52 of 177

location of the callee, that is, the routing information of the callee. In the mobile
network, the routing information is provided in the form of roaming number. The
roaming number provides the location information necessary to the setup of call
connection between the MSC of the caller and that of the callee. The HLR is necessary
to the process of obtaining the roaming number. First, the GMSC initiates the request
for obtaining the routing information to the HLR. Upon receiving the request, the HLR
sends a request for obtaining the roaming number to the MSC of the callee. The MSC
of the callee sends a response message with the roaming number to the HLR, and the
HLR then sends a response message with the roaming number to the GMSC. The
following shows the basic flow:

The HLR9820 provides standard protocol-compliant call processing services,
including:
Send Routing Information (WHFD-070100)
Provide Roaming Number (WHFD-070200)
1.6.1 WHFD-070100 Send Routing Information
Availability
Specification
3GPP29002
Summary
When receiving a request for obtaining routing information, the HLR carries the
routing information in the response message.

Feature Description

Issue 1.0 (2013-02-25)
Page 53 of 177

Benefits
For carriers
This service realizes a basic network function.
For subscribers
None.
Description
The GMSC initiates the flow of obtaining the routing information. It sends a request
for obtaining the roaming number of the callee to the HLR. When receiving the
message for obtaining the routing information, the HLR checks the services of the
subscriber, for example, whether the subscriber has subscribed to the call barring
service and the call forwarding service. Next, the HLR decides whether to continue to
obtain the roaming number, or return a message with error codes or FTN to the
GMSC.
If the HLR intends to return a message with error codes, the message contains
such information as unknown subscriber, call barring, forwarding restriction, and
absent subscriber.
If the subscriber has subscribed to the unconditional call forwarding service, the
subscriber returns the message with the FTN.
If the HLR intends to obtain the roaming number, the HLR initiates the flow of
obtaining the roaming number from the MSC of the callee. After obtaining the
roaming number, the HLR sends a response message with the roaming number to
the MSC of the caller.
Enhancement
The HLR9820 supports processing a call flow according to the bearer capability of the
call flow. When receiving a request with the ISDN-BC (bearer capability), the HLR
first converts ISDN-BC into the GSM-BC, and then translates it into basic service
code. If the subscriber has subscribed to the basic service, the HLR sends a request to
the VLR for obtaining the roaming number. When the HLR receives a request without
the ISDN-BC, the HLR initiates a request for obtaining the roaming number according
to the default basic service of the subscriber. Meanwhile, the HLR supports multiple
MSISDNs. When the caller initiates a call to the assisting MSISDN of the callee, the
HLR converts the assisting MSISDN into basic service code, and sends a request to
the VLR for obtaining the roaming number.
Dependency
for other NEs.
1.6.2 WHFD-070200 Provide Roaming Number
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 54 of 177

Specification
3GPP29002
Summary
The HLR9820 supports sending a request for obtaining the roaming number to the
VLR of the callee. When receiving the roaming number, the HLR sends a response
message with the roaming number to the GMSC.
Benefits
For carriers
This service realizes a basic network function.
For subscribers
None.
Description
When receiving the request for obtaining the roaming number from the GMSC, the
HLR initiates the flow of obtaining the roaming number from the VLR of the callee
according to the current processing results. The MSC of the callee carries the roaming
number in its response message to the HLR. The HLR then sends a response message
with the roaming number to the GMSC.
Dependency
for other NEs.
1.7 WHFD-080000 SS-Specific Services
The HLR9820 provides standard protocol-compliant SS-related services, including:
SS Registration (RegisterSS) (WHFD-080100)
SS Deletion (Erase SS) (WHFD-080200)
SS Activation (Activate SS) (WHFD-080300)
SS Deactivation (Deactivate SS) (WHFD-080400)
SS Query (Interrogate SS) (WHFD-080500)
SS Password Registration (Register password) (WHFD-080600)
SS Password Provision (Get password) (WHFD-080700)
1.7.1 WHFD-080100 SS Registration
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 55 of 177

Specification
3GPP29002
Summary
The HLR9820 enables the subscriber to initiate the registration of a supplementary
service from the terminal.
Benefits
For carriers
This service enables carriers to provide a subscriber-oriented service flow.
For subscribers
This service enables the subscriber to register supplementary services through the
terminal without going to the business hall.
Description
The HLR9820 enables the subscriber to register a supplementary service related to call
forwarding from the terminal. Before the subscriber can register a supplementary
service related to call forwarding from the terminal, carriers must provide the SS
Registration service in its business hall. The registration of call forwarding
supplementary services can be based on basic service groups. For example, the HLR
supports forwarding both a voice call and a data call. When initiating the registration
of call forwarding services, the subscriber needs to provide the corresponding FTNs.
Upon receiving the request of registering the FTNs, the HLR stores these FTNs, and
activates the services for the subscriber. The HLR then sends the subscriber's call
forwarding service data to the VLR.
Dependency
for other NEs.
1.7.2 WHFD-080200 SS Deletion
Availability
Specification
3GPP29002
Summary
The HLR9820 enables the subscriber to deregister a supplementary service from the
terminal.

Feature Description

Issue 1.0 (2013-02-25)
Page 56 of 177

Benefits
For carriers
For subscribers
This service enables the subscriber to deregister supplementary services through
the terminal without going to the business hall.
Description
The HLR9820 enables the subscriber to deregister a supplementary service related to
call forwarding from the terminal. Deregistration of a call forwarding supplementary
service can be based on basic service groups. For example, the HLR9820 supports
forwarding both a voice call and a data call. Upon receiving the request of
deregistering the call forwarding service, the HLR deletes these FTNs, and deactivates
the service for the subscriber. The HLR then sends the subscriber's call forwarding
service data to the VLR.
Dependency
for other NEs.
1.7.3 WHFD-080300 SS Activation
Availability
Specification
3GPP29002
Summary
The HLR9820 enables the subscriber to activate a supplementary service from the
terminal.
Benefits
For carriers
For subscribers
This service enables the subscriber to activate a supplementary service through

Feature Description

Issue 1.0 (2013-02-25)
Page 57 of 177

Description
The HLR9820 enables the subscriber to activate a call barring supplementary service
from the terminal. Before the subscriber can activate a call barring related
supplementary service from the terminal, carriers must provide the SS Activation
service in the business hall. The activation of call barring related supplementary
barring both a voice call and a data call. After receiving a request from the subscriber,
the HLR activates the call barring service of the subscriber, and then resends the
subscriber's call barring service data to the VLR.
Dependency
for other NEs.
1.7.4 WHFD-080400 SS Deactivation
Availability
Specification
3GPP29002
Summary
The HLR9820 enables the subscriber to deactivate supplementary services from the
terminal.
Benefits
For carriers
For subscribers
This service enables the subscriber to deactivate a supplementary service through
Description
The HLR9820 enables the subscriber to deactivate a call barring supplementary
service from the terminal. The deactivation of a call barring related supplementary
barring both a voice call and a data call. After receiving a request from the subscriber,
the HLR deactivates the call barring service of the subscriber, and then resends the
subscriber's call barring service data to the VLR.

Feature Description

Issue 1.0 (2013-02-25)
Page 58 of 177

Dependency
for other NEs.
1.7.5 WHFD-080500 SS Query
Availability
Specification
3GPP29002
Summary
The HLR9820 enables the subscriber to query the status of a supplementary service
from the terminal.
Benefits
For carriers
For subscribers
This service enables the subscriber to query the status of a supplementary service
from the terminal.
Description
The HLR9820 enables the subscriber to query the status of a supplementary service
from the terminal. For example, the subscriber can query whether a call forwarding
supplementary service or call barring supplementary service has been activated. When
receiving a query request, the HLR sends a message with information on the status of
the service to the MSC. The query result is displayed in the subscriber's terminal.
Dependency
for other NEs.
1.7.6 WHFD-080600 SS Password Registration
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 59 of 177

Specification
3GPP29002 and 3GPP22004
Summary
When a subscriber activates the supplementary service from the terminal, he/she needs
to input the password of the supplementary service. The HLR9820 enables the
subscriber to configure and modify the password of the supplementary service from
the terminal.
Benefits
For carriers
This service enables carriers to provide a service security protection mechanism
for the subscriber.
For subscribers
This service can guarantee the security of the subscriber's service.
Description
The HLR9820 enables the subscriber to configure and modify the password of a
supplementary service from the terminal. When configuring the password of a
supplementary service, the network requests the subscriber to input the initial
password. After the initial password is confirmed, the network requests the subscriber
to input a new password, and then confirm it. At the time of subscription, the default
password is 0000. When a subscriber activates a call barring supplementary service
from the terminal, the subscriber needs to input the password of the supplementary
service.
Dependency
for other NEs.
1.7.7 WHFD-080700 SS Password Provision
Availability
Specification
3GPP29002 and 3GPP22004
Summary
When a subscriber operates a supplementary service from the terminal, the HLR
requires the subscriber to input the password of the supplementary service to
authenticate the legality of the subscriber.

Feature Description

Issue 1.0 (2013-02-25)
Page 60 of 177

Benefits
For carriers
This service enables carriers to provide a service security protection mechanism
for the subscriber.
For subscribers
This service can guarantee the security of the subscriber's service.
Description
When a subscriber activates a supplementary service or modifies the password of a
supplementary service from the terminal, the HLR requires the subscriber to input the
password of the supplementary service. After obtaining the original password, the
HLR requires the subscriber to input and verify the new password. When a subscriber
modifies the password of a supplementary service or changes the status of a call
barring supplementary service, the flow between the HLR and the MSC requires the
subscriber to input the password of the supplementary service so as to authenticate the
legality of the subscriber.
Dependency
for other NEs.
1.8 WHFD-090000 Subscriber Data Management
The HLR9820 provides subscriber data management functions, including Subscriber
Definition, Subscriber Deletion, and IMSI Change, and so on. The following describes
these functions:
The HLR9820 supports the following basic subscriber data management (090100)
functions:
Subscriber Definition (090901)
Subscriber Deletion (090902)
IMSI Change (090903)
MSISDN Change (090904)
Subscriber Number Query (090905)
Basic Service Setting and Query (090906)
Dynamic Data Query (090907)
The HLR9820 supports the following dynamic subscriber data management (090300)
functions:
Subscriber Location Modification (WHFD-090301). This function allows you to
modify VLR number, MSC number, and SGSN number.
Unsupported Service Replacement (WHFD-090301). The HLR uses other
supplementary services to replace services that are not supported by some
network entities, including ODB, AoCC, and CUG.

Feature Description

Issue 1.0 (2013-02-25)
Page 61 of 177

1.8.1 WHFD-090101 Subscriber Definition
Availability
Specification
None.
Summary
The HLR9820 supports defining a single subscriber and a template subscriber.
Benefits
For carriers
This service enables carriers to provide more convenient subscriber definition
modes.
For subscribers
None.
Description
The HLR9820 supports subscriber definition with or without a template. It provides a
maximum of 255 templates. In either of the two definition modes, the parameters
related to various services, such as call forwarding service, call barring service, and
General Packet Radio Service (GPRS), are provided.
Dependency
for other NEs.
1.8.2 WHFD-090102 Subscriber Deletion
Availability
Specification
None.
Summary
The HLR9820 supports deleting a subscriber.

Feature Description

Issue 1.0 (2013-02-25)
Page 62 of 177

Benefits
For carriers
This service enables carriers to provide a basic subscriber deletion function.
For subscribers
None.
Description
The HLR9820 supports subscriber deletion. It can delete only the service subscription
data or all the data of a subscriber, including the KI data. It also supports batch
operation of subscriber deletion.
Dependency
for other NEs.
1.8.3 WHFD-090103 IMSI Change
Availability
Specification
None.
Summary
The HLR9820 enables a subscriber to change his/her SIM card while keeping the
MSISDN number unchanged.
Benefits
For carriers
This service enables carriers to reduce the waste in subscriber number resources,
maintains the stability of the subscribers as a whole, and cultivates the loyalty of
the subscriber.
For subscribers
When a subscriber's SIM card is lost or damaged, the subscriber can change
his/her SIM card while keeping the MSISDN number and the subscription data
unchanged.
Description
The HLR9820 supports the IMSI Change service, allowing a subscriber to change
his/her SIM card while keeping the MSISDN number and other subscription data
unchanged.

Feature Description

Issue 1.0 (2013-02-25)
Page 63 of 177

Dependency
for other NEs.
1.8.4 WHFD-090104 MSISDN Change
Availability
Specification
None.
Summary
The HLR9820 enables a subscriber to change his/her MSISDN number without
changing the SIM card.
Benefits
For carriers
This service enables carriers to maintain the stability of its subscribers.
For subscribers
Sometimes, a subscriber intends to change his/her MSISDN number out of
privacy reason or other security considerations. This service can well satisfy this
requirement of the subscriber.
Description
The HLR9820 supports the MSISDN Change service, allowing a subscriber to change
his/her MSISDN number while keeping the subscription data unchanged.
Dependency
for other NEs.
1.8.5 WHFD-090105 Subscriber Number Query
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 64 of 177

Summary
The HLR9820 supports querying the MSISDN number of a subscriber.
Benefits
For carriers
This service enhances the subscriber maintenance capability.
For subscribers
None.
Description
The HLR9820 supports querying the MSISDN number of a subscriber. By inputting
the subscriber's IMSI or the MSISDN (the subscriber has subscribed to multiple
MSISDN numbers), you can query the subscriber's MSISDN number or the
subscriber's other MSISDN numbers.
Dependency
for other NEs.
1.8.6 WHFD-090106 Basic Service Setting and Query
Availability
Specification
None.
Summary
The HLR9820 supports configuring and querying a basic service.
Benefits
For carriers
For subscribers
None.
Description
The HLR9820 supports configuring and querying a basic service, including
Teleservices and bearer service (such as voice service and data service).

Feature Description

Issue 1.0 (2013-02-25)
Page 65 of 177

Dependency
for other NEs.
1.8.7 WHFD-090107 Dynamic Data Query
Availability
Specification
None.
Summary
The HLR9820 supports querying a subscriber's dynamic information.
Benefits
For carriers
For subscribers
None.
Description
The HLR9820 supports querying the dynamic data of a subscriber, including:
The subscriber's roaming status in the CS domain or the PS domain
Number of the MSC/VLR of the subscriber
Domestic roaming or international roaming
CAMEL supporting capability of the MSC/VLR of the subscriber
Number and address of the SGSN of the subscriber
CAMEL supporting capability of the SGSN
Information on the short message center
Supported ODB attributes
Unsupported Service Replacement
Location Service (LCS)
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 66 of 177

1.8.8 WHFD-090200 Operator Authority Management
Availability
Specification
None.
Summary
The HLR9820 supports right/level based subscriber data management.
Benefits
For carriers
For subscribers
None.
Description
The HLR defines various roles, allocates different rights to different roles, and
allocates different roles to different operators to realize level-based operator
management. Meanwhile, the rights can be managed based on number segments.
Different number segments are allocated to different operators. An operator can only
handle subscribers with numbers falling within the number segment allocated to the
operator.
Dependency
for other NEs.
1.8.9 WHFD-090301 Dynamic Subscriber Data Management
Availability
Specification
None.
Summary
The HLR9820 supports the modification of the subscriber location information,
including VLR number, MSC number, and SGSN number.

Feature Description

Issue 1.0 (2013-02-25)
Page 67 of 177

Benefits
For carriers
For subscribers
None.
Description
The HLR9820 allows you to modify the location information of a subscriber from the
operation & maintenance terminal, including VLR number and MSC number. It can
also force a subscriber online and insert subscription data, increasing the system
maintainability.
Dependency
for other NEs.
1.8.10 WHFD-090302 Unsupported Service Replacement
Availability
Specification
None.
Summary
The HLR9820 uses other supplementary services to replace services not supported by
some network entities, including ODB, AoCC, and CUG.
Benefits
For carriers
This service enhances the network compatibility and configurability, and provides
carriers with additional means of data configuration.
For subscribers
None.
Description
When the MSC/VLR receives unsupported service data, it returns a response to the
HLR. Upon receiving the response message, the HLR processes the data or resends
replacement services to the MSC/VLR according to the related configuration.

Feature Description

Issue 1.0 (2013-02-25)
Page 68 of 177

Dependency
for other NEs.
1.8.11 WHFD-090400 Service Template Setting
Availability
Specification
None.
Summary
The HLR9820 supports configuring the common service templates (including
subscriber definition template, CAMEL template, and VLR roaming restriction
template) for higher operating efficiency.
Benefits
For carriers
This service greatly simplifies service subscription formalities.
For subscribers
None.
Description
The HLR9820 provides a series of templates for the subscription data. These templates
include subscriber definition template and CAMEL template, and can be referenced
repeatedly. When a subscriber subscribes to a service, he/she only needs to reference
the related template. This not only simplifies service subscription formalities, but also
improves the operating efficiency.
Dependency
for other NEs.
1.8.12 WHFD-090500 Batch Operation
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 69 of 177

Specification
None.
Summary
The HLR9820 supports batch processing functions, including:
Batch processing of consecutive number segments
Batch processing of non-consecutive number segments
Batch processing of files
Benefits
For carriers
This service simplifies the service subscription procedure and improves operating
efficiency.
For subscribers
None.
Description
The HLR9820 supports defining/deleting subscribers in batches by specifying the
IMSI/MSISDN list file (namely batch process of non-consecutive number segments)
or the starting IMSI/MSISDN number and subscriber quantity (namely batch process
of consecutive number segments). Meanwhile, the HLR9820 also supports file batch
process. You can write all commands to be executed into a file, and the HLR can
execute these commands automatically.
Dependency
for other NEs.
1.8.13 WHFD-090600 Operation Log Management
Availability
Specification
None.
Summary
The HLR9820 supports operation log management. An operation log clearly records
all operations by an operator. The information in an operation log mainly includes time,
IP address of the operated PC, and executed MML commands. Carriers can get to
know the data operations conducted by an HLR operator.

Feature Description

Issue 1.0 (2013-02-25)
Page 70 of 177

Benefits
For carriers
This service provides carriers with a means of checking and auditing historical
commands.
For subscribers
None.
Description
The HLR9820 supports querying the historical commands executed by an operator.
You can query the operation logs by operator, time range, or the associated subscriber
number. An operator can only query the historical commands executed personally.
This mechanism effectively protects the security of the information.
Dependency
for other NEs.
1.8.14 WHFD-090800 Subscriber Statistics
Availability
Specification
None.
Summary
The HLR9820 provides the subscriber statistics function, allowing you to collect
statistics on the total subscribers and total roaming subscribers.
Benefits
For carriers
This service provides carriers with a means of collecting statistics.
For subscribers
None.
Description
The HLR9820 supports collecting statistics on authentication data records, total
subscribers, and roaming subscribers (for example, subscribers roaming under a
specific VLR).

Feature Description

Issue 1.0 (2013-02-25)
Page 71 of 177

Dependency
for other NEs.
1.9 WHFD-100000 Protocol Interfaces
The HLR9820 supports MAP protocols and the related interfaces (including C, D, J,
Gc, Gr, and Lh interfaces), as well as the BOSS interface.
1.9.1 WHFD-100100 MAP Protocols
Availability
Specification
3GPP29002
Summary
The HLR9820 supports MAP Phase 2+ protocol, MAP Phase 2 protocol, and MAP
Phase 1 protocol.
Benefits
For carriers
This service provides carriers with additional service attributes and enables the
smooth network evolution.
For subscribers
None.
Description
The HLR9820 supports MAP Phase 2+ protocol, MAP Phase 2 protocol, and MAP
Phase 1 protocol. The HLR9820 is forward compatible, and can be upgraded to a
higher version smoothly.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 72 of 177

1.9.2 WHFD-100101 C/D/J/Gc/Gr/Lh Interface
Availability
Specification
3GPP29002
Summary
The HLR9820 supports the following interfaces:
C interface (the peer end entity is MSC)
D interface (the peer end entity is VLR)
J interface (the peer end entity is gsmSCF)
Gc interface (the peer end entity is GGSN)
Gr interface (the peer end entity is SGSN)
Lh interface (the peer end entity is GMLC)
The supported protocols are: MTP2/MTP3/SCCP/TCAP/MAP
Benefits
For carriers
This service enables carriers to satisfy the basic interface requirements.
For subscribers
None.
Description
The HLR9820 supports various interfaces connecting to the surrounding NEs. Figure
1-1 shows the interfaces between the HLR and surrounding NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 73 of 177

Figure 1-1 Interfaces between the HLR and surrounding NEs
BS
BS
BS
BS
BS
BS
BSC
RNC
SGSN GGSN
MSC
SCP
HLR
IP Network
GSM/PSTN
Iu
Iu
Gn Gi
C/D
CAP
ISUP
Gc
Gr
GMLC
Lg
Lh
Lg
Lc
J

Dependency
for other NEs.
1.9.3 WHFD-100200 BOSS Interface
Availability
Specification
None.
Summary
The HLR9820 provides the BOSS interface. Through the BOOS interface, carriers can
provide subscriber data management interfaces in the business hall, and realize second
system development.
Benefits
For carriers
This service enables carriers to satisfy the basic interface requirements.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 74 of 177

Description
Currently, the HLR9820 supports the BOSS interface adopting the man-machine
language (MML) command format.
Dependency
for other NEs.
1.9.4 WHFD-100300 Application/Data Layer Interface
Availability
This service is inherited from HLR9820 V900R003.
Specification
None.
Summary
The connection between the application layer and the data layer is bi-directional IP
connection. The links between the application layer and data layer work in load
sharing mode.
Benefits
For carriers
This service can satisfy carriers's requirements for smooth system upgrading and
expansion.
For subscribers
None.
Description
The latest-generation HLR9820 supports the separation of services from data. This
service layer is also referred to as application layer. The connection between the
application layer and the data layer is of IP connection.
The design of the interfaces in the service layer and the data layer can be characterized
as follows:
Adopts data access based design. The data interface is irrelevant to services.
Optimize the interface design of the BE. The interface design improves the
usability of data, which is independent of service processing. The interface
supports both HLR application and CDMA HLR and HSS applications.
Provides message-based asynchronous access mode.
Supports separating services from data and incorporating multiple operations in a
message into a transaction.

Feature Description

Issue 1.0 (2013-02-25)
Page 75 of 177

The BE interface is independent of the service processing. All interactions
between the service processing and the data processing adopt the request
response mode. The BE receives request messages and sends response messages.
Provides excellent compatibility. The new function is compatible with the
original interface.
Dependency
for other NEs.
1.10 WHFD-110000 Operation and Maintenance
Functions
For the convenience of operation and maintenance, the HLR9820 provides the
following operation and maintenance functions:
Security Management
Performance Management
Fault Management
Configuration Management
Equipment Management
Signaling Tracing (WHFD-110600, including Interface the Signaling Tracing
function and the Subscriber Signaling Tracing function)
1.10.1 WHFD-110100 Security Management
Availability
Specification
None.
Summary
The HLR security management function allows you to assign operation rights to an
operator or a workstation to prevent the system from being accessed by an illegal
workstation and prevent an operator from executing unauthorized commands.
The HLR assigns operation rights based on command groups. A command group is a
set that organizes a series of commands together according to a certain rule. In the
HLR, there are totally 32 command groups. Command groups 1031 are user defined;
other command groups are default ones and cannot be modified. You can assign
operation rights to an operator or a workstation by configuring command groups.

Feature Description

Issue 1.0 (2013-02-25)
Page 76 of 177

The HLR provides level-based management for operators and workstations. Different
operators and workstations are allocated with different operation rights. This
mechanism can prevent unauthorized operations and improve system security.
Meanwhile, the HLR provides maintenance and operation logs for recording the
operations and maintenance conducted by an operator. When problems occur, the
operation logs can be used to check these operations and maintenance.
Benefits
For carriers
This service provides a perfect system right control mechanism. Carriers can
control the access of the system by both workstations and operators, making daily
operation and maintenance very flexible and safe.
For subscribers
None.
Description
Right: It refers to the right of operating and managing the system. The assignment
of rights to an operator or a workstation is based on command groups.
Operator: It refers to the person who manages or operates the system. The
operators are graded into five levels, as shown in the table below:
Level Right
Administrator View data, maintain the system, configure data,
and manage users.
Operator View data, maintain the system, and configure
data.
User View data and maintain the system.
Guest View data.
Custom The rights allocated by the administrator.
Command groups: A command group is a set that organizes a series of commands
together according to a certain rule. There are totally 32 command groups in the
system. The table below lists the categories of these command groups:
Command
group
category
Rights allocated to every
member of the group
Right of
modifying commands
G_ADMIN Only the Admin and
administrator-level operator have the
rights of the command group. The
command group comprises all
commands of the system.

It is prohibited to
modify command
names.

It is prohibited to
add/delete a
command to/from the
command group.

Feature Description

Issue 1.0 (2013-02-25)
Page 77 of 177

Command
group
category
Rights allocated to every
member of the group
Right of
modifying commands
G_OPERA
TOR
The administrator-level operator and
operator-level operator have the rights
of the command group.

It is prohibited to
modify command
names.

It is prohibited to
add/delete a
command to/from the
command group.
G_USER The administrator-level operator,
operator-level operator, and user-level
operator have rights of the command
group.

It is prohibited to
modify command
names.

It is prohibited to
add/delete a
command to/from the
command group.
G_GUEST The rights of the command group are
allocated to all operators. The
guest-level operator has the rights of
the command group only.

It is prohibited to
modify command
names.

It is prohibited to
add/delete a
command to/from the
command group.
G_0G_9 The Admin, administrator-level
operator, and NMS operator have all
custom-level operator has all or
partial rights of the command group.

It is prohibited to
modify command
names.

It is prohibited to
add/delete a
command to/from the
command group.
G_10_31 The Admin, administrator-level
operator, and NMS operator have all
custom-level operator has all or
partial rights of the command group.

It is allowed to
modify command
names.

It is allowed to
add/delete a
command to/from the
command group.
Figure 1-2 shows the relationship between different command groups.

Feature Description

Issue 1.0 (2013-02-25)
Page 78 of 177

Figure 1-2 Relationship between different command groups
G_OPERATOR
G_USER
G_GUEST
G_ADMIN

Workstation: It refers to the PC that is connected to the BAM server and contains
the BAM client programs. The HLR distinguishes different workstations by IP
addresses. The assignment of rights to a workstation is based on command groups.
The rights of workstation can be graded into four levels:
Level Rights
G_Admin View data, maintain the system, configure data,
and manage users.
G_Operator View data, maintain the system, and configure
data.
G_User View data and maintain the system.
G_Guest View data.
Ultimate rights of an operator: The ultimate rights of an operator are the
intersection of the rights allocated to the operator and the rights of the
workstation operated by the operator. For example, the workstation has the rights
of command groups G_0 and G_1; the operator has the rights of the command
groups G_1 and G_2. Consequently, the operator can only execute commands of
the command group G_1 in the workstation.
Dependency
for other NEs.
1.10.2 WHFD-110200 Performance Management
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 79 of 177

Summary
Performance management refers to the activities of measuring the performance of a
device and its surrounding network, involving traffics measurement, system resource
measurement, signaling procedure measurement, and failure cause measurement. In
the HLR, the performance measurement involves system resource measurement and
signaling procedure measurement.
In addition to the basic measurement items, the performance measurement function of
the HLR9820 allows you to define new measurement items on the basis of the original
measurement items. You can collect the desired measurement data conveniently, and
observe the running status of the network flexibly.
Benefits
For carriers
This service enables carriers to implement various traffic measurement tasks,
monitor the running status of the equipment, and optimize the network.
For subscribers
None.
Description
The table below lists the measurement items supported by the HLR9820.
Measurement category Measurement items
Global component
measurement
CPU occupancy measurement
HDU measurement task CPU measurement
MAP measurement
SUB measurement
3GSCS measurement
3GSWB measurement
3GSWC measurement
3GSWCS measurement
3GSWG measurement
3GSWL measurement
3GSWLK measurement
3GSWO measurement
3GSWOS measurement
3GSWR measurement
2GSWG measurement

Feature Description

Issue 1.0 (2013-02-25)
Page 80 of 177

Measurement category Measurement items
2GSWC measurement
2GSCS measurement
2GSWCS measurement
2GSWL measurement
2GSWLK measurement
2GSWO measurement
2GSWOS measurement
2GSWR measurement
Signaling and interface
measurement
M3UA link traffics measurement
M3UA link set traffics measurement
M3UA destination entity measurement.
M3UA signaling link measurement
MTP3B signaling link measurement
MTP3B signaling link set measurement
MTP3B destination signaling point measurement
MTP destination signaling point measurement
MTP signaling link measurement
MTP signaling link measurement
SAAL signaling measurement
SCCP availability measurement
SCCP utilization rate measurement
SCCP performance measurement
TCAP CSL performance measurement
TCAP TSL performance measurement
TCAP availability measurement
TCAP messages count
TCAP utilization rate measurement

Feature Description

Issue 1.0 (2013-02-25)
Page 81 of 177

Dependency
for other NEs.
1.10.3 WHFD-110300 Fault Management
Availability
Specification
None.
Summary
The HLR9820 provides alarm information output. It can report abnormality occurring
during its operation process. The output alarms can be classified into alarms outputted
to the alarm maintenance terminal and the alarms outputted to the alarm box.
Benefits
For carriers
This service enables carriers to get to know the problems in the HLR, and take
preventive measures accordingly.
For subscribers
None.
Description
The HLR9820 provides two types of alarms: fault alarms and event alarms. Generally,
the fault alarm is more serious than the event alarm. The fault alarm involves alarm
generation and alarm recovery. The event alarm is generated due to an occasional
event occurring during the running process of the equipment. The event alarm does not
involve recovery. Some event alarms recur at a specified time.
The HLR9820 enables carriers to implement the following alarm management
operations:
Query alarm information at any time, and specify the alarm level, alarm type,
alarm time for an alarm to facilitate alarm query.
Conveniently know about each alarm based on explanatory information contained
in the alarm.
Enable/disable alarm shielding manually.
The HLR9820 provides an alarm box. When an alarm is reported, the alarm box
generates siren to remind the maintenance personnel.

Feature Description

Issue 1.0 (2013-02-25)
Page 82 of 177

Dependency
for other NEs.
1.10.4 WHFD-110400 Configuration Management
Availability
Specification
None.
Summary
The HLR9820 provides configuration management function, allowing you to
configure the system, a board, and an interface.
Benefits
For carriers
This service enables carriers to configure the data of the HLR flexibly and satisfy
various data configuration requirements.
For subscribers
None.
Description
The HLR9820 provides flexible data configuration functions, allowing you to
configure data online and offline. Meanwhile, the HLR9820 supports configuring the
data through the MML. You can produce data configuration scripts conveniently, thus
reducing configuration difficulties.
Dependency
for other NEs.
1.10.5 WHFD-110500 Equipment Management
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 83 of 177

Specification
None.
Summary
The HLR9820 provides equipment management function, allowing you to manage the
software and hardware of the equipment conveniently.
Benefits
For carriers
This service enables carriers to manage the HLR conveniently and satisfy the
daily operation requirements.
For subscribers
None.
Description
The hardware management involves:
Resetting a board
Switching a board
Loading data to a board
Other related functions
Software management involves:
Loading patches
Activating patches
Deactivating patches
Other related functions
Dependency
for other NEs.
1.10.6 WHFD-110601 Interface Signaling Tracing
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 84 of 177

Summary
The HLR9820 provides powerful signaling tracing functions, including interface
signaling tracing and subscriber interface signaling tracing.
Benefits
For carriers
This service enables carriers to trace all messages of an interface. When locating
equipment interconnection fault or interface fault, it can check protocol
compliance of messages through the service.
For subscribers
None.
Description
The interface signaling tracing involves:
Tracing the signaling of the Signaling Connection and Control Part (SCCP)
interface, Signaling Control Transmission Protocol (SCTP) interface, MTP3-User
Adaptation Layer (M3UA) interface, and Message Transfer Part Layer 3 (MTP3)
interface.
Tracing the Mobile Application Part (MAP) signaling message of the
C/D/Gc/Gr/Lh/J interface
After the tracing finishes, you can view the file with the traced messages. The HLR
provides explanations for the message in line with standard protocols, allowing you to
read the message code stream conveniently.
Dependency
for other NEs.
1.10.7 WHFD-110602 Subscriber Signaling Tracing
Availability
Specification
None.
Summary
This service enables you to create a subscriber interface tracing task by IMSI/MISDN,
that is, to trace the signaling of a specified interface of a specified subscriber. You can
obtain online explanations for the traced messages and save them in a file.

Feature Description

Issue 1.0 (2013-02-25)
Page 85 of 177

Benefits
For carriers
This service enables carriers to find causes of the problems in the services of a
subscriber.
For subscribers
None.
Description
You can trace the signaling messages of a subscriber at the C/D/Gc/Gr/Lh/J interface.
After the tracing finishes, you can view the file with the traced messages. The HLR
provides explanations for the message in line with standard protocols, allowing you to
read the message code stream conveniently.
Dependency
for other NEs.
1.10.8 WHFD-110700 Equipment Archive Management
Availability
Specification
None.
Summary
This function enables you to query the hardware and software information of the HLR
through the BAM or NMS.
Benefits
For carriers
This function facilitates the management and maintenance of the HLR devices.
For subscribers
None.
Description
This function enables you to query the detailed information of the HLR, which
includes the following:
Basic information about the hardware devices
Connection information, module information and configuration of the HLR

Feature Description

Issue 1.0 (2013-02-25)
Page 86 of 177

Information about the peer devices
Version information of the host
Information about the cabinet, subrack, and board, and the Flash E-label of the
board
The BAM server creates an .xml file after receiving the command of generating the
device profile sent by the NMS, and then the NMS can send commands to require the
BAM server to upload the .xml file to a specified directory of the NMS.
Dependency
This service is a non-standard service. The implementation of this service needs the
support of Huawei network management system.
1.10.9 WHFD-110800 Service Processing Panel
Availability
This feature is inherited from HLR9820 V900R003.
Specification
None.
Summary
The HLR9820 automatically collects information about the whole system and presents
the running status of each service node through a visualized interface.
Benefits
For carriers
This feature enables carriers to query observe the running status of the system,
thus helping carriers to prevent some faults. If a fault occurs, this feature can help
carriers to troubleshoot the fault and support the subsequent recovery measures
taken by carriers.
For subscribers
None.
Description
The service processing panel provides a typology view about the logical modules of
the system. The system automatically obtains the configuration of each logical node
and visually presents the relations among all the nodes (for example, whether the
nodes are in the same cluster) on the panel. In addition, the panel also shows the
physical position of each node.
After obtaining the service processing information of each node, the system
determines the running status of each node and displays the status in different colors.
The running status of each node can be one of the following:

Feature Description

Issue 1.0 (2013-02-25)
Page 87 of 177

Normal state, indicating that the service processing capability of the node or
module is normal.
Warn state, indicating that the service processing capability of the node or module
deteriorates.
Faulty state, indicating that the service processing capability of the node or
module is abnormal.
Unknown state, indicating that the service processing capability of the node or
module is unknown.
In addition, this feature provides the historical and real-time information about the
running status of nodes upon query, and presents the information in a visualized
interface.
Dependency
This feature is a non-standard feature. The implementation of this service needs the
1.10.10 WHFD-110900 Monitoring Connection to the
Provisioning System
Availability
Specification
None.
Summary
The HLR9820 can automatically monitor the status of the connection to the
provisioning system.
Benefits
For carriers
This service allows carriers to conveniently monitor the connection between the
HLR and the provisioning system.
For subscribers
None.
Description
The provisioning system manages the provisioning of services. If the connection
between the provisioning system and the HLR is interrupted, the HLR can
automatically detect the fault and send alarms to the network management system
(NMS). The maintenance engineers can view the alarms on the NMS, and then rectify
the fault.

Feature Description

Issue 1.0 (2013-02-25)
Page 88 of 177

Dependency
This service is a non-standard service. The implementation of this service needs the
1.11 WHFD-120000 Reliability Functions
Comprehensive protection measures are adopted in the hardware and software design
of the HLR9820 to ensure high reliability.
The hardware reliability design of the HLR9820 includes:
Redundancy and Backup Design (WHFD-120101)
Power Reliability (WHFD-120102)
Distributed Boards (WHFD-120103)
Distributed Power Supply (WHFD-120104)
Dual-Plane Communications over IP (WHFD-120105)
Automatic Adjustment of Fan Speed (WHFD-120106)
The software reliability design of the HLR9820 includes
Automatic Fault Detection And Self-Healing (WHFD-120201)
Automatic/Manual Switchover (WHFD-120202)
Automatic Multi-Level Backup and Recovery of Subscriber Data
(WHFD-120203)
Flow Control (WHFD-120204)
System Restoration upon Upgrade Failure (WHFD-120205)
Support Memory Data Management Technology (WHFD-120206)
Distributed Design of Software Modules (WHFD-120207)
Support Subscriber Data Consistency Check (WHFD-120208)
Distributed Storage of Subscriber Data (WHFD-120209)
Automatic Load Sharing Among Modules (WHFD-120210)

1.11.1 WHFD-120101 Redundancy and Backup Design
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 89 of 177

Summary
The HLR9820 adopts redundancy & backup design. It adopts redundancy design for
all the components.
Benefits
For carriers
This service can enhance the system reliability and ensure uninterrupted service
provisioning.
For subscribers
None.
Description
The faults of some components may lower the bearer capability of the system. To
avoid such adverse impact and ensure the reliability of the system, the HLR9820
adopts the redundancy and backup design for components. All the components of the
same type work in load-sharing mode. If a component fails, the component of the
same type will automatically take over the service processing, thus ensuring that the
service provisioning of the HLR is not interrupted.
Dependency
for other NEs.
1.11.2 WHFD-120102 Power Reliability
Availability
This feature is inherited from HLR9820 V600.
Specification
None.
Summary
Faults in the power supply may result in a disaster. The HLR9820 adopts
high-reliability design for the power supply system.
Benefits
For carriers
This feature enables carriers to enhance the system reliability, ensure service
provisioning uninterrupted, and improve the customer's satisfaction level.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 90 of 177

Description
The HLR9820 adopts the following technologies to ensure the high reliability of the
power supply system:
Checks the input voltage of the power system, and generates an alarm when the
voltage of the power system is too high or too low.
Prevents voltage drop and is lightning-proof.
Provides power-off protection for programs and data.
Provides over-voltage protection, over-current protection, and wrong polarity
connection.
Provides backup for the power module of the board.
Dependency
for other NEs.
1.11.3 WHFD-120103 Distributed Boards
Availability
Specification
None.
Summary
The distributed structure allows multiple functional entities that are identical in a
system to work in load-sharing mode to accomplish a certain function. The most
distinguished feature of the distributed structure is resource sharing in the system.
When any functional entity fails, the load will be automatically switched over to other
functional entities. Thus, the service provisioning of the whole system is not adversely
affected.
The HLR9820 adopts the distributed design for the boards.
Benefits
For carriers
This feature enhances the reliability of the system and ensures that the service
provisioning is not interrupted, thus improving the customers' satisfaction.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 91 of 177

Description
All the boards in the HLR9820 work in distributed and load-sharing mode. If a board
fails, another board of the same type will take over the service processing. Thus, the
service provisioning of the HLR is not interrupted.
The process of service takeover is as follows:
When a board fails, other boards of the same type immediately take over the
service processing of the faulty board.
The overall process is automatically implemented. No manual operation is
required.
The service takeover is complete within three seconds.
During the whole process, the service is not interrupted.
After taking over the services, the boards automatically distributes the load in a
balance mode.
Dependency
for other NEs.
1.11.4 WHFD-120104 Distributed Power System
Availability
Specification
None.
Summary
affected.
The HLR9820 adopts the distributed design for the power system.
Benefits
For carriers
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 92 of 177

Description
The power modules of the HLR9820 adopt distributed architecture. If a power module
fails, the other power module will take over the load of the faulty module, thus
ensuring that the power supply of the HLR is not interrupted.
The components of a subrack are evenly divided into two zones: S1 and S2. Two
power modules lead in different power supplies for the two zones. Module 1 controls a
power input (A1) of S1 and a power input (B1) of S2; Module 2 controls a power
input (A2) of S1 and a power input (B2) of S2, as shown in Figure 1-3.
Figure 1-3 Operating principle of the distributed power system

Dependency
for other NEs.
1.11.5 WHFD-120105 Dual-Plane Communications over IP
Availability
Specification
None.
Summary
The HLR9820 adopts dual planes for IP communications and dual dual-star
architecture to avoid single-point faults. The service plane and the management plane
are separated. Thus, the system reliability is greatly improved.

Feature Description

Issue 1.0 (2013-02-25)
Page 93 of 177

Benefits
For carriers
For subscribers
None.
Description
There are two switching units (SWUs) in the subrack of the HLR9820. Each SWU
communicates with other service boards in the dual-star mode. The dual dual-star
architecture can effectively avoid single-point faults.
The exchange of service data and the exchange of management signaling are
implemented in two independent planes. The two planes are separated, as shown in
Figure 1-4, thus ensuring the reliability of the system.
Figure 1-4 Dual-plane communications over IP

Dependency
for other NEs.
1.11.6 WHFD-120106 Automatic Adjustment of Fan Speed
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 94 of 177

Summary
The HLR9820 automatically adjusts the speed of the fan according to the temperature
of the system.
Benefits
For carriers
provisioning is not interrupted, thus improving the customers' satisfaction. In
addition, this feature lowers the power consumption, thus helping carriers to
reduce the operation cost.
For subscribers
None.
Description
The HLR generates heat during the running. The fans dissipate the heat from the
subrack, thus ensuring a proper temperature for the system running. The fans of higher
speed can achieve better heat dissipation, but also require more power at the same time.
The HLR9820 can automatically adjust the speed of fans based on the temperature of
the system, thus creating a suitable environment for the system running and effectively
reducing power consumption.
Dependency
for other NEs.
1.11.7 WHFD-120201 Automatic Fault Detection and
Self-Healing
Availability
Specification
None.
Summary
The HLR9820 adopts real-time fault monitoring and self-healing designs to ensure the
reliability of its software.
Benefits
For carriers

Feature Description

Issue 1.0 (2013-02-25)
Page 95 of 177

This service enables carriers to enhance the system reliability, ensure
uninterrupted service provisioning, and improve the customer's satisfaction level.
For subscribers
None.
Description
The HLR9820 applies the real-time fault monitoring and self-healing technologies on
the following occasions:
Automatic detection of hardware/software faults
Automatic execution of the fault handling program to remove faults in important
hardware or software
Implementation of failover if the fault cannot be removed. The system
automatically switches the services to another board based on the load sharing
principle.
Dependency
for other NEs.
1.11.8 WHFD-120202 Automatic/Manual Switchover
Availability
Specification
None.
Summary
When the active system of the HLR is faulty, the HLR9820 can automatically switch
to the standby system. The HLR9820 supports both automatic switchover and manual
switchover.
Benefits
For carriers
This service enables carriers to enhance the system reliability, ensure
uninterrupted service provisioning, and improve the customer's satisfaction level.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 96 of 177

Description
When the active signaling access board of the HLR is broken down, the HLR can
automatically switches to the standby board. On some special occasions (such as
network upgrading), you switch from the active system to the standby system
manually.
Dependency
for other NEs.
1.11.9 WHFD-120203 Automatic Multi-Level Backup and
Recovery of Subscriber Data
Availability
Specification
None.
Summary
A core function of the HLR9820 is to store a large quantity of subscriber data, which
are very important to carriers. The HLR9820 adopts automatic multi-level backup and
recovery mechanism to ensure the security of the subscriber data. When an accident
takes place, the subscriber data can be recovered immediately.
Benefits
For carriers
This service can enhance the system reliability. It provides multiple data backup
functions to ensure the security of subscriber data. When accidents take place, the
service can recover the subscriber data immediately to avoid further loss.
For subscribers
None.
Description
The HLR9820 adopts the multi-level data backup and recovery mechanism. This
mechanism enables subscriber data to be stored in different physical data storage
devices, ensuring the security of subscriber data: The multi-level data backup
comprises:
Level-1 backup
The subscriber data is stored in the memories of different boards. Multiple boards
form a cluster. The data of the master node is synchronized to the slave node.

Feature Description

Issue 1.0 (2013-02-25)
Page 97 of 177

Level-2 backup
The subscriber data stored in the board memory is backed up to the local hard
disk of the board. Two local hard disks work in RAID 1 mode.
Level-3 backup
The subscriber data stored in the board memory is backed up to the disk array.
The disk array works in RAID mode and is configured with hot spare disks.
Accordingly, there are three means to realize the data recovery:
Recovering the data by duplicating data from the other nodes in the same cluster
Recovering data from the local disk
Recovering data from the disk array
Dependency
for other NEs.
1.11.10 WHFD-120204 Flow Control
Availability
Specification
None.
Summary
The HLR9820 provides the flow control function. When the traffic volume exceeds
the upper threshold of the processing capability of the HLR, the service can prevent
the large quantity of messages received by the HLR from interrupting the service.
Benefits
For carriers
This service enables carriers to enhance the system reliability, avoid service
interruption resulting from heavy burst traffics, and prevent the avalanche effect.
For subscribers
None.
Description
If the HLR enables its flow control mechanism, when congestion occurs due to
excessive messages, the HLR discards a portion of message. In this way, it can ensure
the successful transmission of messages falling within its processing capacity.
Consequently, the services can be provisioned for most subscribers normally, and the
avalanche effect can be prevented.

Feature Description

Issue 1.0 (2013-02-25)
Page 98 of 177

Adopting perfect traffic control design, the HLR9820 can effectively process burst
heavy traffics.
Applies multi-level traffic control over the MTP, SCCP and TCAP layer of the
service layer to realize smooth traffic volume adjustment.
Supports prioritized flow control of MAP messages.
Detects and checks the payload handling efficiency and resource utilization rate
of the processor in real time to realize auto-adapted flow control.
Provides high-speed BOSS command processing capability. If the flow reaches
the maximum processing capability, the HLR enables the flow control function to
protect the system.
Allows flexible configuration of flow control parameters to realize forced flow
control.
Applies the flow control to the subscriber data management and MAP operations
separately. The priority of the MAP operation is higher than that of the subscriber
data management.
Dependency
for other NEs.
1.11.11 WHFD-120205 System Restoration Upon Upgrade
Failure
Availability
Specification
None.
Summary
When upgrading fails due to exceptions, the HLR9820 supports quick rollback to the
original version. This can prevent the upgrading failure from affecting the services too
long.
Benefits
For carriers
This service provides carriers with an assurance measure against upgrading
failure. Once the upgrading fails, the service can restore the subscriber data and
roll back the version to protect the system against the failure.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 99 of 177

Description
To prevent upgrading failure, the HLR9820 provides the version rollback function.
This function is a system assurance mechanism. It can restore the subscriber data and
version to the initial status, and minimize the impact of the upgrading failure.
Dependency
for other NEs.
1.11.12 WHFD-120206 Support Memory Data Management
Technology
Availability
This function is inherited from HLR9820 V900R003.
Specification
None.
Summary
The traditional HLR adopts the business database such as Oracle and DB2 to store
subscriber data; that is, the subscriber data is stored in hard disks. With the memory
data management technology, the HLR9820 stores all the subscriber data in the
memory, and the hard disks are used only for permanent storage. Thus, the memory
data management technology enables the HLR9820 to feature in higher reliability and
fast processing speed.
Benefits
For carriers
The memory data management technology prevents the adverse impact on the
reliability of the system in the case of hard disk fault. Besides, it provides
high-speed data processing. Therefore, this technology is widely used for
large-capacity HLRs.
For subscribers
None.
Description
The memory manages all the subscriber data stored in the HLR9820. The board
memory accomplishes the data query and data modification related to service
processing. The external storage device (such as the disk array) of boards only
provides permanent storage of data. It is independent of service processing.
The memory data management endues the HLR9820 the following advantages:

Feature Description

Issue 1.0 (2013-02-25)
Page 100 of 177

This service processing is independent of the external data storage device of
boards. If the external data storage device of boards fails, the service processing
will not be adversely affected.
Compared with the data management in the hard disk, the in-memory data
management features higher throughput and shorter time delay. It greatly
enhances the system performance, especially for the large-capacity HSS.
Dependency
for other NEs.
1.11.13 WHFD-120207 Distributed Design of Software
Modules
Availability
Specification
None.
Summary
affected.
The HLR9820 adopts the distributed design for software modules.
Benefits
For carriers
The distributed design prevents single-point faults and improves the reliability of
system. Therefore, the service provisioning is not interrupted even if some faults occur.
This feature helps carriers to improve the customers' satisfaction.
For subscribers
None.
Description
The HLR9820 adopts a fully distributed architecture. It logically consists of the
following functional layers:
Signaling Processing Layer

Feature Description

Issue 1.0 (2013-02-25)
Page 101 of 177

Data Service Layer
Subscriber Data Management Layer
Data Storage Layer
Each layer adopts a distributed structure, as shown in Figure 1-5.
Figure 1-5 Distributed design of software

The signaling processing layer consists of the signaling access unit (SAU) and the
service control function (SCF). This layer is called the frond end (FE). The FE leads in,
analyzes and processes signaling
The data service layer consists of the data routing unit (DRU) and the data service unit
(DSU).
The subscriber data management layer consists of the subscriber management unit
(SMU) and the subscriber management function (SMF).
The data storage layer adopts the highly reliable commercialized database
management system. It also uses the disk array to provide permanent storage of
subscriber data. The hard disks of the disk array adopt RAID technology and hot spare
disks to ensure the security of subscriber data.
The data service layer, subscriber data management layer and data storage layer
composes the back end (BE). The BE stores and manages subscriber data, and also
provides data service for other modules upon request.
The distributed architecture of these software modules prevents single-point faults and
greatly improves the reliability of the system.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 102 of 177

1.11.14 WHFD-120208 Support Subscriber Data Consistency
Check
Availability
Specification
None.
Summary
The HLR9820 adopts the multi-level data backup and duplication technology. This
technology enables subscriber data to be stored in different physical data storage
devices, and also provides the data consistency check function to ensure that the data
stored different physical data storage devices is consistent.
Benefits
For carriers
This function ensures the correctness of subscriber data in the case of data recovery,
thus ensuring the reliability of the system.
For subscribers
None.
Description
The HLR9820 supports the subscriber data consistency check function. If the data is
inconsistent, the HLR9820 can automatically restore the data to be consistent. The
data consistency check consists of the following:
Data consistency check performed on the master and slave nodes of an HLR
Data consistency check performed on the memory database and physical data
storage devices of an HLR
Data consistency check performed on the active and redundancy HLRs if the
HLRs adopt the seamless geographical redundancy solution.
Dependency
for other NEs.
1.11.15 WHFD-120209 Distributed Storage of Subscriber Data
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 103 of 177

Specification
None.
Summary
affected.
The HLR9820 adopts distributed storage of subscriber data.
Benefits
For carriers
The distributed storage ensures the security of subscriber data and improves the
reliability of system. Therefore, the service provisioning is not interrupted even if
some faults occur. This feature helps carriers to improve the customers' satisfaction.
For subscribers
None.
Description
Subscriber data is important for carriers. The HLR9820 uses DSU clusters to store
subscriber data. The DSCU clusters work with the DRU to provide data services for
other modules.
The HLR9820 adopts distributed storage of subscriber data. The DSU clusters store
subscriber data based on the capacity-balancing strategy. All the DSUs in a DSU
cluster store the same subscriber data and work in load-sharing mode. If a DSU fails,
the other DSUs in the same cluster will take over the load of the faulty DSU.
Therefore, data loss is prevented and the HLR9820 can continue to provide services.
Dependency
for other NEs.
1.11.16 WHFD-120210 Automatic Load Sharing Among
Modules
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 104 of 177

Specification
None.
Summary
The HLR9820 can automatically balance the load among different software modules.
Benefits
For carriers
The automatic load sharing technology protects the boards from being overloaded and
prevents system breakdown caused by overload. This improves the reliability of the
system.
For subscribers
None.
Description
During the system running, the load of different boards is unbalanced due to the
diversity of tasks and complexity of signaling processing. Therefore, some boards may
work inefficiently while the others are overloaded.
The HLR9820 can automatically balance the load among modules of the same type by
using software technology. Then, the boards work with the same load. This helps to
improve the stability and reliability of the system.
Dependency
for other NEs.
1.12 WHFD-572600 GSMR Functions
The HLR supports the following GSMR functions:
Voice Broadcast Service (VBS) (WHFD-572700)
Voice Group Call Service (VGCS) (WHFD-572800)
Follow Me (WHFD-573800)
User-to-User Signaling (UUS) service (WHFD-573900)
1.12.1 WHFD-572700 VBS
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 105 of 177

Specification
3GPP29002
Summary
In short, the VBS is a P2MP voice service. There is only one speaker, the dispatcher or
the business subscriber. There is no limitation on the number of listeners.
The subscribers involved in the VBS can be divided into two categories: dispatcher
and business subscriber.
Benefits
For carriers
The VBS service complies with the GSMR specifications, and is mainly applied
in railway mobile telecommunication. The carrier can capitalize on the group call
capability of the VBS service to serve the subscribers.
For subscribers
The service enables the subscriber to make unidirectional conversation.
Description
The VBS service can establish a broadcast call to a group of subscribers in a specified
area. The service is provisioned in simplex mode. Only the initiator adopts duplex
channel. During the process of the call, only the initiator can speak, and other
subscribers can only be the listeners.
The VBS service establishes a broadcast channel for every cell of the broadcasted area.
All subscribers in the cell share the downstream broadcast channel and receive the
voice.
The VBS call also supports establishing connections to the dispatcher. Each call can
establish connections to up to five dispatchers. The VBS call can be initiated by either
the business subscriber or the authorized dispatcher.
The subscribers involved in the VBS call can be divided into two categories:
dispatcher and business subscriber.
Dispatcher
Each VBS call supports up to 5 dispatchers. The dispatcher can be either a fixed
network subscriber or mobile subscriber. A dedicated channel is established for
the dispatcher.
Business subscriber
The business subscriber is the mobile subscriber who has subscribed to the VBS
service. The called business subscriber participates in the communication through
the group call channel of the group call area.
The VBS service enables a subscriber to establish a call connection to a group of
subscribers with specified group ID in the specified group call area. The group call
area consists of cells under the same MSC or different MSCs. When a VBS call is
made, a group call channel is established for every cell. The upstream channel is for
the current speaker only, and all listeners share the downstream channel. The

Feature Description

Issue 1.0 (2013-02-25)
Page 106 of 177

notification messages of the VBS call are broadcasted over the Notification Channel
(NCH).
During the process of a VBS call, only the calling dispatcher can speak. Other
dispatchers and business subscribers serve as the audience and cannot speak.
The VBS service differs from the VGCS service in that:
In the VBS call, only the VBS call initiator can speak, and other subscribers can
only serve as the listeners.
In the VGCS call, all subscribers except the dispatcher can seize the upstream
channel and make speech.
Therefore, the VBS service does not provide upstream channel management and
control, which is available in the VGCS service.
Dependency
The HLR realizes the function in compliance with the standard protocol and must
cooperate with the MSC/VLR. But there is no special requirement for MSC/VLR.
1.12.2 WHFD-572800 Voice Group Call Service (VGCS)
Availability
Specification
3GPP29002
Summary
The VGCS service is a voice service that realizes M2MP conversation. It allows up to
6 subscribers (including 5 dispatchers and 1 service subscriber) to speak, but imposes
no limitation on the quantity of listeners. The subscribers involved in the VGCS can be
divided into two categories: dispatcher and business subscriber.
Benefits
For carriers
The VGCS service complies with the GSMR specifications, and is mainly applied
in railway mobile telecommunication. The carrier can capitalize on the group call
capability of the VGCS service to serve the subscribers.
For subscribers
The service enables the subscriber to realize multi-party conversation (half
duplex).
Description
The VGCS service can establish broadcast call connections to a group of business
subscribers in a specified area. The VGCS service works in half duplex mode. In the

Feature Description

Issue 1.0 (2013-02-25)
Page 107 of 177

call process, any business subscriber can become the speaker. At any time, only one
speaker is allowed, and other business subscriber can only be the listeners.
Besides the broadcast call connections to the business subscribers, the VGCS also
supports establishing a dedicated duplex connection to the dispatcher. The dispatcher
can receive messages from and publish messages to the whole group.
The VGC call can be initiated by either the business subscriber or the authorized
dispatcher.
The subscribers involved in the VGCS call can be divided into two categories:
dispatcher and business subscriber.
Dispatcher
The dispatcher can be either a fixed network subscriber or a mobile subscriber. A
dedicated channel is established for the dispatcher. All dispatchers can speak at
any time. A dispatcher is authorized to initiate the VGCS call.
Business subscriber
The business subscriber is the mobile subscriber who has subscribed to the VGCS
service. The called business subscriber participates in the communication through
the group call channel for the group call area. All business subscribers scratch an
upstream channel. The authorized business subscriber can initiate the VGCS call.
The VBS service differs from the VGCS service in that:
In the VBS call, only the VBS call initiator can speak, and other subscribers can
only serve as the listeners.
In the VGCS call, all subscribers except the dispatcher can scratch the upstream
channel and make speech.
Therefore, the VBS service does not provide upstream channel management and
control, which is available in the VGCS service.
Dependency
1.12.3 WHFD-573800 Follow Me (FM)
Availability
Specification
3GPP22094, 3GPP23094
Summary
In the cluster communication, the follow-me function number represents a position
rather than a real subscriber. The current in-position person can register his/her

Feature Description

Issue 1.0 (2013-02-25)
Page 108 of 177

MSISDN under the follow-me function number, and associate the follow-me function
number with the real subscribers.
Benefits
For carriers
The FM service is an important service of the GSMR cluster service. It can be
used to provide dispatching for the railway, thus expanding the business scope of
the carrier.
For subscribers
The subscriber can dial the follow-me function number to call the in-position
person of the MS, without being concerned about the subscriber number. The
calling process is simple and quick.
Description
The FM service is also referred to as function number based addressing. The console
controls the current in-position subscriber according to the follow-me function number.
When the in-position subscriber changes, the telephone number also changes, but the
follow-me function number of the position remains unchanged. You can still initiate a
call to the in-position subscriber by dialing the follow-me function number.
The information on the mappings between the telephone numbers and follow-me
function numbers is saved in the HLR/Follow-Me Function Node (FFN). Currently,
Huawei FFN is integrated into the HLR. The FFN is a network node of the PLMN
carrier. The FM data of remote subscribers is saved in the FFN.
The HLR complies with the 3GPP 22.094 protocol. The HLR also supports storing,
modifying, and querying the FM data, and configuring the range of the actual
subscriber numbers. The subscriber of USSD service can register, deregister, and
query the follow-me function numbers through the subscriber's terminal.
Out of security consideration, the HLR supports authenticating rights of the FM
service subscriber, including COR and authorization range.
The HLR supports IN based FM service and MSC based FM service.
The following defines the general terminologies adopted in the FM function.
Initial subscriber
The initial subscriber can modify the FM data of a remote subscriber, so that a
call to the remote subscriber can be forwarded to a mobile subscriber of the initial
subscriber. An initial subscriber is correlated to multiple remote subscribers. In
other words, calls to the remote subscribers can be forwarded to the same initial
subscriber.
Remote subscriber
The remote subscriber is a subscriber defined by the carrier, and serves as the
callee of an FM call. The remote subscriber is a virtual subscriber, and is also a
mobile subscriber in some special circumstances. The remote subscriber can be
correlated to an initial subscriber. Any call to the remote subscriber is forwarded
to the correlated initial subscriber.
Initial number

Feature Description

Issue 1.0 (2013-02-25)
Page 109 of 177

The initial number refers to the MSISDN number of the initial subscriber. Any
call to the remote subscriber is forwarded to the number. The MSISDN number
must be the subscriber's basic MSISDN.
Remote number
The remote number is a function number correlated to an initial subscriber.
Generally, the remote number is a virtual number. In special circumstances, the
remote subscriber is the PLMN GSM subscriber. In this case, the remote number
is the subscriber's basic MSISDN number.
Potential initial subscriber
Out of security consideration, not all subscribers can become the initial subscriber
of a remote subscriber. Therefore, the carrier defines a potential subscriber for a
remote subscriber in the FM functional node. Only an authorized subscriber can
become the initial subscriber of the remote subscriber.
FM service manager
The FM service manager is a special initial subscriber, and is entitled to cancel
the forwarding correlation between a specified remote subscriber and an initial
subscriber. The carrier configures the FM service manager in the FM functional
node.
Dependency
1.12.4 WHFD-573900 User-to-User Signaling (UUS)
Availability
Specification
3GPP29002, 3GPP22087, 3GPP23087, 3GPP24087
Summary
The UUS service allows the subscriber to send and receive User-to-User Information
(UUI) during the calling process. The UUI information is transparently transmitted
over the network.
Benefits
For carriers
As an application scenario, the UUS1 enables the cluster system to realize the
transfer of follow-me function numbers, confirmation of high-priority calls, and
accurate addressing. It can also provide GSMR value-added service for the
carrier.
For subscribers
Under the GSMR system, the subscriber can realize transfer of follow-me
function numbers, confirmation of high-priority calls, and accurate addressing.

Feature Description

Issue 1.0 (2013-02-25)
Page 110 of 177

Description
The HLR supports storing, modifying, and querying the UUS subscription data. The
HLR also sends the subscriber's UUS subscription data to the VLR.
The UUS service also realizes the transfer of follow-me function numbers in the
cluster system.
The following describes the values of the UUS, based on the different phases of the
UUI messages:
UUS1
The UUI is inserted into the call process control message transmitted between the
caller and the callee. When a call connection is set up, the subscriber can insert
the UUI information to activate to the UUS1 implicitly or select a suitable way to
activate UUS1 explicitly. UUS1 can only be initiated by the caller, and can be
carried over all control signaling. When the UUS1 is the implicit request of the
caller, the callee's terminal does not make a response to the UUI from the caller,
but inserts the UUI into the subsequent message. When the UUS1 is the explicit
request of the caller, the callee's terminal needs to confirm it in the Alert message,
and inserts the UUI into the subsequent message.
UUS2
After receiving an indicator from the other party of the call, the UUS subscriber
can send and receive the UUI information. The UUS2 can be activated
explicitly.UUS2 can only be initiated by the caller. The callee's terminal must
confirm it in the Alert message. After UUS2 is confirmed, the caller and the
callee can transfer the UUS through the User-User Info signaling before the
callee makes a response.
UUS3
The subscriber can explicitly request the network to provide the UUS3 through
the indicator in the SETUP message or the Facility message. Only the caller can
request the network to provide UUS3 through the indicator in the SETUP
message. The callee's terminal needs to confirm it in the CONNECT message.
During the conversation period, both the caller and the callee can request the
network to provide the UUS3 through the Facility message. Both parties must
verify the Facility message. Once the UUS3 message is verified, both the caller
and the callee can transfer the UUI through the User-User Info signaling during
the conversation period.
The service flows of MAP 1/MAP 2 support UUS1; the service flow of MAP 3
supports UUS1, UUS2 and UUS3.
Dependency

Feature Description

Issue 1.0 (2013-02-25)
Page 111 of 177

2 Optional Features
2.1 WHFD-510000 CS Data Services
Availability
Specification
3GPP29002
Summary
The HLR9820 supports all standard data services, including the FAX service, data
CDA service, data CDS service, PAD service (CA), data PDS service, voice and data
alternation service, and voice + data service.
Benefits
For carriers
This service enables carriers to provide diversified data services, satisfy the
requirements of telecommunication markets, and boost its competitiveness.
For subscribers
Data service subscribers can obtain up-to-date information resources anywhere at
any time.
Description
FAX service
The HLR9820 supports two types of FAX services:
Voice + G3 FAX (TS 61) service
Automatic G3 FAX (TS 62) service
Data CDA service

Feature Description

Issue 1.0 (2013-02-25)
Page 112 of 177

Asynchronous duplex circuit data service working at 300 bit/s (BS21), 1200
bit/s (BS22), 1200/75 bit/s (BS23), 2400 bit/s (BS24), 4800 bit/s (BS25), and
9600 bit/s (BS26)
Transparent/Non-transparent 3.1 kHz audio VF/UDI data service
Data CDS service
Packet access, synchronous non-transparent 3.1K AF /UDI working at 1200 bits/s
(BS31), 2400 bits/s (BS32), 4800 bits/s (BS33), and 9600 bits/s (BS34).
PAD (CA) service
PAD access, circuit asynchronous transparent/non-transparent 3.1k audio/UDI
working at 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
Packet access, synchronous, UDI, non-transparent PDS service working at 2.4
kbits/s (BS51), 4.8 kbits/s (BS52), and 9.6 kbits/s (BS53).
Voice and data alternation service
The HLR9820 supports voice and data alternation service (BS61).
Voice + data service
The HLR9820 supports the data service that consists of voice service + data
service (BS81).
UMTS bearer service
The HLR9820 supports asynchronous bearer service (BS20) and synchronous
bearer service (BS30).
Dependency
The HLR9820 cooperates with the MSC/VLR to implement the service in compliance
with standard protocols. There is no special requirement for the MSC/VLR.
2.2 WHFD-520000 GPRS Services
The General Packet Radio Service (GPRS) is developed on the basis of the existing
GSM system. The GPRS adopts packet switching functional entities in the GSM
network to realize transmission of packet data. The GPRS system, the expansion of the
GSM circuit switching system, enables the mobile subscriber to access the Internet or
other packet data networks from his/her packet data mobile terminal.
The HLR9820 supports the following:
2.5G GPRS (WHFD-520100)
3G GPRS (WHFD-520200)
Enhanced HSPA (WHFD-520300)
Support GPRS charging character (WHFD-520400)

Feature Description

Issue 1.0 (2013-02-25)
Page 113 of 177

2.2.1 WHFD-520100 2.5G GPRS
Availability
Specification
Summary
The GPRS service accomplishes packet data functions through additional functional
entities deployed in the GSM network. The additional functional entities comprise the
GSM-GPRS network, provide bypass for the data, and implement the GPRS service.
The original GSM network accomplishes the voice function. The GPRS service is
realized without too many changes to the GSM network. The GPRS system consists of
two network functional entities: GGSN and SGSN. The GGSN functions in a way
similar to the GMSC; the SGSN functions in a way similar to the MSC/VLR.
The GPRS is mainly applied to E-mail service, WWW browsing, WAP service,
e-commerce, information query, and remote monitor.
Benefits
For carriers
This service enables carriers to manage the GSM and GPRS networks through one
HLR, thus saving the investment of carriers.
For subscribers
The GPRS service enables the subscriber to roam in the Internet, send E-mails, browse
the WWW webs, enjoy e-commerce, and conduct remote monitoring. Since the service
charge is based on traffic volume, the subscriber does not need to consider the duration
of enjoying the service and can remain online all the time.
Description
The HLR9820 provides the Gc/Gr interfaces, and supports GPRS attachment,
obtaining routing information, performing authentication, generating authentication
failure reports, short messages function, and tracing/querying messages through
interfaces.
The HLR9820 supports 2G and 2.5G GRRS services. It allows the subscriber to access
GSM or GPRS network, or both of them.
Dependency
The HLR9820 cooperates with the GGSN/SGSN to implement the function in
compliance with standard protocols. There is no special requirement for the
GGSN/SGSN.

Feature Description

Issue 1.0 (2013-02-25)
Page 114 of 177

2.2.2 WHFD-520200 3G GPRS
Availability
Specification
3GPP29002, 3GPP22060, 3GPP23060, and3GPP29061
Summary
Compared with the GSM network, the UMTS network greatly accelerates the data
transmission, thus providing high-speed and more reliable GPRS services.
Benefits
For carriers
This service enables carriers to manage the GPRS and UMTS networks through
one HLR, thus saving the investment of carriers.
For subscribers
This service allows the subscriber to enjoy high-speed GPRS services on the 3G
network.
Description
The HLR9820 provides the Gc/Gr interfaces, and supports GPRS attachment,
obtaining routing information, performing authentication, generating authentication
failure reports, short messages function, and tracing/querying messages through
interfaces.
The HLR9820 supports the 3G GPRS. Compared with the GSM GPRS, the UMTS
GPRS supports the expanded QoS attribute and the PDP accounting attributes, and
provides more powerful and excellent network services.
Dependency
GGSN/SGSN.
2.2.3 WHFD-520300 Enhanced HSPA
Availability
Specification
3GPP24008

Feature Description

Issue 1.0 (2013-02-25)
Page 115 of 177

Summary
The High Speed Downlink Packet Access (HSDPA) achieves the high-speed downlink
data services in the UMTS network. At present, it is favored by carriers to develop
high-traffic mobile media services.
The High Speed Uplink Packet Access (HSUPA) aims to optimize the capacity and
data throughput in the uplink direction and minimize the delay in dedicated channels.
The enhanced HSPA specified in 3GPP defines a new transport channel to provide
high-speed uplink data services.
Benefits
For carriers
This service enables carriers to provide HSPA-based high-speed data services.
For subscribers
This service allows the subscriber to enjoy high-speed uplink/downlink
broadband services.
Description
The HLR manages the subscription data of the HSDPA/HSUPA services, and sends the
subscription data to the SGSN when the subscriber originates for GPRS location
update request.
Dependency
The HLR9820 realizes the function in compliance with the standard protocol, and the
network must support the HSDPA/HSUPA service.
2.2.4 WHFD-520400 Support GPRS Charging Character
Availability
Specification
3GPP29002, 3GPP23060, 3GPP 32215, and 3GPP 32015
Summary
The GPRS Charging Characteristics refer to various charging types that a subscriber
can adopt. Different charging types use different ways to generate the CDR.
Benefits
For carriers
This service enables carriers to apply different CDR generation methods for
different subscribers.

Feature Description

Issue 1.0 (2013-02-25)
Page 116 of 177

For subscribers
This service enables the subscriber to choose the suitable charging service.
Description
The HLR9820 supports the subscription of different charging characteristics, and
sends the subscription information to the SGSN/GGSN. The charging characteristics
supported by the HLR9820 are as follows:
NONE.: disable the setting on charging characteristics
HOT: hot charging, real time charging
FLAT: flat charging
PREPAID: prepaid
NORMAL: ordinary charging
Dependency
GGSN/SGSN.
2.3 WHFD-030000 Supplementary Services
The following introduces the supplementary services of the optional functions,
including:
Call Waiting/Call Hold (CW/CH)
Multi Party (MPTY)
Unstructured Supplementary Service Data (USSD)
Closed User Group (CUG)
2.3.1 WHFD-030400 Call Waiting/Call Hold (CW/CH)
Availability
Specification
Summary
The CW service allows a mobile subscriber in conversation status to establish a call
connection to another incoming call. The call hold service allows a VoBB subscriber to
place an existing active call on hold and answer an incoming call.

Feature Description

Issue 1.0 (2013-02-25)
Page 117 of 177

Benefits
For carriers
This service can enhance the service provisioning capability of carriers, and
attract the more subscribers. Meanwhile, the service can improve call completion
rate, and improve traffic volume.
For subscribers
This service can establish a call connection to a subscriber when the subscriber is
busy. It can improve the satisfaction level of the subscribers, especially high-end
subscribers and business subscribers.
Description
In the case of CW, the network reminds the subscriber of another incoming call, and
requests the subscriber to answer the call. The subscriber can make a decision on
whether to answer the call.
In the case of CH, the subscriber can establish a call connection to the second call, and
switch between the first call and the second call. The first call is in hold-on status.
The CW and CH function are always used together. Therefore, the subscriber must
subscribe to the CW and CH services in the HLR simultaneously. When a subscriber
in conversation needs to receive a new call, the subscriber must support the CW. After
the connection to the new call is established, the subscriber needs to hold the first call
so that he/she can switch between the first call and the second call.
Dependency
2.3.2 WHFD-030500 Multi Party (MPTY)
Availability
Specification
Summary
A subscriber who has subscribed to the service can hold a telephone meeting for
multiple subscribers (including mobile subscribers). The participants of the meeting
can talk with each other. The MPTY service allows up to six subscribers to talk with
each other simultaneously. In MPTY, the controlling subscriber can add a remote
subscriber to the meeting, disconnect a remote subscriber, and isolate a remote
subscriber (the remote subscriber holds on the call with the controlling subscriber, but
cannot talk with other subscribers of the MPTY).

Feature Description

Issue 1.0 (2013-02-25)
Page 118 of 177

Benefits
For carriers:
attract the more subscribers. It provides a simple telephone meeting solution for
the business subscriber.
For subscribers:
This service allows multiple subscribers to talk with each other. This service
allows the business subscriber to hold a simple telephone meeting.
Description
The MPTY enables a subscriber to establish call connections with multiple subscribers.
In other words, the subscriber can talk with three or more subscribers simultaneously.
The MPTY service of Huawei's MSC allows up to 6 subscribers to participate a
meeting.
When a subscriber of the service has to deal with an activated call and a held call and
has answered the two calls, the subscriber can combine the two calls into an MPTY
call through the MPTY service, and then talk with the other two subscribers.
The subscriber of the MPTY service can:
Hold the MPTY call, and resume the MPTY call later on.
Initiate a new call while holding the MPTY call.
Handle an MPTY call and a single call alternatively, or add the single call to the
MPTY call.
Establish a private call connection with a remote subscriber. The call connection
is separated from the meeting.
Disconnect a remote subscriber.
Release the MPTY call.
Enhancement
Before subscribing to the MPTY service, the subscriber must have subscribed to the
CH service.
Dependency
2.3.3 WHFD-030600 Unstructured Supplementary Service
Data (USSD)
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 119 of 177

Specification
3GPP29002 and 3GPP24090
Summary
The USSD service allows a subscriber to input USSD format compliant non-standard
supplementary service operation commands in the MS to initiate service requests to
the network. The USSD service also allows the network to send USSD commands to
the MS to implement a service.
Benefits
For carriers:
This service enables carriers to provide many value-added services, such as
information on stock exchange, lottery, weather forecast, and air freights, thus
attracting more subscribers.
For subscribers:
This service can satisfy the subscriber's requirements for information in many
aspects, such as lottery information and stock exchange.
Description
Compared with the short message service, the USSD service realizes real-time short
message exchange. It is suitable to stock exchange information query.
Currently, the HLR9820 supports the USSD service of version 1 and version 2. The
HLR9820 also sends the required USSD code to other network elements for further
processing.
Dependency
The HLR9820 cooperates with the SCP (or the USSD center) and the VMSC to realize
the function in compliance with standard protocols.
2.3.4 WHFD-030700 Closed User Group (CUG)
Availability
Specification
Summary
A Closed User Group (CUG) can be set up for one or several subscribers with the
identical attributes. Members of the CUG share the same call attributes. The CUG can
be a small group consisting of few members or a large-sized enterprise boasting
thousands of subscribers.

Feature Description

Issue 1.0 (2013-02-25)
Page 120 of 177

Benefits
For carriers
attract the enterprise subscribers.
For subscribers
The subscribers within the CGU can enjoy flexible call rates.
Description
The CUG service allows a subscriber connecting to a PLMN or other networks to set
up a CUG. The incoming/outgoing calls into/from the CUG are subject to restriction. A
subscriber can become the member of one or multiple CUGs. The member of a CUG
can communicate with other members within the CUG, but are generally prohibited
from communicating with subscribers outside the CUG.
The following describes the attributes of the CUG:
CUG index: Allocated by the network, it is intended to identify a CUG, and is
used by the MS.
CUG Interlock Code (IC): It is intended to identify the relationship between
members of the GUG, and is used by the network rather than the MS.
Preferential CUG: When the CUG index is unavailable, the preferential CUG is
used as the default CUG index.
Inter-group incoming call permitted: Subscribers with this attribute are allowed to
receive incoming calls from subscribers outside the CGU.
Inter-group outgoing call permitted: Subscribers with this attribute are allowed to
initiate calls to subscribers outside the CGU.
Intra-group incoming call prohibited: Subscribers with this attribute are
prohibited from receiving incoming calls from other members within the CGU,
but are allowed to initiate calls to other subscribers within the CGU.
Intra-group outgoing call prohibited: Subscribers with this attribute are prohibited
from initiating calls to other subscribers within the CGU, but are allowed to
receive incoming calls from other members within the CGU.
CUG call: It refers to the call initiated by a member of a CUG.
Dependency
The HLR9820 cooperates with the MSC/VLR to realize the function in compliance
2.3.5 WHFD-030900 PLMN Specific Supplementary Services
(PLMNSS)
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 121 of 177

Specification
3GPP29002
Summary
The PLMN Specific Supplementary Services (PMNSS)allow a subscriber to use the
supplementary services defined by carriers. The PLMNSS service includes the hot
billing and Customized Ring Back Tone (CRBT) services.
Benefits
For carriers
This service facilitates carriers to introduce new services, and reduces the service
development cost.
For subscribers
None.
Description
The HLR9820 supports the subscription of the PLMNSS. The value of the PLMNSS
code ranges from 241 to 245. During the location update, the HLR sends the
subscription data of the PLMNSS to the MSC/VLR through standard cell. If carriers
plan to introduce a new service, they only need to define the PLMNSS code of the new
service, and then develop the service on the MSC/VLR.
Enhancement
The HLR9820 can flexibly send the PLMNSS code in the following ways:
The PLMN-SS code is delivered in the ISD procedure.
The PLMN-SS code is delivered with the MSRN in the sending routing
information (SRI) procedure.
The PLMN-SS code is delivered with the MSRN/forward-to number (FTN) in the
SRI procedure.
Dependency
2.4 WHFD-530000 CAMEL Services
The Customized Applications for Mobile network Enhanced Logic (CAMEL) is an
intelligent network solution based on the GSM/WCDMA protocol stack.
The CAMEL provides a mechanism that enables the WCDMA network to provide
services independently from the service network. Carriers can control the self-defined
services outside the service network. The CAMEL is not a new supplementary service,
but must be viewed as a network attribute. Through the mobile network with the

Feature Description

Issue 1.0 (2013-02-25)
Page 122 of 177

CAMEL attribute, carriers can provide self-defined services for the subscriber, even
though the subscriber may be outside the home network.
The development of the CAMEL experiences four phases:
CAMEL phase 1
CAMEL phase 2
CAMEL phase 3
CAMEL phase 4
In the four phases, the CAMEL has different application scopes:
CAMEL phase 1: The CAMEL attribute is applied to services related to MO/MT
calls.
CAMEL phase 2: The CAMEL attribute is applied to services related to the
utilization of supplementation services.
CAMEL Phase 3: The CAMEL attribute is applied in SMS MO, GPRS sessions,
PDP context, HLR subscriber data control, and network signaling traffics.
CAMEL phase 4: The CAMEL attribute is applied in the SMS MT service.
The CAMEL service of higher version encompasses the subscription data of lower
version. The HLR9820 supports the four CAMEL versions.
2.4.1 WHFD-530100 CAMEL Phase 2 Services
Availability
Specification
3GPP29002 and 3GPP23078
Summary
The CAMEL is a network attribute, and is incorporated into the GSM and IN network
entities. When a subscriber of the CAMEL service roams or serves as the callee, the
data of the CAMEL service is transmitted between the HPLMN and the VPLMN to
trigger the IN services of the subscriber.
Benefits
For carriers
The HLR supporting the CAMEL service allows the subscriber to subscribe to
the IN service immediately, and makes IN service configuration more flexible.
The CAMEL service enables carriers to add new services and new attributes
more flexibly and conveniently. Meanwhile, carriers can utilize the attributes of
the exiting IN network (familiarity number, pre-payment, and message station
service), and reduce the subsequent investment in equipment.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 123 of 177

The subscriber can enjoy various IN services provided by the HLR, for example,
familiarity number, message station service, and advice of charge.
Description
The HLR9820 supports the following CAMEL-related functions:
Supports the MAP interface for connection with the gsmSCF function entity.
Supports CAMEL Phase 1 and CAMEL Phase 2.
Supports subscribing to O-CSI, T-CSI, SS-CSI, and TIF-CSI data.
Enables the CAMEL subscriber who has subscribed to the U-CSI/UG-CSI to
interact with the HLR in the USSD mode.
Provides subscription items that specify actions to be taken by the HLR if the
NEs do not support the CAMEL.
The implementation of the CAMEL service necessitates the supports from the network
entities at the side of the IN network, including SSP, SCP, and SCF.
The intelligent subscription items of CAMEL Phase 2 include:
O-CSI (WHFD-530101)
T-CSI (WHFD-530102)
SS-CSI (WHFD-530103)
TIF-CSI (WHFD-530104)
U-CSI (WHFD-530105)
UG-CSI (WHFD-530106)
Dependency
Availability
Specification
3GPP29002 and 3GPP23078
Summary
The HLR9820 supports CAMEL Phase 3 service.
Benefits
For carriers
The CAMEL service enables the subscriber to subscribe to the IN service
immediately. Utilizing the flexible service configuration methods of the IN

Feature Description

Issue 1.0 (2013-02-25)
Page 124 of 177

network, the CAMEL service allows carriers to add new services and new
attributes more flexibly and conveniently. Meanwhile, carriers can utilize the
attributes of the IN network (familiarity number, pre-payment, and message
station service), and reduce the subsequent investment in equipment.
For subscribers
Description
In addition to the attributes of CAMEL Phase 2, CAMEL Phase 3 service supports:
O-CSI (WHFD-530201)
T-CSI (WHFD-530202)
SS-CSI (WHFD-530203)
TIF-CSI (WHFD-530204)
U-CSI (WHFD-530205)
UG-CSI (WHFD-530206)
GPRS-CSI (WHFD-530207)
SMS-CSI (WHFD-530208)
D-CSI (WHFD-530209)
M-CSI (WHFD-530210)
VT-CSI (WHFD-530211)
Dependency
Availability
Specification
3GPP29002 and 3GPP29078
Summary
The HLR9820 support CAMEL Phase 4 service.
Benefits
For carriers
The CAMEL service enables the subscriber to subscribe to the IN service
immediately. Utilizing the flexible service configuration methods of the IN

Feature Description

Issue 1.0 (2013-02-25)
Page 125 of 177

network, the CAMEL service allows carriers to add new services and new
attributes more flexibly and conveniently. Meanwhile, carriers can utilize the
attributes of the IN network (familiarity number, pre-payment, and message
station service), and reduce the subsequent investment in equipment.
For subscribers
Description
In addition to the attributes of CAMEL Phase 3, CAMEL Phase 4 service supports:
MO-SMS-CSI (WHFD-530301)
MT-SMS-CSI (WHFD-530302)
Dependency
2.5 WHFD-540000 Location Services (LCS)
Availability
Specification
3GPP22071, 3GPP23171, 3GPP24030, 3GPP25305, 3GPP25923, and GPP29002
Summary
The LCS service is a GSM standard compliant service. It functions independently
from any basic service.
Benefits
For carriers
With the development of the telecommunication market, the provisioning of the
LCS service is inevitable. Carriers should provide the LCS service as soon as
possible to satisfy the requirements of the market and enhance its service
competitiveness.
For subscribers
The LCS allows a subscriber to know his/her current location, and brings about
great convenience to the daily life.

Feature Description

Issue 1.0 (2013-02-25)
Page 126 of 177

Description
The LCS can provide information on the specific location of a subscriber in term of
channel ID (CID) or latitude and longitude. The SMLC is the functional entity
realizing the LCS service. Different from the GPS, the LCS service capitalizes on the
existing GSM network. Carriers can provide the LCS service by deploying several
LCS functional entities, without too many changes to the network.
The HLR9820 supports subscribing to the LCS service in Universal, Call related,
Non-call related, or PLMN operator mode. The HLR9820 also supports the Lh
interface used for connecting to the GMLC, and provides routing function of the LCS
service.
If the LCS can be realized in the whole network, the LCS subscriber can query the
location information through the mobile IN network or the Internet that supports the
LCS service. If the application of the LCS in the third party is very mature, the
subscriber can know at any time his/her current location, whether a supermarket or
cinema is available in the nearby, and how to get there. The subscriber can also specify
other subscribers so that they can locate the subscriber and know his/her whereabouts.
In short, the LCS will bring about great changes to our daily lives.
Dependency
The HLR9820 cooperates with the GMLC/SMLC/MSC/SGSN to realize the function
in compliance with standard protocols.
2.6 WHFD-050000 Other Services
Other services include:
Call Forwarding Default (CFD) (WHFD-050600)
CFNRy Default Time Medication (WHFD-050800)
Automatic Device Detection (ADD)
2.6.1 WHFD-050600 Call Forwarding Default (CFD)
Availability
Specification
None.
Summary
The HLR9820 provides the CFD service independently, without cooperation with the
MSC/VLR.

Feature Description

Issue 1.0 (2013-02-25)
Page 127 of 177

Benefits
For carriers
After the CFD service is provisioned and activated for a subscriber, every call to
the subscriber can be put through. At least, every call to the subscriber can be
connected to the FTN (such as the voice mail box) specified by the CFD service.
In this way, the call completion rate of the overall network can be improved
substantially. Besides, the CFD service has greatly simplified the call forwarding
service configuration operation. If a subscriber intends to forward all calls to the
same number, the operator can capitalize on the CFD service, and does not have
to configure the FTN for every conditional call forwarding service.
The CFD service enables carriers to provide powerful and flexible call
forwarding function for the subscriber and enhance its competitiveness.
For subscribers
If a subscriber has registered the CFD service, every call to the subscriber can be
put through. At least, every call to the subscriber can be connected to the FTN
(such as the voice mail box) specified by the CFD service.
Description
The CFD is supplementary to the call forwarding services CFB, CFNRy, and CFNRc.
But it is not a standard supplementary service, and has no allocated supplementary
service code. The registration and deregistration of the service can only be performed
by carriers.
If a subscriber's CFD service based on a basic service is activated but the subscriber's
conditional call forwarding service based on the same basic service is not activated,
the call is forwarded to the FTN specified by the CFD service. This mechanism can
ensure that every call to the subscriber can be put through.
Here, the subscriber's conditional call forwarding service is not activated because:
The subscriber has not subscribed to the conditional call forwarding
supplementary service.
The subscriber has not registered the supplementary service.
The subscriber has not activated the supplementary service.
For example, subscriber A has registered and activated the CFD service; the
subscriber's FTN is N1, the number of a voice mail box. The subscriber has not
registered the CFB service. When subscriber A is in conversation status, if subscriber
B initiates a call to subscriber B, the call is forwarded to subscriber A's voice mail box.
Dependency
The CFD service is a special service of the HLR. The interface of the CFD service
complies with standard protocols. There is no special requirement for the MSC/VLR.
2.6.2 WHFD-050800 CFNRy Default Time Modification
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 128 of 177

Specification
None.
Summary
The HLR9820 supports the CFNRy Default Time Modification.
Benefits
For carriers
Carriers can configure the no replay time for the CFNRy service of every
subscriber so that the call forwarding services can be provided for the subscriber
more flexibly.
For subscribers
The subscriber to enjoy a better CFNRy service based on the no replay time of
call forwarding configured by carriers.
Description
When a subscriber activates the CFNRy service, if the subscriber does not select the no
reply time, the system usually provides a default time (30s) for the subscriber's
CFNRy service. When a call remains unanswered for the specified time, the system
triggers the CFNRy service. The HLR9820 provides an interface for modifying the
default time. The default no reply time can be 5s, 10s, 15s, 20s, 25s, or 30s.
Dependency
2.6.3 WHFD-050900 Automatic Device Detection (ADD)
Availability
Specification
3GPP29002
Summary
The HLR9820 provides the ADD function provided that the ADD server is deployed
in the network. 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.

Feature Description

Issue 1.0 (2013-02-25)
Page 129 of 177

Benefits
For carriers
The ADD function simplifies the operations of the subscribers who use the data
services, and thus increases the customer satisfaction.
For subscribers
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.
Description
During the location update of a subscriber, the MSC sends the IMEISV of the
subscriber in the location update request to the HLR. The HLR checks whether the
IMEISV of the subscriber changes. If the IMEISV changes, the HLR sends a message
to the ADD server. The ADD server then sends the related configuration data to the
UE based on the type of the UE. (The ADD server stores and manages the
configuration data of various types of UE, such as the configuration of the MMS and
GRPS. It also allows the configuration data to be automatically sent to the UE.)
When detecting the change of the IMSI, MSISDN, IMEISV, or subscription data such
as the subscriber identity (pre-paid service subscriber or post-paid service subscriber),
the HLR sends the related modification information to the ADD server. The ADD
server then updates the configuration data of the UE through the network.
Dependency
The HLR9820 cooperates with the ADD server to implement the ADD function. In
addition, a proprietary interface, namely the SOAP interface, is required between the
HLR9820 and the ADD server.
2.7 WHFD-060000 Mobility Services
The mobility services include the Subscriber Information Services (WHFD-060500).
Subscriber Information Services consist of:
Any Time Interrogation (WHFD-060501)
Subscriber Information Provision (WHFD-060502)
2.7.1 WHFD-060501 Any Time Interrogation
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 130 of 177

Specification
3GPP29002
Summary
The Any time interrogation is a standard protocol-compliant subscriber information
service.
Benefits
For carriers
This service enables carriers to adopt the call charge rate based on the location to
which a subscriber roams, and boost its competitiveness.
For subscribers
The subscriber can benefit from the call charges.
Description
The SCP can initiate a request for obtaining a subscriber's location information and
status information to the HLR.
Dependency
2.7.2 WHFD-060502 Subscriber Information Provision
Availability
Specification
3GPP29002
Summary
The Subscriber Information Provision service is a standard compliant subscriber
information service.
Benefits
For carriers
This service enables carriers to obtain detailed subscriber's location and status
information to provide more powerful functions. For example, carriers can adopt
the call charge rates based on the cell to which a subscriber roams, and boost its
competitiveness.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 131 of 177

The subscriber can benefit greatly from the call charges or enjoy better network
service.
Description
The HLR can obtain the information on the current cell and the status of the subscriber
from the VLR of the subscriber. The HLR then sends a message with the mentioned
information to the GMSC as the response to its routing information message or sends a
message to the SCP as a response to its Anytime Subscription Interrogation message.
Dependency
2.8 WHFD-090000 Subscriber Data Management
The subscriber data management function involves:
Scheduled Batch Operation Execution (WHFD-090700)
3G Subscriber Data Storage (WHFD-091100)
2.8.1 WHFD-090700 Scheduled Batch Operation Execution
Availability
Specification
None.
Summary
The execution of batch operations has a certain impact on the system performance. To
avoid the impact, the Scheduled Batch Operation Execution service enables the system
to execute the batch operations at the time of low traffic volume automatically.
Benefits
For carriers
Carriers can conduct batch operations more flexibly.
For subscribers
None.
Description
Carriers can perform the batch operations at the time other than peak traffic hours, and
avoid the inconvenience brought about by manual batch operations.

Feature Description

Issue 1.0 (2013-02-25)
Page 132 of 177

Dependency
for other NEs.
2.8.2 WHFD-091100 3G Subscriber Data Storage
Availability
Specification
3GPP29002, 3GPP23008
Summary
The HLR9820 supports storage and identification of 3G subscriber data.
Benefits
For carriers
This service enables carriers to provide diversified customized 3G services.
For subscribers
The subscriber can enjoy the benefits bought about by 3G service.
Description
The HLR9820 stores the subscription data and authentication data of a 3G subscriber
to satisfy the 3G subscriber's requirements for 3G services, such as location updating,
calling, and video conversation.
Dependency
2.9 WHFD-560000 Networking Functions
The networking functions include:
Multi-SP (WHFD-560100)
TDM 2M Signaling Link (WHFD-560200)
MAP phase2+ (WHFD-560500)
SIGTRAN (WHFD-560300)

Feature Description

Issue 1.0 (2013-02-25)
Page 133 of 177

2.9.1 WHFD-560100 Multi-SP
Availability
Specification
None.
Summary
The Multi-SP enables a physical HLR to be configured with multiple signaling points.
It can increase the number of link connections between the HLR and the neighboring
NEs, and enlarge the capacity of the links between the HLR and the neighboring NEs.
Benefits
For carriers
This service enables the HLR to break through the link limitation, and improve its
signaling processing capability, without imposing extra requirements on the peer
end network entity.
For subscribers
None.
Description
Due to the limitations imposed by No. 7 MTP layer protocol, the maximum number of
signaling links between two neighboring signaling points is 16. When the number of
subscribers exceeds a certain level, the 16 links between the HLR and a signaling point
cannot satisfy the requirements for signaling data transmission, causing link
congestion.
The Multi-SP service enables you to configure 16 signaling points in an HLR.
Consequently, the HLR can establish up to 16 16 links with a neighboring signaling
entity without imposing extra requirements on the peer end entity, well satisfying the
requirements for signaling transmission.
Dependency
for other NEs.
2.9.2 WHFD-560200 TDM 2M Signaling Link
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 134 of 177

Specification
None.
Summary
The HLR9820 supports TDM 2 Mbit/s links.
Benefits
For carriers
The application of 2 Mbit/s link in signaling points with large signaling traffics in
between can reduce cost and simplify networking. In addition, if the HLR does
not support the Multi-SP function, it is subject to the limitation of 16 links. If the
sixteen 64 kbit/s links cannot satisfy the traffic volume requirements, the
adoption of 2 Mbit/s links can satisfy the traffic requirements.
For subscribers
None.
Description
With the increase in the HLR's capacity and processing capability, the processing
capacity of a signaling link becomes the bottleneck. The speed of a 2M high-speed
signaling link is 31 time as high as that of a No.7 signaling link, well satisfying the
requirements of mobile service on the HLR links.
Dependency
for other NEs.
2.9.3 WHFD-560500 MAP phase2+
Availability
Specification
3GPP29002
Summary
The HLR9820 supports the MAP phase2+.
Benefits
For carriers
The HLR9820 supports MAP phase2+. As a result, carriers can provide services
that are based on the MAP phase2+, and increase its revenue.
For subscribers

Feature Description

Issue 1.0 (2013-02-25)
Page 135 of 177

The subscriber can enjoy services that are based on MAP phase2+.
Description
MAP phase2+ is supplementary to the MAP protocol. It is intended to satisfy the
requirements for GSM supplementary services and telecommunication services.
MAP phase2+ supports CSI-triggered IN services (including CAMEL phase1 and
CAMEL phase2), regardless of voice service or data service.
MAP phase2+ also helps to realize the LCS service.
Dependency
2.9.4 WHFD-560300 SIGTRAN
Availability
Specification
None.
Summary
The HLR9820 supports the SIGTRAN, namely IP networking.
Benefits
For carriers
The HLR9820 supports independent IP networking and can help carriers to save
investment in SG construction. The HLR9820 can satisfy the diversified
networking requirements. The types of signaling bearers between the HLR and
other NEs can be TDM and IP. The signaling type is not subject to the limitation
of the physical bearer type, and can be selected flexibly.
For subscribers
None.
Description
The HLR9820 provides the M3UA adaptation function to realize the conversion
between MTP3/MTP2 based TDM bearer and SCTP/IP based IP bearer for the MAP
signaling. The M3UA is the adaptation layer of MTP3. It adapts MTP3 subscriber
messages to the SCTP layer for transmission over IP bearer. The M3UA layer must
support MTP3 signaling point management and MTP routing management. Therefore,
to realize the SG function through the M3UA, the SG must support MTP signaling
point encoding.

Feature Description

Issue 1.0 (2013-02-25)
Page 136 of 177

Note:
The SIGTRAN service does not include the M2UA function.
Dependency
for other NEs. If the peer end adopts TDM for bearing No. 7 signaling, a signaling
gateway must be adopted for signaling conversion.
2.9.5 WHFD-560600 SCTP multi-homing
Availability
Specification
RFC2960
Summary
In IP networking, the HLR9820 provides the SCTP multi-homing function, which
improves the reliability of the IP network.
Benefits
For carriers
The reliability of the IP network is improved.
For subscribers
None.
Description
In IP networking, the HLR9820 provides the SCTP multi-homing function, which
allows multiple source addresses and destination addresses to be configured for an IP
link. The source addresses can be configured on the same board or on different boards.
Thus, multiple logical links and physical paths are established. The source addresses
and destination addresses are assigned different connection priorities and belong to
different network segments, and different network equipment can be connected to an
SCTP association. Thus, single-point failure is eliminated from the IP links through the
SCTP associations, and the reliability of the IP network is improved.
Dependency
The HLR9820 implements the SCTP multi-homing function in compliance with
standard protocols. The implementation of the SCTP multi-homing function, however,
requires the cooperation of the MSC/VLR. There is no special requirement for the
MSC/VLR.

Feature Description

Issue 1.0 (2013-02-25)
Page 137 of 177

2.10 WHFD-570000 Enhanced Functions
The enhanced functions include: some special services, such as multi-MSISDN
function, hot billing, voice ring back tone service, and voice broadcast service.
2.10.1 WHFD-570100 VLR Regional Roaming Restriction
Availability
Specification
None.
Summary
The VLR Regional Roaming Restriction service is based on VLR/SGSN roaming list.
Every subscriber has his/her own VLR/SGSN roaming list.
Benefits
For carriers
This service enables carriers to provide local communication network service for
the subscribers or provide roaming restriction services for the subscribers
individually, thus improving its competitiveness.
For subscribers
The subscriber who has subscribed to the service can enjoy relatively low charge
rate and save the expense. If carriers provide the roaming restriction service for a
subscriber, the subscriber can specify the roaming area for himself/herself.
Description
The VLR Regional Roaming Restriction service enables carriers to provide various
roaming restriction services flexibly. Without deploying any extra network equipment,
carriers can restrict the subscriber's roaming to some specified VLR or present the
subscriber from roaming to some specified VLR through the subscriber roaming
restriction template in the HLR.
The VLR Regional Roaming Restriction service supports template-based
configuration. In the HLR, carriers can specify some VLR numbers, and compile a
roaming restriction template based these VLR numbers. When subscribing to the VLR
Regional Roaming Restriction service, the subscriber only needs to reference the
template. This method can greatly improve the working efficiency of carriers.
The VLR Regional Roaming Restriction service is widely applied in local
communication services. Carriers apply a subscriber roaming restriction template
based on all local VLR numbers. When a subscriber subscribes to the service based on
the template, the subscriber can only roam and access the network locally (for example,
a region, province, or city).

Feature Description

Issue 1.0 (2013-02-25)
Page 138 of 177

To provide the VLR Regional Roaming Restriction service, carriers must configure a
VLR/SGSN roaming list for every subscriber. The list describes the roaming rules (for
example, whether roaming is allowed) and the default roaming rule.
When a subscriber's location in CS domain or PS domain is updated, the VLR/SGSN
initiates a location update request to the HLR. The HLR then checks the subscriber's
VLR/SGSN roaming list. If the number of the VLR/SGSN matches a record in the
VLR/SGSN roaming list, the HLR decides whether the subscriber is allowed to roam
in the area according to the specified roaming rule. If the number of the VLR/SGSN
matches no record in the VLR/SGSN roaming list, the HLR uses the default roaming
rule to decide whether the subscriber is allowed to roam in the area.
Dependency
for other NEs.
2.10.2 WHFD-570700 CAMEL Restriction
Availability
Specification
None.
Summary
The CAMEL Restriction service is a special service provided by the HLR9820.
Sometimes, when the HLR sends CAMEL data to the MSC/SGSN, the MSC/SGSN
does not support the CAMEL data due to its poor compatibility. Consequently, the
location update flow or the send routing information (SRI) flow fails, and the
subscriber cannot access the network or serve as the callee. To improve the network
compatibility of the HLR, the CAMEL Restriction service allows you to configure a
switch. When the switch is turned on, it can prevent the HLR from sending some
specified CAMEL data to the MSC/SGSN.
Benefits
For carriers
This service enables carriers to configure the subscriber-based CAMEL
processing capability in the HLR. Carriers can provide more customized CAMEL
services for the subscriber, and enhance its competitiveness.
For subscribers
None.
Description
The HLR9820 supports the CAMEL Restriction service. Carriers can configure the
service in the HLR to control whether it should send CAMEL data in a flow.

Feature Description

Issue 1.0 (2013-02-25)
Page 139 of 177

The following lists the major CAMEL restriction solutions:
Selective Bypass:
This is a CAMEL-based selective bypass solution. When the callee passes the
selective bypass authentication, the HLR does include the T-CSI information of
the subscriber's PPS service into the response messages of the SRI request.
SMS-CSI data insertion restriction:
The HLR decides whether to send the SMS-CSI data according to the
VLR/SGSN to which the PPS subscriber roams. For example, if the subscriber
roams to the country that has not signed the CAMEL roaming agreement, the
HLR does not send the SMS-CSI to the subscriber. As a result, the subscriber
cannot send short messages.
VLR-based outgoing call restriction:
The HLR decides whether to send the outgoing call restriction data to the
subscriber according to the VLR to which the PPS subscriber roams. For example,
if the subscriber roams to the country that has not signed the CAMEL roaming
agreement, the subscriber is prohibited to make outgoing calls.
Subscriber-oriented CAMEL service customization
When a subscriber roams outside the local network, the HLR decides whether to
send the O-CSI and TCSI data to the subscriber according to the network
compatibility and the CAMEL agreement signed between carriers. For example,
according to the basic service keys, carriers can specify that:
The CAMEL logic is triggered only when the subscriber roams to the
specified areas.
Whether the subscriber is allowed to access the network after the subscriber
roams to the areas where the CAMEL is not supported.
Whether a call is allowed when the network of the caller does not support the
CAMEL.
Dependency
for other NEs.
2.10.3 WHFD-570701 TCSI Suppression Enhancement
Availability
Specification
None.
Summary
The HLR9820 supports the TCSI Suppression Enhancement function. Carriers can
configure the service to decide whether the HLR should send the subscriber TCSI
data.

Feature Description

Issue 1.0 (2013-02-25)
Page 140 of 177

Benefits
For carriers
This service enables carriers to configure the subscriber-based CAMEL
processing schemes in the HLR. Carriers can provide more customized CAMEL
services, and enhance its competitiveness.
For subscribers
None.
Description
The HLR9820 supports T-CSI suppression. When a subscriber serves as the callee, the
HLR checks whether the subscriber roams under the local VLR. If yes, the response
message of the SRI message does not contain the T-CSI flag; if not, the returned
response message of the SRI message contains the T-CSI flag.
Dependency
for other NEs.
2.10.4 WHFD-570900 Multi-MSISDN
Availability
Specification
3GPP29002
Summary
The HLR9820 allows an IMSI subscriber to subscribe to multiple MSISDN numbers.
Benefits
For carriers
This service enables carriers to attract more subscribers and improve its market.
For subscribers
The subscriber of the service can use different MSISDN numbers for different
services.
Description
The HLR9820 allows a subscriber to subscribe to multiple MSISDN numbers. A
subscriber holding a SIM card can have multiple MSISDN numbers, with each
MSISDN number corresponding to different default basic services (for example,
telephone service, FAX service and other data service respectively).

Feature Description

Issue 1.0 (2013-02-25)
Page 141 of 177

When the subscriber uses the FAX service and data service, the FAX service or data
service initiated by the PSTN network does not contain the bearer capability
information. If the subscriber has only one MSISDN number, the HLR cannot know
whether the service initiated by the PSTN is a voice call or data call. Through the
Multi-MSISDN service, the HLR can specify three numbers for the subscriber's voice
service, FAX service, and data service respectively. When the PSTN dials a number,
the HLR can know the call is of FAX service or data service.
Dependency
The HLR9820 realizes the function in compliance with the standard protocol and must
2.10.5 WHFD-571300 Multi-OP
Availability
Specification
None.
Summary
Operator Variant Algorithm Configuration Field (OP) is a parameter of the
authentication calculation involving the MILENAGE authentication algorithm. All
subscribers of a carrier use the same OP to distinguish themselves from subscribers of
other carriers. Currently, the HLR9820 supports allocating multiple OPs for a carrier.
Benefits
For carriers
This service allows different USIM cards to use different OPs, greatly enhancing
the security of the system.
For subscribers
Every subscriber can have his/her own OP. Consequently, the security of the
USIM card is further improved.
Description
OP is a parameter of the UMTS authentication. Through the parameter, carriers can
configure UMTIS authentication algorithms. The OP is stored in the HLR/AuC and
the USIM card. The HLR9820 supports multiple OPs. Different USIM cards under an
HLR can use different OPs.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 142 of 177

2.10.6 WHFD-571700 Hot Billing
Availability
Specification
None.
Summary
The HLR9820 provides the Hot Billing service for the subscriber. This service belongs
to carriers's self-defined supplementary service.
Benefits
For carriers
Carriers can provide real-time billing service for the subscriber, for example,
telephone lease service.
For subscribers
The subscriber can obtain the call bill in real time. The subscriber can enjoy
real-time billing services.
Description
If the subscriber has subscribed to the Hot Billing service, the MSC sends the original
call bill to the iGWB. The iGWB allocates a separate channel for the final call bill, and
sends the bill to the billing center in real time.
Dependency
This service is of non-standard service. The HLR9820 must cooperate with Huawei's
MSC/VLR.
2.10.7 WHFD-571800 Alternative Line Service (ALS)
Availability
Specification
3GPP29002
Summary
The ALS service allows a subscriber holding one MS and one SIM card to have two
MSISDN numbers. The billing for the two numbers is carried out separately.

Feature Description

Issue 1.0 (2013-02-25)
Page 143 of 177

Benefits
For carriers
This service can attract more subscribers for carriers and improve the
competitiveness of carriers.
For subscribers
The subscriber of the ALS service can apply for two lines and two numbers, and
use them to make both business calls and private calls separately. The subscriber
only needs to prepare for one card, and the billing for the business calls and
private calls is made separately.
Description
The subscriber of the ALS service can make both business calls and private calls
through one MS and one SIM card. The billing for the business calls and private calls
is made separately. The subscriber does not have to prepare for two SIM cards to make
business calls and private calls separately or use one SIM card to make both business
calls and private calls.
The provisioning of the ALS service requires the support from the MSC/VLR.
Meanwhile, the MS must support configuring line 1 and line 2.
The MSISDN numbers of the ALS service possess the following attributes:
The two numbers correspond to line 1 and line 2 of the MS. When the subscriber
initiates a call through a different line, the caller ID displayed in the callee's
terminal is also different.
The ALS service supports activating supplementary services, including call
barring services, call forwarding services, and call wait service for line 2
separately.
The number of line 2 can only receive short messages. It does not support
initiating a short message or performing the USSD operation.
Dependency
This service is non-standard. The HLR9820 must cooperate with the MSC/VLR to
achieve this service.
2.10.8 WHFD-572000 HLR-Specific Roaming Restriction
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 144 of 177

Summary
The HLR-Specific Roaming Restriction is based on VLR/SGSN roaming list. Once
being configured, the VLR/SGSN roaming list is effective to all subscribers.
Benefits
For carriers
The HLR-Specific Roaming Restriction service is of HLR level, and is effective
to all subscribers. It provides a flexible roaming restriction function for carriers.
For subscribers
None.
Description
The HLR-Specific Roaming Restriction service configures a VLR/SGSN roaming list for
the HLR. Meanwhile, the list contains a roaming rule (whether roaming is allowed)
and a default roaming rule.
When the VLR/SGSN initiates a location update request, the HLR queries the
VLR/SGSN roaming list, and checks whether the VLR/SGSN number matches a
record in the VLR/SGSN roaming list. If yes, the HLR applies the roaming rule to
decide whether the subscriber is allowed to roam. If not, apply the default rule to
decide whether the subscriber is allowed to roam. The roaming restriction in the
VLR/SGSN roaming list is effective to all subscribers under the HLR.
Dependency
for other NEs.
2.10.9 WHFD-572100 SMC Address Filtering
Availability
Specification
None.
Summary
The HLR9820 supports filtering messages from the short message center according to
an address list.
Benefits
For carriers

Feature Description

Issue 1.0 (2013-02-25)
Page 145 of 177

This service can avoid malicious attacks through short messages and alleviate the
payload of the HLR and the network
For subscribers
None.
Description
You can configure an address list in the HLR9820. The HLR9820 can apply the
address list to shield short messages from the short message center. This mechanism
can avoid malicious attacks, and alleviate the payload of the HLR and the network.
Dependency
for other NEs.
2.10.10 WHFD-572101 SCP Address Filtering
Availability
Specification
None.
Summary
The HLR9820 supports the SCP address filtering function.
Benefits
For carriers
This service can avoid malicious attacks through short messages and alleviate the
payload of the HLR and the network.
For subscribers
None.
Description
You can configure an SCP address list in the HLR9820. The HLR9820 can apply the
address list to shield short messages from the SCP. This mechanism can avoid
malicious attacks, and alleviate the payload of the HLR and the network.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 146 of 177

2.10.11 WHFD-572200 CF-Specific Black and White Lists
Availability
Specification
None.
Summary
The CF-Specific Black and White Lists service enables the HLR to control the
subscriber's registration of the call forwarding service. This service is effective to all
subscribers. You can configure call forwarding rules for the specified FTNs in the
HLR. Through the configuration, the HLR can control whether a subscriber can
register the FTNs.
Benefits
For carriers
This service enables carriers to manage the subscriber's call forwarding more
flexibly, and prevent the registration of illegal numbers.
For subscribers
This service prevents the subscriber from incurring financial loss resulting from
registration of illegal FTNs.
Description
The CF-Specific Black and White Lists are effective to all subscribers. Carriers can
compile FTN segments (including the start FTN and the end FTN) according to the
actual circumstances, and configure the call forwarding rule and the default call
forwarding rule based on the number segments. When the FTNs registered by a
subscriber are within the number segments, the HLR adopts the call forwarding rule. If
not, the HLR applies the default call forwarding rule. If the call forwarding rule or the
default call forwarding rule prohibits the registration of the FTNs, the registration
fails.
Dependency
for other NEs.
2.10.12 WHFD-572300 Network Capability Configuration
(NCC)
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 147 of 177

Specification
None.
Summary
The NCC service allows you to configure the capabilities sets for the services and
MAP operations supported by the VLR, so that the HLR can process services and
MAP flows according to the capability sets, improving the network compatibility.
Benefits
For carriers
This service can improve the HLR's compatibility with the surrounding NEs,
increase the HLR's MAP operation success rate and efficiency, satisfy carriers's
customized network compatibility requirements and facilitate carriers's network
deployment.
For subscribers
None.
Description
The NCC service is based on the NCC template and the VLR/SGSN type. It
establishes mappings between the NCC templates and the VLR/SGSN numbers in the
VLR/SGSN Type table. The following offers the detailed description of the service:
Processing of special services by the HLR
Some services, such as MPTY and PLMNSS, are only supported by some VLRs.
If the HLR intends to send the data of these special services to the VLR in the
location update flow and subscriber data insertion flow, the HLR queries the VLR
Type table according to the VLR number, and obtains the corresponding NCC
template. The HLR then processes the services according to the methods
specified in the template.
Processing of the VLR Type table by the HLR
In the CS domain, the HLR and the VLR support different MAP Phases. When
performing MAP operations such as location update and subscriber data insertion,
the HLR first queries the VLR Type table according to the VLR number to obtain
the NCC template and obtain the MAP Phase supported by the VLR. Next, the
HLR processes data as follows:
If the HLR receives the MAP messages initiated by the VLR and the version
value of the MAP Phase in the request is higher than that in the template, the
HLR performs version negotiation.
If the HLR initiates the MAP message, the HLR performs the MAP operations
according to the MAP Phase supported by the VLR in the NCC template, and
avoid version negotiation to reduce waste in link resources caused by version
negotiation.
Processing the SGSN Type table by the HLR
In the PS domain, the HLR and the SGSN support different MAP Phases. When
performing MAP operations such as location update and subscriber data insertion,
the HLR first queries the SGSN Type table according to the SGSN number to

Feature Description

Issue 1.0 (2013-02-25)
Page 148 of 177

obtain the NCC template and obtain the MAP Phase supported by the SGSN.
Next, the HLR processes data as follows:
If the HLR receives the MAP messages initiated by the SGSN and the version
value of the MAP Phase in the request is higher than that in the template, the
HLR performs version negotiation.
If the HLR initiates the MAP message, the HLR performs the MAP operations
according to the MAP Phase supported by the SGSN in the NCC template,
and avoid version negotiation to reduce waste in link resources caused by
version negotiation.
The HLR's processing when a VLR number matches no record in the VLR Type
table
In the CS domain, not all VLR numbers match records in the VLR Type table.
Sometimes, the HLR cannot find a record in the VLR Type table to match a VLR
number. In this case, the HLR is not compatible with the VLR. Therefore, the
HLR needs to use the VLR's default NCC template. When the HLR cannot find
an NCC template because the VLR number matches no record in the VLR Type
table, the HLR processes the services and MAP flow according to the default
NCC template.
The processing by the HLR when an SGSN number matches no record in the
SGSN Type table
In the PS domain, not all SGSN numbers are included into the SGSN Type table.
Sometimes, the HLR cannot find a record in the SGSN Type table to match an
SGSN number. In this case, the HLR cannot conduct network compatibility
processing. Therefore, the HLR needs to use the default NCC template. When the
HLR cannot find an NCC template because the SGSN number matches no record
in the SGSN Type table, and the HLR processes the services and MAP flow
according to the default NCC template.
Dependency
for other NEs.
2.10.13 WHFD-572400 Ring Back Tone
Availability
Specification
None.
Summary
Through the RBT service, the subscriber can subscribe to personalized coloring ring
back tone to replace the traditional ring back tone. When a subscriber initiates a call to
another subscriber, the subscriber as the caller can hear the ring back tone subscribed
by the callee. The ring back tone can be either a piece of music, advertisement, or
recorded speech.

Feature Description

Issue 1.0 (2013-02-25)
Page 149 of 177

Benefits
For carriers
This service can provide extra revenue for carriers and improve the subscriber's
satisfaction level.
For subscribers
The subscriber of the service can modify his/her own personalized ring back tone,
and enable the callee to enjoy brilliant music or personalized tone.
Description
The Ring Back Tone service, or personalized ring back tone service, is a piece of
music or a greeting subscribed by the callee for the caller in replacement of a common
ring back tone.
After a subscriber has subscribed to the Ring Back Tone service, he/she can configure
the coloring ring back tone through WWW, WAP, and access code. When a subscriber
serves as the callee and is idle, the HLR can play a piece of music, DIY announcement,
or video according to the calling number, home area of the callee, and the time
specified by the callee in replacement of the common ring back tone for the caller.
Dependency
This service is of non-standard service. The HLR9820 must cooperate with the
MSC/VLR.
2.10.14 WHFD-573000 Local Mobile Station Identity (LMSI)
Availability
Specification
None.
Summary
The HLR9820 supports the LMSI service. This service is designed especially for some
special areas. Some services are provisioned in cooperation with the satellite mobile
telecommunication system. The HLR9820 provides the LMSI function to facilitate the
provisioning of these services.
Benefits
For carriers
This service enables carriers to provide services in special areas under the help of
the satellite mobile telecommunication system, enlarge the service coverage, and
enhance its competitiveness.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 150 of 177

Description
The following describes the basic processing flow of the function:
The HLR transfers Location Area Code (LAC) over the LMSI cells.
In the location update flow, the VLR sends the subscriber's LAC to the HLR.
The HLR stores the received LMSI cells without any processing.
When the HLR initiates the PRN request, it sends the LMSI cells to the VLR.
Through the function of the HLR, carriers can provide services in some special areas
under the help of the satellite mobile telecommunication system.
Dependency
This service is of a non-standard service. The HLR9820 must cooperate with the
MSC/VLR to realize the service.
2.10.15 WHFD-573100 Zone Code
Availability
Specification
3GPP29002
Summary
The HLR9820 allows the subscriber to subscribe to the Zone Code service. Through
the service, the MSC/SGSN can restrict the roaming of a subscriber to the cell level.
Benefits
For carriers
This service enables carriers to provide local communication network service for
the subscribers or provide roaming restriction services for the subscribers
individually, thus improving its competitiveness.
For subscribers
The subscriber who has subscribed to the service can enjoy relatively low charge
rate and save the expense. If carriers provide the roaming restriction service for a
subscriber, the subscriber can specify the roaming area for himself/herself.
Description
The Zone Code service is a flexible subscriber's roaming restriction service. Compared
with the VLR Regional Roaming Restriction service, the Zone Code service can
restrict the roaming of a subscriber to a smaller area, the roaming area defined by
carriers through the Zone Code service. A roaming area can have up to 10 zone codes.

Feature Description

Issue 1.0 (2013-02-25)
Page 151 of 177

When the subscriber subscribes to the Zone Code service, if the CC and NDC of the
subscriber's VLR/SGSN is included into the subscription data, the HLR sends the zone
code list to the subscriber's VLR/SGSN. After receiving the zone code list, the
VLR/SGSN can control the subscriber's roaming according to the zone code of the
area where the subscriber is located. If the zone code of the area where the subscriber
is located is not included in the zone code list, the VLR/SGSN prevents the subscriber
from roaming further.
Dependency
The HLR9820 cooperates with the MSC/VLR/SGSN to realize the function in
MSC/VLR/SGSN.
2.10.16 WHFD-573200 Access Restriction Data (ARD)
Availability
Specification
3GPP29002
Summary
The ARD service enables carriers to restrict the GSM subscriber's accessing the
UMTS network.
Benefits
For carriers
This service enables carriers to control 2G subscribers' access to the UMTS
network, and reasonably arrange and open the network resources for the
subscribers.
For subscribers
This service enables the subscriber to access the desired wireless network.
Description
The HLR9820 supports inserting the access restriction flag into the expended MAP
ISD transmitted between the HLR and the VLR/SGSN. When receiving the ISD, the
VLR/SGSN decides whether it should permit the subscriber's login request according
to the related software configuration and the subscriber's wireless access system. If the
VLR/SGSN rejects the subscriber's login request, it returns a message with the value
of the cause. Carriers can configure the value of the cause flexibly. For example, a
subscriber has subscribed to the ARD service in the HLR. The ARD service supports
the attribute GREANAllowed/UTRANNOTAllowed. Provided that the local
MSFTX3000 supports the ARD service, when the subscriber exits the 3G UTRAN and

Feature Description

Issue 1.0 (2013-02-25)
Page 152 of 177

logs in to the local network, the location update fails due to access restriction.
Consequently, 2G subscriber's access to the 3G network is under control.
Dependency
2.10.17 WHFD-573300 CS Allocation/Retention Priority
(CARP)
Availability
Specification
3GPP29002
Summary
The CARP service enables carriers to configure the priority of a subscriber at the time
of network congestion. The CARP service is effective to the subscribers in the CS
domain only.
Benefits
For carriers
This service enables carriers to allocate different priorities to different subscribers
and provide voice service of different QoS for these subscribers accordingly. This
service also enables carriers to provide QoS solutions for the subscribers flexibly.
When the network is congested, carriers can provide excellent voice service
(short call connection setup time, high voice quality, and high call completion
rate) for the high-end subscribers. The low-end subscriber's line may be occupied
or the voice encoding rate of the line is decreased for attracting more high-end
subscribers.
For subscribers
This service ensures that the high-end subscriber can enjoy better voice and data
services.
Description
The CARP service divides the subscriber's priorities into three levels: high (category-1
subscriber), medium (category-2 subscriber), and low (category-3 subscriber). Carriers
can configure the priorities of a subscriber in the access process and the service
provisioning process respectively.
In the HLR, you can add and manage the subscriber's CARP data. The HLR sends the
subscriber's CARP data to the subscriber's VLR. When the subscriber establishes a call
connection for a call, the VLR sends the CARP data to the RNC. The RNC provides
differentiated service for the subscriber according to the subscriber's CARP priority.

Feature Description

Issue 1.0 (2013-02-25)
Page 153 of 177

Dependency
2.10.18 WHFD-573301 PS Allocation/Retention Priority (ARP)
Availability
Specification
3GPP29002
Summary
The ARP service enables carriers to configure the priority of a subscriber at the time of
GPRS network resource congestion. The CARP service is effective to the subscribers
in the PS domain only.
Benefits
For carriers
This service enables carriers to allocate different priorities to different subscribers
and provide voice service of different QoS for these subscribers accordingly. This
service also enables carriers to provide QoS solutions for the subscribers flexibly.
When the network is congested, carriers can provide excellent voice service
(short call connection setup time, high voice quality, and high call completion
rate) for the high-end subscribers. The low-end subscriber's line may be occupied
or the voice encoding rate of the line is decreased for attracting more high-end
subscribers.
For subscribers
This service ensures that the high-end subscriber can enjoy better voice and data
services.
Description
The ARP service divides the subscriber's priorities into three levels: high (category-1
subscriber), medium (category-2 subscriber), and low (category-3 subscriber). Carriers
can configure the priorities of a subscriber in the access process and service
provisioning process respectively.
In the HLR, you can add and manage the subscriber's ARP data. The HLR sends the
subscriber's ARP data to the subscriber's SGSN. When the subscriber establishes a call
connection for a call, the SGSN sends the ARP data to the RNC. The RNC provides
differentiated service for the subscriber according to the subscriber's ARP priority.

Feature Description

Issue 1.0 (2013-02-25)
Page 154 of 177

Dependency
The HLR9820 cooperates with the SGSN/GGSN to implement the function in
SGSN/GGSN.
2.10.19 WHFD-574000 Global Tracing
Availability
Specification
3GPP29002
Summary
To remove faults in the increasingly-complex telecommunication network, you need to
figure out where the problem is found first. The next task is to analyze the root of the
problem and remove the faults. The SOR function is to trace and collect information
on the specified subscriber at minimum consumption of system resources. Through the
service, the maintenance personnel can pinpoint a problem to a specific NE, analyze
the cause of the problem, and remove the fault.
Benefits
For carriers
This service enables the maintenance personnel to pinpoint a fault in a network to
a specific NE, and then remove the fault. Carriers can improve the fault handling
efficiency.
For subscribers
None.
Description
The Global Tracing service enables the network to trace the network entities at the
occurrence of some special events and obtain the call related information. Refer to
GSM 12.08 protocol.
The HLR9820 supports the Global Tracing service. As a part of the end-to-end tracing
solution, the HLR supports the CS domain-based tracing function. The HLR instructs
the MSC/VLR of a subscriber to trace the subscriber. The MSC records the
information on the actions of the traced subscriber (such as location update, MS
power-on/off, originating/terminating a call, and originating /terminating a short
message) in a tracing file, and stores the file in the daemon. If necessary, the
maintenance personnel can read the file to locate faults.
Dependency

Feature Description

Issue 1.0 (2013-02-25)
Page 155 of 177

2.10.20 WHFD-574200 Service Change and UDI Fallback
Function
Availability
Specification
3GPP23172 and 3GPP23018
Summary
The HLR9820 supports the Service Change and UDI Fallback Function service.
Benefits
For carriers
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.
For subscribers
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.
Description
The HLR9820 complies with the 3GPP 23.172 and 23.018 protocols. The HLR also
supports the multimedia fallback function. When a subscriber initiates a multimedia
call, the network automatically turns the call into a common call on the following
occasions:
The callee's MS does not support the VP call.
The callee is unwilling to receive the call in VP mode.
The callee has not subscribed to the VP service.
The callee has roamed to the GSM network.
During the VP call process, the caller or callee is switched to the GSM network.
Dependency

Feature Description

Issue 1.0 (2013-02-25)
Page 156 of 177

2.10.21 WHFD-574500 CLIP by HLR
Availability
Specification
None.
Summary
This service enables the HLR to realize the CLIP function by carrying the calling
number in the MAP layer of the obtaining roam number request message.
Benefits
For carriers
This service enables the network to realize the CLIP service when the MSC of the
caller cannot send the calling number to the MSC of the callee directly.
For subscribers
None.
Description
The CLIP service enables the network to display the calling number in the MS of the
callee. For example, subscriber A has subscribed to the service. When subscriber B
initiates a call to subscriber A, subscriber A's MS rings and displays subscriber B's
telephone number.
In the implementation of the function, the HLR sends the calling number to the MSC
of the callee, and the MSC of the callee then sends the calling number to the callee.
The following describes the specific flow:
The GMSC carriers the calling number in the SRI request message.
HLR sends the PRN request with the calling number in private coding
Dependency
This service is of non-standard service. The HLR9820 must cooperate with the
MSC/VLR to realize the service.
2.10.22 WHFD-574800 USSD Barring
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 157 of 177

Summary
The HLR9820 supports barring the USSD operations.
Benefits
For carriers
This service enhances carriers's control over the subscriber's behaviors, and
ensures the interests of carriers.
For subscribers
None.
Description
The HLR9820 enables carriers to control whether to bar the subscriber's USSD
operations through the global configuration. For example, a subscriber has subscribed
to a self-defined supplementary service with the service code of PLMN-SS-1. If
carriers intends to bar the USSD operation for the service, it only needs to set the
USSD baring parameter to PLMN-SS-1 in the global configuration. Currently, the
HLR supports barring the USSD operations for 15 self-defined supplementary services,
ranging from PLMN-SS-1 to PLMN-SS-F.
Enhancement
For example, carriers provide the coloring ring back tone service, allowing the
subscriber to activate the coloring ring back tone service from the MS. The
subscriber's activation of the coloring ring back tone service in the MS is a USSD
operation.
Dependency
for other NEs.
2.10.23 WHFD-574900 2G/3G QoS Mapping
Availability
Specification
None.
Summary
The HLR9820 supports the 2G/3G QoS mapping.
Benefits
For carriers

Feature Description

Issue 1.0 (2013-02-25)
Page 158 of 177

This service enhances the network's compatibility.
For subscribers
None.
Description
In the GPRS location update flow, if the SGSN carries the GPRS enhancement flag in
its message, it means that the SGSN supports the 3G QoS service. In this case, the
HLR sends the GPRS QoS data to the SGSN directly. If the SGSN does not carry the
GPRS enhancement flag in its message, the HLR maps the GPRS QoS data into 2G
data to the SGSN.
Dependency
for other NEs.
2.10.24 WHFD-575000 Multi-SIM
Availability
Specification
None.
Summary
The HLR9820 supports the multi-SIM service.
Benefits
For carriers
This service attracts the subscribers and strengthens the competitiveness of
carriers in the market.
For subscribers
This service allows the subscriber to associate an MSISDN with multiple SIM or
USIM cards.
Description
The multi-SIM service allows an MSISDN to be associated with a maximum of nine
SIM or USIM cards. All the SIM or USIM cards associated with the same MSISDN
have the same service subscription data but different authentication data and dynamic
data. In addition, all the SIM or USIM cards can be used to originate or receive calls.
One SIM or USIM card can be used to receive short messages. Subscribers can change
the initial settings of the call sequence through USSD operations.
The multi-SIM service can be implemented with the following solutions:

Feature Description

Issue 1.0 (2013-02-25)
Page 159 of 177

One live solution
This solution allows the location information about only one of the nine SIM or
USIM cards to be stored in the HLR, at the same time. In this case, if a multi-SIM
subscriber is called, the call is connected to this SIM or USIM card directly
regardless of its connection sequence.
Main/auxiliary card solution
In this solution, if a multi-SIM subscriber is called, the call is only connected to
the SIM or USIM card that has the highest connection sequence.
Simultaneous ringing solution
In this solution, if a multi-SIM subscriber is called, all the MSs with the same
MSISDN are alerted simultaneously, and the subscriber who firstly answers the
call can communicate with the calling subscriber.
Orderly ringing solution
In this solution, if a multi-IMSI subscriber is called, the MSs with the same
MSISDN are orderly alerted based on the connection sequences. The call is
connected to the IMSIs based on the connection sequence until it is answered by
a subscriber.
Dependency
The one live solution and the main/auxiliary card solution are achieved by the
HLR9820 and have no requirement for other NEs. The simultaneous ringing solution
and orderly ringing solution require the cooperation of the MSC/VLR.
2.10.25 WHFD-575100 Dial Identification Code
Availability
Specification
None.
Summary
The HLR9820 supports the DIC function.
Benefits
For carriers
This function attracts the subscribers and strengthens the competitiveness of
For subscribers
This function allows subscribers to know the call cost on a type of callees.

Feature Description

Issue 1.0 (2013-02-25)
Page 160 of 177

Description
The dialing identification code (DIC) function allows the subscriber to know the call
cost on a type of callees. The callees can be categorized as family members,
colleagues and classmates, etc.
When the DIC subscriber originates a call, the subscriber dials the called number + # +
dialing identification code. The dialing identification code can be flexibly defined by
the subscriber. Thus, the call cost lists in the CDR can be summarized based on the
dialing identification code.
Dependency
The DIC function is a non-standard service and requires the cooperation of the Huawei
MSC/VLR.
2.10.26 WHFD-575400Multimedia RBT
Availability
Specification
None.
Summary
The HLR9820 supports the multimedia RBT service.
Benefits
For carriers
For subscribers
This service allows the subscriber to change their multimedia RBT flexibly, so
that the callers can enjoy personalized video/audio services.
Description
The 3G network supports the high-speed multimedia services. The multimedia RBT
service is developed based on the traditional RBT service. The multimedia RBT
service enables subscribers to customize the video or audio chips according to their
favorites or requirements to replace the traditional RBT. When subscribers are called,
the caller can view the customized video or listen to the customized RBT.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 161 of 177

2.10.27 WHFD-575500 Enhanced CLIP
Availability
Specification
None.
Summary
The HLR9820 supports the enhanced CLIP function.
Benefits
For carriers
For subscribers
This service allows the subscriber to determine whether to present the number to
the callees in voice calls and video calls.
Description
The Calling Line Identification Presentation (CLIP) service enables the calling number
to be displayed to the called subscriber. For example, if subscriber A calls subscriber B
who subscriber to the CLIP service, the MS of subscriber B is ringing and also
presents the number of subscriber A.
The enhanced CLIP service is implemented based on service groups; that is, the
HLR9820 allows subscribers to determine whether to display the numbers in voice
calls or video calls. The setting of the enhanced CLIP service can be different for voice
calls and video calls.
Dependency
for other NEs.
2.10.28 WHFD-575600 Batch Query for Subscriber Data
Availability
Specification
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 162 of 177

Summary
The HLR9820 supports batch query for subscriber data.
Benefits
For carriers
This function realizes the batch query for subscriber data, thus facilitating carriers'
management on the HLR.
For subscribers
None.
Description
During the daily operation and management, carriers may need the subscription data of
a large number of subscribers. The HLR9820 helps carriers to query the subscriber
data in batch.
Carriers can query the subscriber data such as subscription data and dynamic data in
batch. Carriers can query the required data by specifying the IMSI file or MSISDN file
if the numbers of subscribers are inconsecutive, or by specifying the starting IMSI or
MSISDN and the number of subscribers if the numbers of subscribers are consecutive.
Dependency
for other NEs.
2.10.29 WHFD-572900 Enhanced Multi-Level Precedence and
Pre-Emption (eMLPP)
Availability
Specification
3GPP22067, 3GPP23067, 3GPP24067
Summary
The eMLPP service allows the network to adopt different network resources allocation
policies (the queuing policy and preemption policy) based on the subscriber's priority
when the network resources are very scarce. Besides, the service also enables the
network to adopt different call connection setup flows and resource assignment flows
to satisfy the requirements in delay by calls of different priorities. When the network
resources are sufficient, the role of the eMLPP service is rather weak, because the
preemption capability of the service cannot be put into full play. When the network
resources are very scarce, the eMLPP service becomes very precious, because it can
help carriers to maximize its benefits.

Feature Description

Issue 1.0 (2013-02-25)
Page 163 of 177

Benefits
For carriers
This service allows carriers to provide differentiated services for subscriber
groups of different levels. When the network resources are scarce, the service can
help carriers to maximize its benefits.
For subscribers
This service enables subscribers of different eMLPP priorities to enjoy
differentiated services.
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 scarce. 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 his/her top priority. Meanwhile, 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 his/her 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 decide whether to adopt quick call setup flow.
Queuing & preemption
When the network resources (including trunk circuits, signaling channels, and
service channels) are scarce, 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.
Dependency
The HLR9820 cooperates with the MSC/VLR/BSC/RNC/MS/UE to implement the
function in compliance with standard protocols. There is no special requirement for
these NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 164 of 177

2.11 WHFD-130000 Authentication Centre Functions
The authentication function is defined according to a protocol, and is accomplished by
the Authentication Centre (AuC). Incorporating the AuC function, the HLR9820
supports 2G and 3GPP standard authentication flows and the respective authentication
encryption algorithms.
The HLR9820 supports the encrypted KI data (WHFD-130200). Out of consideration
of security, the KI data is encrypted during its transfer from the card manufacturer to
carriers. The HLR9820 supports loading the encrypted KI data directly and storing the
encrypted KI in the database. Meanwhile, the key is also encrypted to ensure the
security of the KI data.
The HLR9820 uses K4 as the key, and encrypts/decrypts KI data through the DES or
AES algorithm. The subscriber can select different K4 for encrypting the KI.
2.11.1 WHFD- 130100 Quintuplet to Triplet Conversion
Availability
Specification
3GPP29002 and 3GPP33102
Summary
When a subscriber holding the USIM card roams to the GSM network, the HLR
converts the calculated authentication quintuples into authentication triplets, and sends
them to the VLR/SGSN.
Benefits
For carriers
This service solves the problem that a 3G subscriber cannot pass the
authentication of a 2G network due to different authentication algorithms adopted
by the 3G network and the 2G network. Therefore, the service not only protects
the network security but also allows a 3G subscriber to roam in a 2G network,
well protecting the investment of carriers in the 2G network.
For subscribers
This service allows a 3G subscriber to roam to a 2G network and ensures smooth
and safe voice conversation.
Description
In the GSM network, the MSC/VLR performs subscriber authentication based on
authentication triplets. When a subscriber holding the USIM card roams in the GSM
network, the MSC/VLR sends an authentication request to the HLR/AuC. The HLR
generates authentication quintuples according to the information saved in the USIM
card, and sends them to the MSC/VLR. If the MSC/VLR cannot process them, the

Feature Description

Issue 1.0 (2013-02-25)
Page 165 of 177

authentication fails. In this case, the HLR/AuC converts the authentication quintuples
into authentication triplets, and sends them to the MSC/VLR. In this way, it can ensure
that the 3G subscriber can pass the authentication, and roam in 2G network
successfully.
Dependency
2.11.2 WHFD-130201 DES Algorithm
Availability
Specification
None.
Summary
The DES is a symmetrical encryption algorithm, and was invented by IBM in 70s of
last century. Currently, it has been widely applied in every field.
Benefits
For carriers
The security of the DES algorithm is very high. Without the key, it is very
difficult to decrypt the KI data. Therefore, the DES can effectively protect the KI
data, and ensure the security of the subscriber's authentication data.
For subscribers
None.
Description
The key of the DES algorithm is 56 bits long (or 64 bits long if the parity check bits
are considered). The DES is a group-based encryption algorithm.
The HLR9820 uses K4 as the key, and encrypts/decrypts KI data through the DES
algorithm.
Dependency
for other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 166 of 177

2.11.3 WHFD-130202 AES Algorithm
Availability
Specification
None.
Summary
The advanced encryption standard (AES) is the next generation encryption standard. It
is the most advanced technology in the world, having strength in fast speed and high
security.
Benefits
For carriers
The security of the AES algorithm is very high. Therefore, it effectively protects
the KI data, and ensures the security of the subscriber's authentication data.
For subscribers
None.
Description
The AES is a cryptographic algorithm designated by the National Institute of
Standards and Technology (NIST) on November 15th, 2002, as a replacement for the
DES. The AES series consist of various algorithms and testing standards of modules,
including the Advanced Encryption Standard (AES) in Federal Information Processing
Standards Publication (FIPS PUB) 197 and the Advanced Encryption Standard
Algorithm Validation Suite (AESAVS) designed by the NIST.
Dependency
The HLR9820 realizes the function independently. There is no special requirement for
other NEs.
2.11.4 WHFD-130300 COMP128-1 Algorithm
Availability
Specification
3GPP29002

Feature Description

Issue 1.0 (2013-02-25)
Page 167 of 177

Summary
The HLR9820 supports the COMP128-1 algorithm.
Benefits
For carriers
This service provides basic authentication algorithm to satisfy basic network
authentication requirements.
For subscribers
None.
Description
The COMP128-1 is a standard algorithm that realizes the A3 algorithm and the A8
algorithm.
The A3 algorithm is also referred to as the authentication algorithm. It calculates the
SRES based on the RAND generated by the HLR/AuC and the authentication key Ki
of the SIM card. The SRES is used to identify a mobile subscriber.
The A8 algorithm is also referred to as encryption key generator. It calculates the
encryption key Kc based on the RAND and Ki. The A5 algorithm uses Kc as the key
and is used to encrypt the signaling data and subscriber data transmitted over
encrypted channels.
Dependency
Availability
Specification
3GPP29002
Summary
Benefits
For carriers
The COMP128-1 is widely applied in the GSM. Therefore, the security of the
GSM network is not well protected. In comparison, the COMP128-2 algorithm is
more competitive, and can well protect the authentication security.

Feature Description

Issue 1.0 (2013-02-25)
Page 168 of 177

For subscribers
None.
Description
The HLR9820 supports the COMP128-2 algorithm. The COMP128-2 is a standard
algorithm that realizes the A3 algorithm and the A8 algorithm.
encrypted channels.
Dependency
Availability
Specification
3GPP29002
Summary
Benefits
For carriers
Compared with COMP128-2, the COMP128-3 algorithm can better protect the
security of authentication security.
For subscribers
None.
Description
The COMP128-3 is a standard algorithm that realizes the A3 algorithm and the A8
algorithm.

Feature Description

Issue 1.0 (2013-02-25)
Page 169 of 177

encrypted channels.
Dependency
2.11.7 WHFD-130600 Milenage Algorithm
Availability
Specification
3GPP29002, 3GPP35205, and 3GPP35206
Summary
The HLR9820 supports the 3G Milenage authentication algorithm.
Benefits
For carriers
This service can satisfy the requirements of 3G MS/network for authentication
algorithms.
For subscribers
None.
Description
The Milenage authentication algorithm is a 3G network authentication algorithm. The
USIM card supports the Milenage authentication algorithm only.
Dependency
2.11.8 WHFD-130700 G-Milenage Algorithm
Availability

Feature Description

Issue 1.0 (2013-02-25)
Page 170 of 177

Specification
3GPP29002, 3GPP35205, and 3GPP35206
Summary
The HLR9820 supports the G-Milenage authentication algorithm. The G-Milenage
algorithm is the Milenage algorithm applied in the GSM network.
Benefits
For carriers
algorithms. It supports multiple authentication algorithms.
For subscribers
None.
Description
The G-Milenage is a GSM network authentication algorithm. The SIM card supports
the G-Milenage authentication algorithm. The G-Milenage algorithm differs from the
Milenage algorithm in that the G-Milenage outputs the calculation results in
authentication triplets, that is, it converts the quintuples into triplets. While the
Milenage algorithm outputs the calculation results in authentication quintuples.
Dependency
2.11.9 WHFD-130800 XOR Algorithm
Availability
Specification
None.
Summary
The HLR9820 supports the XOR algorithm.
Benefits
For carriers
algorithms. It supports multiple authentication algorithms.

Feature Description

Issue 1.0 (2013-02-25)
Page 171 of 177

For subscribers
None.
Description
The XOR is a GSM network authentication algorithm. The XOR algorithm is
implemented based on a random number RAND generated by the HLR/AuC and the
authentication key Ki mapping the SIM. After the XOR algorithm is complete, the
SRES and Kc are obtained. The SRES is used for authenticating subscriber identities,
and the Kc is used as the encryption key. The A5 algorithm works in conjunction with
the Kc to cipher signaling and subscriber data transferred in channels.
Dependency
The HLR9820 cooperates with the MSC/VLR and the MS to implements this function.
2.12 WHFD-570403 Redundancy Functions
The HLR9820 supports the following redundancy functions:
N+1 Compatibility Redundancy (WHFD-570502)
Seamless Geography Redundancy (WHFD-010300)
2.12.1 WHFD-570502 N+1 Compatibility Redundancy
Availability
Specification
None.
Summary
The HLR9820 supports the N+1 Compatibility Redundancy solution.
Benefits
For carriers
This service can greatly improve the network availability. When the active HLR
becomes faulty, the other HLR takes over all services immediately.
Advantages: Multiple HLRs share an HLR disaster center, saving the subscriber's
investment.
For subscribers
None.

Feature Description

Issue 1.0 (2013-02-25)
Page 172 of 177

Description
In the N+1 Compatibility Redundancy solution, the active HLR can be the HLR of
various vendors. There is only one redundancy HLR, which can take over the services
of N active HLRs. The active HLR processes the services; the redundancy HLR is
ready to take over the services of the active HLR. In this solution, the redundancy
HLR can take over the services of multiple active HLRs simultaneously, as long as the
total capacity of these active HLRs is slightly smaller than that of the redundancy
HLR.
Dependency
It is required to configure the corresponding data in the STP/MSC, and establish
connections between the STP/MSC and the redundancy HLR.
2.12.2 WHFD-010300 Seamless Geography Redundancy
Availability
Specification
None.
Summary
The HLR9820 supports the seamless geography redundancy solution, which allows
the active HLR and the redundancy HLR to be deployed in different places. In
addition, the FE and the BE can be separately deployed. When the subscriber data in
the active HLR is modified, the modified data is sent to the redundancy HLR in real
time. Thus, data synchronization between the active and redundancy HLRs is ensured.
The HLR provides the periodic data check function to ensure data consistency
between active and redundancy HLRs.
Benefits
For carriers
The HLR supporting the seamless geography redundancy solution has higher
reliability and security. This reduces the CAPEX and OPEX of carriers and
improves the competitiveness of carriers.
For subscribers
None.
Description
The HLR9820 supports three types of seamless geography redundancy solutions:
1+1 mated seamless geography redundancy solution: The FE and the BE are
integrated. The two HLRs implement data synchronization over the data layer.

Feature Description

Issue 1.0 (2013-02-25)
Page 173 of 177

The active HLR processes all the services, and the redundancy HLR does not
process services in normal conditions.
1+1 load-sharing seamless geography redundancy solution: The FE and the BE
are integrated. The two HLRs implement data synchronization over the data layer.
The two HLRs process services simultaneously, and each HLR backs up the data
of the other one.
FE and BE separated seamless geography redundancy solution: The FE and the
BE are deployed separately. They work in active/standby or load-sharing mode.
The seamless geography redundancy solutions supported by the HLR9820 have the
following features:
Using dedicated IP channels to automatically synchronize dynamic and static data
between the active and redundancy HLRs in real time
Providing the data consistency check function to ensure data consistency
Supporting automatic active-to-redundancy HLR switchover, which ensures the
uninterrupted services
Supporting separated deployment of the FE and the BE, which allows carriers to
perform network planning flexibly
Dependency
for other NEs.
2.12.3 WHFD-010301 Geographic Distributed Deployment of
the FEs
Availability
Specification
None.
Summary
The HLR9820 consists of FEs and BEs. An HLR may contain multiple FEs. These
FEs can be deployed as a physical entity (integrated deployment) or separately
(distributed deployment). In integrated deployment, the FEs work in the same physical
entity; in distributed deployment, the FEs work in different physical entities. The FEs
work in load sharing mode. When an FE fails, other FEs take over the load of the
faulty FE to ensure the normal running of the system. If FEs adopt the distributed
deployment, they can be distributed geographically. When an NE requests to
communicate with the FEs, the system establishes a connection between the NE and
the nearest FE.
Benefits
For carriers

Feature Description

Issue 1.0 (2013-02-25)
Page 174 of 177

Separation of service from data enables the FE to concentrate on leading in and
processing signaling. The separation also brings convenience and flexibility to the
carrier. In the case of geographic distributed deployment, requests from the local MSC
are sent to the local FE directly, without forwarding by the STP. Working in load
sharing mode, the FEs have greatly enhanced the network reliability. When the
network capacity is insufficient, you can expand the network capacity by only adding
FEs to the network.
For subscribers
None.
Description
The FEs of the HLR mainly accomplish the processing of signaling and service logics.
The FEs deployed in different locations are disaster tolerant, and work in load sharing
mode, as shown in Figure 2-1.
Figure 2-1 Geographic distributed deployment of the FEs

An FE of the HLR9820 consists of two modules:
Signaling Access Unit (SAU)
Service Control Function (SCF)
The SAU works in load sharing mode, and sends services to the SCF according to the
dialogue number of the TCAP and the load sharing principle. The SCF also works in

Feature Description

Issue 1.0 (2013-02-25)
Page 175 of 177

load sharing mode, and distributes data requests to the DRUs. Figure 2-2 shows the
internal modules of the FE.
Figure 2-2 Internal modules of the FE

Dependency
for other NEs.
2.12.4 WHFD-010302 Geographic Distributed Deployment of
the BEs
Availability
Specification
None.
Summary
The HLR9820 consists of FEs and BEs. An HLR may contain multiple BEs. These
BEs can be deployed as a physical entity (integrated deployment) or separately
(distributed deployment). In integrated deployment, the BEs work in the same physical
entity; in distributed deployment, the BEs work in different physical entities. The BEs
can be deployed in different locations. Each BE stores all subscriber data. The
subscriber data in these BEs are well synchronized. In this way, the BEs are disaster
tolerant. The BE stores the subscriber data of the FEs, and allows addition, deletion,
update and query of subscriber data upon request from the FEs.
Benefits
For carriers
The distributed deployment of the BEs enables carriers to provide more services and
attract more subscribers.
For subscribers
None..

Feature Description

Issue 1.0 (2013-02-25)
Page 176 of 177

Description
The BE of the HLR9820 consists of the following modules:
SMF. The SMF manages subscription data, and works in load sharing mode. The
SMF processes MML commands of the BOSS forwarded by the SMU server.
During the processing, the SMF forwards the data requests to the DRU for
processing.
DRU. The DRU queries the routing table according to the key (IMSI or MSISDN)
in the requests from the SCF and the SMF, and forwards the data requests to the
DSU. The DRUs work in load sharing mode. Each DRU contains all routing data.
The DRU distributes the data requests to DSU clusters according to the routing
information.
DSU. The DSU stores subscriber data in a distributed manner, and provides data
access service. Several DSUs comprise a DSU cluster. Each DSU cluster is
responsible for a portion of the subscriber data; all DSU clusters are responsible
for all subscriber data. These data are stored in the HLR memory databases.
SMU. The SMU provides MML interfaces for the BOSS, converts MML
commands into internal modification commands, and forwards them to the SMF.
Currently, the SMU works in active/standby mode.
The DRUs and the DSUs are deployed separately in clusters. The DRUs and DSUs in
the same cluster have the same data, and work in master/slave load sharing mode, as
shown in Figure 2-3.
Figure 2-3 Geographic distributed deployment of the BEs

Dependency
This function complies with standard protocols. There is no special requirement for
other NEs.

Feature Description

Issue 1.0 (2013-02-25)
Page 177 of 177

GSM R Hlr9820

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

GSM R Hlr9820

Загружено:

Авторское право:

Доступные форматы

GSM-R HLR9820 V900R003 Feature

Вам также может понравиться